[Kernel-packages] [Bug 2015397] 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 2015397 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2015397 Title: [Lenovo Legion 5i pro] 90 second delay during boot (Failed to start systemd-backlight@backlight:nvidia_0.service) Status in linux package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-525 package in Ubuntu: New Bug description: Hi, Lunar, 525.105.17 I get a very very very slow boot using dynamic graphics in my Lenovo Legion 5i pro i7/3070 Ti. Using discrete graphics is ok. Using Nouveau with hybrid graphics is ok. After some research, it seems the culprit is: Failed to start systemd-backlight@backlight:nvidia_0.service - Load/Save Screen Backlight Brightness of backlight:nvidia_0. systemd blame: 1min 34.046s plymouth-quit-wait.service 1min 30.278s gpu-manager.service To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2015397/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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 timeout on B-KVM
** Summary changed: - hyperv_synic in ubuntu_kvm_unit_tests failed on B-KVM / B-Oracle-5.3 + hyperv_synic in ubuntu_kvm_unit_tests timeout on B-KVM -- 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 timeout on B-KVM 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 2015503] [NEW] Xorg freeze. Can not login because black screen (GPU: Nvidia Geforce RTX 3060).
You have been subscribed to a public bug: The last time I used my computer (right now) I applied 3 or 4 system updates before to ask to reboot. Now when booting the screen is black (impossible to login). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-69.76-generic 5.15.87 Uname: Linux 5.15.0-69-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 515.105.01 Mon Feb 27 12:49:44 UTC 2023 GCC version: ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass Date: Thu Apr 6 22:13:19 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation TigerLake-H GT1 [UHD Graphics] [8086:9a68] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] TigerLake-H GT1 [UHD Graphics] [1025:153b] NVIDIA Corporation GA106M [GeForce RTX 3060 Mobile / Max-Q] [10de:2520] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] GA106M [GeForce RTX 3060 Mobile / Max-Q] [1025:1544] InstallationDate: Installed on 2022-12-12 (115 days ago) InstallationMedia: Kubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Acer Nitro AN517-54 ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-69-generic root=UUID=3929c5bf-9857-465d-ba3d-a34cf1bdd89d ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/02/2022 dmi.bios.release: 1.17 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.17 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Kamiq_TLS dmi.board.vendor: TGL dmi.board.version: V1.17 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.17 dmi.ec.firmware.release: 1.10 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.17:bd06/02/2022:br1.17:efr1.10:svnAcer:pnNitroAN517-54:pvrV1.17:rvnTGL:rnKamiq_TLS:rvrV1.17:cvnAcer:ct10:cvrV1.17:sku: dmi.product.family: Nitro 5 dmi.product.name: Nitro AN517-54 dmi.product.sku: dmi.product.version: V1.17 dmi.sys.vendor: Acer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.9 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: nvidia-graphics-drivers-515 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug false-gpu-hang freeze jammy ubuntu -- Xorg freeze. Can not login because black screen (GPU: Nvidia Geforce RTX 3060). https://bugs.launchpad.net/bugs/2015503 You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-515 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 2015503] Re: Xorg freeze. Can not login because black screen (GPU: Nvidia Geforce RTX 3060).
Seems the driver update messed up somehow: [4.214845] NVRM: API mismatch: the client has the version 515.86.01, but NVRM: this kernel module has the version 515.105.01. Please NVRM: make sure that this kernel module and all NVIDIA driver NVRM: components have the same version. ** Package changed: xorg (Ubuntu) => nvidia-graphics-drivers-515 (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-515 in Ubuntu. https://bugs.launchpad.net/bugs/2015503 Title: Xorg freeze. Can not login because black screen (GPU: Nvidia Geforce RTX 3060). Status in nvidia-graphics-drivers-515 package in Ubuntu: New Bug description: The last time I used my computer (right now) I applied 3 or 4 system updates before to ask to reboot. Now when booting the screen is black (impossible to login). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-69.76-generic 5.15.87 Uname: Linux 5.15.0-69-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 515.105.01 Mon Feb 27 12:49:44 UTC 2023 GCC version: ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass Date: Thu Apr 6 22:13:19 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation TigerLake-H GT1 [UHD Graphics] [8086:9a68] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] TigerLake-H GT1 [UHD Graphics] [1025:153b] NVIDIA Corporation GA106M [GeForce RTX 3060 Mobile / Max-Q] [10de:2520] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] GA106M [GeForce RTX 3060 Mobile / Max-Q] [1025:1544] InstallationDate: Installed on 2022-12-12 (115 days ago) InstallationMedia: Kubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Acer Nitro AN517-54 ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-69-generic root=UUID=3929c5bf-9857-465d-ba3d-a34cf1bdd89d ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/02/2022 dmi.bios.release: 1.17 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.17 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Kamiq_TLS dmi.board.vendor: TGL dmi.board.version: V1.17 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.17 dmi.ec.firmware.release: 1.10 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.17:bd06/02/2022:br1.17:efr1.10:svnAcer:pnNitroAN517-54:pvrV1.17:rvnTGL:rnKamiq_TLS:rvrV1.17:cvnAcer:ct10:cvrV1.17:sku: dmi.product.family: Nitro 5 dmi.product.name: Nitro AN517-54 dmi.product.sku: dmi.product.version: V1.17 dmi.sys.vendor: Acer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.9 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-515/+bug/2015503/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2015670] Re: Kernel loop PCIe Bus Error on RTL810xE
Apr 09 09:30:55 corrado-n8-ll-0402 kernel: pcieport :00:1d.0: AER: Multiple Corrected error received: :01:00.0 Apr 09 09:30:55 corrado-n8-ll-0402 kernel: r8169 :01:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) Apr 09 09:30:55 corrado-n8-ll-0402 kernel: r8169 :01:00.0: device [10ec:8136] error status/mask=0001/6000 Apr 09 09:30:55 corrado-n8-ll-0402 kernel: r8169 :01:00.0:[ 0] RxErr (First) Apr 09 09:30:55 corrado-n8-ll-0402 kernel: pcieport :00:1d.0: AER: Multiple Corrected error received: :01:00.0 Apr 09 09:30:55 corrado-n8-ll-0402 kernel: r8169 :01:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) Apr 09 09:30:55 corrado-n8-ll-0402 kernel: r8169 :01:00.0: device [10ec:8136] error status/mask=0001/6000 Apr 09 09:30:55 corrado-n8-ll-0402 kernel: r8169 :01:00.0:[ 0] RxErr (First) Apr 09 09:30:56 corrado-n8-ll-0402 kernel: pcieport :00:1d.0: AER: Multiple Corrected error received: :01:00.0 Apr 09 09:30:56 corrado-n8-ll-0402 kernel: r8169 :01:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) Apr 09 09:30:56 corrado-n8-ll-0402 kernel: r8169 :01:00.0: device [10ec:8136] error status/mask=0001/6000 Apr 09 09:30:56 corrado-n8-ll-0402 kernel: r8169 :01:00.0:[ 0] RxErr (First) ** Summary changed: - Kernel loop PCIe Bus Error on RTL810xE + [r8169] Kernel loop PCIe Bus Error on RTL810xE -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2015670 Title: [r8169] Kernel loop PCIe Bus Error on RTL810xE Status in linux package in Ubuntu: Confirmed Bug description: Kernel loop after login This happens with both kernels 6.2.0-18 and 6.2.0-19 on 2 different partitions of same PC: Partition installed from beta and partition from ISO dated 04/02. No problem on same PC different partitions of same disk with Ubuntu Focal, Jammy and Kinetic Problem does not occur with kernel 5.19.17-051917-generic installed from https://kernel.ubuntu.com/~kernel-ppa/mainline/ Adding journalctl -b related to the problem note: I opened another bug for this problem blaming gnome-shell but it's wrong https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2015540 ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: linux-image-6.2.0-19-generic 6.2.0-19.19 ProcVersionSignature: Ubuntu 6.2.0-19.19-generic 6.2.6 Uname: Linux 6.2.0-19-generic x86_64 ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: corrado1511 F wireplumber /dev/snd/seq:corrado1508 F pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Apr 9 09:33:06 2023 InstallationDate: Installed on 2023-04-07 (1 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Daily amd64 (20230402) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0bda:5520 Realtek Semiconductor Corp. Integrated_Webcam_HD Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications Bus 001 Device 002: ID 145f:02b5 Trust Trust Wireless Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 3793 ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-19-generic root=UUID=78239576-b8af-4c66-bf15-8d5ee9a63d35 ro quiet splash RelatedPackageVersions: linux-restricted-modules-6.2.0-19-generic N/A linux-backports-modules-6.2.0-19-generic N/A linux-firmware20230323.gitbcdcfbcf-0ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/17/2019 dmi.bios.release: 1.5 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.0 dmi.board.name: 0C1PF2 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.0:bd12/17/2019:br1.5:svnDellInc.:pnInspiron3793:pvr:rvnDellInc.:rn0C1PF2:rvrA00:cvnDellInc.:ct10:cvr:sku097A: dmi.product.family: Inspiron dmi.product.name: Inspiron 3793 dmi.product.sku: 097A dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2015670/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2015972] [NEW] Dell: Enable speaker mute hotkey LED indicator
Public bug reported: [Feature Description] When users press the speaker mute hotkey and the speaker is muted, the speaker mute LED indicator will light up. When the speaker is not muted, the speaker mute LED indicator will light out. [Test Case] 1. run G16 with target kernel. 2. press the mute hotkey 3. check if speaker mute led can be switched. [Where problems could occur] Low, just register a speaker mute led control for dell-laptop. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: linux-oem-6.1 (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Affects: linux-oem-6.1 (Ubuntu Jammy) Importance: Undecided Status: New ** Affects: linux (Ubuntu Kinetic) Importance: Undecided Status: New ** Affects: linux-oem-6.1 (Ubuntu Kinetic) Importance: Undecided Status: New ** Affects: linux (Ubuntu Lunar) Importance: Undecided Status: New ** Affects: linux-oem-6.1 (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: linux-oem-6.1 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: linux-oem-6.1 (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-oem-6.1 (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: linux-oem-6.1 (Ubuntu Kinetic) 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/2015972 Title: Dell: Enable speaker mute hotkey LED indicator Status in linux package in Ubuntu: New Status in linux-oem-6.1 package in Ubuntu: New Status in linux source package in Jammy: New Status in linux-oem-6.1 source package in Jammy: New Status in linux source package in Kinetic: New Status in linux-oem-6.1 source package in Kinetic: New Status in linux source package in Lunar: New Status in linux-oem-6.1 source package in Lunar: New Bug description: [Feature Description] When users press the speaker mute hotkey and the speaker is muted, the speaker mute LED indicator will light up. When the speaker is not muted, the speaker mute LED indicator will light out. [Test Case] 1. run G16 with target kernel. 2. press the mute hotkey 3. check if speaker mute led can be switched. [Where problems could occur] Low, just register a speaker mute led control for dell-laptop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2015972/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2004132] Re: btrfs/154: rename fails with EOVERFLOW when calculating item size during item key collision
bionic:linux-snapdragon was not released last cycle, hence it asks for verification again. Given that the main kernel was verified, I will mark this as verified as well. ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2004132 Title: btrfs/154: rename fails with EOVERFLOW when calculating item size during item key collision Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Status in linux source package in Focal: Fix Released Bug description: BugLink: https://bugs.launchpad.net/bugs/2004132 [Impact] xfstests btrfs/154 fails on both Bionic and Focal, leading to a kernel oops and the btrfs volume being forced readonly. In btrfs, item key collision is allowed for some item types, namely dir item and inode references. When inserting items into the btree, there are two objects, the btrfs_item and the item data. These objects must fit within the btree nodesize. When a hash collision occurs, and we call btrfs_search_slot() to place the objects in the tree, when btrfs_search_slot() reaches the leaf node, a check is performed to see if we need to split the leaf. The check is incorrect, returning that we need to split the leaf, since it thinks that both btrfs_item and the item data need to be inserted, when in reality, the item can be merged with the existing one and no new btrfs_item will be inserted. split_leaf() will return EOVERFLOW from following code: if (extend && data_size + btrfs_item_size_nr(l, slot) + sizeof(struct btrfs_item) > BTRFS_LEAF_DATA_SIZE(fs_info)) return -EOVERFLOW; In the rename case, btrfs_check_dir_item_collision() is called early stages of treewalking, and correctly calculates the needed size, taking into account that a hash collision has occurred. data_size = sizeof(*di) + name_len; if (data_size + btrfs_item_size_nr(leaf, slot) + sizeof(struct btrfs_item) > BTRFS_LEAF_DATA_SIZE(root->fs_info)) The two sizes reported from btrfs_check_dir_item_collision() and btrfs_search_slot() are different, and rename fails due to split_leaf() returning -EOVERFLOW, leading to transaction abort and forcing the volume readonly. Kernel oops: BTRFS: Transaction aborted (error -75) WARNING: CPU: 0 PID: 2921 at /build/linux-fTmV3T/linux-4.15.0/fs/btrfs/inode.c:10217 btrfs_rename+0xcf1/0xdf0 [btrfs] CPU: 0 PID: 2921 Comm: python3 Not tainted 4.15.0-202-generic #213-Ubuntu RIP: 0010:btrfs_rename+0xcf1/0xdf0 [btrfs] RSP: 0018:9e6f4183fd20 EFLAGS: 00010282 RAX: RBX: 91a493f27b98 RCX: 0006 RDX: 0007 RSI: 0096 RDI: 91a4bfc1b4d0 RBP: 9e6f4183fdc0 R08: 02b4 R09: 0004 R10: R11: 0001 R12: 0236 R13: 91a493f56518 R14: 91a4b6b57b40 R15: 91a493f27b98 FS: 7f6041081740() GS:91a4bfc0() knlGS: CS: 0010 DS: ES: CR0: 80050033 CR2: 7f6040fe84c8 CR3: 00015c8ca005 CR4: 00760ef0 PKRU: 5554 Call Trace: btrfs_rename2+0x1d/0x30 [btrfs] vfs_rename+0x46e/0x960 SyS_rename+0x362/0x3c0 do_syscall_64+0x73/0x130 entry_SYSCALL_64_after_hwframe+0x41/0xa6 Code: 0f ba a8 d0 cd 00 00 02 72 2b 41 83 f8 fb 0f 84 d9 00 00 00 44 89 c6 48 c7 c7 68 43 4b c0 44 89 55 80 44 89 45 98 e8 8f 5c a6 d0 <0f> 0b 44 8b 45 98 44 8b 55 80 44 89 55 80 44 89 c1 44 89 45 98 ---[ end trace 9c6b87a19f4436f3 ]--- BTRFS: error (device vdd) in btrfs_rename:10217: errno=-75 unknown BTRFS info (device vdd): forced readonly [Testcase] Start a fresh Bionic or Focal VM. Attach two scratch disks, I used standard virtio disks with 3gb of storage each. These disks are /dev/vdc and /dev/vdd. Compile xfstests: $ sudo apt-get install acl attr automake bc dbench dump e2fsprogs fio gawk \ gcc git indent libacl1-dev libaio-dev libcap-dev libgdbm-dev libtool \ libtool-bin libuuid1 lvm2 make psmisc python3 quota sed \ uuid-dev uuid-runtime xfsprogs linux-headers-$(uname -r) sqlite3 make $ sudo apt-get install f2fs-tools ocfs2-tools udftools xfsdump \ xfslibs-dev $ git clone git://git.kernel.org/pub/scm/fs/xfs/xfstests-dev.git $ cd xfstests-dev $ make $ sudo su # mkdir /test # mkdir /scratch # mkfs.btrfs -f /dev/vdc # cat << EOF >> ./local.config export TEST_DEV=/dev/vdc export TEST_DIR=/test export SCRATCH_DEV=/dev/vdd export SCRATCH_MNT=/scratch EOF # ./check btrfs/154 btrfs/154 _check_dmesg: something found in dmesg (see /home/ubuntu/xfstests-dev/results//btrfs/154.dmesg) - output mismatch (see /home/ubuntu/xfstests-dev/results//btrfs/154.out.bad) -
[Kernel-packages] [Bug 2015972] 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 2015972 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 Jammy) Status: New => Incomplete ** Changed in: linux (Ubuntu Kinetic) 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/2015972 Title: Dell: Enable speaker mute hotkey LED indicator Status in linux package in Ubuntu: Incomplete Status in linux-oem-6.1 package in Ubuntu: New Status in linux source package in Jammy: Incomplete Status in linux-oem-6.1 source package in Jammy: New Status in linux source package in Kinetic: Incomplete Status in linux-oem-6.1 source package in Kinetic: New Status in linux source package in Lunar: Incomplete Status in linux-oem-6.1 source package in Lunar: New Bug description: [Feature Description] When users press the speaker mute hotkey and the speaker is muted, the speaker mute LED indicator will light up. When the speaker is not muted, the speaker mute LED indicator will light out. [Test Case] 1. run G16 with target kernel. 2. press the mute hotkey 3. check if speaker mute led can be switched. [Where problems could occur] Low, just register a speaker mute led control for dell-laptop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2015972/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2015751] [NEW] Screen output is laggy after boot
You have been subscribed to a public bug: The screen constantly lags and need several seconds to update the output on my device and sometimes causes horizontal stripes every time I boot from normal mode. It keeps lagging even when I press Ctrl+Alt+Fn and enter terminal mode. However, mouse and keyboard input still works as normal. The problem first appeared after I resolved a package dependency issue on Feb 17 (but I cannot remember what package was causing the dependency issue) and then rebooted the system. But the problem disappears if I choose to boot from recovery mode (this is how I gathered information for my device). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Apr 10 19:52:10 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Alder Lake-P Integrated Graphics Controller [8086:46a6] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0b3e] InstallationDate: Installed on 2022-04-30 (344 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Dell Inc. Vostro 5620 ProcEnviron: LANGUAGE=zh_CN:zh TERM=xterm-256color PATH=(custom, no user) LANG=zh_CN.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-38-generic root=UUID=1438c542-3a97-452b-822c-b17b4c0120a2 ro recovery nomodeset dis_ucode_ldr SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/13/2022 dmi.bios.release: 1.11 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.11.0 dmi.board.name: 0HRNCW 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:bd12/13/2022:br1.11:svnDellInc.:pnVostro5620:pvr:rvnDellInc.:rn0HRNCW:rvrA00:cvnDellInc.:ct10:cvr:sku0B3E: dmi.product.family: Vostro dmi.product.name: Vostro 5620 dmi.product.sku: 0B3E dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 22.2.5-0ubuntu0.1~22.04.1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.9 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: linux-hwe-5.19 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy performance ubuntu -- Screen output is laggy after boot https://bugs.launchpad.net/bugs/2015751 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.19 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 2015855] Re: Add split lock detection for EMR
** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Changed in: linux (Ubuntu Jammy) 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/2015855 Title: Add split lock detection for EMR Status in linux package in Ubuntu: Confirmed Status in linux source package in Jammy: Confirmed Bug description: SRU Justification [Impact] #2009315 adds support for their new Emerald Rapids CPU to Jammy. Commit d7ce15e1d4162ab5e56dead10d4ae69a6b5c8ee8 from linux-next introduces support for Split lock detection. [Testing] Kernel was built on cbd and boot tested on a VM. TODO ask for help from intel. [Regression potential] TODO assess this To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2015855/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2015751] Re: Screen output is laggy after boot
*** This bug is a duplicate of bug 2007668 *** https://bugs.launchpad.net/bugs/2007668 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 2007668, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** Package changed: xorg (Ubuntu) => linux-hwe-5.19 (Ubuntu) ** This bug has been marked a duplicate of bug 2007668 Intel 12th gen: Noisy screen corruption during cursor movement, and whole screen freezes, in 5.19 kernels -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2015751 Title: Screen output is laggy after boot Status in linux-hwe-5.19 package in Ubuntu: New Bug description: The screen constantly lags and need several seconds to update the output on my device and sometimes causes horizontal stripes every time I boot from normal mode. It keeps lagging even when I press Ctrl+Alt+Fn and enter terminal mode. However, mouse and keyboard input still works as normal. The problem first appeared after I resolved a package dependency issue on Feb 17 (but I cannot remember what package was causing the dependency issue) and then rebooted the system. But the problem disappears if I choose to boot from recovery mode (this is how I gathered information for my device). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Apr 10 19:52:10 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Alder Lake-P Integrated Graphics Controller [8086:46a6] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0b3e] InstallationDate: Installed on 2022-04-30 (344 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Dell Inc. Vostro 5620 ProcEnviron: LANGUAGE=zh_CN:zh TERM=xterm-256color PATH=(custom, no user) LANG=zh_CN.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-38-generic root=UUID=1438c542-3a97-452b-822c-b17b4c0120a2 ro recovery nomodeset dis_ucode_ldr SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/13/2022 dmi.bios.release: 1.11 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.11.0 dmi.board.name: 0HRNCW 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:bd12/13/2022:br1.11:svnDellInc.:pnVostro5620:pvr:rvnDellInc.:rn0HRNCW:rvrA00:cvnDellInc.:ct10:cvr:sku0B3E: dmi.product.family: Vostro dmi.product.name: Vostro 5620 dmi.product.sku: 0B3E dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 22.2.5-0ubuntu0.1~22.04.1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.9 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.19/+bug/2015751/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2007668] Re: Intel 12th gen: Noisy screen corruption during cursor movement, and whole screen freezes, in 5.19 kernels
** Description changed: + WORKAROUND: + + Add kernel parameter: i915.enable_psr=0 + + ORIGINAL DESCRIPTION: + This always happens when the cursor sweeps over a height range (approximately 960px ~ 990px from the top). Even when watching a video, the top of the screen sometimes glitches. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Feb 17 16:24:32 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: - Intel Corporation Device [8086:46aa] (rev 0c) (prog-if 00 [VGA controller]) -Subsystem: Dell Device [1028:0b14] + Intel Corporation Device [8086:46aa] (rev 0c) (prog-if 00 [VGA controller]) + Subsystem: Dell Device [1028:0b14] InstallationDate: Installed on 2022-08-13 (187 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Dell Inc. XPS 9315 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-32-generic root=UUID=3ba28059-7aea-46a5-bf4e-44dd0203b83d ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/04/2023 dmi.bios.release: 1.7 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.1 dmi.board.name: 02GGG1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.1:bd01/04/2023:br1.7:svnDellInc.:pnXPS9315:pvr:rvnDellInc.:rn02GGG1:rvrA00:cvnDellInc.:ct10:cvr:sku0B14: dmi.product.family: XPS dmi.product.name: XPS 9315 dmi.product.sku: 0B14 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2007668 Title: Intel 12th gen: Noisy screen corruption during cursor movement, and whole screen freezes, in 5.19 kernels Status in linux package in Ubuntu: Fix Released Status in linux-hwe-5.19 package in Ubuntu: Confirmed Bug description: WORKAROUND: Add kernel parameter: i915.enable_psr=0 ORIGINAL DESCRIPTION: This always happens when the cursor sweeps over a height range (approximately 960px ~ 990px from the top). Even when watching a video, the top of the screen sometimes glitches. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Feb 17 16:24:32 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Device [8086:46aa] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0b14] InstallationDate: Installed on 2022-08-13 (187 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Dell Inc. XPS 9315 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-32-generic root=UUID=3ba28059-7aea-46a5-bf4e-44dd0203b83d ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/04/2023 dmi.bios.release: 1.7 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.1 dmi.board.name: 02GGG1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.1:bd01/04/2023:br1.7:svnDellInc.:pnXPS9315:pvr:rvnDellInc.:rn02GGG1:rvrA00:cvnDellInc.:ct10:cvr:sku0B14: dmi.product.family: XPS dmi.product.name: XPS 9315 dmi.product.sku: 0B14 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A versio
[Kernel-packages] [Bug 1987507] Autopkgtest regression report (linux-meta-hwe-5.15/5.15.0.70.77~20.04.31)
All autopkgtests for the newly accepted linux-meta-hwe-5.15 (5.15.0.70.77~20.04.31) for focal have finished running. The following regressions have been reported in tests triggered by the package: systemd/245.4-4ubuntu3.20 (amd64, armhf, ppc64el, s390x) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#linux-meta-hwe-5.15 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-hwe-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/1987507 Title: Migrate oem-20.04 to hwe-5.15 Status in linux-meta-hwe-5.15 package in Ubuntu: Invalid Status in linux-restricted-modules-hwe-5.15 package in Ubuntu: Invalid Status in linux-meta-hwe-5.15 source package in Focal: New Status in linux-restricted-modules-hwe-5.15 source package in Focal: New Bug description: [Impact] Migrate oem-5.14 to hwe-5.15 now that there should be no functional regressions left anymore. [Test case] Update a machine with oem-5.14 metapackages to the proposed ones, and verify that all packages (including nvidia etc) migrate properly. [Where things could go wrong] In theory we might miss a package to transition, but at this point this is unlikely. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe-5.15/+bug/1987507/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2015414] Re: 5.15.0-69 ice driver deadlocks with bonded e810 NICs
*** This bug is a duplicate of bug 2004262 *** https://bugs.launchpad.net/bugs/2004262 ** This bug has been marked a duplicate of bug 2004262 Intel E810 NICs driver in causing hangs when booting and bonds configured -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2015414 Title: 5.15.0-69 ice driver deadlocks with bonded e810 NICs Status in linux package in Ubuntu: Confirmed Bug description: The ice driver in the 5.15.0-69 kernel deadlocks on rtnl_lock() when adding e810 NICs to a bond interface. Booting with `sysctl.hung_task_panic=1` and `sysctl.hung_task_all_cpu_backtrace=1` added to the kernel command-line shows (among lots of other output): ``` [ 244.980100] INFO: task kworker/6:1:182 blocked for more than 120 seconds. [ 244.988431] Not tainted 5.15.0-69-generic #76-Ubuntu [ 244.995279] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 245.004826] task:kworker/6:1 state:D stack:0 pid: 182 ppid: 2 flags:0x4000 [ 245.015017] Workqueue: events linkwatch_event [ 245.020734] Call Trace: [ 245.024144] [ 245.027137] __schedule+0x24e/0x590 [ 245.031848] schedule+0x69/0x110 [ 245.036228] schedule_preempt_disabled+0xe/0x20 [ 245.042066] __mutex_lock.constprop.0+0x267/0x490 [ 245.047993] __mutex_lock_slowpath+0x13/0x20 [ 245.053432] mutex_lock+0x38/0x50 [ 245.057714] rtnl_lock+0x15/0x20 [ 245.061901] linkwatch_event+0xe/0x30 [ 245.066571] process_one_work+0x228/0x3d0 [ 245.071607] worker_thread+0x53/0x420 [ 245.076260] ? process_one_work+0x3d0/0x3d0 [ 245.081493] kthread+0x127/0x150 [ 245.085592] ? set_kthread_struct+0x50/0x50 [ 245.090769] ret_from_fork+0x1f/0x30 [ 245.095266] ``` and ``` [ 245.530629] INFO: task ifenslave:849 blocked for more than 121 seconds. [ 245.540433] Not tainted 5.15.0-69-generic #76-Ubuntu [ 245.549050] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 245.558960] task:ifenslave state:D stack:0 pid: 849 ppid: 847 flags:0x4002 [ 245.570930] Call Trace: [ 245.576175] [ 245.581018] __schedule+0x24e/0x590 [ 245.587445] schedule+0x69/0x110 [ 245.593631] schedule_timeout+0x103/0x140 [ 245.600573] __wait_for_common+0xab/0x150 [ 245.607526] ? usleep_range_state+0x90/0x90 [ 245.614743] wait_for_completion+0x24/0x30 [ 245.621903] flush_workqueue+0x133/0x3e0 [ 245.628887] ib_cache_cleanup_one+0x21/0xf0 [ib_core] [ 245.637083] __ib_unregister_device+0x79/0xc0 [ib_core] [ 245.645398] ib_unregister_device+0x27/0x40 [ib_core] [ 245.653541] irdma_ib_unregister_device+0x4b/0x70 [irdma] [ 245.662105] irdma_remove+0x1f/0x70 [irdma] [ 245.669446] auxiliary_bus_remove+0x1d/0x40 [ 245.676688] __device_release_driver+0x1a8/0x2a0 [ 245.684241] device_release_driver+0x29/0x40 [ 245.691416] bus_remove_device+0xde/0x150 [ 245.698396] device_del+0x19c/0x400 [**712178] ice_lag_link.isra.0+0xdd/0xf0 [ice] m] (3 of 5) A start job is runni[ 245.720683] ice_lag_changeupper_event+0xe1/0x130 [ice] ng for\u2026rk interfaces (3min 47s[ 245.729739] ice_lag_event_handler+0x5b/0x150 [ice] / 5min 3s) [ 245.738525] raw_notifier_call_chain+0x46/0x60 [ 245.746006] call_netdevice_notifiers_info+0x52/0xa0 [ 245.754123] __netdev_upper_dev_link+0x1b7/0x310 [ 245.761658] netdev_master_upper_dev_link+0x3e/0x60 [ 245.769627] bond_enslave+0xc3a/0x1720 [bonding] [ 245.777398] ? sscanf+0x4e/0x70 [ 245.783375] bond_option_slaves_set+0xca/0x170 [bonding] [ 245.791738] __bond_opt_set+0xbd/0x1a0 [bonding] [ 245.799505] __bond_opt_set_notify+0x30/0xb0 [bonding] [ 245.807860] bond_opt_tryset_rtnl+0x56/0xa0 [bonding] [ 245.816062] bonding_sysfs_store_option+0x52/0xa0 [bonding] [ 245.824750] dev_attr_store+0x14/0x30 [ 245.831443] sysfs_kf_write+0x3b/0x50 [ 245.837979] kernfs_fop_write_iter+0x138/0x1c0 [ 245.845469] new_sync_write+0x111/0x1a0 [ 245.852210] vfs_write+0x1d5/0x270 [ 245.858429] ksys_write+0x67/0xf0 [ 245.864624] __x64_sys_write+0x19/0x20 [ 245.871288] do_syscall_64+0x59/0xc0 [ 245.877715] ? handle_mm_fault+0xd8/0x2c0 [ 245.884566] ? do_user_addr_fault+0x1e7/0x670 [ 245.891990] ? filp_close+0x60/0x70 [ 245.898452] ? exit_to_user_mode_prepare+0x37/0xb0 [ 245.906272] ? irqentry_exit_to_user_mode+0x9/0x20 [ 245.914042] ? irqentry_exit+0x1d/0x30 [ 245.920703] ? exc_page_fault+0x89/0x170 [ 245.927555] entry_SYSCALL_64_after_hwframe+0x61/0xcb [ 245.935763] RIP: 0033:0x7f1e86855a37 [ 245.942153] RSP: 002b:7fff8da477a8 EFLAGS: 0246 ORIG_RAX: 0001 [ 245.953034] RAX: ffda RBX: 000a RCX: 7f1e86855a37 [ 245.963554] RDX: 000a RSI: 556ef
[Kernel-packages] [Bug 2015651] Re: 6.2.0-19 won't boot (partition UUID not found), 6.2.0-18 runs fine
also happening in 6.2.0-20 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2015651 Title: 6.2.0-19 won't boot (partition UUID not found), 6.2.0-18 runs fine Status in linux package in Ubuntu: Confirmed Bug description: 6.2.0-19 won't boot (grub error says partition UUID not found), but 6.2.0-18 runs fine with the same config ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: linux-image-6.2.0-19-generic 6.2.0-19.19 ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6 Uname: Linux 6.2.0-18-generic x86_64 ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ramses 2692 F wireplumber /dev/snd/seq:ramses 2690 F pipewire CasperMD5CheckResult: unknown CurrentDmesg: Error: command ['pkexec', 'dmesg'] failed with exit code 127: Error executing command as another user: Not authorized This incident has been reported. Date: Sat Apr 8 22:20:01 2023 InstallationDate: Installed on 2017-06-21 (2116 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0cf3:e300 Qualcomm Atheros Communications QCA61x4 Bluetooth 4.0 Bus 001 Device 004: ID 0c45:6713 Microdia Integrated_Webcam_HD Bus 001 Device 002: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 15 9560 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-18-generic root=UUID=18bdf6ee-e85b-4eb2-8fd1-68cf15fe1167 ro quiet nouveau.noaccel=1 splash acpi_rev_override=5 pci=noaer security=selinux selinux=0 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.2.0-18-generic N/A linux-backports-modules-6.2.0-18-generic N/A linux-firmware20230323.gitbcdcfbcf-0ubuntu1 SourcePackage: linux UpgradeStatus: Upgraded to lunar on 2023-04-02 (5 days ago) dmi.bios.date: 11/17/2019 dmi.bios.release: 1.18 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.18.0 dmi.board.name: 05FFDN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.18.0:bd11/17/2019:br1.18:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr:sku07BE: dmi.product.family: XPS dmi.product.name: XPS 15 9560 dmi.product.sku: 07BE dmi.sys.vendor: Dell Inc. --- ProblemType: Bug ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ramses 2692 F wireplumber /dev/snd/seq:ramses 2690 F pipewire CasperMD5CheckResult: unknown DistroRelease: Ubuntu 23.04 InstallationDate: Installed on 2017-06-21 (2116 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0cf3:e300 Qualcomm Atheros Communications QCA61x4 Bluetooth 4.0 Bus 001 Device 004: ID 0c45:6713 Microdia Integrated_Webcam_HD Bus 001 Device 002: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 15 9560 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-18-generic root=UUID=18bdf6ee-e85b-4eb2-8fd1-68cf15fe1167 ro quiet nouveau.noaccel=1 splash acpi_rev_override=5 pci=noaer security=selinux selinux=0 ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.2.0-18-generic N/A linux-backports-modules-6.2.0-18-generic N/A linux-firmware20230323.gitbcdcfbcf-0ubuntu1 Tags: lunar Uname: Linux 6.2.0-18-generic x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: Upgraded to lunar on 2023-04-02 (5 days ago) UserGroups: adm cdrom dip docker lpadmin microk8s plugdev sambashare sudo _MarkForUpload: False dmi.bios.date: 11/17/2019 dmi.bios.release: 1.18 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.18.0 dmi.board.name: 05FFDN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.18.0:bd11/17/2019:br1.18:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr:sku07BE: dmi.produc
[Kernel-packages] [Bug 2015651] Re: 6.2.0-19 won't boot (partition UUID not found), 6.2.0-18 runs fine
Same issue on Lenovo Legion 5 15ARH05. Happening on 6.2.0-20 and 6.2.0-19. On 6.2.0-18 - it's booting correctly. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2015651 Title: 6.2.0-19 won't boot (partition UUID not found), 6.2.0-18 runs fine Status in linux package in Ubuntu: Confirmed Bug description: 6.2.0-19 won't boot (grub error says partition UUID not found), but 6.2.0-18 runs fine with the same config ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: linux-image-6.2.0-19-generic 6.2.0-19.19 ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6 Uname: Linux 6.2.0-18-generic x86_64 ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ramses 2692 F wireplumber /dev/snd/seq:ramses 2690 F pipewire CasperMD5CheckResult: unknown CurrentDmesg: Error: command ['pkexec', 'dmesg'] failed with exit code 127: Error executing command as another user: Not authorized This incident has been reported. Date: Sat Apr 8 22:20:01 2023 InstallationDate: Installed on 2017-06-21 (2116 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0cf3:e300 Qualcomm Atheros Communications QCA61x4 Bluetooth 4.0 Bus 001 Device 004: ID 0c45:6713 Microdia Integrated_Webcam_HD Bus 001 Device 002: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 15 9560 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-18-generic root=UUID=18bdf6ee-e85b-4eb2-8fd1-68cf15fe1167 ro quiet nouveau.noaccel=1 splash acpi_rev_override=5 pci=noaer security=selinux selinux=0 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.2.0-18-generic N/A linux-backports-modules-6.2.0-18-generic N/A linux-firmware20230323.gitbcdcfbcf-0ubuntu1 SourcePackage: linux UpgradeStatus: Upgraded to lunar on 2023-04-02 (5 days ago) dmi.bios.date: 11/17/2019 dmi.bios.release: 1.18 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.18.0 dmi.board.name: 05FFDN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.18.0:bd11/17/2019:br1.18:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr:sku07BE: dmi.product.family: XPS dmi.product.name: XPS 15 9560 dmi.product.sku: 07BE dmi.sys.vendor: Dell Inc. --- ProblemType: Bug ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ramses 2692 F wireplumber /dev/snd/seq:ramses 2690 F pipewire CasperMD5CheckResult: unknown DistroRelease: Ubuntu 23.04 InstallationDate: Installed on 2017-06-21 (2116 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0cf3:e300 Qualcomm Atheros Communications QCA61x4 Bluetooth 4.0 Bus 001 Device 004: ID 0c45:6713 Microdia Integrated_Webcam_HD Bus 001 Device 002: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 15 9560 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-18-generic root=UUID=18bdf6ee-e85b-4eb2-8fd1-68cf15fe1167 ro quiet nouveau.noaccel=1 splash acpi_rev_override=5 pci=noaer security=selinux selinux=0 ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.2.0-18-generic N/A linux-backports-modules-6.2.0-18-generic N/A linux-firmware20230323.gitbcdcfbcf-0ubuntu1 Tags: lunar Uname: Linux 6.2.0-18-generic x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: Upgraded to lunar on 2023-04-02 (5 days ago) UserGroups: adm cdrom dip docker lpadmin microk8s plugdev sambashare sudo _MarkForUpload: False dmi.bios.date: 11/17/2019 dmi.bios.release: 1.18 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.18.0 dmi.board.name: 05FFDN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.18.0:bd11/17/2019:br1.18:svnDellInc.:
[Kernel-packages] [Bug 2008113] Re: Add firmware for amdgpu products with GC 11.01
** Changed in: hwe-next Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2008113 Title: Add firmware for amdgpu products with GC 11.01 Status in HWE Next: Fix Released Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Jammy: Fix Released Status in linux-firmware source package in Lunar: Fix Released Bug description: Firmware has been submitted upstream for a product that contains the IP blocks: DCN 3.1.4 GC 11.0.1 SDMA 6.0.1 PSP 13.0.4 VCN 4.0.2 Upstreamed commits: 5c11a374 amdgpu: Add VCN 4.0.2 firmware 5fe2d73c amdgpu: Add PSP 13.0.4 firmware a3332f8b amdgpu: Add SDMA 6.0.1 fimware 4535de67 amdgpu: Add GC 11.0.1 firmware 2e93e4c9 amdgpu: Add DCN 3.1.4 firmware c0a0bc23 amdgpu: Update GC 11.0.1 firmware To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2008113/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2002089] Re: Mediatek FM350-GL wwan module failed to init: Invalid device status 0x1
** Changed in: hwe-next
Status: New => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.0 in Ubuntu.
https://bugs.launchpad.net/bugs/2002089
Title:
Mediatek FM350-GL wwan module failed to init: Invalid device status
0x1
Status in HWE Next:
Fix Released
Status in linux package in Ubuntu:
Fix Released
Status in linux-oem-6.0 package in Ubuntu:
Invalid
Status in linux-oem-6.1 package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Invalid
Status in linux-oem-6.0 source package in Jammy:
Fix Released
Status in linux-oem-6.1 source package in Jammy:
Fix Released
Status in linux source package in Kinetic:
Won't Fix
Status in linux-oem-6.0 source package in Kinetic:
Invalid
Status in linux-oem-6.1 source package in Kinetic:
Invalid
Status in linux source package in Lunar:
Fix Released
Status in linux-oem-6.0 source package in Lunar:
Invalid
Status in linux-oem-6.1 source package in Lunar:
Invalid
Bug description:
[SRU Justification]
[Impact]
Mediatek FM350-GL wwan module failed to init: Invalid device status
0x1:
[ 1.623253] mtk_t7xx :71:00.0: enabling device ( -> 0002)
[ 3.632963] mtk_t7xx :71:00.0: Invalid device status 0x1
[Fix]
The t7xx driver once received following fixes to complete its functions in
v6.1-rc1:
d20ef656f994 net: wwan: t7xx: Add AP CLDMA
007f26f0d68e net: wwan: t7xx: Infrastructure for early port configuration
140424d90165 net: wwan: t7xx: PCIe reset rescan
87dae9e70bf7 net: wwan: t7xx: Enable devlink based fw flashing and coredump
collection
b0bc1709b768 net: wwan: t7xx: Devlink documentation
However it was soon reverted for a second revision. Before that, in bug
1990700
we need the first (reverted) patch "net: wwan: t7xx: Add AP CLDMA" to fix
device
suspend in a minimum level for development. Then, in this bug 2002089, a fully
revised resubmission is now available.
An additional patch from v6.1, commit bb67012331f7 ("net: devlink:
extend info_get() version put to indicate a flash component"), is
necessary for oem-6.0 backport.
[Test Case]
Modprobe on new platforms that suffers this invalid device status issue,
and run suspend/resume tests to ensure bug 1990700 is still in a good
state.
[Where problems could occur]
This re-introduce the device firmware update support via devlink, so far
it has been tested many times from 3rd party/vendor, but might still
bump into platform compatibility issue as we have here.
[Other Info]
While this is only planned for oem-6.0/oem-6.1 and on, only U/L/OEM-6.x
are nominated for fix.
== original bug report ==
[ 1.623253] mtk_t7xx :71:00.0: enabling device ( -> 0002)
[ 3.632963] mtk_t7xx :71:00.0: Invalid device status 0x1
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: u 1216 F pulseaudio
CRDA: N/A
CasperMD5CheckResult: pass
DistributionChannelDescriptor:
# This is the distribution channel descriptor for the OEM CDs
# For more information see
http://wiki.ubuntu.com/DistributionChannelDescriptor
canonical-oem-somerville-jammy-amd64-20220504-33+jellyfish-arcanine-14+X58
DistroRelease: Ubuntu 22.04
InstallationDate: Installed on 2023-01-05 (5 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" -
somerville-jammy-amd64-20220504-33
IwConfig:
lono wireless extensions.
enp0s31f6 no wireless extensions.
wwan0 no wireless extensions.
MachineType: Dell Inc. Precision 3480
Package: linux (not installed)
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.0.0-1010-oem
root=UUID=0b4b52c5-ca19-4e54-a610-17e965212e64 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 6.0.0-1010.10-oem 6.0.9
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-6.0.0-1010-oem N/A
linux-backports-modules-6.0.0-1010-oem N/A
linux-firmware 20220329.git681281e4-0ubuntu3.7
Tags: jammy
Uname: Linux 6.0.0-1010-oem x86_64
UnreportableReason: This report is about a package that is not installed.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: N/A
_MarkForUpload: False
dmi.bios.date: 12/22/2022
dmi.bios.release: 0.6
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 0.6.55
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.ec.firmware.release: 0.0
dmi.modalias:
dmi:bvnDellInc.:bvr0.6.55:bd12/22/2022:br0.6:efr0.0:svnDellInc.:pnPrecision3480:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:sku0C02:
dmi.product.family: Latitude
dmi.product.name: Precisi
[Kernel-packages] [Bug 1997944] Re: Soundwire support for the Intel RPL Gen platforms
** Changed in: hwe-next
Status: New => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1997944
Title:
Soundwire support for the Intel RPL Gen platforms
Status in HWE Next:
Fix Released
Status in firmware-sof package in Ubuntu:
Fix Released
Status in linux package in Ubuntu:
Fix Released
Status in linux-oem-6.0 package in Ubuntu:
Invalid
Status in firmware-sof source package in Jammy:
Fix Released
Status in linux source package in Jammy:
Won't Fix
Status in linux-oem-6.0 source package in Jammy:
Fix Released
Status in firmware-sof source package in Lunar:
Fix Released
Status in linux source package in Lunar:
Fix Released
Status in linux-oem-6.0 source package in Lunar:
Invalid
Bug description:
[SRU Justfication]
[Impact]
Need soundwire support for the Intel RPL Gen platforms, specifically
0C10/0C4F/0C11. 0C40 added due to dependency.
[Fix]
Fixes from linux-next for v6.2, as well as those for firmware-sof and
alsa-ucm-conf.
[Test Case]
All the fixes are currently packaged in experimental kernel/firmware
PPAs. Install the latest ones and check audio functions.
[Where problems could occur]
Most of the patches add model information only, and they'd only take
effect on platforms with the corresponding hardware pieces.
[Other Info]
Nominated for Unstable/Lunar and OEM-6.0.
== original bug report ==
Include the support for Soundwire of RPL Gen platforms
Related components/fixes:
* kernel:
* b07908ab26ce ALSA: hda: intel-dsp-config: Add RaptorLake PCI IDs
* d608bc44181c ASoC: Intel: sof_sdw: Add support for SKU 0C10 product
* 55fc03445e2c ASoC: Intel: soc-acpi: add SKU 0C10 SoundWire configuration
* 880bf4b47fc1 ASoC: Intel: sof_sdw: Add support for SKU 0C40 product
* 97b5fbf44c00 ASoC: Intel: soc-acpi: add SKU 0C40 SoundWire configuration
* a9248c868c39 ASoC: Intel: sof_sdw: Add support for SKU 0C4F product
* 6ad73a2b42ea ASoC: rt1318: Add RT1318 SDCA vendor-specific driver
* 8c4b3a8ea2c0 ASoC: intel: sof_sdw: add rt1318 codec support.
* d84e10da17e7 ASoC: Intel: sof_sdw: Add support for SKU 0C11 product
* 0050e3d3d43d ASoC: Intel: soc-acpi: add SKU 0C11 SoundWire configuration
* SOF Audio firmware and topology support for Intel RPL Mobiles
* https://github.com/thesofproject/sof/releases/tag/v2.2.3
* https://github.com/thesofproject/sof-bin/pull/108
* https://github.com/alsa-project/alsa-ucm-conf
* c82c400fb653 ucm2: sof-soundwire: add basic settings for RT1318 SDCA
device
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: ubuntu 1337 F pulseaudio
/dev/snd/pcmC0D4c: ubuntu 1337 F...m pulseaudio
/dev/snd/pcmC0D2p: ubuntu 1337 F...m pulseaudio
CasperMD5json:
{
"result": "skip"
}
DistributionChannelDescriptor:
# This is the distribution channel descriptor for the OEM CDs
# For more information see
http://wiki.ubuntu.com/DistributionChannelDescriptor
canonical-oem-somerville-jammy-amd64-20220504-33+jellyfish-torchic+X72
DistroRelease: Ubuntu 22.04
InstallationDate: Installed on 2022-11-25 (25 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" -
somerville-jammy-amd64-20220504-33
MachineType: Dell Inc. Precision 5480
NonfreeKernelModules: nvidia_modeset nvidia
Package: linux (not installed)
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.0.0-9009-oem
root=UUID=58df5e81-0c25-471c-ace5-4decd3bcf449 ro automatic-oem-config quiet
splash
ProcVersionSignature: Ubuntu 6.0.0-9009.9+exp.25-oem 6.0.10
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-6.0.0-9009-oem N/A
linux-backports-modules-6.0.0-9009-oem N/A
linux-firmware 20220329.git681281e4-0ubuntu3.7
Tags: jammy apport-hook-error
Uname: Linux 6.0.0-9009-oem x86_64
UnreportableReason: This report is about a package that is not installed.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: N/A
_MarkForUpload: False
dmi.bios.date: 11/01/2022
dmi.bios.release: 88.3
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 88.3.29
dmi.board.vendor: Dell Inc.
dmi.chassis.asset.tag: RUNNING
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.ec.firmware.release: 153.0
dmi.modalias:
dmi:bvnDellInc.:bvr88.3.29:bd11/01/2022:br88.3:efr153.0:svnDellInc.:pnPrecision5480:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:sku0C40:
dmi.product.family: Precision
dmi.product.name: Precision 5480
dmi.product.sku: 0C40
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug
[Kernel-packages] [Bug 2013236] Re: Failed to install bcmwl wireless driver during the install
With the broadcom-sta-dkms package installed, can you blacklist bcma, reboot, and see if wireless shows up? -- 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/2013236 Title: Failed to install bcmwl wireless driver during the install Status in linux-firmware package in Ubuntu: Invalid Status in ubuntu-drivers-common package in Ubuntu: Confirmed Bug description: Specifically for Lunar - using a Macbook Air 2012, its wireless driver was not enabled even though I ticked the wireless tickbox on the installer. A quick look at the installer logs reveals various issues syslog:2023-03-29T18:01:25.141599+00:00 ubuntu-budgie kernel: [ 43.063747] b43 bcma0:1: Direct firmware load for b43/ucode29_mimo.fw failed with error -2 syslog:2023-03-29T18:01:25.141625+00:00 ubuntu-budgie kernel: [ 43.063802] b43 bcma0:1: Direct firmware load for b43/ucode29_mimo.fw failed with error -2 syslog:2023-03-29T18:01:25.141626+00:00 ubuntu-budgie kernel: [ 43.063862] b43 bcma0:1: Direct firmware load for b43-open/ucode29_mimo.fw failed with error -2 syslog:2023-03-29T18:01:25.141626+00:00 ubuntu-budgie kernel: [ 43.063908] b43 bcma0:1: Direct firmware load for b43-open/ucode29_mimo.fw failed with error -2 I will attach the installer logs manually since this was captured after the installation Note - on 20.04.6, 22.04.2 and 22.10 with the same laptop bcmwl was installed correctly during the install so this is a regression with the 6.2 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2013236/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2015455] Re: Intel PET not available on recent kernel causing QEMU VM crashes
** Changed in: linux (Ubuntu) Status: Incomplete => New ** 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/2015455 Title: Intel PET not available on recent kernel causing QEMU VM crashes Status in linux package in Ubuntu: Confirmed Bug description: Hi Following a recent kernel update on Ubuntu Server 22.04.2 x86_64 to 5.19.0-35 (& ..0-38), QEMU (via LXD) Windows Server 2022 VMs are crashing every day. The CPU has Intel PET feature, but I've had to disable tdp_mmu using modprobe so stabilise the VMs. The platform: - Linux 5.19.0-38-generic #39~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Fri Mar 17 21:16:15 UTC 2 x86_64 x86_64 x86_64 GNU/Linux The CPU tech specs on Dell R620: https://www.intel.com/content/www/us/en/products/sku/75277/intel-xeon-processor-e52680-v2-25m-cache-2-80-ghz/specifications.html The work-around (success with modprobe): https://pve.proxmox.com/wiki/Upgrade_from_6.x_to_7.0#KVM:_entry_failed.2C_hardware_error_0x8021 LXD Issue: -- https://github.com/lxc/lxd/issues/11520 The QEMU log: - someadmin@us2204-iph-lxd03:/home/someadmin# cat /var/snap/lxd/common/lxd/logs/mw2022-ivm-test01/qemu.log.old qemu-system-x86_64: Issue while setting TUNSETSTEERINGEBPF: Invalid argument with fd: 48, prog_fd: -1 KVM: entry failed, hardware error 0x8021 If you're running a guest on an Intel machine without unrestricted mode support, the failure can be most likely due to the guest entering an invalid state for Intel VT. For example, the guest maybe running in big real mode which is not supported on less recent Intel processors. EAX=0008 EBX=00040ee0 ECX=83ac EDX= ESI=32e2f000 EDI=32e26040 EBP=813d2810 ESP=813d2790 EIP=8000 EFL=0002 [---] CPL=0 II=0 A20=1 SMM=1 HLT=0 ES = 00809300 CS =8000 7ff8 00809300 SS = 00809300 DS = 00809300 FS = 00809300 GS = 00809300 LDT= TR =0040 ff2a 0067 8b00 GDT= ff2a1fb0 0057 IDT= CR0=00050032 CR2=7c3fa0b0 CR3=001ae002 CR4= DR0= DR1= DR2= DR3= DR6=0ff0 DR7=0400 EFER= Code=qemu-system-x86_64: ../hw/core/cpu-sysemu.c:77: cpu_asidx_from_attrs: Assertion `ret < cpu->num_ases && ret >= 0' failed. The CPU via lscpu: -- Architecture:x86_64 CPU op-mode(s):32-bit, 64-bit Address sizes: 46 bits physical, 48 bits virtual Byte Order:Little Endian CPU(s): 40 On-line CPU(s) list: 0-39 Vendor ID: GenuineIntel Model name:Intel(R) Xeon(R) CPU E5-2680 v2 @ 2.80GHz CPU family: 6 Model: 62 Thread(s) per core: 2 Core(s) per socket: 10 Socket(s): 2 Stepping:4 CPU max MHz: 3600. CPU min MHz: 1200. BogoMIPS:5599.96 Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm pcid dca sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm cpuid_fault pti ssbd ibrs ibpb stibp tpr_shad ow vnmi flexpriority ept vpid fsgsbase smep erms xsaveopt dtherm ida arat pln pts md_clear flush_l1d Virtualization features: Virtualization:VT-x Caches (sum of all): L1d: 640 KiB (20 instances) L1i: 640 KiB (20 instances) L2:5 MiB (20 instances) L3:50 MiB (2 instances) NUMA: NUMA node(s): 2 NUMA node0 CPU(s): 0,2,4,6,8,10,12,14,16,18,20,22,24,26,28,30,32,34,36,38 NUMA node1 CPU(s): 1,3,5,7,9,11,13,15,17,19,21,23,25,27,29,31,33,35,37,39 Vulnerabilities: Itlb multihit: KVM: Mitigation: Split huge pages L1tf: Mitigation; PTE Inversion; VMX conditional cache flushes, SMT vulnerable Mds: Mitigation; Clear CPU buffers; SMT vulnerable Meltdown: Mitigation; PTI Mmio stale data: Unknown: No mitigations Retbleed: Not affected Spec store bypass: Mitigation; Speculative Store Bypass disabled via prctl Spectre v1
[Kernel-packages] [Bug 2015994] [NEW] 23.04 installer display broken with fbdev on ppc64el
Public bug reported: Hi, latest cloud image ( Daily Build [20230405] : https://cloud-images.ubuntu.com/lunar/current/lunar-server-cloudimg-ppc64el.img ) , especially kernel 6.2.0-19-generic used, has the same issue as the one I encountered on Debian : https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033058 . qemu vga output with fbdev gets stuck at kernel boot time while serial console looks ok till login prompt . I guess it's going to propagate to http://cdimage.ubuntu.com/ubuntu- server/daily-live/current/lunar-live-server-ppc64el.iso soon. I open this bug to monitor the upstream fix Cyril Brulebois proposed and hopefully get it into Ubuntu asap. Thanks, F. ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Attachment added: "vga output" https://bugs.launchpad.net/bugs/2015994/+attachment/5663234/+files/23.04_20230405_qemu_ppc64el.png -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2015994 Title: 23.04 installer display broken with fbdev on ppc64el Status in linux package in Ubuntu: Incomplete Bug description: Hi, latest cloud image ( Daily Build [20230405] : https://cloud-images.ubuntu.com/lunar/current/lunar-server-cloudimg-ppc64el.img ) , especially kernel 6.2.0-19-generic used, has the same issue as the one I encountered on Debian : https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033058 . qemu vga output with fbdev gets stuck at kernel boot time while serial console looks ok till login prompt . I guess it's going to propagate to http://cdimage.ubuntu.com/ubuntu- server/daily-live/current/lunar-live-server-ppc64el.iso soon. I open this bug to monitor the upstream fix Cyril Brulebois proposed and hopefully get it into Ubuntu asap. Thanks, F. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2015994/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2015994] Re: 23.04 installer display broken with fbdev on ppc64el
Functional serial output (sorry for the OpenQA artifacts) ** Attachment added: "Serial output" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2015994/+attachment/5663235/+files/23.04_20230405_qemu_serial_ppc64el.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/2015994 Title: 23.04 installer display broken with fbdev on ppc64el Status in linux package in Ubuntu: Incomplete Bug description: Hi, latest cloud image ( Daily Build [20230405] : https://cloud-images.ubuntu.com/lunar/current/lunar-server-cloudimg-ppc64el.img ) , especially kernel 6.2.0-19-generic used, has the same issue as the one I encountered on Debian : https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033058 . qemu vga output with fbdev gets stuck at kernel boot time while serial console looks ok till login prompt . I guess it's going to propagate to http://cdimage.ubuntu.com/ubuntu- server/daily-live/current/lunar-live-server-ppc64el.iso soon. I open this bug to monitor the upstream fix Cyril Brulebois proposed and hopefully get it into Ubuntu asap. Thanks, F. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2015994/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2015994] 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 2015994 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2015994 Title: 23.04 installer display broken with fbdev on ppc64el Status in linux package in Ubuntu: Incomplete Bug description: Hi, latest cloud image ( Daily Build [20230405] : https://cloud-images.ubuntu.com/lunar/current/lunar-server-cloudimg-ppc64el.img ) , especially kernel 6.2.0-19-generic used, has the same issue as the one I encountered on Debian : https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033058 . qemu vga output with fbdev gets stuck at kernel boot time while serial console looks ok till login prompt . I guess it's going to propagate to http://cdimage.ubuntu.com/ubuntu- server/daily-live/current/lunar-live-server-ppc64el.iso soon. I open this bug to monitor the upstream fix Cyril Brulebois proposed and hopefully get it into Ubuntu asap. Thanks, F. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2015994/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1931325] Re: cfs_bandwidth01 in sched from ubuntu_ltp_stable failed on B-4.15
** Changed in: linux (Ubuntu Bionic) Assignee: Po-Hsu Lin (cypressyew) => (unassigned) ** Changed in: ubuntu-kernel-tests Assignee: Po-Hsu Lin (cypressyew) => (unassigned) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1931325 Title: cfs_bandwidth01 in sched from ubuntu_ltp_stable failed on B-4.15 Status in ubuntu-kernel-tests: Confirmed Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Confirmed Bug description: [Impact] Test case cfs_bandwidth01 in LTP sched test suite is a reproducer of a CFS unthrottle_cfs_rq() issue (fe61468b2cbc2b sched/fair: Fix enqueue_task_fair warning). This test triggers a warning on our 4.15 kernel: LTP: starting cfs_bandwidth01 (cfs_bandwidth01 -i 5) [ cut here ] rq->tmp_alone_branch != &rq->leaf_cfs_rq_list WARNING: CPU: 0 PID: 0 at /build/linux-fYK9kF/linux-4.15.0/kernel/sched/fair.c:393 unthrottle_cfs_rq+0x16f/0x200 Modules linked in: input_leds joydev serio_raw mac_hid qemu_fw_cfg kvm_intel kvm irqbypass sch_fq_codel binfmt_misc ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi nfsd auth_rpcgss nfs_acl lockd grace sunrpc ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear cirrus ttm drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops drm psmouse virtio_blk pata_acpi floppy virtio_net i2c_piix4 CPU: 0 PID: 0 Comm: swapper/0 Not tainted 4.15.0-144-generic #148-Ubuntu Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.10.2-1ubuntu1 04/01/2014 RIP: 0010:unthrottle_cfs_rq+0x16f/0x200 RSP: 0018:989ebfc03e80 EFLAGS: 00010082 RAX: RBX: 989eb4c6ac00 RCX: RDX: 0005 RSI: acb63c4d RDI: 0046 RBP: 989ebfc03ea8 R08: 00af39e61b33 R09: acb63c20 R10: R11: 0001 R12: 989eb57fe400 R13: 989ebfc21900 R14: 0001 R15: 0001 FS: () GS:989ebfc0() knlGS: CS: 0010 DS: ES: CR0: 80050033 CR2: 55593258d618 CR3: 7a044000 CR4: 06f0 DR0: DR1: DR2: DR3: DR6: fffe0ff0 DR7: 0400 Call Trace: distribute_cfs_runtime+0xc3/0x110 sched_cfs_period_timer+0xff/0x220 ? sched_cfs_slack_timer+0xd0/0xd0 __hrtimer_run_queues+0xdf/0x230 hrtimer_interrupt+0xa0/0x1d0 smp_apic_timer_interrupt+0x6f/0x140 apic_timer_interrupt+0x90/0xa0 RIP: 0010:native_safe_halt+0x12/0x20 RSP: 0018:ac603e28 EFLAGS: 0246 ORIG_RAX: ff11 RAX: abbc9280 RBX: RCX: RDX: RSI: RDI: RBP: ac603e28 R08: 00af39850067 R09: 989e73749d00 R10: R11: 7fff R12: R13: R14: R15: ? __sched_text_end+0x1/0x1 default_idle+0x20/0x100 arch_cpu_idle+0x15/0x20 default_idle_call+0x23/0x30 do_idle+0x172/0x1f0 cpu_startup_entry+0x73/0x80 rest_init+0xae/0xb0 start_kernel+0x4dc/0x500 x86_64_start_reservations+0x24/0x26 x86_64_start_kernel+0x74/0x77 secondary_startup_64+0xa5/0xb0 Code: 50 09 00 00 49 39 85 60 09 00 00 74 68 80 3d 3a 6e 54 01 00 75 5f 31 db 48 c7 c7 c0 3d 2d ac c6 05 28 6e 54 01 01 e8 11 36 fc ff <0f> 0b 48 85 db 74 43 49 8b 85 78 09 00 00 49 39 85 70 09 00 00 ---[ end trace b6b9a70bc2945c0c ]--- [Fix] Base on the test case description, we will need these fixes: * fe61468b2cbc2b sched/fair: Fix enqueue_task_fair warning * b34cb07dde7c23 sched/fair: Fix enqueue_task_fair() warning some more * 39f23ce07b9355 sched/fair: Fix unthrottle_cfs_rq() for leaf_cfs_rq list * 6d4d22468dae3d sched/fair: Reorder enqueue/dequeue_task_fair path * 5ab297bab98431 sched/fair: Fix reordering of enqueue/dequeue_task_fair() Backport needed for Bionic since we're missing some new variables / coding style changes introduced in the following commits (and their corresponding fixes): * 97fb7a0a8944bd sched: Clean up and harmonize the coding style of the scheduler code base * 9f68395333ad7f sched/pelt: Add a new runnable average signal * 6212437f0f6043 sched/fair: Fix runnable_avg for throttled cfs * 43e9f7f231e40e sched/fair: Start tracking SCHED_IDLE tasks count in cfs_rq I have also searched in the upstream tree to see if there is any other commit claim to be a fix of these but didn't see any. [Test] Test kernel can be found here: https://people.ca
[Kernel-packages] [Bug 1973434] Re: massive performance issues since 22.04 upgrade
I conquer with chris (platoscave). Pretty all my problems went a away with time by magic. It is obvious that many bugs plagued us and where fixed by the different projects composing Ubuntu as time passed by. 22.04 just wasn't ready went it came out. My only issue that remains is when waking up my laptop from S3, everything is (almost) frozen for at least 5 seconds; seams that the CPU hits 100% (no confirmation) for some reason. But that should be another bug report. I am running under Wayland now, btw. System: Dell Latitude E7470 (2016), Intel(R) Core(TM) i5-6200U CPU @ 2.30GHz, Skylake GT2 [HD Graphics 520], 32 GiB Ram, 1 TiB SSD, 1900x1080 screen. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1973434 Title: massive performance issues since 22.04 upgrade Status in linux package in Ubuntu: Confirmed Bug description: Hi, After upgrading to 22.04 i had to fight with massive performance issues. Browsers appeared to hang every other minute, youtube videos being laggy and hang in between, applications in a virtualbox VM where slow and also hanging every other minute to a level of not being useable. On a pretty recent and powerful system just 2 years old. I noticed CPU jumps in top, but also somehow thought it could be a graphics issue so invested some time installing nvidia drivers properly. Also I wondered if it might be the lowlatency kernel I normally use because I do audio stuff, and switched to generic. But nothing helped. ThenI had the idea it could be a kernel/scheduler issue because the system wasn't always slow, but it appeared certain things kept hanging when other processed had a lot of cpu for a few seconds. So I got a recent mainline kernel, configured it with my last running config from 21.10 before the update, made the debs and installed them, and now can tell that a mainline kernel 5.17.7 with all the dkms modules that i had before which got compiled automatically at installation brings back a "normal" performance. I can browse the web, run multiple youtube vids at once, even in another browser, have thunderbird running, and a virtualbox machine open with another browser for some web app testing and everything runs fine and smooth, no lagging. Not sure yet what the real reason is - either the kernel version, or a patch in the ubuntu version, or the 22.04 kernel config so far, or some configuration made in 21.10 that isn't good with 22.04 and it's kernel anymore. I will go ahead tomorrow and see if I can build a vanilla kernel with the config from the ubuntu 22.04 kernel and "make oldconfig", then I will be able to tell if only the config is making the difference. Please let me know of there is anything I should test to further analyze this issue, or any ideas I can try to solve it without having to run a mainline manually installed kernel. Thanks. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-generic 5.15.0.30.33 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 Uname: Linux 5.15.0-30-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: henning6198 F pulseaudio /dev/snd/controlC1: henning6198 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat May 14 23:02:38 2022 InstallationDate: Installed on 2020-04-12 (761 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 20QV00CEGE ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-30-generic root=/dev/mapper/vgubuntu-root ro RelatedPackageVersions: linux-restricted-modules-5.15.0-30-generic N/A linux-backports-modules-5.15.0-30-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-04-28 (15 days ago) dmi.bios.date: 12/06/2021 dmi.bios.release: 1.42 dmi.bios.vendor: LENOVO dmi.bios.version: N2OET55W (1.42 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QV00CEGE dmi.board.vendor: LENOVO dmi.board.version: SDK0T08861 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.23 dmi.modalias: dmi:bvnLENOVO:bvrN2OET55W(1.42):bd12/06/2021:br1.42:efr1.23:svnLENOVO:pn20QV00CEGE:pvrThinkPadX1Extreme2nd:rvnLENOVO:rn20QV00CEGE:rvrSDK0T08861WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20QV_BU_Think_FM_ThinkPadX1Extreme2nd: dmi.product.family: ThinkPad X1 Extreme 2nd dmi.product.name: 20QV00CEGE dmi.product.sku: LENOVO_MT_20QV_BU_Think_FM_ThinkPad X1 Extreme 2nd dmi.product.version: ThinkPad X1 Extreme 2nd dmi.sys.vendor: LENOVO
[Kernel-packages] [Bug 2015827] Re: NFS performance issue while clearing the file access cache upon login
Du ChengEn, I would second Jan's opinion. This whole chain of fixes that has gone in to fix LP: #2003053, should be rolled back. There where no heavy arguments to cherry-pick those changes in the first place. (It is not in upstream LTS either). Once it was discovered what kind of impact it had, it should have been rolled back. As it is also now clear that LP: #2003053 cannot be solved without impacting other use-cases, and by only introducing an extra mount- option, this is just another argument for reverting this set of patches. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2015827 Title: NFS performance issue while clearing the file access cache upon login Status in linux package in Ubuntu: In Progress Bug description: The performance issue that has been observed may be attributed to an increase in NFS ACCESS operations, possibly due to a new mechanism introduced in the Linux 6.2-rc3 NFS client side. This mechanism clears the access cache as soon as the cache timestamp becomes older than the user's login time, with the primary objective of preventing the NFS client's access cache from becoming stale due to any changes made to the user's group membership on the server after the user has already logged in on the client. It's worth noting that POSIX only refreshes the user's supplementary group information upon login. Upstream has taken into consideration that users may reasonably expect the access cache to be cleared when they log out and log back in again, with all behavior returning to normal after the replacement. The performance overhead can be particularly noticeable when applications or users switch to other privileged users via commands such as "su" to operate on NFS-mounted folders. In such cases, the privileged user's login time will be renewed, and NFS ACCESS operations will need to be re-sent, potentially leading to performance degradation. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2015827/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2016005] [NEW] qxl should be in linux-modules, and not just linux-modules-extra
Public bug reported: The qxl kernel module is present in linux-modules-extra, which is not installed by default using cloud images. The scenario that breaks is if you want to have an ubuntu desktop in a VM. Since we don't have a desktop image, you start by deploying the normal image, and then install the ubuntu-desktop metapackage. But without the qxl module, and given that our libvirt/qemu VM defaults to using qxl for its graphics device, the desktop will fail to come up. You just get a blinking cursor, no gdm. Perhaps there is another way to get this experience working out of the box, though. Perhaps something with dependencies and virtual provides, I'm unsure. Or there is another way to deploy an ubuntu desktop in a VM. I'm also unsure when this stopped working. Maybe qxl was in linux- modules before, or maybe we started defaulting to that graphics device at some later point in time, and qxl was never in linux-modules to begin with. $ dpkg -S /lib/modules/6.2.0-20-generic/kernel/drivers/gpu/drm/qxl/qxl.ko linux-modules-extra-6.2.0-20-generic: /lib/modules/6.2.0-20-generic/kernel/drivers/gpu/drm/qxl/qxl.ko ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Description changed: The qxl kernel module is present in linux-modules-extra, which is not installed by default using cloud images. The scenario that breaks is if you want to have an ubuntu desktop in a VM. Since we don't have a desktop image, you start by deploying the normal image, and then install the ubuntu-desktop metapackage. But without the qxl module, and given that our libvirt/qemu VM defaults to using qxl for its graphics device, the desktop will fail to come up. You just get a blinking cursor, no gdm. Perhaps there is another way to get this experience working out of the box, though. Perhaps something with dependencies and virtual provides, I'm unsure. Or there is another way to deploy an ubuntu desktop in a VM. I'm also unsure when this stopped working. Maybe qxl was in linux- modules before, or maybe we started defaulting to that graphics device at some later point in time, and qxl was never in linux-modules to begin with. + + + $ dpkg -S /lib/modules/6.2.0-20-generic/kernel/drivers/gpu/drm/qxl/qxl.ko + linux-modules-extra-6.2.0-20-generic: /lib/modules/6.2.0-20-generic/kernel/drivers/gpu/drm/qxl/qxl.ko -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2016005 Title: qxl should be in linux-modules, and not just linux-modules-extra Status in linux package in Ubuntu: Incomplete Bug description: The qxl kernel module is present in linux-modules-extra, which is not installed by default using cloud images. The scenario that breaks is if you want to have an ubuntu desktop in a VM. Since we don't have a desktop image, you start by deploying the normal image, and then install the ubuntu-desktop metapackage. But without the qxl module, and given that our libvirt/qemu VM defaults to using qxl for its graphics device, the desktop will fail to come up. You just get a blinking cursor, no gdm. Perhaps there is another way to get this experience working out of the box, though. Perhaps something with dependencies and virtual provides, I'm unsure. Or there is another way to deploy an ubuntu desktop in a VM. I'm also unsure when this stopped working. Maybe qxl was in linux- modules before, or maybe we started defaulting to that graphics device at some later point in time, and qxl was never in linux-modules to begin with. $ dpkg -S /lib/modules/6.2.0-20-generic/kernel/drivers/gpu/drm/qxl/qxl.ko linux-modules-extra-6.2.0-20-generic: /lib/modules/6.2.0-20-generic/kernel/drivers/gpu/drm/qxl/qxl.ko To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2016005/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2016005] 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 2016005 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2016005 Title: qxl should be in linux-modules, and not just linux-modules-extra Status in linux package in Ubuntu: Incomplete Bug description: The qxl kernel module is present in linux-modules-extra, which is not installed by default using cloud images. The scenario that breaks is if you want to have an ubuntu desktop in a VM. Since we don't have a desktop image, you start by deploying the normal image, and then install the ubuntu-desktop metapackage. But without the qxl module, and given that our libvirt/qemu VM defaults to using qxl for its graphics device, the desktop will fail to come up. You just get a blinking cursor, no gdm. Perhaps there is another way to get this experience working out of the box, though. Perhaps something with dependencies and virtual provides, I'm unsure. Or there is another way to deploy an ubuntu desktop in a VM. I'm also unsure when this stopped working. Maybe qxl was in linux- modules before, or maybe we started defaulting to that graphics device at some later point in time, and qxl was never in linux-modules to begin with. $ dpkg -S /lib/modules/6.2.0-20-generic/kernel/drivers/gpu/drm/qxl/qxl.ko linux-modules-extra-6.2.0-20-generic: /lib/modules/6.2.0-20-generic/kernel/drivers/gpu/drm/qxl/qxl.ko To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2016005/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2016005] Re: qxl should be in linux-modules, and not just linux-modules-extra
There is no need for logs for this issue, so setting the bug back to "confirmed". ** 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/2016005 Title: qxl should be in linux-modules, and not just linux-modules-extra Status in linux package in Ubuntu: Confirmed Bug description: The qxl kernel module is present in linux-modules-extra, which is not installed by default using cloud images. The scenario that breaks is if you want to have an ubuntu desktop in a VM. Since we don't have a desktop image, you start by deploying the normal image, and then install the ubuntu-desktop metapackage. But without the qxl module, and given that our libvirt/qemu VM defaults to using qxl for its graphics device, the desktop will fail to come up. You just get a blinking cursor, no gdm. Perhaps there is another way to get this experience working out of the box, though. Perhaps something with dependencies and virtual provides, I'm unsure. Or there is another way to deploy an ubuntu desktop in a VM. I'm also unsure when this stopped working. Maybe qxl was in linux- modules before, or maybe we started defaulting to that graphics device at some later point in time, and qxl was never in linux-modules to begin with. $ dpkg -S /lib/modules/6.2.0-20-generic/kernel/drivers/gpu/drm/qxl/qxl.ko linux-modules-extra-6.2.0-20-generic: /lib/modules/6.2.0-20-generic/kernel/drivers/gpu/drm/qxl/qxl.ko To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2016005/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2015994] Re: 23.04 installer display broken with fbdev on ppc64el
apport information ** Tags added: apport-collected cloud-image lunar ** Description changed: Hi, latest cloud image ( Daily Build [20230405] : https://cloud-images.ubuntu.com/lunar/current/lunar-server-cloudimg-ppc64el.img ) , especially kernel 6.2.0-19-generic used, has the same issue as the one I encountered on Debian : https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033058 . qemu vga output with fbdev gets stuck at kernel boot time while serial console looks ok till login prompt . I guess it's going to propagate to http://cdimage.ubuntu.com/ubuntu- server/daily-live/current/lunar-live-server-ppc64el.iso soon. I open this bug to monitor the upstream fix Cyril Brulebois proposed and hopefully get it into Ubuntu asap. Thanks, F. + --- + ProblemType: Bug + .var.log.platform: + + AlsaDevices: + total 0 + crw-rw 1 root audio 116, 1 Apr 12 12:49 seq + crw-rw 1 root audio 116, 33 Apr 12 12:49 timer + AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' + ApportVersion: 2.26.0-0ubuntu2 + Architecture: ppc64el + 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: + CRDA: N/A + CasperMD5CheckResult: unknown + CloudArchitecture: ppc64le + CloudBuildName: server + CloudID: nocloud + CloudName: unknown + CloudPlatform: nocloud + CloudSerial: 20230405 + CloudSubPlatform: config-disk (/dev/sr0) + DistroRelease: Ubuntu 23.04 + IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' + Lspci-vt: + -[:00]-+-00.0 Device 1234: + +-01.0 NEC Corporation uPD720200 USB 3.0 Host Controller + \-02.0 Red Hat, Inc. Virtio network device + Lsusb: + Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub + Bus 001 Device 003: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Mouse + Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Keyboard + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + Lsusb-t: + /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M + /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 480M + |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 480M + |__ Port 2: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 480M + Package: linux (not installed) + PciMultimedia: + + ProcEnviron: + LANG=C.UTF-8 + PATH=(custom, no user) + SHELL=/bin/bash + TERM=vt220 + XDG_RUNTIME_DIR= + ProcFB: + + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinux-6.2.0-19-generic root=LABEL=cloudimg-rootfs ro console=hvc0 earlyprintk + ProcLoadAvg: 0.06 0.05 0.02 1/109 938 + ProcLocks: + 1: FLOCK ADVISORY WRITE 597 08:01:73471 0 EOF + 2: FLOCK ADVISORY WRITE 585 00:18:949 0 EOF + 3: POSIX ADVISORY WRITE 311 00:18:436 0 EOF + ProcSwaps: Filename TypeSize UsedPriority + ProcVersion: Linux version 6.2.0-19-generic (buildd@bos02-ppc64el-009) (powerpc64le-linux-gnu-gcc-12 (Ubuntu 12.2.0-17ubuntu1) 12.2.0, GNU ld (GNU Binutils for Ubuntu) 2.40) #19-Ubuntu SMP Sat Mar 25 10:13:41 UTC 2023 + ProcVersionSignature: Ubuntu 6.2.0-19.19-generic 6.2.6 + RelatedPackageVersions: + linux-restricted-modules-6.2.0-19-generic N/A + linux-backports-modules-6.2.0-19-generic N/A + linux-firmwareN/A + RfKill: Error: [Errno 2] No such file or directory: 'rfkill' + Tags: cloud-image lunar + Uname: Linux 6.2.0-19-generic ppc64le + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: N/A + _MarkForUpload: True + acpidump: + + cpu_cores: Number of cores present = 1 + cpu_coreson: Number of cores online = 1 + cpu_dscr: DSCR is 0 + cpu_freq: + Tool Computed frequencies + min : 2.293 GHz (cpu 0) + max : 2.293 GHz (cpu 0) + avg : 2.293 GHz + cpu_runmode: run-mode=0 + cpu_smt: Error: command ['ppc64_cpu', '--smt'] failed with exit code 255: Machine is not SMT capable ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/2015994/+attachment/5663268/+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/2015994 Title: 23.04 installer display broken with fbdev on ppc64el Status in linux package in Ubuntu: Confirmed Bug description: Hi, latest cloud image ( Daily Build [20230405] : https://cloud-images.ubuntu.com/lunar/current/lunar-server-cloudimg-ppc64el.img ) , especially kernel 6.2.0-19-generic used, has the same issue as the one I encountered on Debian : https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033058 . qemu vga output with fbdev gets stuck at kernel boot time while serial console looks ok till login prompt . I guess it's going to propagate to http://cdimage.ubuntu.com/ubuntu- server/daily-
[Kernel-packages] [Bug 2015994] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/2015994/+attachment/5663270/+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/2015994 Title: 23.04 installer display broken with fbdev on ppc64el Status in linux package in Ubuntu: Confirmed Bug description: Hi, latest cloud image ( Daily Build [20230405] : https://cloud-images.ubuntu.com/lunar/current/lunar-server-cloudimg-ppc64el.img ) , especially kernel 6.2.0-19-generic used, has the same issue as the one I encountered on Debian : https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033058 . qemu vga output with fbdev gets stuck at kernel boot time while serial console looks ok till login prompt . I guess it's going to propagate to http://cdimage.ubuntu.com/ubuntu- server/daily-live/current/lunar-live-server-ppc64el.iso soon. I open this bug to monitor the upstream fix Cyril Brulebois proposed and hopefully get it into Ubuntu asap. Thanks, F. --- ProblemType: Bug .var.log.platform: AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Apr 12 12:49 seq crw-rw 1 root audio 116, 33 Apr 12 12:49 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.26.0-0ubuntu2 Architecture: ppc64el 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: CRDA: N/A CasperMD5CheckResult: unknown CloudArchitecture: ppc64le CloudBuildName: server CloudID: nocloud CloudName: unknown CloudPlatform: nocloud CloudSerial: 20230405 CloudSubPlatform: config-disk (/dev/sr0) DistroRelease: Ubuntu 23.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci-vt: -[:00]-+-00.0 Device 1234: +-01.0 NEC Corporation uPD720200 USB 3.0 Host Controller \-02.0 Red Hat, Inc. Virtio network device Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Mouse Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Keyboard Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 480M |__ Port 2: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 480M Package: linux (not installed) PciMultimedia: ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=vt220 XDG_RUNTIME_DIR= ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinux-6.2.0-19-generic root=LABEL=cloudimg-rootfs ro console=hvc0 earlyprintk ProcLoadAvg: 0.06 0.05 0.02 1/109 938 ProcLocks: 1: FLOCK ADVISORY WRITE 597 08:01:73471 0 EOF 2: FLOCK ADVISORY WRITE 585 00:18:949 0 EOF 3: POSIX ADVISORY WRITE 311 00:18:436 0 EOF ProcSwaps: Filename TypeSize UsedPriority ProcVersion: Linux version 6.2.0-19-generic (buildd@bos02-ppc64el-009) (powerpc64le-linux-gnu-gcc-12 (Ubuntu 12.2.0-17ubuntu1) 12.2.0, GNU ld (GNU Binutils for Ubuntu) 2.40) #19-Ubuntu SMP Sat Mar 25 10:13:41 UTC 2023 ProcVersionSignature: Ubuntu 6.2.0-19.19-generic 6.2.6 RelatedPackageVersions: linux-restricted-modules-6.2.0-19-generic N/A linux-backports-modules-6.2.0-19-generic N/A linux-firmwareN/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: cloud-image lunar Uname: Linux 6.2.0-19-generic ppc64le UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True acpidump: cpu_cores: Number of cores present = 1 cpu_coreson: Number of cores online = 1 cpu_dscr: DSCR is 0 cpu_freq: Tool Computed frequencies min : 2.293 GHz (cpu 0) max : 2.293 GHz (cpu 0) avg : 2.293 GHz cpu_runmode: run-mode=0 cpu_smt: Error: command ['ppc64_cpu', '--smt'] failed with exit code 255: Machine is not SMT capable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2015994/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2015994] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/2015994/+attachment/5663273/+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/2015994 Title: 23.04 installer display broken with fbdev on ppc64el Status in linux package in Ubuntu: Confirmed Bug description: Hi, latest cloud image ( Daily Build [20230405] : https://cloud-images.ubuntu.com/lunar/current/lunar-server-cloudimg-ppc64el.img ) , especially kernel 6.2.0-19-generic used, has the same issue as the one I encountered on Debian : https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033058 . qemu vga output with fbdev gets stuck at kernel boot time while serial console looks ok till login prompt . I guess it's going to propagate to http://cdimage.ubuntu.com/ubuntu- server/daily-live/current/lunar-live-server-ppc64el.iso soon. I open this bug to monitor the upstream fix Cyril Brulebois proposed and hopefully get it into Ubuntu asap. Thanks, F. --- ProblemType: Bug .var.log.platform: AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Apr 12 12:49 seq crw-rw 1 root audio 116, 33 Apr 12 12:49 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.26.0-0ubuntu2 Architecture: ppc64el 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: CRDA: N/A CasperMD5CheckResult: unknown CloudArchitecture: ppc64le CloudBuildName: server CloudID: nocloud CloudName: unknown CloudPlatform: nocloud CloudSerial: 20230405 CloudSubPlatform: config-disk (/dev/sr0) DistroRelease: Ubuntu 23.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci-vt: -[:00]-+-00.0 Device 1234: +-01.0 NEC Corporation uPD720200 USB 3.0 Host Controller \-02.0 Red Hat, Inc. Virtio network device Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Mouse Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Keyboard Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 480M |__ Port 2: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 480M Package: linux (not installed) PciMultimedia: ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=vt220 XDG_RUNTIME_DIR= ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinux-6.2.0-19-generic root=LABEL=cloudimg-rootfs ro console=hvc0 earlyprintk ProcLoadAvg: 0.06 0.05 0.02 1/109 938 ProcLocks: 1: FLOCK ADVISORY WRITE 597 08:01:73471 0 EOF 2: FLOCK ADVISORY WRITE 585 00:18:949 0 EOF 3: POSIX ADVISORY WRITE 311 00:18:436 0 EOF ProcSwaps: Filename TypeSize UsedPriority ProcVersion: Linux version 6.2.0-19-generic (buildd@bos02-ppc64el-009) (powerpc64le-linux-gnu-gcc-12 (Ubuntu 12.2.0-17ubuntu1) 12.2.0, GNU ld (GNU Binutils for Ubuntu) 2.40) #19-Ubuntu SMP Sat Mar 25 10:13:41 UTC 2023 ProcVersionSignature: Ubuntu 6.2.0-19.19-generic 6.2.6 RelatedPackageVersions: linux-restricted-modules-6.2.0-19-generic N/A linux-backports-modules-6.2.0-19-generic N/A linux-firmwareN/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: cloud-image lunar Uname: Linux 6.2.0-19-generic ppc64le UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True acpidump: cpu_cores: Number of cores present = 1 cpu_coreson: Number of cores online = 1 cpu_dscr: DSCR is 0 cpu_freq: Tool Computed frequencies min : 2.293 GHz (cpu 0) max : 2.293 GHz (cpu 0) avg : 2.293 GHz cpu_runmode: run-mode=0 cpu_smt: Error: command ['ppc64_cpu', '--smt'] failed with exit code 255: Machine is not SMT capable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2015994/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2015994] DeviceTree.tar.gz
apport information ** Attachment added: "DeviceTree.tar.gz" https://bugs.launchpad.net/bugs/2015994/+attachment/5663269/+files/DeviceTree.tar.gz -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2015994 Title: 23.04 installer display broken with fbdev on ppc64el Status in linux package in Ubuntu: Confirmed Bug description: Hi, latest cloud image ( Daily Build [20230405] : https://cloud-images.ubuntu.com/lunar/current/lunar-server-cloudimg-ppc64el.img ) , especially kernel 6.2.0-19-generic used, has the same issue as the one I encountered on Debian : https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033058 . qemu vga output with fbdev gets stuck at kernel boot time while serial console looks ok till login prompt . I guess it's going to propagate to http://cdimage.ubuntu.com/ubuntu- server/daily-live/current/lunar-live-server-ppc64el.iso soon. I open this bug to monitor the upstream fix Cyril Brulebois proposed and hopefully get it into Ubuntu asap. Thanks, F. --- ProblemType: Bug .var.log.platform: AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Apr 12 12:49 seq crw-rw 1 root audio 116, 33 Apr 12 12:49 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.26.0-0ubuntu2 Architecture: ppc64el 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: CRDA: N/A CasperMD5CheckResult: unknown CloudArchitecture: ppc64le CloudBuildName: server CloudID: nocloud CloudName: unknown CloudPlatform: nocloud CloudSerial: 20230405 CloudSubPlatform: config-disk (/dev/sr0) DistroRelease: Ubuntu 23.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci-vt: -[:00]-+-00.0 Device 1234: +-01.0 NEC Corporation uPD720200 USB 3.0 Host Controller \-02.0 Red Hat, Inc. Virtio network device Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Mouse Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Keyboard Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 480M |__ Port 2: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 480M Package: linux (not installed) PciMultimedia: ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=vt220 XDG_RUNTIME_DIR= ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinux-6.2.0-19-generic root=LABEL=cloudimg-rootfs ro console=hvc0 earlyprintk ProcLoadAvg: 0.06 0.05 0.02 1/109 938 ProcLocks: 1: FLOCK ADVISORY WRITE 597 08:01:73471 0 EOF 2: FLOCK ADVISORY WRITE 585 00:18:949 0 EOF 3: POSIX ADVISORY WRITE 311 00:18:436 0 EOF ProcSwaps: Filename TypeSize UsedPriority ProcVersion: Linux version 6.2.0-19-generic (buildd@bos02-ppc64el-009) (powerpc64le-linux-gnu-gcc-12 (Ubuntu 12.2.0-17ubuntu1) 12.2.0, GNU ld (GNU Binutils for Ubuntu) 2.40) #19-Ubuntu SMP Sat Mar 25 10:13:41 UTC 2023 ProcVersionSignature: Ubuntu 6.2.0-19.19-generic 6.2.6 RelatedPackageVersions: linux-restricted-modules-6.2.0-19-generic N/A linux-backports-modules-6.2.0-19-generic N/A linux-firmwareN/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: cloud-image lunar Uname: Linux 6.2.0-19-generic ppc64le UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True acpidump: cpu_cores: Number of cores present = 1 cpu_coreson: Number of cores online = 1 cpu_dscr: DSCR is 0 cpu_freq: Tool Computed frequencies min : 2.293 GHz (cpu 0) max : 2.293 GHz (cpu 0) avg : 2.293 GHz cpu_runmode: run-mode=0 cpu_smt: Error: command ['ppc64_cpu', '--smt'] failed with exit code 255: Machine is not SMT capable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2015994/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2015994] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/2015994/+attachment/5663271/+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/2015994 Title: 23.04 installer display broken with fbdev on ppc64el Status in linux package in Ubuntu: Confirmed Bug description: Hi, latest cloud image ( Daily Build [20230405] : https://cloud-images.ubuntu.com/lunar/current/lunar-server-cloudimg-ppc64el.img ) , especially kernel 6.2.0-19-generic used, has the same issue as the one I encountered on Debian : https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033058 . qemu vga output with fbdev gets stuck at kernel boot time while serial console looks ok till login prompt . I guess it's going to propagate to http://cdimage.ubuntu.com/ubuntu- server/daily-live/current/lunar-live-server-ppc64el.iso soon. I open this bug to monitor the upstream fix Cyril Brulebois proposed and hopefully get it into Ubuntu asap. Thanks, F. --- ProblemType: Bug .var.log.platform: AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Apr 12 12:49 seq crw-rw 1 root audio 116, 33 Apr 12 12:49 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.26.0-0ubuntu2 Architecture: ppc64el 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: CRDA: N/A CasperMD5CheckResult: unknown CloudArchitecture: ppc64le CloudBuildName: server CloudID: nocloud CloudName: unknown CloudPlatform: nocloud CloudSerial: 20230405 CloudSubPlatform: config-disk (/dev/sr0) DistroRelease: Ubuntu 23.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci-vt: -[:00]-+-00.0 Device 1234: +-01.0 NEC Corporation uPD720200 USB 3.0 Host Controller \-02.0 Red Hat, Inc. Virtio network device Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Mouse Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Keyboard Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 480M |__ Port 2: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 480M Package: linux (not installed) PciMultimedia: ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=vt220 XDG_RUNTIME_DIR= ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinux-6.2.0-19-generic root=LABEL=cloudimg-rootfs ro console=hvc0 earlyprintk ProcLoadAvg: 0.06 0.05 0.02 1/109 938 ProcLocks: 1: FLOCK ADVISORY WRITE 597 08:01:73471 0 EOF 2: FLOCK ADVISORY WRITE 585 00:18:949 0 EOF 3: POSIX ADVISORY WRITE 311 00:18:436 0 EOF ProcSwaps: Filename TypeSize UsedPriority ProcVersion: Linux version 6.2.0-19-generic (buildd@bos02-ppc64el-009) (powerpc64le-linux-gnu-gcc-12 (Ubuntu 12.2.0-17ubuntu1) 12.2.0, GNU ld (GNU Binutils for Ubuntu) 2.40) #19-Ubuntu SMP Sat Mar 25 10:13:41 UTC 2023 ProcVersionSignature: Ubuntu 6.2.0-19.19-generic 6.2.6 RelatedPackageVersions: linux-restricted-modules-6.2.0-19-generic N/A linux-backports-modules-6.2.0-19-generic N/A linux-firmwareN/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: cloud-image lunar Uname: Linux 6.2.0-19-generic ppc64le UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True acpidump: cpu_cores: Number of cores present = 1 cpu_coreson: Number of cores online = 1 cpu_dscr: DSCR is 0 cpu_freq: Tool Computed frequencies min : 2.293 GHz (cpu 0) max : 2.293 GHz (cpu 0) avg : 2.293 GHz cpu_runmode: run-mode=0 cpu_smt: Error: command ['ppc64_cpu', '--smt'] failed with exit code 255: Machine is not SMT capable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2015994/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2015994] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/2015994/+attachment/5663272/+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/2015994 Title: 23.04 installer display broken with fbdev on ppc64el Status in linux package in Ubuntu: Confirmed Bug description: Hi, latest cloud image ( Daily Build [20230405] : https://cloud-images.ubuntu.com/lunar/current/lunar-server-cloudimg-ppc64el.img ) , especially kernel 6.2.0-19-generic used, has the same issue as the one I encountered on Debian : https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033058 . qemu vga output with fbdev gets stuck at kernel boot time while serial console looks ok till login prompt . I guess it's going to propagate to http://cdimage.ubuntu.com/ubuntu- server/daily-live/current/lunar-live-server-ppc64el.iso soon. I open this bug to monitor the upstream fix Cyril Brulebois proposed and hopefully get it into Ubuntu asap. Thanks, F. --- ProblemType: Bug .var.log.platform: AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Apr 12 12:49 seq crw-rw 1 root audio 116, 33 Apr 12 12:49 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.26.0-0ubuntu2 Architecture: ppc64el 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: CRDA: N/A CasperMD5CheckResult: unknown CloudArchitecture: ppc64le CloudBuildName: server CloudID: nocloud CloudName: unknown CloudPlatform: nocloud CloudSerial: 20230405 CloudSubPlatform: config-disk (/dev/sr0) DistroRelease: Ubuntu 23.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci-vt: -[:00]-+-00.0 Device 1234: +-01.0 NEC Corporation uPD720200 USB 3.0 Host Controller \-02.0 Red Hat, Inc. Virtio network device Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Mouse Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Keyboard Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 480M |__ Port 2: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 480M Package: linux (not installed) PciMultimedia: ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=vt220 XDG_RUNTIME_DIR= ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinux-6.2.0-19-generic root=LABEL=cloudimg-rootfs ro console=hvc0 earlyprintk ProcLoadAvg: 0.06 0.05 0.02 1/109 938 ProcLocks: 1: FLOCK ADVISORY WRITE 597 08:01:73471 0 EOF 2: FLOCK ADVISORY WRITE 585 00:18:949 0 EOF 3: POSIX ADVISORY WRITE 311 00:18:436 0 EOF ProcSwaps: Filename TypeSize UsedPriority ProcVersion: Linux version 6.2.0-19-generic (buildd@bos02-ppc64el-009) (powerpc64le-linux-gnu-gcc-12 (Ubuntu 12.2.0-17ubuntu1) 12.2.0, GNU ld (GNU Binutils for Ubuntu) 2.40) #19-Ubuntu SMP Sat Mar 25 10:13:41 UTC 2023 ProcVersionSignature: Ubuntu 6.2.0-19.19-generic 6.2.6 RelatedPackageVersions: linux-restricted-modules-6.2.0-19-generic N/A linux-backports-modules-6.2.0-19-generic N/A linux-firmwareN/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: cloud-image lunar Uname: Linux 6.2.0-19-generic ppc64le UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True acpidump: cpu_cores: Number of cores present = 1 cpu_coreson: Number of cores online = 1 cpu_dscr: DSCR is 0 cpu_freq: Tool Computed frequencies min : 2.293 GHz (cpu 0) max : 2.293 GHz (cpu 0) avg : 2.293 GHz cpu_runmode: run-mode=0 cpu_smt: Error: command ['ppc64_cpu', '--smt'] failed with exit code 255: Machine is not SMT capable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2015994/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2015994] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/2015994/+attachment/5663276/+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/2015994 Title: 23.04 installer display broken with fbdev on ppc64el Status in linux package in Ubuntu: Confirmed Bug description: Hi, latest cloud image ( Daily Build [20230405] : https://cloud-images.ubuntu.com/lunar/current/lunar-server-cloudimg-ppc64el.img ) , especially kernel 6.2.0-19-generic used, has the same issue as the one I encountered on Debian : https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033058 . qemu vga output with fbdev gets stuck at kernel boot time while serial console looks ok till login prompt . I guess it's going to propagate to http://cdimage.ubuntu.com/ubuntu- server/daily-live/current/lunar-live-server-ppc64el.iso soon. I open this bug to monitor the upstream fix Cyril Brulebois proposed and hopefully get it into Ubuntu asap. Thanks, F. --- ProblemType: Bug .var.log.platform: AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Apr 12 12:49 seq crw-rw 1 root audio 116, 33 Apr 12 12:49 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.26.0-0ubuntu2 Architecture: ppc64el 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: CRDA: N/A CasperMD5CheckResult: unknown CloudArchitecture: ppc64le CloudBuildName: server CloudID: nocloud CloudName: unknown CloudPlatform: nocloud CloudSerial: 20230405 CloudSubPlatform: config-disk (/dev/sr0) DistroRelease: Ubuntu 23.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci-vt: -[:00]-+-00.0 Device 1234: +-01.0 NEC Corporation uPD720200 USB 3.0 Host Controller \-02.0 Red Hat, Inc. Virtio network device Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Mouse Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Keyboard Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 480M |__ Port 2: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 480M Package: linux (not installed) PciMultimedia: ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=vt220 XDG_RUNTIME_DIR= ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinux-6.2.0-19-generic root=LABEL=cloudimg-rootfs ro console=hvc0 earlyprintk ProcLoadAvg: 0.06 0.05 0.02 1/109 938 ProcLocks: 1: FLOCK ADVISORY WRITE 597 08:01:73471 0 EOF 2: FLOCK ADVISORY WRITE 585 00:18:949 0 EOF 3: POSIX ADVISORY WRITE 311 00:18:436 0 EOF ProcSwaps: Filename TypeSize UsedPriority ProcVersion: Linux version 6.2.0-19-generic (buildd@bos02-ppc64el-009) (powerpc64le-linux-gnu-gcc-12 (Ubuntu 12.2.0-17ubuntu1) 12.2.0, GNU ld (GNU Binutils for Ubuntu) 2.40) #19-Ubuntu SMP Sat Mar 25 10:13:41 UTC 2023 ProcVersionSignature: Ubuntu 6.2.0-19.19-generic 6.2.6 RelatedPackageVersions: linux-restricted-modules-6.2.0-19-generic N/A linux-backports-modules-6.2.0-19-generic N/A linux-firmwareN/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: cloud-image lunar Uname: Linux 6.2.0-19-generic ppc64le UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True acpidump: cpu_cores: Number of cores present = 1 cpu_coreson: Number of cores online = 1 cpu_dscr: DSCR is 0 cpu_freq: Tool Computed frequencies min : 2.293 GHz (cpu 0) max : 2.293 GHz (cpu 0) avg : 2.293 GHz cpu_runmode: run-mode=0 cpu_smt: Error: command ['ppc64_cpu', '--smt'] failed with exit code 255: Machine is not SMT capable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2015994/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2015994] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/2015994/+attachment/5663277/+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/2015994 Title: 23.04 installer display broken with fbdev on ppc64el Status in linux package in Ubuntu: Confirmed Bug description: Hi, latest cloud image ( Daily Build [20230405] : https://cloud-images.ubuntu.com/lunar/current/lunar-server-cloudimg-ppc64el.img ) , especially kernel 6.2.0-19-generic used, has the same issue as the one I encountered on Debian : https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033058 . qemu vga output with fbdev gets stuck at kernel boot time while serial console looks ok till login prompt . I guess it's going to propagate to http://cdimage.ubuntu.com/ubuntu- server/daily-live/current/lunar-live-server-ppc64el.iso soon. I open this bug to monitor the upstream fix Cyril Brulebois proposed and hopefully get it into Ubuntu asap. Thanks, F. --- ProblemType: Bug .var.log.platform: AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Apr 12 12:49 seq crw-rw 1 root audio 116, 33 Apr 12 12:49 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.26.0-0ubuntu2 Architecture: ppc64el 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: CRDA: N/A CasperMD5CheckResult: unknown CloudArchitecture: ppc64le CloudBuildName: server CloudID: nocloud CloudName: unknown CloudPlatform: nocloud CloudSerial: 20230405 CloudSubPlatform: config-disk (/dev/sr0) DistroRelease: Ubuntu 23.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci-vt: -[:00]-+-00.0 Device 1234: +-01.0 NEC Corporation uPD720200 USB 3.0 Host Controller \-02.0 Red Hat, Inc. Virtio network device Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Mouse Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Keyboard Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 480M |__ Port 2: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 480M Package: linux (not installed) PciMultimedia: ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=vt220 XDG_RUNTIME_DIR= ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinux-6.2.0-19-generic root=LABEL=cloudimg-rootfs ro console=hvc0 earlyprintk ProcLoadAvg: 0.06 0.05 0.02 1/109 938 ProcLocks: 1: FLOCK ADVISORY WRITE 597 08:01:73471 0 EOF 2: FLOCK ADVISORY WRITE 585 00:18:949 0 EOF 3: POSIX ADVISORY WRITE 311 00:18:436 0 EOF ProcSwaps: Filename TypeSize UsedPriority ProcVersion: Linux version 6.2.0-19-generic (buildd@bos02-ppc64el-009) (powerpc64le-linux-gnu-gcc-12 (Ubuntu 12.2.0-17ubuntu1) 12.2.0, GNU ld (GNU Binutils for Ubuntu) 2.40) #19-Ubuntu SMP Sat Mar 25 10:13:41 UTC 2023 ProcVersionSignature: Ubuntu 6.2.0-19.19-generic 6.2.6 RelatedPackageVersions: linux-restricted-modules-6.2.0-19-generic N/A linux-backports-modules-6.2.0-19-generic N/A linux-firmwareN/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: cloud-image lunar Uname: Linux 6.2.0-19-generic ppc64le UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True acpidump: cpu_cores: Number of cores present = 1 cpu_coreson: Number of cores online = 1 cpu_dscr: DSCR is 0 cpu_freq: Tool Computed frequencies min : 2.293 GHz (cpu 0) max : 2.293 GHz (cpu 0) avg : 2.293 GHz cpu_runmode: run-mode=0 cpu_smt: Error: command ['ppc64_cpu', '--smt'] failed with exit code 255: Machine is not SMT capable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2015994/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2015994] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/2015994/+attachment/5663278/+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/2015994 Title: 23.04 installer display broken with fbdev on ppc64el Status in linux package in Ubuntu: Confirmed Bug description: Hi, latest cloud image ( Daily Build [20230405] : https://cloud-images.ubuntu.com/lunar/current/lunar-server-cloudimg-ppc64el.img ) , especially kernel 6.2.0-19-generic used, has the same issue as the one I encountered on Debian : https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033058 . qemu vga output with fbdev gets stuck at kernel boot time while serial console looks ok till login prompt . I guess it's going to propagate to http://cdimage.ubuntu.com/ubuntu- server/daily-live/current/lunar-live-server-ppc64el.iso soon. I open this bug to monitor the upstream fix Cyril Brulebois proposed and hopefully get it into Ubuntu asap. Thanks, F. --- ProblemType: Bug .var.log.platform: AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Apr 12 12:49 seq crw-rw 1 root audio 116, 33 Apr 12 12:49 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.26.0-0ubuntu2 Architecture: ppc64el 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: CRDA: N/A CasperMD5CheckResult: unknown CloudArchitecture: ppc64le CloudBuildName: server CloudID: nocloud CloudName: unknown CloudPlatform: nocloud CloudSerial: 20230405 CloudSubPlatform: config-disk (/dev/sr0) DistroRelease: Ubuntu 23.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci-vt: -[:00]-+-00.0 Device 1234: +-01.0 NEC Corporation uPD720200 USB 3.0 Host Controller \-02.0 Red Hat, Inc. Virtio network device Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Mouse Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Keyboard Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 480M |__ Port 2: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 480M Package: linux (not installed) PciMultimedia: ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=vt220 XDG_RUNTIME_DIR= ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinux-6.2.0-19-generic root=LABEL=cloudimg-rootfs ro console=hvc0 earlyprintk ProcLoadAvg: 0.06 0.05 0.02 1/109 938 ProcLocks: 1: FLOCK ADVISORY WRITE 597 08:01:73471 0 EOF 2: FLOCK ADVISORY WRITE 585 00:18:949 0 EOF 3: POSIX ADVISORY WRITE 311 00:18:436 0 EOF ProcSwaps: Filename TypeSize UsedPriority ProcVersion: Linux version 6.2.0-19-generic (buildd@bos02-ppc64el-009) (powerpc64le-linux-gnu-gcc-12 (Ubuntu 12.2.0-17ubuntu1) 12.2.0, GNU ld (GNU Binutils for Ubuntu) 2.40) #19-Ubuntu SMP Sat Mar 25 10:13:41 UTC 2023 ProcVersionSignature: Ubuntu 6.2.0-19.19-generic 6.2.6 RelatedPackageVersions: linux-restricted-modules-6.2.0-19-generic N/A linux-backports-modules-6.2.0-19-generic N/A linux-firmwareN/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: cloud-image lunar Uname: Linux 6.2.0-19-generic ppc64le UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True acpidump: cpu_cores: Number of cores present = 1 cpu_coreson: Number of cores online = 1 cpu_dscr: DSCR is 0 cpu_freq: Tool Computed frequencies min : 2.293 GHz (cpu 0) max : 2.293 GHz (cpu 0) avg : 2.293 GHz cpu_runmode: run-mode=0 cpu_smt: Error: command ['ppc64_cpu', '--smt'] failed with exit code 255: Machine is not SMT capable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2015994/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2015994] nvram.gz
apport information ** Attachment added: "nvram.gz" https://bugs.launchpad.net/bugs/2015994/+attachment/5663279/+files/nvram.gz ** 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/2015994 Title: 23.04 installer display broken with fbdev on ppc64el Status in linux package in Ubuntu: Confirmed Bug description: Hi, latest cloud image ( Daily Build [20230405] : https://cloud-images.ubuntu.com/lunar/current/lunar-server-cloudimg-ppc64el.img ) , especially kernel 6.2.0-19-generic used, has the same issue as the one I encountered on Debian : https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033058 . qemu vga output with fbdev gets stuck at kernel boot time while serial console looks ok till login prompt . I guess it's going to propagate to http://cdimage.ubuntu.com/ubuntu- server/daily-live/current/lunar-live-server-ppc64el.iso soon. I open this bug to monitor the upstream fix Cyril Brulebois proposed and hopefully get it into Ubuntu asap. Thanks, F. --- ProblemType: Bug .var.log.platform: AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Apr 12 12:49 seq crw-rw 1 root audio 116, 33 Apr 12 12:49 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.26.0-0ubuntu2 Architecture: ppc64el 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: CRDA: N/A CasperMD5CheckResult: unknown CloudArchitecture: ppc64le CloudBuildName: server CloudID: nocloud CloudName: unknown CloudPlatform: nocloud CloudSerial: 20230405 CloudSubPlatform: config-disk (/dev/sr0) DistroRelease: Ubuntu 23.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci-vt: -[:00]-+-00.0 Device 1234: +-01.0 NEC Corporation uPD720200 USB 3.0 Host Controller \-02.0 Red Hat, Inc. Virtio network device Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Mouse Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Keyboard Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 480M |__ Port 2: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 480M Package: linux (not installed) PciMultimedia: ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=vt220 XDG_RUNTIME_DIR= ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinux-6.2.0-19-generic root=LABEL=cloudimg-rootfs ro console=hvc0 earlyprintk ProcLoadAvg: 0.06 0.05 0.02 1/109 938 ProcLocks: 1: FLOCK ADVISORY WRITE 597 08:01:73471 0 EOF 2: FLOCK ADVISORY WRITE 585 00:18:949 0 EOF 3: POSIX ADVISORY WRITE 311 00:18:436 0 EOF ProcSwaps: Filename TypeSize UsedPriority ProcVersion: Linux version 6.2.0-19-generic (buildd@bos02-ppc64el-009) (powerpc64le-linux-gnu-gcc-12 (Ubuntu 12.2.0-17ubuntu1) 12.2.0, GNU ld (GNU Binutils for Ubuntu) 2.40) #19-Ubuntu SMP Sat Mar 25 10:13:41 UTC 2023 ProcVersionSignature: Ubuntu 6.2.0-19.19-generic 6.2.6 RelatedPackageVersions: linux-restricted-modules-6.2.0-19-generic N/A linux-backports-modules-6.2.0-19-generic N/A linux-firmwareN/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: cloud-image lunar Uname: Linux 6.2.0-19-generic ppc64le UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True acpidump: cpu_cores: Number of cores present = 1 cpu_coreson: Number of cores online = 1 cpu_dscr: DSCR is 0 cpu_freq: Tool Computed frequencies min : 2.293 GHz (cpu 0) max : 2.293 GHz (cpu 0) avg : 2.293 GHz cpu_runmode: run-mode=0 cpu_smt: Error: command ['ppc64_cpu', '--smt'] failed with exit code 255: Machine is not SMT capable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2015994/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2015994] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/2015994/+attachment/5663274/+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/2015994 Title: 23.04 installer display broken with fbdev on ppc64el Status in linux package in Ubuntu: Confirmed Bug description: Hi, latest cloud image ( Daily Build [20230405] : https://cloud-images.ubuntu.com/lunar/current/lunar-server-cloudimg-ppc64el.img ) , especially kernel 6.2.0-19-generic used, has the same issue as the one I encountered on Debian : https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033058 . qemu vga output with fbdev gets stuck at kernel boot time while serial console looks ok till login prompt . I guess it's going to propagate to http://cdimage.ubuntu.com/ubuntu- server/daily-live/current/lunar-live-server-ppc64el.iso soon. I open this bug to monitor the upstream fix Cyril Brulebois proposed and hopefully get it into Ubuntu asap. Thanks, F. --- ProblemType: Bug .var.log.platform: AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Apr 12 12:49 seq crw-rw 1 root audio 116, 33 Apr 12 12:49 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.26.0-0ubuntu2 Architecture: ppc64el 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: CRDA: N/A CasperMD5CheckResult: unknown CloudArchitecture: ppc64le CloudBuildName: server CloudID: nocloud CloudName: unknown CloudPlatform: nocloud CloudSerial: 20230405 CloudSubPlatform: config-disk (/dev/sr0) DistroRelease: Ubuntu 23.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci-vt: -[:00]-+-00.0 Device 1234: +-01.0 NEC Corporation uPD720200 USB 3.0 Host Controller \-02.0 Red Hat, Inc. Virtio network device Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Mouse Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Keyboard Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 480M |__ Port 2: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 480M Package: linux (not installed) PciMultimedia: ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=vt220 XDG_RUNTIME_DIR= ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinux-6.2.0-19-generic root=LABEL=cloudimg-rootfs ro console=hvc0 earlyprintk ProcLoadAvg: 0.06 0.05 0.02 1/109 938 ProcLocks: 1: FLOCK ADVISORY WRITE 597 08:01:73471 0 EOF 2: FLOCK ADVISORY WRITE 585 00:18:949 0 EOF 3: POSIX ADVISORY WRITE 311 00:18:436 0 EOF ProcSwaps: Filename TypeSize UsedPriority ProcVersion: Linux version 6.2.0-19-generic (buildd@bos02-ppc64el-009) (powerpc64le-linux-gnu-gcc-12 (Ubuntu 12.2.0-17ubuntu1) 12.2.0, GNU ld (GNU Binutils for Ubuntu) 2.40) #19-Ubuntu SMP Sat Mar 25 10:13:41 UTC 2023 ProcVersionSignature: Ubuntu 6.2.0-19.19-generic 6.2.6 RelatedPackageVersions: linux-restricted-modules-6.2.0-19-generic N/A linux-backports-modules-6.2.0-19-generic N/A linux-firmwareN/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: cloud-image lunar Uname: Linux 6.2.0-19-generic ppc64le UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True acpidump: cpu_cores: Number of cores present = 1 cpu_coreson: Number of cores online = 1 cpu_dscr: DSCR is 0 cpu_freq: Tool Computed frequencies min : 2.293 GHz (cpu 0) max : 2.293 GHz (cpu 0) avg : 2.293 GHz cpu_runmode: run-mode=0 cpu_smt: Error: command ['ppc64_cpu', '--smt'] failed with exit code 255: Machine is not SMT capable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2015994/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2015994] ProcMisc.txt
apport information ** Attachment added: "ProcMisc.txt" https://bugs.launchpad.net/bugs/2015994/+attachment/5663275/+files/ProcMisc.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/2015994 Title: 23.04 installer display broken with fbdev on ppc64el Status in linux package in Ubuntu: Confirmed Bug description: Hi, latest cloud image ( Daily Build [20230405] : https://cloud-images.ubuntu.com/lunar/current/lunar-server-cloudimg-ppc64el.img ) , especially kernel 6.2.0-19-generic used, has the same issue as the one I encountered on Debian : https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033058 . qemu vga output with fbdev gets stuck at kernel boot time while serial console looks ok till login prompt . I guess it's going to propagate to http://cdimage.ubuntu.com/ubuntu- server/daily-live/current/lunar-live-server-ppc64el.iso soon. I open this bug to monitor the upstream fix Cyril Brulebois proposed and hopefully get it into Ubuntu asap. Thanks, F. --- ProblemType: Bug .var.log.platform: AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Apr 12 12:49 seq crw-rw 1 root audio 116, 33 Apr 12 12:49 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.26.0-0ubuntu2 Architecture: ppc64el 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: CRDA: N/A CasperMD5CheckResult: unknown CloudArchitecture: ppc64le CloudBuildName: server CloudID: nocloud CloudName: unknown CloudPlatform: nocloud CloudSerial: 20230405 CloudSubPlatform: config-disk (/dev/sr0) DistroRelease: Ubuntu 23.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci-vt: -[:00]-+-00.0 Device 1234: +-01.0 NEC Corporation uPD720200 USB 3.0 Host Controller \-02.0 Red Hat, Inc. Virtio network device Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Mouse Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Keyboard Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 480M |__ Port 2: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 480M Package: linux (not installed) PciMultimedia: ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=vt220 XDG_RUNTIME_DIR= ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinux-6.2.0-19-generic root=LABEL=cloudimg-rootfs ro console=hvc0 earlyprintk ProcLoadAvg: 0.06 0.05 0.02 1/109 938 ProcLocks: 1: FLOCK ADVISORY WRITE 597 08:01:73471 0 EOF 2: FLOCK ADVISORY WRITE 585 00:18:949 0 EOF 3: POSIX ADVISORY WRITE 311 00:18:436 0 EOF ProcSwaps: Filename TypeSize UsedPriority ProcVersion: Linux version 6.2.0-19-generic (buildd@bos02-ppc64el-009) (powerpc64le-linux-gnu-gcc-12 (Ubuntu 12.2.0-17ubuntu1) 12.2.0, GNU ld (GNU Binutils for Ubuntu) 2.40) #19-Ubuntu SMP Sat Mar 25 10:13:41 UTC 2023 ProcVersionSignature: Ubuntu 6.2.0-19.19-generic 6.2.6 RelatedPackageVersions: linux-restricted-modules-6.2.0-19-generic N/A linux-backports-modules-6.2.0-19-generic N/A linux-firmwareN/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: cloud-image lunar Uname: Linux 6.2.0-19-generic ppc64le UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True acpidump: cpu_cores: Number of cores present = 1 cpu_coreson: Number of cores online = 1 cpu_dscr: DSCR is 0 cpu_freq: Tool Computed frequencies min : 2.293 GHz (cpu 0) max : 2.293 GHz (cpu 0) avg : 2.293 GHz cpu_runmode: run-mode=0 cpu_smt: Error: command ['ppc64_cpu', '--smt'] failed with exit code 255: Machine is not SMT capable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2015994/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2013236] Re: Failed to install bcmwl wireless driver during the install
@Brian: by default, the b43 driver won't override the bcma driver (unless you force it to, of course). As for ubuntu-drivers, it does things correctly, meaning that it lists the compatible proprietary driver (broadcom-sta-dkms), without recommending its installation (over the open driver). The "Additional Drivers" interface (software-properties-gtk) lies - even here on my 2011 Macbook Air (with a BCM43224 wifi card, which I am using though the bcma driver - showing the Broadcom device, and saying that the "device is not working", and having "Do not use the device" selected. This is very confusing, although not specific to Ubuntu 23.04. -- 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/2013236 Title: Failed to install bcmwl wireless driver during the install Status in linux-firmware package in Ubuntu: Invalid Status in ubuntu-drivers-common package in Ubuntu: Confirmed Bug description: Specifically for Lunar - using a Macbook Air 2012, its wireless driver was not enabled even though I ticked the wireless tickbox on the installer. A quick look at the installer logs reveals various issues syslog:2023-03-29T18:01:25.141599+00:00 ubuntu-budgie kernel: [ 43.063747] b43 bcma0:1: Direct firmware load for b43/ucode29_mimo.fw failed with error -2 syslog:2023-03-29T18:01:25.141625+00:00 ubuntu-budgie kernel: [ 43.063802] b43 bcma0:1: Direct firmware load for b43/ucode29_mimo.fw failed with error -2 syslog:2023-03-29T18:01:25.141626+00:00 ubuntu-budgie kernel: [ 43.063862] b43 bcma0:1: Direct firmware load for b43-open/ucode29_mimo.fw failed with error -2 syslog:2023-03-29T18:01:25.141626+00:00 ubuntu-budgie kernel: [ 43.063908] b43 bcma0:1: Direct firmware load for b43-open/ucode29_mimo.fw failed with error -2 I will attach the installer logs manually since this was captured after the installation Note - on 20.04.6, 22.04.2 and 22.10 with the same laptop bcmwl was installed correctly during the install so this is a regression with the 6.2 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2013236/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1964992] Re: ZFS ignores ARC sizes below allmem/32
** Tags added: verification-needed-focal ** Tags added: se-sponsor-halves -- 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/1964992 Title: ZFS ignores ARC sizes below allmem/32 Status in zfs-linux package in Ubuntu: Fix Released Status in zfs-linux source package in Bionic: Fix Released Status in zfs-linux source package in Focal: Fix Committed Bug description: [Impact] ZFS ignores tunable "zfs_arc_max" due to it being below allmem/32 threshold. This prevents users from properly restraining ARC sizes, and can cause increased memory contention in some systems. [Test Plan] 1. Deploy test system with ZFS storage and 32GB RAM 2. Add ARC tunables to /etc/modprobe.d/99-zfs-arc.conf # cat /etc/modprobe.d/99-zfs-arc.conf options zfs zfs_arc_min=536870912 options zfs zfs_arc_max=966367641 3. Reboot system 4. Verify ARC sizes through "arc_summary" # arc_summary | grep -A3 "ARC size" ARC size (current): < 0.1 %1.3 MiB Target size (adaptive): 100.0 % 15.7 GiB Min size (hard limit): 3.2 % 512.0 MiB Max size (high water): 31:1 15.7 GiB For a 32GB test system, we should be able to set max ARC sizes below 1GB. [Fix] This has been fixed by upstream commit: - 36a6e2335c45 "Don't ignore zfs_arc_max below allmem/32" - e945e8d7f4fc "Restore FreeBSD sysctl processing for arc.min and arc.max" The commit has been introduced in upstream zfs-2.0.0, so it's needed for Bionic and Focal. Releases starting with Impish already have this commit by default: $ git describe --contains 36a6e2335c45 zfs-2.0.0-rc1~332 $ rmadison zfs-linux zfs-linux | 0.7.5-1ubuntu15| bionic | source zfs-linux | 0.7.5-1ubuntu16.12 | bionic-updates | source zfs-linux | 0.8.3-1ubuntu12| focal | source zfs-linux | 0.8.3-1ubuntu12.9 | focal-security | source zfs-linux | 0.8.3-1ubuntu12.13 | focal-updates | source zfs-linux | 0.8.3-1ubuntu12.14 | focal-proposed | source zfs-linux | 2.0.6-1ubuntu2 | impish | source zfs-linux | 2.0.6-1ubuntu2.1 | impish-updates | source zfs-linux | 2.1.2-1ubuntu3 | jammy | source [Regression Potential] The introduced commit essentially removes the limitation of setting ARC tunables below allmem/32, and re-arranges the order of how some of the tunables are parsed. Regressions would possibly show up as other tunables being ignored or not being set correctly due to parsing errors. We should validate whether other ARC related tunables are still being set correctly, and whether ZFS is using the set values for the ARC memory thresholds. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1964992/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1964992] Re: ZFS ignores ARC sizes below allmem/32
zfs-linux FTBS on riscv64, but that's been the case for the versions from -updates for some time now. It's not related to this upload, but rather to the ZFS version in focal not supporting riscv64: In file included from ../../lib/libspl/include/sys/types.h:36, from ../../module/avl/avl.c:101: ../../lib/libspl/include/sys/isa_defs.h:200:2: error: #error "Unsupported ISA type" 200 | #error "Unsupported ISA type" | ^ ../../lib/libspl/include/sys/isa_defs.h:216:2: error: #error "Neither _LITTLE_ENDIAN nor _BIG_ENDIAN are defined" 216 | #error "Neither _LITTLE_ENDIAN nor _BIG_ENDIAN are defined" | ^ make[5]: *** [Makefile:709: avl.lo] Error 1 -- 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/1964992 Title: ZFS ignores ARC sizes below allmem/32 Status in zfs-linux package in Ubuntu: Fix Released Status in zfs-linux source package in Bionic: Fix Released Status in zfs-linux source package in Focal: Fix Committed Bug description: [Impact] ZFS ignores tunable "zfs_arc_max" due to it being below allmem/32 threshold. This prevents users from properly restraining ARC sizes, and can cause increased memory contention in some systems. [Test Plan] 1. Deploy test system with ZFS storage and 32GB RAM 2. Add ARC tunables to /etc/modprobe.d/99-zfs-arc.conf # cat /etc/modprobe.d/99-zfs-arc.conf options zfs zfs_arc_min=536870912 options zfs zfs_arc_max=966367641 3. Reboot system 4. Verify ARC sizes through "arc_summary" # arc_summary | grep -A3 "ARC size" ARC size (current): < 0.1 %1.3 MiB Target size (adaptive): 100.0 % 15.7 GiB Min size (hard limit): 3.2 % 512.0 MiB Max size (high water): 31:1 15.7 GiB For a 32GB test system, we should be able to set max ARC sizes below 1GB. [Fix] This has been fixed by upstream commit: - 36a6e2335c45 "Don't ignore zfs_arc_max below allmem/32" - e945e8d7f4fc "Restore FreeBSD sysctl processing for arc.min and arc.max" The commit has been introduced in upstream zfs-2.0.0, so it's needed for Bionic and Focal. Releases starting with Impish already have this commit by default: $ git describe --contains 36a6e2335c45 zfs-2.0.0-rc1~332 $ rmadison zfs-linux zfs-linux | 0.7.5-1ubuntu15| bionic | source zfs-linux | 0.7.5-1ubuntu16.12 | bionic-updates | source zfs-linux | 0.8.3-1ubuntu12| focal | source zfs-linux | 0.8.3-1ubuntu12.9 | focal-security | source zfs-linux | 0.8.3-1ubuntu12.13 | focal-updates | source zfs-linux | 0.8.3-1ubuntu12.14 | focal-proposed | source zfs-linux | 2.0.6-1ubuntu2 | impish | source zfs-linux | 2.0.6-1ubuntu2.1 | impish-updates | source zfs-linux | 2.1.2-1ubuntu3 | jammy | source [Regression Potential] The introduced commit essentially removes the limitation of setting ARC tunables below allmem/32, and re-arranges the order of how some of the tunables are parsed. Regressions would possibly show up as other tunables being ignored or not being set correctly due to parsing errors. We should validate whether other ARC related tunables are still being set correctly, and whether ZFS is using the set values for the ARC memory thresholds. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1964992/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2015369] Re: Azure: Add PCI pass-thru support to Hyper-V Confidential VMs
This bug was fixed in the package linux-azure - 6.2.0-1003.3 --- linux-azure (6.2.0-1003.3) lunar; urgency=medium * lunar/linux-azure: 6.2.0-1003.3 -proposed tracker (LP: #2015432) * Packaging resync (LP: #1786013) - debian/dkms-versions -- update from kernel-versions (main/master) * Azure: Add PCI pass-thru support to Hyper-V Confidential VMs (LP: #2015369) - x86/ioremap: Add hypervisor callback for private MMIO mapping in coco VM * Azure: Add new MANA VF performance counters for easier troubleshooting (LP: #2014015) - net: mana: Add new MANA VF performance counters for easier troubleshooting * Azure: smb3: allow deferred close timeout to be configurable (LP: #2013349) - keys: Do not cache key in task struct if key is requested from kernel thread * Azure: not enough RAM under 4GB for CVM (LP: #1967166) - SAUCE: azure: Swiotlb: Add swiotlb_alloc_from_low_pages switch - SAUCE: azure: x86/hyperv: Make swiotlb bounce buffer allocation not just from low pages * Miscellaneous Ubuntu changes - [Config] azure: update annotations after rebase to the latest 6.2 [ Ubuntu: 6.2.0-20.20 ] * lunar/linux: 6.2.0-20.20 -proposed tracker (LP: #2015429) * Packaging resync (LP: #1786013) - debian/dkms-versions -- update from kernel-versions (main/master) * FTBFS with different dkms or when makeflags are set (LP: #2015361) - [Packaging] FTBFS with different dkms or when makeflags are set * expoline.o is packaged unconditionally for s390x (LP: #2013209) - [Packaging] Copy expoline.o only when produced by the build * net:l2tp.sh failure with lunar:linux 6.2 (LP: #2013014) - SAUCE: l2tp: generate correct module alias strings * Miscellaneous Ubuntu changes - [Packaging] annotations: prevent duplicate include lines [ Ubuntu: 6.2.0-19.19 ] * lunar/linux: 6.2.0-19.19 -proposed tracker (LP: #2012488) * Neuter signing tarballs (LP: #2012776) - [Packaging] neuter the signing tarball * LSM stacking and AppArmor refresh for 6.2 kernel (LP: #2012136) - Revert "UBUNTU: [Config] define CONFIG_SECURITY_APPARMOR_RESTRICT_USERNS" - Revert "UBUNTU: SAUCE: apparmor: add user namespace creation mediation" - Revert "UBUNTU: SAUCE: apparmor: Add fine grained mediation of posix mqueues" - Revert "UBUNTU: SAUCE: Revert "apparmor: make __aa_path_perm() static"" - Revert "UBUNTU: SAUCE: LSM: Specify which LSM to display (using struct cred as input)" - Revert "UBUNTU: SAUCE: apparmor: Fix build error, make sk parameter const" - Revert "UBUNTU: SAUCE: LSM: Use lsmblob in smk_netlbl_mls()" - Revert "UBUNTU: SAUCE: LSM: change ima_read_file() to use lsmblob" - Revert "UBUNTU: SAUCE: apparmor: rename kzfree() to kfree_sensitive()" - Revert "UBUNTU: SAUCE: AppArmor: Remove the exclusive flag" - Revert "UBUNTU: SAUCE: LSM: Add /proc attr entry for full LSM context" - Revert "UBUNTU: SAUCE: Audit: Fix incorrect static inline function declration." - Revert "UBUNTU: SAUCE: Audit: Fix for missing NULL check" - Revert "UBUNTU: SAUCE: Audit: Add a new record for multiple object LSM attributes" - Revert "UBUNTU: SAUCE: Audit: Add new record for multiple process LSM attributes" - Revert "UBUNTU: SAUCE: NET: Store LSM netlabel data in a lsmblob" - Revert "UBUNTU: SAUCE: LSM: security_secid_to_secctx in netlink netfilter" - Revert "UBUNTU: SAUCE: LSM: Use lsmcontext in security_inode_getsecctx" - Revert "UBUNTU: SAUCE: LSM: Use lsmcontext in security_secid_to_secctx" - Revert "UBUNTU: SAUCE: LSM: Ensure the correct LSM context releaser" - Revert "UBUNTU: SAUCE: LSM: Specify which LSM to display" - Revert "UBUNTU: SAUCE: IMA: Change internal interfaces to use lsmblobs" - Revert "UBUNTU: SAUCE: LSM: Use lsmblob in security_cred_getsecid" - Revert "UBUNTU: SAUCE: LSM: Use lsmblob in security_inode_getsecid" - Revert "UBUNTU: SAUCE: LSM: Use lsmblob in security_task_getsecid" - Revert "UBUNTU: SAUCE: LSM: Use lsmblob in security_ipc_getsecid" - Revert "UBUNTU: SAUCE: LSM: Use lsmblob in security_secid_to_secctx" - Revert "UBUNTU: SAUCE: LSM: Use lsmblob in security_secctx_to_secid" - Revert "UBUNTU: SAUCE: net: Prepare UDS for security module stacking" - Revert "UBUNTU: SAUCE: LSM: Use lsmblob in security_kernel_act_as" - Revert "UBUNTU: SAUCE: LSM: Use lsmblob in security_audit_rule_match" - Revert "UBUNTU: SAUCE: LSM: Create and manage the lsmblob data structure." - Revert "UBUNTU: SAUCE: LSM: Infrastructure management of the sock security" - Revert "UBUNTU: SAUCE: apparmor: LSM stacking: switch from SK_CTX() to aa_sock()" - Revert "UBUNTU: SAUCE: apparmor: rename aa_sock() to aa_unix_sk()" - Revert "UBUNTU: SAUCE: apparmor: disable showing the mode as part of a secid to secctx" - Revert "UBUNTU: SAUCE: apparmor: fix use after free in sk_peer_label" - Revert
[Kernel-packages] [Bug 2014015] Re: Azure: Add new MANA VF performance counters for easier troubleshooting
This bug was fixed in the package linux-azure - 6.2.0-1003.3 --- linux-azure (6.2.0-1003.3) lunar; urgency=medium * lunar/linux-azure: 6.2.0-1003.3 -proposed tracker (LP: #2015432) * Packaging resync (LP: #1786013) - debian/dkms-versions -- update from kernel-versions (main/master) * Azure: Add PCI pass-thru support to Hyper-V Confidential VMs (LP: #2015369) - x86/ioremap: Add hypervisor callback for private MMIO mapping in coco VM * Azure: Add new MANA VF performance counters for easier troubleshooting (LP: #2014015) - net: mana: Add new MANA VF performance counters for easier troubleshooting * Azure: smb3: allow deferred close timeout to be configurable (LP: #2013349) - keys: Do not cache key in task struct if key is requested from kernel thread * Azure: not enough RAM under 4GB for CVM (LP: #1967166) - SAUCE: azure: Swiotlb: Add swiotlb_alloc_from_low_pages switch - SAUCE: azure: x86/hyperv: Make swiotlb bounce buffer allocation not just from low pages * Miscellaneous Ubuntu changes - [Config] azure: update annotations after rebase to the latest 6.2 [ Ubuntu: 6.2.0-20.20 ] * lunar/linux: 6.2.0-20.20 -proposed tracker (LP: #2015429) * Packaging resync (LP: #1786013) - debian/dkms-versions -- update from kernel-versions (main/master) * FTBFS with different dkms or when makeflags are set (LP: #2015361) - [Packaging] FTBFS with different dkms or when makeflags are set * expoline.o is packaged unconditionally for s390x (LP: #2013209) - [Packaging] Copy expoline.o only when produced by the build * net:l2tp.sh failure with lunar:linux 6.2 (LP: #2013014) - SAUCE: l2tp: generate correct module alias strings * Miscellaneous Ubuntu changes - [Packaging] annotations: prevent duplicate include lines [ Ubuntu: 6.2.0-19.19 ] * lunar/linux: 6.2.0-19.19 -proposed tracker (LP: #2012488) * Neuter signing tarballs (LP: #2012776) - [Packaging] neuter the signing tarball * LSM stacking and AppArmor refresh for 6.2 kernel (LP: #2012136) - Revert "UBUNTU: [Config] define CONFIG_SECURITY_APPARMOR_RESTRICT_USERNS" - Revert "UBUNTU: SAUCE: apparmor: add user namespace creation mediation" - Revert "UBUNTU: SAUCE: apparmor: Add fine grained mediation of posix mqueues" - Revert "UBUNTU: SAUCE: Revert "apparmor: make __aa_path_perm() static"" - Revert "UBUNTU: SAUCE: LSM: Specify which LSM to display (using struct cred as input)" - Revert "UBUNTU: SAUCE: apparmor: Fix build error, make sk parameter const" - Revert "UBUNTU: SAUCE: LSM: Use lsmblob in smk_netlbl_mls()" - Revert "UBUNTU: SAUCE: LSM: change ima_read_file() to use lsmblob" - Revert "UBUNTU: SAUCE: apparmor: rename kzfree() to kfree_sensitive()" - Revert "UBUNTU: SAUCE: AppArmor: Remove the exclusive flag" - Revert "UBUNTU: SAUCE: LSM: Add /proc attr entry for full LSM context" - Revert "UBUNTU: SAUCE: Audit: Fix incorrect static inline function declration." - Revert "UBUNTU: SAUCE: Audit: Fix for missing NULL check" - Revert "UBUNTU: SAUCE: Audit: Add a new record for multiple object LSM attributes" - Revert "UBUNTU: SAUCE: Audit: Add new record for multiple process LSM attributes" - Revert "UBUNTU: SAUCE: NET: Store LSM netlabel data in a lsmblob" - Revert "UBUNTU: SAUCE: LSM: security_secid_to_secctx in netlink netfilter" - Revert "UBUNTU: SAUCE: LSM: Use lsmcontext in security_inode_getsecctx" - Revert "UBUNTU: SAUCE: LSM: Use lsmcontext in security_secid_to_secctx" - Revert "UBUNTU: SAUCE: LSM: Ensure the correct LSM context releaser" - Revert "UBUNTU: SAUCE: LSM: Specify which LSM to display" - Revert "UBUNTU: SAUCE: IMA: Change internal interfaces to use lsmblobs" - Revert "UBUNTU: SAUCE: LSM: Use lsmblob in security_cred_getsecid" - Revert "UBUNTU: SAUCE: LSM: Use lsmblob in security_inode_getsecid" - Revert "UBUNTU: SAUCE: LSM: Use lsmblob in security_task_getsecid" - Revert "UBUNTU: SAUCE: LSM: Use lsmblob in security_ipc_getsecid" - Revert "UBUNTU: SAUCE: LSM: Use lsmblob in security_secid_to_secctx" - Revert "UBUNTU: SAUCE: LSM: Use lsmblob in security_secctx_to_secid" - Revert "UBUNTU: SAUCE: net: Prepare UDS for security module stacking" - Revert "UBUNTU: SAUCE: LSM: Use lsmblob in security_kernel_act_as" - Revert "UBUNTU: SAUCE: LSM: Use lsmblob in security_audit_rule_match" - Revert "UBUNTU: SAUCE: LSM: Create and manage the lsmblob data structure." - Revert "UBUNTU: SAUCE: LSM: Infrastructure management of the sock security" - Revert "UBUNTU: SAUCE: apparmor: LSM stacking: switch from SK_CTX() to aa_sock()" - Revert "UBUNTU: SAUCE: apparmor: rename aa_sock() to aa_unix_sk()" - Revert "UBUNTU: SAUCE: apparmor: disable showing the mode as part of a secid to secctx" - Revert "UBUNTU: SAUCE: apparmor: fix use after free in sk_peer_label" - Revert
[Kernel-packages] [Bug 2009325] Re: NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74
This bug was fixed in the package linux-aws - 6.2.0-1003.3 --- linux-aws (6.2.0-1003.3) lunar; urgency=medium * lunar/linux-aws: 6.2.0-1003.3 -proposed tracker (LP: #2015430) * Packaging resync (LP: #1786013) - debian/dkms-versions -- update from kernel-versions (main/master) * Miscellaneous Ubuntu changes - [Config] aws: update annotations after rebase to the latest 6.2 [ Ubuntu: 6.2.0-20.20 ] * lunar/linux: 6.2.0-20.20 -proposed tracker (LP: #2015429) * Packaging resync (LP: #1786013) - debian/dkms-versions -- update from kernel-versions (main/master) * FTBFS with different dkms or when makeflags are set (LP: #2015361) - [Packaging] FTBFS with different dkms or when makeflags are set * expoline.o is packaged unconditionally for s390x (LP: #2013209) - [Packaging] Copy expoline.o only when produced by the build * net:l2tp.sh failure with lunar:linux 6.2 (LP: #2013014) - SAUCE: l2tp: generate correct module alias strings * Miscellaneous Ubuntu changes - [Packaging] annotations: prevent duplicate include lines [ Ubuntu: 6.2.0-19.19 ] * lunar/linux: 6.2.0-19.19 -proposed tracker (LP: #2012488) * Neuter signing tarballs (LP: #2012776) - [Packaging] neuter the signing tarball * LSM stacking and AppArmor refresh for 6.2 kernel (LP: #2012136) - Revert "UBUNTU: [Config] define CONFIG_SECURITY_APPARMOR_RESTRICT_USERNS" - Revert "UBUNTU: SAUCE: apparmor: add user namespace creation mediation" - Revert "UBUNTU: SAUCE: apparmor: Add fine grained mediation of posix mqueues" - Revert "UBUNTU: SAUCE: Revert "apparmor: make __aa_path_perm() static"" - Revert "UBUNTU: SAUCE: LSM: Specify which LSM to display (using struct cred as input)" - Revert "UBUNTU: SAUCE: apparmor: Fix build error, make sk parameter const" - Revert "UBUNTU: SAUCE: LSM: Use lsmblob in smk_netlbl_mls()" - Revert "UBUNTU: SAUCE: LSM: change ima_read_file() to use lsmblob" - Revert "UBUNTU: SAUCE: apparmor: rename kzfree() to kfree_sensitive()" - Revert "UBUNTU: SAUCE: AppArmor: Remove the exclusive flag" - Revert "UBUNTU: SAUCE: LSM: Add /proc attr entry for full LSM context" - Revert "UBUNTU: SAUCE: Audit: Fix incorrect static inline function declration." - Revert "UBUNTU: SAUCE: Audit: Fix for missing NULL check" - Revert "UBUNTU: SAUCE: Audit: Add a new record for multiple object LSM attributes" - Revert "UBUNTU: SAUCE: Audit: Add new record for multiple process LSM attributes" - Revert "UBUNTU: SAUCE: NET: Store LSM netlabel data in a lsmblob" - Revert "UBUNTU: SAUCE: LSM: security_secid_to_secctx in netlink netfilter" - Revert "UBUNTU: SAUCE: LSM: Use lsmcontext in security_inode_getsecctx" - Revert "UBUNTU: SAUCE: LSM: Use lsmcontext in security_secid_to_secctx" - Revert "UBUNTU: SAUCE: LSM: Ensure the correct LSM context releaser" - Revert "UBUNTU: SAUCE: LSM: Specify which LSM to display" - Revert "UBUNTU: SAUCE: IMA: Change internal interfaces to use lsmblobs" - Revert "UBUNTU: SAUCE: LSM: Use lsmblob in security_cred_getsecid" - Revert "UBUNTU: SAUCE: LSM: Use lsmblob in security_inode_getsecid" - Revert "UBUNTU: SAUCE: LSM: Use lsmblob in security_task_getsecid" - Revert "UBUNTU: SAUCE: LSM: Use lsmblob in security_ipc_getsecid" - Revert "UBUNTU: SAUCE: LSM: Use lsmblob in security_secid_to_secctx" - Revert "UBUNTU: SAUCE: LSM: Use lsmblob in security_secctx_to_secid" - Revert "UBUNTU: SAUCE: net: Prepare UDS for security module stacking" - Revert "UBUNTU: SAUCE: LSM: Use lsmblob in security_kernel_act_as" - Revert "UBUNTU: SAUCE: LSM: Use lsmblob in security_audit_rule_match" - Revert "UBUNTU: SAUCE: LSM: Create and manage the lsmblob data structure." - Revert "UBUNTU: SAUCE: LSM: Infrastructure management of the sock security" - Revert "UBUNTU: SAUCE: apparmor: LSM stacking: switch from SK_CTX() to aa_sock()" - Revert "UBUNTU: SAUCE: apparmor: rename aa_sock() to aa_unix_sk()" - Revert "UBUNTU: SAUCE: apparmor: disable showing the mode as part of a secid to secctx" - Revert "UBUNTU: SAUCE: apparmor: fix use after free in sk_peer_label" - Revert "UBUNTU: SAUCE: apparmor: af_unix mediation" - Revert "UBUNTU: SAUCE: apparmor: patch to provide compatibility with v2.x net rules" - Revert "UBUNTU: SAUCE: apparmor: add/use fns to print hash string hex value" - SAUCE: apparmor: rename SK_CTX() to aa_sock and make it an inline fn - SAUCE: apparmor: Add sysctls for additional controls of unpriv userns restrictions - SAUCE: Stacking v38: LSM: Identify modules by more than name - SAUCE: Stacking v38: LSM: Add an LSM identifier for external use - SAUCE: Stacking v38: LSM: Identify the process attributes for each module - SAUCE: Stacking v38: LSM: Maintain a table of LSM attribute data - SAUCE: Stacking v38: proc: Use lsmids instead
[Kernel-packages] [Bug 2012908] Re: nvidia driver 515 fails to boot on kernel 6.2
After updating the machine doesn't hang anymore, but I do get: me@mymachine:~$ nvidia-smi Failed to initialize NVML: Driver/library version mismatch at the terminal now. (Also, this version of 515 seems to bork external displays on my machine too... :() -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/2012908 Title: nvidia driver 515 fails to boot on kernel 6.2 Status in linux-signed package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-515 package in Ubuntu: In Progress Bug description: I just updated my Lunar install, which brought me the 6.2 kernel, and it failed to start, stalling after enumerating my USB devices, until something times out with a message saying that the udev event queue failed to be drained. When attempting to move on to the normal graphics boot from rescue mode once the timeout is hit, I simply get a black screen. I'm blaming this on the nvidia driver because of this appearing in the log: mars 27 10:33:54 gandalf kernel: INFO: task systemd-udevd:304 blocked for more than 120 seconds. mars 27 10:33:54 gandalf kernel: Tainted: P OE 6.2.0-18-generic #18-Ubuntu mars 27 10:33:54 gandalf kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. mars 27 10:33:54 gandalf kernel: task:systemd-udevd state:D stack:0 pid:304 ppid:258flags:0x4006 mars 27 10:33:54 gandalf kernel: Call Trace: mars 27 10:33:54 gandalf kernel: mars 27 10:33:54 gandalf kernel: __schedule+0x2aa/0x610 mars 27 10:33:54 gandalf kernel: schedule+0x63/0x110 mars 27 10:33:54 gandalf kernel: schedule_preempt_disabled+0x15/0x30 mars 27 10:33:54 gandalf kernel: __mutex_lock.constprop.0+0x3f8/0x7a0 mars 27 10:33:54 gandalf kernel: ? __kmem_cache_alloc_node+0x19d/0x340 mars 27 10:33:54 gandalf kernel: ? nv_drm_calloc+0x1e/0x40 [nvidia_drm] mars 27 10:33:54 gandalf kernel: __mutex_lock_slowpath+0x13/0x20 mars 27 10:33:54 gandalf kernel: mutex_lock+0x3c/0x50 mars 27 10:33:54 gandalf kernel: __nv_drm_connector_detect_internal+0x15c/0x2f0 [nvidia_drm] mars 27 10:33:54 gandalf kernel: nv_drm_connector_detect+0xe/0x20 [nvidia_drm] mars 27 10:33:54 gandalf kernel: drm_helper_probe_detect_ctx+0xa3/0x120 [drm_kms_helper] mars 27 10:33:54 gandalf kernel: check_connector_changed+0x52/0x200 [drm_kms_helper] mars 27 10:33:54 gandalf kernel: drm_helper_hpd_irq_event+0xbc/0x170 [drm_kms_helper] mars 27 10:33:54 gandalf kernel: nv_drm_load+0x2e7/0x480 [nvidia_drm] mars 27 10:33:54 gandalf kernel: ? __pfx_nv_drm_event_callback+0x10/0x10 [nvidia_drm] mars 27 10:33:54 gandalf kernel: drm_dev_register+0x10e/0x250 [drm] mars 27 10:33:54 gandalf kernel: nv_drm_probe_devices+0x111/0x200 [nvidia_drm] mars 27 10:33:54 gandalf kernel: ? __pfx_init_module+0x10/0x10 [nvidia_drm] mars 27 10:33:54 gandalf kernel: nv_drm_init+0x1e/0x60 [nvidia_drm] mars 27 10:33:54 gandalf kernel: nv_linux_drm_init+0xe/0xff0 [nvidia_drm] mars 27 10:33:54 gandalf kernel: do_one_initcall+0x5e/0x250 mars 27 10:33:54 gandalf kernel: do_init_module+0x7b/0x260 mars 27 10:33:54 gandalf kernel: load_module+0xc76/0xd60 mars 27 10:33:54 gandalf kernel: ? kernel_read_file+0x2a4/0x320 mars 27 10:33:54 gandalf kernel: __do_sys_finit_module+0xc4/0x140 mars 27 10:33:54 gandalf kernel: ? __do_sys_finit_module+0xc4/0x140 mars 27 10:33:54 gandalf kernel: __x64_sys_finit_module+0x18/0x30 mars 27 10:33:54 gandalf kernel: do_syscall_64+0x5b/0x90 mars 27 10:33:54 gandalf kernel: ? ksys_mmap_pgoff+0x120/0x260 mars 27 10:33:54 gandalf kernel: ? exit_to_user_mode_prepare+0x30/0xb0 mars 27 10:33:54 gandalf kernel: ? exit_to_user_mode_prepare+0x30/0xb0 mars 27 10:33:54 gandalf kernel: ? syscall_exit_to_user_mode+0x29/0x50 mars 27 10:33:54 gandalf kernel: ? do_syscall_64+0x67/0x90 mars 27 10:33:54 gandalf kernel: ? do_syscall_64+0x67/0x90 mars 27 10:33:54 gandalf kernel: ? exit_to_user_mode_prepare+0x30/0xb0 mars 27 10:33:54 gandalf kernel: ? syscall_exit_to_user_mode+0x29/0x50 mars 27 10:33:54 gandalf kernel: ? do_syscall_64+0x67/0x90 mars 27 10:33:54 gandalf kernel: ? syscall_exit_to_user_mode+0x29/0x50 mars 27 10:33:54 gandalf kernel: ? do_syscall_64+0x67/0x90 mars 27 10:33:54 gandalf kernel: ? do_syscall_64+0x67/0x90 mars 27 10:33:54 gandalf kernel: entry_SYSCALL_64_after_hwframe+0x72/0xdc mars 27 10:33:54 gandalf kernel: RIP: 0033:0x7fd3dc85d89d mars 27 10:33:54 gandalf kernel: RSP: 002b:7ffc801034a8 EFLAGS: 0246 ORIG_RAX: 0139 mars 27 10:33:54 gandalf kernel: RAX: ffda RBX: 55f373907c60 RCX: 7fd3dc85d89d mars 27 10:33:54 gandalf kernel: RDX: RSI: 55f373889af0 RDI: 0012 mars 27 10:33:54 gandalf kernel: RBP: 55f373889af0 R08: R09: 7ffc
[Kernel-packages] [Bug 2015588] Re: package linux-modules-nvidia-525-5.19.0-38-generic 5.19.0-38.39~22.04.1+1 failed to install/upgrade: installed linux-modules-nvidia-525-5.19.0-38-generic package po
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-restricted-modules-hwe-5.19 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2015588 Title: package linux-modules-nvidia-525-5.19.0-38-generic 5.19.0-38.39~22.04.1+1 failed to install/upgrade: installed linux- modules-nvidia-525-5.19.0-38-generic package post-installation script subprocess returned error exit status 127 Status in linux-restricted-modules-hwe-5.19 package in Ubuntu: Confirmed Bug description: dont know what this is about ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-modules-nvidia-525-5.19.0-38-generic 5.19.0-38.39~22.04.1+1 ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass Date: Fri Apr 7 07:46:03 2023 DuplicateSignature: package:linux-modules-nvidia-525-5.19.0-38-generic:5.19.0-38.39~22.04.1+1 Setting up linux-modules-nvidia-525-5.19.0-38-generic (5.19.0-38.39~22.04.1+1) ... /var/lib/dpkg/info/linux-modules-nvidia-525-5.19.0-38-generic.config: 6: /etc/default/linux-modules-nvidia: linux-modules-nvidia-525-open-generic-hwe-22.04: not found dpkg: error processing package linux-modules-nvidia-525-5.19.0-38-generic (--configure): installed linux-modules-nvidia-525-5.19.0-38-generic package post-installation script subprocess returned error exit status 127 ErrorMessage: installed linux-modules-nvidia-525-5.19.0-38-generic package post-installation script subprocess returned error exit status 127 InstallationDate: Installed on 2023-04-03 (3 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.8 SourcePackage: linux-restricted-modules-hwe-5.19 Title: package linux-modules-nvidia-525-5.19.0-38-generic 5.19.0-38.39~22.04.1+1 failed to install/upgrade: installed linux-modules-nvidia-525-5.19.0-38-generic package post-installation script subprocess returned error exit status 127 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules-hwe-5.19/+bug/2015588/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2013086] Re: regression: max number of loop devices
Users of our software (singularity) were affected by this issue. https://github.com/sylabs/singularity/issues/1499 For historic reasons (old kernels without /dev/loop-control), we have been creating /dev/loopXX devices directly via mknod, if needed, before using them. After the backport of https://lkml.org/lkml/2022/12/8/904 it was possible to mknod additional loop devices, in addition to those present on boot, but they could not then be used successfully. We found that switching to creating devices via LOOP_CTL_ADD ioctl against /dev/loop-control avoids the issue. >8 devices are created and are usable. While there will be a workaround for people who can upgrade to a new version of our software, the change in the Ubuntu kernel causes a regression for users of existing versions of singularity, who must set max_loop in the kernel cmdline to work around the problem. ** Bug watch added: github.com/sylabs/singularity/issues #1499 https://github.com/sylabs/singularity/issues/1499 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/2013086 Title: regression: max number of loop devices Status in linux-hwe-5.15 package in Ubuntu: Confirmed Bug description: Since the patch in https://lkml.org/lkml/2022/12/8/904 got backported to linux-hwe-5.15 (apparently in 5.15.0-68) the kernel effectively boots with max_loop=CONFIG_BLK_DEV_LOOP_MIN_COUNT as a parameter. In /boot/config-... we find CONFIG_BLK_DEV_LOOP_MIN_COUNT=8, which means no more than 8 loop devices are supported. This is a regression. At least one other distro solves this by compiling with CONFIG_BLK_DEV_LOOP_MIN_COUNT=0 [1]; maybe Ubuntu could start doing that as well. We currently workaround this by setting max_loop=0 on the kernel cmdline but would rather not have to. [1] https://github.com/archlinux/svntogit- packages/blob/62b8243b1d485493d3e8b10b05281efa20fe7918/trunk/config#L2517 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.15/+bug/2013086/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2007581] Re: gpio: Restrict usage of GPIO chip irq members before initialization
** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/2007581 Title: gpio: Restrict usage of GPIO chip irq members before initialization Status in linux-bluefield package in Ubuntu: Invalid Status in linux-bluefield source package in Focal: Fix Committed Bug description: SRU Justification: [Impact] GPIO chip irq members are exposed before they could be completely initialized and this leads to race conditions. One such issue was observed for the gc->irq.domain variable which was accessed through the pwr-mlxbf.c driver in gpiochip_to_irq() before it could be initialized by gpiochip_add_irqchip(). This resulted in Kernel NULL pointer dereference. This is a well known issue in the linux community and was fixed via 2 commits: 5467801f1fcbdc46bc7298a84dbf3ca1ff2a7320 and 06fb4ecfeac7e00d6704fa5ed19299f2fefb3cc9 (since the previous commit caused a regression) This race condition is intermittent and hard to reproduce. [Fix] * Cherry pick: 5467801f1fcbdc46bc7298a84dbf3ca1ff2a7320 to fix the bug at stake * cherry-pick: 06fb4ecfeac7e00d6704fa5ed19299f2fefb3cc9 to fix a regression introduced by the previous commit [Test Case] * Check that the gpio-mlxbf2.c driver is loaded with no kernel panic * check that all drivers dependent on gpio-mlxbf2.c driver are loaded (mlxbf-gige and pwr-mlxbf) * do 5000 reboots to make sure this race condition no longer happens [Regression Potential] This could cause some regression with the use of gpio interrupts so it is important to test the dependent drivers mlxbf-gige and pwr-mlxbf. Trigger power reset interrupt to test pwr-mlxbf and bring down/up the oob_net0 interface to test mlxbf-gige. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2007581/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2015511] Re: Kinetic update: upstream stable patchset 2023-04-06
** Changed in: linux (Ubuntu Kinetic) 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/2015511 Title: Kinetic update: upstream stable patchset 2023-04-06 Status in linux package in Ubuntu: Invalid Status in linux source package in Kinetic: 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 2023-04-06 Ported from the following upstream stable releases: v5.15.92, v6.1.10 v5.15.93, v6.1.11 v5.15.94, v6.1.12 v5.15.95, v6.1.13 from git://git.kernel.org/ ARM: dts: imx: Fix pca9547 i2c-mux node name ARM: dts: vf610: Fix pca9548 i2c-mux node names arm64: dts: freescale: Fix pca954x i2c-mux node names arm64: dts: imx8mq-thor96: fix no-mmc property for SDHCI firmware: arm_scmi: Clear stale xfer->hdr.status bpf: Skip task with pid=1 in send_signal_common() erofs/zmap.c: Fix incorrect offset calculation blk-cgroup: fix missing pd_online_fn() while activating policy HID: playstation: sanity check DualSense calibration data. dmaengine: imx-sdma: Fix a possible memory leak in sdma_transfer_init cifs: fix return of uninitialized rc in dfs_cache_update_tgthint() extcon: usbc-tusb320: fix kernel-doc warning net: fix NULL pointer in skb_segment_list net: mctp: purge receive queues on sk destruction UBUNTU: Upstream stable to v5.15.92, v6.1.10 firewire: fix memory leak for payload of request subaction to IEC 61883-1 FCP region bus: sunxi-rsb: Fix error handling in sunxi_rsb_init() ASoC: Intel: bytcht_es8316: Drop reference count of ACPI device after use ASoC: Intel: bytcr_rt5651: Drop reference count of ACPI device after use ASoC: Intel: bytcr_rt5640: Drop reference count of ACPI device after use ASoC: Intel: bytcr_wm5102: Drop reference count of ACPI device after use bpf: Fix a possible task gone issue with bpf_send_signal[_thread]() helpers ALSA: hda/via: Avoid potential array out-of-bound in add_secret_dac_path() bpf: Fix to preserve reg parent/live fields when copying range info bpf, sockmap: Check for any of tcp_bpf_prots when cloning a listener arm64: dts: imx8mm: Fix pad control for UART1_DTE_RX drm/vc4: hdmi: make CEC adapter name unique scsi: Revert "scsi: core: map PQ=1, PDT=other values to SCSI_SCAN_TARGET_PRESENT" vhost/net: Clear the pending messages when the backend is removed WRITE is "data source", not destination... READ is "data destination", not source... fix iov_iter_bvec() "direction" argument fix "direction" argument of iov_iter_kvec() ice: Prevent set_channel from changing queues while RDMA active qede: execute xdp_do_flush() before napi_complete_done() virtio-net: execute xdp_do_flush() before napi_complete_done() dpaa_eth: execute xdp_do_flush() before napi_complete_done() dpaa2-eth: execute xdp_do_flush() before napi_complete_done() sfc: correctly advertise tunneled IPv6 segmentation net: phy: dp83822: Fix null pointer access on DP83825/DP83826 devices block, bfq: replace 0/1 with false/true in bic apis block, bfq: fix uaf for bfqq in bic_set_bfqq() netrom: Fix use-after-free caused by accept on already connected socket drm/i915/guc: Fix locking when searching for a hung request drm/i915/adlp: Fix typo for reference clock netfilter: br_netfilter: disable sabotage_in hook after first suppression squashfs: harden sanity check in squashfs_read_xattr_id_table net: phy: meson-gxl: Add generic dummy stubs for MMD register access ip/ip6_gre: Fix changing addr gen mode not generating IPv6 link local address ip/ip6_gre: Fix non-point-to-point tunnel not generating IPv6 link local address riscv: kprobe: Fixup kernel panic when probing an illegal position igc: return an error if the mac type is unknown in igc_ptp_systim_to_hwtstamp() can: j1939: fix errant WARN_ON_ONCE in j1939_session_deactivate ata: libata: Fix sata_down_spd_limit() when no link speed is reported selftests: net: udpgso_bench_rx: Fix 'used uninitialized' compiler warning selftests: net: udpgso_bench_rx/tx: Stop when wrong CLI args are provided selftests: net: udpgso_bench_tx: Cater for pending datagrams zerocopy benchmarking virtio-net: Keep stop() to follow mirror sequence of open() net: openvswitch: fix flow memory leak in ovs_flow_cmd_new efi: fix potential NUL
[Kernel-packages] [Bug 2015812] Re: Kinetic update: upstream stable patchset 2023-04-10
** Changed in: linux (Ubuntu Kinetic) 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/2015812 Title: Kinetic update: upstream stable patchset 2023-04-10 Status in linux package in Ubuntu: Invalid Status in linux source package in Kinetic: 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 2023-04-10 Ported from the following upstream stable releases: v5.15.96, v6.1.14 v5.15.97, v6.1.15 from git://git.kernel.org/ drm/etnaviv: don't truncate physical page address wifi: rtl8xxxu: gen2: Turn on the rate control drm/edid: Fix minimum bpc supported with DSC1.2 for HDMI sink clk: mxl: Switch from direct readl/writel based IO to regmap based IO clk: mxl: Remove redundant spinlocks clk: mxl: Add option to override gate clks clk: mxl: Fix a clk entry by adding relevant flags powerpc: dts: t208x: Mark MAC1 and MAC2 as 10G clk: mxl: syscon_node_to_regmap() returns error pointers random: always mix cycle counter in add_latent_entropy() KVM: x86: Fail emulation during EMULTYPE_SKIP on any exception KVM: SVM: Skip WRMSR fastpath on VM-Exit if next RIP isn't valid can: kvaser_usb: hydra: help gcc-13 to figure out cmd_len powerpc: dts: t208x: Disable 10G on MAC1 and MAC2 powerpc/vmlinux.lds: Ensure STRICT_ALIGN_SIZE is at least page aligned powerpc/64s/radix: Fix RWX mapping with relocated kernel uaccess: Add speculation barrier to copy_from_user() wifi: mwifiex: Add missing compatible string for SD8787 audit: update the mailing list in MAINTAINERS ext4: Fix function prototype mismatch for ext4_feat_ktype Revert "net/sched: taprio: make qdisc_leaf() see the per-netdev-queue pfifo child qdiscs" bpf: add missing header file include wifi: ath11k: fix warning in dma_free_coherent() of memory chunks while recovery sched/psi: Stop relying on timer_pending() for poll_work rescheduling docs: perf: Fix PMU instance name of hisi-pcie-pmu randstruct: disable Clang 15 support UBUNTU: Upstream stable to v5.15.96, v6.1.14 ionic: refactor use of ionic_rx_fill() Fix XFRM-I support for nested ESP tunnels arm64: dts: rockchip: drop unused LED mode property from rk3328-roc-cc ARM: dts: rockchip: add power-domains property to dp node on rk3288 HID: elecom: add support for TrackBall 056E:011C ACPI: NFIT: fix a potential deadlock during NFIT teardown btrfs: send: limit number of clones and allocated memory size ASoC: rt715-sdca: fix clock stop prepare timeout issue IB/hfi1: Assign npages earlier neigh: make sure used and confirmed times are valid HID: core: Fix deadloop in hid_apply_multiplier. x86/cpu: Add Lunar Lake M bpf: bpf_fib_lookup should not return neigh in NUD_FAILED state net: Remove WARN_ON_ONCE(sk->sk_forward_alloc) from sk_stream_kill_queues(). vc_screen: don't clobber return value in vcs_read scripts/tags.sh: fix incompatibility with PCRE2 usb: dwc3: pci: add support for the Intel Meteor Lake-M USB: serial: option: add support for VW/Skoda "Carstick LTE" usb: gadget: u_serial: Add null pointer check in gserial_resume USB: core: Don't hold device lock while reading the "descriptors" sysfs file UBUNTU: Upstream stable to v5.15.97, v6.1.15 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2015812/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2013236] Re: Failed to install bcmwl wireless driver during the install
To answer Paolo - the wireless device did show up and appeared to be usable if I blacklisted bcma on the kernel commandline. Trying to use 'blacklist bcma' in modprobe.d/ did not work. Steve had suggested that if the b43 driver is unusable, like an unsupported PHY, that the module should not be loaded / used anymore. I don't know how feasible that is though. -- 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/2013236 Title: Failed to install bcmwl wireless driver during the install Status in linux-firmware package in Ubuntu: Invalid Status in ubuntu-drivers-common package in Ubuntu: Confirmed Bug description: Specifically for Lunar - using a Macbook Air 2012, its wireless driver was not enabled even though I ticked the wireless tickbox on the installer. A quick look at the installer logs reveals various issues syslog:2023-03-29T18:01:25.141599+00:00 ubuntu-budgie kernel: [ 43.063747] b43 bcma0:1: Direct firmware load for b43/ucode29_mimo.fw failed with error -2 syslog:2023-03-29T18:01:25.141625+00:00 ubuntu-budgie kernel: [ 43.063802] b43 bcma0:1: Direct firmware load for b43/ucode29_mimo.fw failed with error -2 syslog:2023-03-29T18:01:25.141626+00:00 ubuntu-budgie kernel: [ 43.063862] b43 bcma0:1: Direct firmware load for b43-open/ucode29_mimo.fw failed with error -2 syslog:2023-03-29T18:01:25.141626+00:00 ubuntu-budgie kernel: [ 43.063908] b43 bcma0:1: Direct firmware load for b43-open/ucode29_mimo.fw failed with error -2 I will attach the installer logs manually since this was captured after the installation Note - on 20.04.6, 22.04.2 and 22.10 with the same laptop bcmwl was installed correctly during the install so this is a regression with the 6.2 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2013236/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2015498] Re: Debian autoreconstruct Fix restoration of execute permissions
** Changed in: linux (Ubuntu Bionic) Status: Incomplete => Fix Committed ** Changed in: linux (Ubuntu Focal) Status: Incomplete => Fix Committed ** Changed in: linux (Ubuntu Jammy) Status: Incomplete => Fix Committed ** Changed in: linux (Ubuntu Kinetic) Status: Incomplete => Fix Committed ** Changed in: linux (Ubuntu Lunar) 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/2015498 Title: Debian autoreconstruct Fix restoration of execute permissions Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Jammy: Fix Committed Status in linux source package in Kinetic: Fix Committed Status in linux source package in Lunar: Confirmed Bug description: SRU justification [Impact] Debian source package diffs cannot represent that a file should be executable. gen-auto-reconstruct detects when a commit adds a script that is supposed to be invoked during the build and restores the execute permissions in the reconstruct script by adding `chmod +x $file`. But, if a file removes its execute permission, this will change it back. This happened in the last jammy release (version 5.15.0-70.77) where a commit from upstream removed the execute permission for a header file but then our scripts brought it back. [Fix] Andy proposed the following fix https://dpaste.com/6SJ8YR3BM Basically it checks if the permission was added or removed and uses either +x or -x. [Test plan] Easily tested with jammy-kvm, latest release where a rebase picked this commit "treewide: fix up files incorrectly marked executable" where `drivers/gpu/drm/vmwgfx/vmwgfx_msg_arm64.h` changed its permission from 755 to 644 (removed execute). When debian packages are prepared, you'll notice the file has changed its permission back to 755. With the fix, it should be the same. [Regression potential] Low, it is a small fix. Scripts will still have execute permission. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2015498/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2015440] Re: fib_tests.sh in ubuntu_kernel_selftests was skipped silently on Focal
** Changed in: linux (Ubuntu Focal)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2015440
Title:
fib_tests.sh in ubuntu_kernel_selftests was skipped silently on Focal
Status in ubuntu-kernel-tests:
In Progress
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Focal:
Fix Committed
Bug description:
[Impact]
When applying the following commit via stable update (bug 2011625):
Revert "ipv4: Fix incorrect route flushing when source address is
deleted"
The executable bit of this script was dropped. And this test will be
skipped on 5.4:
# selftests: net: fib_tests.sh
# Warning: file fib_tests.sh is missing!
not ok 1 selftests: net: fib_tests.sh
[Fix]
* f0c95f229a ("selftests: Fix the executable permissions for fib_tests.sh")
This can be cherry-picked to Focal from linux-5.4.y of the stable
tree.
[Test]
Run the test with the patched kernel. This test will not be skipped.
[Where problems could occur]
This change just allow the script to get tested, however we will see
failures reported from this test.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2015440/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2016039] [NEW] mlxbf-tmfifo: fix potential race
Public bug reported: SRU Justification: [Impact] This change is needed to avoid potential race of accessing the 'vq' pointer [Fix] The fix adds memory barrier for the is_ready flag and the 'vq' pointer access in mlxbf_tmfifo_virtio_find_vqs(), so updated in vq will be visible before accessing this pointer. [Test Case] Same functionality and testing as on BlueField-1/2/2. No functionality change. [Regression Potential] Same behavior from user perspective. ** Affects: linux-bluefield (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/2016039 Title: mlxbf-tmfifo: fix potential race Status in linux-bluefield package in Ubuntu: New Bug description: SRU Justification: [Impact] This change is needed to avoid potential race of accessing the 'vq' pointer [Fix] The fix adds memory barrier for the is_ready flag and the 'vq' pointer access in mlxbf_tmfifo_virtio_find_vqs(), so updated in vq will be visible before accessing this pointer. [Test Case] Same functionality and testing as on BlueField-1/2/2. No functionality change. [Regression Potential] Same behavior from user perspective. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2016039/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2016040] [NEW] Creating bcache backing device using a Dell Ent NVMe CM6 MU 6.4TB storage fails with "cannot allocate memory" error
Public bug reported: # make-bcache -B /dev/nvme4n1 UUID: 569e90b3-cc2a-4a0e-a201-476c426a2141 Set UUID: d8d8458a-01df-481e-a7dc-e75843a9608f version:1 block_size: 1 data_offset:16 kern.log: Apr 12 18:21:56 pc6a-rb3-n2 kernel: [ 723.854659] bcache: register_bdev() error nvme4n1: cannot allocate memory Apr 12 18:21:56 pc6a-rb3-n2 kernel: [ 723.854662] bcache: register_bdev_worker() error /dev/nvme4n1: fail to register backing device Same error message is mentioned in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1909518, but the suggested configuration change does not fix the issue: # nvme id-ns /dev/nvme4n1 -n 1 -H |grep "LBA Format" [3:0] : 0x3 Current LBA Format Selected LBA Format 0 : Metadata Size: 0 bytes - Data Size: 512 bytes - Relative Performance: 0 Best LBA Format 1 : Metadata Size: 8 bytes - Data Size: 512 bytes - Relative Performance: 0 Best LBA Format 2 : Metadata Size: 0 bytes - Data Size: 1 bytes - Relative Performance: 0 Best LBA Format 3 : Metadata Size: 0 bytes - Data Size: 4096 bytes - Relative Performance: 0 Best (in use) LBA Format 4 : Metadata Size: 8 bytes - Data Size: 4096 bytes - Relative Performance: 0 Best LBA Format 5 : Metadata Size: 64 bytes - Data Size: 4096 bytes - Relative Performance: 0 Best Using a Dell Ent NVMe P5800x WI U.2 400GB storage works as expected: # make-bcache -B /dev/nvme2n1 UUID: b1405a6d-8732-4175-8aba-d67be23b3ff0 Set UUID: af6b190f-a57e-4f2b-926e-904a95268390 version:1 block_size: 8 data_offset:16 # lsblk NAMEMAJ:MIN RM SIZE RO TYPE MOUNTPOINTS ... nvme2n1 259:10 372.6G 0 disk └─bcache0 252:00 372.6G 0 disk ... kern.log: Apr 12 18:47:33 pc6a-rb3-n2 kernel: [ 2261.135332] bcache: register_bdev() registered backing device nvme2n1 Kernel versions tested: 5.19.0-38-generic #39~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC 5.15.0-69-generic #76-Ubuntu SMP ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2016040 Title: Creating bcache backing device using a Dell Ent NVMe CM6 MU 6.4TB storage fails with "cannot allocate memory" error Status in linux package in Ubuntu: New Bug description: # make-bcache -B /dev/nvme4n1 UUID: 569e90b3-cc2a-4a0e-a201-476c426a2141 Set UUID: d8d8458a-01df-481e-a7dc-e75843a9608f version:1 block_size: 1 data_offset:16 kern.log: Apr 12 18:21:56 pc6a-rb3-n2 kernel: [ 723.854659] bcache: register_bdev() error nvme4n1: cannot allocate memory Apr 12 18:21:56 pc6a-rb3-n2 kernel: [ 723.854662] bcache: register_bdev_worker() error /dev/nvme4n1: fail to register backing device Same error message is mentioned in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1909518, but the suggested configuration change does not fix the issue: # nvme id-ns /dev/nvme4n1 -n 1 -H |grep "LBA Format" [3:0] : 0x3 Current LBA Format Selected LBA Format 0 : Metadata Size: 0 bytes - Data Size: 512 bytes - Relative Performance: 0 Best LBA Format 1 : Metadata Size: 8 bytes - Data Size: 512 bytes - Relative Performance: 0 Best LBA Format 2 : Metadata Size: 0 bytes - Data Size: 1 bytes - Relative Performance: 0 Best LBA Format 3 : Metadata Size: 0 bytes - Data Size: 4096 bytes - Relative Performance: 0 Best (in use) LBA Format 4 : Metadata Size: 8 bytes - Data Size: 4096 bytes - Relative Performance: 0 Best LBA Format 5 : Metadata Size: 64 bytes - Data Size: 4096 bytes - Relative Performance: 0 Best Using a Dell Ent NVMe P5800x WI U.2 400GB storage works as expected: # make-bcache -B /dev/nvme2n1 UUID: b1405a6d-8732-4175-8aba-d67be23b3ff0 Set UUID: af6b190f-a57e-4f2b-926e-904a95268390 version:1 block_size: 8 data_offset:16 # lsblk NAMEMAJ:MIN RM SIZE RO TYPE MOUNTPOINTS ... nvme2n1 259:10 372.6G 0 disk └─bcache0 252:00 372.6G 0 disk ... kern.log: Apr 12 18:47:33 pc6a-rb3-n2 kernel: [ 2261.135332] bcache: register_bdev() registered backing device nvme2n1 Kernel versions tested: 5.19.0-38-generic #39~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC 5.15.0-69-generic #76-Ubuntu SMP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2016040/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2016040] 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 2016040 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2016040 Title: Creating bcache backing device using a Dell Ent NVMe CM6 MU 6.4TB storage fails with "cannot allocate memory" error Status in linux package in Ubuntu: Incomplete Bug description: # make-bcache -B /dev/nvme4n1 UUID: 569e90b3-cc2a-4a0e-a201-476c426a2141 Set UUID: d8d8458a-01df-481e-a7dc-e75843a9608f version:1 block_size: 1 data_offset:16 kern.log: Apr 12 18:21:56 pc6a-rb3-n2 kernel: [ 723.854659] bcache: register_bdev() error nvme4n1: cannot allocate memory Apr 12 18:21:56 pc6a-rb3-n2 kernel: [ 723.854662] bcache: register_bdev_worker() error /dev/nvme4n1: fail to register backing device Same error message is mentioned in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1909518, but the suggested configuration change does not fix the issue: # nvme id-ns /dev/nvme4n1 -n 1 -H |grep "LBA Format" [3:0] : 0x3 Current LBA Format Selected LBA Format 0 : Metadata Size: 0 bytes - Data Size: 512 bytes - Relative Performance: 0 Best LBA Format 1 : Metadata Size: 8 bytes - Data Size: 512 bytes - Relative Performance: 0 Best LBA Format 2 : Metadata Size: 0 bytes - Data Size: 1 bytes - Relative Performance: 0 Best LBA Format 3 : Metadata Size: 0 bytes - Data Size: 4096 bytes - Relative Performance: 0 Best (in use) LBA Format 4 : Metadata Size: 8 bytes - Data Size: 4096 bytes - Relative Performance: 0 Best LBA Format 5 : Metadata Size: 64 bytes - Data Size: 4096 bytes - Relative Performance: 0 Best Using a Dell Ent NVMe P5800x WI U.2 400GB storage works as expected: # make-bcache -B /dev/nvme2n1 UUID: b1405a6d-8732-4175-8aba-d67be23b3ff0 Set UUID: af6b190f-a57e-4f2b-926e-904a95268390 version:1 block_size: 8 data_offset:16 # lsblk NAMEMAJ:MIN RM SIZE RO TYPE MOUNTPOINTS ... nvme2n1 259:10 372.6G 0 disk └─bcache0 252:00 372.6G 0 disk ... kern.log: Apr 12 18:47:33 pc6a-rb3-n2 kernel: [ 2261.135332] bcache: register_bdev() registered backing device nvme2n1 Kernel versions tested: 5.19.0-38-generic #39~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC 5.15.0-69-generic #76-Ubuntu SMP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2016040/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2016040] Re: Creating bcache backing device using a Dell Ent NVMe CM6 MU 6.4TB storage fails with "cannot allocate memory" error
apport information ** Tags added: apport-collected jammy uec-images ** Description changed: # make-bcache -B /dev/nvme4n1 UUID: 569e90b3-cc2a-4a0e-a201-476c426a2141 Set UUID: d8d8458a-01df-481e-a7dc-e75843a9608f version:1 block_size: 1 data_offset:16 kern.log: Apr 12 18:21:56 pc6a-rb3-n2 kernel: [ 723.854659] bcache: register_bdev() error nvme4n1: cannot allocate memory Apr 12 18:21:56 pc6a-rb3-n2 kernel: [ 723.854662] bcache: register_bdev_worker() error /dev/nvme4n1: fail to register backing device Same error message is mentioned in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1909518, but the suggested configuration change does not fix the issue: # nvme id-ns /dev/nvme4n1 -n 1 -H |grep "LBA Format" [3:0] : 0x3 Current LBA Format Selected LBA Format 0 : Metadata Size: 0 bytes - Data Size: 512 bytes - Relative Performance: 0 Best LBA Format 1 : Metadata Size: 8 bytes - Data Size: 512 bytes - Relative Performance: 0 Best LBA Format 2 : Metadata Size: 0 bytes - Data Size: 1 bytes - Relative Performance: 0 Best LBA Format 3 : Metadata Size: 0 bytes - Data Size: 4096 bytes - Relative Performance: 0 Best (in use) LBA Format 4 : Metadata Size: 8 bytes - Data Size: 4096 bytes - Relative Performance: 0 Best LBA Format 5 : Metadata Size: 64 bytes - Data Size: 4096 bytes - Relative Performance: 0 Best Using a Dell Ent NVMe P5800x WI U.2 400GB storage works as expected: # make-bcache -B /dev/nvme2n1 UUID: b1405a6d-8732-4175-8aba-d67be23b3ff0 Set UUID: af6b190f-a57e-4f2b-926e-904a95268390 version:1 block_size: 8 data_offset:16 # lsblk NAMEMAJ:MIN RM SIZE RO TYPE MOUNTPOINTS ... nvme2n1 259:10 372.6G 0 disk └─bcache0 252:00 372.6G 0 disk ... kern.log: Apr 12 18:47:33 pc6a-rb3-n2 kernel: [ 2261.135332] bcache: register_bdev() registered backing device nvme2n1 Kernel versions tested: 5.19.0-38-generic #39~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC 5.15.0-69-generic #76-Ubuntu SMP + --- + ProblemType: Bug + AlsaDevices: + total 0 + crw-rw 1 root audio 116, 1 Apr 12 18:10 seq + crw-rw 1 root audio 116, 33 Apr 12 18:10 timer + AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' + ApportVersion: 2.20.11-0ubuntu82.3 + 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: + CRDA: N/A + CasperMD5CheckResult: unknown + DistroRelease: Ubuntu 22.04 + IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' + MachineType: Dell Inc. PowerEdge R7525 + Package: linux (not installed) + PciMultimedia: + + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + LANG=C.UTF-8 + SHELL=/bin/bash + ProcFB: 0 mgag200drmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-38-generic root=UUID=3c0a9c0d-3f5d-4d4d-a571-37298c70a1a3 ro + ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 + RelatedPackageVersions: + linux-restricted-modules-5.19.0-38-generic N/A + linux-backports-modules-5.19.0-38-generic N/A + linux-firmware 20220329.git681281e4-0ubuntu3.12 + RfKill: Error: [Errno 2] No such file or directory: 'rfkill' + Tags: jammy uec-images + Uname: Linux 5.19.0-38-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: N/A + _MarkForUpload: True + dmi.bios.date: 10/25/2022 + dmi.bios.release: 2.10 + dmi.bios.vendor: Dell Inc. + dmi.bios.version: 2.10.2 + dmi.board.name: 03WYW4 + dmi.board.vendor: Dell Inc. + dmi.board.version: A01 + dmi.chassis.type: 23 + dmi.chassis.vendor: Dell Inc. + dmi.modalias: dmi:bvnDellInc.:bvr2.10.2:bd10/25/2022:br2.10:svnDellInc.:pnPowerEdgeR7525:pvr:rvnDellInc.:rn03WYW4:rvrA01:cvnDellInc.:ct23:cvr:skuSKU=08FF;ModelName=PowerEdgeR7525: + dmi.product.family: PowerEdge + dmi.product.name: PowerEdge R7525 + dmi.product.sku: SKU=08FF;ModelName=PowerEdge R7525 + dmi.sys.vendor: Dell Inc. ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/2016040/+attachment/5663411/+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/2016040 Title: Creating bcache backing device using a Dell Ent NVMe CM6 MU 6.4TB storage fails with "cannot allocate memory" error Status in linux package in Ubuntu: Confirmed Bug description: # make-bcache -B /dev/nvme4n1 UUID: 569e90b3-cc2a-4a0e-a201-476c426a2141 Set UUID: d8d8458a-01df-481e-a7dc-e75843a9608f version:1 block_size: 1 data_offset:16 kern.log: Apr 12 18:21:56 pc6
[Kernel-packages] [Bug 2016040] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/2016040/+attachment/5663412/+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/2016040 Title: Creating bcache backing device using a Dell Ent NVMe CM6 MU 6.4TB storage fails with "cannot allocate memory" error Status in linux package in Ubuntu: Confirmed Bug description: # make-bcache -B /dev/nvme4n1 UUID: 569e90b3-cc2a-4a0e-a201-476c426a2141 Set UUID: d8d8458a-01df-481e-a7dc-e75843a9608f version:1 block_size: 1 data_offset:16 kern.log: Apr 12 18:21:56 pc6a-rb3-n2 kernel: [ 723.854659] bcache: register_bdev() error nvme4n1: cannot allocate memory Apr 12 18:21:56 pc6a-rb3-n2 kernel: [ 723.854662] bcache: register_bdev_worker() error /dev/nvme4n1: fail to register backing device Same error message is mentioned in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1909518, but the suggested configuration change does not fix the issue: # nvme id-ns /dev/nvme4n1 -n 1 -H |grep "LBA Format" [3:0] : 0x3 Current LBA Format Selected LBA Format 0 : Metadata Size: 0 bytes - Data Size: 512 bytes - Relative Performance: 0 Best LBA Format 1 : Metadata Size: 8 bytes - Data Size: 512 bytes - Relative Performance: 0 Best LBA Format 2 : Metadata Size: 0 bytes - Data Size: 1 bytes - Relative Performance: 0 Best LBA Format 3 : Metadata Size: 0 bytes - Data Size: 4096 bytes - Relative Performance: 0 Best (in use) LBA Format 4 : Metadata Size: 8 bytes - Data Size: 4096 bytes - Relative Performance: 0 Best LBA Format 5 : Metadata Size: 64 bytes - Data Size: 4096 bytes - Relative Performance: 0 Best Using a Dell Ent NVMe P5800x WI U.2 400GB storage works as expected: # make-bcache -B /dev/nvme2n1 UUID: b1405a6d-8732-4175-8aba-d67be23b3ff0 Set UUID: af6b190f-a57e-4f2b-926e-904a95268390 version:1 block_size: 8 data_offset:16 # lsblk NAMEMAJ:MIN RM SIZE RO TYPE MOUNTPOINTS ... nvme2n1 259:10 372.6G 0 disk └─bcache0 252:00 372.6G 0 disk ... kern.log: Apr 12 18:47:33 pc6a-rb3-n2 kernel: [ 2261.135332] bcache: register_bdev() registered backing device nvme2n1 Kernel versions tested: 5.19.0-38-generic #39~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC 5.15.0-69-generic #76-Ubuntu SMP --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Apr 12 18:10 seq crw-rw 1 root audio 116, 33 Apr 12 18:10 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82.3 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: CRDA: N/A CasperMD5CheckResult: unknown DistroRelease: Ubuntu 22.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: Dell Inc. PowerEdge R7525 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-38-generic root=UUID=3c0a9c0d-3f5d-4d4d-a571-37298c70a1a3 ro ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-38-generic N/A linux-backports-modules-5.19.0-38-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.12 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: jammy uec-images Uname: Linux 5.19.0-38-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 10/25/2022 dmi.bios.release: 2.10 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.10.2 dmi.board.name: 03WYW4 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.10.2:bd10/25/2022:br2.10:svnDellInc.:pnPowerEdgeR7525:pvr:rvnDellInc.:rn03WYW4:rvrA01:cvnDellInc.:ct23:cvr:skuSKU=08FF;ModelName=PowerEdgeR7525: dmi.product.family: PowerEdge dmi.product.name: PowerEdge R7525 dmi.product.sku: SKU=08FF;ModelName=PowerEdge R7525 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2016040/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2016040] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/2016040/+attachment/5663413/+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/2016040 Title: Creating bcache backing device using a Dell Ent NVMe CM6 MU 6.4TB storage fails with "cannot allocate memory" error Status in linux package in Ubuntu: Confirmed Bug description: # make-bcache -B /dev/nvme4n1 UUID: 569e90b3-cc2a-4a0e-a201-476c426a2141 Set UUID: d8d8458a-01df-481e-a7dc-e75843a9608f version:1 block_size: 1 data_offset:16 kern.log: Apr 12 18:21:56 pc6a-rb3-n2 kernel: [ 723.854659] bcache: register_bdev() error nvme4n1: cannot allocate memory Apr 12 18:21:56 pc6a-rb3-n2 kernel: [ 723.854662] bcache: register_bdev_worker() error /dev/nvme4n1: fail to register backing device Same error message is mentioned in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1909518, but the suggested configuration change does not fix the issue: # nvme id-ns /dev/nvme4n1 -n 1 -H |grep "LBA Format" [3:0] : 0x3 Current LBA Format Selected LBA Format 0 : Metadata Size: 0 bytes - Data Size: 512 bytes - Relative Performance: 0 Best LBA Format 1 : Metadata Size: 8 bytes - Data Size: 512 bytes - Relative Performance: 0 Best LBA Format 2 : Metadata Size: 0 bytes - Data Size: 1 bytes - Relative Performance: 0 Best LBA Format 3 : Metadata Size: 0 bytes - Data Size: 4096 bytes - Relative Performance: 0 Best (in use) LBA Format 4 : Metadata Size: 8 bytes - Data Size: 4096 bytes - Relative Performance: 0 Best LBA Format 5 : Metadata Size: 64 bytes - Data Size: 4096 bytes - Relative Performance: 0 Best Using a Dell Ent NVMe P5800x WI U.2 400GB storage works as expected: # make-bcache -B /dev/nvme2n1 UUID: b1405a6d-8732-4175-8aba-d67be23b3ff0 Set UUID: af6b190f-a57e-4f2b-926e-904a95268390 version:1 block_size: 8 data_offset:16 # lsblk NAMEMAJ:MIN RM SIZE RO TYPE MOUNTPOINTS ... nvme2n1 259:10 372.6G 0 disk └─bcache0 252:00 372.6G 0 disk ... kern.log: Apr 12 18:47:33 pc6a-rb3-n2 kernel: [ 2261.135332] bcache: register_bdev() registered backing device nvme2n1 Kernel versions tested: 5.19.0-38-generic #39~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC 5.15.0-69-generic #76-Ubuntu SMP --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Apr 12 18:10 seq crw-rw 1 root audio 116, 33 Apr 12 18:10 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82.3 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: CRDA: N/A CasperMD5CheckResult: unknown DistroRelease: Ubuntu 22.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: Dell Inc. PowerEdge R7525 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-38-generic root=UUID=3c0a9c0d-3f5d-4d4d-a571-37298c70a1a3 ro ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-38-generic N/A linux-backports-modules-5.19.0-38-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.12 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: jammy uec-images Uname: Linux 5.19.0-38-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 10/25/2022 dmi.bios.release: 2.10 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.10.2 dmi.board.name: 03WYW4 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.10.2:bd10/25/2022:br2.10:svnDellInc.:pnPowerEdgeR7525:pvr:rvnDellInc.:rn03WYW4:rvrA01:cvnDellInc.:ct23:cvr:skuSKU=08FF;ModelName=PowerEdgeR7525: dmi.product.family: PowerEdge dmi.product.name: PowerEdge R7525 dmi.product.sku: SKU=08FF;ModelName=PowerEdge R7525 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2016040/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2016040] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/2016040/+attachment/5663414/+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/2016040 Title: Creating bcache backing device using a Dell Ent NVMe CM6 MU 6.4TB storage fails with "cannot allocate memory" error Status in linux package in Ubuntu: Confirmed Bug description: # make-bcache -B /dev/nvme4n1 UUID: 569e90b3-cc2a-4a0e-a201-476c426a2141 Set UUID: d8d8458a-01df-481e-a7dc-e75843a9608f version:1 block_size: 1 data_offset:16 kern.log: Apr 12 18:21:56 pc6a-rb3-n2 kernel: [ 723.854659] bcache: register_bdev() error nvme4n1: cannot allocate memory Apr 12 18:21:56 pc6a-rb3-n2 kernel: [ 723.854662] bcache: register_bdev_worker() error /dev/nvme4n1: fail to register backing device Same error message is mentioned in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1909518, but the suggested configuration change does not fix the issue: # nvme id-ns /dev/nvme4n1 -n 1 -H |grep "LBA Format" [3:0] : 0x3 Current LBA Format Selected LBA Format 0 : Metadata Size: 0 bytes - Data Size: 512 bytes - Relative Performance: 0 Best LBA Format 1 : Metadata Size: 8 bytes - Data Size: 512 bytes - Relative Performance: 0 Best LBA Format 2 : Metadata Size: 0 bytes - Data Size: 1 bytes - Relative Performance: 0 Best LBA Format 3 : Metadata Size: 0 bytes - Data Size: 4096 bytes - Relative Performance: 0 Best (in use) LBA Format 4 : Metadata Size: 8 bytes - Data Size: 4096 bytes - Relative Performance: 0 Best LBA Format 5 : Metadata Size: 64 bytes - Data Size: 4096 bytes - Relative Performance: 0 Best Using a Dell Ent NVMe P5800x WI U.2 400GB storage works as expected: # make-bcache -B /dev/nvme2n1 UUID: b1405a6d-8732-4175-8aba-d67be23b3ff0 Set UUID: af6b190f-a57e-4f2b-926e-904a95268390 version:1 block_size: 8 data_offset:16 # lsblk NAMEMAJ:MIN RM SIZE RO TYPE MOUNTPOINTS ... nvme2n1 259:10 372.6G 0 disk └─bcache0 252:00 372.6G 0 disk ... kern.log: Apr 12 18:47:33 pc6a-rb3-n2 kernel: [ 2261.135332] bcache: register_bdev() registered backing device nvme2n1 Kernel versions tested: 5.19.0-38-generic #39~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC 5.15.0-69-generic #76-Ubuntu SMP --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Apr 12 18:10 seq crw-rw 1 root audio 116, 33 Apr 12 18:10 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82.3 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: CRDA: N/A CasperMD5CheckResult: unknown DistroRelease: Ubuntu 22.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: Dell Inc. PowerEdge R7525 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-38-generic root=UUID=3c0a9c0d-3f5d-4d4d-a571-37298c70a1a3 ro ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-38-generic N/A linux-backports-modules-5.19.0-38-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.12 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: jammy uec-images Uname: Linux 5.19.0-38-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 10/25/2022 dmi.bios.release: 2.10 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.10.2 dmi.board.name: 03WYW4 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.10.2:bd10/25/2022:br2.10:svnDellInc.:pnPowerEdgeR7525:pvr:rvnDellInc.:rn03WYW4:rvrA01:cvnDellInc.:ct23:cvr:skuSKU=08FF;ModelName=PowerEdgeR7525: dmi.product.family: PowerEdge dmi.product.name: PowerEdge R7525 dmi.product.sku: SKU=08FF;ModelName=PowerEdge R7525 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2016040/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2016040] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/2016040/+attachment/5663415/+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/2016040 Title: Creating bcache backing device using a Dell Ent NVMe CM6 MU 6.4TB storage fails with "cannot allocate memory" error Status in linux package in Ubuntu: Confirmed Bug description: # make-bcache -B /dev/nvme4n1 UUID: 569e90b3-cc2a-4a0e-a201-476c426a2141 Set UUID: d8d8458a-01df-481e-a7dc-e75843a9608f version:1 block_size: 1 data_offset:16 kern.log: Apr 12 18:21:56 pc6a-rb3-n2 kernel: [ 723.854659] bcache: register_bdev() error nvme4n1: cannot allocate memory Apr 12 18:21:56 pc6a-rb3-n2 kernel: [ 723.854662] bcache: register_bdev_worker() error /dev/nvme4n1: fail to register backing device Same error message is mentioned in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1909518, but the suggested configuration change does not fix the issue: # nvme id-ns /dev/nvme4n1 -n 1 -H |grep "LBA Format" [3:0] : 0x3 Current LBA Format Selected LBA Format 0 : Metadata Size: 0 bytes - Data Size: 512 bytes - Relative Performance: 0 Best LBA Format 1 : Metadata Size: 8 bytes - Data Size: 512 bytes - Relative Performance: 0 Best LBA Format 2 : Metadata Size: 0 bytes - Data Size: 1 bytes - Relative Performance: 0 Best LBA Format 3 : Metadata Size: 0 bytes - Data Size: 4096 bytes - Relative Performance: 0 Best (in use) LBA Format 4 : Metadata Size: 8 bytes - Data Size: 4096 bytes - Relative Performance: 0 Best LBA Format 5 : Metadata Size: 64 bytes - Data Size: 4096 bytes - Relative Performance: 0 Best Using a Dell Ent NVMe P5800x WI U.2 400GB storage works as expected: # make-bcache -B /dev/nvme2n1 UUID: b1405a6d-8732-4175-8aba-d67be23b3ff0 Set UUID: af6b190f-a57e-4f2b-926e-904a95268390 version:1 block_size: 8 data_offset:16 # lsblk NAMEMAJ:MIN RM SIZE RO TYPE MOUNTPOINTS ... nvme2n1 259:10 372.6G 0 disk └─bcache0 252:00 372.6G 0 disk ... kern.log: Apr 12 18:47:33 pc6a-rb3-n2 kernel: [ 2261.135332] bcache: register_bdev() registered backing device nvme2n1 Kernel versions tested: 5.19.0-38-generic #39~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC 5.15.0-69-generic #76-Ubuntu SMP --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Apr 12 18:10 seq crw-rw 1 root audio 116, 33 Apr 12 18:10 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82.3 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: CRDA: N/A CasperMD5CheckResult: unknown DistroRelease: Ubuntu 22.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: Dell Inc. PowerEdge R7525 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-38-generic root=UUID=3c0a9c0d-3f5d-4d4d-a571-37298c70a1a3 ro ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-38-generic N/A linux-backports-modules-5.19.0-38-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.12 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: jammy uec-images Uname: Linux 5.19.0-38-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 10/25/2022 dmi.bios.release: 2.10 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.10.2 dmi.board.name: 03WYW4 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.10.2:bd10/25/2022:br2.10:svnDellInc.:pnPowerEdgeR7525:pvr:rvnDellInc.:rn03WYW4:rvrA01:cvnDellInc.:ct23:cvr:skuSKU=08FF;ModelName=PowerEdgeR7525: dmi.product.family: PowerEdge dmi.product.name: PowerEdge R7525 dmi.product.sku: SKU=08FF;ModelName=PowerEdge R7525 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2016040/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2016040] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/2016040/+attachment/5663416/+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/2016040 Title: Creating bcache backing device using a Dell Ent NVMe CM6 MU 6.4TB storage fails with "cannot allocate memory" error Status in linux package in Ubuntu: Confirmed Bug description: # make-bcache -B /dev/nvme4n1 UUID: 569e90b3-cc2a-4a0e-a201-476c426a2141 Set UUID: d8d8458a-01df-481e-a7dc-e75843a9608f version:1 block_size: 1 data_offset:16 kern.log: Apr 12 18:21:56 pc6a-rb3-n2 kernel: [ 723.854659] bcache: register_bdev() error nvme4n1: cannot allocate memory Apr 12 18:21:56 pc6a-rb3-n2 kernel: [ 723.854662] bcache: register_bdev_worker() error /dev/nvme4n1: fail to register backing device Same error message is mentioned in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1909518, but the suggested configuration change does not fix the issue: # nvme id-ns /dev/nvme4n1 -n 1 -H |grep "LBA Format" [3:0] : 0x3 Current LBA Format Selected LBA Format 0 : Metadata Size: 0 bytes - Data Size: 512 bytes - Relative Performance: 0 Best LBA Format 1 : Metadata Size: 8 bytes - Data Size: 512 bytes - Relative Performance: 0 Best LBA Format 2 : Metadata Size: 0 bytes - Data Size: 1 bytes - Relative Performance: 0 Best LBA Format 3 : Metadata Size: 0 bytes - Data Size: 4096 bytes - Relative Performance: 0 Best (in use) LBA Format 4 : Metadata Size: 8 bytes - Data Size: 4096 bytes - Relative Performance: 0 Best LBA Format 5 : Metadata Size: 64 bytes - Data Size: 4096 bytes - Relative Performance: 0 Best Using a Dell Ent NVMe P5800x WI U.2 400GB storage works as expected: # make-bcache -B /dev/nvme2n1 UUID: b1405a6d-8732-4175-8aba-d67be23b3ff0 Set UUID: af6b190f-a57e-4f2b-926e-904a95268390 version:1 block_size: 8 data_offset:16 # lsblk NAMEMAJ:MIN RM SIZE RO TYPE MOUNTPOINTS ... nvme2n1 259:10 372.6G 0 disk └─bcache0 252:00 372.6G 0 disk ... kern.log: Apr 12 18:47:33 pc6a-rb3-n2 kernel: [ 2261.135332] bcache: register_bdev() registered backing device nvme2n1 Kernel versions tested: 5.19.0-38-generic #39~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC 5.15.0-69-generic #76-Ubuntu SMP --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Apr 12 18:10 seq crw-rw 1 root audio 116, 33 Apr 12 18:10 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82.3 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: CRDA: N/A CasperMD5CheckResult: unknown DistroRelease: Ubuntu 22.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: Dell Inc. PowerEdge R7525 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-38-generic root=UUID=3c0a9c0d-3f5d-4d4d-a571-37298c70a1a3 ro ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-38-generic N/A linux-backports-modules-5.19.0-38-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.12 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: jammy uec-images Uname: Linux 5.19.0-38-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 10/25/2022 dmi.bios.release: 2.10 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.10.2 dmi.board.name: 03WYW4 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.10.2:bd10/25/2022:br2.10:svnDellInc.:pnPowerEdgeR7525:pvr:rvnDellInc.:rn03WYW4:rvrA01:cvnDellInc.:ct23:cvr:skuSKU=08FF;ModelName=PowerEdgeR7525: dmi.product.family: PowerEdge dmi.product.name: PowerEdge R7525 dmi.product.sku: SKU=08FF;ModelName=PowerEdge R7525 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2016040/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2016040] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/2016040/+attachment/5663419/+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/2016040 Title: Creating bcache backing device using a Dell Ent NVMe CM6 MU 6.4TB storage fails with "cannot allocate memory" error Status in linux package in Ubuntu: Confirmed Bug description: # make-bcache -B /dev/nvme4n1 UUID: 569e90b3-cc2a-4a0e-a201-476c426a2141 Set UUID: d8d8458a-01df-481e-a7dc-e75843a9608f version:1 block_size: 1 data_offset:16 kern.log: Apr 12 18:21:56 pc6a-rb3-n2 kernel: [ 723.854659] bcache: register_bdev() error nvme4n1: cannot allocate memory Apr 12 18:21:56 pc6a-rb3-n2 kernel: [ 723.854662] bcache: register_bdev_worker() error /dev/nvme4n1: fail to register backing device Same error message is mentioned in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1909518, but the suggested configuration change does not fix the issue: # nvme id-ns /dev/nvme4n1 -n 1 -H |grep "LBA Format" [3:0] : 0x3 Current LBA Format Selected LBA Format 0 : Metadata Size: 0 bytes - Data Size: 512 bytes - Relative Performance: 0 Best LBA Format 1 : Metadata Size: 8 bytes - Data Size: 512 bytes - Relative Performance: 0 Best LBA Format 2 : Metadata Size: 0 bytes - Data Size: 1 bytes - Relative Performance: 0 Best LBA Format 3 : Metadata Size: 0 bytes - Data Size: 4096 bytes - Relative Performance: 0 Best (in use) LBA Format 4 : Metadata Size: 8 bytes - Data Size: 4096 bytes - Relative Performance: 0 Best LBA Format 5 : Metadata Size: 64 bytes - Data Size: 4096 bytes - Relative Performance: 0 Best Using a Dell Ent NVMe P5800x WI U.2 400GB storage works as expected: # make-bcache -B /dev/nvme2n1 UUID: b1405a6d-8732-4175-8aba-d67be23b3ff0 Set UUID: af6b190f-a57e-4f2b-926e-904a95268390 version:1 block_size: 8 data_offset:16 # lsblk NAMEMAJ:MIN RM SIZE RO TYPE MOUNTPOINTS ... nvme2n1 259:10 372.6G 0 disk └─bcache0 252:00 372.6G 0 disk ... kern.log: Apr 12 18:47:33 pc6a-rb3-n2 kernel: [ 2261.135332] bcache: register_bdev() registered backing device nvme2n1 Kernel versions tested: 5.19.0-38-generic #39~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC 5.15.0-69-generic #76-Ubuntu SMP --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Apr 12 18:10 seq crw-rw 1 root audio 116, 33 Apr 12 18:10 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82.3 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: CRDA: N/A CasperMD5CheckResult: unknown DistroRelease: Ubuntu 22.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: Dell Inc. PowerEdge R7525 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-38-generic root=UUID=3c0a9c0d-3f5d-4d4d-a571-37298c70a1a3 ro ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-38-generic N/A linux-backports-modules-5.19.0-38-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.12 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: jammy uec-images Uname: Linux 5.19.0-38-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 10/25/2022 dmi.bios.release: 2.10 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.10.2 dmi.board.name: 03WYW4 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.10.2:bd10/25/2022:br2.10:svnDellInc.:pnPowerEdgeR7525:pvr:rvnDellInc.:rn03WYW4:rvrA01:cvnDellInc.:ct23:cvr:skuSKU=08FF;ModelName=PowerEdgeR7525: dmi.product.family: PowerEdge dmi.product.name: PowerEdge R7525 dmi.product.sku: SKU=08FF;ModelName=PowerEdge R7525 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2016040/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2016040] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/2016040/+attachment/5663418/+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/2016040 Title: Creating bcache backing device using a Dell Ent NVMe CM6 MU 6.4TB storage fails with "cannot allocate memory" error Status in linux package in Ubuntu: Confirmed Bug description: # make-bcache -B /dev/nvme4n1 UUID: 569e90b3-cc2a-4a0e-a201-476c426a2141 Set UUID: d8d8458a-01df-481e-a7dc-e75843a9608f version:1 block_size: 1 data_offset:16 kern.log: Apr 12 18:21:56 pc6a-rb3-n2 kernel: [ 723.854659] bcache: register_bdev() error nvme4n1: cannot allocate memory Apr 12 18:21:56 pc6a-rb3-n2 kernel: [ 723.854662] bcache: register_bdev_worker() error /dev/nvme4n1: fail to register backing device Same error message is mentioned in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1909518, but the suggested configuration change does not fix the issue: # nvme id-ns /dev/nvme4n1 -n 1 -H |grep "LBA Format" [3:0] : 0x3 Current LBA Format Selected LBA Format 0 : Metadata Size: 0 bytes - Data Size: 512 bytes - Relative Performance: 0 Best LBA Format 1 : Metadata Size: 8 bytes - Data Size: 512 bytes - Relative Performance: 0 Best LBA Format 2 : Metadata Size: 0 bytes - Data Size: 1 bytes - Relative Performance: 0 Best LBA Format 3 : Metadata Size: 0 bytes - Data Size: 4096 bytes - Relative Performance: 0 Best (in use) LBA Format 4 : Metadata Size: 8 bytes - Data Size: 4096 bytes - Relative Performance: 0 Best LBA Format 5 : Metadata Size: 64 bytes - Data Size: 4096 bytes - Relative Performance: 0 Best Using a Dell Ent NVMe P5800x WI U.2 400GB storage works as expected: # make-bcache -B /dev/nvme2n1 UUID: b1405a6d-8732-4175-8aba-d67be23b3ff0 Set UUID: af6b190f-a57e-4f2b-926e-904a95268390 version:1 block_size: 8 data_offset:16 # lsblk NAMEMAJ:MIN RM SIZE RO TYPE MOUNTPOINTS ... nvme2n1 259:10 372.6G 0 disk └─bcache0 252:00 372.6G 0 disk ... kern.log: Apr 12 18:47:33 pc6a-rb3-n2 kernel: [ 2261.135332] bcache: register_bdev() registered backing device nvme2n1 Kernel versions tested: 5.19.0-38-generic #39~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC 5.15.0-69-generic #76-Ubuntu SMP --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Apr 12 18:10 seq crw-rw 1 root audio 116, 33 Apr 12 18:10 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82.3 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: CRDA: N/A CasperMD5CheckResult: unknown DistroRelease: Ubuntu 22.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: Dell Inc. PowerEdge R7525 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-38-generic root=UUID=3c0a9c0d-3f5d-4d4d-a571-37298c70a1a3 ro ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-38-generic N/A linux-backports-modules-5.19.0-38-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.12 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: jammy uec-images Uname: Linux 5.19.0-38-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 10/25/2022 dmi.bios.release: 2.10 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.10.2 dmi.board.name: 03WYW4 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.10.2:bd10/25/2022:br2.10:svnDellInc.:pnPowerEdgeR7525:pvr:rvnDellInc.:rn03WYW4:rvrA01:cvnDellInc.:ct23:cvr:skuSKU=08FF;ModelName=PowerEdgeR7525: dmi.product.family: PowerEdge dmi.product.name: PowerEdge R7525 dmi.product.sku: SKU=08FF;ModelName=PowerEdge R7525 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2016040/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2016040] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/2016040/+attachment/5663417/+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/2016040 Title: Creating bcache backing device using a Dell Ent NVMe CM6 MU 6.4TB storage fails with "cannot allocate memory" error Status in linux package in Ubuntu: Confirmed Bug description: # make-bcache -B /dev/nvme4n1 UUID: 569e90b3-cc2a-4a0e-a201-476c426a2141 Set UUID: d8d8458a-01df-481e-a7dc-e75843a9608f version:1 block_size: 1 data_offset:16 kern.log: Apr 12 18:21:56 pc6a-rb3-n2 kernel: [ 723.854659] bcache: register_bdev() error nvme4n1: cannot allocate memory Apr 12 18:21:56 pc6a-rb3-n2 kernel: [ 723.854662] bcache: register_bdev_worker() error /dev/nvme4n1: fail to register backing device Same error message is mentioned in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1909518, but the suggested configuration change does not fix the issue: # nvme id-ns /dev/nvme4n1 -n 1 -H |grep "LBA Format" [3:0] : 0x3 Current LBA Format Selected LBA Format 0 : Metadata Size: 0 bytes - Data Size: 512 bytes - Relative Performance: 0 Best LBA Format 1 : Metadata Size: 8 bytes - Data Size: 512 bytes - Relative Performance: 0 Best LBA Format 2 : Metadata Size: 0 bytes - Data Size: 1 bytes - Relative Performance: 0 Best LBA Format 3 : Metadata Size: 0 bytes - Data Size: 4096 bytes - Relative Performance: 0 Best (in use) LBA Format 4 : Metadata Size: 8 bytes - Data Size: 4096 bytes - Relative Performance: 0 Best LBA Format 5 : Metadata Size: 64 bytes - Data Size: 4096 bytes - Relative Performance: 0 Best Using a Dell Ent NVMe P5800x WI U.2 400GB storage works as expected: # make-bcache -B /dev/nvme2n1 UUID: b1405a6d-8732-4175-8aba-d67be23b3ff0 Set UUID: af6b190f-a57e-4f2b-926e-904a95268390 version:1 block_size: 8 data_offset:16 # lsblk NAMEMAJ:MIN RM SIZE RO TYPE MOUNTPOINTS ... nvme2n1 259:10 372.6G 0 disk └─bcache0 252:00 372.6G 0 disk ... kern.log: Apr 12 18:47:33 pc6a-rb3-n2 kernel: [ 2261.135332] bcache: register_bdev() registered backing device nvme2n1 Kernel versions tested: 5.19.0-38-generic #39~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC 5.15.0-69-generic #76-Ubuntu SMP --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Apr 12 18:10 seq crw-rw 1 root audio 116, 33 Apr 12 18:10 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82.3 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: CRDA: N/A CasperMD5CheckResult: unknown DistroRelease: Ubuntu 22.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: Dell Inc. PowerEdge R7525 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-38-generic root=UUID=3c0a9c0d-3f5d-4d4d-a571-37298c70a1a3 ro ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-38-generic N/A linux-backports-modules-5.19.0-38-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.12 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: jammy uec-images Uname: Linux 5.19.0-38-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 10/25/2022 dmi.bios.release: 2.10 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.10.2 dmi.board.name: 03WYW4 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.10.2:bd10/25/2022:br2.10:svnDellInc.:pnPowerEdgeR7525:pvr:rvnDellInc.:rn03WYW4:rvrA01:cvnDellInc.:ct23:cvr:skuSKU=08FF;ModelName=PowerEdgeR7525: dmi.product.family: PowerEdge dmi.product.name: PowerEdge R7525 dmi.product.sku: SKU=08FF;ModelName=PowerEdge R7525 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2016040/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2016040] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/2016040/+attachment/5663421/+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/2016040 Title: Creating bcache backing device using a Dell Ent NVMe CM6 MU 6.4TB storage fails with "cannot allocate memory" error Status in linux package in Ubuntu: Confirmed Bug description: # make-bcache -B /dev/nvme4n1 UUID: 569e90b3-cc2a-4a0e-a201-476c426a2141 Set UUID: d8d8458a-01df-481e-a7dc-e75843a9608f version:1 block_size: 1 data_offset:16 kern.log: Apr 12 18:21:56 pc6a-rb3-n2 kernel: [ 723.854659] bcache: register_bdev() error nvme4n1: cannot allocate memory Apr 12 18:21:56 pc6a-rb3-n2 kernel: [ 723.854662] bcache: register_bdev_worker() error /dev/nvme4n1: fail to register backing device Same error message is mentioned in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1909518, but the suggested configuration change does not fix the issue: # nvme id-ns /dev/nvme4n1 -n 1 -H |grep "LBA Format" [3:0] : 0x3 Current LBA Format Selected LBA Format 0 : Metadata Size: 0 bytes - Data Size: 512 bytes - Relative Performance: 0 Best LBA Format 1 : Metadata Size: 8 bytes - Data Size: 512 bytes - Relative Performance: 0 Best LBA Format 2 : Metadata Size: 0 bytes - Data Size: 1 bytes - Relative Performance: 0 Best LBA Format 3 : Metadata Size: 0 bytes - Data Size: 4096 bytes - Relative Performance: 0 Best (in use) LBA Format 4 : Metadata Size: 8 bytes - Data Size: 4096 bytes - Relative Performance: 0 Best LBA Format 5 : Metadata Size: 64 bytes - Data Size: 4096 bytes - Relative Performance: 0 Best Using a Dell Ent NVMe P5800x WI U.2 400GB storage works as expected: # make-bcache -B /dev/nvme2n1 UUID: b1405a6d-8732-4175-8aba-d67be23b3ff0 Set UUID: af6b190f-a57e-4f2b-926e-904a95268390 version:1 block_size: 8 data_offset:16 # lsblk NAMEMAJ:MIN RM SIZE RO TYPE MOUNTPOINTS ... nvme2n1 259:10 372.6G 0 disk └─bcache0 252:00 372.6G 0 disk ... kern.log: Apr 12 18:47:33 pc6a-rb3-n2 kernel: [ 2261.135332] bcache: register_bdev() registered backing device nvme2n1 Kernel versions tested: 5.19.0-38-generic #39~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC 5.15.0-69-generic #76-Ubuntu SMP --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Apr 12 18:10 seq crw-rw 1 root audio 116, 33 Apr 12 18:10 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82.3 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: CRDA: N/A CasperMD5CheckResult: unknown DistroRelease: Ubuntu 22.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: Dell Inc. PowerEdge R7525 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-38-generic root=UUID=3c0a9c0d-3f5d-4d4d-a571-37298c70a1a3 ro ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-38-generic N/A linux-backports-modules-5.19.0-38-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.12 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: jammy uec-images Uname: Linux 5.19.0-38-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 10/25/2022 dmi.bios.release: 2.10 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.10.2 dmi.board.name: 03WYW4 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.10.2:bd10/25/2022:br2.10:svnDellInc.:pnPowerEdgeR7525:pvr:rvnDellInc.:rn03WYW4:rvrA01:cvnDellInc.:ct23:cvr:skuSKU=08FF;ModelName=PowerEdgeR7525: dmi.product.family: PowerEdge dmi.product.name: PowerEdge R7525 dmi.product.sku: SKU=08FF;ModelName=PowerEdge R7525 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2016040/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2016040] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/2016040/+attachment/5663422/+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/2016040 Title: Creating bcache backing device using a Dell Ent NVMe CM6 MU 6.4TB storage fails with "cannot allocate memory" error Status in linux package in Ubuntu: Confirmed Bug description: # make-bcache -B /dev/nvme4n1 UUID: 569e90b3-cc2a-4a0e-a201-476c426a2141 Set UUID: d8d8458a-01df-481e-a7dc-e75843a9608f version:1 block_size: 1 data_offset:16 kern.log: Apr 12 18:21:56 pc6a-rb3-n2 kernel: [ 723.854659] bcache: register_bdev() error nvme4n1: cannot allocate memory Apr 12 18:21:56 pc6a-rb3-n2 kernel: [ 723.854662] bcache: register_bdev_worker() error /dev/nvme4n1: fail to register backing device Same error message is mentioned in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1909518, but the suggested configuration change does not fix the issue: # nvme id-ns /dev/nvme4n1 -n 1 -H |grep "LBA Format" [3:0] : 0x3 Current LBA Format Selected LBA Format 0 : Metadata Size: 0 bytes - Data Size: 512 bytes - Relative Performance: 0 Best LBA Format 1 : Metadata Size: 8 bytes - Data Size: 512 bytes - Relative Performance: 0 Best LBA Format 2 : Metadata Size: 0 bytes - Data Size: 1 bytes - Relative Performance: 0 Best LBA Format 3 : Metadata Size: 0 bytes - Data Size: 4096 bytes - Relative Performance: 0 Best (in use) LBA Format 4 : Metadata Size: 8 bytes - Data Size: 4096 bytes - Relative Performance: 0 Best LBA Format 5 : Metadata Size: 64 bytes - Data Size: 4096 bytes - Relative Performance: 0 Best Using a Dell Ent NVMe P5800x WI U.2 400GB storage works as expected: # make-bcache -B /dev/nvme2n1 UUID: b1405a6d-8732-4175-8aba-d67be23b3ff0 Set UUID: af6b190f-a57e-4f2b-926e-904a95268390 version:1 block_size: 8 data_offset:16 # lsblk NAMEMAJ:MIN RM SIZE RO TYPE MOUNTPOINTS ... nvme2n1 259:10 372.6G 0 disk └─bcache0 252:00 372.6G 0 disk ... kern.log: Apr 12 18:47:33 pc6a-rb3-n2 kernel: [ 2261.135332] bcache: register_bdev() registered backing device nvme2n1 Kernel versions tested: 5.19.0-38-generic #39~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC 5.15.0-69-generic #76-Ubuntu SMP --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Apr 12 18:10 seq crw-rw 1 root audio 116, 33 Apr 12 18:10 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82.3 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: CRDA: N/A CasperMD5CheckResult: unknown DistroRelease: Ubuntu 22.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: Dell Inc. PowerEdge R7525 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-38-generic root=UUID=3c0a9c0d-3f5d-4d4d-a571-37298c70a1a3 ro ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-38-generic N/A linux-backports-modules-5.19.0-38-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.12 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: jammy uec-images Uname: Linux 5.19.0-38-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 10/25/2022 dmi.bios.release: 2.10 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.10.2 dmi.board.name: 03WYW4 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.10.2:bd10/25/2022:br2.10:svnDellInc.:pnPowerEdgeR7525:pvr:rvnDellInc.:rn03WYW4:rvrA01:cvnDellInc.:ct23:cvr:skuSKU=08FF;ModelName=PowerEdgeR7525: dmi.product.family: PowerEdge dmi.product.name: PowerEdge R7525 dmi.product.sku: SKU=08FF;ModelName=PowerEdge R7525 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2016040/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2016040] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/2016040/+attachment/5663423/+files/acpidump.txt ** 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/2016040 Title: Creating bcache backing device using a Dell Ent NVMe CM6 MU 6.4TB storage fails with "cannot allocate memory" error Status in linux package in Ubuntu: Confirmed Bug description: # make-bcache -B /dev/nvme4n1 UUID: 569e90b3-cc2a-4a0e-a201-476c426a2141 Set UUID: d8d8458a-01df-481e-a7dc-e75843a9608f version:1 block_size: 1 data_offset:16 kern.log: Apr 12 18:21:56 pc6a-rb3-n2 kernel: [ 723.854659] bcache: register_bdev() error nvme4n1: cannot allocate memory Apr 12 18:21:56 pc6a-rb3-n2 kernel: [ 723.854662] bcache: register_bdev_worker() error /dev/nvme4n1: fail to register backing device Same error message is mentioned in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1909518, but the suggested configuration change does not fix the issue: # nvme id-ns /dev/nvme4n1 -n 1 -H |grep "LBA Format" [3:0] : 0x3 Current LBA Format Selected LBA Format 0 : Metadata Size: 0 bytes - Data Size: 512 bytes - Relative Performance: 0 Best LBA Format 1 : Metadata Size: 8 bytes - Data Size: 512 bytes - Relative Performance: 0 Best LBA Format 2 : Metadata Size: 0 bytes - Data Size: 1 bytes - Relative Performance: 0 Best LBA Format 3 : Metadata Size: 0 bytes - Data Size: 4096 bytes - Relative Performance: 0 Best (in use) LBA Format 4 : Metadata Size: 8 bytes - Data Size: 4096 bytes - Relative Performance: 0 Best LBA Format 5 : Metadata Size: 64 bytes - Data Size: 4096 bytes - Relative Performance: 0 Best Using a Dell Ent NVMe P5800x WI U.2 400GB storage works as expected: # make-bcache -B /dev/nvme2n1 UUID: b1405a6d-8732-4175-8aba-d67be23b3ff0 Set UUID: af6b190f-a57e-4f2b-926e-904a95268390 version:1 block_size: 8 data_offset:16 # lsblk NAMEMAJ:MIN RM SIZE RO TYPE MOUNTPOINTS ... nvme2n1 259:10 372.6G 0 disk └─bcache0 252:00 372.6G 0 disk ... kern.log: Apr 12 18:47:33 pc6a-rb3-n2 kernel: [ 2261.135332] bcache: register_bdev() registered backing device nvme2n1 Kernel versions tested: 5.19.0-38-generic #39~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC 5.15.0-69-generic #76-Ubuntu SMP --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Apr 12 18:10 seq crw-rw 1 root audio 116, 33 Apr 12 18:10 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82.3 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: CRDA: N/A CasperMD5CheckResult: unknown DistroRelease: Ubuntu 22.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: Dell Inc. PowerEdge R7525 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-38-generic root=UUID=3c0a9c0d-3f5d-4d4d-a571-37298c70a1a3 ro ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-38-generic N/A linux-backports-modules-5.19.0-38-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.12 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: jammy uec-images Uname: Linux 5.19.0-38-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 10/25/2022 dmi.bios.release: 2.10 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.10.2 dmi.board.name: 03WYW4 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.10.2:bd10/25/2022:br2.10:svnDellInc.:pnPowerEdgeR7525:pvr:rvnDellInc.:rn03WYW4:rvrA01:cvnDellInc.:ct23:cvr:skuSKU=08FF;ModelName=PowerEdgeR7525: dmi.product.family: PowerEdge dmi.product.name: PowerEdge R7525 dmi.product.sku: SKU=08FF;ModelName=PowerEdge R7525 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2016040/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://
[Kernel-packages] [Bug 2016040] Re: Creating bcache backing device using a Dell Ent NVMe CM6 MU 6.4TB storage fails with "cannot allocate memory" error
# lspci -vv |grep NVMe c1:00.0 Non-Volatile memory controller: KIOXIA Corporation NVMe SSD Controller Cx6 (rev 01) (prog-if 02 [NVM Express]) Subsystem: Dell Dell Ent NVMe CM6 MU 6.4TB [PN] Part number: Dell Ent NVMe CM6 MU 6.4TB c2:00.0 Non-Volatile memory controller: KIOXIA Corporation NVMe SSD Controller Cx6 (rev 01) (prog-if 02 [NVM Express]) Subsystem: Dell Dell Ent NVMe CM6 MU 6.4TB [PN] Part number: Dell Ent NVMe CM6 MU 6.4TB c3:00.0 Non-Volatile memory controller: Intel Corporation NVMe Datacenter SSD [Optane] (prog-if 02 [NVM Express]) Subsystem: Dell NVMe Datacenter SSD [Optane] 400GB 2.5" U.2 (P5800X) c4:00.0 Non-Volatile memory controller: Intel Corporation NVMe Datacenter SSD [Optane] (prog-if 02 [NVM Express]) Subsystem: Dell NVMe Datacenter SSD [Optane] 400GB 2.5" U.2 (P5800X) c7:00.0 Non-Volatile memory controller: KIOXIA Corporation NVMe SSD Controller Cx6 (rev 01) (prog-if 02 [NVM Express]) Subsystem: Dell Dell Ent NVMe CM6 MU 6.4TB [PN] Part number: Dell Ent NVMe CM6 MU 6.4TB c8:00.0 Non-Volatile memory controller: KIOXIA Corporation NVMe SSD Controller Cx6 (rev 01) (prog-if 02 [NVM Express]) Subsystem: Dell Dell Ent NVMe CM6 MU 6.4TB [PN] Part number: Dell Ent NVMe CM6 MU 6.4TB -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2016040 Title: Creating bcache backing device using a Dell Ent NVMe CM6 MU 6.4TB storage fails with "cannot allocate memory" error Status in linux package in Ubuntu: Confirmed Bug description: # make-bcache -B /dev/nvme4n1 UUID: 569e90b3-cc2a-4a0e-a201-476c426a2141 Set UUID: d8d8458a-01df-481e-a7dc-e75843a9608f version:1 block_size: 1 data_offset:16 kern.log: Apr 12 18:21:56 pc6a-rb3-n2 kernel: [ 723.854659] bcache: register_bdev() error nvme4n1: cannot allocate memory Apr 12 18:21:56 pc6a-rb3-n2 kernel: [ 723.854662] bcache: register_bdev_worker() error /dev/nvme4n1: fail to register backing device Same error message is mentioned in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1909518, but the suggested configuration change does not fix the issue: # nvme id-ns /dev/nvme4n1 -n 1 -H |grep "LBA Format" [3:0] : 0x3 Current LBA Format Selected LBA Format 0 : Metadata Size: 0 bytes - Data Size: 512 bytes - Relative Performance: 0 Best LBA Format 1 : Metadata Size: 8 bytes - Data Size: 512 bytes - Relative Performance: 0 Best LBA Format 2 : Metadata Size: 0 bytes - Data Size: 1 bytes - Relative Performance: 0 Best LBA Format 3 : Metadata Size: 0 bytes - Data Size: 4096 bytes - Relative Performance: 0 Best (in use) LBA Format 4 : Metadata Size: 8 bytes - Data Size: 4096 bytes - Relative Performance: 0 Best LBA Format 5 : Metadata Size: 64 bytes - Data Size: 4096 bytes - Relative Performance: 0 Best Using a Dell Ent NVMe P5800x WI U.2 400GB storage works as expected: # make-bcache -B /dev/nvme2n1 UUID: b1405a6d-8732-4175-8aba-d67be23b3ff0 Set UUID: af6b190f-a57e-4f2b-926e-904a95268390 version:1 block_size: 8 data_offset:16 # lsblk NAMEMAJ:MIN RM SIZE RO TYPE MOUNTPOINTS ... nvme2n1 259:10 372.6G 0 disk └─bcache0 252:00 372.6G 0 disk ... kern.log: Apr 12 18:47:33 pc6a-rb3-n2 kernel: [ 2261.135332] bcache: register_bdev() registered backing device nvme2n1 Kernel versions tested: 5.19.0-38-generic #39~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC 5.15.0-69-generic #76-Ubuntu SMP --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Apr 12 18:10 seq crw-rw 1 root audio 116, 33 Apr 12 18:10 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82.3 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: CRDA: N/A CasperMD5CheckResult: unknown DistroRelease: Ubuntu 22.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: Dell Inc. PowerEdge R7525 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-38-generic root=UUID=3c0a9c0d-3f5d-4d4d-a571-37298c70a1a3 ro ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-38-generic N/A linux-backports-modules-5.19.0-38-generic N/A linux-firmware
[Kernel-packages] [Bug 2016040] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/2016040/+attachment/5663420/+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/2016040 Title: Creating bcache backing device using a Dell Ent NVMe CM6 MU 6.4TB storage fails with "cannot allocate memory" error Status in linux package in Ubuntu: Confirmed Bug description: # make-bcache -B /dev/nvme4n1 UUID: 569e90b3-cc2a-4a0e-a201-476c426a2141 Set UUID: d8d8458a-01df-481e-a7dc-e75843a9608f version:1 block_size: 1 data_offset:16 kern.log: Apr 12 18:21:56 pc6a-rb3-n2 kernel: [ 723.854659] bcache: register_bdev() error nvme4n1: cannot allocate memory Apr 12 18:21:56 pc6a-rb3-n2 kernel: [ 723.854662] bcache: register_bdev_worker() error /dev/nvme4n1: fail to register backing device Same error message is mentioned in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1909518, but the suggested configuration change does not fix the issue: # nvme id-ns /dev/nvme4n1 -n 1 -H |grep "LBA Format" [3:0] : 0x3 Current LBA Format Selected LBA Format 0 : Metadata Size: 0 bytes - Data Size: 512 bytes - Relative Performance: 0 Best LBA Format 1 : Metadata Size: 8 bytes - Data Size: 512 bytes - Relative Performance: 0 Best LBA Format 2 : Metadata Size: 0 bytes - Data Size: 1 bytes - Relative Performance: 0 Best LBA Format 3 : Metadata Size: 0 bytes - Data Size: 4096 bytes - Relative Performance: 0 Best (in use) LBA Format 4 : Metadata Size: 8 bytes - Data Size: 4096 bytes - Relative Performance: 0 Best LBA Format 5 : Metadata Size: 64 bytes - Data Size: 4096 bytes - Relative Performance: 0 Best Using a Dell Ent NVMe P5800x WI U.2 400GB storage works as expected: # make-bcache -B /dev/nvme2n1 UUID: b1405a6d-8732-4175-8aba-d67be23b3ff0 Set UUID: af6b190f-a57e-4f2b-926e-904a95268390 version:1 block_size: 8 data_offset:16 # lsblk NAMEMAJ:MIN RM SIZE RO TYPE MOUNTPOINTS ... nvme2n1 259:10 372.6G 0 disk └─bcache0 252:00 372.6G 0 disk ... kern.log: Apr 12 18:47:33 pc6a-rb3-n2 kernel: [ 2261.135332] bcache: register_bdev() registered backing device nvme2n1 Kernel versions tested: 5.19.0-38-generic #39~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC 5.15.0-69-generic #76-Ubuntu SMP --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Apr 12 18:10 seq crw-rw 1 root audio 116, 33 Apr 12 18:10 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82.3 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: CRDA: N/A CasperMD5CheckResult: unknown DistroRelease: Ubuntu 22.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: Dell Inc. PowerEdge R7525 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-38-generic root=UUID=3c0a9c0d-3f5d-4d4d-a571-37298c70a1a3 ro ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-38-generic N/A linux-backports-modules-5.19.0-38-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.12 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: jammy uec-images Uname: Linux 5.19.0-38-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 10/25/2022 dmi.bios.release: 2.10 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.10.2 dmi.board.name: 03WYW4 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.10.2:bd10/25/2022:br2.10:svnDellInc.:pnPowerEdgeR7525:pvr:rvnDellInc.:rn03WYW4:rvrA01:cvnDellInc.:ct23:cvr:skuSKU=08FF;ModelName=PowerEdgeR7525: dmi.product.family: PowerEdge dmi.product.name: PowerEdge R7525 dmi.product.sku: SKU=08FF;ModelName=PowerEdge R7525 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2016040/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1788928] Re: psmouse: after sleep/suspend thinkpad touchpad not functional
*** This bug is a duplicate of bug 1786574 *** https://bugs.launchpad.net/bugs/1786574 Same issue with my Thinkpad T14 AMD Gen 1 with Ubuntu 22.04.2 Workaround so far as above - sudo modprobe -r psmouse; sudo modprobe psmouse -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1788928 Title: psmouse: after sleep/suspend thinkpad touchpad not functional Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Bug description: Summary: The touchpad after sleep/suspend of my ThinkPad X1 will not function correctly. Expected Behavior: After sleep/suspend scroll works correctly. Actual Behavior: Unable to scroll or correctly click on a window and move it without reloading the driver Steps to reproduce: 1. Install Bionic on Thinkpad X1 (4.15.0-32-generic) 2. Open something to scroll (e.g. browser, terminal, etc.) 3. Close lid 4. Re-open lid once sleeping/suspended 5. Try to scroll and note that it does not work Workaround: Run the following after re-opening the lid $ sudo modprobe psmouse -r; sudo modprobe psmouse dmesg on reload: [12753.847050] psmouse serio1: synaptics: queried max coordinates: x [..5676], y [..4758] [12753.879362] psmouse serio1: synaptics: queried min coordinates: x [1266..], y [1096..] [12753.879375] psmouse serio1: synaptics: Trying to set up SMBus access [12753.882246] psmouse serio1: synaptics: SMbus companion is not ready yet [12753.944774] psmouse serio1: synaptics: Touchpad model: 1, fw: 8.1, id: 0x1e2b1, caps: 0xf003a3/0x943300/0x12e800/0x1, board id: 3072, fw id: 1795685 [12753.944791] psmouse serio1: synaptics: serio: Synaptics pass-through port at isa0060/serio1/input0 [12753.985102] input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio1/input/input24 [12754.619594] psmouse serio5: trackpoint: IBM TrackPoint firmware: 0x0e, buttons: 3/3 [12754.823238] input: TPPS/2 IBM TrackPoint as /devices/platform/i8042/serio1/serio5/input/input25 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: powersj2506 F pulseaudio /dev/snd/controlC0: powersj2506 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=40a4eb28-4454-44f0-a377-ea611ce685bb InstallationDate: Installed on 2018-02-19 (185 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214) Lsusb: Bus 001 Device 002: ID 8087:8001 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 002: ID 04f2:b45d Chicony Electronics Co., Ltd Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20BSCTO1WW NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-32-generic root=/dev/mapper/ubuntu--vg-root ro ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-32-generic N/A linux-backports-modules-4.15.0-32-generic N/A linux-firmware 1.173.1 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: bionic Uname: Linux 4.15.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker kvm libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/13/2017 dmi.bios.vendor: LENOVO dmi.bios.version: N14ET42W (1.20 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BSCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0E50512 STD dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN14ET42W(1.20):bd09/13/2017:svnLENOVO:pn20BSCTO1WW:pvrThinkPadX1Carbon3rd:rvnLENOVO:rn20BSCTO1WW:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 3rd dmi.product.name: 20BSCTO1WW dmi.product.version: ThinkPad X1 Carbon 3rd dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788928/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009276] Re: Audio Hdmi (Radeon rx580) not recognized
*** This bug is a duplicate of bug 2009136 *** https://bugs.launchpad.net/bugs/2009136 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2009276 Title: Audio Hdmi (Radeon rx580) not recognized Status in linux-signed-hwe-5.19 package in Ubuntu: Confirmed Bug description: After kernel upgrade, from 5.19.0-32 to 5.19.0-35 the audio don't work. At boot appears the message: hdaudio_hdaudioC0D0: no AFG or MFG node found snd_hda-intel :26:00.1: no codecs initialized Processor: AMD® Ryzen 5 3600 6-core processor × 12 Graphic: AMD® Radeon rx 580 series OS Name: Ubuntu 22.04.2 LTS 64-bit GNOME version: 42.5 Graphic System: Wayland ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-35-generic 5.19.0-35.36~22.04.1 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Mar 4 19:17:19 2023 InstallationDate: Installed on 2022-05-07 (301 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-5.19 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.19/+bug/2009276/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009276] Re: Audio Hdmi (Radeon rx580) not recognized
*** This bug is a duplicate of bug 2009136 *** https://bugs.launchpad.net/bugs/2009136 I have the same problem, does someone know how to fix that? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2009276 Title: Audio Hdmi (Radeon rx580) not recognized Status in linux-signed-hwe-5.19 package in Ubuntu: Confirmed Bug description: After kernel upgrade, from 5.19.0-32 to 5.19.0-35 the audio don't work. At boot appears the message: hdaudio_hdaudioC0D0: no AFG or MFG node found snd_hda-intel :26:00.1: no codecs initialized Processor: AMD® Ryzen 5 3600 6-core processor × 12 Graphic: AMD® Radeon rx 580 series OS Name: Ubuntu 22.04.2 LTS 64-bit GNOME version: 42.5 Graphic System: Wayland ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-35-generic 5.19.0-35.36~22.04.1 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Mar 4 19:17:19 2023 InstallationDate: Installed on 2022-05-07 (301 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-5.19 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.19/+bug/2009276/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2016040] Re: Creating bcache backing device using a Dell Ent NVMe CM6 MU 6.4TB storage fails with "cannot allocate memory" error
Testing with the following kernels yields the same result: https://kernel.ubuntu.com/~kernel-ppa/mainline/v6.2.10/ https://kernel.ubuntu.com/~kernel-ppa/mainline/v6.3-rc6/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2016040 Title: Creating bcache backing device using a Dell Ent NVMe CM6 MU 6.4TB storage fails with "cannot allocate memory" error Status in linux package in Ubuntu: Confirmed Bug description: # make-bcache -B /dev/nvme4n1 UUID: 569e90b3-cc2a-4a0e-a201-476c426a2141 Set UUID: d8d8458a-01df-481e-a7dc-e75843a9608f version:1 block_size: 1 data_offset:16 kern.log: Apr 12 18:21:56 pc6a-rb3-n2 kernel: [ 723.854659] bcache: register_bdev() error nvme4n1: cannot allocate memory Apr 12 18:21:56 pc6a-rb3-n2 kernel: [ 723.854662] bcache: register_bdev_worker() error /dev/nvme4n1: fail to register backing device Same error message is mentioned in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1909518, but the suggested configuration change does not fix the issue: # nvme id-ns /dev/nvme4n1 -n 1 -H |grep "LBA Format" [3:0] : 0x3 Current LBA Format Selected LBA Format 0 : Metadata Size: 0 bytes - Data Size: 512 bytes - Relative Performance: 0 Best LBA Format 1 : Metadata Size: 8 bytes - Data Size: 512 bytes - Relative Performance: 0 Best LBA Format 2 : Metadata Size: 0 bytes - Data Size: 1 bytes - Relative Performance: 0 Best LBA Format 3 : Metadata Size: 0 bytes - Data Size: 4096 bytes - Relative Performance: 0 Best (in use) LBA Format 4 : Metadata Size: 8 bytes - Data Size: 4096 bytes - Relative Performance: 0 Best LBA Format 5 : Metadata Size: 64 bytes - Data Size: 4096 bytes - Relative Performance: 0 Best Using a Dell Ent NVMe P5800x WI U.2 400GB storage works as expected: # make-bcache -B /dev/nvme2n1 UUID: b1405a6d-8732-4175-8aba-d67be23b3ff0 Set UUID: af6b190f-a57e-4f2b-926e-904a95268390 version:1 block_size: 8 data_offset:16 # lsblk NAMEMAJ:MIN RM SIZE RO TYPE MOUNTPOINTS ... nvme2n1 259:10 372.6G 0 disk └─bcache0 252:00 372.6G 0 disk ... kern.log: Apr 12 18:47:33 pc6a-rb3-n2 kernel: [ 2261.135332] bcache: register_bdev() registered backing device nvme2n1 Kernel versions tested: 5.19.0-38-generic #39~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC 5.15.0-69-generic #76-Ubuntu SMP --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Apr 12 18:10 seq crw-rw 1 root audio 116, 33 Apr 12 18:10 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82.3 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: CRDA: N/A CasperMD5CheckResult: unknown DistroRelease: Ubuntu 22.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: Dell Inc. PowerEdge R7525 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-38-generic root=UUID=3c0a9c0d-3f5d-4d4d-a571-37298c70a1a3 ro ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-38-generic N/A linux-backports-modules-5.19.0-38-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.12 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: jammy uec-images Uname: Linux 5.19.0-38-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 10/25/2022 dmi.bios.release: 2.10 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.10.2 dmi.board.name: 03WYW4 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.10.2:bd10/25/2022:br2.10:svnDellInc.:pnPowerEdgeR7525:pvr:rvnDellInc.:rn03WYW4:rvrA01:cvnDellInc.:ct23:cvr:skuSKU=08FF;ModelName=PowerEdgeR7525: dmi.product.family: PowerEdge dmi.product.name: PowerEdge R7525 dmi.product.sku: SKU=08FF;ModelName=PowerEdge R7525 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2016040/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2008136] Re: netfilter: flowtable: add counter support in HW offload
** Description changed: * Explain the bug(s) While conntrack tuples are offloaded to hardware and conntrack packet accounting is enabled, offloaded packets aren't counted. * Brief explanation of fixes Cherry-pick. No adaptation. First commit for SW, second commit of HW offloaded rules. ef803b3cf96a netfilter: flowtable: add counter support in HW offload 9312eabab4a6 netfilter: conntrack: add nf_ct_acct_add() note: need to change a little due to cherry-pick conflict with 24384e28586c netfilter: flowtable: Set offload timeouts according to proto values * How to test Create OVS bridge with 2 devices mlx5 rep devices. Enable HW offload and configure regular connection tracking OpenFlow rules: e.g: ovs-ofctl del-flows br-ovs ovs-ofctl add-flow br-ovs arp,actions=normal ovs-ofctl add-flow br-ovs "table=0, ip,ct_state=-trk actions=ct(table=1)" ovs-ofctl add-flow br-ovs "table=1, ip,ct_state=+trk+new actions=ct(commit),normal" ovs-ofctl add-flow br-ovs "table=1, ip,ct_state=+trk+est, actions=normal" Run a TCP connection, e.g: on mlx5 VF1 iperf -s on mlx5 VF2 iperf -c -t 10 Optional: In different terminal, while traffic is running, check for offload: tcpdump -nnepi tcp and see no iperf tcp packets. Dump conntrack with relevant ip: + echo "1" > /proc/sys/net/netfilter/nf_conntrack_acct cat /proc/net/nf_conntrack | grep -i See counters (packets=.*) advancing while tuples were offloaded: ipv4 2 tcp 6 src=1.1.1.2 dst=1.1.1.3 sport=56394 dport=5001 packets=2 bytes=112 src=1.1.1.3 dst=1.1.1.2 sport=5001 dport=56394 packets=1777 bytes=665340 [HW_OFFLOAD] mark=0 zone=0 use=3 * What it could break. Nothing. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/2008136 Title: netfilter: flowtable: add counter support in HW offload Status in linux-bluefield package in Ubuntu: New Status in linux-bluefield source package in Focal: Fix Committed Bug description: * Explain the bug(s) While conntrack tuples are offloaded to hardware and conntrack packet accounting is enabled, offloaded packets aren't counted. * Brief explanation of fixes Cherry-pick. No adaptation. First commit for SW, second commit of HW offloaded rules. ef803b3cf96a netfilter: flowtable: add counter support in HW offload 9312eabab4a6 netfilter: conntrack: add nf_ct_acct_add() note: need to change a little due to cherry-pick conflict with 24384e28586c netfilter: flowtable: Set offload timeouts according to proto values * How to test Create OVS bridge with 2 devices mlx5 rep devices. Enable HW offload and configure regular connection tracking OpenFlow rules: e.g: ovs-ofctl del-flows br-ovs ovs-ofctl add-flow br-ovs arp,actions=normal ovs-ofctl add-flow br-ovs "table=0, ip,ct_state=-trk actions=ct(table=1)" ovs-ofctl add-flow br-ovs "table=1, ip,ct_state=+trk+new actions=ct(commit),normal" ovs-ofctl add-flow br-ovs "table=1, ip,ct_state=+trk+est, actions=normal" Run a TCP connection, e.g: on mlx5 VF1 iperf -s on mlx5 VF2 iperf -c -t 10 Optional: In different terminal, while traffic is running, check for offload: tcpdump -nnepi tcp and see no iperf tcp packets. Dump conntrack with relevant ip: echo "1" > /proc/sys/net/netfilter/nf_conntrack_acct cat /proc/net/nf_conntrack | grep -i See counters (packets=.*) advancing while tuples were offloaded: ipv4 2 tcp 6 src=1.1.1.2 dst=1.1.1.3 sport=56394 dport=5001 packets=2 bytes=112 src=1.1.1.3 dst=1.1.1.2 sport=5001 dport=56394 packets=1777 bytes=665340 [HW_OFFLOAD] mark=0 zone=0 use=3 * What it could break. Nothing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2008136/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1988711] Re: Update Broadcom Emulex FC HBA lpfc driver to 14.2.0.5
Hi Laurie,
This update is in the Kinetic (5.19) kernel. It has not made it into
Jammy 5.15 yet.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1988711
Title:
Update Broadcom Emulex FC HBA lpfc driver to 14.2.0.5
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Jammy:
In Progress
Status in linux source package in Kinetic:
Fix Released
Bug description:
[IMPACT/Justification]
There are numerous bug fixes included in the more recent version of lpfc That
Broadcom has asked to pull into Jammy and Kinetic to better support customers
in the field who are using the GA kernel and cant or wont move to the HWE
kernels. These all are limited to the lpfc driver itself, no patches to core
code are requested.
[FIX]
A few of these were already landed in Jammy, and all but 6 (ones landed in
6.0 upstream) were already in Kinetic.
b3d11f195cbb scsi: lpfc: Copyright updates for 14.2.0.5 patches
71faf8d30fdb scsi: lpfc: Update lpfc version to 14.2.0.5
b21c9deb1479 scsi: lpfc: Refactor lpfc_nvmet_prep_abort_wqe() into
lpfc_sli_prep_abort_xri()
ffc566411ade scsi: lpfc: Revert RSCN_MEMENTO workaround for misbehaved
configuration
ea92e173dc55 scsi: lpfc: Fix lost NVMe paths during LIF bounce stress test
2f67dc7970bc scsi: lpfc: Fix possible memory leak when failing to issue CMF
WQE
0948a9c53860 scsi: lpfc: Remove extra atomic_inc on cmd_pending in
queuecommand after VMID
35251b4d79db scsi: lpfc: Set PU field when providing D_ID in
XMIT_ELS_RSP64_CX iocb
f8191d40aa61 scsi: lpfc: Prevent buffer overflow crashes in debugfs with
malformed user input
4ecc9b0271a7 scsi: lpfc: Fix uninitialized cqe field in
lpfc_nvme_cancel_iocb()
1af48fffd7ff scsi: lpfc: Update lpfc version to 14.2.0.4
2e7e9c0c1ec0 scsi: lpfc: Allow reduced polling rate for
nvme_admin_async_event cmd completion
ea7bd1f39331 scsi: lpfc: Add more logging of cmd and cqe information for
aborted NVMe cmds
336d63615466 scsi: lpfc: Fix port stuck in bypassed state after LIP in PT2PT
topology
b1b3440f437b scsi: lpfc: Resolve NULL ptr dereference after an ELS LOGO is
aborted
6f808bd78e82 scsi: lpfc: Address NULL pointer dereference after
starget_to_rport()
e27f05147bff scsi: lpfc: Resolve some cleanup issues following SLI path
refactoring
24e1f056677e scsi: lpfc: Resolve some cleanup issues following abort path
refactoring
44ba9786b673 scsi: lpfc: Correct BDE type for XMIT_SEQ64_WQE in
lpfc_ct_reject_event()
a5b168efba21 scsi: lpfc: Add support for ATTO Fibre Channel devices
348efeca7487 scsi: lpfc: Rework lpfc_vmid_get_appid() to be protocol
independent
ed913cf4a533 scsi: lpfc: Commonize VMID code location
fcb9e738667c scsi: lpfc: Update lpfc version to 14.2.0.3
a14396b6d139 scsi: lpfc: Use sg_dma_address() and sg_dma_len() macros for
NVMe I/O
e6f510414502 scsi: lpfc: Alter FPIN stat accounting logic
de3ec318fee3 scsi: lpfc: Rework FDMI initialization after link up
5099478e436f scsi: lpfc: Change VMID registration to be based on fabric
parameters
dc8a71bd414f scsi: lpfc: Decrement outstanding gidft_inp counter if
lpfc_err_lost_link()
4a0f4aff3ce5 scsi: lpfc: Use list_for_each_entry_safe() in
rscn_recovery_check()
596fc8adb171 scsi: lpfc: Fix dmabuf ptr assignment in lpfc_ct_reject_event()
ead76d4c09b8 scsi: lpfc: Inhibit aborts if external loopback plug is inserted
b7e952cbc63c scsi: lpfc: Fix ndlp put following a LOGO completion
ba3d58a1df46 scsi: lpfc: Fill in missing ndlp kref puts in error paths
84c6f99e3907 scsi: lpfc: Fix element offset in __lpfc_sli_release_iocbq_s4()
775266207105 scsi: lpfc: Correct BDE DMA address assignment for GEN_REQ_WQE
cc28fac16ab7 scsi: lpfc: Fix split code for FLOGI on FCoE
c2024e3b33ee scsi: lpfc: Remove redundant lpfc_sli_prep_wqe() call
92bd903da12b scsi: lpfc: Fix additional reference counting in
lpfc_bsg_rport_els()
db05628435aa blk-cgroup: move blkcg_{get,set}_fc_appid out of line
646db1a560f4 scsi: lpfc: Fix resource leak in lpfc_sli4_send_seq_to_ulp()
3d1d34ec1fbc scsi: lpfc: Remove unnecessary null ndlp check in
lpfc_sli_prep_wqe()
a346f28ad231 scsi: lpfc: Remove unneeded variable
66c20a97367a scsi: lpfc: Copyright updates for 14.2.0.2 patches
4af4d0e2ea94 scsi: lpfc: Update lpfc version to 14.2.0.2
fd4a0c6da5c1 scsi: lpfc: Expand setting ELS_ID field in ELS_REQUEST64_WQE
f4fbf4acaa50 scsi: lpfc: Update stat accounting for READ_STATUS mbox command
ef47575fd982 scsi: lpfc: Refactor cleanup of mailbox commands
d51cf5bd926c scsi: lpfc: Fix field overload in lpfc_iocbq data structure
1045592fc968 scsi: lpfc: Introduce FC_RSCN_MEMENTO flag for tracking post
RSCN completion
6c983d327b9e scsi: lpfc: Register for Application Services FC-4 type in
Fabric topology
6c8a3ce64b2c scsi: lpfc: Remove false FDMI NVMe FC-4 support for NPIV ports
c364c453d30a sc
[Kernel-packages] [Bug 2016040] Re: Creating bcache backing device using a Dell Ent NVMe CM6 MU 6.4TB storage fails with "cannot allocate memory" error
Works as expected with Ubuntu 20.04, kernel 5.4.0-146-generic # make-bcache -B /dev/nvme4n1 UUID: c2422b08-d969-4d6c-8922-f35509719146 Set UUID: 035df7a9-13b8-4309-83d9-65263e95b338 version:1 block_size: 1 data_offset:16 # lsblk NAMEMAJ:MIN RM SIZE RO TYPE MOUNTPOINT ... nvme4n1 259:60 5.8T 0 disk └─bcache0 252:00 5.8T 0 disk ... kern.log: Apr 13 00:39:56 ... kernel: [ 718.192424] bcache: register_bdev() registered backing device nvme4n1 # lsb_release -r Release:20.04 # uname -r 5.4.0-146-generic ** Description changed: # make-bcache -B /dev/nvme4n1 UUID: 569e90b3-cc2a-4a0e-a201-476c426a2141 Set UUID: d8d8458a-01df-481e-a7dc-e75843a9608f version:1 block_size: 1 data_offset:16 kern.log: - Apr 12 18:21:56 pc6a-rb3-n2 kernel: [ 723.854659] bcache: register_bdev() error nvme4n1: cannot allocate memory - Apr 12 18:21:56 pc6a-rb3-n2 kernel: [ 723.854662] bcache: register_bdev_worker() error /dev/nvme4n1: fail to register backing device + Apr 12 18:21:56 ... kernel: [ 723.854659] bcache: register_bdev() error nvme4n1: cannot allocate memory + Apr 12 18:21:56 ... kernel: [ 723.854662] bcache: register_bdev_worker() error /dev/nvme4n1: fail to register backing device Same error message is mentioned in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1909518, but the suggested configuration change does not fix the issue: # nvme id-ns /dev/nvme4n1 -n 1 -H |grep "LBA Format" - [3:0] : 0x3 Current LBA Format Selected + [3:0] : 0x3 Current LBA Format Selected LBA Format 0 : Metadata Size: 0 bytes - Data Size: 512 bytes - Relative Performance: 0 Best LBA Format 1 : Metadata Size: 8 bytes - Data Size: 512 bytes - Relative Performance: 0 Best LBA Format 2 : Metadata Size: 0 bytes - Data Size: 1 bytes - Relative Performance: 0 Best LBA Format 3 : Metadata Size: 0 bytes - Data Size: 4096 bytes - Relative Performance: 0 Best (in use) LBA Format 4 : Metadata Size: 8 bytes - Data Size: 4096 bytes - Relative Performance: 0 Best LBA Format 5 : Metadata Size: 64 bytes - Data Size: 4096 bytes - Relative Performance: 0 Best Using a Dell Ent NVMe P5800x WI U.2 400GB storage works as expected: # make-bcache -B /dev/nvme2n1 UUID: b1405a6d-8732-4175-8aba-d67be23b3ff0 Set UUID: af6b190f-a57e-4f2b-926e-904a95268390 version:1 block_size: 8 data_offset:16 # lsblk NAMEMAJ:MIN RM SIZE RO TYPE MOUNTPOINTS ... nvme2n1 259:10 372.6G 0 disk └─bcache0 252:00 372.6G 0 disk ... kern.log: - Apr 12 18:47:33 pc6a-rb3-n2 kernel: [ 2261.135332] bcache: register_bdev() registered backing device nvme2n1 + Apr 12 18:47:33 ... kernel: [ 2261.135332] bcache: register_bdev() registered backing device nvme2n1 Kernel versions tested: 5.19.0-38-generic #39~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC 5.15.0-69-generic #76-Ubuntu SMP - --- + --- ProblemType: Bug AlsaDevices: - total 0 - crw-rw 1 root audio 116, 1 Apr 12 18:10 seq - crw-rw 1 root audio 116, 33 Apr 12 18:10 timer + total 0 + crw-rw 1 root audio 116, 1 Apr 12 18:10 seq + crw-rw 1 root audio 116, 33 Apr 12 18:10 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82.3 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: CRDA: N/A CasperMD5CheckResult: unknown DistroRelease: Ubuntu 22.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: Dell Inc. PowerEdge R7525 Package: linux (not installed) PciMultimedia: - + ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - LANG=C.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + LANG=C.UTF-8 + SHELL=/bin/bash ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-38-generic root=UUID=3c0a9c0d-3f5d-4d4d-a571-37298c70a1a3 ro ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 RelatedPackageVersions: - linux-restricted-modules-5.19.0-38-generic N/A - linux-backports-modules-5.19.0-38-generic N/A - linux-firmware 20220329.git681281e4-0ubuntu3.12 + linux-restricted-modules-5.19.0-38-generic N/A + linux-backports-modules-5.19.0-38-generic N/A + linux-firmware 20220329.git681281e4-0ubuntu3.12 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: jammy uec-images Uname: Linux 5.19.0-38-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date:
[Kernel-packages] [Bug 2008136] Re: netfilter: flowtable: add counter support in HW offload
** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/2008136 Title: netfilter: flowtable: add counter support in HW offload Status in linux-bluefield package in Ubuntu: New Status in linux-bluefield source package in Focal: Fix Committed Bug description: * Explain the bug(s) While conntrack tuples are offloaded to hardware and conntrack packet accounting is enabled, offloaded packets aren't counted. * Brief explanation of fixes Cherry-pick. No adaptation. First commit for SW, second commit of HW offloaded rules. ef803b3cf96a netfilter: flowtable: add counter support in HW offload 9312eabab4a6 netfilter: conntrack: add nf_ct_acct_add() note: need to change a little due to cherry-pick conflict with 24384e28586c netfilter: flowtable: Set offload timeouts according to proto values * How to test Create OVS bridge with 2 devices mlx5 rep devices. Enable HW offload and configure regular connection tracking OpenFlow rules: e.g: ovs-ofctl del-flows br-ovs ovs-ofctl add-flow br-ovs arp,actions=normal ovs-ofctl add-flow br-ovs "table=0, ip,ct_state=-trk actions=ct(table=1)" ovs-ofctl add-flow br-ovs "table=1, ip,ct_state=+trk+new actions=ct(commit),normal" ovs-ofctl add-flow br-ovs "table=1, ip,ct_state=+trk+est, actions=normal" Run a TCP connection, e.g: on mlx5 VF1 iperf -s on mlx5 VF2 iperf -c -t 10 Optional: In different terminal, while traffic is running, check for offload: tcpdump -nnepi tcp and see no iperf tcp packets. Dump conntrack with relevant ip: echo "1" > /proc/sys/net/netfilter/nf_conntrack_acct cat /proc/net/nf_conntrack | grep -i See counters (packets=.*) advancing while tuples were offloaded: ipv4 2 tcp 6 src=1.1.1.2 dst=1.1.1.3 sport=56394 dport=5001 packets=2 bytes=112 src=1.1.1.3 dst=1.1.1.2 sport=5001 dport=56394 packets=1777 bytes=665340 [HW_OFFLOAD] mark=0 zone=0 use=3 * What it could break. Nothing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2008136/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1988711] Re: Update Broadcom Emulex FC HBA lpfc driver to 14.2.0.5
Michael, that is the same status we’ve had for quite some time now.
On Wed, Apr 12, 2023 at 8:06 PM Michael Reed <1988...@bugs.launchpad.net>
wrote:
> Hi Laurie,
>
> This update is in the Kinetic (5.19) kernel. It has not made it into
> Jammy 5.15 yet.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1988711
>
> Title:
> Update Broadcom Emulex FC HBA lpfc driver to 14.2.0.5
>
> Status in linux package in Ubuntu:
> In Progress
> Status in linux source package in Jammy:
> In Progress
> Status in linux source package in Kinetic:
> Fix Released
>
> Bug description:
> [IMPACT/Justification]
> There are numerous bug fixes included in the more recent version of lpfc
> That Broadcom has asked to pull into Jammy and Kinetic to better support
> customers in the field who are using the GA kernel and cant or wont move to
> the HWE kernels. These all are limited to the lpfc driver itself, no
> patches to core code are requested.
>
> [FIX]
> A few of these were already landed in Jammy, and all but 6 (ones landed
> in 6.0 upstream) were already in Kinetic.
>
> b3d11f195cbb scsi: lpfc: Copyright updates for 14.2.0.5 patches
> 71faf8d30fdb scsi: lpfc: Update lpfc version to 14.2.0.5
> b21c9deb1479 scsi: lpfc: Refactor lpfc_nvmet_prep_abort_wqe() into
> lpfc_sli_prep_abort_xri()
> ffc566411ade scsi: lpfc: Revert RSCN_MEMENTO workaround for misbehaved
> configuration
> ea92e173dc55 scsi: lpfc: Fix lost NVMe paths during LIF bounce stress
> test
> 2f67dc7970bc scsi: lpfc: Fix possible memory leak when failing to issue
> CMF WQE
> 0948a9c53860 scsi: lpfc: Remove extra atomic_inc on cmd_pending in
> queuecommand after VMID
> 35251b4d79db scsi: lpfc: Set PU field when providing D_ID in
> XMIT_ELS_RSP64_CX iocb
> f8191d40aa61 scsi: lpfc: Prevent buffer overflow crashes in debugfs with
> malformed user input
> 4ecc9b0271a7 scsi: lpfc: Fix uninitialized cqe field in
> lpfc_nvme_cancel_iocb()
> 1af48fffd7ff scsi: lpfc: Update lpfc version to 14.2.0.4
> 2e7e9c0c1ec0 scsi: lpfc: Allow reduced polling rate for
> nvme_admin_async_event cmd completion
> ea7bd1f39331 scsi: lpfc: Add more logging of cmd and cqe information for
> aborted NVMe cmds
> 336d63615466 scsi: lpfc: Fix port stuck in bypassed state after LIP in
> PT2PT topology
> b1b3440f437b scsi: lpfc: Resolve NULL ptr dereference after an ELS LOGO
> is aborted
> 6f808bd78e82 scsi: lpfc: Address NULL pointer dereference after
> starget_to_rport()
> e27f05147bff scsi: lpfc: Resolve some cleanup issues following SLI path
> refactoring
> 24e1f056677e scsi: lpfc: Resolve some cleanup issues following abort
> path refactoring
> 44ba9786b673 scsi: lpfc: Correct BDE type for XMIT_SEQ64_WQE in
> lpfc_ct_reject_event()
> a5b168efba21 scsi: lpfc: Add support for ATTO Fibre Channel devices
> 348efeca7487 scsi: lpfc: Rework lpfc_vmid_get_appid() to be protocol
> independent
> ed913cf4a533 scsi: lpfc: Commonize VMID code location
> fcb9e738667c scsi: lpfc: Update lpfc version to 14.2.0.3
> a14396b6d139 scsi: lpfc: Use sg_dma_address() and sg_dma_len() macros
> for NVMe I/O
> e6f510414502 scsi: lpfc: Alter FPIN stat accounting logic
> de3ec318fee3 scsi: lpfc: Rework FDMI initialization after link up
> 5099478e436f scsi: lpfc: Change VMID registration to be based on fabric
> parameters
> dc8a71bd414f scsi: lpfc: Decrement outstanding gidft_inp counter if
> lpfc_err_lost_link()
> 4a0f4aff3ce5 scsi: lpfc: Use list_for_each_entry_safe() in
> rscn_recovery_check()
> 596fc8adb171 scsi: lpfc: Fix dmabuf ptr assignment in
> lpfc_ct_reject_event()
> ead76d4c09b8 scsi: lpfc: Inhibit aborts if external loopback plug is
> inserted
> b7e952cbc63c scsi: lpfc: Fix ndlp put following a LOGO completion
> ba3d58a1df46 scsi: lpfc: Fill in missing ndlp kref puts in error paths
> 84c6f99e3907 scsi: lpfc: Fix element offset in
> __lpfc_sli_release_iocbq_s4()
> 775266207105 scsi: lpfc: Correct BDE DMA address assignment for
> GEN_REQ_WQE
> cc28fac16ab7 scsi: lpfc: Fix split code for FLOGI on FCoE
> c2024e3b33ee scsi: lpfc: Remove redundant lpfc_sli_prep_wqe() call
> 92bd903da12b scsi: lpfc: Fix additional reference counting in
> lpfc_bsg_rport_els()
> db05628435aa blk-cgroup: move blkcg_{get,set}_fc_appid out of line
> 646db1a560f4 scsi: lpfc: Fix resource leak in lpfc_sli4_send_seq_to_ulp()
> 3d1d34ec1fbc scsi: lpfc: Remove unnecessary null ndlp check in
> lpfc_sli_prep_wqe()
> a346f28ad231 scsi: lpfc: Remove unneeded variable
> 66c20a97367a scsi: lpfc: Copyright updates for 14.2.0.2 patches
> 4af4d0e2ea94 scsi: lpfc: Update lpfc version to 14.2.0.2
> fd4a0c6da5c1 scsi: lpfc: Expand setting ELS_ID field in ELS_REQUEST64_WQE
> f4fbf4acaa50 scsi: lpfc: Update stat accounting for READ_STATUS mbox
> command
> ef47575fd982 scsi: lpfc: Refactor cleanup of mailbox commands
> d51cf5bd926c scsi: lpfc: Fix field overload in lpfc_iocbq d
[Kernel-packages] [Bug 2015972] Re: Dell: Enable speaker mute hotkey LED indicator
** Changed in: linux-oem-6.1 (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux-oem-6.1 (Ubuntu Jammy) Assignee: (unassigned) => koba (kobako) ** Changed in: linux (Ubuntu Jammy) Status: Incomplete => In Progress ** Changed in: linux (Ubuntu Kinetic) Status: Incomplete => In Progress ** Changed in: linux (Ubuntu Lunar) Status: Incomplete => In Progress ** Changed in: linux (Ubuntu Jammy) Assignee: (unassigned) => koba (kobako) ** Changed in: linux (Ubuntu Kinetic) Assignee: (unassigned) => koba (kobako) ** Changed in: linux (Ubuntu Lunar) Assignee: (unassigned) => koba (kobako) ** Tags added: oem-priority originate-from-2004439 somerville -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2015972 Title: Dell: Enable speaker mute hotkey LED indicator Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.1 package in Ubuntu: New Status in linux source package in Jammy: In Progress Status in linux-oem-6.1 source package in Jammy: In Progress Status in linux source package in Kinetic: In Progress Status in linux-oem-6.1 source package in Kinetic: New Status in linux source package in Lunar: In Progress Status in linux-oem-6.1 source package in Lunar: New Bug description: [Feature Description] When users press the speaker mute hotkey and the speaker is muted, the speaker mute LED indicator will light up. When the speaker is not muted, the speaker mute LED indicator will light out. [Test Case] 1. run G16 with target kernel. 2. press the mute hotkey 3. check if speaker mute led can be switched. [Where problems could occur] Low, just register a speaker mute led control for dell-laptop. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2015972/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2015670] Re: [r8169] Kernel loop PCIe Bus Error on RTL810xE
Can you please attach `sudo lspci -vvnn`? ** Changed in: linux (Ubuntu) Status: Confirmed => 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/2015670 Title: [r8169] Kernel loop PCIe Bus Error on RTL810xE Status in linux package in Ubuntu: Incomplete Bug description: Kernel loop after login This happens with both kernels 6.2.0-18 and 6.2.0-19 on 2 different partitions of same PC: Partition installed from beta and partition from ISO dated 04/02. No problem on same PC different partitions of same disk with Ubuntu Focal, Jammy and Kinetic Problem does not occur with kernel 5.19.17-051917-generic installed from https://kernel.ubuntu.com/~kernel-ppa/mainline/ Adding journalctl -b related to the problem note: I opened another bug for this problem blaming gnome-shell but it's wrong https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2015540 ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: linux-image-6.2.0-19-generic 6.2.0-19.19 ProcVersionSignature: Ubuntu 6.2.0-19.19-generic 6.2.6 Uname: Linux 6.2.0-19-generic x86_64 ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: corrado1511 F wireplumber /dev/snd/seq:corrado1508 F pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Apr 9 09:33:06 2023 InstallationDate: Installed on 2023-04-07 (1 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Daily amd64 (20230402) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0bda:5520 Realtek Semiconductor Corp. Integrated_Webcam_HD Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications Bus 001 Device 002: ID 145f:02b5 Trust Trust Wireless Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 3793 ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-19-generic root=UUID=78239576-b8af-4c66-bf15-8d5ee9a63d35 ro quiet splash RelatedPackageVersions: linux-restricted-modules-6.2.0-19-generic N/A linux-backports-modules-6.2.0-19-generic N/A linux-firmware20230323.gitbcdcfbcf-0ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/17/2019 dmi.bios.release: 1.5 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.0 dmi.board.name: 0C1PF2 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.0:bd12/17/2019:br1.5:svnDellInc.:pnInspiron3793:pvr:rvnDellInc.:rn0C1PF2:rvrA00:cvnDellInc.:ct10:cvr:sku097A: dmi.product.family: Inspiron dmi.product.name: Inspiron 3793 dmi.product.sku: 097A dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2015670/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2013325] Re: net:cmsg_time.sh in ubuntu_kernel_selftests failed on RISCV64 kernels (TXTIME rel returned '', expected 'OK')
lunar/linux-riscv/6.2.0-19.19.1 Case ICMPv4 - TXTIME rel returned '', expected 'OK' Case RAWv4 - TXTIME rel returned '', expected 'OK' Case UDPv6 - TXTIME rel returned '', expected 'OK' Case ICMPv6 - TXTIME rel returned '', expected 'OK' Case RAWv6 - TXTIME rel returned '', expected 'OK' ** Tags added: 6.2 lunar -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-allwinner in Ubuntu. https://bugs.launchpad.net/bugs/2013325 Title: net:cmsg_time.sh in ubuntu_kernel_selftests failed on RISCV64 kernels (TXTIME rel returned '', expected 'OK') Status in ubuntu-kernel-tests: New Status in linux-allwinner package in Ubuntu: New Status in linux-riscv package in Ubuntu: New Status in linux-starfive package in Ubuntu: New Status in linux-allwinner source package in Kinetic: New Status in linux-riscv source package in Kinetic: New Status in linux-starfive source package in Kinetic: New Bug description: Issue found on Kinetic 5.19 RISCV kernels: * kinetic/linux-allwinner/5.19.0-1009.9 # selftests: net: cmsg_time.sh # Case UDPv4 - TXTIME rel returned '', expected 'OK' # Case ICMPv4 - TXTIME rel returned '', expected 'OK' # Case UDPv6 - TXTIME rel returned '', expected 'OK' # Case ICMPv6 - TXTIME rel returned '', expected 'OK' # Case RAWv6 - TXTIME rel returned '', expected 'OK' # FAIL - 5/36 cases failed not ok 1 selftests: net: cmsg_time.sh # exit=1 * kinetic/linux-riscv/5.19.0-1015.16 # selftests: net: cmsg_time.sh # Case ICMPv4 - TXTIME rel returned '', expected 'OK' # Case UDPv6 - TXTIME rel returned '', expected 'OK' # Case ICMPv6 - TXTIME rel returned '', expected 'OK' # Case RAWv6 - TXTIME rel returned '', expected 'OK' # FAIL - 4/36 cases failed not ok 1 selftests: net: cmsg_time.sh # exit=1 * kinetic/linux-starfive/5.19.0-1014.16 # selftests: net: cmsg_time.sh # Case UDPv4 - TXTIME rel returned '', expected 'OK' # Case ICMPv4 - TXTIME rel returned '', expected 'OK' # Case UDPv6 - TXTIME rel returned '', expected 'OK' # Case ICMPv6 - TXTIME rel returned '', expected 'OK' # Case RAWv6 - TXTIME rel returned '', expected 'OK' # FAIL - 5/36 cases failed not ok 1 selftests: net: cmsg_time.sh # exit=1 This is only affecting RISCV64 kernels, it does not affect kinetic generic kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2013325/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1956562] Re: 5.15 kernel selftest srv6_end_dt4_l3vpn_test.sh failure
With Lunar 6.2 RISCV, there are just 4 failures in SRv6 VPN connectivity test: # TEST: Hosts connectivity: hs-t100-1 -> hs-t100-2 (tenant 100) [FAIL] # # TEST: Hosts connectivity: hs-t100-2 -> hs-t100-1 (tenant 100) [FAIL] # # TEST: Hosts connectivity: hs-t200-3 -> hs-t200-4 (tenant 200) [FAIL] # # TEST: Hosts connectivity: hs-t200-4 -> hs-t200-3 (tenant 200) [FAIL] All tests in IPv6 routers connectivity test have passed without any issue. ** Tags added: 6.2 riscv -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1956562 Title: 5.15 kernel selftest srv6_end_dt4_l3vpn_test.sh failure Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Jammy: Confirmed Status in linux source package in Kinetic: New Bug description: Script srv6_end_dt4_l3vpn_test.sh reports the following failure (upstream issue). With Jammy 5.15: # ### # TEST SECTION: IPv6 routers connectivity test # ### # # TEST: Routers connectivity: rt-1 -> rt-2 [FAIL] # # TEST: Routers connectivity: rt-2 -> rt-1 [FAIL] # ### # TEST SECTION: SRv6 VPN connectivity test among hosts in the same tenant # ### # # TEST: Hosts connectivity: hs-t100-1 -> hs-t100-2 (tenant 100) [FAIL] # # TEST: Hosts connectivity: hs-t100-2 -> hs-t100-1 (tenant 100) [FAIL] # # TEST: Hosts connectivity: hs-t200-3 -> hs-t200-4 (tenant 200) [FAIL] # # TEST: Hosts connectivity: hs-t200-4 -> hs-t200-3 (tenant 200) [FAIL] # With Kinetic 5.19: # ### # TEST SECTION: IPv6 routers connectivity test # ### # # TEST: Routers connectivity: rt-1 -> rt-2 [FAIL] # # TEST: Routers connectivity: rt-2 -> rt-1 [ OK ] # # TEST SECTION: SRv6 VPN connectivity test among hosts in the same tenant # ### # # TEST: Hosts connectivity: hs-t100-1 -> hs-t100-2 (tenant 100) [FAIL] # # TEST: Hosts connectivity: hs-t100-2 -> hs-t100-1 (tenant 100) [FAIL] # # TEST: Hosts connectivity: hs-t200-3 -> hs-t200-4 (tenant 200) [FAIL] # # TEST: Hosts connectivity: hs-t200-4 -> hs-t200-3 (tenant 200) [FAIL] # To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1956562/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2013114] Re: The panel get blank for too long after disconnecting dock with monitors
** Tags removed: verification-needed-jammy ** Tags added: verification-done-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2013114 Title: The panel get blank for too long after disconnecting dock with monitors Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.1 source package in Jammy: Fix Committed Bug description: [Impact] Connect 2 or more external monitors via type-C docking station, the dp-mst function is working correctly. However, after unplugging the docking station, the internal display seems to freeze for more than 5 seconds to get back with normal display. [Fix] Intel release a fix to abort the DP AUX transfer on a disconnected TC port. It prevent the DP to stuck in a unexpected long retry. [Test] Connect external monitors to the type-C port on the system. Make sure external monitor display OK then unplug the dock. The internal panel should not stay in blank for more than 10 seconds. [Where problems could occur] The long AUX transfer timeout and retry are meaningless on a disconnected sink. Should be no risk for regression. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2013114/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2016036] [NEW] [radeon] HDMI port doesn't work
You have been subscribed to a public bug: hello ubuntu developer i have a strict bug in latest version of ubuntu which make my hdmi port unable to connect to monitors or tv and need to disconnect the hdmi and power off and power on laptop again and when everything is up connect the hdmi to work probably and even reset doesn't work for it and this problem is exist on stackoverflow where i learned i should power of to solve the problem ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Apr 12 21:37:13 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company 3rd Gen Core processor Graphics Controller [103c:194d] Advanced Micro Devices, Inc. [AMD/ATI] Mars [Radeon HD 8670A/8670M/8750M / R7 M370] [1002:6600] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Mars [Radeon HD 8670A/8670M/8750M / R7 M370] [103c:194d] InstallationDate: Installed on 2023-03-23 (20 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) MachineType: Hewlett-Packard HP ProBook 450 G0 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-38-generic root=UUID=0c5a4433-24e9-49cb-8f3e-abeb93f03066 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/11/2019 dmi.bios.release: 15.112 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68IRF Ver. F.70 dmi.board.name: 194B dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 90.0F dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.ec.firmware.release: 144.15 dmi.modalias: dmi:bvnHewlett-Packard:bvr68IRFVer.F.70:bd04/11/2019:br15.112:efr144.15:svnHewlett-Packard:pnHPProBook450G0:pvrA2018CD200:rvnHewlett-Packard:rn194B:rvrKBCVersion90.0F:cvnHewlett-Packard:ct10:cvr:skuC5F33AV#AB4: dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=PRO dmi.product.name: HP ProBook 450 G0 dmi.product.sku: C5F33AV#AB4 dmi.product.version: A2018CD200 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.9 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: linux-hwe-5.19 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug dualgpu hybrid i915 jammy radeon ubuntu wayland-session -- [radeon] HDMI port doesn't work https://bugs.launchpad.net/bugs/2016036 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.19 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 2016036] Re: hdmi port
** Tags added: dualgpu hybrid i915 radeon ** Summary changed: - hdmi port + [radeon] HDMI port doesn't work ** Package changed: xorg (Ubuntu) => linux-hwe-5.19 (Ubuntu) ** Summary changed: - [radeon] HDMI port doesn't work + [HP ProBook 450 G0][radeon] HDMI port doesn't work -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2016036 Title: [HP ProBook 450 G0][radeon] HDMI port doesn't work Status in linux-hwe-5.19 package in Ubuntu: New Bug description: hello ubuntu developer i have a strict bug in latest version of ubuntu which make my hdmi port unable to connect to monitors or tv and need to disconnect the hdmi and power off and power on laptop again and when everything is up connect the hdmi to work probably and even reset doesn't work for it and this problem is exist on stackoverflow where i learned i should power of to solve the problem ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Apr 12 21:37:13 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company 3rd Gen Core processor Graphics Controller [103c:194d] Advanced Micro Devices, Inc. [AMD/ATI] Mars [Radeon HD 8670A/8670M/8750M / R7 M370] [1002:6600] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Mars [Radeon HD 8670A/8670M/8750M / R7 M370] [103c:194d] InstallationDate: Installed on 2023-03-23 (20 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) MachineType: Hewlett-Packard HP ProBook 450 G0 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-38-generic root=UUID=0c5a4433-24e9-49cb-8f3e-abeb93f03066 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/11/2019 dmi.bios.release: 15.112 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68IRF Ver. F.70 dmi.board.name: 194B dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 90.0F dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.ec.firmware.release: 144.15 dmi.modalias: dmi:bvnHewlett-Packard:bvr68IRFVer.F.70:bd04/11/2019:br15.112:efr144.15:svnHewlett-Packard:pnHPProBook450G0:pvrA2018CD200:rvnHewlett-Packard:rn194B:rvrKBCVersion90.0F:cvnHewlett-Packard:ct10:cvr:skuC5F33AV#AB4: dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=PRO dmi.product.name: HP ProBook 450 G0 dmi.product.sku: C5F33AV#AB4 dmi.product.version: A2018CD200 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.9 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.19/+bug/2016036/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2015670] Re: [r8169] Kernel loop PCIe Bus Error on RTL810xE
corrado@corrado-n8-ll-0402:~$ sudo lspci -vvnn 00:00.0 Host bridge [0600]: Intel Corporation Ice Lake-LP Processor Host Bridge/DRAM Registers [8086:8a12] (rev 03) Subsystem: Dell Ice Lake-LP Processor Host Bridge/DRAM Registers [1028:097a] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: icl_uncore 00:02.0 VGA compatible controller [0300]: Intel Corporation Iris Plus Graphics G1 (Ice Lake) [8086:8a56] (rev 07) (prog-if 00 [VGA controller]) DeviceName: To Be Filled by O.E.M. Subsystem: Dell Iris Plus Graphics G1 (Ice Lake) [1028:097a] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Capabilities: [70] Express (v2) Root Complex Integrated Endpoint, MSI 00 DevCap: MaxPayload 128 bytes, PhantFunc 0 ExtTag- RBE+ FLReset+ DevCtl: CorrErr- NonFatalErr- FatalErr- UnsupReq- RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop- FLReset- MaxPayload 128 bytes, MaxReadReq 128 bytes DevSta: CorrErr- NonFatalErr- FatalErr- UnsupReq- AuxPwr- TransPend- DevCap2: Completion Timeout: Not Supported, TimeoutDis- NROPrPrP- LTR- 10BitTagComp- 10BitTagReq- OBFF Not Supported, ExtFmt- EETLPPrefix- EmergencyPowerReduction Not Supported, EmergencyPowerReductionInit- FRS- AtomicOpsCap: 32bit- 64bit- 128bitCAS- DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis- LTR- 10BitTagReq- OBFF Disabled, AtomicOpsCtl: ReqEn- Capabilities: [ac] MSI: Enable+ Count=1/1 Maskable+ 64bit- Address: fee00018 Data: Masking: Pending: Capabilities: [d0] Power Management version 2 Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Capabilities: [100 v1] Process Address Space ID (PASID) PASIDCap: Exec- Priv-, Max PASID Width: 14 PASIDCtl: Enable- Exec- Priv- Capabilities: [200 v1] Address Translation Service (ATS) ATSCap: Invalidate Queue Depth: 00 ATSCtl: Enable-, Smallest Translation Unit: 00 Capabilities: [300 v1] Page Request Interface (PRI) PRICtl: Enable- Reset- PRISta: RF- UPRGI- Stopped+ Page Request Capacity: 8000, Page Request Allocation: Kernel driver in use: i915 Kernel modules: i915 00:04.0 Signal processing controller [1180]: Intel Corporation Processor Power and Thermal Controller [8086:8a03] (rev 03) Subsystem: Dell Processor Power and Thermal Controller [1028:097a] Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: proc_thermal Kernel modules: processor_thermal_device_pci_legacy 00:14.0 USB controller [0c03]: Intel Corporation Ice Lake-LP USB 3.1 xHCI Host Controller [8086:34ed] (rev 30) (prog-if 30 [XHCI]) Subsystem: Dell Ice Lake-LP USB 3.1 xHCI Host Controller [1028:097a] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- Kernel driver in use: xhci_hcd Kernel modules: xhci_pci 00:14.2 RAM memory [0500]: Intel Corporation Ice Lake-LP DRAM Controller [8086:34ef] (rev 30) Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- Kernel driver in use: intel-lpss Kernel modules: intel_lpss_pci 00:15.1 Serial bus controller [0c80]: Intel Corporation Ice Lake-LP Serial IO I2C Controller #1 [8086:34e9] (rev 30) Subsystem: Dell Ice Lake-LP Serial IO I2C Controller [1028:097a] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: intel-lpss Kernel modules: intel_lpss_pci 00:16.0 Communication controller [0780]: Intel Corporation Ice Lake-LP Management Engine [8086:34e0] (rev 30) Subsystem: Dell Ice Lake-LP Management Engine [1028:097a] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGAS
[Kernel-packages] [Bug 2011389] Re: vmd may fail to create sysfs entry while `pci_rescan_bus()` called in some other drivers like wwan
verified. ** Tags removed: verification-needed-jammy ** Tags added: verification-done-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.0 in Ubuntu. https://bugs.launchpad.net/bugs/2011389 Title: vmd may fail to create sysfs entry while `pci_rescan_bus()` called in some other drivers like wwan Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.0 source package in Jammy: Won't Fix Status in linux-oem-6.1 source package in Jammy: Fix Committed Status in linux source package in Lunar: In Progress Status in linux-oem-6.0 source package in Lunar: Invalid Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [SRU Justification] [Impact] With wwan t7xx driver patched, vmd may fail the probe process because it does not lock properly. [Fix] https://lore.kernel.org/linux- pci/20230313173733.1815277-1-vicamo.y...@canonical.com/T/#u [Test Case] Verify on platforms with FM350 wwan module with prebuilt oem-6.1 or above kernels. No vmd probe error should be found in dmesg. [Where problems could occur] This is the way it should have been done. [Other Info] This is not reproducible with v6.0 or older kernels, so only Lunar and oem-6.1 are nominated for fix. OEM-6.0 patch goes to Gerrit instead. == original bug report == vmd may fail to create sysfs entry while `pci_rescan_bus()` called in some other drivers like wwan. This happens after bug 2002089 re-added pci rescan feature back to wwan t7xx driver to support firmware updates via devlink. t7xx may call `pci_rescan_bus()` with proper locks, but vmd doesn't. sysfs: cannot create duplicate filename '/devices/.../resource0' Call Trace: sysfs_warn_dup.cold+0x17/0x34 sysfs_add_bin_file_mode_ns+0xc0/0xf0 sysfs_create_bin_file+0x6d/0xb0 pci_create_attr+0x117/0x260 pci_create_resource_files+0x6b/0x150 pci_create_sysfs_dev_files+0x18/0x30 pci_bus_add_device+0x30/0x80 pci_bus_add_devices+0x31/0x80 pci_bus_add_devices+0x5b/0x80 vmd_enable_domain.constprop.0+0x6b7/0x880 [vmd] vmd_probe+0x16d/0x193 [vmd] To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2011389/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2012730] Re: lspci can't show physical slot on 22.04
Hi Ubuntu team, After about 3 weeks, do you have any update about this issue? Thanks! Aaron -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/2012730 Title: lspci can't show physical slot on 22.04 Status in linux-hwe-5.15 package in Ubuntu: New Bug description: On 22.04 with ga-5.15-generic kernel the lspci -vvv can get physical slot info, but it works on 5.4.0 kernel of 20.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.15/+bug/2012730/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
