[Kernel-packages] [Bug 1960605] Re: System freeze
** Package changed: ubuntu => linux-hwe-5.13 (Ubuntu) ** Also affects: nvidia-graphics-drivers-470 (Ubuntu) Importance: Undecided Status: New ** Changed in: nvidia-graphics-drivers-470 (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1960605 Title: System freeze Status in linux-hwe-5.13 package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-470 package in Ubuntu: Incomplete Bug description: When booting the system, sometimes the system freezes (HP logo, Ubuntu logo and stopped rotating symbol), and can't do anything not even ping the system. After zero or a few re-try's I get to the login screen. It is then possible to log in via ssh from another system. Everything looks OK. Then I can select the user give her password and then one of two things happens. one: Ubuntu starts and works OK. two: the system freezes (black screen) and nothing works not even the ssh session. I've tried looking at syslog and other files, but can't make any sense of it. I also attached the last lines of the syslog wich ended in a crash/hangup. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.13.0-28.31~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-28-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 470.86 Tue Oct 26 21:55:45 UTC 2021 GCC version: ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Errno 13] Toegang geweigerd: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Feb 11 10:29:20 2022 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a day GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Since a couple weeks or more GraphicsCard: Intel Corporation UHD Graphics [8086:9bc4] (rev 05) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:8745] NVIDIA Corporation Device [10de:1f95] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:8745] InstallationDate: Installed on 2021-12-04 (69 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: HP HP Pavilion Gaming Laptop 17-cd1xxx ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=nl_NL.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-28-generic root=UUID=84ab800e-9239-453f-8f4a-dc7e4377e5ad ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/08/2021 dmi.bios.release: 15.21 dmi.bios.vendor: Insyde dmi.bios.version: F.21 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8745 dmi.board.vendor: HP dmi.board.version: 03.34 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 3.34 dmi.modalias: dmi:bvnInsyde:bvrF.21:bd01/08/2021:br15.21:efr3.34:svnHP:pnHPPavilionGamingLaptop17-cd1xxx:pvrType1ProductConfigId:rvnHP:rn8745:rvr03.34:cvnHP:ct10:cvrChassisVersion:sku1C4U6EA#ABH: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Gaming Laptop 17-cd1xxx dmi.product.sku: 1C4U6EA#ABH dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.5 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3~20.04.5 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.13/+bug/1960605/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to :
[Kernel-packages] [Bug 1960605] [NEW] System freeze
You have been subscribed to a public bug: When booting the system, sometimes the system freezes (HP logo, Ubuntu logo and stopped rotating symbol), and can't do anything not even ping the system. After zero or a few re-try's I get to the login screen. It is then possible to log in via ssh from another system. Everything looks OK. Then I can select the user give her password and then one of two things happens. one: Ubuntu starts and works OK. two: the system freezes (black screen) and nothing works not even the ssh session. I've tried looking at syslog and other files, but can't make any sense of it. I also attached the last lines of the syslog wich ended in a crash/hangup. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.13.0-28.31~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-28-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 470.86 Tue Oct 26 21:55:45 UTC 2021 GCC version: ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Errno 13] Toegang geweigerd: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Feb 11 10:29:20 2022 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a day GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Since a couple weeks or more GraphicsCard: Intel Corporation UHD Graphics [8086:9bc4] (rev 05) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:8745] NVIDIA Corporation Device [10de:1f95] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:8745] InstallationDate: Installed on 2021-12-04 (69 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: HP HP Pavilion Gaming Laptop 17-cd1xxx ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=nl_NL.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-28-generic root=UUID=84ab800e-9239-453f-8f4a-dc7e4377e5ad ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/08/2021 dmi.bios.release: 15.21 dmi.bios.vendor: Insyde dmi.bios.version: F.21 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8745 dmi.board.vendor: HP dmi.board.version: 03.34 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 3.34 dmi.modalias: dmi:bvnInsyde:bvrF.21:bd01/08/2021:br15.21:efr3.34:svnHP:pnHPPavilionGamingLaptop17-cd1xxx:pvrType1ProductConfigId:rvnHP:rn8745:rvr03.34:cvnHP:ct10:cvrChassisVersion:sku1C4U6EA#ABH: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Gaming Laptop 17-cd1xxx dmi.product.sku: 1C4U6EA#ABH dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.5 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3~20.04.5 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: linux-hwe-5.13 (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: amd64 apport-bug focal freeze nvidia ubuntu -- System freeze https://bugs.launchpad.net/bugs/1960605 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.13 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 1963919] Re: fbtft overlay is missing
** Also affects: linux-raspi (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-raspi2 (Ubuntu) Status: New => Won't Fix ** Changed in: linux-raspi (Ubuntu) Importance: Undecided => Wishlist ** Tags added: kern-2643 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1963919 Title: fbtft overlay is missing Status in linux-raspi package in Ubuntu: New Status in linux-raspi2 package in Ubuntu: Won't Fix Bug description: To attach TFT touchscreens the pi-foundation kernel ships the fbtft devicetree overlay along with rpi-display. While you can attach a stand-alone TFT display just fine when only using rpi-display to provide the drivers with hardcoded GPIO assignments, it gets extremely tricky to even enable the touchscreen input or to use such a TFT with other sensors attached since rpi- display does not allow any re-assignment of the GPIO pins in use. The upstream fbtft driver can make use of the already included rpi-display drivers by defining "rpi-display" in its params. It also allows to freely re-assign the GPIO pins for backlight, D/C and Reset to give you enough flexibility to have the display co-exist with any attached sensors and touch input devices that do not have the ability to re-assign GPIO pins and that clash with the hardcoded numbering of rpi-display. An example with freely assigned GPIOs can be seen in the upstream (rpi-foundation) overlay README file at: https://github.com/raspberrypi/firmware/blob/master/boot/overlays/README#L884 Please include fbtft in the ubuntu kernels to allow a more flexible usage of SPI based TFT touchscreens on the Pi. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1963919/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1955882] Re: MT7921[14c3:7961] ASPM is disabled and it affects power consumption
** Tags added: originate-from-1961591 sutton -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1955882 Title: MT7921[14c3:7961] ASPM is disabled and it affects power consumption Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.14 source package in Focal: In Progress Status in linux source package in Jammy: In Progress Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: [Impact] MT7921 is disabled by default, and it affects the power consumption. [Fix] MTK pointed out we need this commit which is included in v5.16-rc1 bf3747ae2e25 mt76: mt7921: enable aspm by default After ASPM is enabled, we found the card disappears after reboot sometimes, so MTK provides another commit for it https://patchwork.kernel.org/project/linux-mediatek/patch/70e27cbc652cbdb78277b9c691a3a5ba02653afb.1641540175.git.obj...@gmail.com/ [Test] Verified on Dell machines with MT7921 wifi card. [Where problems could occur] Enable device ASPM is always risky, we've done our best to test these patches, and no regression could be found. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1955882/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1956461] Re: Creative HD720p webcam doesn't work
Interestingly, I looked deeper and even before I wrote the comment above, the patch had already been added to the 5.10 and 5.15 stable trees. It seems that for some reason it wasn't added to the 5.4 tree. Weird...I wonder if it doesn't cleanly apply or something. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1956461 Title: Creative HD720p webcam doesn't work Status in linux package in Ubuntu: Confirmed Bug description: After installing kernel 5.4.0-92 the webcam Creative HD720p stop to be seen by the system. There is no /dev/vl4/ folder --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: piotr 3094 F pulseaudio /dev/snd/controlC0: piotr 3094 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20.2 InstallationDate: Installed on 2020-06-07 (578 days ago) InstallationMedia: Linux Mint 19.3 "Tricia" - Release amd64 20191213 IwConfig: enp3s0no wireless extensions. lono wireless extensions. MachineType: Gigabyte Technology Co., Ltd. H67MA-USB3-B3 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-92-generic root=UUID=3bdaa7b0-765c-41ce-b67a-deeeabde9c42 ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-92.103-generic 5.4.157 RelatedPackageVersions: linux-restricted-modules-5.4.0-92-generic N/A linux-backports-modules-5.4.0-92-generic N/A linux-firmware1.187.24 RfKill: Tags: uma Uname: Linux 5.4.0-92-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 10/27/2011 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F4 dmi.board.name: H67MA-USB3-B3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF4:bd10/27/2011:svnGigabyteTechnologyCo.,Ltd.:pnH67MA-USB3-B3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnH67MA-USB3-B3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: H67MA-USB3-B3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956461/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1879345] Re: probe event parser error log check in ftrace from ubuntu_kernel_selftests failed on F-OEM-5.6
OEM 5.6 EOL ** Changed in: ubuntu-kernel-tests Status: New => Won't Fix ** Changed in: linux-oem-5.6 (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1879345 Title: probe event parser error log check in ftrace from ubuntu_kernel_selftests failed on F-OEM-5.6 Status in ubuntu-kernel-tests: Won't Fix Status in linux-oem-5.6 package in Ubuntu: Won't Fix Bug description: $ sudo ./ftracetest test.d/kprobe/kprobe_syntax_errors.tc === Ftrace unit tests === [1] Kprobe event parser error log check [FAIL] # of passed: 0 # of failed: 1 # of unresolved: 0 # of untested: 0 # of unsupported: 0 # of xfailed: 0 # of undefined(test bug): 0 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.6.0-1010-oem 5.6.0-1010.10 ProcVersionSignature: User Name 5.6.0-1010.10-oem 5.6.8 Uname: Linux 5.6.0-1010-oem x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon May 18 15:21:01 2020 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-oem-5.6 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1879345/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1916237] Re: Compiling kernel with clang-11 and lld-10 lead to segfault
[Expired for llvm-toolchain-11 (Ubuntu) because there has been no activity for 60 days.] ** Changed in: llvm-toolchain-11 (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to llvm-toolchain-11 in Ubuntu. https://bugs.launchpad.net/bugs/1916237 Title: Compiling kernel with clang-11 and lld-10 lead to segfault Status in llvm-toolchain-11 package in Ubuntu: Expired Bug description: I have installed "clang clang-11 llvm llvm-11 lld-11 lld" on an Ubuntu focal. Then switched to clang-11 via: update-alternatives --install /usr/bin/clang clang /usr/bin/clang-11 100 Compiling a 5.4 kernel lead to: Stack dump: 0.Program arguments: ld.lld -m elf_x86_64 -z max-page-size=0x20 --emit-relocs --discard-none --build-id --strip-debug -o .tmp_vmlinux.kallsyms1 -T ./arch/x86/kernel/vmlinux.lds --whole-archive arch/x86/kernel/head_64.o arch/x86/kernel/head64.o arch/x86/kernel/ebda.o arch/x86/kernel/platform-quirks.o init/built-in.a usr/built-in.a arch/x86/built-in.a kernel/built-in.a certs/built-in.a mm/built-in.a fs/built-in.a ipc/built-in.a security/built-in.a crypto/built-in.a block/built-in.a lib/built-in.a arch/x86/lib/built-in.a drivers/built-in.a sound/built-in.a arch/x86/pci/built-in.a arch/x86/power/built-in.a arch/x86/video/built-in.a net/built-in.a virt/built-in.a --no-whole-archive --start-group lib/lib.a arch/x86/lib/lib.a --end-group #0 0x7f1ae78be4ff llvm::sys::PrintStackTrace(llvm::raw_ostream&) (/lib/x86_64-linux-gnu/libLLVM-10.so.1+0x9814ff) #1 0x7f1ae78bc7b0 llvm::sys::RunSignalHandlers() (/lib/x86_64-linux-gnu/libLLVM-10.so.1+0x97f7b0) #2 0x7f1ae78beac5 (/lib/x86_64-linux-gnu/libLLVM-10.so.1+0x981ac5) #3 0x7f1aeb5e63c0 __restore_rt (/lib/x86_64-linux-gnu/libpthread.so.0+0x153c0) #4 0x7f1ae787e8fd llvm::Twine::printOneChild(llvm::raw_ostream&, llvm::Twine::Child, llvm::Twine::NodeKind) const (/lib/x86_64-linux-gnu/libLLVM-10.so.1+0x9418fd) #5 0x7f1ae787e69f (/lib/x86_64-linux-gnu/libLLVM-10.so.1+0x94169f) #6 0x7f1ae787e537 llvm::Twine::str[abi:cxx11]() const (/lib/x86_64-linux-gnu/libLLVM-10.so.1+0x941537) #7 0x005df47b (/usr/lib/llvm-10/bin/lld+0x5df47b) #8 0x00528ea8 (/usr/lib/llvm-10/bin/lld+0x528ea8) #9 0x005224cb (/usr/lib/llvm-10/bin/lld+0x5224cb) #10 0x004b7a71 (/usr/lib/llvm-10/bin/lld+0x4b7a71) #11 0x004adf44 (/usr/lib/llvm-10/bin/lld+0x4adf44) #12 0x004ac539 (/usr/lib/llvm-10/bin/lld+0x4ac539) #13 0x0042734a (/usr/lib/llvm-10/bin/lld+0x42734a) #14 0x7f1ae6a270b3 __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x270b3) #15 0x00426b4e (/usr/lib/llvm-10/bin/lld+0x426b4e) Segmentation fault (core dumped) make[1]: *** [/buildbot/5_4_amd64/build/ghelper/linux-5.4/Makefile:1100: vmlinux] Error 139 Removing packages "lld llvm lld-10 llvm-10" and doing manually symlink ln -s ld.lld-11 ld.lld and doing the same for llvm-ar llvm-nm llvm-objcopy llvm-objdump llvm-readelf lead to a successfull build. That's unfortunate that there are no update-alternative for llvm/lld To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/llvm-toolchain-11/+bug/1916237/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1910863] Re: Clang 11 crash on Ubuntu 20.10: sorry, this include generates a translation unit too large for Clang to process.
[Expired for llvm-toolchain-11 (Ubuntu) because there has been no activity for 60 days.] ** Changed in: llvm-toolchain-11 (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to llvm-toolchain-11 in Ubuntu. https://bugs.launchpad.net/bugs/1910863 Title: Clang 11 crash on Ubuntu 20.10: sorry, this include generates a translation unit too large for Clang to process. Status in llvm-toolchain-11 package in Ubuntu: Expired Bug description: clang11 provided by ubuntu on 20.10 crashes on some C++ code with the message: sorry, this include generates a translation unit too large for Clang to process. Installing clang-11 from llvm fixes the issue. This issue occur only on 20.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/llvm-toolchain-11/+bug/1910863/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1955644] Re: AMD GPU driver warning found in log after crash
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1955644 Title: AMD GPU driver warning found in log after crash Status in linux package in Ubuntu: Expired Bug description: With new Kubuntu 21.10 installation I experienced instabilities of my work system (when letting the system run over night, at morning the system had rebooted by itself and asks for disk encryption password). I had a look into the kernel log and I found an incident that may be related to the instability. Anyway there seems to be something going wrong. I have attached the log snippet as a text file. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2021-12-18 (19 days ago) InstallationMedia: Kubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: ASUS System Product Name NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-23-generic root=/dev/mapper/vgkubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.13.0-23.23-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-23-generic N/A linux-backports-modules-5.13.0-23-generic N/A linux-firmware 1.201.3 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: impish Uname: Linux 5.13.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/09/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2423 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX B550-E GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2423:bd08/09/2021:br5.17:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXB550-EGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1955644/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1955882] Re: MT7921[14c3:7961] ASPM is disabled and it affects power consumption
** Description changed: [Impact] MT7921 is disabled by default, and it affects the power consumption. [Fix] MTK pointed out we need this commit which is included in v5.16-rc1 -bf3747ae2e25 mt76: mt7921: enable aspm by default + bf3747ae2e25 mt76: mt7921: enable aspm by default + After ASPM is enabled, we found the card disappears after reboot sometimes, so MTK provides another commit for it + https://patchwork.kernel.org/project/linux-mediatek/patch/70e27cbc652cbdb78277b9c691a3a5ba02653afb.1641540175.git.obj...@gmail.com/ [Test] Verified on Dell machines with MT7921 wifi card. [Where problems could occur] - Enable device ASPM is always risky, but MT7921 is a rather new device, - and MTK submitted the patch at June, so it should be safe to enable ASPM - on this new device and there is no follow up fixes commit after ASPM is enabled. + Enable device ASPM is always risky, we've done our best to test these patches, and no regression could be found. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1955882 Title: MT7921[14c3:7961] ASPM is disabled and it affects power consumption Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.14 source package in Focal: In Progress Status in linux source package in Jammy: In Progress Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: [Impact] MT7921 is disabled by default, and it affects the power consumption. [Fix] MTK pointed out we need this commit which is included in v5.16-rc1 bf3747ae2e25 mt76: mt7921: enable aspm by default After ASPM is enabled, we found the card disappears after reboot sometimes, so MTK provides another commit for it https://patchwork.kernel.org/project/linux-mediatek/patch/70e27cbc652cbdb78277b9c691a3a5ba02653afb.1641540175.git.obj...@gmail.com/ [Test] Verified on Dell machines with MT7921 wifi card. [Where problems could occur] Enable device ASPM is always risky, we've done our best to test these patches, and no regression could be found. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1955882/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1962799] Re: Bad items from Powertop on oem kernel
@acelan, Cause we want to drop the tlp package, so we hope that these values could be default in kernel. Thanks! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1962799 Title: Bad items from Powertop on oem kernel Status in OEM Priority Project: New Status in linux-oem package in Ubuntu: New Bug description: On Jaguar2, we found some items are bad from powertop, could we set them 'Good' by default from oem kernel, so that we could save more power consumption. System info "ThinkPad X1 Yoga Gen 7", "BIOS": "N3AET52W (1.17 ) 02/21/2022", CPU": "12th Gen Intel(R) Core(TM) i5-1235U", VGA: [8086:46a8], Kernel: 5.14.0-1024-oem Power Consumption === The idle-screen-on-residency-check/cpu-low-power-idle/system-low-power-idle passed. Default value and the value after set all ‘Good’ in powertop ShortIdle: 5.5W, 5W LongIdle: 1.8W, 2W S2Idle: 0.6W, 0.6W Bad items === * VM writeback timeout (echo ‘1500’ > /proc/sys/vm/dirty_writeback_centisecs) * Should we turn off the NMI watchdog for the OEM kernel? It prompt“NMI watchdog should be turned off” (/proc/sys/kernel/nmi_watchdog) * Runtime PM for I2C Adapter i2c-[2-10] (i915 gmbus tc[1-6]/dp[a-c])? By default these values are ‘on’, should we set it to ‘auto’? (/sys/bus/i2c/devices/i2c-2/device/power/control) * Runtime PM for PCI Device Intel Corporation Device [4601,46a8,461d,464f,51a4,51f0,5182,51ed,51ef,51fc]? Host bridge,VGA controller,Signal processing controller,System peripheral,Serial bus controller,Network Controller,ISA bridge,USB controller,RAM memory,Serial controller. (/sys/bus/pci/devices/:00:00.0/power/control) * Runtime PM for PCI Device MEDIATEK Corp. Device 4d75 * Runtime PM for PCI Device Samsung Electronics Co Ltd Device a80a * Autosuspend for USB device USB Bridge [MCHP]? (/sys/bus/usb/devices/3-8/power/control) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1962799/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1940485] Re: thermald often limits CPU frequency while on AC
I've been most recently running on git commit 2fc02bbf3a654c4e56fae51518f9983733ccd776, which would be slightly after 2.4.8. I see that we've got a new thermald version (2.4.7) in the archive. I shall re-enable the system thermald and see if I can still reproduce. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1940485 Title: thermald often limits CPU frequency while on AC Status in thermald package in Ubuntu: In Progress Bug description: I'm not entirely sure if this is a thermald issue, but on my laptop (Dell XPS 15" 2-in-1) I find that the CPU frequency, under load on AC, is often throttled to 2.5GHz rather than the base 3.1GHz or 3.8GHz turbo frequency. Restarting thermald (with `systemctl restart thermald`) will let the system scale up to the expected ~3.8GHz boost frequency. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: thermald 2.4.6-1 ProcVersionSignature: Ubuntu 5.11.0-20.21+21.10.1-generic 5.11.21 Uname: Linux 5.11.0-20-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu67 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Aug 19 09:24:56 2021 InstallationDate: Installed on 2021-06-26 (53 days ago) InstallationMedia: Ubuntu 21.10.0 2021.05.28 amd64 "bcachefs" (20210622) SourcePackage: thermald UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1940485/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1962799] Re: Bad items from Powertop on oem kernel
All those values could be set by tlp, it's not related to kernel. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1962799 Title: Bad items from Powertop on oem kernel Status in OEM Priority Project: New Status in linux-oem package in Ubuntu: New Bug description: On Jaguar2, we found some items are bad from powertop, could we set them 'Good' by default from oem kernel, so that we could save more power consumption. System info "ThinkPad X1 Yoga Gen 7", "BIOS": "N3AET52W (1.17 ) 02/21/2022", CPU": "12th Gen Intel(R) Core(TM) i5-1235U", VGA: [8086:46a8], Kernel: 5.14.0-1024-oem Power Consumption === The idle-screen-on-residency-check/cpu-low-power-idle/system-low-power-idle passed. Default value and the value after set all ‘Good’ in powertop ShortIdle: 5.5W, 5W LongIdle: 1.8W, 2W S2Idle: 0.6W, 0.6W Bad items === * VM writeback timeout (echo ‘1500’ > /proc/sys/vm/dirty_writeback_centisecs) * Should we turn off the NMI watchdog for the OEM kernel? It prompt“NMI watchdog should be turned off” (/proc/sys/kernel/nmi_watchdog) * Runtime PM for I2C Adapter i2c-[2-10] (i915 gmbus tc[1-6]/dp[a-c])? By default these values are ‘on’, should we set it to ‘auto’? (/sys/bus/i2c/devices/i2c-2/device/power/control) * Runtime PM for PCI Device Intel Corporation Device [4601,46a8,461d,464f,51a4,51f0,5182,51ed,51ef,51fc]? Host bridge,VGA controller,Signal processing controller,System peripheral,Serial bus controller,Network Controller,ISA bridge,USB controller,RAM memory,Serial controller. (/sys/bus/pci/devices/:00:00.0/power/control) * Runtime PM for PCI Device MEDIATEK Corp. Device 4d75 * Runtime PM for PCI Device Samsung Electronics Co Ltd Device a80a * Autosuspend for USB device USB Bridge [MCHP]? (/sys/bus/usb/devices/3-8/power/control) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1962799/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1940485] Re: thermald often limits CPU frequency while on AC
@Chris, which upstream version did you use? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1940485 Title: thermald often limits CPU frequency while on AC Status in thermald package in Ubuntu: In Progress Bug description: I'm not entirely sure if this is a thermald issue, but on my laptop (Dell XPS 15" 2-in-1) I find that the CPU frequency, under load on AC, is often throttled to 2.5GHz rather than the base 3.1GHz or 3.8GHz turbo frequency. Restarting thermald (with `systemctl restart thermald`) will let the system scale up to the expected ~3.8GHz boost frequency. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: thermald 2.4.6-1 ProcVersionSignature: Ubuntu 5.11.0-20.21+21.10.1-generic 5.11.21 Uname: Linux 5.11.0-20-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu67 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Aug 19 09:24:56 2021 InstallationDate: Installed on 2021-06-26 (53 days ago) InstallationMedia: Ubuntu 21.10.0 2021.05.28 amd64 "bcachefs" (20210622) SourcePackage: thermald UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1940485/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1940485] Re: thermald often limits CPU frequency while on AC
Sorry about the late reply. I do not exactly know how to reproduce this behaviour, so I've been consistently running upstream thermald and collecting the logs while using the laptop normally. Unfortunately, I have not observed this behaviour with the upstream thermald, so I can't get the requested logs. It's possible that the upstream code contains a fix for whatever my problem is? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1940485 Title: thermald often limits CPU frequency while on AC Status in thermald package in Ubuntu: In Progress Bug description: I'm not entirely sure if this is a thermald issue, but on my laptop (Dell XPS 15" 2-in-1) I find that the CPU frequency, under load on AC, is often throttled to 2.5GHz rather than the base 3.1GHz or 3.8GHz turbo frequency. Restarting thermald (with `systemctl restart thermald`) will let the system scale up to the expected ~3.8GHz boost frequency. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: thermald 2.4.6-1 ProcVersionSignature: Ubuntu 5.11.0-20.21+21.10.1-generic 5.11.21 Uname: Linux 5.11.0-20-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu67 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Aug 19 09:24:56 2021 InstallationDate: Installed on 2021-06-26 (53 days ago) InstallationMedia: Ubuntu 21.10.0 2021.05.28 amd64 "bcachefs" (20210622) SourcePackage: thermald UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1940485/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1964035] Re: no image on monitor on laptop with two graphics card (onboard intel+nvidia rtx3050) if run nvidia only
** Also affects: xorg (Ubuntu) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-510 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-hwe-5.13 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.8 in Ubuntu. https://bugs.launchpad.net/bugs/1964035 Title: no image on monitor on laptop with two graphics card (onboard intel+nvidia rtx3050) if run nvidia only Status in linux-hwe-5.13 package in Ubuntu: New Status in linux-signed-hwe-5.8 package in Ubuntu: New Status in nvidia-graphics-drivers-510 package in Ubuntu: New Status in xorg package in Ubuntu: New Bug description: i have laptop (Vendor:MSI / Model:Katana GF76 11UC) with two graphics card (onboard intel+nvidia rtx3050) I didn't like how intel (i915) works (flickering problem has not yet been overcome) so I decided to try using nvidia only. I spent a long time dealing with the "xorg" settings in order to run "x" on nvidia only: * disable the i915 driver with kernel settings: `modprobe.blacklist=i915 i915.modeset=0` * rename /usr/share/X11/xorg.conf.d/20-intel.conf to *.bak * then modify /usr/share/X11/xorg.conf.d/10-nvidia.conf (set Identifier "Card0" ) after starting startx on the screen, the image freezes when switching to tty2 and back to tty1, the server does not render anything, and if you open `top` in tty2, you can see: ``` MiB Mem : 31808,1 total, 24998,2 free, 5471,6 used, 1338,3 buff/cache MiB Swap:954,0 total,954,0 free, 0,0 used. 25914,7 avail Mem PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 2547 root 20 0 2880328 156160 86076 R 100,3 0,5 6:19.96 kwin_x11 3033 hetman20 0 3052116 350728 186196 S 1,0 1,1 0:06.43 firefox 3314 hetman20 0 2477080 140688 93056 S 1,0 0,4 0:01.23 Isolated Web Co 306 root 20 0 0 0 0 I 0,3 0,0 0:00.36 kworker/6:2-events 776 message+ 20 09044 6032 3828 S 0,3 0,0 0:01.62 dbus-daemon 801 root 20 0 16852 7828 6892 S 0,3 0,0 0:00.17 systemd-logind 2967 hetman20 0 5771360 4,4g 124548 S 0,3 14,1 2:04.60 plasmashell 3000 hetman20 0 340504 63760 50732 S 0,3 0,2 0:00.37 kwalletd5 3207 hetman20 0 2427008 110324 89080 S 0,3 0,3 0:00.30 Privileged Cont 3607 root 20 0 0 0 0 I 0,3 0,0 0:00.03 kworker/u24:2-events_power_efficient ``` nvidia-smi ``` hetman@katana-lin:/mnt/giga/xorg_nvidia$ cat mvidia-smi.log Mon Mar 7 23:03:53 2022 +-+ | NVIDIA-SMI 510.47.03Driver Version: 510.47.03CUDA Version: 11.6 | |---+--+--+ | GPU NamePersistence-M| Bus-IdDisp.A | Volatile Uncorr. ECC | | Fan Temp Perf Pwr:Usage/Cap| Memory-Usage | GPU-Util Compute M. | | | | MIG M. | |===+==+==| | 0 NVIDIA GeForce ... Off | :01:00.0 Off | N/A | | N/A 41CP8N/A / N/A |132MiB / 4096MiB | 0% Default | | | | N/A | +---+--+--+ +-+ | Processes: | | GPU GI CIPID Type Process name GPU Memory | |ID ID Usage | |=| |0 N/A N/A 2847 G /usr/lib/xorg/Xorg 12MiB | |0 N/A N/A 2967 G /usr/bin/plasmashell8MiB | |0 N/A N/A 3033 G /usr/lib/firefox/firefox 85MiB | |0 N/A N/A 4436 G ...bexec/kscreenlocker_greet 12MiB | +-+ ``` Thus, I stated that the X's started up and are working, but the image is not displayed. if return modprobe i915.modeset=1 /usr/share/X11/xorg.conf.d/20-intel.conf /usr/share/X11/xorg.conf.d/10-nvidia.conf - otherwise the output always goes through only intel (i915) nvidia not uses even if use `prime-select nvidia` - this option ignoring -
[Kernel-packages] [Bug 1964035] [NEW] no image on monitor on laptop with two graphics card (onboard intel+nvidia rtx3050) if run nvidia only
Public bug reported: i have laptop (Vendor:MSI / Model:Katana GF76 11UC) with two graphics card (onboard intel+nvidia rtx3050) I didn't like how intel (i915) works (flickering problem has not yet been overcome) so I decided to try using nvidia only. I spent a long time dealing with the "xorg" settings in order to run "x" on nvidia only: * disable the i915 driver with kernel settings: `modprobe.blacklist=i915 i915.modeset=0` * rename /usr/share/X11/xorg.conf.d/20-intel.conf to *.bak * then modify /usr/share/X11/xorg.conf.d/10-nvidia.conf (set Identifier "Card0" ) after starting startx on the screen, the image freezes when switching to tty2 and back to tty1, the server does not render anything, and if you open `top` in tty2, you can see: ``` MiB Mem : 31808,1 total, 24998,2 free, 5471,6 used, 1338,3 buff/cache MiB Swap:954,0 total,954,0 free, 0,0 used. 25914,7 avail Mem PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 2547 root 20 0 2880328 156160 86076 R 100,3 0,5 6:19.96 kwin_x11 3033 hetman20 0 3052116 350728 186196 S 1,0 1,1 0:06.43 firefox 3314 hetman20 0 2477080 140688 93056 S 1,0 0,4 0:01.23 Isolated Web Co 306 root 20 0 0 0 0 I 0,3 0,0 0:00.36 kworker/6:2-events 776 message+ 20 09044 6032 3828 S 0,3 0,0 0:01.62 dbus-daemon 801 root 20 0 16852 7828 6892 S 0,3 0,0 0:00.17 systemd-logind 2967 hetman20 0 5771360 4,4g 124548 S 0,3 14,1 2:04.60 plasmashell 3000 hetman20 0 340504 63760 50732 S 0,3 0,2 0:00.37 kwalletd5 3207 hetman20 0 2427008 110324 89080 S 0,3 0,3 0:00.30 Privileged Cont 3607 root 20 0 0 0 0 I 0,3 0,0 0:00.03 kworker/u24:2-events_power_efficient ``` nvidia-smi ``` hetman@katana-lin:/mnt/giga/xorg_nvidia$ cat mvidia-smi.log Mon Mar 7 23:03:53 2022 +-+ | NVIDIA-SMI 510.47.03Driver Version: 510.47.03CUDA Version: 11.6 | |---+--+--+ | GPU NamePersistence-M| Bus-IdDisp.A | Volatile Uncorr. ECC | | Fan Temp Perf Pwr:Usage/Cap| Memory-Usage | GPU-Util Compute M. | | | | MIG M. | |===+==+==| | 0 NVIDIA GeForce ... Off | :01:00.0 Off | N/A | | N/A 41CP8N/A / N/A |132MiB / 4096MiB | 0% Default | | | | N/A | +---+--+--+ +-+ | Processes: | | GPU GI CIPID Type Process name GPU Memory | |ID ID Usage | |=| |0 N/A N/A 2847 G /usr/lib/xorg/Xorg 12MiB | |0 N/A N/A 2967 G /usr/bin/plasmashell8MiB | |0 N/A N/A 3033 G /usr/lib/firefox/firefox 85MiB | |0 N/A N/A 4436 G ...bexec/kscreenlocker_greet 12MiB | +-+ ``` Thus, I stated that the X's started up and are working, but the image is not displayed. if return modprobe i915.modeset=1 /usr/share/X11/xorg.conf.d/20-intel.conf /usr/share/X11/xorg.conf.d/10-nvidia.conf - otherwise the output always goes through only intel (i915) nvidia not uses even if use `prime-select nvidia` - this option ignoring - Description:Ubuntu 20.04.4 LTS Release:20.04 nvidia-driver-510: Installed: 510.47.03-0ubuntu0.20.04.1 Candidate: 510.47.03-0ubuntu0.20.04.1 Version table: *** 510.47.03-0ubuntu0.20.04.1 500 500 http://by.archive.ubuntu.com/ubuntu focal-updates/restricted amd64 Packages 500 http://security.ubuntu.com/ubuntu focal-security/restricted amd64 Packages 100 /var/lib/dpkg/status hetman@katana-lin:/mnt/giga/xorg_ hetman@katana-lin:~$ hwinfo --gfxcard 16: PCI 100.0: 0302 3D controller [Created at pci.386] Unique ID: VCu0.AC6K6Gkky5B Parent ID: vSkL.7WoufefUDA8 SysFS ID: /devices/pci:00/:00:01.0/:01:00.0 SysFS BusID: :01:00.0 Hardware Class: graphics card Model: "nVidia 3D controller" Vendor: pci 0x10de "nVidia Corporation" Device: pci 0x25a2 SubVendor: pci 0x1462 "Micro-Star International Co.,
[Kernel-packages] [Bug 1951289] Re: ubuntu_ltp_controllers:cpuset_sched_domains: tests 3, 9, 11, 17, 19, 25 report incorrect sched domain for cpu#32
After some debugging, I realized the above is the same issue that this commit fixed upstream: commit 71e5f6644fb2f3304fcb310145ded234a37e7cc1 Author: Dietmar Eggemann Date: Mon Feb 1 10:53:53 2021 +0100 sched/topology: Fix sched_domain_topology_level alloc in sched_init_numa() I've backported these fixes and submitted them to stable (5.10.y, 5.4.y & 4.19.y): https://www.spinics.net/lists/stable/msg539011.html https://www.spinics.net/lists/stable/msg539981.html 4.14.y's code is too different for these changes to easily apply. I'll wait for them to bake there to shake out any regressions before submitting to Ubuntu. I expect that focal will pick up the fix from there naturally, but bionic will need an explicit submission since they won't make it into a 4.14.y release. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1951289 Title: ubuntu_ltp_controllers:cpuset_sched_domains: tests 3,9,11,17,19,25 report incorrect sched domain for cpu#32 Status in kunpeng920: New Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Status in linux source package in Focal: Incomplete Status in linux source package in Hirsute: Incomplete Bug description: On scobee-kernel(arm64) with hirsute:linux(5.11.0-41.45) for sru-20211108 there are several reports about the sched domain not covering the full range. The same does not happen on kuzzle. But 32 is a bit of a suspicious number. Running tests... cpuset_sched_domains 1 TINFO: CPUs are numbered continuously starting at 0 (0-127) cpuset_sched_domains 1 TINFO: Nodes are numbered continuously starting at 0 (0-3) cpuset_sched_domains 1 TINFO: root group load balance test cpuset_sched_domains 1 TINFO: sched load balance: 0 cpuset_sched_domains 1 TINFO: CPU hotplug: cpuset_check_domains1 TPASS : check_sched_domains passed cpuset_sched_domains 1 TPASS: partition sched domains succeeded. cpuset_sched_domains 3 TINFO: root group load balance test cpuset_sched_domains 3 TINFO: sched load balance: 1 cpuset_sched_domains 3 TINFO: CPU hotplug: cpuset_check_domains1 TFAIL : cpuset_sched_domains_check.c:110: cpu32's sched domain is wrong(Domain: 0-127, CPU's Sched Domain: 0-95). cpuset_sched_domains 3 TFAIL: partition sched domains failed. cpuset_sched_domains 5 TINFO: root group load balance test cpuset_sched_domains 5 TINFO: sched load balance: 0 cpuset_sched_domains 5 TINFO: CPU hotplug: cpuset_check_domains1 TPASS : check_sched_domains passed cpuset_sched_domains 5 TPASS: partition sched domains succeeded. cpuset_sched_domains 7 TINFO: root group load balance test cpuset_sched_domains 7 TINFO: sched load balance: 0 cpuset_sched_domains 7 TINFO: CPU hotplug: cpuset_check_domains1 TPASS : check_sched_domains passed cpuset_sched_domains 7 TPASS: partition sched domains succeeded. cpuset_sched_domains 9 TINFO: root group load balance test cpuset_sched_domains 9 TINFO: sched load balance: 1 cpuset_sched_domains 9 TINFO: CPU hotplug: cpuset_check_domains1 TFAIL : cpuset_sched_domains_check.c:110: cpu32's sched domain is wrong(Domain: 0-127, CPU's Sched Domain: 0-95). cpuset_sched_domains 9 TFAIL: partition sched domains failed. cpuset_sched_domains 11 TINFO: root group load balance test cpuset_sched_domains 11 TINFO: sched load balance: 1 cpuset_sched_domains 11 TINFO: CPU hotplug: cpuset_check_domains1 TFAIL : cpuset_sched_domains_check.c:110: cpu32's sched domain is wrong(Domain: 0-127, CPU's Sched Domain: 0-95). cpuset_sched_domains 11 TFAIL: partition sched domains failed. cpuset_sched_domains 13 TINFO: general group load balance test cpuset_sched_domains 13 TINFO: root group info: cpuset_sched_domains 13 TINFO: sched load balance: 0 cpuset_sched_domains 13 TINFO: general group info: cpuset_sched_domains 13 TINFO: cpus: - cpuset_sched_domains 13 TINFO: sched load balance: 1 cpuset_check_domains1 TPASS : check_sched_domains passed cpuset_sched_domains 13 TPASS: partition sched domains succeeded. cpuset_sched_domains 15 TINFO: general group load balance test cpuset_sched_domains 15 TINFO: root group info: cpuset_sched_domains 15 TINFO: sched load balance: 0 cpuset_sched_domains 15 TINFO: general group info: cpuset_sched_domains 15 TINFO: cpus: 1 cpuset_sched_domains 15 TINFO: sched load balance: 0 cpuset_check_domains1 TPASS : check_sched_domains passed cpuset_sched_domains 15 TPASS: partition sched domains succeeded. cpuset_sched_domains 17 TINFO: general group load balance test cpuset_sched_domains 17 TINFO: root group info:
[Kernel-packages] [Bug 1963926] Re: focal , mlx5, steering, Add support for non FDB domain
** Changed in: linux (Ubuntu Focal) Status: New => Invalid ** Changed in: linux (Ubuntu Impish) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1963926 Title: focal ,mlx5, steering, Add support for non FDB domain Status in linux package in Ubuntu: Invalid Status in rdma-core package in Ubuntu: New Status in linux source package in Focal: Invalid Status in rdma-core source package in Focal: New Status in linux source package in Impish: Invalid Status in rdma-core source package in Impish: New Status in linux source package in Jammy: Invalid Status in rdma-core source package in Jammy: New Bug description: [Impact] Although focal kernel supports non FDB domains, rdma-core support is missing. we need the below rdma-core patches to add this support [Test Case] install latest DPDK from github $ git clone git://dpdk.org/dpdk $ cd $ mason build $ ninja -C build - Run testpmd /download/dpdk/build-meson/app/dpdk-testpmd -n 4 -a :00:06.0,l3_vxlan_en=1,dv_flow_en=1 -a :00:07.0,l3_vxlan_en=1,dv_flow_en=1 -- --mbcache=512 -i --nb- cores=11 --txd=256 --rxd=256 --burst=64 --mask-event=intr_lsc --mask-event=flow_aged --vxlan-gpe-port=6081 - Try to create any SW Steering rule "group > 0 " testpmd> flow create 0 priority 3 ingress group 0 pattern eth / end actions jump group 34 / end port_flow_complain(): Caught PMD error type 16 (specific action): cannot create jump action.: Operation not supported testpmd>flow create 0 priority 0 egress group 106 pattern eth dst spec 00:16:3e:68:61:b6 dst prefix 32 src spec 00:16:3e:01:73:ac src mask FF:FF:FF:FF:FF:00 type is 33024 has_vlan spec 1 has_vlan prefix 1 / vlan has_more_vlan spec 0 has_more_vlan mask 1 / ipv4 tos spec 228 tos mask 0xff ttl spec 144 ttl prefix 3 / tcp flags spec 228 flags mask 0x00 / end actions set_ipv4_src ipv4_addr 73.93.224.47 / set_ipv4_dst ipv4_addr 53.230.88.14 / set_tp_src port 58291 / inc_tcp_seq value 3623434402 / raw_decap index 0 / raw_encap index 0 / count / end port_flow_complain(): Caught PMD error type 16 (specific action): can't create encap action: Invalid argument testpmd>flow create 0 priority 0 ingress group 20 pattern eth dst is 00:16:3e:26:e2:0f src spec 00:16:3e:49:cf:16 src mask FF:FF:FF:FF:FF:00 type spec 2048 type prefix 16 has_vlan spec 0 has_vlan mask 1 / ipv4 dst is 211.147.138.110 proto spec 1 proto prefix 0 tos spec 18 tos mask 0xf0 ttl is 211 / icmp type spec 18 type prefix 1 ident spec 4790 ident prefix 8 seq spec 4790 seq prefix 1 / end actions mark id 6169568 / set_ipv4_src ipv4_addr 169.127.92.45 / set_mac_src mac_addr 00:16:3e:6d:da:4a / rss queues 0 3 0 3 5 end types ipv6 ipv6-udp-ex ip end / end port_flow_complain(): Caught PMD error type 1 (cause unspecified): cannot create modification action: Cannot allocate memory testpmd>flow create 0 priority 0 ingress group 1 pattern eth dst is 00:16:3e:4e:67:1f src spec 00:16:3e:34:4b:71 src prefix 0 type is 33024 / vlan vid is 2989 has_more_vlan spec 0 has_more_vlan prefix 1 / ipv6 src spec ::3496 src prefix 96 dst spec ::bad0 dst prefix 128 has_frag_ext spec 0 has_frag_ext mask 1 / end actions drop / end port_flow_complain(): Caught PMD error type 1 (cause unspecified): cannot get table: Cannot allocate memory [Regression Potential] TBD [Other Info] Feature patchset: userspace (rdma-core-31): 6724f653 mlx5: DR, Query RoCE capabilities 244015c4 mlx5: DR, Enable SW Steering RX/TX domains both patches cleanly applied on debian/28.1 branch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1963926/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1963835] Re: Message: "Error! Arguments and are not specified." when upgrading
** Package changed: ubuntu => dkms (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/1963835 Title: Message: "Error! Arguments and are not specified." when upgrading Status in dkms package in Ubuntu: New Bug description: Running pre-release Xubuntu 22.04. No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu Jammy Jellyfish (development branch) Release: 22.04 Codename: jammy Linux willem-Aspire-A315-53 5.15.0-18-generic #18-Ubuntu SMP Fri Jan 21 14:57:54 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux After upgrading from 21.04 tot 22.04 I did: sudo apt update && sudo apt full-upgrade I saw this message in the output: dkms: removing: (5.13.0-30-generic) (x86_64) Error! Arguments and are not specified. Usage: remove / or remove -m / or remove -m -v All the output: willem@willem-Aspire-A315-53:~$ sudo apt update && sudo apt full-upgrade [sudo] wachtwoord voor willem: Pakketlijsten worden ingelezen... Klaar Boom van vereisten wordt opgebouwd... Klaar De statusinformatie wordt gelezen... Klaar Opwaardering wordt doorgerekend... Klaar De volgende pakketten zijn automatisch geïnstalleerd en zijn niet langer nodig: libboost-regex1.74.0 libcmis-0.5-5v5 libdecor-0-0 libextutils-pkgconfig-perl libfftw3-double3 libfuse2 libgtksourceview-3.0-1 libgtksourceview-3.0-common libidn11 libigdgmm11 libneon27-gnutls libperl5.32 libpython3.9 libsdl2-2.0-0 libsource-highlight-common libsource-highlight4v5 linux-headers-5.13.0-30 linux-headers-5.13.0-30-generic linux-image-5.13.0-30-generic linux-modules-5.13.0-30-generic linux-modules-extra-5.13.0-30-generic perl-modules-5.32 pkg-config python3-certifi python3-requests python3-simplejson Gebruik 'sudo apt autoremove' om ze te verwijderen. 0 opgewaardeerd, 0 nieuw geïnstalleerd, 0 te verwijderen en 0 niet opgewaardeerd. Pakketlijsten worden ingelezen... Klaar Boom van vereisten wordt opgebouwd... Klaar De statusinformatie wordt gelezen... Klaar Opwaardering wordt doorgerekend... Klaar De volgende pakketten zijn automatisch geïnstalleerd en zijn niet langer nodig: libboost-regex1.74.0 libcmis-0.5-5v5 libdecor-0-0 libextutils-pkgconfig-perl libfftw3-double3 libfuse2 libgtksourceview-3.0-1 libgtksourceview-3.0-common libidn11 libigdgmm11 libneon27-gnutls libperl5.32 libpython3.9 libsdl2-2.0-0 libsource-highlight-common libsource-highlight4v5 linux-headers-5.13.0-30 perl-modules-5.32 pkg-config python3-certifi python3-requests python3-simplejson Gebruik 'sudo apt autoremove' om ze te verwijderen. De volgende pakketten zullen VERWIJDERD worden: linux-headers-5.13.0-30-generic linux-image-5.13.0-30-generic linux-modules-5.13.0-30-generic linux-modules-extra-5.13.0-30-generic 0 opgewaardeerd, 0 nieuw geïnstalleerd, 4 te verwijderen en 0 niet opgewaardeerd. Na deze bewerking zal er 428 MB schijfruimte vrijkomen. Wilt u doorgaan? [J/n] (Database wordt ingelezen ... 402831 bestanden en mappen momenteel geïnstalleerd .) linux-headers-5.13.0-30-generic (5.13.0-30.33) wordt verwijderd ... linux-modules-extra-5.13.0-30-generic (5.13.0-30.33) wordt verwijderd ... linux-modules-5.13.0-30-generic (5.13.0-30.33) wordt verwijderd ... linux-image-5.13.0-30-generic (5.13.0-30.33) wordt verwijderd ..] /etc/kernel/prerm.d/dkms: dkms: removing: (5.13.0-30-generic) (x86_64) Error! Arguments and are not specified. Usage: remove / or remove -m / or remove -m -v /etc/kernel/postrm.d/initramfs-tools: update-initramfs: Deleting /boot/initrd.img-5.13.0-30-generic /etc/kernel/postrm.d/zz-update-grub: Sourcing file `/etc/default/grub' Sourcing file `/etc/default/grub.d/init-select.cfg' Generating grub configuration file ... Found linux image: /boot/vmlinuz-5.15.0-18-generic Found initrd image: /boot/initrd.img-5.15.0-18-generic Found linux image: /boot/vmlinuz-5.13.0-32-generic Found initrd image: /boot/initrd.img-5.13.0-32-generic Memtest86+ needs a 16-bit boot, that is not available on EFI, exiting Warning: os-prober will be executed to detect other bootable partitions. Its output will be used to detect bootable binaries on them and create new boot entries. Found Ubuntu 21.10 (21.10) on /dev/sda2 Found Zorin OS 16 (16) on /dev/sda5 Adding boot menu entry for UEFI Firmware Settings ... done To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1963835/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1963835] [NEW] Message: "Error! Arguments and are not specified." when upgrading
You have been subscribed to a public bug: Running pre-release Xubuntu 22.04. No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu Jammy Jellyfish (development branch) Release:22.04 Codename: jammy Linux willem-Aspire-A315-53 5.15.0-18-generic #18-Ubuntu SMP Fri Jan 21 14:57:54 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux After upgrading from 21.04 tot 22.04 I did: sudo apt update && sudo apt full-upgrade I saw this message in the output: dkms: removing: (5.13.0-30-generic) (x86_64) Error! Arguments and are not specified. Usage: remove / or remove -m / or remove -m -v All the output: willem@willem-Aspire-A315-53:~$ sudo apt update && sudo apt full-upgrade [sudo] wachtwoord voor willem: Pakketlijsten worden ingelezen... Klaar Boom van vereisten wordt opgebouwd... Klaar De statusinformatie wordt gelezen... Klaar Opwaardering wordt doorgerekend... Klaar De volgende pakketten zijn automatisch geïnstalleerd en zijn niet langer nodig: libboost-regex1.74.0 libcmis-0.5-5v5 libdecor-0-0 libextutils-pkgconfig-perl libfftw3-double3 libfuse2 libgtksourceview-3.0-1 libgtksourceview-3.0-common libidn11 libigdgmm11 libneon27-gnutls libperl5.32 libpython3.9 libsdl2-2.0-0 libsource-highlight-common libsource-highlight4v5 linux-headers-5.13.0-30 linux-headers-5.13.0-30-generic linux-image-5.13.0-30-generic linux-modules-5.13.0-30-generic linux-modules-extra-5.13.0-30-generic perl-modules-5.32 pkg-config python3-certifi python3-requests python3-simplejson Gebruik 'sudo apt autoremove' om ze te verwijderen. 0 opgewaardeerd, 0 nieuw geïnstalleerd, 0 te verwijderen en 0 niet opgewaardeerd. Pakketlijsten worden ingelezen... Klaar Boom van vereisten wordt opgebouwd... Klaar De statusinformatie wordt gelezen... Klaar Opwaardering wordt doorgerekend... Klaar De volgende pakketten zijn automatisch geïnstalleerd en zijn niet langer nodig: libboost-regex1.74.0 libcmis-0.5-5v5 libdecor-0-0 libextutils-pkgconfig-perl libfftw3-double3 libfuse2 libgtksourceview-3.0-1 libgtksourceview-3.0-common libidn11 libigdgmm11 libneon27-gnutls libperl5.32 libpython3.9 libsdl2-2.0-0 libsource-highlight-common libsource-highlight4v5 linux-headers-5.13.0-30 perl-modules-5.32 pkg-config python3-certifi python3-requests python3-simplejson Gebruik 'sudo apt autoremove' om ze te verwijderen. De volgende pakketten zullen VERWIJDERD worden: linux-headers-5.13.0-30-generic linux-image-5.13.0-30-generic linux-modules-5.13.0-30-generic linux-modules-extra-5.13.0-30-generic 0 opgewaardeerd, 0 nieuw geïnstalleerd, 4 te verwijderen en 0 niet opgewaardeerd. Na deze bewerking zal er 428 MB schijfruimte vrijkomen. Wilt u doorgaan? [J/n] (Database wordt ingelezen ... 402831 bestanden en mappen momenteel geïnstalleerd .) linux-headers-5.13.0-30-generic (5.13.0-30.33) wordt verwijderd ... linux-modules-extra-5.13.0-30-generic (5.13.0-30.33) wordt verwijderd ... linux-modules-5.13.0-30-generic (5.13.0-30.33) wordt verwijderd ... linux-image-5.13.0-30-generic (5.13.0-30.33) wordt verwijderd ..] /etc/kernel/prerm.d/dkms: dkms: removing: (5.13.0-30-generic) (x86_64) Error! Arguments and are not specified. Usage: remove / or remove -m / or remove -m -v /etc/kernel/postrm.d/initramfs-tools: update-initramfs: Deleting /boot/initrd.img-5.13.0-30-generic /etc/kernel/postrm.d/zz-update-grub: Sourcing file `/etc/default/grub' Sourcing file `/etc/default/grub.d/init-select.cfg' Generating grub configuration file ... Found linux image: /boot/vmlinuz-5.15.0-18-generic Found initrd image: /boot/initrd.img-5.15.0-18-generic Found linux image: /boot/vmlinuz-5.13.0-32-generic Found initrd image: /boot/initrd.img-5.13.0-32-generic Memtest86+ needs a 16-bit boot, that is not available on EFI, exiting Warning: os-prober will be executed to detect other bootable partitions. Its output will be used to detect bootable binaries on them and create new boot entries. Found Ubuntu 21.10 (21.10) on /dev/sda2 Found Zorin OS 16 (16) on /dev/sda5 Adding boot menu entry for UEFI Firmware Settings ... done ** Affects: dkms (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment test -- Message: "Error! Arguments and are not specified." when upgrading https://bugs.launchpad.net/bugs/1963835 You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms 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 1962831] Re: [UBUNTU 20.04] KVM: Enable storage key checking for intercepted instruction
** Description changed: SRU Justification: == [Impact] * KVM uses lazy storage key enablement as Linux does no longer make use of - the storage keys. When the guest enters keyed mode, then KVM will - save/restore the key during paging, provide change/reference tracking for - guest and host and for all interpreted instructions will do key protection. + the storage keys. When the guest enters keyed mode, then KVM will + save/restore the key during paging, provide change/reference tracking for + guest and host and for all interpreted instructions will do key protection. * If an instruction is intercepted and passed along to userspace (like QEMU) - no storage key protection is checked, though. - + no storage key protection is checked, though. + * But this is in violation of the architecture and it can result in misbehaving - guests that rely on key protection for all instructions. + guests that rely on key protection for all instructions. * This item will improve the MEMOP ioctl to also add key checking. - In case of a key protection the right fault is injected in the guest. + In case of a key protection the right fault is injected in the guest. [Fix] * The following changes since commit dbdbd581976f9dfcc9e21a777273b55bdb9bf138: - UBUNTU: Ubuntu-5.4.0-102.115 (2022-02-23 15:32:05 +0100) - are available in the Git repository at: - https://git.launchpad.net/~fheimes/+git/lp1962831/ 16c0809cf1012e68279a8936a482c1d63cc4d14c - for you to fetch changes up to 16c0809cf1012e68279a8936a482c1d63cc4d14c: - KVM: s390: Add missing vm MEM_OP size check (2022-03-03 22:45:50 +0100) + UBUNTU: Ubuntu-5.4.0-102.115 (2022-02-23 15:32:05 +0100) + are available in the Git repository at: + https://git.launchpad.net/~fheimes/+git/lp1962831/ 16c0809cf1012e68279a8936a482c1d63cc4d14c + for you to fetch changes up to 16c0809cf1012e68279a8936a482c1d63cc4d14c: + KVM: s390: Add missing vm MEM_OP size check (2022-03-03 22:45:50 +0100) - * All patches are upstream accepted (but some are as of today in linux- - next). + * Patches are upstream accepted (but some are as of today still in + linux-next). - * The backports are largely needed due to minor conflicts. + * Notes on why the backports are needed are included in the provenance + of the corresponding commit. [Test Case] * An IBM z13 or LinuxONE system is needed running Ubuntu Server 20.04 - with QEMU/KVM setup. + with QEMU/KVM setup. * These modification here are covered by the following three tests: * [kvm-unit-tests,v2] s390x: Test effect of storage keys on some instructions - https://patchwork.kernel.org/project/kvm/patch/20220301095059.3026178-1-s...@linux.ibm.com/ + https://patchwork.kernel.org/project/kvm/patch/20220301095059.3026178-1-s...@linux.ibm.com/ * [PATCH v2 0/5] memop selftest for storage key checking - https://lore.kernel.org/kvm/20220225155311.3540514-1-s...@linux.ibm.com/ + https://lore.kernel.org/kvm/20220225155311.3540514-1-s...@linux.ibm.com/ * c7ef9ebbed20 "KVM: s390: selftests: Test TEST PROTECTION emulation" * The tests and the verification will be done by the IBM Z team. * On top a test build is available (see below). [Where problems could occur] * Issues with vm ioctl may occur due to the introduction of _vm_ioctl. * Tests may fail or may report wrong states due to the new TEST_FAIL macro in - tests/utilities or due to new variants of GUEST_ASSERT in selftests. + tests/utilities or due to new variants of GUEST_ASSERT in selftests. * Problems on gaccess might be caused due to the refactoring of gpa, length - calculation, access address range check and the new access_guest_page helper - function. + calculation, access address range check and the new access_guest_page helper + function. * In uaccess issues may occur due to the introduction of the bit field for OAC - specifier, that causes lot's but relatively straight forward changes or due - to the new storage key checking functions copy_from/to_user_key functions. + specifier, that causes lot's but relatively straight forward changes or due + to the new storage key checking functions copy_from/to_user_key functions. * Compile issues may happen if the changes in uaccess.h bout z10 features - are erroneous. + are erroneous. * Instructions that are emulated by KVM might be impacted due to the expanded - storage key checking, that now covers intercepted instructions, too. - This is the most significant modification in terms of size and complexity - and therefore carries the highest risk. + storage key checking, that now covers intercepted instructions, too. + This is the most significant modification in terms of size and complexity + and therefore carries the highest risk. * MEM_OP IOCTL could be harmed due to the additional, but optional, storage - key extension and checking, or
[Kernel-packages] [Bug 1962831] Re: [UBUNTU 20.04] KVM: Enable storage key checking for intercepted instruction
Additional comment to #16: adjust capability number to 211 to account for an outstanding merge in kvm-next that changed it: https://git.kernel.org/pub/scm/virt/kvm/kvm.git/commit/?h=next=4dfc4ec2b7f5a3a27d166ac42cf8a583fa2d328 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1962831 Title: [UBUNTU 20.04] KVM: Enable storage key checking for intercepted instruction Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: In Progress Bug description: SRU Justification: == [Impact] * KVM uses lazy storage key enablement as Linux does no longer make use of the storage keys. When the guest enters keyed mode, then KVM will save/restore the key during paging, provide change/reference tracking for guest and host and for all interpreted instructions will do key protection. * If an instruction is intercepted and passed along to userspace (like QEMU) no storage key protection is checked, though. * But this is in violation of the architecture and it can result in misbehaving guests that rely on key protection for all instructions. * This item will improve the MEMOP ioctl to also add key checking. In case of a key protection the right fault is injected in the guest. [Fix] * The following changes since commit dbdbd581976f9dfcc9e21a777273b55bdb9bf138: UBUNTU: Ubuntu-5.4.0-102.115 (2022-02-23 15:32:05 +0100) are available in the Git repository at: https://git.launchpad.net/~fheimes/+git/lp1962831/ 16c0809cf1012e68279a8936a482c1d63cc4d14c for you to fetch changes up to 16c0809cf1012e68279a8936a482c1d63cc4d14c: KVM: s390: Add missing vm MEM_OP size check (2022-03-03 22:45:50 +0100) * Patches are upstream accepted (but some are as of today still in linux-next). * Notes on why the backports are needed are included in the provenance of the corresponding commit. [Test Case] * An IBM z13 or LinuxONE system is needed running Ubuntu Server 20.04 with QEMU/KVM setup. * These modification here are covered by the following three tests: * [kvm-unit-tests,v2] s390x: Test effect of storage keys on some instructions https://patchwork.kernel.org/project/kvm/patch/20220301095059.3026178-1-s...@linux.ibm.com/ * [PATCH v2 0/5] memop selftest for storage key checking https://lore.kernel.org/kvm/20220225155311.3540514-1-s...@linux.ibm.com/ * c7ef9ebbed20 "KVM: s390: selftests: Test TEST PROTECTION emulation" * The tests and the verification will be done by the IBM Z team. * On top a test build is available (see below). [Where problems could occur] * Issues with vm ioctl may occur due to the introduction of _vm_ioctl. * Tests may fail or may report wrong states due to the new TEST_FAIL macro in tests/utilities or due to new variants of GUEST_ASSERT in selftests. * Problems on gaccess might be caused due to the refactoring of gpa, length calculation, access address range check and the new access_guest_page helper function. * In uaccess issues may occur due to the introduction of the bit field for OAC specifier, that causes lot's but relatively straight forward changes or due to the new storage key checking functions copy_from/to_user_key functions. * Compile issues may happen if the changes in uaccess.h bout z10 features are erroneous. * Instructions that are emulated by KVM might be impacted due to the expanded storage key checking, that now covers intercepted instructions, too. This is the most significant modification in terms of size and complexity and therefore carries the highest risk. * MEM_OP IOCTL could be harmed due to the additional, but optional, storage key extension and checking, or the new size check and I/O emulation can be impacted due to the new vm IOCTL for key checked guest memory access. * Some tests were added to mitigate this, like the selftests TEST PROTECTION. * The renaming of the existing vcpu memop functions shouldn't be very harmful, since issues will already occur test build. * The rest are API documentation updates and clarifications. * Except two include/header changes and changes in tools/testing all other modifications are s390x specific [Other] * It was ensured that these changes are in jammy based on LP#1933179. __ Description: KVM uses lazy storage key enablement as Linux does no longer make use of the storage keys. When the guest enters keyed mode, then KVM will save/restore the key during paging, provide change/reference tracking for guest and host and for all interpreted instructions will do key protection. If an instruction is intercepted and passed along to userspace (like QEMU) no storage key protection is checked, though. This is in violation of the architecture and it can result in misbehaving guests that rely
[Kernel-packages] [Bug 1961300] Re: linux-azure: Fix NUMA node assignment when kernel boots with custom NUMA topology
** Changed in: linux-azure (Ubuntu Focal)
Status: In Progress => Fix Committed
** Changed in: linux-azure (Ubuntu Impish)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1961300
Title:
linux-azure: Fix NUMA node assignment when kernel boots with custom
NUMA topology
Status in linux-azure package in Ubuntu:
Fix Committed
Status in linux-hwe-5.11 package in Ubuntu:
Invalid
Status in linux-azure source package in Focal:
Fix Committed
Status in linux-hwe-5.11 source package in Focal:
In Progress
Status in linux-azure source package in Impish:
Fix Committed
Status in linux-hwe-5.11 source package in Impish:
Invalid
Status in linux-azure source package in Jammy:
Fix Committed
Status in linux-hwe-5.11 source package in Jammy:
Invalid
Bug description:
SRU Justification
[Impact]
When kernel boots with a NUMA topology with some NUMA nodes offline, the PCI
driver should only set an online NUMA node on the device. This can happen
during KDUMP where some NUMA nodes are not made online by the KDUMP kernel.
This patch also fixes the case where kernel is booting with "numa=off".
Fixes: 999dd956d838 ("PCI: hv: Add support for protocol 1.3 and
support PCI_BUS_RELATIONS2")
[Test Case]
Microsoft tested.
[Where things could go wrong]
NUMA node assignments could be wrong.
[Other Info]
SF: #00323281
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1961300/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1960059] Re: linux-4.4 scheduling while atomic on azure
** Changed in: linux (Ubuntu Xenial) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1960059 Title: linux-4.4 scheduling while atomic on azure Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Fix Committed Bug description: SRU Justification [Impact] Xenial Azure instance types Standard_F32s_v2 and Standard_D8d_v4 frequently panic with linux-lowlatency. [ 11.338145] BUG: scheduling while atomic: systemd-udevd/891/0x0002 [ 11.343832] Modules linked in: edac_core mlx4_core(+) kvm_intel input_leds kvm irqbypass nf_conntrack_ipv4 serio_raw hv_balloon pci_hyperv i2c_piix4 nf_defrag_ipv4 8250_fintek xt_conntrack joydev nf_conntrack mac_hid xt_owner xt_tcpudp iptable_security ip_tables x_tables ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi autofs4 btrfs raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear hid_generic hid_hyperv hv_utils ptp hv_storvsc hyperv_keyboard hid hv_netvsc pps_core scsi_transport_fc hyperv_fb crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper psmouse pata_acpi cryptd hv_vmbus floppy fjes [ 11.343869] CPU: 10 PID: 891 Comm: systemd-udevd Not tainted 4.4.0-219-lowlatency #252-Ubuntu [ 11.343870] Hardware name: Microsoft Corporation Virtual Machine/Virtual Machine, BIOS 090008 12/07/2018 [ 11.343872] 0286 1002a46b615445cb 881095a8f598 81861c01 [ 11.343874] 88109f096280 881095a8f5a8 810ac88b [ 11.343876] 881095a8f5f8 8186c241 881095a8f5c8 000a [ 11.343877] Call Trace: [ 11.343883] [] dump_stack+0x6d/0x8b [ 11.343887] [] __schedule_bug+0x4b/0x60 [ 11.343890] [] __schedule+0x641/0x830 [ 11.343892] [] schedule+0x3c/0x90 [ 11.343894] [] schedule_timeout+0x21d/0x2b0 [ 11.343896] [] wait_for_completion+0xa5/0x120 [ 11.343899] [] ? wake_up_q+0x70/0x70 [ 11.343902] [] hv_compose_msi_msg+0x1d6/0x290 [pci_hyperv] [ 11.343904] [] ? put_hvpcibus+0x20/0x20 [pci_hyperv] [ 11.343908] [] irq_chip_compose_msi_msg+0x4b/0x60 [ 11.343910] [] msi_domain_activate+0x2c/0x70 [ 11.343912] [] irq_domain_activate_irq+0x44/0x50 [ 11.343914] [] irq_startup+0x38/0x90 [ 11.343916] [] __setup_irq+0x5a2/0x650 [ 11.343928] [] ? mlx4_free_cmd_mailbox+0x2d/0x40 [mlx4_core] [ 11.343932] [] ? kmem_cache_alloc_trace+0x1ed/0x210 [ 11.343940] [] ? mlx4_interrupt+0x80/0x80 [mlx4_core] [ 11.343942] [] request_threaded_irq+0xfb/0x1a0 [ 11.343948] [] mlx4_init_eq_table+0x3f8/0x630 [mlx4_core] [ 11.343956] [] mlx4_setup_hca+0x1f8/0x770 [mlx4_core] [ 11.343962] [] mlx4_load_one+0xb67/0x1670 [mlx4_core] [ 11.343967] [] mlx4_init_one+0x528/0x6c0 [mlx4_core] [ 11.343970] [] local_pci_probe+0x4a/0xa0 [ 11.343972] [] ? pci_match_device+0xe0/0x110 [ 11.343973] [] pci_device_probe+0x103/0x150 [ 11.343976] [] driver_probe_device+0x1be/0x4b0 [ 11.343978] [] __driver_attach+0x87/0x90 [ 11.343980] [] ? driver_probe_device+0x4b0/0x4b0 [ 11.343982] [] bus_for_each_dev+0x72/0xc0 [ 11.343983] [] driver_attach+0x1e/0x20 [ 11.343985] [] bus_add_driver+0x1e2/0x280 [ 11.343986] [] ? 0xc078e000 [ 11.343988] [] driver_register+0x60/0xe0 [ 11.343990] [] __pci_register_driver+0x4c/0x50 [ 11.343996] [] mlx4_init+0x115/0x1000 [mlx4_core] [ 11.343998] [] do_one_initcall+0xb5/0x200 [ 11.344003] [] ? __vunmap+0xa5/0x100 [ 11.344005] [] ? kfree+0x166/0x180 [ 11.344007] [] do_init_module+0x5f/0x1da [ 11.344010] [] load_module+0x1712/0x1c90 [ 11.344012] [] ? __symbol_put+0x70/0x70 [ 11.344014] [] ? kernel_read+0x50/0x80 [ 11.344016] [] SYSC_finit_module+0xb4/0xe0 [ 11.344018] [] SyS_finit_module+0xe/0x10 [ 11.344020] [] entry_SYSCALL_64_fastpath+0x22/0xd0 [ 11.344383] BUG: scheduling while atomic: systemd-udevd/891/0x [ 11.349908] Modules linked in: edac_core mlx4_core(+) kvm_intel input_leds kvm irqbypass nf_conntrack_ipv4 serio_raw hv_balloon pci_hyperv i2c_piix4 nf_defrag_ipv4 8250_fintek xt_conntrack joydev nf_conntrack mac_hid xt_owner xt_tcpudp iptable_security ip_tables x_tables ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi autofs4 btrfs raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear hid_generic hid_hyperv hv_utils ptp hv_storvsc hyperv_keyboard hid hv_netvsc pps_core scsi_transport_fc hyperv_fb crct10dif_pclmul crc32_pclmul
[Kernel-packages] [Bug 1963926] Re: focal , mlx5, steering, Add support for non FDB domain
** Also affects: rdma-core (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: Incomplete => Invalid ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: Invalid ** Also affects: rdma-core (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: rdma-core (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: rdma-core (Ubuntu Impish) 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/1963926 Title: focal ,mlx5, steering, Add support for non FDB domain Status in linux package in Ubuntu: Invalid Status in rdma-core package in Ubuntu: New Status in linux source package in Focal: New Status in rdma-core source package in Focal: New Status in linux source package in Impish: New Status in rdma-core source package in Impish: New Status in linux source package in Jammy: Invalid Status in rdma-core source package in Jammy: New Bug description: [Impact] Although focal kernel supports non FDB domains, rdma-core support is missing. we need the below rdma-core patches to add this support [Test Case] install latest DPDK from github $ git clone git://dpdk.org/dpdk $ cd $ mason build $ ninja -C build - Run testpmd /download/dpdk/build-meson/app/dpdk-testpmd -n 4 -a :00:06.0,l3_vxlan_en=1,dv_flow_en=1 -a :00:07.0,l3_vxlan_en=1,dv_flow_en=1 -- --mbcache=512 -i --nb- cores=11 --txd=256 --rxd=256 --burst=64 --mask-event=intr_lsc --mask-event=flow_aged --vxlan-gpe-port=6081 - Try to create any SW Steering rule "group > 0 " testpmd> flow create 0 priority 3 ingress group 0 pattern eth / end actions jump group 34 / end port_flow_complain(): Caught PMD error type 16 (specific action): cannot create jump action.: Operation not supported testpmd>flow create 0 priority 0 egress group 106 pattern eth dst spec 00:16:3e:68:61:b6 dst prefix 32 src spec 00:16:3e:01:73:ac src mask FF:FF:FF:FF:FF:00 type is 33024 has_vlan spec 1 has_vlan prefix 1 / vlan has_more_vlan spec 0 has_more_vlan mask 1 / ipv4 tos spec 228 tos mask 0xff ttl spec 144 ttl prefix 3 / tcp flags spec 228 flags mask 0x00 / end actions set_ipv4_src ipv4_addr 73.93.224.47 / set_ipv4_dst ipv4_addr 53.230.88.14 / set_tp_src port 58291 / inc_tcp_seq value 3623434402 / raw_decap index 0 / raw_encap index 0 / count / end port_flow_complain(): Caught PMD error type 16 (specific action): can't create encap action: Invalid argument testpmd>flow create 0 priority 0 ingress group 20 pattern eth dst is 00:16:3e:26:e2:0f src spec 00:16:3e:49:cf:16 src mask FF:FF:FF:FF:FF:00 type spec 2048 type prefix 16 has_vlan spec 0 has_vlan mask 1 / ipv4 dst is 211.147.138.110 proto spec 1 proto prefix 0 tos spec 18 tos mask 0xf0 ttl is 211 / icmp type spec 18 type prefix 1 ident spec 4790 ident prefix 8 seq spec 4790 seq prefix 1 / end actions mark id 6169568 / set_ipv4_src ipv4_addr 169.127.92.45 / set_mac_src mac_addr 00:16:3e:6d:da:4a / rss queues 0 3 0 3 5 end types ipv6 ipv6-udp-ex ip end / end port_flow_complain(): Caught PMD error type 1 (cause unspecified): cannot create modification action: Cannot allocate memory testpmd>flow create 0 priority 0 ingress group 1 pattern eth dst is 00:16:3e:4e:67:1f src spec 00:16:3e:34:4b:71 src prefix 0 type is 33024 / vlan vid is 2989 has_more_vlan spec 0 has_more_vlan prefix 1 / ipv6 src spec ::3496 src prefix 96 dst spec ::bad0 dst prefix 128 has_frag_ext spec 0 has_frag_ext mask 1 / end actions drop / end port_flow_complain(): Caught PMD error type 1 (cause unspecified): cannot get table: Cannot allocate memory [Regression Potential] TBD [Other Info] Feature patchset: userspace (rdma-core-31): 6724f653 mlx5: DR, Query RoCE capabilities 244015c4 mlx5: DR, Enable SW Steering RX/TX domains both patches cleanly applied on debian/28.1 branch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1963926/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1963926] 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 1963926 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/1963926 Title: focal ,mlx5, steering, Add support for non FDB domain Status in linux package in Ubuntu: Invalid Status in rdma-core package in Ubuntu: New Status in linux source package in Focal: New Status in rdma-core source package in Focal: New Status in linux source package in Impish: New Status in rdma-core source package in Impish: New Status in linux source package in Jammy: Invalid Status in rdma-core source package in Jammy: New Bug description: [Impact] Although focal kernel supports non FDB domains, rdma-core support is missing. we need the below rdma-core patches to add this support [Test Case] install latest DPDK from github $ git clone git://dpdk.org/dpdk $ cd $ mason build $ ninja -C build - Run testpmd /download/dpdk/build-meson/app/dpdk-testpmd -n 4 -a :00:06.0,l3_vxlan_en=1,dv_flow_en=1 -a :00:07.0,l3_vxlan_en=1,dv_flow_en=1 -- --mbcache=512 -i --nb- cores=11 --txd=256 --rxd=256 --burst=64 --mask-event=intr_lsc --mask-event=flow_aged --vxlan-gpe-port=6081 - Try to create any SW Steering rule "group > 0 " testpmd> flow create 0 priority 3 ingress group 0 pattern eth / end actions jump group 34 / end port_flow_complain(): Caught PMD error type 16 (specific action): cannot create jump action.: Operation not supported testpmd>flow create 0 priority 0 egress group 106 pattern eth dst spec 00:16:3e:68:61:b6 dst prefix 32 src spec 00:16:3e:01:73:ac src mask FF:FF:FF:FF:FF:00 type is 33024 has_vlan spec 1 has_vlan prefix 1 / vlan has_more_vlan spec 0 has_more_vlan mask 1 / ipv4 tos spec 228 tos mask 0xff ttl spec 144 ttl prefix 3 / tcp flags spec 228 flags mask 0x00 / end actions set_ipv4_src ipv4_addr 73.93.224.47 / set_ipv4_dst ipv4_addr 53.230.88.14 / set_tp_src port 58291 / inc_tcp_seq value 3623434402 / raw_decap index 0 / raw_encap index 0 / count / end port_flow_complain(): Caught PMD error type 16 (specific action): can't create encap action: Invalid argument testpmd>flow create 0 priority 0 ingress group 20 pattern eth dst is 00:16:3e:26:e2:0f src spec 00:16:3e:49:cf:16 src mask FF:FF:FF:FF:FF:00 type spec 2048 type prefix 16 has_vlan spec 0 has_vlan mask 1 / ipv4 dst is 211.147.138.110 proto spec 1 proto prefix 0 tos spec 18 tos mask 0xf0 ttl is 211 / icmp type spec 18 type prefix 1 ident spec 4790 ident prefix 8 seq spec 4790 seq prefix 1 / end actions mark id 6169568 / set_ipv4_src ipv4_addr 169.127.92.45 / set_mac_src mac_addr 00:16:3e:6d:da:4a / rss queues 0 3 0 3 5 end types ipv6 ipv6-udp-ex ip end / end port_flow_complain(): Caught PMD error type 1 (cause unspecified): cannot create modification action: Cannot allocate memory testpmd>flow create 0 priority 0 ingress group 1 pattern eth dst is 00:16:3e:4e:67:1f src spec 00:16:3e:34:4b:71 src prefix 0 type is 33024 / vlan vid is 2989 has_more_vlan spec 0 has_more_vlan prefix 1 / ipv6 src spec ::3496 src prefix 96 dst spec ::bad0 dst prefix 128 has_frag_ext spec 0 has_frag_ext mask 1 / end actions drop / end port_flow_complain(): Caught PMD error type 1 (cause unspecified): cannot get table: Cannot allocate memory [Regression Potential] TBD [Other Info] Feature patchset: userspace (rdma-core-31): 6724f653 mlx5: DR, Query RoCE capabilities 244015c4 mlx5: DR, Enable SW Steering RX/TX domains both patches cleanly applied on debian/28.1 branch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1963926/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1963948] [NEW] Fix flow table lookup after ct clear or switching zones
Public bug reported: * Explain the bug Flow table lookup is skipped if packet either went through ct clear action (which set the IP_CT_UNTRACKED flag on the packet), or while switching zones and there is already a connection associated with the packet. This will result in no SW offload of the connection, and the and connection not being removed from flow table with TCP teardown (fin/rst packet). * How to test Create OVS bridge with 2 veth pairs, put each veth peer device in a different namespace - ns0, ns1, and add the other side veth devices (named ns[01]_veth below) to OVS bridge. Configure the namespace devices with an ip, and bring all devices up. Enable HW offload in ovs and configure connection tracking OpenFlow rules that pass via two zones (but drop the FIN packets on the reply side or they will still teardown the connection in second zone from the reply side as it happens first): ovs-ofctl add-flow br-ovs "arp actions=NORMAL" ovs-ofctl add-flow br-ovs "ct_state=-trk,ip,in_port=ns0_veth actions=ct(table=5,zone=5)" ovs-ofctl add-flow br-ovs "ct_state=-trk,tcp,in_port=ns1_veth,tcp_flags=-fin actions=ct(table=8,zone=7)" ovs-ofctl add-flow br-ovs "ct_state=+new+trk,ip,in_port=ns0_veth actions=ct(commit,zone=5),ct(table=7,zone=7)" ovs-ofctl add-flow br-ovs "ct_state=+est+trk,ip,in_port=ns0_veth actions=ct(table=7,zone=7)" ovs-ofctl add-flow br-ovs "ct_state=+new+trk,ip,in_port=ns0_veth actions=ct(commit,zone=7),output:ns1_veth" ovs-ofctl add-flow br-ovs "ct_state=+est+trk,ip,in_port=ns0_veth actions=output:ns1_veth" ovs-ofctl add-flow br-ovs "ct_state=+est+trk,tcp,in_port=ns1_veth actions=ct(table=9,zone=5)" ovs-ofctl add-flow br-ovs "ct_state=+est+trk,tcp,in_port=ns1_veth actions=output:ns0_veth" Run TCP iperf from ns0 namespace to an iperf server on ns1 namepsace with the given ip. After traffic ends, check cat /proc/net/nf_conntrack | grep -i offload If bug occurs, connections will remain offloaded till timeout, otherwise, they will be in teardown state. * What it could break. NA ** 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/1963948 Title: Fix flow table lookup after ct clear or switching zones Status in linux-bluefield package in Ubuntu: New Bug description: * Explain the bug Flow table lookup is skipped if packet either went through ct clear action (which set the IP_CT_UNTRACKED flag on the packet), or while switching zones and there is already a connection associated with the packet. This will result in no SW offload of the connection, and the and connection not being removed from flow table with TCP teardown (fin/rst packet). * How to test Create OVS bridge with 2 veth pairs, put each veth peer device in a different namespace - ns0, ns1, and add the other side veth devices (named ns[01]_veth below) to OVS bridge. Configure the namespace devices with an ip, and bring all devices up. Enable HW offload in ovs and configure connection tracking OpenFlow rules that pass via two zones (but drop the FIN packets on the reply side or they will still teardown the connection in second zone from the reply side as it happens first): ovs-ofctl add-flow br-ovs "arp actions=NORMAL" ovs-ofctl add-flow br-ovs "ct_state=-trk,ip,in_port=ns0_veth actions=ct(table=5,zone=5)" ovs-ofctl add-flow br-ovs "ct_state=-trk,tcp,in_port=ns1_veth,tcp_flags=-fin actions=ct(table=8,zone=7)" ovs-ofctl add-flow br-ovs "ct_state=+new+trk,ip,in_port=ns0_veth actions=ct(commit,zone=5),ct(table=7,zone=7)" ovs-ofctl add-flow br-ovs "ct_state=+est+trk,ip,in_port=ns0_veth actions=ct(table=7,zone=7)" ovs-ofctl add-flow br-ovs "ct_state=+new+trk,ip,in_port=ns0_veth actions=ct(commit,zone=7),output:ns1_veth" ovs-ofctl add-flow br-ovs "ct_state=+est+trk,ip,in_port=ns0_veth actions=output:ns1_veth" ovs-ofctl add-flow br-ovs "ct_state=+est+trk,tcp,in_port=ns1_veth actions=ct(table=9,zone=5)" ovs-ofctl add-flow br-ovs "ct_state=+est+trk,tcp,in_port=ns1_veth actions=output:ns0_veth" Run TCP iperf from ns0 namespace to an iperf server on ns1 namepsace with the given ip. After traffic ends, check cat /proc/net/nf_conntrack | grep -i offload If bug occurs, connections will remain offloaded till timeout, otherwise, they will be in teardown state. * What it could break. NA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1963948/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1963926] Re: focal , mlx5, steering, Add support for non FDB domain
** Summary changed: - mlx5: steering, Add support for non FDB domain + focal ,mlx5, steering, Add support for non FDB domain -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1963926 Title: focal ,mlx5, steering, Add support for non FDB domain Status in linux package in Ubuntu: New Bug description: [Impact] Although focal kernel supports non FDB domains, rdma-core support is missing. we need the below rdma-core patches to add this support [Test Case] install latest DPDK from github $ git clone git://dpdk.org/dpdk $ cd $ mason build $ ninja -C build - Run testpmd /download/dpdk/build-meson/app/dpdk-testpmd -n 4 -a :00:06.0,l3_vxlan_en=1,dv_flow_en=1 -a :00:07.0,l3_vxlan_en=1,dv_flow_en=1 -- --mbcache=512 -i --nb- cores=11 --txd=256 --rxd=256 --burst=64 --mask-event=intr_lsc --mask-event=flow_aged --vxlan-gpe-port=6081 - Try to create any SW Steering rule "group > 0 " testpmd> flow create 0 priority 3 ingress group 0 pattern eth / end actions jump group 34 / end port_flow_complain(): Caught PMD error type 16 (specific action): cannot create jump action.: Operation not supported testpmd>flow create 0 priority 0 egress group 106 pattern eth dst spec 00:16:3e:68:61:b6 dst prefix 32 src spec 00:16:3e:01:73:ac src mask FF:FF:FF:FF:FF:00 type is 33024 has_vlan spec 1 has_vlan prefix 1 / vlan has_more_vlan spec 0 has_more_vlan mask 1 / ipv4 tos spec 228 tos mask 0xff ttl spec 144 ttl prefix 3 / tcp flags spec 228 flags mask 0x00 / end actions set_ipv4_src ipv4_addr 73.93.224.47 / set_ipv4_dst ipv4_addr 53.230.88.14 / set_tp_src port 58291 / inc_tcp_seq value 3623434402 / raw_decap index 0 / raw_encap index 0 / count / end port_flow_complain(): Caught PMD error type 16 (specific action): can't create encap action: Invalid argument testpmd>flow create 0 priority 0 ingress group 20 pattern eth dst is 00:16:3e:26:e2:0f src spec 00:16:3e:49:cf:16 src mask FF:FF:FF:FF:FF:00 type spec 2048 type prefix 16 has_vlan spec 0 has_vlan mask 1 / ipv4 dst is 211.147.138.110 proto spec 1 proto prefix 0 tos spec 18 tos mask 0xf0 ttl is 211 / icmp type spec 18 type prefix 1 ident spec 4790 ident prefix 8 seq spec 4790 seq prefix 1 / end actions mark id 6169568 / set_ipv4_src ipv4_addr 169.127.92.45 / set_mac_src mac_addr 00:16:3e:6d:da:4a / rss queues 0 3 0 3 5 end types ipv6 ipv6-udp-ex ip end / end port_flow_complain(): Caught PMD error type 1 (cause unspecified): cannot create modification action: Cannot allocate memory testpmd>flow create 0 priority 0 ingress group 1 pattern eth dst is 00:16:3e:4e:67:1f src spec 00:16:3e:34:4b:71 src prefix 0 type is 33024 / vlan vid is 2989 has_more_vlan spec 0 has_more_vlan prefix 1 / ipv6 src spec ::3496 src prefix 96 dst spec ::bad0 dst prefix 128 has_frag_ext spec 0 has_frag_ext mask 1 / end actions drop / end port_flow_complain(): Caught PMD error type 1 (cause unspecified): cannot get table: Cannot allocate memory [Regression Potential] TBD [Other Info] Feature patchset: userspace (rdma-core-31): 6724f653 mlx5: DR, Query RoCE capabilities 244015c4 mlx5: DR, Enable SW Steering RX/TX domains both patches cleanly applied on debian/28.1 branch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1963926/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1963926] [NEW] mlx5: steering, Add support for non FDB domain
Public bug reported: [Impact] Although focal kernel supports non FDB domains, rdma-core support is missing. we need the below rdma-core patches to add this support [Test Case] install latest DPDK from github $ git clone git://dpdk.org/dpdk $ cd $ mason build $ ninja -C build - Run testpmd /download/dpdk/build-meson/app/dpdk-testpmd -n 4 -a :00:06.0,l3_vxlan_en=1,dv_flow_en=1 -a :00:07.0,l3_vxlan_en=1,dv_flow_en=1 -- --mbcache=512 -i --nb- cores=11 --txd=256 --rxd=256 --burst=64 --mask-event=intr_lsc --mask- event=flow_aged --vxlan-gpe-port=6081 - Try to create any SW Steering rule "group > 0 " testpmd> flow create 0 priority 3 ingress group 0 pattern eth / end actions jump group 34 / end port_flow_complain(): Caught PMD error type 16 (specific action): cannot create jump action.: Operation not supported testpmd>flow create 0 priority 0 egress group 106 pattern eth dst spec 00:16:3e:68:61:b6 dst prefix 32 src spec 00:16:3e:01:73:ac src mask FF:FF:FF:FF:FF:00 type is 33024 has_vlan spec 1 has_vlan prefix 1 / vlan has_more_vlan spec 0 has_more_vlan mask 1 / ipv4 tos spec 228 tos mask 0xff ttl spec 144 ttl prefix 3 / tcp flags spec 228 flags mask 0x00 / end actions set_ipv4_src ipv4_addr 73.93.224.47 / set_ipv4_dst ipv4_addr 53.230.88.14 / set_tp_src port 58291 / inc_tcp_seq value 3623434402 / raw_decap index 0 / raw_encap index 0 / count / end port_flow_complain(): Caught PMD error type 16 (specific action): can't create encap action: Invalid argument testpmd>flow create 0 priority 0 ingress group 20 pattern eth dst is 00:16:3e:26:e2:0f src spec 00:16:3e:49:cf:16 src mask FF:FF:FF:FF:FF:00 type spec 2048 type prefix 16 has_vlan spec 0 has_vlan mask 1 / ipv4 dst is 211.147.138.110 proto spec 1 proto prefix 0 tos spec 18 tos mask 0xf0 ttl is 211 / icmp type spec 18 type prefix 1 ident spec 4790 ident prefix 8 seq spec 4790 seq prefix 1 / end actions mark id 6169568 / set_ipv4_src ipv4_addr 169.127.92.45 / set_mac_src mac_addr 00:16:3e:6d:da:4a / rss queues 0 3 0 3 5 end types ipv6 ipv6-udp-ex ip end / end port_flow_complain(): Caught PMD error type 1 (cause unspecified): cannot create modification action: Cannot allocate memory testpmd>flow create 0 priority 0 ingress group 1 pattern eth dst is 00:16:3e:4e:67:1f src spec 00:16:3e:34:4b:71 src prefix 0 type is 33024 / vlan vid is 2989 has_more_vlan spec 0 has_more_vlan prefix 1 / ipv6 src spec ::3496 src prefix 96 dst spec ::bad0 dst prefix 128 has_frag_ext spec 0 has_frag_ext mask 1 / end actions drop / end port_flow_complain(): Caught PMD error type 1 (cause unspecified): cannot get table: Cannot allocate memory [Regression Potential] TBD [Other Info] Feature patchset: userspace (rdma-core-31): 6724f653 mlx5: DR, Query RoCE capabilities 244015c4 mlx5: DR, Enable SW Steering RX/TX domains both patches cleanly applied on debian/28.1 branch ** 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/1963926 Title: mlx5: steering, Add support for non FDB domain Status in linux package in Ubuntu: New Bug description: [Impact] Although focal kernel supports non FDB domains, rdma-core support is missing. we need the below rdma-core patches to add this support [Test Case] install latest DPDK from github $ git clone git://dpdk.org/dpdk $ cd $ mason build $ ninja -C build - Run testpmd /download/dpdk/build-meson/app/dpdk-testpmd -n 4 -a :00:06.0,l3_vxlan_en=1,dv_flow_en=1 -a :00:07.0,l3_vxlan_en=1,dv_flow_en=1 -- --mbcache=512 -i --nb- cores=11 --txd=256 --rxd=256 --burst=64 --mask-event=intr_lsc --mask-event=flow_aged --vxlan-gpe-port=6081 - Try to create any SW Steering rule "group > 0 " testpmd> flow create 0 priority 3 ingress group 0 pattern eth / end actions jump group 34 / end port_flow_complain(): Caught PMD error type 16 (specific action): cannot create jump action.: Operation not supported testpmd>flow create 0 priority 0 egress group 106 pattern eth dst spec 00:16:3e:68:61:b6 dst prefix 32 src spec 00:16:3e:01:73:ac src mask FF:FF:FF:FF:FF:00 type is 33024 has_vlan spec 1 has_vlan prefix 1 / vlan has_more_vlan spec 0 has_more_vlan mask 1 / ipv4 tos spec 228 tos mask 0xff ttl spec 144 ttl prefix 3 / tcp flags spec 228 flags mask 0x00 / end actions set_ipv4_src ipv4_addr 73.93.224.47 / set_ipv4_dst ipv4_addr 53.230.88.14 / set_tp_src port 58291 / inc_tcp_seq value 3623434402 / raw_decap index 0 / raw_encap index 0 / count / end port_flow_complain(): Caught PMD error type 16 (specific action): can't create encap action: Invalid argument testpmd>flow create 0 priority 0 ingress group 20 pattern eth dst is 00:16:3e:26:e2:0f src spec 00:16:3e:49:cf:16 src mask FF:FF:FF:FF:FF:00 type spec 2048 type prefix 16 has_vlan spec 0 has_vlan
[Kernel-packages] [Bug 1963919] [NEW] fbtft overlay is missing
Public bug reported: To attach TFT touchscreens the pi-foundation kernel ships the fbtft devicetree overlay along with rpi-display. While you can attach a stand-alone TFT display just fine when only using rpi-display to provide the drivers with hardcoded GPIO assignments, it gets extremely tricky to even enable the touchscreen input or to use such a TFT with other sensors attached since rpi-display does not allow any re-assignment of the GPIO pins in use. The upstream fbtft driver can make use of the already included rpi-display drivers by defining "rpi-display" in its params. It also allows to freely re-assign the GPIO pins for backlight, D/C and Reset to give you enough flexibility to have the display co-exist with any attached sensors and touch input devices that do not have the ability to re-assign GPIO pins and that clash with the hardcoded numbering of rpi-display. An example with freely assigned GPIOs can be seen in the upstream (rpi-foundation) overlay README file at: https://github.com/raspberrypi/firmware/blob/master/boot/overlays/README#L884 Please include fbtft in the ubuntu kernels to allow a more flexible usage of SPI based TFT touchscreens on the Pi. ** Affects: linux-raspi2 (Ubuntu) Importance: Wishlist Status: New ** Changed in: linux-raspi2 (Ubuntu) Importance: Undecided => Wishlist ** Description changed: To attach TFT touchscreens the pi-foundation kernel ships the fbtft devicetree overlay along with rpi-display. While you can attach a stand-alone TFT display just fine when only using rpi-display to provide the drivers with hardcoded GPIO assignments, it - gets extremely tricky to even enable the touchscreen or use a TFT with - other sensors attached since rpi-display does not allow any re- - assignment of the GPIO pins in use. + gets extremely tricky to even enable the touchscreen input or to use + such a TFT with other sensors attached since rpi-display does not allow + any re-assignment of the GPIO pins in use. - The upstream fbtft driver can make use of the already included rpi-display drivers by defining "rpi-display" in its params. It also allows to freely re-assign the GPIO pins for backlight, D/C and Reset to give you enough flexibility to have the display co-exist with any attached sensors and touch input devices that do not have the ability to re-assign GPIO pins and that clash with the hardcoded numbering of rpi-display. + The upstream fbtft driver can make use of the already included rpi-display drivers by defining "rpi-display" in its params. It also allows to freely re-assign the GPIO pins for backlight, D/C and Reset to give you enough flexibility to have the display co-exist with any attached sensors and touch input devices that do not have the ability to re-assign GPIO pins and that clash with the hardcoded numbering of rpi-display. An example with freely assigned GPIOs can be seen in the upstream (rpi-foundation) overlay README file at: https://github.com/raspberrypi/firmware/blob/master/boot/overlays/README#L884 Please include fbtft in the ubuntu kernels to allow a more flexible usage of SPI based TFT touchscreens on the Pi. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1963919 Title: fbtft overlay is missing Status in linux-raspi2 package in Ubuntu: New Bug description: To attach TFT touchscreens the pi-foundation kernel ships the fbtft devicetree overlay along with rpi-display. While you can attach a stand-alone TFT display just fine when only using rpi-display to provide the drivers with hardcoded GPIO assignments, it gets extremely tricky to even enable the touchscreen input or to use such a TFT with other sensors attached since rpi- display does not allow any re-assignment of the GPIO pins in use. The upstream fbtft driver can make use of the already included rpi-display drivers by defining "rpi-display" in its params. It also allows to freely re-assign the GPIO pins for backlight, D/C and Reset to give you enough flexibility to have the display co-exist with any attached sensors and touch input devices that do not have the ability to re-assign GPIO pins and that clash with the hardcoded numbering of rpi-display. An example with freely assigned GPIOs can be seen in the upstream (rpi-foundation) overlay README file at: https://github.com/raspberrypi/firmware/blob/master/boot/overlays/README#L884 Please include fbtft in the ubuntu kernels to allow a more flexible usage of SPI based TFT touchscreens on the Pi. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1963919/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help :
[Kernel-packages] [Bug 1963914] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1963914 Title: Require force_probe for i915 driver probing Status in linux package in Ubuntu: Confirmed Bug description: The kernel require force_probe to support ADL-P graphic. Reproduce step: 1. Boot into Ubuntu Jammy 2. $ lsmod | grep i915, the used number is 0 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-18-generic 5.15.0-18.18 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: u 1183 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Mar 7 21:50:41 2022 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-psyduck+X192 InstallationDate: Installed on 2022-03-07 (0 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Dell Inc. Latitude 5530 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-18-generic root=UUID=b3c94cea-c8f7-4579-b41d-6360718d00f0 ro i915.force_probe=4626 quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-18-generic N/A linux-backports-modules-5.15.0-18-generic N/A linux-firmware 20220302.gitee0667aa-0ubuntu1 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-03-07 (0 days ago) dmi.bios.date: 02/25/2022 dmi.bios.release: 1.0 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.1 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.1:bd02/25/2022:br1.0:svnDellInc.:pnLatitude5530:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:sku0B06: dmi.product.family: Latitude dmi.product.name: Latitude 5530 dmi.product.sku: 0B06 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1963914/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1963914] [NEW] Require force_probe for i915 driver probing
Public bug reported: The kernel require force_probe to support ADL-P graphic. Reproduce step: 1. Boot into Ubuntu Jammy 2. $ lsmod | grep i915, the used number is 0 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-18-generic 5.15.0-18.18 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: u 1183 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Mar 7 21:50:41 2022 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-psyduck+X192 InstallationDate: Installed on 2022-03-07 (0 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Dell Inc. Latitude 5530 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-18-generic root=UUID=b3c94cea-c8f7-4579-b41d-6360718d00f0 ro i915.force_probe=4626 quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-18-generic N/A linux-backports-modules-5.15.0-18-generic N/A linux-firmware 20220302.gitee0667aa-0ubuntu1 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-03-07 (0 days ago) dmi.bios.date: 02/25/2022 dmi.bios.release: 1.0 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.1 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.1:bd02/25/2022:br1.0:svnDellInc.:pnLatitude5530:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:sku0B06: dmi.product.family: Latitude dmi.product.name: Latitude 5530 dmi.product.sku: 0B06 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug jammy wayland-session ** Description changed: - The kernel require force_probe to support ADL-S graphic. + The kernel require force_probe to support ADL-P graphic. Reproduce step: 1. Boot into Ubuntu Jammy 2. $ lsmod | grep i915, the used number is 0 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-18-generic 5.15.0-18.18 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: u 1183 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC0: u 1183 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Mar 7 21:50:41 2022 DistributionChannelDescriptor: - # This is the distribution channel descriptor for the OEM CDs - # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor - canonical-oem-somerville-focal-amd64-20200502-85+fossa-psyduck+X192 + # This is the distribution channel descriptor for the OEM CDs + # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor + canonical-oem-somerville-focal-amd64-20200502-85+fossa-psyduck+X192 InstallationDate: Installed on 2022-03-07 (0 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Dell Inc. Latitude 5530 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-18-generic root=UUID=b3c94cea-c8f7-4579-b41d-6360718d00f0 ro i915.force_probe=4626 quiet splash vt.handoff=7 RelatedPackageVersions: - linux-restricted-modules-5.15.0-18-generic N/A - linux-backports-modules-5.15.0-18-generic N/A - linux-firmware 20220302.gitee0667aa-0ubuntu1 + linux-restricted-modules-5.15.0-18-generic N/A + linux-backports-modules-5.15.0-18-generic N/A + linux-firmware 20220302.gitee0667aa-0ubuntu1 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-03-07 (0 days ago) dmi.bios.date: 02/25/2022 dmi.bios.release: 1.0 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.1 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.1:bd02/25/2022:br1.0:svnDellInc.:pnLatitude5530:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:sku0B06: dmi.product.family: Latitude dmi.product.name: Latitude 5530 dmi.product.sku: 0B06 dmi.sys.vendor: Dell Inc. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1963914 Title: Require force_probe for i915 driver probing Status in linux package in Ubuntu: Confirmed Bug description: The kernel require force_probe to support ADL-P graphic. Reproduce step: 1. Boot into Ubuntu Jammy 2. $
[Kernel-packages] [Bug 1962542] Re: [jammy] Bluetooth headphones unable to connect after suspend in BlueZ 5.63
Thank you, I was plagued by this issue on my Bose NC700 cans. In my case bluetoothd isn't crashing btw. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1962542 Title: [jammy] Bluetooth headphones unable to connect after suspend in BlueZ 5.63 Status in Bluez Utilities: Fix Released Status in bluez package in Ubuntu: Fix Released Bug description: Bose quietcomfort 35 is a common headset that can no longer connect to a jammy system after just one suspend. This started at the end of January but just now really debugging the issue. Side note that my bluetooth mouse works fine without problem after any amount of suspends. The headset is only trying to connect to the jammy system (no other bluetooth devices it's paired with has active bluetooth, to isolate only the jammy <-> headset issue). This is jammy running on a T590, up to date, not proposed. heather@fenrir:~$ dpkg -l | grep bluetooth ii gir1.2-gnomebluetooth-1.0:amd643.34.5-4 amd64Introspection data for GnomeBluetooth ii gnome-bluetooth3.34.5-4 amd64GNOME Bluetooth tools ii libbluetooth-dev:amd64 5.63-0ubuntu1 amd64Development files for using the BlueZ Linux Bluetooth library ii libbluetooth3:amd645.63-0ubuntu1 amd64Library to use the BlueZ Linux Bluetooth stack ii libgnome-bluetooth13:amd64 3.34.5-4 amd64GNOME Bluetooth tools - support library ii pulseaudio-module-bluetooth1:15.99.1+dfsg1-1ubuntu1 amd64Bluetooth module for PulseAudio sound server On a fresh boot (not suspended yet), I can connect the headset successfully. Here are the logs of that: Mar 01 09:44:02 fenrir kernel: input: Bose QuietComfort 35 (AVRCP) as /devices/virtual/input/input30 Mar 01 09:44:02 fenrir systemd-logind[1570]: Watching system buttons on /dev/input/event22 (Bose QuietComfort 35 (AVRCP)) Mar 01 09:44:03 fenrir NetworkManager[1536]: [1646124243.8660] platform-linux: do-add-ip6-address[3: fe80::c1bc:a705:9e66:e0d0]: failure 13 (Permission denied) Mar 01 09:44:04 fenrir bluetoothd[1532]: /org/bluez/hci0/dev_60_AB_D2_07_DB_9F/fd0: fd(32) ready Mar 01 09:44:04 fenrir rtkit-daemon[2349]: Supervising 6 threads of 3 processes of 1 users. Mar 01 09:44:04 fenrir rtkit-daemon[2349]: Successfully made thread 5660 of process 2708 owned by '1000' RT at priority 5. Mar 01 09:44:04 fenrir rtkit-daemon[2349]: Supervising 7 threads of 3 processes of 1 users. Mar 01 09:44:04 fenrir pulseaudio[2708]: org.freedesktop.DBus.Properties.Get /org/bluez/hci0/dev_60_AB_D2_07_DB_9F/fd0 Volume failed: org.freedesktop.DBus.Error.InvalidArgs: No such property 'Volume' Mar 01 09:44:04 fenrir pulseaudio[2708]: Battery Level: 70% Mar 01 09:44:04 fenrir pulseaudio[2708]: Dock Status: undocked But then if I close the laptop lid and reopen, login, and try to connect the headset the device is found invalid with the following logs: Mar 01 00:47:08 fenrir kernel: input: Bose QuietComfort 35 (AVRCP) as /devices/virtual/input/input152 Mar 01 00:47:08 fenrir pulseaudio[253956]: Information about device /org/bluez/hci0/dev_60_AB_D2_07_DB_9F is invalid Mar 01 00:47:08 fenrir bluetoothd[40741]: profiles/audio/media.c:endpoint_reply() Endpoint replied with an error: org.bluez.Error.InvalidArguments Mar 01 00:47:08 fenrir pulseaudio[253956]: Information about device /org/bluez/hci0/dev_60_AB_D2_07_DB_9F is invalid Mar 01 00:47:08 fenrir bluetoothd[40741]: profiles/audio/media.c:endpoint_reply() Endpoint replied with an error: org.bluez.Error.InvalidArguments Mar 01 00:47:08 fenrir systemd-logind[1545]: Watching system buttons on /dev/input/event19 (Bose QuietComfort 35 (AVRCP)) Mar 01 00:47:09 fenrir pulseaudio[253956]: Information about device /org/bluez/hci0/dev_60_AB_D2_07_DB_9F is invalid Mar 01 00:47:09 fenrir bluetoothd[40741]: profiles/audio/media.c:endpoint_reply() Endpoint replied with an error: org.bluez.Error.InvalidArguments Mar 01 00:47:09 fenrir pulseaudio[253956]: Information about device /org/bluez/hci0/dev_60_AB_D2_07_DB_9F is invalid Mar 01 00:47:09 fenrir bluetoothd[40741]: profiles/audio/media.c:endpoint_reply() Endpoint replied with an error: org.bluez.Error.InvalidArguments Mar 01 00:47:09 fenrir pulseaudio[253956]: Device doesn't exist for /org/bluez/hci0/dev_60_AB_D2_07_DB_9F Mar 01 00:47:09 fenrir bluetoothd[40741]: src/profile.c:new_conn_reply() Hands-Free Voice gateway replied with an error: org.bluez.Error.InvalidArguments, Unable to handle new connection Mar 01 00:47:09 fenrir pulseaudio[253956]: Device doesn't exist for
[Kernel-packages] [Bug 1963802] Re: lenovo x260: unable to suspend or power off cleanly
Worked around for now by disabling the security chip via the BIOS. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1963802 Title: lenovo x260: unable to suspend or power off cleanly Status in linux package in Ubuntu: Confirmed Bug description: Since upgrading to the new 5.15 kernel in Jammy development I've been unable to suspend or power of my x260 successfully. suspend - laptop appears to have suspended with the power led pulsing but then won't resume power off - laptop appears to have powered off but infact has not - power led is off - have to hold down power button to 5s to fully power off. I was convinced this was a hardware issue so tried with a 20.04 live image which completed both operations sucessfully. I've tried all 5.15 kernels including the one in jammy-proposed. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-18-generic 5.15.0-18.18 ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19 Uname: Linux 5.15.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jamespage 3148 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Mar 6 11:17:25 2022 InstallationDate: Installed on 2018-10-18 (1234 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: LENOVO 20F6CTO1WW ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-22-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-22-generic N/A linux-backports-modules-5.15.0-22-generic N/A linux-firmware 20220302.gitee0667aa-0ubuntu1 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2021-05-12 (298 days ago) dmi.bios.date: 05/08/2019 dmi.bios.release: 1.44 dmi.bios.vendor: LENOVO dmi.bios.version: R02ET71W (1.44 ) dmi.board.asset.tag: Not Available dmi.board.name: 20F6CTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.12 dmi.modalias: dmi:bvnLENOVO:bvrR02ET71W(1.44):bd05/08/2019:br1.44:efr1.12:svnLENOVO:pn20F6CTO1WW:pvrThinkPadX260:rvnLENOVO:rn20F6CTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20F6_BU_Think_FM_ThinkPadX260: dmi.product.family: ThinkPad X260 dmi.product.name: 20F6CTO1WW dmi.product.sku: LENOVO_MT_20F6_BU_Think_FM_ThinkPad X260 dmi.product.version: ThinkPad X260 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1963802/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1963893] Re: Radeon Pro W5500 in passthrough with vfio generates spuriour NMI reason 25
** Attachment added: "dmesg without vendor-reset" https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.13/+bug/1963893/+attachment/5566465/+files/dmesg.txt ** Summary changed: - Radeon Pro W5500 in passthrough with vfio generates spuriour NMI reason 25 + Radeon Pro W5500 in passthrough with vfio generates spurious NMI reason 25 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1963893 Title: Radeon Pro W5500 in passthrough with vfio generates spurious NMI reason 25 Status in linux-signed-hwe-5.13 package in Ubuntu: New Bug description: First encountered in 5.4 kernel, but still present in HWE. Description: Ubuntu 20.04.4 LTS Release: 20.04 We have three of those cards in three identical EPYC 7302P HP DL325 Gen10 servers. ruben@alpha:~$ cat /proc/cmdline BOOT_IMAGE=/vmlinuz-5.13.0-30-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro amd_iommu=on vfio-pci.ids=1002:7341,1002:ab38 nofb iommu=pt dmesg excerpt (with vendor-reset): [ 412.868799] vfio-pci :86:00.0: enabling device (0142 -> 0143) [ 412.868980] vfio-pci :86:00.0: AMD_NAVI14: version 1.1 [ 412.868982] vfio-pci :86:00.0: AMD_NAVI14: performing pre-reset [ 412.42] vfio-pci :86:00.0: AMD_NAVI14: performing reset [ 412.925218] ATOM BIOS: 113-D3250100-102 [ 412.925221] vendor-reset-drm: atomfirmware: bios_scratch_reg_offset initialized to 4c [ 413.171020] vfio-pci :86:00.0: AMD_NAVI14: bus reset disabled? yes [ 413.171028] vfio-pci :86:00.0: AMD_NAVI14: SMU response reg: 0, sol reg: 0, mp1 intr enabled? no, bl ready? yes [ 413.171035] vfio-pci :86:00.0: AMD_NAVI14: performing post-reset [ 413.208794] vfio-pci :86:00.0: AMD_NAVI14: reset result = 0 [ 413.208971] vfio-pci :86:00.0: vfio_ecap_init: hiding ecap 0x19@0x270 [ 413.208985] vfio-pci :86:00.0: vfio_ecap_init: hiding ecap 0x1b@0x2d0 [ 413.208990] vfio-pci :86:00.0: vfio_ecap_init: hiding ecap 0x25@0x400 [ 413.208992] vfio-pci :86:00.0: vfio_ecap_init: hiding ecap 0x26@0x410 [ 413.208994] vfio-pci :86:00.0: vfio_ecap_init: hiding ecap 0x27@0x440 [ 413.228798] vfio-pci :86:00.1: enabling device (0140 -> 0142) [ 413.296899] vfio-pci :86:00.0: AMD_NAVI14: version 1.1 [ 413.296904] vfio-pci :86:00.0: AMD_NAVI14: performing pre-reset [ 413.297096] vfio-pci :86:00.0: AMD_NAVI14: performing reset [ 413.49] ATOM BIOS: 113-D3250100-102 [ 413.51] vendor-reset-drm: atomfirmware: bios_scratch_reg_offset initialized to 4c [ 413.579787] vfio-pci :86:00.0: AMD_NAVI14: bus reset disabled? yes [ 413.579793] vfio-pci :86:00.0: AMD_NAVI14: SMU response reg: 0, sol reg: 0, mp1 intr enabled? no, bl ready? yes [ 413.579797] vfio-pci :86:00.0: AMD_NAVI14: performing post-reset [ 413.616795] vfio-pci :86:00.0: AMD_NAVI14: reset result = 0 [ 419.766917] Uhhuh. NMI received for unknown reason 25 on CPU 0. [ 419.766919] Do you have a strange power saving mode enabled? [ 419.766920] Dazed and confused, but trying to continue [ 436.498601] Uhhuh. NMI received for unknown reason 25 on CPU 0. [ 436.498604] Do you have a strange power saving mode enabled? [ 436.498605] Dazed and confused, but trying to continue [ 454.306951] Uhhuh. NMI received for unknown reason 25 on CPU 0. [ 454.306955] Do you have a strange power saving mode enabled? [ 454.306955] Dazed and confused, but trying to continue [ 456.237162] Uhhuh. NMI received for unknown reason 25 on CPU 0. [ 456.237165] Do you have a strange power saving mode enabled? [ 456.237166] Dazed and confused, but trying to continue [ 457.800596] Uhhuh. NMI received for unknown reason 25 on CPU 0. [ 457.800598] Do you have a strange power saving mode enabled? [ 457.800599] Dazed and confused, but trying to continue [ 474.068911] Uhhuh. NMI received for unknown reason 25 on CPU 0. [ 474.068914] Do you have a strange power saving mode enabled? [ 474.068915] Dazed and confused, but trying to continue This happens both with and without the vendor-reset workaround (https://github.com/gnif/vendor-reset/). The GPU works "fine" in a VM (in OpenStack, KVM), although it generates these spurious NMIs frequently, especially when booting the VM and when using ROCm (eg. clinfo) in the VM. I will now move one of these GPUs in an older Intel system and run bare metal because we need a student to work on it. I'll also test passthrough on that machine, to see whether it has the same behaviour. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.13.0-30-generic 5.13.0-30.33~20.04.1 ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64
[Kernel-packages] [Bug 1953587] Re: Fix sanity checker and cleanup metadata
This bug was fixed in the package linux-firmware - 1.173.21 --- linux-firmware (1.173.21) bionic; urgency=medium * Fix sanity checker and cleanup metadata (LP: #1953587) - Makefile: improve `make check` usefulness - check_whence: python3/utf-8 support - SAUCE: check_whence.py: Add python3 shebang - SAUCE: check_whence.py: Also process WHENCE.ubuntu - SAUCE: check_whence.py: Ignore debian/ and fw_source/ directories - SAUCE: check_whence.py: Ignore ea/ directory - Fix File: entries in WHENCE.ubuntu - SAUCE: Remove non-existing files from WHENCE - Remove non-existing files from WHENCE.ubuntu - SAUCE: Add missing files entries to WHENCE - Add missing entries to WHENCE.ubuntu - Remove unnecessary file LICENCE.tda7706-firmware.txt * Miscellaneous Ubuntu changes - [Packaging] Move scripts to debian/scripts - [Packaging] Add check rule and call it in clean stage - [Packaging] Add packaging helper scripts * Missing firmware /lib/firmware/intel/ice/ddp/ice.pkg for ice driver (LP: #1960839) - ice: Add package file for Intel E800 series driver -- Juerg Haefliger Fri, 18 Feb 2022 15:59:21 +0100 ** Changed in: linux-firmware (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1953587 Title: Fix sanity checker and cleanup metadata Status in linux-firmware package in Ubuntu: New Status in linux-firmware source package in Bionic: Fix Released Status in linux-firmware source package in Focal: Fix Released Status in linux-firmware source package in Hirsute: Fix Released Status in linux-firmware source package in Impish: Fix Released Bug description: The repo contains a checker script check_whence.py that checks WHENCE data against present firmware files and flags missing files and missing WHENCE entries. It currently doesn't parse the downstream WHENCE.ubuntu file. Fix that and cleanup any errors flagged by the checker. [ Impact ] None. These are packaging changes that are not visible to the end user. [ Where Problems Could Occur ] None. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1953587/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1960839] Update Released
The verification of the Stable Release Update for linux-firmware has
completed successfully and the package is now being released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1960839
Title:
Missing firmware /lib/firmware/intel/ice/ddp/ice.pkg for ice driver
Status in linux-firmware package in Ubuntu:
Fix Released
Status in linux-firmware source package in Bionic:
Fix Released
Bug description:
[Impact]
* Missing firmware for Intel ICE driver on Bionic,
which is supported by the HWE kernel from Focal.
[Fix]
* commit 9ae61e7d8658 ("ice: Add package file for Intel E800 series driver")
brings the Bionic package in line with Focal (ice-1.3.4.0.pkg,LICENSE.ice)
[Test Case]
* Without firmware:
ice :98:00.0: firmware 5.4.5 api 1.7.6 nvm 2.40 0x8000706a 0.0.0
build 0x391f7640
ice :98:00.0: Direct firmware load for intel/ice/ddp/ice.pkg failed
with error -2
ice :98:00.0: The DDP package file was not found or could not be
read. Entering Safe Mode
ice :98:00.0: Package download failed. Advanced features disabled -
Device now in Safe Mode
* With firmware:
ice :98:00.0: firmware 5.4.5 api 1.7.6 nvm 2.40 0x8000706a 0.0.0
build 0x391f7640
ice :98:00.0: The DDP package was successfully loaded: ICE OS Default
Package version 1.3.4.0
ice :98:00.0: DCB is enabled in the hardware, max number of TCs
supported on this port are 8
ice :98:00.0: FW LLDP is disabled, DCBx/LLDP in SW mode.
[Where problems could occur]
* Systems with devices managed by the ice driver on Bionic HWE kernel
from Focal.
* The firmware enables advanced features, increasing driver exposure
and device activity.
* This has been available on Focal, which helps with some chance of issues
being hit and
reported previously (e.g. bug 1939855, searched for 'kernel ice driver' on
bugs.lp.net).
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1960839/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1963888] [NEW] Jammy update: v5.15.23 upstream stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.15.23 upstream stable release from git://git.kernel.org/ Linux 5.15.23 tipc: improve size validations for received domain records crypto: api - Move cryptomgr soft dependency into algapi ksmbd: fix SMB 3.11 posix extension mount failure KVM: s390: Return error on SIDA memop on normal guest arm64: Add Cortex-A510 CPU part definition moxart: fix potential use-after-free on remove path ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: linux (Ubuntu Jammy) Importance: Undecided Status: Confirmed ** Tags: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: 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/1963888 Title: Jammy update: v5.15.23 upstream stable release Status in linux package in Ubuntu: Confirmed Status in linux source package in Jammy: Confirmed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.15.23 upstream stable release from git://git.kernel.org/ Linux 5.15.23 tipc: improve size validations for received domain records crypto: api - Move cryptomgr soft dependency into algapi ksmbd: fix SMB 3.11 posix extension mount failure KVM: s390: Return error on SIDA memop on normal guest arm64: Add Cortex-A510 CPU part definition moxart: fix potential use-after-free on remove path To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1963888/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1963890] [NEW] Jammy update: v5.15.25 upstream stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.15.25 upstream stable release from git://git.kernel.org/ Linux 5.15.25 lockdep: Correct lock_classes index mapping i2c: brcmstb: fix support for DSL and CM variants ice: enable parsing IPSEC SPI headers for RSS scsi: qedi: Fix ABBA deadlock in qedi_process_tmf_resp() and qedi_process_cmd_cleanup_resp() copy_process(): Move fd_install() out of sighand->siglock critical section dmaengine: ptdma: Fix the error handling path in pt_core_init() i2c: qcom-cci: don't put a device tree node before i2c_add_adapter() i2c: qcom-cci: don't delete an unregistered adapter tests: fix idmapped mount_setattr test dmaengine: sh: rcar-dmac: Check for error num after dma_set_max_seg_size dmaengine: stm32-dmamux: Fix PM disable depth imbalance in stm32_dmamux_probe dmaengine: sh: rcar-dmac: Check for error num after setting mask net: sched: limit TC_ACT_REPEAT loops ucounts: Move RLIMIT_NPROC handling after set_user rlimit: Fix RLIMIT_NPROC enforcement failure caused by capability calls in set_user lib/iov_iter: initialize "flags" in new pipe_buffer ucounts: Enforce RLIMIT_NPROC not RLIMIT_NPROC+1 ucounts: Base set_cred_ucounts changes on the real user ucounts: In set_cred_ucounts assume new->ucounts is non-NULL ucounts: Handle wrapping in is_ucounts_overlimit EDAC: Fix calculation of returned address and next offset in edac_align_ptr() scsi: lpfc: Fix pt2pt NVMe PRLI reject LOGO loop kconfig: fix failing to generate auto.conf net: macb: Align the dma and coherent dma masks net: usb: qmi_wwan: Add support for Dell DW5829e drm/amd/display: fix yellow carp wm clamping drm/amd/display: Cap pflip irqs per max otg number display/amd: decrease message verbosity about watermarks table failure tracing: Fix tp_printk option related with tp_printk_stop_on_boot drm/rockchip: dw_hdmi: Do not leave clock enabled in error case xprtrdma: fix pointer derefs in error cases of rpcrdma_ep_create soc: aspeed: lpc-ctrl: Block error printing on probe defer cases ata: libata-core: Disable TRIM on M88V29 kconfig: let 'shell' return enough output for deep path names ACPI: PM: Revert "Only mark EC GPE for wakeup on Intel systems" mm: io_uring: allow oom-killer from io_uring_setup selftests: fixup build warnings in pidfd / clone3 tests pidfd: fix test failure due to stack overflow on some arches arm64: dts: meson-g12: drop BL32 region from SEI510/SEI610 arm64: dts: meson-g12: add ATF BL32 reserved-memory region arm64: dts: meson-gx: add ATF BL32 reserved-memory region ksmbd: don't align last entry offset in smb2 query directory ksmbd: fix same UniqueId for dot and dotdot entries netfilter: conntrack: don't refresh sctp entries in closed state x86/bug: Merge annotate_reachable() into _BUG_FLAGS() asm irqchip/sifive-plic: Add missing thead,c900-plic match string phy: phy-mtk-tphy: Fix duplicated argument in phy-mtk-tphy staging: vc04_services: Fix RCU dereference check phy: usb: Leave some clocks running during suspend ARM: OMAP2+: adjust the location of put_device() call in omapdss_init_of ARM: OMAP2+: hwmod: Add of_node_put() before break KVM: x86/pmu: Use AMD64_RAW_EVENT_MASK for PERF_TYPE_RAW KVM: x86/pmu: Don't truncate the PerfEvtSeln MSR when creating a perf event KVM: x86/pmu: Refactoring find_arch_event() to pmc_perf_hw_id() Drivers: hv: vmbus: Fix memory leak in vmbus_add_channel_kobj mtd: rawnand: ingenic: Fix missing put_device in ingenic_ecc_get HID: elo: fix memory leak in elo_probe mtd: rawnand: brcmnand: Fixed incorrect sub-page ECC status mtd: phram: Prevent divide by zero bug in phram_setup() mtd: parsers: qcom: Fix missing free for pparts in cleanup mtd: parsers: qcom: Fix kernel panic on skipped partition mtd: rawnand: qcom: Fix clock sequencing in qcom_nandc_probe() block: fix surprise removal for drivers calling blk_set_queue_dying tty: n_tty: do not look ahead for EOL character past the end of the buffer NFS: Do not report writeback errors in nfs_getattr() NFS: LOOKUP_DIRECTORY is also ok with symlinks NFS: Remove an incorrect revalidation in nfs4_update_changeattr_locked() block/wbt: fix negative inflight counter when remove scsi device ASoC: qcom: Actually clear DMA interrupt register for HDMI ASoC: tas2770: Insert post reset delay scsi: ufs: Fix a deadlock in the error handler scsi: ufs: Remove dead code tipc: fix wrong notification node addresses smb3: fix snapshot mount option mtd: rawnand: gpmi: don't leak PM reference in error path powerpc/lib/sstep: fix 'ptesync' build error powerpc/603: Fix boot failure with DEBUG_PAGEALLOC
[Kernel-packages] [Bug 1963889] [NEW] Jammy update: v5.15.24 upstream stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.15.24 upstream stable release from git://git.kernel.org/ Linux 5.15.24 iommu: Fix potential use-after-free during probe perf: Fix list corruption in perf_cgroup_switch() arm64: dts: imx8mq: fix lcdif port node MIPS: octeon: Fix missed PTR->PTR_WD conversion scsi: lpfc: Reduce log messages seen after firmware download scsi: lpfc: Remove NVMe support if kernel has NVME_FC disabled Makefile.extrawarn: Move -Wunaligned-access to W=1 x86/sgx: Silence softlockup detection when releasing large enclaves hwmon: (dell-smm) Speed up setting of fan speed bus: mhi: pci_generic: Add mru_default for Cinterion MV31-W bus: mhi: pci_generic: Add mru_default for Foxconn SDX55 s390/cio: verify the driver availability for path_event call signal: HANDLER_EXIT should clear SIGNAL_UNKILLABLE seccomp: Invalidate seccomp mode to catch death failures mm: memcg: synchronize objcg lists with a dedicated spinlock iio: buffer: Fix file related error handling in IIO_BUFFER_GET_FD_IOCTL phy: ti: Fix missing sentinel for clk_div_table speakup-dectlk: Restore pitch setting USB: serial: cp210x: add CPI Bulk Coin Recycler id USB: serial: cp210x: add NCR Retail IO box id USB: serial: ch341: add support for GW Instek USB2.0-Serial devices USB: serial: option: add ZTE MF286D modem USB: serial: ftdi_sio: add support for Brainboxes US-159/235/320 usb: raw-gadget: fix handling of dual-direction-capable endpoints usb: gadget: f_uac2: Define specific wTerminalType usb: gadget: rndis: check size of RNDIS_MSG_SET command USB: gadget: validate interface OS descriptor requests usb: gadget: udc: renesas_usb3: Fix host to USB_ROLE_NONE transition usb: dwc3: gadget: Prevent core from processing stale TRBs usb: ulpi: Call of_node_put correctly usb: ulpi: Move of_node_put to ulpi_dev_release net: usb: ax88179_178a: Fix out-of-bounds accesses in RX fixup Revert "usb: dwc2: drd: fix soft connect when gadget is unconfigured" usb: dwc2: drd: fix soft connect when gadget is unconfigured eeprom: ee1004: limit i2c reads to I2C_SMBUS_BLOCK_MAX n_tty: wake up poll(POLLRDNORM) on receiving data vt_ioctl: add array_index_nospec to VT_ACTIVATE vt_ioctl: fix array_index_nospec in vt_setactivate net: dsa: mv88e6xxx: fix use-after-free in mv88e6xxx_mdios_unregister net: mscc: ocelot: fix mutex lock error during ethtool stats read ice: Avoid RTNL lock when re-creating auxiliary device ice: Fix KASAN error in LAG NETDEV_UNREGISTER handler ice: fix IPIP and SIT TSO offload ice: fix an error code in ice_cfg_phy_fec() dpaa2-eth: unregister the netdev before disconnecting from the PHY mptcp: netlink: process IPv6 addrs in creating listening sockets drm/amd/pm: fix hwmon node of power1_label create issue net: amd-xgbe: disable interrupts during pci removal tipc: rate limit warning for received illegal binding update net: mdio: aspeed: Add missing MODULE_DEVICE_TABLE veth: fix races around rq->rx_notify_masked net: fix a memleak when uncloning an skb dst and its metadata net: do not keep the dst cache when uncloning an skb dst and its metadata nfp: flower: fix ida_idx not being released ipmr,ip6mr: acquire RTNL before calling ip[6]mr_free_table() on failure path net: dsa: lantiq_gswip: don't use devres for mdiobus net: dsa: mt7530: fix kernel bug in mdiobus_free() when unbinding net: dsa: felix: don't use devres for mdiobus net: dsa: bcm_sf2: don't use devres for mdiobus net: dsa: ar9331: register the mdiobus under devres net: dsa: mv88e6xxx: don't use devres for mdiobus bonding: pair enable_port with slave_arr_updates fbcon: Avoid 'cap' set but not used warning gpio: sifive: use the correct register to read output values gpiolib: Never return internal error codes to user space ACPI: PM: s2idle: Cancel wakeup before dispatching EC GPE drm/panel: simple: Assign data from panel_dpi_probe() correctly ixgbevf: Require large buffers for build_skb on 82599VF arm64: dts: meson-sm1-odroid: fix boot loop after reboot arm64: dts: meson-sm1-bananapi-m5: fix wrong GPIO domain for GPIOE_2 arm64: dts: meson-sm1-odroid: use correct enable-gpio pin for tf-io regulator arm64: dts: meson-g12b-odroid-n2: fix typo 'dio2133' netfilter: ctnetlink: disable helper autoassign net: sparx5: Fix get_stat64 crash in tcpdump misc: fastrpc: avoid double fput() on failed usercopy drm/vc4: hdmi: Allow DBLCLK modes even if horz timing is odd. NFS: Don't skip directory entries when doing uncached readdir NFS: Don't overfill uncached readdir pages gpio: aggregator: Fix calling into sleeping GPIO controllers phy: dphy:
[Kernel-packages] [Bug 1963891] [NEW] Jammy update: v5.15.26 upstream stable release
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from a mainline/stable Linux tree or
a minimally backported form of that patch. The following upstream
stable patches should be included in the Ubuntu kernel:
v5.15.26 upstream stable release
from git://git.kernel.org/
Linux 5.15.26
ice: fix concurrent reset and removal of VFs
ice: Fix race conditions between virtchnl handling and VF ndo ops
memblock: use kfree() to release kmalloced memblock regions
gpio: tegra186: Fix chip_data type confusion
pinctrl: k210: Fix bias-pull-up
pinctrl: fix loop in k210_pinconf_get_drive()
tty: n_gsm: fix deadlock in gsmtty_open()
tty: n_gsm: fix wrong modem processing in convergence layer type 2
tty: n_gsm: fix wrong tty control line for flow control
tty: n_gsm: fix NULL pointer access due to DLCI release
tty: n_gsm: fix proper link termination after failed open
tty: n_gsm: fix encoding of control signal octet bit DV
riscv: fix oops caused by irqsoff latency tracer
riscv: fix nommu_k210_sdcard_defconfig
IB/qib: Fix duplicate sysfs directory name
tps6598x: clear int mask on probe failure
staging: fbtft: fb_st7789v: reset display before initialization
thermal: int340x: fix memory leak in int3400_notify()
RDMA/cma: Do not change route.addr.src_addr outside state checks
btrfs: prevent copying too big compressed lzo segment
driver core: Free DMA range map when device is released
mtd: core: Fix a conflict between MTD and NVMEM on wp-gpios property
nvmem: core: Fix a conflict between MTD and NVMEM on wp-gpios property
xhci: Prevent futile URB re-submissions due to incorrect return value.
xhci: re-initialize the HC during resume if HCE was set
usb: dwc3: gadget: Let the interrupt handler disable bottom halves.
usb: dwc3: pci: Fix Bay Trail phy GPIO mappings
usb: dwc3: pci: Add "snps,dis_u2_susphy_quirk" for Intel Bay Trail
usb: dwc2: drd: fix soft connect when gadget is unconfigured
USB: serial: option: add Telit LE910R1 compositions
USB: serial: option: add support for DW5829e
tracefs: Set the group ownership in apply_options() not parse_options()
USB: gadget: validate endpoint index for xilinx udc
usb: gadget: rndis: add spinlock for rndis response list
Revert "USB: serial: ch341: add new Product ID for CH341A"
ata: pata_hpt37x: disable primary channel on HPT371
sc16is7xx: Fix for incorrect data being transmitted
iio: Fix error handling for PM
iio: imu: st_lsm6dsx: wait for settling time in st_lsm6dsx_read_oneshot
iio: accel: fxls8962af: add padding to regmap for SPI
iio: adc: ad7124: fix mask used for setting AIN_BUFP & AIN_BUFM bits
iio: adc: tsc2046: fix memory corruption by preventing array overflow
iio: adc: men_z188_adc: Fix a resource leak in an error handling path
iio:imu:adis16480: fix buffering for devices with no burst mode
tracing: Have traceon and traceoff trigger honor the instance
tracing: Dump stacktrace trigger to the corresponding instance
RDMA/ib_srp: Fix a deadlock
configfs: fix a race in configfs_{,un}register_subsystem()
bnxt_en: Increase firmware message response DMA wait time
RDMA/rtrs-clt: Move free_permit from free_clt to rtrs_clt_close
RDMA/rtrs-clt: Fix possible double free in error case
net-timestamp: convert sk->sk_tskey to atomic_t
regmap-irq: Update interrupt clear register for proper reset
gpio: rockchip: Reset int_bothedge when changing trigger
spi: spi-zynq-qspi: Fix a NULL pointer dereference in zynq_qspi_exec_mem_op()
net/mlx5: Update log_max_qp value to be 17 at most
net/mlx5e: kTLS, Use CHECKSUM_UNNECESSARY for device-offloaded packets
net/mlx5e: MPLSoUDP decap, fix check for unsupported matches
net/mlx5: DR, Fix the threshold that defines when pool sync is initiated
net/mlx5: Fix wrong limitation of metadata match on ecpf
net/mlx5: Fix possible deadlock on rule deletion
net/mlx5: DR, Don't allow match on IP w/o matching on full ethertype/ip_version
ibmvnic: schedule failover only if vioctl fails
net/mlx5: DR, Cache STE shadow memory
udp_tunnel: Fix end of loop test in udp_tunnel_nic_unregister()
surface: surface3_power: Fix battery readings on batteries without a serial
number
net/smc: Use a mutex for locking "struct smc_pnettable"
netfilter: nf_tables: fix memory leak during stateful obj update
net: mdio-ipq4019: add delay after clock enable
nfp: flower: Fix a potential leak in nfp_tunnel_add_shared_mac()
netfilter: nf_tables: unregister flowtable hooks on netns exit
net: Force inlining of checksum functions in net/checksum.h
net: ll_temac: check the return value of devm_kmalloc()
net/sched: act_ct: Fix flow table lookup after ct clear or switching zones
drm/i915/dg2: Print PHY name properly on calibration error
drm/vc4: crtc: Fix runtime_pm reference counting
net/mlx5e: Fix wrong return value on
[Kernel-packages] [Bug 1963893] Re: Radeon Pro W5500 in passthrough with vfio generates spuriour NMI reason 25
** Attachment added: "dmesg with vendor-reset" https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.13/+bug/1963893/+attachment/5566464/+files/dmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1963893 Title: Radeon Pro W5500 in passthrough with vfio generates spuriour NMI reason 25 Status in linux-signed-hwe-5.13 package in Ubuntu: New Bug description: First encountered in 5.4 kernel, but still present in HWE. Description: Ubuntu 20.04.4 LTS Release: 20.04 We have three of those cards in three identical EPYC 7302P HP DL325 Gen10 servers. ruben@alpha:~$ cat /proc/cmdline BOOT_IMAGE=/vmlinuz-5.13.0-30-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro amd_iommu=on vfio-pci.ids=1002:7341,1002:ab38 nofb iommu=pt dmesg excerpt (with vendor-reset): [ 412.868799] vfio-pci :86:00.0: enabling device (0142 -> 0143) [ 412.868980] vfio-pci :86:00.0: AMD_NAVI14: version 1.1 [ 412.868982] vfio-pci :86:00.0: AMD_NAVI14: performing pre-reset [ 412.42] vfio-pci :86:00.0: AMD_NAVI14: performing reset [ 412.925218] ATOM BIOS: 113-D3250100-102 [ 412.925221] vendor-reset-drm: atomfirmware: bios_scratch_reg_offset initialized to 4c [ 413.171020] vfio-pci :86:00.0: AMD_NAVI14: bus reset disabled? yes [ 413.171028] vfio-pci :86:00.0: AMD_NAVI14: SMU response reg: 0, sol reg: 0, mp1 intr enabled? no, bl ready? yes [ 413.171035] vfio-pci :86:00.0: AMD_NAVI14: performing post-reset [ 413.208794] vfio-pci :86:00.0: AMD_NAVI14: reset result = 0 [ 413.208971] vfio-pci :86:00.0: vfio_ecap_init: hiding ecap 0x19@0x270 [ 413.208985] vfio-pci :86:00.0: vfio_ecap_init: hiding ecap 0x1b@0x2d0 [ 413.208990] vfio-pci :86:00.0: vfio_ecap_init: hiding ecap 0x25@0x400 [ 413.208992] vfio-pci :86:00.0: vfio_ecap_init: hiding ecap 0x26@0x410 [ 413.208994] vfio-pci :86:00.0: vfio_ecap_init: hiding ecap 0x27@0x440 [ 413.228798] vfio-pci :86:00.1: enabling device (0140 -> 0142) [ 413.296899] vfio-pci :86:00.0: AMD_NAVI14: version 1.1 [ 413.296904] vfio-pci :86:00.0: AMD_NAVI14: performing pre-reset [ 413.297096] vfio-pci :86:00.0: AMD_NAVI14: performing reset [ 413.49] ATOM BIOS: 113-D3250100-102 [ 413.51] vendor-reset-drm: atomfirmware: bios_scratch_reg_offset initialized to 4c [ 413.579787] vfio-pci :86:00.0: AMD_NAVI14: bus reset disabled? yes [ 413.579793] vfio-pci :86:00.0: AMD_NAVI14: SMU response reg: 0, sol reg: 0, mp1 intr enabled? no, bl ready? yes [ 413.579797] vfio-pci :86:00.0: AMD_NAVI14: performing post-reset [ 413.616795] vfio-pci :86:00.0: AMD_NAVI14: reset result = 0 [ 419.766917] Uhhuh. NMI received for unknown reason 25 on CPU 0. [ 419.766919] Do you have a strange power saving mode enabled? [ 419.766920] Dazed and confused, but trying to continue [ 436.498601] Uhhuh. NMI received for unknown reason 25 on CPU 0. [ 436.498604] Do you have a strange power saving mode enabled? [ 436.498605] Dazed and confused, but trying to continue [ 454.306951] Uhhuh. NMI received for unknown reason 25 on CPU 0. [ 454.306955] Do you have a strange power saving mode enabled? [ 454.306955] Dazed and confused, but trying to continue [ 456.237162] Uhhuh. NMI received for unknown reason 25 on CPU 0. [ 456.237165] Do you have a strange power saving mode enabled? [ 456.237166] Dazed and confused, but trying to continue [ 457.800596] Uhhuh. NMI received for unknown reason 25 on CPU 0. [ 457.800598] Do you have a strange power saving mode enabled? [ 457.800599] Dazed and confused, but trying to continue [ 474.068911] Uhhuh. NMI received for unknown reason 25 on CPU 0. [ 474.068914] Do you have a strange power saving mode enabled? [ 474.068915] Dazed and confused, but trying to continue This happens both with and without the vendor-reset workaround (https://github.com/gnif/vendor-reset/). The GPU works "fine" in a VM (in OpenStack, KVM), although it generates these spurious NMIs frequently, especially when booting the VM and when using ROCm (eg. clinfo) in the VM. I will now move one of these GPUs in an older Intel system and run bare metal because we need a student to work on it. I'll also test passthrough on that machine, to see whether it has the same behaviour. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.13.0-30-generic 5.13.0-30.33~20.04.1 ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Mar 7 10:26:25 2022 InstallationDate: Installed on 2022-01-05 (60 days ago) InstallationMedia: Ubuntu-Server 18.04.6 LTS "Bionic Beaver" - Release amd64
[Kernel-packages] [Bug 1963893] [NEW] Radeon Pro W5500 in passthrough with vfio generates spuriour NMI reason 25
Public bug reported: First encountered in 5.4 kernel, but still present in HWE. Description:Ubuntu 20.04.4 LTS Release:20.04 We have three of those cards in three identical EPYC 7302P HP DL325 Gen10 servers. ruben@alpha:~$ cat /proc/cmdline BOOT_IMAGE=/vmlinuz-5.13.0-30-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro amd_iommu=on vfio-pci.ids=1002:7341,1002:ab38 nofb iommu=pt dmesg excerpt (with vendor-reset): [ 412.868799] vfio-pci :86:00.0: enabling device (0142 -> 0143) [ 412.868980] vfio-pci :86:00.0: AMD_NAVI14: version 1.1 [ 412.868982] vfio-pci :86:00.0: AMD_NAVI14: performing pre-reset [ 412.42] vfio-pci :86:00.0: AMD_NAVI14: performing reset [ 412.925218] ATOM BIOS: 113-D3250100-102 [ 412.925221] vendor-reset-drm: atomfirmware: bios_scratch_reg_offset initialized to 4c [ 413.171020] vfio-pci :86:00.0: AMD_NAVI14: bus reset disabled? yes [ 413.171028] vfio-pci :86:00.0: AMD_NAVI14: SMU response reg: 0, sol reg: 0, mp1 intr enabled? no, bl ready? yes [ 413.171035] vfio-pci :86:00.0: AMD_NAVI14: performing post-reset [ 413.208794] vfio-pci :86:00.0: AMD_NAVI14: reset result = 0 [ 413.208971] vfio-pci :86:00.0: vfio_ecap_init: hiding ecap 0x19@0x270 [ 413.208985] vfio-pci :86:00.0: vfio_ecap_init: hiding ecap 0x1b@0x2d0 [ 413.208990] vfio-pci :86:00.0: vfio_ecap_init: hiding ecap 0x25@0x400 [ 413.208992] vfio-pci :86:00.0: vfio_ecap_init: hiding ecap 0x26@0x410 [ 413.208994] vfio-pci :86:00.0: vfio_ecap_init: hiding ecap 0x27@0x440 [ 413.228798] vfio-pci :86:00.1: enabling device (0140 -> 0142) [ 413.296899] vfio-pci :86:00.0: AMD_NAVI14: version 1.1 [ 413.296904] vfio-pci :86:00.0: AMD_NAVI14: performing pre-reset [ 413.297096] vfio-pci :86:00.0: AMD_NAVI14: performing reset [ 413.49] ATOM BIOS: 113-D3250100-102 [ 413.51] vendor-reset-drm: atomfirmware: bios_scratch_reg_offset initialized to 4c [ 413.579787] vfio-pci :86:00.0: AMD_NAVI14: bus reset disabled? yes [ 413.579793] vfio-pci :86:00.0: AMD_NAVI14: SMU response reg: 0, sol reg: 0, mp1 intr enabled? no, bl ready? yes [ 413.579797] vfio-pci :86:00.0: AMD_NAVI14: performing post-reset [ 413.616795] vfio-pci :86:00.0: AMD_NAVI14: reset result = 0 [ 419.766917] Uhhuh. NMI received for unknown reason 25 on CPU 0. [ 419.766919] Do you have a strange power saving mode enabled? [ 419.766920] Dazed and confused, but trying to continue [ 436.498601] Uhhuh. NMI received for unknown reason 25 on CPU 0. [ 436.498604] Do you have a strange power saving mode enabled? [ 436.498605] Dazed and confused, but trying to continue [ 454.306951] Uhhuh. NMI received for unknown reason 25 on CPU 0. [ 454.306955] Do you have a strange power saving mode enabled? [ 454.306955] Dazed and confused, but trying to continue [ 456.237162] Uhhuh. NMI received for unknown reason 25 on CPU 0. [ 456.237165] Do you have a strange power saving mode enabled? [ 456.237166] Dazed and confused, but trying to continue [ 457.800596] Uhhuh. NMI received for unknown reason 25 on CPU 0. [ 457.800598] Do you have a strange power saving mode enabled? [ 457.800599] Dazed and confused, but trying to continue [ 474.068911] Uhhuh. NMI received for unknown reason 25 on CPU 0. [ 474.068914] Do you have a strange power saving mode enabled? [ 474.068915] Dazed and confused, but trying to continue This happens both with and without the vendor-reset workaround (https://github.com/gnif/vendor-reset/). The GPU works "fine" in a VM (in OpenStack, KVM), although it generates these spurious NMIs frequently, especially when booting the VM and when using ROCm (eg. clinfo) in the VM. I will now move one of these GPUs in an older Intel system and run bare metal because we need a student to work on it. I'll also test passthrough on that machine, to see whether it has the same behaviour. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.13.0-30-generic 5.13.0-30.33~20.04.1 ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Mar 7 10:26:25 2022 InstallationDate: Installed on 2022-01-05 (60 days ago) InstallationMedia: Ubuntu-Server 18.04.6 LTS "Bionic Beaver" - Release amd64 (20210915) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-5.13 UpgradeStatus: Upgraded to focal on 2022-01-17 (48 days ago) ** Affects: linux-signed-hwe-5.13 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal uec-images -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1963893 Title: Radeon Pro W5500 in passthrough with vfio generates spuriour NMI reason 25
[Kernel-packages] [Bug 1962515] Re: Intermittent AX211 iwlwifi RT ucode init failed -110 at boot
** Changed in: linux-firmware (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1962515 Title: Intermittent AX211 iwlwifi RT ucode init failed -110 at boot Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-firmware package in Ubuntu: Fix Released Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-firmware source package in Focal: Fix Committed Status in linux-oem-5.14 source package in Focal: Won't Fix Status in linux source package in Impish: New Status in linux-firmware source package in Impish: New Status in linux-oem-5.14 source package in Impish: New Status in linux source package in Jammy: In Progress Status in linux-firmware source package in Jammy: Fix Released Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: [SRU Justification] [Impact] AX211 might fail to load -64 firmware on some platforms. iwlwifi :00:14.3: Failed to start RT ucode: -110 [Fix] This can only be fixed in the firmware, and currently v5.14 kernel has FW API 64, v5.15 has 66 and only v5.16 or above has 67. [Test Case] Run checkbox reboot stress tests to try trigger this issue: $ checkbox-cli run com.canonical.certification::stress/reboot [Where problems could occur] The source commit originally contains 67 fw for several models, and yet AX211, which taks iwlwifi-so-a0-gf-a0-*.ucode and its corresponding pnvm file, is the only known problematic model affected. This pull request imports only the needed files to eliminate the possibility of regression as possible. == original bug report == [ 5.675835] iwlwifi :00:14.3: enabling device ( -> 0002) [ 5.693214] iwlwifi :00:14.3: api flags index 2 larger than supported by driver [ 5.693277] iwlwifi :00:14.3: TLV_FW_FSEQ_VERSION: FSEQ Version: 0.0.2.25 [ 5.698065] iwlwifi :00:14.3: loaded firmware version 64.97bbee0a.0 so-a0-gf-a0-64.ucode op_mode iwlmvm [ 5.933114] iwlwifi :00:14.3: Detected Intel(R) Wi-Fi 6E AX211 160MHz, REV=0x370 [ 6.101350] iwlwifi :00:14.3: loaded PNVM version 0x4b50f925 [ 6.113388] iwlwifi :00:14.3: Detected RF GF, rfid=0x2010d000 [ 6.181309] iwlwifi :00:14.3: base HW address: 7c:50:79:c9:29:67 [ 6.201398] iwlwifi :00:14.3 wlp0s20f3: renamed from wlan0 [ 7.396811] iwlwifi :00:14.3: SecBoot CPU1 Status: 0x71f7, CPU2 Status: 0xb03 [ 7.396859] iwlwifi :00:14.3: UMAC PC: 0xc0081906 [ 7.396912] iwlwifi :00:14.3: LMAC PC: 0x1541c [ 7.396914] iwlwifi :00:14.3: WRT: Collecting data: ini trigger 13 fired (delay=0ms). [ 7.399116] iwlwifi :00:14.3: Loaded firmware version: 64.97bbee0a.0 so-a0-gf-a0-64.ucode [ 7.399119] iwlwifi :00:14.3: 0x | ADVANCED_SYSASSERT [ 7.399121] iwlwifi :00:14.3: 0x | trm_hw_status0 [ 7.399123] iwlwifi :00:14.3: 0x | trm_hw_status1 [ 7.399124] iwlwifi :00:14.3: 0x | branchlink2 [ 7.399125] iwlwifi :00:14.3: 0x | interruptlink1 [ 7.399127] iwlwifi :00:14.3: 0x | interruptlink2 [ 7.399128] iwlwifi :00:14.3: 0x | data1 [ 7.399129] iwlwifi :00:14.3: 0x | data2 [ 7.399130] iwlwifi :00:14.3: 0x | data3 [ 7.399132] iwlwifi :00:14.3: 0x | beacon time [ 7.399133] iwlwifi :00:14.3: 0x | tsf low [ 7.399134] iwlwifi :00:14.3: 0x | tsf hi [ 7.399135] iwlwifi :00:14.3: 0x | time gp1 [ 7.399136] iwlwifi :00:14.3: 0x | time gp2 [ 7.399137] iwlwifi :00:14.3: 0x | uCode revision type [ 7.399139] iwlwifi :00:14.3: 0x | uCode version major [ 7.399140] iwlwifi :00:14.3: 0x | uCode version minor [ 7.399141] iwlwifi :00:14.3: 0x | hw version [ 7.399143] iwlwifi :00:14.3: 0x | board version [ 7.399144] iwlwifi :00:14.3: 0x | hcmd [ 7.399145] iwlwifi :00:14.3: 0x | isr0 [ 7.399146] iwlwifi :00:14.3: 0x | isr1 [ 7.399147] iwlwifi :00:14.3: 0x | isr2 [ 7.399148] iwlwifi :00:14.3: 0x | isr3 [ 7.399149] iwlwifi :00:14.3: 0x | isr4 [ 7.399150] iwlwifi :00:14.3: 0x | last cmd Id [ 7.399152] iwlwifi :00:14.3: 0x | wait_event [ 7.399153] iwlwifi :00:14.3: 0x | l2p_control [ 7.399154] iwlwifi :00:14.3: 0x | l2p_duration [ 7.399155] iwlwifi :00:14.3: 0x | l2p_mhvalid [ 7.399157] iwlwifi :00:14.3: 0x | l2p_addr_match [ 7.399158] iwlwifi :00:14.3: 0x | lmpm_pmg_sel [ 7.399159] iwlwifi :00:14.3: 0x | timestamp [ 7.399161] iwlwifi :00:14.3:
[Kernel-packages] [Bug 1963614] Re: mt7921e device disappear after warm boot stress
** Changed in: linux-firmware (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-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1963614 Title: mt7921e device disappear after warm boot stress Status in HWE Next: New Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Focal: Fix Committed Status in linux-firmware source package in Jammy: Fix Released Bug description: [SRU Justification] [Impact] mt7921e may not appear in the bus enumeration during warm boot stress tests. [Fix] This can only be fixed in the firmware. [Test Case] Run checkbox reboot stress tests to try trigger this issue: $ checkbox-cli run com.canonical.certification::stress/reboot [Where problems could occur] While this backports proprietary fw blob, it may bring driver compatibility issues we cannot know in the first place. Jammy has these already, so only Focal (for oem-5.14) is nominated. We don't have mt7921e hardware v2.1 support in Impish 5.13 kernel. == original bug report == [Summary] mt7921 wlan device disappear after warm reset, can be recovered by cold boot. [Reproduce Steps] 1. do warm boot stress 100 times 2. check wifi function after stress finished 3. wifi has no function and mt7921e device disappeared [Results] Expected: wifi works normally Actual: wifi broken To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1963614/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
