[Kernel-packages] [Bug 1968235] [NEW] [i915] Dual DP 4K @60Hz requires toggling to 30Hz and back to 60Hz
You have been subscribed to a public bug: I recently started using a Cable-Matters-201355 with my XPS 9380 (8th Gen TB3). The dock supports dual 4K DP @ 60Hz via thunderbolt with PD input. (HBR3 compliant USB-C Dock (DSC/DP1.4 support) that uses all 4 high speed lanes to get dual 60Hz) Both displays boot mirrored when powered up (Dell Logo, Grub, Kernel output) however go blank just as wayland starts up. Unplugging one of them allows the other to appear at 3840x2160@60Hz, after which I have to execute the following process to get both up and running. 1) Change the refresh rate of the active display to 30Hz, apply in Screen Display settings dialog 2) Plug the 2nd monitor in; At this point both appear in Screen Display dialog @60Hz, but the 2nd remains blank 3) Change both to 30Hz, apply; At this point the 2nd screen turns on 4) Change both to 60Hz, apply; At this point both are working at 60Hz, my desired end state Inspection of edid seems fine (below), other than the DisplaySize showing 27" instead of 32". Monitors are identical. Previously, I might be able to script my steps above using xrandr, but that seems to no longer be the case with 21.10 and wayland. I seem to be limited to the Screen Display dialog. Since I can fix by simply re-applying the settings, it seems like a bug on startup. If I could find a CLI option to allow me to script this somehow, that workaround would be just fine for myself. Lid open/closed, power via the 201344 or direct via other TB-PD port has no impact. Here's hoping for a bugfix in 22.04 or at least a way to script the display configuration. $ cat /sys/class/drm/card0-DP-4/edid | parse-edid Checksum Correct Section "Monitor" Identifier "LG HDR 4K" ModelName "LG HDR 4K" VendorName "GSM" # Monitor Manufactured week 5 of 2021 # EDID version 1.4 # Digital Display DisplaySize 600 340 Gamma 2.20 Option "DPMS" "true" Horizsync 30-135 VertRefresh 56-61 # Maximum pixel clock is 560MHz #Not giving standard mode: 1152x864, 60Hz #Not giving standard mode: 1280x1024, 60Hz #Not giving standard mode: 1280x720, 60Hz #Not giving standard mode: 1600x900, 60Hz #Not giving standard mode: 1920x1080, 60Hz #Not giving standard mode: 1280x800, 60Hz #Extension block found. Parsing... Modeline "Mode 6" 148.50 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync Modeline "Mode 0" 519.38 3840 3864 3880 3896 2160 2214 2219 +hsync -vsync Modeline "Mode 1" 266.64 3840 3848 3992 4000 2160 2214 2219 +hsync -vsync Modeline "Mode 2" 148.500 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync Modeline "Mode 3" 74.250 1280 1390 1420 1650 720 725 730 750 +hsync +vsync Modeline "Mode 4" 27.027 720 736 798 858 480 489 495 525 -hsync -vsync Modeline "Mode 5" 25.200 640 656 752 800 480 490 492 525 -hsync -vsync Modeline "Mode 7" 241.50 2560 2608 2640 2720 1440 1443 1448 1481 +hsync -vsync Option "PreferredMode" "Mode 6" EndSection ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- [i915] Dual DP 4K @60Hz requires toggling to 30Hz and back to 60Hz https://bugs.launchpad.net/bugs/1968235 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1964427] Re: [Security] CVE-2022-0847 lib/iov_iter: initialize "flags" in new pipe_buffer
This was fixed in affected kernels in
https://ubuntu.com/security/notices/USN-5317-1 and
https://ubuntu.com/security/notices/USN-5362-1
** Package changed: ubuntu => linux (Ubuntu)
** Changed in: linux (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1964427
Title:
[Security] CVE-2022-0847 lib/iov_iter: initialize "flags" in new
pipe_buffer
Status in intel:
New
Status in linux package in Ubuntu:
Fix Released
Bug description:
[Feature Description]
CVE-2022-0847
A critical linux kernel vulnerability has been found, which exists since
Linux kernel v5.8 or later.
If linux kernel has this commit f6dd975583bd ("pipe: merge
anon_pipe_buf*_ops"), please backport this patch:
9d2231c5d74e13b2a0546fee6737ee4446017903(“lib/iov_iter: initialize "flags" in
new pipe_buffer”) to fix.
Please note: This commit f6dd975583bd did not introduce the bug, it just made
it easier to exploit.
The vulnerability has been fixed in linux kernel 5.16.11, 5.15.25 and
5.10.102.
For more details see:
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-0847
Commit: 9d2231c5d74e13b2a0546fee6737ee4446017903
git tag --contains 9d2231c5d74e13b2a0546fee6737ee4446017903
v5.17-rc6
Commit:f6dd975583bd
git tag --contains f6dd975583bd
v5.10
Target Kernel: 5.17
Target Release: 22.10/22.04/Others
[HW/SW Information]
Bug fix for vulnerability
[Business Justification]
Function improvement
To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1964427/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-azure-cvm/5.4.0.1076.73)
All autopkgtests for the newly accepted linux-meta-azure-cvm (5.4.0.1076.73) for focal have finished running. The following regressions have been reported in tests triggered by the package: snapd/2.54.3+20.04.1ubuntu0.2 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#linux-meta-azure-cvm [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packing resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1964427] [NEW] [Security] CVE-2022-0847 lib/iov_iter: initialize "flags" in new pipe_buffer
*** This bug is a security vulnerability ***
You have been subscribed to a public security bug:
[Feature Description]
CVE-2022-0847
A critical linux kernel vulnerability has been found, which exists since Linux
kernel v5.8 or later.
If linux kernel has this commit f6dd975583bd ("pipe: merge
anon_pipe_buf*_ops"), please backport this patch:
9d2231c5d74e13b2a0546fee6737ee4446017903(“lib/iov_iter: initialize "flags" in
new pipe_buffer”) to fix.
Please note: This commit f6dd975583bd did not introduce the bug, it just made
it easier to exploit.
The vulnerability has been fixed in linux kernel 5.16.11, 5.15.25 and 5.10.102.
For more details see:
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-0847
Commit: 9d2231c5d74e13b2a0546fee6737ee4446017903
git tag --contains 9d2231c5d74e13b2a0546fee6737ee4446017903
v5.17-rc6
Commit:f6dd975583bd
git tag --contains f6dd975583bd
v5.10
Target Kernel: 5.17
Target Release: 22.10/22.04/Others
[HW/SW Information]
Bug fix for vulnerability
[Business Justification]
Function improvement
** Affects: intel
Importance: Undecided
Status: New
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Fix Released
** Tags: intel-kernel-22.10
--
[Security] CVE-2022-0847 lib/iov_iter: initialize "flags" in new pipe_buffer
https://bugs.launchpad.net/bugs/1964427
You received this bug notification because you are a member of Kernel Packages,
which is subscribed to linux in Ubuntu.
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-gcp-5.4/5.4.0.1071.55)
All autopkgtests for the newly accepted linux-meta-gcp-5.4 (5.4.0.1071.55) for bionic have finished running. The following regressions have been reported in tests triggered by the package: r8168/8.045.08-2ubuntu1 (amd64) snapd/2.54.3+18.04.2ubuntu0.2 (amd64) dpdk/17.11.10-0ubuntu0.1 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-meta-gcp-5.4 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packing resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1968631] Re: regression in jammy kernel 5.15 for module ath9k
Reproduced with the daily live iso to avoid loading out of tree module, installing qemu-system and loading the kvm module triggers the issue as well. -- 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/1968631 Title: regression in jammy kernel 5.15 for module ath9k Status in linux package in Ubuntu: Confirmed Bug description: wireless connection is unstable with kernel 5.15 in jammy release. the following line is in my log, ath: phy0: DMA failed to stop in 10 ms AR_CR=0x0024 AR_DIAG_SW=0x0220 DMADBG_7=0x6100 the bug appears to no longer be present in kernel 5.17.2 from the mainline kernel ppa. lsb_release -rd output: Description: Ubuntu Jammy Jellyfish (development branch) Release: 22.04 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-25-generic 5.15.0-25.25 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: david 1871 F pulseaudio /dev/snd/controlC1: david 1871 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Apr 11 18:05:36 2022 InstallationDate: Installed on 2022-02-01 (69 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: ASUSTeK COMPUTER INC. X550LA ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic root=UUID=eb3fe525-e2d6-4de4-aa48-57ebb0fa0881 ro libata.noacpi=1 quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-25-generic N/A linux-backports-modules-5.15.0-25-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-04-09 (2 days ago) dmi.bios.date: 05/14/2014 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X550LA.508 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X550LA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX550LA.508:bd05/14/2014:br4.6:svnASUSTeKCOMPUTERINC.:pnX550LA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550LA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:skuASUS-NotebookSKU: dmi.product.family: X dmi.product.name: X550LA dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1968631/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1968475] Re: Fix broken HDMI audio on AMD PRO VII after S3
** Tags added: originate-from-1967711 ** Tags added: somerville -- 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/1968475 Title: Fix broken HDMI audio on AMD PRO VII after S3 Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.14 source package in Focal: Confirmed Status in linux source package in Jammy: Confirmed Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: [Impact] DP/HDMI audio on AMD PRO VII stops working after S3. [Fix] Ensure HDA function is suspended before ASIC reset so the subsequent resume can be carried out successfully. [Test] With the patch applied, DP/HDMI audio continues to work after S3. [Where problems could occur] The suspend_noirq phase should not trigger any interrupt, so if amdgpu_asic_reset() somehow raised IRQ, it can break the system. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1968475/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1968564] Re: linux-azure-cvm doesn't currently support arm64
This bug is awaiting verification that the linux-azure- cvm/5.4.0-1076.79+cvm1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification- done-focal'. If the problem still exists, change the tag 'verification- needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure-cvm in Ubuntu. https://bugs.launchpad.net/bugs/1968564 Title: linux-azure-cvm doesn't currently support arm64 Status in linux-azure-cvm package in Ubuntu: New Status in linux-azure-cvm source package in Focal: New Bug description: [Impact] The current linux-azure-cvm doesn't need to support arm64. Ensure we skip the arm64 changes from the base kernel. [Test Plan] linux-azure-cvm doesn't need to produce arm64 binaries. [Where problems could occur] It might cause problems during the rebase of linux-azure-cvm on top of linux-azure. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure-cvm/+bug/1968564/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1925421] Re: arm64 support
This bug is awaiting verification that the linux-gcp/5.4.0-1071.76 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1925421 Title: arm64 support Status in linux-gcp package in Ubuntu: New Status in linux-oracle package in Ubuntu: Fix Released Status in linux-oracle-5.4 package in Ubuntu: Invalid Status in linux-oracle-5.8 package in Ubuntu: Invalid Status in linux-gcp source package in Bionic: New Status in linux-oracle source package in Bionic: Invalid Status in linux-oracle-5.4 source package in Bionic: Fix Released Status in linux-oracle-5.8 source package in Bionic: New Status in linux-gcp source package in Focal: New Status in linux-oracle source package in Focal: Fix Released Status in linux-oracle-5.4 source package in Focal: Invalid Status in linux-oracle-5.8 source package in Focal: Fix Released Status in linux-oracle source package in Groovy: Fix Released Status in linux-oracle-5.4 source package in Groovy: Invalid Status in linux-oracle-5.8 source package in Groovy: Fix Committed Status in linux-oracle source package in Hirsute: Fix Released Status in linux-oracle-5.4 source package in Hirsute: Invalid Status in linux-oracle-5.8 source package in Hirsute: Invalid Status in linux-oracle source package in Impish: Fix Released Status in linux-oracle-5.4 source package in Impish: Invalid Status in linux-oracle-5.8 source package in Impish: Invalid Bug description: See https://canonical.lightning.force.com/lightning/r/Case/5003z2BzFG4AAN/view for more info [Impact] No support for arm64 currently [Fix] Add arm64 support, including hardware support patches [Test] Confirm that it boots on desired arm64 hardware, as well as VMs [Regression Potential] This was never working on arm64 so there should be no risk of regression. The requested changes included some refactorings of early memory initialization code (all arches) so this presents a small risk. The changes were tested on arm64 as well amd64. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/1925421/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-hwe-5.4/5.4.0.109.123~18.04.94)
All autopkgtests for the newly accepted linux-meta-hwe-5.4 (5.4.0.109.123~18.04.94) for bionic have finished running. The following regressions have been reported in tests triggered by the package: virtualbox-hwe/5.2.42-dfsg-0~ubuntu1.18.04.1 (amd64) lxc/3.0.3-0ubuntu1~18.04.1 (ppc64el, s390x, amd64) snapd/2.54.3+18.04.2ubuntu0.2 (ppc64el, s390x, amd64, arm64) asic0x/1.0.1-1 (s390x) kpatch/0.5.0-0ubuntu1.1 (amd64) v4l2loopback/0.10.0-1ubuntu1.2 (s390x) acpi-call/1.1.0-4 (ppc64el, s390x) virtualbox/5.2.42-dfsg-0~ubuntu1.18.04.1 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-meta-hwe-5.4 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packing resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1968255] Re: Sudden, unexpected restart of the whole system. Reporting after automatic restart
A whole system restart is likely a kernel bug. Next time it happens, please run: journalctl -b-1 > prevboot.txt and attach the resulting text file here. ** Package changed: gnome-shell (Ubuntu) => linux (Ubuntu) ** 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/1968255 Title: Sudden, unexpected restart of the whole system. Reporting after automatic restart Status in linux package in Ubuntu: Incomplete Bug description: Using browser the system just stopped and restarted. Browser hardware acceleration option was on. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Apr 8 07:25:13 2022 DisplayManager: gdm3 InstallationDate: Installed on 2018-08-02 (1344 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) RelatedPackageVersions: mutter-common 42.0-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-04-07 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1968255/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1968255] [NEW] Sudden, unexpected restart of the whole system. Reporting after automatic restart
You have been subscribed to a public bug: Using browser the system just stopped and restarted. Browser hardware acceleration option was on. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Apr 8 07:25:13 2022 DisplayManager: gdm3 InstallationDate: Installed on 2018-08-02 (1344 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) RelatedPackageVersions: mutter-common 42.0-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-04-07 (0 days ago) ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- Sudden, unexpected restart of the whole system. Reporting after automatic restart https://bugs.launchpad.net/bugs/1968255 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1967274] Re: Screen sometimes can't update on Intel Alder Lake GPUs [Failed to post KMS update: CRTC property (GAMMA_LUT) not found]
** Tags added: originate-from-1968244 somerville
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1967274
Title:
Screen sometimes can't update on Intel Alder Lake GPUs [Failed to post
KMS update: CRTC property (GAMMA_LUT) not found]
Status in Mutter:
Unknown
Status in OEM Priority Project:
New
Status in linux package in Ubuntu:
Triaged
Status in mutter package in Ubuntu:
Triaged
Bug description:
Screen can't turn back on by clicking keyboard after screen off by meta + l
key.
Try to do VT switch can make the screen back, some error poped when I try to
wake up screen.
gnome-shell[1666]: Failed to post KMS update: CRTC property (GAMMA_LUT) not
found
gnome-shell[1666]: Failed to post KMS update: CRTC property (GAMMA_LUT) not
found
gnome-shell[1666]: Failed to post KMS update: drmModeAtomicCommit: Invalid
argument
gnome-shell[1666]: Failed to post KMS update: drmModeAtomicCommit: Invalid
argument
gnome-shell[1666]: Failed to post KMS update: drmModeAtomicCommit: Invalid
argument
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DisplayManager: gdm3
DistroRelease: Ubuntu 22.04
GsettingsChanges:
b'org.gnome.shell' b'welcome-dialog-last-shown-version' b"'42.beta'"
b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]"
b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
b'org.gnome.desktop.privacy' b'report-technical-problems' b'true'
InstallationDate: Installed on 2022-03-31 (0 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326)
Package: gnome-shell 42~beta-1ubuntu3 [origin: unknown]
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
Tags: wayland-session jammy third-party-packages
Uname: Linux 5.15.0-23-generic x86_64
UnreportableReason: This does not seem to be an official Ubuntu package.
Please retry after updating the indexes of available packages, if that does not
work then remove related third party packages and try again.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1967274/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-gkeop-5.4/5.4.0.1039.40~18.04.39)
All autopkgtests for the newly accepted linux-meta-gkeop-5.4 (5.4.0.1039.40~18.04.39) for bionic have finished running. The following regressions have been reported in tests triggered by the package: lxc/3.0.3-0ubuntu1~18.04.1 (amd64) snapd/2.54.3+18.04.2ubuntu0.2 (amd64) kpatch/0.5.0-0ubuntu1.1 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-meta-gkeop-5.4 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packing resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1967848] 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 1967848 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/1967848 Title: FLOGI failure and port state bypassed connecting to 3PAR storage on Ubuntu 18.04.3 Status in linux package in Ubuntu: Incomplete Bug description: This bug is raised as per the suggestion by Jeff Email snapshot: -- File a bug, point me to a patch, and I'll see if I can pull it. Though we'd need more info... for are we talking the 4.15 GA kernel, or the 5.4 kernel? It would be a bit more involved If I have to pull the patch into 4 different kernels in order to get it back into 4.15 to avoid regressions. BUT it's not difficult, assuming any patches are only applied to lpfc. Once it lands in the scsi tree we can start looking, though I'd be more comfy for it to be in linux-next or mainline. I'll also need someone to fill out some info on the bug to create the SRU justification. -- There is an issue in which we are seeing login failure with Ubuntu 18.04.3, inbox driver version 12.0.0.0 but this issue is not seen with Ubuntu 20.04.2 with inbox driver 12.0.0.6. I found that upstream commit id [0a9e9687acaf6ac1198fd41f03d64f8b92e4515e] could potentially fix this issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967848/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1968631] 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/1968631 Title: regression in jammy kernel 5.15 for module ath9k Status in linux package in Ubuntu: Confirmed Bug description: wireless connection is unstable with kernel 5.15 in jammy release. the following line is in my log, ath: phy0: DMA failed to stop in 10 ms AR_CR=0x0024 AR_DIAG_SW=0x0220 DMADBG_7=0x6100 the bug appears to no longer be present in kernel 5.17.2 from the mainline kernel ppa. lsb_release -rd output: Description: Ubuntu Jammy Jellyfish (development branch) Release: 22.04 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-25-generic 5.15.0-25.25 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: david 1871 F pulseaudio /dev/snd/controlC1: david 1871 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Apr 11 18:05:36 2022 InstallationDate: Installed on 2022-02-01 (69 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: ASUSTeK COMPUTER INC. X550LA ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic root=UUID=eb3fe525-e2d6-4de4-aa48-57ebb0fa0881 ro libata.noacpi=1 quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-25-generic N/A linux-backports-modules-5.15.0-25-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-04-09 (2 days ago) dmi.bios.date: 05/14/2014 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X550LA.508 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X550LA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX550LA.508:bd05/14/2014:br4.6:svnASUSTeKCOMPUTERINC.:pnX550LA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550LA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:skuASUS-NotebookSKU: dmi.product.family: X dmi.product.name: X550LA dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1968631/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1967848] Re: FLOGI failure and port state bypassed connecting to 3PAR storage on Ubuntu 18.04.3
** Package changed: ubuntu => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1967848 Title: FLOGI failure and port state bypassed connecting to 3PAR storage on Ubuntu 18.04.3 Status in linux package in Ubuntu: Incomplete Bug description: This bug is raised as per the suggestion by Jeff Email snapshot: -- File a bug, point me to a patch, and I'll see if I can pull it. Though we'd need more info... for are we talking the 4.15 GA kernel, or the 5.4 kernel? It would be a bit more involved If I have to pull the patch into 4 different kernels in order to get it back into 4.15 to avoid regressions. BUT it's not difficult, assuming any patches are only applied to lpfc. Once it lands in the scsi tree we can start looking, though I'd be more comfy for it to be in linux-next or mainline. I'll also need someone to fill out some info on the bug to create the SRU justification. -- There is an issue in which we are seeing login failure with Ubuntu 18.04.3, inbox driver version 12.0.0.0 but this issue is not seen with Ubuntu 20.04.2 with inbox driver 12.0.0.6. I found that upstream commit id [0a9e9687acaf6ac1198fd41f03d64f8b92e4515e] could potentially fix this issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967848/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1967848] [NEW] FLOGI failure and port state bypassed connecting to 3PAR storage on Ubuntu 18.04.3
You have been subscribed to a public bug: This bug is raised as per the suggestion by Jeff Email snapshot: -- File a bug, point me to a patch, and I'll see if I can pull it. Though we'd need more info... for are we talking the 4.15 GA kernel, or the 5.4 kernel? It would be a bit more involved If I have to pull the patch into 4 different kernels in order to get it back into 4.15 to avoid regressions. BUT it's not difficult, assuming any patches are only applied to lpfc. Once it lands in the scsi tree we can start looking, though I'd be more comfy for it to be in linux-next or mainline. I'll also need someone to fill out some info on the bug to create the SRU justification. -- There is an issue in which we are seeing login failure with Ubuntu 18.04.3, inbox driver version 12.0.0.0 but this issue is not seen with Ubuntu 20.04.2 with inbox driver 12.0.0.6. I found that upstream commit id [0a9e9687acaf6ac1198fd41f03d64f8b92e4515e] could potentially fix this issue. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- FLOGI failure and port state bypassed connecting to 3PAR storage on Ubuntu 18.04.3 https://bugs.launchpad.net/bugs/1967848 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1968631] [NEW] regression in jammy kernel 5.15 for module ath9k
Public bug reported: wireless connection is unstable with kernel 5.15 in jammy release. the following line is in my log, ath: phy0: DMA failed to stop in 10 ms AR_CR=0x0024 AR_DIAG_SW=0x0220 DMADBG_7=0x6100 the bug appears to no longer be present in kernel 5.17.2 from the mainline kernel ppa. lsb_release -rd output: Description:Ubuntu Jammy Jellyfish (development branch) Release:22.04 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-25-generic 5.15.0-25.25 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: david 1871 F pulseaudio /dev/snd/controlC1: david 1871 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Apr 11 18:05:36 2022 InstallationDate: Installed on 2022-02-01 (69 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: ASUSTeK COMPUTER INC. X550LA ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic root=UUID=eb3fe525-e2d6-4de4-aa48-57ebb0fa0881 ro libata.noacpi=1 quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-25-generic N/A linux-backports-modules-5.15.0-25-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-04-09 (2 days ago) dmi.bios.date: 05/14/2014 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X550LA.508 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X550LA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX550LA.508:bd05/14/2014:br4.6:svnASUSTeKCOMPUTERINC.:pnX550LA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550LA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:skuASUS-NotebookSKU: dmi.product.family: X dmi.product.name: X550LA dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- 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/1968631 Title: regression in jammy kernel 5.15 for module ath9k Status in linux package in Ubuntu: New Bug description: wireless connection is unstable with kernel 5.15 in jammy release. the following line is in my log, ath: phy0: DMA failed to stop in 10 ms AR_CR=0x0024 AR_DIAG_SW=0x0220 DMADBG_7=0x6100 the bug appears to no longer be present in kernel 5.17.2 from the mainline kernel ppa. lsb_release -rd output: Description: Ubuntu Jammy Jellyfish (development branch) Release: 22.04 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-25-generic 5.15.0-25.25 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: david 1871 F pulseaudio /dev/snd/controlC1: david 1871 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Apr 11 18:05:36 2022 InstallationDate: Installed on 2022-02-01 (69 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: ASUSTeK COMPUTER INC. X550LA ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic root=UUID=eb3fe525-e2d6-4de4-aa48-57ebb0fa0881 ro libata.noacpi=1 quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-25-generic N/A linux-backports-modules-5.15.0-25-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-04-09 (2 days ago) dmi.bios.date: 05/14/2014 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X550LA.508 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X550LA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10
[Kernel-packages] [Bug 1968612] Re: Ubuntu 20.04 Cloud Image: missing nfsd.ko module in linux-kvm
@Andreas: I also had this thought but before changing the kernel flavour I wanted to be sure not to have missed sth. obvious :) @Seve: I completely agree with your opinion. Even if this is a minimal image (as a small starting point) it shouldn't prevent installing such common additional server software as NFS Server is IMHO. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1968612 Title: Ubuntu 20.04 Cloud Image: missing nfsd.ko module in linux-kvm Status in cloud-images: Invalid Status in linux-meta-kvm package in Ubuntu: New Bug description: I just installed the Ubuntu 20.04 LTS minimal cloud image (from here: https://cloud-images.ubuntu.com/minimal/releases/focal/release/) in a Proxmox VM. Then I installed the NFS Server with apt install nfs-server But it fails to start with these errors in journalctl: Apr 10 18:03:55 servername01 systemd[1]: Starting Preprocess NFS configuration... -- Subject: A start job for unit nfs-config.service has begun execution -- Defined-By: systemd -- Support: http://www.ubuntu.com/support -- -- A start job for unit nfs-config.service has begun execution. -- -- The job identifier is 563. Apr 10 18:03:55 servername01 mount[9668]: mount: /proc/fs/nfsd: unknown filesystem type 'nfsd'. Apr 10 18:03:55 servername01 systemd[1]: proc-fs-nfsd.mount: Mount process exited, code=exited, status=32/n/a -- Subject: Unit process exited -- Defined-By: systemd -- Support: http://www.ubuntu.com/support -- -- An n/a= process belonging to unit proc-fs-nfsd.mount has exited. -- -- The process' exit code is 'exited' and its exit status is 32. Apr 10 18:03:55 servername01 systemd[1]: proc-fs-nfsd.mount: Failed with result 'exit-code'. -- Subject: Unit failed -- Defined-By: systemd -- Support: http://www.ubuntu.com/support -- -- The unit proc-fs-nfsd.mount has entered the 'failed' state with result 'exit-code'. Apr 10 18:03:55 servername01 systemd[1]: Failed to mount NFSD configuration filesystem. -- Subject: A start job for unit proc-fs-nfsd.mount has failed -- Defined-By: systemd -- Support: http://www.ubuntu.com/support -- -- A start job for unit proc-fs-nfsd.mount has finished with a failure. -- -- The job identifier is 556 and the job result is failed. Apr 10 18:03:55 servername01 systemd[1]: Dependency failed for NFS Mount Daemon. "mount: /proc/fs/nfsd: unknown filesystem type 'nfsd'." ... So it seems, that the nfsd kernel module is missing: # modprobe nfsd modprobe: FATAL: Module nfsd not found in directory /lib/modules/5.4.0-1061-kvm I can't figure out how to install this for the running kernel. Any idea? To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1968612/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1966194] Re: [Jammy, mlx5, ConnectX-7] add CX7 support for software steering
Thanks Amir. If the test results are the same w/ and w/o these patches, then I assume those tests are regression tests. Are you able to also confirm that the new functionality (CX7 software steering support) is working as expected? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1966194 Title: [Jammy, mlx5, ConnectX-7] add CX7 support for software steering Status in linux package in Ubuntu: Confirmed Bug description: [Impact] Add support for software steering on cx7 [Test Case] configure software steering on cx7 setup run asap testing (reference https://github.com/Mellanox/ovs-tests) [Regression Potential] TBD [Other Info] Feature patchset: All patches are cleanly applied on Jamy master-next beside these two who add minor conflicts due to context difference. net/mlx5: Introduce software defined steering capabilities net/mlx5: DR, Add support for matching on #fixes 624bf42c2e39 net/mlx5: DR, Fix querying eswitch manager vport for ECPF 0aec12d97b20 net/mlx5: DR, Fix slab-out-of-bounds in mlx5_cmd_dr_create_fte 9091b821aaa4 net/mlx5: DR, Handle eswitch manager and uplink vports separately #CX7 SMFS support 6862c787c7e8 net/mlx5: DR, Add support for ConnectX-7 steering 638a07f1090e net/mlx5: DR, Refactor ste_ctx handling for STE v0/1 75a3926ca6a4 net/mlx5: DR, Rename action modify fields to reflect naming in HW spec bdc3ab5795a6 net/mlx5: DR, Fix handling of different actions on the same STE in STEv1 11659ef8d28e net/mlx5: DR, Remove unneeded comments 5c422bfad2fb net/mlx5: DR, Add support for matching on Internet Header Length (IHL) #dependencies: 60dc0ef674ec net/mlx5: VLAN push on RX, pop on TX 8348b71ccd92 net/mlx5: Introduce software defined steering capabilities #depencecies: #SW STEERING DEBUG DUMP aa36c94853b2 net/mlx5: Set SMFS as a default steering mode if device supports it 4ff725e1d4ad net/mlx5: DR, Ignore modify TTL if device doesn't support it cc2295cd54e4 net/mlx5: DR, Improve steering for empty or RX/TX-only matchers f59464e257bd net/mlx5: DR, Add support for matching on geneve_tlv_option_0_exist field 09753babaf46 net/mlx5: DR, Support matching on tunnel headers 0 and 1 8c2b4fee9c4b net/mlx5: DR, Add misc5 to match_param structs 0f2a6c3b9219 net/mlx5: Add misc5 flow table match parameters b54128275ef8 net/mlx5: DR, Warn on failure to destroy objects due to refcount e3a0f40b2f90 net/mlx5: DR, Add support for UPLINK destination type 9222f0b27da2 net/mlx5: DR, Add support for dumping steering info 7766c9b922fe net/mlx5: DR, Add missing reserved fields to dr_match_param 89cdba3224f0 net/mlx5: DR, Add check for flex parser ID value 08fac109f7bb net/mlx5: DR, Rename list field in matcher struct to list_node 32e9bd585307 net/mlx5: DR, Remove unused struct member in matcher c3fb0e280b4c net/mlx5: DR, Fix lower case macro prefix "mlx5_" to "MLX5_" 84dfac39c61f net/mlx5: DR, Fix error flow in creating matcher 58a606dba708 net/mlx5: Introduce new uplink destination type 455832d49666 net/mlx5: DR, Fix check for unsupported fields in match param 9091b821aaa4 net/mlx5: DR, Handle eswitch manager and uplink vports separately #SW STEERING SF 515ce2ffa621 net/mlx5: DR, init_next_match only if needed 5dde00a73048 net/mlx5: DR, Fix typo 'offeset' to 'offset' 1ffd498901c1 net/mlx5: DR, Increase supported num of actions to 32 11a45def2e19 net/mlx5: DR, Add support for SF vports c0e90fc2ccaa net/mlx5: DR, Support csum recalculation flow table on SFs ee1887fb7cdd net/mlx5: DR, Align error messages for failure to obtain vport caps dd4acb2a0954 net/mlx5: DR, Add missing query for vport 0 7ae8ac9a5820 net/mlx5: DR, Replace local WIRE_PORT macro with the existing MLX5_VPORT_UPLINK f9f93bd55ca6 net/mlx5: DR, Fix vport number data type to u16 c228dce26222 net/mlx5: DR, Fix code indentation in dr_ste_v1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1966194/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1964827] Re: zfs-linux upstream at 2.1.4, jammy has 2.1.2
Since the 2.1 branch is itself cherry-picks of updates backported from zfs master, it might make sense to just follow the 2.1 series for jammy, as opposed to re-cherry-picking from the upstream cherry-pick backports to the 2.1? Otherwise, there will be a lot of duplicated work... The zfs-devs appear to be pretty conservative with what they choose to backport... -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1964827 Title: zfs-linux upstream at 2.1.4, jammy has 2.1.2 Status in zfs-linux package in Ubuntu: Triaged Bug description: I know Jammy is in freeze zfs upstream is now at 2.1.3, which has a lovely set of fixes for issues I have noticed (such as zfs complaining when waking for sleep, and also patches to support 5.16 better and also for the support of 5.17.) Please peruse the large number of important patches, which will make supporting this in LTS much easier: https://github.com/openzfs/zfs/pull/13063 I'm running a version of https://launchpad.net/~jonathonf/+archive/ubuntu/zfs built for 2.1.3 on Ubuntu mainline kernel 5.17-rc8 on multiple Jammy-dev systems, and it works beautifully. I have attached the debian dir I put on top of the 2.1.3 source release which I used to generate debs for this release, which I have tested on a server and client desktop x86_64 machine running Ubuntu Jammy 22.04 (as of March 14, 2022). I am having no zfs related issues. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1964827/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1964827] Re: zfs-linux upstream at 2.1.4, jammy has 2.1.2
See https://github.com/openzfs/zfs/commits/zfs-2.1.5-staging -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1964827 Title: zfs-linux upstream at 2.1.4, jammy has 2.1.2 Status in zfs-linux package in Ubuntu: Triaged Bug description: I know Jammy is in freeze zfs upstream is now at 2.1.3, which has a lovely set of fixes for issues I have noticed (such as zfs complaining when waking for sleep, and also patches to support 5.16 better and also for the support of 5.17.) Please peruse the large number of important patches, which will make supporting this in LTS much easier: https://github.com/openzfs/zfs/pull/13063 I'm running a version of https://launchpad.net/~jonathonf/+archive/ubuntu/zfs built for 2.1.3 on Ubuntu mainline kernel 5.17-rc8 on multiple Jammy-dev systems, and it works beautifully. I have attached the debian dir I put on top of the 2.1.3 source release which I used to generate debs for this release, which I have tested on a server and client desktop x86_64 machine running Ubuntu Jammy 22.04 (as of March 14, 2022). I am having no zfs related issues. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1964827/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1967086] Re: MIR: mesa-amber
Override component to main mesa-amber 21.3.7-0ubuntu1 in jammy: universe/graphics -> main libegl-amber0 21.3.7-0ubuntu1 in jammy amd64: universe/libs/optional/100% -> main libegl-amber0 21.3.7-0ubuntu1 in jammy arm64: universe/libs/optional/100% -> main libegl-amber0 21.3.7-0ubuntu1 in jammy armhf: universe/libs/optional/100% -> main libegl-amber0 21.3.7-0ubuntu1 in jammy ppc64el: universe/libs/optional/100% -> main libegl-amber0 21.3.7-0ubuntu1 in jammy riscv64: universe/libs/optional/100% -> main libegl-amber0 21.3.7-0ubuntu1 in jammy s390x: universe/libs/optional/100% -> main libgl1-amber-dri 21.3.7-0ubuntu1 in jammy amd64: universe/libs/optional/100% -> main libgl1-amber-dri 21.3.7-0ubuntu1 in jammy arm64: universe/libs/optional/100% -> main libgl1-amber-dri 21.3.7-0ubuntu1 in jammy armhf: universe/libs/optional/100% -> main libgl1-amber-dri 21.3.7-0ubuntu1 in jammy ppc64el: universe/libs/optional/100% -> main libgl1-amber-dri 21.3.7-0ubuntu1 in jammy riscv64: universe/libs/optional/100% -> main libgl1-amber-dri 21.3.7-0ubuntu1 in jammy s390x: universe/libs/optional/100% -> main libglx-amber0 21.3.7-0ubuntu1 in jammy amd64: universe/libs/optional/100% -> main libglx-amber0 21.3.7-0ubuntu1 in jammy arm64: universe/libs/optional/100% -> main libglx-amber0 21.3.7-0ubuntu1 in jammy armhf: universe/libs/optional/100% -> main libglx-amber0 21.3.7-0ubuntu1 in jammy ppc64el: universe/libs/optional/100% -> main libglx-amber0 21.3.7-0ubuntu1 in jammy riscv64: universe/libs/optional/100% -> main libglx-amber0 21.3.7-0ubuntu1 in jammy s390x: universe/libs/optional/100% -> main 19 publications overridden. ** Changed in: mesa-amber (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to mesa-amber in Ubuntu. https://bugs.launchpad.net/bugs/1967086 Title: MIR: mesa-amber Status in mesa-amber package in Ubuntu: Fix Released Bug description: Hi, This is essentially a renamed mesa 21.3.x, in order to support 'classic' DRI drivers which got removed upstream from 22.0 and up. The amber branch was created as an LTS one to support these old drivers. This only builds what is needed for the classic DRI drivers, nothing else is shipped than what these require. The upstream merge request has more as to why: https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/10557 I doubt there's a need for a thorough MIR process to let this through? It's needed for image builds, or HW support for older GPU's would be lacking. The kernel-packages (?) team is subscribed to the bugs now. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa-amber/+bug/1967086/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1967562] Re: jammy beta (220330) arm iso pxe boot kernel panic on Ampere Mt. Jade
I randomly picked another ARM server, a Cavium ThunderX system, and it also fails to net boot w/ jammy's GRUB, but works fine w/ the patch in comment #16. So this is looking like possibly an architecture-wide issue. I tested on an x86 VM, but I didn't see any of the LoadFile2 messages. I assume (didn't check the code) that LoadFile2 initramfs is disabled there. ** Changed in: grub2-unsigned (Ubuntu) Importance: Undecided => High ** Changed in: linux (Ubuntu) Assignee: dann frazier (dannf) => (unassigned) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1967562 Title: jammy beta (220330) arm iso pxe boot kernel panic on Ampere Mt. Jade Status in grub2-unsigned package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Status in subiquity package in Ubuntu: Invalid Bug description: = Description = Platforms: Ampere Mt. Jade Altra (bizzy), Cavium thunderX crb2s (recht) Image: Jammy Beta (220330) I setup my pxe server to provision jammy beta and got the following kernel panic message after grub stage: log from console log [1.176614] integrity: Couldn't parse dbx signatures: -74^M [1.371630] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)^M [1.379891] CPU: 42 PID: 1 Comm: swapper/0 Not tainted 5.15.0-23-generic #23-Ubuntu^M [1.387535] Hardware name: WIWYNN Mt.Jade Server System B81.030Z1.0007/Mt.Jade Motherboard, BIOS 1.6.20210526 (SCP: 1.06.20210526) 2021/05/26^M [1.400215] Call trace:^M [1.402649] dump_backtrace+0x0/0x1ec^M [1.406310] show_stack+0x24/0x30^M [1.409614] dump_stack_lvl+0x68/0x84^M [1.413271] dump_stack+0x18/0x34^M [1.416573] panic+0x18c/0x39c^M [1.419616] mount_block_root+0x160/0x210^M [1.423622] mount_root+0x12c/0x14c^M [1.427097] prepare_namespace+0x140/0x1a0^M [1.431182] kernel_init_freeable+0x1c8/0x214^M [1.435527] kernel_init+0x30/0x160^M [1.439006] ret_from_fork+0x10/0x20^M [1.442573] SMP: stopping secondary CPUs^M [1.447323] Kernel Offset: 0x55263ee9 from 0x8800^M [1.453404] PHYS_OFFSET: 0x8000^M [1.456879] CPU features: 0x85c1,a3302e42^M [1.461225] Memory Limit: none^M [1.464271] ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) ]---^M = Steps to Reproduce = 1. Followed this guide to setup the pxe server https://discourse.ubuntu.com/t/netbooting-the-live-server-installer-via-uefi-pxe-on-arm-aarch64-arm64-and-x86-64-amd64/19240 with the jammy beta image (220330) http://cdimage.ubuntu.com/ubuntu-server/daily-live/20220330/jammy-live-server-arm64.iso 1-1. You may use this script to perform the set-up https://github.com/tai271828/ubuntu-autoinstall-pxe-server by invoking: `sudo ./setup-pxe-server.sh --url http://cdimage.ubuntu.com/ubuntu-server/daily-live/20220330/jammy-live-server-arm64.iso` 2. Boot the system via PXE 3. Select Ubuntu at Grub menu = Expected Result = The image is loaded to the system locally via PXE, and subiquity is launched = Actual Result = Console log simply shows nothing for 10 seconds and then the kernel panic shows up. = Additional Information = - If we install via the virtual CD of the server, subiquity could be launched and the installation process completes successfully. - MAAS could deploy Jammy to the Mt. Jade server as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2-unsigned/+bug/1967562/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1964827] Re: zfs-linux upstream at 2.1.4, jammy has 2.1.2
** Information type changed from Public to Public Security -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1964827 Title: zfs-linux upstream at 2.1.4, jammy has 2.1.2 Status in zfs-linux package in Ubuntu: Triaged Bug description: I know Jammy is in freeze zfs upstream is now at 2.1.3, which has a lovely set of fixes for issues I have noticed (such as zfs complaining when waking for sleep, and also patches to support 5.16 better and also for the support of 5.17.) Please peruse the large number of important patches, which will make supporting this in LTS much easier: https://github.com/openzfs/zfs/pull/13063 I'm running a version of https://launchpad.net/~jonathonf/+archive/ubuntu/zfs built for 2.1.3 on Ubuntu mainline kernel 5.17-rc8 on multiple Jammy-dev systems, and it works beautifully. I have attached the debian dir I put on top of the 2.1.3 source release which I used to generate debs for this release, which I have tested on a server and client desktop x86_64 machine running Ubuntu Jammy 22.04 (as of March 14, 2022). I am having no zfs related issues. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1964827/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1968387] Re: ubuntu-fan fails to set https_proxy when running the "docker" dep8 test on autopkgtest.u.c
** Merge proposal linked: https://code.launchpad.net/~sergiodj/ubuntu/+source/ubuntu-fan/+git/ubuntu-fan/+merge/419232 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to ubuntu-fan in Ubuntu. https://bugs.launchpad.net/bugs/1968387 Title: ubuntu-fan fails to set https_proxy when running the "docker" dep8 test on autopkgtest.u.c Status in ubuntu-fan package in Ubuntu: In Progress Status in ubuntu-fan source package in Focal: In Progress Status in ubuntu-fan source package in Impish: In Progress Status in ubuntu-fan source package in Jammy: In Progress Bug description: [Impact] ubuntu-fan currently fails to properly set the $https_proxy variable when running the "docker" dep8 test on autopkgtest.u.c. At the time of this writing this is a major problem on Focal because ubuntu-fan is blocking docker.io from migrating: Error response from daemon: Get "https://registry-1.docker.io/v2/": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers) FAIL: error on docker test local docker test: docker pull ubuntu failure! local docker test: skipping test. autopkgtest [03:44:06]: test docker: ---] autopkgtest [03:44:06]: test docker: - - - - - - - - - - results - - - - - - - - - - docker FAIL non-zero exit status 1 [Test Plan] The dep8 test (named "docker") shall pass when performed in the autopkgtest.u.c. infra. [Where problems could occur] This is a very specific issue on how a dep8 test from the package interacts with autopkgtest.u.c, so there is really no way that a regression can be caused by fixing this problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-fan/+bug/1968387/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1968612] Re: Ubuntu 20.04 Cloud Image: missing nfsd.ko module in linux-kvm
steve - that's a fair point pinging kernel -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1968612 Title: Ubuntu 20.04 Cloud Image: missing nfsd.ko module in linux-kvm Status in cloud-images: Invalid Status in linux-meta-kvm package in Ubuntu: New Bug description: I just installed the Ubuntu 20.04 LTS minimal cloud image (from here: https://cloud-images.ubuntu.com/minimal/releases/focal/release/) in a Proxmox VM. Then I installed the NFS Server with apt install nfs-server But it fails to start with these errors in journalctl: Apr 10 18:03:55 servername01 systemd[1]: Starting Preprocess NFS configuration... -- Subject: A start job for unit nfs-config.service has begun execution -- Defined-By: systemd -- Support: http://www.ubuntu.com/support -- -- A start job for unit nfs-config.service has begun execution. -- -- The job identifier is 563. Apr 10 18:03:55 servername01 mount[9668]: mount: /proc/fs/nfsd: unknown filesystem type 'nfsd'. Apr 10 18:03:55 servername01 systemd[1]: proc-fs-nfsd.mount: Mount process exited, code=exited, status=32/n/a -- Subject: Unit process exited -- Defined-By: systemd -- Support: http://www.ubuntu.com/support -- -- An n/a= process belonging to unit proc-fs-nfsd.mount has exited. -- -- The process' exit code is 'exited' and its exit status is 32. Apr 10 18:03:55 servername01 systemd[1]: proc-fs-nfsd.mount: Failed with result 'exit-code'. -- Subject: Unit failed -- Defined-By: systemd -- Support: http://www.ubuntu.com/support -- -- The unit proc-fs-nfsd.mount has entered the 'failed' state with result 'exit-code'. Apr 10 18:03:55 servername01 systemd[1]: Failed to mount NFSD configuration filesystem. -- Subject: A start job for unit proc-fs-nfsd.mount has failed -- Defined-By: systemd -- Support: http://www.ubuntu.com/support -- -- A start job for unit proc-fs-nfsd.mount has finished with a failure. -- -- The job identifier is 556 and the job result is failed. Apr 10 18:03:55 servername01 systemd[1]: Dependency failed for NFS Mount Daemon. "mount: /proc/fs/nfsd: unknown filesystem type 'nfsd'." ... So it seems, that the nfsd kernel module is missing: # modprobe nfsd modprobe: FATAL: Module nfsd not found in directory /lib/modules/5.4.0-1061-kvm I can't figure out how to install this for the running kernel. Any idea? To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1968612/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1968612] Re: Ubuntu 20.04 Cloud Image: missing nfsd.ko module in linux-kvm
I question whether it's correct to dismiss this as invalid on the basis that this is a minimal image. In general, my expectation is that the minimal image is a suitable base for deploying any of the software in Ubuntu, it's just a smaller starting point. And the purpose of having a separate KVM kernel flavor is to provide the best kernel for booting in VMs, excluding hardware-specific drivers that are necessarily irrelevant when running on a reasonably-configured VM. It does not obviously follow from either of these points that the nfsd driver should be excluded from the KVM kernel. It's as reasonable to run an nfs server in a VM as it is anywhere else. And installing the nfs-server package in a minimal VM shouldn't fail with obscure errors. ** Changed in: linux-meta-kvm (Ubuntu) Status: Invalid => New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1968612 Title: Ubuntu 20.04 Cloud Image: missing nfsd.ko module in linux-kvm Status in cloud-images: Invalid Status in linux-meta-kvm package in Ubuntu: New Bug description: I just installed the Ubuntu 20.04 LTS minimal cloud image (from here: https://cloud-images.ubuntu.com/minimal/releases/focal/release/) in a Proxmox VM. Then I installed the NFS Server with apt install nfs-server But it fails to start with these errors in journalctl: Apr 10 18:03:55 servername01 systemd[1]: Starting Preprocess NFS configuration... -- Subject: A start job for unit nfs-config.service has begun execution -- Defined-By: systemd -- Support: http://www.ubuntu.com/support -- -- A start job for unit nfs-config.service has begun execution. -- -- The job identifier is 563. Apr 10 18:03:55 servername01 mount[9668]: mount: /proc/fs/nfsd: unknown filesystem type 'nfsd'. Apr 10 18:03:55 servername01 systemd[1]: proc-fs-nfsd.mount: Mount process exited, code=exited, status=32/n/a -- Subject: Unit process exited -- Defined-By: systemd -- Support: http://www.ubuntu.com/support -- -- An n/a= process belonging to unit proc-fs-nfsd.mount has exited. -- -- The process' exit code is 'exited' and its exit status is 32. Apr 10 18:03:55 servername01 systemd[1]: proc-fs-nfsd.mount: Failed with result 'exit-code'. -- Subject: Unit failed -- Defined-By: systemd -- Support: http://www.ubuntu.com/support -- -- The unit proc-fs-nfsd.mount has entered the 'failed' state with result 'exit-code'. Apr 10 18:03:55 servername01 systemd[1]: Failed to mount NFSD configuration filesystem. -- Subject: A start job for unit proc-fs-nfsd.mount has failed -- Defined-By: systemd -- Support: http://www.ubuntu.com/support -- -- A start job for unit proc-fs-nfsd.mount has finished with a failure. -- -- The job identifier is 556 and the job result is failed. Apr 10 18:03:55 servername01 systemd[1]: Dependency failed for NFS Mount Daemon. "mount: /proc/fs/nfsd: unknown filesystem type 'nfsd'." ... So it seems, that the nfsd kernel module is missing: # modprobe nfsd modprobe: FATAL: Module nfsd not found in directory /lib/modules/5.4.0-1061-kvm I can't figure out how to install this for the running kernel. Any idea? To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1968612/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1968617] [NEW] uc22 no serial console on rpi
Public bug reported: The current uc22 beta image (2022-04-11) shows nothing on the serial console during boot, nor does it allow console-conf over serial console. I've double checked with jammy, focal, and uc20 and my serial console is working fine with all of those images on this same device (an rpi3b+) but with uc22 I don't see any output at all. Kernel version: Linux ubuntu 5.15.0-1005-raspi #5-Ubuntu SMP PREEMPT Mon Apr 4 12:25:49 UTC 2022 armv7l armv7l armv7l GNU/Linux One thing I did notice, is that I do not see a ttyS0 device, which appears to be what it's expecting to use for the serial console ** Affects: linux-raspi (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/1968617 Title: uc22 no serial console on rpi Status in linux-raspi package in Ubuntu: New Bug description: The current uc22 beta image (2022-04-11) shows nothing on the serial console during boot, nor does it allow console-conf over serial console. I've double checked with jammy, focal, and uc20 and my serial console is working fine with all of those images on this same device (an rpi3b+) but with uc22 I don't see any output at all. Kernel version: Linux ubuntu 5.15.0-1005-raspi #5-Ubuntu SMP PREEMPT Mon Apr 4 12:25:49 UTC 2022 armv7l armv7l armv7l GNU/Linux One thing I did notice, is that I do not see a ttyS0 device, which appears to be what it's expecting to use for the serial console To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1968617/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1968612] Re: Ubuntu 20.04 Cloud Image: missing nfsd.ko module in linux-kvm
closing this but please feel free to comment if you have additional questions or concerns ** Changed in: cloud-images Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1968612 Title: Ubuntu 20.04 Cloud Image: missing nfsd.ko module in linux-kvm Status in cloud-images: Invalid Status in linux-meta-kvm package in Ubuntu: Invalid Bug description: I just installed the Ubuntu 20.04 LTS minimal cloud image (from here: https://cloud-images.ubuntu.com/minimal/releases/focal/release/) in a Proxmox VM. Then I installed the NFS Server with apt install nfs-server But it fails to start with these errors in journalctl: Apr 10 18:03:55 servername01 systemd[1]: Starting Preprocess NFS configuration... -- Subject: A start job for unit nfs-config.service has begun execution -- Defined-By: systemd -- Support: http://www.ubuntu.com/support -- -- A start job for unit nfs-config.service has begun execution. -- -- The job identifier is 563. Apr 10 18:03:55 servername01 mount[9668]: mount: /proc/fs/nfsd: unknown filesystem type 'nfsd'. Apr 10 18:03:55 servername01 systemd[1]: proc-fs-nfsd.mount: Mount process exited, code=exited, status=32/n/a -- Subject: Unit process exited -- Defined-By: systemd -- Support: http://www.ubuntu.com/support -- -- An n/a= process belonging to unit proc-fs-nfsd.mount has exited. -- -- The process' exit code is 'exited' and its exit status is 32. Apr 10 18:03:55 servername01 systemd[1]: proc-fs-nfsd.mount: Failed with result 'exit-code'. -- Subject: Unit failed -- Defined-By: systemd -- Support: http://www.ubuntu.com/support -- -- The unit proc-fs-nfsd.mount has entered the 'failed' state with result 'exit-code'. Apr 10 18:03:55 servername01 systemd[1]: Failed to mount NFSD configuration filesystem. -- Subject: A start job for unit proc-fs-nfsd.mount has failed -- Defined-By: systemd -- Support: http://www.ubuntu.com/support -- -- A start job for unit proc-fs-nfsd.mount has finished with a failure. -- -- The job identifier is 556 and the job result is failed. Apr 10 18:03:55 servername01 systemd[1]: Dependency failed for NFS Mount Daemon. "mount: /proc/fs/nfsd: unknown filesystem type 'nfsd'." ... So it seems, that the nfsd kernel module is missing: # modprobe nfsd modprobe: FATAL: Module nfsd not found in directory /lib/modules/5.4.0-1061-kvm I can't figure out how to install this for the running kernel. Any idea? To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1968612/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1968612] Re: Ubuntu 20.04 Cloud Image: missing nfsd.ko module in linux-kvm
indeed, this image has a minimal kernel you can either install the generic kernel, or use the full ubuntu server image which contains the generic kernel, which will have the necessary support ** Also affects: cloud-images Importance: Undecided Status: New ** Changed in: linux-meta-kvm (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1968612 Title: Ubuntu 20.04 Cloud Image: missing nfsd.ko module in linux-kvm Status in cloud-images: Invalid Status in linux-meta-kvm package in Ubuntu: Invalid Bug description: I just installed the Ubuntu 20.04 LTS minimal cloud image (from here: https://cloud-images.ubuntu.com/minimal/releases/focal/release/) in a Proxmox VM. Then I installed the NFS Server with apt install nfs-server But it fails to start with these errors in journalctl: Apr 10 18:03:55 servername01 systemd[1]: Starting Preprocess NFS configuration... -- Subject: A start job for unit nfs-config.service has begun execution -- Defined-By: systemd -- Support: http://www.ubuntu.com/support -- -- A start job for unit nfs-config.service has begun execution. -- -- The job identifier is 563. Apr 10 18:03:55 servername01 mount[9668]: mount: /proc/fs/nfsd: unknown filesystem type 'nfsd'. Apr 10 18:03:55 servername01 systemd[1]: proc-fs-nfsd.mount: Mount process exited, code=exited, status=32/n/a -- Subject: Unit process exited -- Defined-By: systemd -- Support: http://www.ubuntu.com/support -- -- An n/a= process belonging to unit proc-fs-nfsd.mount has exited. -- -- The process' exit code is 'exited' and its exit status is 32. Apr 10 18:03:55 servername01 systemd[1]: proc-fs-nfsd.mount: Failed with result 'exit-code'. -- Subject: Unit failed -- Defined-By: systemd -- Support: http://www.ubuntu.com/support -- -- The unit proc-fs-nfsd.mount has entered the 'failed' state with result 'exit-code'. Apr 10 18:03:55 servername01 systemd[1]: Failed to mount NFSD configuration filesystem. -- Subject: A start job for unit proc-fs-nfsd.mount has failed -- Defined-By: systemd -- Support: http://www.ubuntu.com/support -- -- A start job for unit proc-fs-nfsd.mount has finished with a failure. -- -- The job identifier is 556 and the job result is failed. Apr 10 18:03:55 servername01 systemd[1]: Dependency failed for NFS Mount Daemon. "mount: /proc/fs/nfsd: unknown filesystem type 'nfsd'." ... So it seems, that the nfsd kernel module is missing: # modprobe nfsd modprobe: FATAL: Module nfsd not found in directory /lib/modules/5.4.0-1061-kvm I can't figure out how to install this for the running kernel. Any idea? To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1968612/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1968387] Re: ubuntu-fan fails to set https_proxy when running the "docker" dep8 test on autopkgtest.u.c
** Also affects: ubuntu-fan (Ubuntu Impish) Importance: Undecided Status: New ** Changed in: ubuntu-fan (Ubuntu Impish) Status: New => In Progress ** Changed in: ubuntu-fan (Ubuntu Impish) Importance: Undecided => Medium ** Changed in: ubuntu-fan (Ubuntu Impish) Assignee: (unassigned) => Sergio Durigan Junior (sergiodj) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to ubuntu-fan in Ubuntu. https://bugs.launchpad.net/bugs/1968387 Title: ubuntu-fan fails to set https_proxy when running the "docker" dep8 test on autopkgtest.u.c Status in ubuntu-fan package in Ubuntu: In Progress Status in ubuntu-fan source package in Focal: In Progress Status in ubuntu-fan source package in Impish: In Progress Status in ubuntu-fan source package in Jammy: In Progress Bug description: [Impact] ubuntu-fan currently fails to properly set the $https_proxy variable when running the "docker" dep8 test on autopkgtest.u.c. At the time of this writing this is a major problem on Focal because ubuntu-fan is blocking docker.io from migrating: Error response from daemon: Get "https://registry-1.docker.io/v2/": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers) FAIL: error on docker test local docker test: docker pull ubuntu failure! local docker test: skipping test. autopkgtest [03:44:06]: test docker: ---] autopkgtest [03:44:06]: test docker: - - - - - - - - - - results - - - - - - - - - - docker FAIL non-zero exit status 1 [Test Plan] The dep8 test (named "docker") shall pass when performed in the autopkgtest.u.c. infra. [Where problems could occur] This is a very specific issue on how a dep8 test from the package interacts with autopkgtest.u.c, so there is really no way that a regression can be caused by fixing this problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-fan/+bug/1968387/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1968612] Re: Ubuntu 20.04 Cloud Image: NFS Server not working
I see you are running the kvm kernel flavor, and indeed I don't see the nfsd.ko module, nor a package named like linux-modules-extra-kvm, which, in the case of the other cloud kernels, does have nfsd.ko. I'm changing this bug to be about the linux kernel, as they can answer best why nfsd.ko is not present, and in the meantime I suggest you install another kernel flavor, like perhaps linux-image-virtual. ** Package changed: nfs-utils (Ubuntu) => linux-meta-kvm (Ubuntu) ** Summary changed: - Ubuntu 20.04 Cloud Image: NFS Server not working + Ubuntu 20.04 Cloud Image: missing nfsd.ko module in linux-kvm -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1968612 Title: Ubuntu 20.04 Cloud Image: missing nfsd.ko module in linux-kvm Status in linux-meta-kvm package in Ubuntu: New Bug description: I just installed the Ubuntu 20.04 LTS minimal cloud image (from here: https://cloud-images.ubuntu.com/minimal/releases/focal/release/) in a Proxmox VM. Then I installed the NFS Server with apt install nfs-server But it fails to start with these errors in journalctl: Apr 10 18:03:55 servername01 systemd[1]: Starting Preprocess NFS configuration... -- Subject: A start job for unit nfs-config.service has begun execution -- Defined-By: systemd -- Support: http://www.ubuntu.com/support -- -- A start job for unit nfs-config.service has begun execution. -- -- The job identifier is 563. Apr 10 18:03:55 servername01 mount[9668]: mount: /proc/fs/nfsd: unknown filesystem type 'nfsd'. Apr 10 18:03:55 servername01 systemd[1]: proc-fs-nfsd.mount: Mount process exited, code=exited, status=32/n/a -- Subject: Unit process exited -- Defined-By: systemd -- Support: http://www.ubuntu.com/support -- -- An n/a= process belonging to unit proc-fs-nfsd.mount has exited. -- -- The process' exit code is 'exited' and its exit status is 32. Apr 10 18:03:55 servername01 systemd[1]: proc-fs-nfsd.mount: Failed with result 'exit-code'. -- Subject: Unit failed -- Defined-By: systemd -- Support: http://www.ubuntu.com/support -- -- The unit proc-fs-nfsd.mount has entered the 'failed' state with result 'exit-code'. Apr 10 18:03:55 servername01 systemd[1]: Failed to mount NFSD configuration filesystem. -- Subject: A start job for unit proc-fs-nfsd.mount has failed -- Defined-By: systemd -- Support: http://www.ubuntu.com/support -- -- A start job for unit proc-fs-nfsd.mount has finished with a failure. -- -- The job identifier is 556 and the job result is failed. Apr 10 18:03:55 servername01 systemd[1]: Dependency failed for NFS Mount Daemon. "mount: /proc/fs/nfsd: unknown filesystem type 'nfsd'." ... So it seems, that the nfsd kernel module is missing: # modprobe nfsd modprobe: FATAL: Module nfsd not found in directory /lib/modules/5.4.0-1061-kvm I can't figure out how to install this for the running kernel. Any idea? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-kvm/+bug/1968612/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1968612] [NEW] Ubuntu 20.04 Cloud Image: NFS Server not working
You have been subscribed to a public bug: I just installed the Ubuntu 20.04 LTS minimal cloud image (from here: https://cloud-images.ubuntu.com/minimal/releases/focal/release/) in a Proxmox VM. Then I installed the NFS Server with apt install nfs-server But it fails to start with these errors in journalctl: Apr 10 18:03:55 servername01 systemd[1]: Starting Preprocess NFS configuration... -- Subject: A start job for unit nfs-config.service has begun execution -- Defined-By: systemd -- Support: http://www.ubuntu.com/support -- -- A start job for unit nfs-config.service has begun execution. -- -- The job identifier is 563. Apr 10 18:03:55 servername01 mount[9668]: mount: /proc/fs/nfsd: unknown filesystem type 'nfsd'. Apr 10 18:03:55 servername01 systemd[1]: proc-fs-nfsd.mount: Mount process exited, code=exited, status=32/n/a -- Subject: Unit process exited -- Defined-By: systemd -- Support: http://www.ubuntu.com/support -- -- An n/a= process belonging to unit proc-fs-nfsd.mount has exited. -- -- The process' exit code is 'exited' and its exit status is 32. Apr 10 18:03:55 servername01 systemd[1]: proc-fs-nfsd.mount: Failed with result 'exit-code'. -- Subject: Unit failed -- Defined-By: systemd -- Support: http://www.ubuntu.com/support -- -- The unit proc-fs-nfsd.mount has entered the 'failed' state with result 'exit-code'. Apr 10 18:03:55 servername01 systemd[1]: Failed to mount NFSD configuration filesystem. -- Subject: A start job for unit proc-fs-nfsd.mount has failed -- Defined-By: systemd -- Support: http://www.ubuntu.com/support -- -- A start job for unit proc-fs-nfsd.mount has finished with a failure. -- -- The job identifier is 556 and the job result is failed. Apr 10 18:03:55 servername01 systemd[1]: Dependency failed for NFS Mount Daemon. "mount: /proc/fs/nfsd: unknown filesystem type 'nfsd'." ... So it seems, that the nfsd kernel module is missing: # modprobe nfsd modprobe: FATAL: Module nfsd not found in directory /lib/modules/5.4.0-1061-kvm I can't figure out how to install this for the running kernel. Any idea? ** Affects: linux-meta-kvm (Ubuntu) Importance: Undecided Status: New -- Ubuntu 20.04 Cloud Image: NFS Server not working https://bugs.launchpad.net/bugs/1968612 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-kvm 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 1786013] Autopkgtest regression report (linux-meta/5.4.0.109.113)
All autopkgtests for the newly accepted linux-meta (5.4.0.109.113) for focal have finished running. The following regressions have been reported in tests triggered by the package: snapd/2.54.3+20.04.1ubuntu0.2 (s390x, arm64, amd64, ppc64el) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#linux-meta [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packing resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-bluefield/5.4.0.1033.34)
All autopkgtests for the newly accepted linux-meta-bluefield (5.4.0.1033.34) for focal have finished running. The following regressions have been reported in tests triggered by the package: lxc/unknown (arm64) langford/unknown (arm64) iptables-netflow/unknown (arm64) snapd/unknown (arm64) openafs/unknown (arm64) linux-bluefield/unknown (arm64) gost-crypto/unknown (arm64) xtables-addons/unknown (arm64) west-chamber/unknown (arm64) mali-midgard/unknown (arm64) ddcci-driver-linux/unknown (arm64) bbswitch/unknown (arm64) r8168/unknown (arm64) glibc/unknown (arm64) jool/unknown (arm64) lime-forensics/unknown (arm64) openrazer/unknown (arm64) acpi-call/unknown (arm64) dm-writeboost/unknown (arm64) adv-17v35x/unknown (arm64) nat-rtsp/unknown (arm64) wireguard-linux-compat/unknown (arm64) dpdk/unknown (arm64) lttng-modules/unknown (arm64) fwts/unknown (arm64) zfs-linux/unknown (arm64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#linux-meta-bluefield [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packing resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1968387] Re: ubuntu-fan fails to set https_proxy when running the "docker" dep8 test on autopkgtest.u.c
The Focal package has been uploaded. I'm waiting on apw's reply to upload the Jammy package. ** Description changed: + [Impact] + ubuntu-fan currently fails to properly set the $https_proxy variable when running the "docker" dep8 test on autopkgtest.u.c. At the time of this writing this is a major problem on Focal because ubuntu-fan is blocking docker.io from migrating: Error response from daemon: Get "https://registry-1.docker.io/v2/": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers) FAIL: error on docker test local docker test: docker pull ubuntu failure! local docker test: skipping test. autopkgtest [03:44:06]: test docker: ---] autopkgtest [03:44:06]: test docker: - - - - - - - - - - results - - - - - - - - - - docker FAIL non-zero exit status 1 + + [Test Plan] + + The dep8 test (named "docker") shall pass when performed in the + autopkgtest.u.c. infra. + + [Where problems could occur] + + This is a very specific issue on how a dep8 test from the package + interacts with autopkgtest.u.c, so there is really no way that a + regression can be caused by fixing this problem. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to ubuntu-fan in Ubuntu. https://bugs.launchpad.net/bugs/1968387 Title: ubuntu-fan fails to set https_proxy when running the "docker" dep8 test on autopkgtest.u.c Status in ubuntu-fan package in Ubuntu: In Progress Status in ubuntu-fan source package in Focal: In Progress Status in ubuntu-fan source package in Jammy: In Progress Bug description: [Impact] ubuntu-fan currently fails to properly set the $https_proxy variable when running the "docker" dep8 test on autopkgtest.u.c. At the time of this writing this is a major problem on Focal because ubuntu-fan is blocking docker.io from migrating: Error response from daemon: Get "https://registry-1.docker.io/v2/": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers) FAIL: error on docker test local docker test: docker pull ubuntu failure! local docker test: skipping test. autopkgtest [03:44:06]: test docker: ---] autopkgtest [03:44:06]: test docker: - - - - - - - - - - results - - - - - - - - - - docker FAIL non-zero exit status 1 [Test Plan] The dep8 test (named "docker") shall pass when performed in the autopkgtest.u.c. infra. [Where problems could occur] This is a very specific issue on how a dep8 test from the package interacts with autopkgtest.u.c, so there is really no way that a regression can be caused by fixing this problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-fan/+bug/1968387/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1967338] Re: linux: CONFIG_SERIAL_8250_MID=y
** Changed in: linux (Ubuntu Jammy) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1967338 Title: linux: CONFIG_SERIAL_8250_MID=y Status in linux package in Ubuntu: Fix Committed Status in linux source package in Jammy: Fix Committed Bug description: SRU Justification [Impact] See discussion at https://lists.ubuntu.com/archives/kernel- team/2022-March/128690.html [Test Plan] Boot with serial console connected [Where things could go wrong] Not really a lot of opportunity for regression To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967338/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1967562] Re: jammy beta (220330) arm iso pxe boot kernel panic on Ampere Mt. Jade
Removing efi-implement-grub_efi_run_image.patch didn't avoid the problem, nor did removing both that and efi-implemented- LoadFile2-initrd-loading-protocol-fo.patch, but that appears to just be because the arm64 code gets migrated to the efi loader code later in the series, basically reintroducing the LoadFile2 support. Instead, I just made the following change, which does avoid the problem: Index: grub2-unsigned-2.06/grub-core/loader/efi/linux.c === --- grub2-unsigned-2.06.orig/grub-core/loader/efi/linux.c +++ grub2-unsigned-2.06/grub-core/loader/efi/linux.c @@ -88,7 +88,7 @@ grub_arch_efi_linux_check_image (struct * LoadFile2 based initrd loading protocol if the image version is >= 1. */ if (optional_header->major_image_version >= 1) -initrd_use_loadfile2 = 1; +initrd_use_loadfile2 = 0; else initrd_use_loadfile2 = 0; -- 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/1967562 Title: jammy beta (220330) arm iso pxe boot kernel panic on Ampere Mt. Jade Status in grub2-unsigned package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Status in subiquity package in Ubuntu: Invalid Bug description: = Description = Platforms: Ampere Mt. Jade Altra (bizzy), Cavium thunderX crb2s (recht) Image: Jammy Beta (220330) I setup my pxe server to provision jammy beta and got the following kernel panic message after grub stage: log from console log [1.176614] integrity: Couldn't parse dbx signatures: -74^M [1.371630] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)^M [1.379891] CPU: 42 PID: 1 Comm: swapper/0 Not tainted 5.15.0-23-generic #23-Ubuntu^M [1.387535] Hardware name: WIWYNN Mt.Jade Server System B81.030Z1.0007/Mt.Jade Motherboard, BIOS 1.6.20210526 (SCP: 1.06.20210526) 2021/05/26^M [1.400215] Call trace:^M [1.402649] dump_backtrace+0x0/0x1ec^M [1.406310] show_stack+0x24/0x30^M [1.409614] dump_stack_lvl+0x68/0x84^M [1.413271] dump_stack+0x18/0x34^M [1.416573] panic+0x18c/0x39c^M [1.419616] mount_block_root+0x160/0x210^M [1.423622] mount_root+0x12c/0x14c^M [1.427097] prepare_namespace+0x140/0x1a0^M [1.431182] kernel_init_freeable+0x1c8/0x214^M [1.435527] kernel_init+0x30/0x160^M [1.439006] ret_from_fork+0x10/0x20^M [1.442573] SMP: stopping secondary CPUs^M [1.447323] Kernel Offset: 0x55263ee9 from 0x8800^M [1.453404] PHYS_OFFSET: 0x8000^M [1.456879] CPU features: 0x85c1,a3302e42^M [1.461225] Memory Limit: none^M [1.464271] ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) ]---^M = Steps to Reproduce = 1. Followed this guide to setup the pxe server https://discourse.ubuntu.com/t/netbooting-the-live-server-installer-via-uefi-pxe-on-arm-aarch64-arm64-and-x86-64-amd64/19240 with the jammy beta image (220330) http://cdimage.ubuntu.com/ubuntu-server/daily-live/20220330/jammy-live-server-arm64.iso 1-1. You may use this script to perform the set-up https://github.com/tai271828/ubuntu-autoinstall-pxe-server by invoking: `sudo ./setup-pxe-server.sh --url http://cdimage.ubuntu.com/ubuntu-server/daily-live/20220330/jammy-live-server-arm64.iso` 2. Boot the system via PXE 3. Select Ubuntu at Grub menu = Expected Result = The image is loaded to the system locally via PXE, and subiquity is launched = Actual Result = Console log simply shows nothing for 10 seconds and then the kernel panic shows up. = Additional Information = - If we install via the virtual CD of the server, subiquity could be launched and the installation process completes successfully. - MAAS could deploy Jammy to the Mt. Jade server as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2-unsigned/+bug/1967562/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1874257] Re: SSH fails with connection timed out - in VPN and hangs here "expecting SSH2_MSG_KEX_ECDH_REPLY" + Ubuntu 16.04.6 LTS
I faced with same issue after changed router from Zyxel Keenetic Lite to Xiaomi A4 Giga Edition. My connection use PPPOE on router. Ubuntu 21.10 and openconnect VPN. -- 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/1874257 Title: SSH fails with connection timed out - in VPN and hangs here "expecting SSH2_MSG_KEX_ECDH_REPLY" + Ubuntu 16.04.6 LTS Status in linux package in Ubuntu: Invalid Status in openconnect package in Ubuntu: Fix Released Status in openssh package in Ubuntu: Invalid Status in openconnect source package in Xenial: Confirmed Bug description: Hello Team, SSH timeout issue, once connect to VPN. Environment == Dell XPS 9570 Ubuntu 16.04.6 Xenial Xerus) kernel - 4.15.0-55-generic $dpkg -l | grep -i openssh ii openssh-client 1:7.2p2-4ubuntu2.8 --> ii openssh-server 1:7.2p2-4ubuntu2.8 ii openssh-sftp-server 1:7.2p2-4ubuntu2.8 VPN tunnel info vpn0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 inet addr:IP P-t-P:xx Mask:255.255.252.0 inet6 addr: fe80::b8e2:bea4:2e62:fe08/64 Scope:Link UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1406 Metric:1 RX packets:962 errors:0 dropped:0 overruns:0 frame:0 TX packets:1029 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:500 RX bytes:87839 (87.8 KB) TX bytes:238740 (238.7 KB) Issue Unable to connect to any host via ssh or sftp after VPN connection Tried = Reinstalled the openssh-client package and still no luck. May I know why the default cipher is not taking/hanging? Please let me know . There were no recent changes. Workaround === Able to connect to ssh / sftp $ssh -c aes128-ctr user@IP Below is the debug ssh client logs === == $ssh -vvv user@ip OpenSSH_7.2p2 Ubuntu-4ubuntu2.8, OpenSSL 1.0.2g 1 Mar 2016 debug1: Reading configuration data /etc/ssh/ssh_config debug1: /etc/ssh/ssh_config line 19: Applying options for * debug2: resolving "IP" port 22 debug2: ssh_connect_direct: needpriv 0 debug1: Connecting to IP [IP] port 22. debug1: Connection established. debug1: key_load_public: No such file or directory debug1: identity file /home/user/.ssh/id_rsa type -1 debug1: key_load_public: No such file or directory debug1: identity file /home/user/.ssh/id_rsa-cert type -1 debug1: key_load_public: No such file or directory debug1: identity file /home/user/.ssh/id_dsa type -1 debug1: key_load_public: No such file or directory debug1: identity file /home/user/.ssh/id_dsa-cert type -1 debug1: key_load_public: No such file or directory debug1: identity file /home/user/.ssh/id_ecdsa type -1 debug1: key_load_public: No such file or directory debug1: identity file /home/user/.ssh/id_ecdsa-cert type -1 debug1: key_load_public: No such file or directory debug1: identity file /home/user/.ssh/id_ed25519 type -1 debug1: key_load_public: No such file or directory debug1: identity file /home/user/.ssh/id_ed25519-cert type -1 debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_7.2p2 Ubuntu-4ubuntu2.8 debug1: Remote protocol version 2.0, remote software version OpenSSH_7.6p1 Ubuntu-4ubuntu0.3 debug1: match: OpenSSH_7.6p1 Ubuntu-4ubuntu0.3 pat OpenSSH* compat 0x0400 debug2: fd 3 setting O_NONBLOCK debug1: Authenticating to IP:22 as 'user' debug3: send packet: type 20 debug1: SSH2_MSG_KEXINIT sent debug3: receive packet: type 20 debug1: SSH2_MSG_KEXINIT received debug2: local client KEXINIT proposal debug2: KEX algorithms: curve25519-sha...@libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,ext-info-c debug2: host key algorithms: ecdsa-sha2-nistp256-cert-...@openssh.com,ecdsa-sha2-nistp384-cert-...@openssh.com,ecdsa-sha2-nistp521-cert-...@openssh.com,ssh-ed25519-cert-...@openssh.com,ssh-rsa-cert-...@openssh.com,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,ssh-ed25519,rsa-sha2-512,rsa-sha2-256,ssh-rsa debug2: ciphers ctos: chacha20-poly1...@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-...@openssh.com,aes256-...@openssh.com,aes128-cbc,aes192-cbc,aes256-cbc,3des-cbc debug2: ciphers stoc: chacha20-poly1...@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-...@openssh.com,aes256-...@openssh.com,aes128-cbc,aes192-cbc,aes256-cbc,3des-cbc debug2: MACs ctos: umac-64-...@openssh.com,umac-128-...@openssh.com,hmac-sha2-256-...@openssh.com,hmac-sha2-512-...@openssh.com,hmac-sha1-...@openssh.com,umac...@openssh.com,umac-...@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-sha1 debug2: MACs stoc:
[Kernel-packages] [Bug 1968604] [NEW] rtl8761b usb bluetooth doesn't work following reboot until unplug/replug
Public bug reported: I have usb bluetooth 5.0 dongle which uses Realtek RTL8761B chip. 0bda:8771 Realtek Semiconductor Corp. Bluetooth Radio USB adapter very often stops working, can't connect or find other bluetooth devices. The adapter can't work even after reboots. The following entries appear in the log: апр 11 13:47:14 desktop kernel: Bluetooth: hci0: command 0x2005 tx timeout апр 11 13:47:16 desktop kernel: Bluetooth: hci0: command 0x2041 tx timeout апр 11 13:47:18 desktop kernel: Bluetooth: hci0: command 0x2042 tx timeout Firmware loaded correctly, but something is not working. апр 11 13:46:54 desktop kernel: Bluetooth: hci0: RTL: examining hci_ver=0a hci_rev=000b lmp_ver=0a lmp_subver=8761 апр 11 13:46:54 desktop kernel: Bluetooth: hci0: RTL: rom_version status=0 version=1 апр 11 13:46:54 desktop kernel: Bluetooth: hci0: RTL: loading rtl_bt/rtl8761bu_fw.bin апр 11 13:46:54 desktop kernel: Bluetooth: hci0: RTL: loading rtl_bt/rtl8761bu_config.bin апр 11 13:46:54 desktop kernel: Bluetooth: hci0: RTL: cfg_sz 6, total sz 27814 1) I use: Description:Ubuntu Jammy Jellyfish (development branch) Release:22.04 2) linux-firmware: 20220329.git681281e4-0ubuntu1 3) What you expected to happen? I expect a well working bluetooth adapter. 4) What happened instead? My bluetooth adapter may work, may not. The adapter may stop finding and connecting to other devices. I've found the same bug https://bugzilla.kernel.org/show_bug.cgi?id=214111#c1 I've downloaded Windows's archive http://download.windowsupdate.com/d/msdownload/update/driver/drvs/2021/05/ca0e770c-6a5d-4de0-b37a-f4b91cccd8c3_7778831d2b9d721cf94d5a8d8c0676ff1b96c874.cab I've unpacked file rtl8761b_mp_chip_bt40_fw_asic_rom_patch_new.dll and replaced /usr/lib/firmware/rtl_bt/rtl8761bu_fw.bin and deleted rtl8761bu_config.bin After I changed firmware my usb dongle work fine. Could you change firmware rtl8761bu_fw.bin rtl8761bu_config.bin to other correct version? Could you move Realtek's rtl_bt firmware or RTL8761B's firmware into separate packages. I will remove the RTL8761B firmware package and put them manually. bluetoothctl --version bluetoothctl: 5.64 hci0: Type: Primary Bus: USB BD Address: 00:E0:4C:FC:E2:03 ACL MTU: 1021:6 SCO MTU: 255:12 UP RUNNING RX bytes:5751 acl:49 sco:0 events:489 errors:0 TX bytes:219114 acl:398 sco:0 commands:83 errors:0 Features: 0xff 0xff 0xff 0xfe 0xdb 0xfd 0x7b 0x87 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 Link policy: RSWITCH HOLD SNIFF PARK Link mode: PERIPHERAL ACCEPT Name: 'desktop' Class: 0x7c0104 Service Classes: Rendering, Capturing, Object Transfer, Audio, Telephony Device Class: Computer, Desktop workstation HCI Version: 5.1 (0xa) Revision: 0x97b LMP Version: 5.1 (0xa) Subversion: 0xec43 Manufacturer: Realtek Semiconductor Corporation (93) rfkill list 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Realtek's worker updated these bad firmware. https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=45dc5f0b8e2f2d43312d22511cb26658b9ee2c80 ** Affects: linux-firmware (Ubuntu) Importance: Undecided Status: New ** Tags: bluetooth firmware realtek ** Description changed: I have usb bluetooth 5.0 dongle which uses Realtek RTL8761B chip. 0bda:8771 Realtek Semiconductor Corp. Bluetooth Radio USB adapter very often stops working, can't connect or find other bluetooth devices. The adapter can't work even after reboots. The following entries appear in the log: апр 11 13:47:14 desktop kernel: Bluetooth: hci0: command 0x2005 tx timeout апр 11 13:47:16 desktop kernel: Bluetooth: hci0: command 0x2041 tx timeout апр 11 13:47:18 desktop kernel: Bluetooth: hci0: command 0x2042 tx timeout Firmware loaded correctly, but something is not working. апр 11 13:46:54 desktop kernel: Bluetooth: hci0: RTL: examining hci_ver=0a hci_rev=000b lmp_ver=0a lmp_subver=8761 апр 11 13:46:54 desktop kernel: Bluetooth: hci0: RTL: rom_version status=0 version=1 апр 11 13:46:54 desktop kernel: Bluetooth: hci0: RTL: loading rtl_bt/rtl8761bu_fw.bin апр 11 13:46:54 desktop kernel: Bluetooth: hci0: RTL: loading rtl_bt/rtl8761bu_config.bin апр 11 13:46:54 desktop kernel: Bluetooth: hci0: RTL: cfg_sz 6, total sz 27814 1) I use: Description:Ubuntu Jammy Jellyfish (development branch) Release:22.04 2) linux-firmware: 20220329.git681281e4-0ubuntu1 3) What you expected to happen? I expect a well working bluetooth adapter. 4) What happened instead? My bluetooth adapter may work, may not. The adapter may stop finding and connecting to other devices. - - I've found the same bug https://www.spinics.net/lists/linux-bluetooth/msg93753.html + I've found the same bug https://bugzilla.kernel.org/show_bug.cgi?id=214111#c1 I've downloaded Windows's archive
[Kernel-packages] [Bug 1965723] Re: audit: improve audit queue handling when "audit=1" on cmdline
Identified this issue in Focal starting with the update to 105 kernel. Constant soft lockups then freezing when kauditd/auditd exceeded backlog limit. Due to DoD requirements, all systems set to audit=1 in kernel boot options and have stringent list of syscalls/binaries/files that are audited. Added focal-proposed repo and updated to 109 kernel. Few hours of compiling and heavy static code analysis loads on system and no lockups as of yet. This is a really scary bug - seems to be present on all linux kernels and a huge threat as a DDoS. -- 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/1965723 Title: audit: improve audit queue handling when "audit=1" on cmdline Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Impish: Fix Committed Bug description: SRU Justification [Impact] When an admin enables audit at early boot via the "audit=1" kernel command line the audit queue behavior is slightly different; the audit subsystem goes to greater lengths to avoid dropping records, which unfortunately can result in problems when the audit daemon is forcibly stopped for an extended period of time. [Fix] upstream discussion: https://lore.kernel.org/all/cahc9vhqgx070poxzk_pusawgzppdqvpezvfybse2dnryrbw...@mail.gmail.com/T/ upstream commit: f26d04331360d42dbd6b58448bd98e4edbfbe1c5 [Test] configurations: auditctl -b 64 auditctl --backlog_wait_time 6 auditctl -r 0 auditctl -w /root/aaa -p wrx shell scripts： #!/bin/bash i=0 while [ $i -le 66 ] do touch /root/aaa let i++ done mandatory conditions: add "audit=1" to the cmdline, and kill -19 pid_number(for /sbin/auditd). As long as we keep the audit_hold_queue non-empty, flush the hold queue will fall into an infinite loop. This could also trigger soft lockup when it drops into a infinite loop, e.g. kernel: [ 94.186433] watchdog: BUG: soft lockup - CPU#2 stuck for 11s! [kauditd:34] kernel: [ 94.187736] Modules linked in: xfs iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_ conntrack libcrc32c iptable_filter isofs xt_cgroup xt_tcpudp iptable_mangle ip_tables x_tables sb_edac crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc aesni_intel aes_x86_64 pp dev crypto_simd glue_helper joydev vmwgfx ttm cryptd vmw_balloon drm_kms_helper intel_rapl_perf input_leds psmouse drm fb_sys_fops syscopyarea vmxnet3 sysfillrect parport_pc parport m ac_hid shpchp i2c_piix4 vmw_vsock_vmci_transport vsock sysimgblt vmw_vmci serio_raw mptspi mptscsih mptbase scsi_transport_spi pata_acpi floppy autofs4 kernel: [ 94.187757] CPU: 2 PID: 34 Comm: kauditd Not tainted 4.15.0-171-generic #180~16.04.1-Ubuntu kernel: [ 94.187757] Hardware name: VMware, Inc. VMware Virtual Platform/440BX Desktop Reference Platform, BIOS 6.00 11/12/2020 kernel: [ 94.187800] skb_queue_head+0x47/0x50 kernel: [ 94.187803] kauditd_rehold_skb+0x18/0x20 kernel: [ 94.187805] kauditd_send_queue+0xcd/0x100 kernel: [ 94.187806] ? kauditd_retry_skb+0x20/0x20 kernel: [ 94.187808] ? kauditd_send_multicast_skb+0x80/0x80 kernel: [ 94.187809] kauditd_thread+0xa7/0x240 kernel: [ 94.187812] ? wait_woken+0x80/0x80 kernel: [ 94.187815] kthread+0x105/0x140 kernel: [ 94.187817] ? auditd_reset+0x90/0x90 kernel: [ 94.187818] ? kthread_bind+0x40/0x40 kernel: [ 94.187820] ret_from_fork+0x35/0x40 [Other Info] SF: #00330803 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1965723/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-azure-5.4/5.4.0.1076.55)
All autopkgtests for the newly accepted linux-meta-azure-5.4 (5.4.0.1076.55) for bionic have finished running. The following regressions have been reported in tests triggered by the package: snapd/2.54.3+18.04.2ubuntu0.2 (amd64) dahdi-linux/1:2.11.1~dfsg-1ubuntu4.2 (amd64) kpatch/0.5.0-0ubuntu1.1 (amd64) lxc/3.0.3-0ubuntu1~18.04.1 (amd64) v4l2loopback/0.10.0-1ubuntu1.2 (amd64) asic0x/1.0.1-1 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-meta-azure-5.4 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packing resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1934620] Re: NVIDIA A100-80GB GPU fails to initialize in R750xa, BAR Address setup failed if SR-IOV is disabled in BIOS
Sujith, Can you get a nvidia-bug-report.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1934620 Title: NVIDIA A100-80GB GPU fails to initialize in R750xa, BAR Address setup failed if SR-IOV is disabled in BIOS Status in dellserver: Won't Fix Status in linux package in Ubuntu: Confirmed Bug description: Installing NVidia A100-80GB GPUs in R750XA fails to initialize BAR memory space for GPUs. Multiple error messages in kernel.log file. Summary: * Dell prefers to set SRIOV to disabled in bios globally * This bug does not occur IF: SRIOV is enabled in BIOS OR "pci=realloc=off" is passed to the kernel at boot time * This bug only affects systems with NVIDIA A100-80GB GPUs, it does not affect systems with NVIDIA A100-40GB GPUs To manage notifications about this bug go to: https://bugs.launchpad.net/dellserver/+bug/1934620/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-hwe-5.4/5.4.0.108.122~18.04.93)
All autopkgtests for the newly accepted linux-meta-hwe-5.4 (5.4.0.108.122~18.04.93) for bionic have finished running. The following regressions have been reported in tests triggered by the package: virtualbox-hwe/5.2.42-dfsg-0~ubuntu1.18.04.1 (amd64) v4l2loopback/0.10.0-1ubuntu1.2 (s390x) acpi-call/1.1.0-4 (s390x, ppc64el) lxc/3.0.3-0ubuntu1~18.04.1 (amd64, s390x, ppc64el) kpatch/0.5.0-0ubuntu1.1 (amd64) asic0x/1.0.1-1 (s390x) snapd/2.54.3+18.04.2ubuntu0.2 (amd64, s390x, arm64, ppc64el) virtualbox/5.2.42-dfsg-0~ubuntu1.18.04.1 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-meta-hwe-5.4 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packing resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1964512] Re: Low RX performance for 40G Solarflare NICs
Validated for Ubuntu Impish with the current kernel from impish-proposed. Tested on a 10G NIC that's affected by this patch (device ID 0x0903). iperf3 shows that we're able to almost saturate the NIC successfully in both standard and reverse sender mode: [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-10.00 sec 10.1 GBytes 8.69 Gbits/sec 990 sender [ 5] 0.00-9.99 sec 10.1 GBytes 8.69 Gbits/sec receiver [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-10.00 sec 10.8 GBytes 9.30 Gbits/sec 155 sender [ 5] 0.00-10.00 sec 10.8 GBytes 9.30 Gbits/sec receiver ubuntu@duduo:~$ uname -rv 5.13.0-40-generic #45-Ubuntu SMP Tue Mar 29 14:48:14 UTC 2022 Other basic smoke testing confirms no major regressions. ** Tags removed: verification-needed-impish ** Tags added: verification-done-impish -- 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/1964512 Title: Low RX performance for 40G Solarflare NICs Status in linux package in Ubuntu: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Impish: Fix Committed Status in linux source package in Jammy: Fix Committed Bug description: [Impact] * Some 40G Solarflare NICs have low RX performance in some cases, due low RX recycle ring size * RX recycle ring size is either 4096 for IOMMU, 16 for NOIOMMU * The low fixed sizes can cause a high number of calls to alloc_pages, tanking performance for higher link speeds [Test Plan] * Users report that iperf3 is sufficient to showcase the bad RX performance * For some setups, RX performance was around 15Gbps while TX stayed consistently above 30Gbps [Fix] * This patch sets the RX recycle ring size according to an adapter's maximum link speed * Fix was introduced by commit: 000fe940e51f "sfc: The size of the RX recycle ring should be more flexible" * --!-- Commit is from net-next --!-- [Regression Potential] * Regressions would show primarily as performance issues, as we're effectively changing ring sizes for all RX traffic * It's possible to see increased calls to alloc_pages if ring sizes aren't being set correctly * We should look out for excessive memory usage in the sfc driver due to the increased ring sizes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1964512/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1964512] Re: Low RX performance for 40G Solarflare NICs
In addition to my own validations above, impacted users that have 40G NICs have also confirmed the patch behaves as expected without major regressions. -- 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/1964512 Title: Low RX performance for 40G Solarflare NICs Status in linux package in Ubuntu: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Impish: Fix Committed Status in linux source package in Jammy: Fix Committed Bug description: [Impact] * Some 40G Solarflare NICs have low RX performance in some cases, due low RX recycle ring size * RX recycle ring size is either 4096 for IOMMU, 16 for NOIOMMU * The low fixed sizes can cause a high number of calls to alloc_pages, tanking performance for higher link speeds [Test Plan] * Users report that iperf3 is sufficient to showcase the bad RX performance * For some setups, RX performance was around 15Gbps while TX stayed consistently above 30Gbps [Fix] * This patch sets the RX recycle ring size according to an adapter's maximum link speed * Fix was introduced by commit: 000fe940e51f "sfc: The size of the RX recycle ring should be more flexible" * --!-- Commit is from net-next --!-- [Regression Potential] * Regressions would show primarily as performance issues, as we're effectively changing ring sizes for all RX traffic * It's possible to see increased calls to alloc_pages if ring sizes aren't being set correctly * We should look out for excessive memory usage in the sfc driver due to the increased ring sizes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1964512/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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] Re: Fix flow table lookup after ct clear or switching zones
** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/1963948 Title: Fix flow table lookup after ct clear or switching zones Status in linux-bluefield package in Ubuntu: Invalid Status in linux-bluefield source package in Focal: Fix Committed 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 1960575] Re: Pass originating device to drivers offloading ct connection so devices will filter the tuples and offload them more efficiently
** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/1960575 Title: Pass originating device to drivers offloading ct connection so devices will filter the tuples and offload them more efficiently Status in linux-bluefield package in Ubuntu: Invalid Status in linux-bluefield source package in Focal: Fix Committed Bug description: * Explain the feature Currently, drivers register to a ct zone that can be shared by multiple devices. This can be inefficient for the driver to offload, as it needs to handle all the cases where the tuple can come from, instead of where it's most likely will arive from. For example, consider the following tc rules: tc filter add dev dev1 ... flower action ct commit zone 5 \ action mirred egress redirect dev dev2 tc filter add dev dev2 ... flower action ct zone 5 \ action goto chain chain 2 tc filter add dev dev2 ... flower ct_state +trk+est ... \ action mirred egress redirect dev dev1 Both dev2 and dev1 register to the zone 5 flow table (created by act_ct). A tuple originating on dev1, going to dev2, will be offloaded to both devices, and both will need to offload both directions, resulting in 4 total rules. The traffic will only hit originiating tuple on dev1, and reply tuple on dev2. By passing the originating device that created the connection with the tuple, dev1 can choose to offload only the originating tuple, and dev2 only the reply tuple. Resulting in a more efficient offload. The first patch adds an act_ct nf conntrack extension, to temporarily store the originiating device from the skb before offloading the connection once the connection is established. Once sent to offload, it fills the tuple originating device. The second patch get this information from tuples which pass in openvswitch. The third patch is Mellanox driver ct offload implementation using this information to provide a hint to firmware of where this offloaded tuple packets will arrive from (LOCAL or UPLINK port), and thus increase insertion rate. * How to test Create OVS bridge with 2 devices mlx5 rep devices. Enable HW offload and configure regular connection tracking OpenFlow rules: e.g: ovs-ofctl del-flows br-ovs ovs-ofctl add-flow br-ovs arp,actions=normal ovs-ofctl add-flow br-ovs "table=0, ip,ct_state=-trk actions=ct(table=1)" ovs-ofctl add-flow br-ovs "table=1, ip,ct_state=+trk+new actions=ct(commit),normal" ovs-ofctl add-flow br-ovs "table=1, ip,ct_state=+trk+est, actions=normal" With SW steering enabled and the above commits (and up to date ofed) tuple insertion rate should be about twice as fast. This can be seen via procfs hw offloaded count while running high traffic: while true; do res=`sudo cat /proc/net/nf_conntrack | grep -i offload` && echo "$res" && echo "$res" | wc -l; done * What it could break. NA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1960575/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1961819] Re: CT: Offload only ASSURED connections
** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/1961819 Title: CT: Offload only ASSURED connections Status in linux-bluefield package in Ubuntu: Invalid Status in linux-bluefield source package in Focal: Fix Committed Bug description: * Explain the feature Assured connections are those connections which deemed of "higher quality" and less like to expire than non-assured connections, as they passed some stricter rule (e.g in udp reply + connection lasting more than 2 seconds). This feature offloads only those connections. * How to test Create OVS bridge with 2 devices mlx5 rep devices. Enable HW offload and configure regular connection tracking OpenFlow rules: e.g: ovs-ofctl del-flows br-ovs ovs-ofctl add-flow br-ovs arp,actions=normal ovs-ofctl add-flow br-ovs "table=0, ip,ct_state=-trk actions=ct(table=1)" ovs-ofctl add-flow br-ovs "table=1, ip,ct_state=+trk+new actions=ct(commit),normal" ovs-ofctl add-flow br-ovs "table=1, ip,ct_state=+trk+est, actions=normal" Run a short UDP connection (< 2 seconds), e.g: on mlx5 VF1 iperf -s -u on mlx5 VF2 iperf -c -t 1 -u Run longer UDP connection (> 2 seconds), e.g: on mlx5 VF1 iperf -s -u on mlx5 VF2 iperf -c -t 10 -u With the above commit quick lived UDP connections (< 2 seconds) will not be offloaded to the flow table as can be checked by cat /proc/net/nf_conntrack | grep -i offload while connections lasting more than 2 seconds (and of course double sided) will be offloaded. * What it could break. NA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1961819/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1962490] Re: Support VF groups rate limit
** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/1962490 Title: Support VF groups rate limit Status in linux-bluefield package in Ubuntu: Invalid Status in linux-bluefield source package in Focal: Fix Committed Bug description: * Explain the feature Managing TX rate of VFs becomes non-trivial task when a big number of VFs are used. This issue can be handled with some grouping mechanism. Currently driver provide two ways to limit TX rate of the VF: TC police action and NDO API callback. Implementation of grouping within this two infrastructures problematic, due to the following: NDO API rate limiting is legacy feature, even though it's available in switchdev mode, and extending it with new abstraction is not good anyway; TC police action is flow based and requires net device with Qdisc on it and implementing this will bring unwanted complications. According to aforesaid devlink is the most appropriate place. * How to test Set tx_max value on the devlink port with a command. For ex.: $ devlink port function rate set pci/:82:00.0/1 tx_max 10gbit or if grouping is required, create rate group with configured tx_max value in a single command and assign port to this group: $ devlink port function rate add pci/:82:00.0/1st_group tx_max 8gbit $ devlink port function rate set pci/:82:00.0/1 tx_max 10gbit parent 1st_group Configuration is done. Run traffic and do measurement. * What it could break. As this pull request backported 130 patches from devlink/netlink, it may break some functionalities from net core layer. Also, the network drivers which are not used by BF are disabled to avoid the fix of conflicts. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1962490/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1967892] Re: Fix flow table lookup failure with no originating ifindex
** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/1967892 Title: Fix flow table lookup failure with no originating ifindex Status in linux-bluefield package in Ubuntu: Invalid Status in linux-bluefield source package in Focal: Fix Committed Bug description: * Explain the bug After the CT ifindex extension feature, flow table entries are populated with ifindex information which was intended to only be used for HW offload. This tuple ifindex is hashed in the flow table key, so it must be filled for lookup to be successful. But tuple ifindex is only relevant for the netfilter flowtables (nft), so it's not filled in act_ct flow table lookup, resulting in lookup failure, and no SW offload and no offload teardown for TCP connection FIN/RST packets. To fix this, add new tc ifindex field to tuple, which will only be used for offloading, not for lookup, as it will not be part of the tuple hash. * How to test Create OVS bridge with 2 devices mlx5 rep devices. Enable HW offload and configure regular connection tracking OpenFlow rules: e.g: ovs-ofctl del-flows br-ovs ovs-ofctl add-flow br-ovs arp,actions=normal ovs-ofctl add-flow br-ovs "table=0, ip,ct_state=-trk actions=ct(table=1)" ovs-ofctl add-flow br-ovs "table=1, ip,ct_state=+trk+new actions=ct(commit),normal" ovs-ofctl add-flow br-ovs "table=1, ip,ct_state=+trk+est, actions=normal" Generate traffic at high rate (e.g. using IXIA). The number of offloaded rules exposed in /sys/kernel/debug/mlx5/\:$BUS\:00.0/ct/offloaded should be in synch the number of generated connections. * What it could break. Perhaps nft offload – it is not part of our tests To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1967892/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1968469] Re: ILITEK_ILI9881C panel driver missing
** Changed in: linux-raspi (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/1968469 Title: ILITEK_ILI9881C panel driver missing Status in linux-raspi package in Ubuntu: Fix Released Bug description: the current 5.15.0-1004-raspi kernel for 22.04 does not enable the CONFIG_DRM_PANEL_ILITEK_ILI9881C=m option, thus such touchscreen panels can not be used the cutiepi (https://cutiepi.io/) project does use this hardware for their pi based tablets. booting ubuntu 22.04 on such a tablet is only possible with an external HDMI monitor attached at this moment. it would be nice if Ubuntu could work OOTB on this hardware. while the jammy kernel seems to already ship the required dtb overlay "cutiepi-panel.dtbo", the modules this overlay uses are not there. below is a Kconfig commit outlining the required options: https://github.com/cutiepi- io/linux/commit/de6774dca11b815e647fa08d71f3eac9009c2dff To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1968469/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1968591] 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 1968591 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/1968591 Title: xfrm interface cannot be changed anymore Status in linux package in Ubuntu: Incomplete Bug description: [Impact] An xfrm interface cannot be changed any more since Ubuntu-hwe-5.4-5.4.0-105. In fact, the regression has been introduced by this backport: https://kernel.ubuntu.com/git/ubuntu/ubuntu-focal.git/commit/?id=13a02539b135 It has been fixed upstream by this commit: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=6d0d95a1c2b0 [Test Case] root@dut-vm:~# ip link add foo type xfrm if_id 1234 dev lo root@dut-vm:~# ip link change foo type xfrm if_id 1234 dev ntfp1 Error: if_id must be non zero. root@dut-vm:~# uname -a Linux dut-vm 5.4.0-107-generic #121~18.04.1-Ubuntu SMP Thu Mar 24 17:21:33 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux root@dut-vm:~# [Regression Potential] The patch is trivial, the potential regressions are low. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1968591/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1968591] [NEW] xfrm interface cannot be changed anymore
Public bug reported: [Impact] An xfrm interface cannot be changed any more since Ubuntu-hwe-5.4-5.4.0-105. In fact, the regression has been introduced by this backport: https://kernel.ubuntu.com/git/ubuntu/ubuntu-focal.git/commit/?id=13a02539b135 It has been fixed upstream by this commit: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=6d0d95a1c2b0 [Test Case] root@dut-vm:~# ip link add foo type xfrm if_id 1234 dev lo root@dut-vm:~# ip link change foo type xfrm if_id 1234 dev ntfp1 Error: if_id must be non zero. root@dut-vm:~# uname -a Linux dut-vm 5.4.0-107-generic #121~18.04.1-Ubuntu SMP Thu Mar 24 17:21:33 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux root@dut-vm:~# [Regression Potential] The patch is trivial, the potential regressions are low. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Description changed: [Impact] An xfrm interface cannot be changed any more since Ubuntu-hwe-5.4-5.4.0-105. In fact, the regression has been introduced by this backport: https://kernel.ubuntu.com/git/ubuntu/ubuntu-focal.git/commit/?id=13a02539b135 + + It has been fixed upstream by this commit: + https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=6d0d95a1c2b0 [Test Case] root@dut-vm:~# ip link add foo type xfrm if_id 1234 dev lo root@dut-vm:~# ip link change foo type xfrm if_id 1234 dev ntfp1 Error: if_id must be non zero. root@dut-vm:~# uname -a Linux dut-vm 5.4.0-107-generic #121~18.04.1-Ubuntu SMP Thu Mar 24 17:21:33 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux root@dut-vm:~# [Regression Potential] The patch is trivial, the potential regressions are low. -- 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/1968591 Title: xfrm interface cannot be changed anymore Status in linux package in Ubuntu: New Bug description: [Impact] An xfrm interface cannot be changed any more since Ubuntu-hwe-5.4-5.4.0-105. In fact, the regression has been introduced by this backport: https://kernel.ubuntu.com/git/ubuntu/ubuntu-focal.git/commit/?id=13a02539b135 It has been fixed upstream by this commit: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=6d0d95a1c2b0 [Test Case] root@dut-vm:~# ip link add foo type xfrm if_id 1234 dev lo root@dut-vm:~# ip link change foo type xfrm if_id 1234 dev ntfp1 Error: if_id must be non zero. root@dut-vm:~# uname -a Linux dut-vm 5.4.0-107-generic #121~18.04.1-Ubuntu SMP Thu Mar 24 17:21:33 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux root@dut-vm:~# [Regression Potential] The patch is trivial, the potential regressions are low. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1968591/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1964512] Re: Low RX performance for 40G Solarflare NICs
Validated for Ubuntu Bionic with the current HWE kernel from bionic-proposed. Tested on a 10G NIC that's affected by this patch (device ID 0x0903). iperf3 shows that we're able to almost saturate the NIC successfully in both standard and reverse sender mode: [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-10.00 sec 10.2 GBytes 8.80 Gbits/sec 376 sender [ 5] 0.00-10.00 sec 10.2 GBytes 8.80 Gbits/sec receiver [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-10.00 sec 10.9 GBytes 9.39 Gbits/sec0 sender [ 5] 0.00-10.00 sec 10.9 GBytes 9.38 Gbits/sec receiver ubuntu@duduo:~$ uname -rv 5.4.0-108-generic #122~18.04.1-Ubuntu SMP Wed Apr 6 16:57:12 UTC 2022 Other basic smoke testing confirms no major regressions. ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1964512 Title: Low RX performance for 40G Solarflare NICs Status in linux package in Ubuntu: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Impish: Fix Committed Status in linux source package in Jammy: Fix Committed Bug description: [Impact] * Some 40G Solarflare NICs have low RX performance in some cases, due low RX recycle ring size * RX recycle ring size is either 4096 for IOMMU, 16 for NOIOMMU * The low fixed sizes can cause a high number of calls to alloc_pages, tanking performance for higher link speeds [Test Plan] * Users report that iperf3 is sufficient to showcase the bad RX performance * For some setups, RX performance was around 15Gbps while TX stayed consistently above 30Gbps [Fix] * This patch sets the RX recycle ring size according to an adapter's maximum link speed * Fix was introduced by commit: 000fe940e51f "sfc: The size of the RX recycle ring should be more flexible" * --!-- Commit is from net-next --!-- [Regression Potential] * Regressions would show primarily as performance issues, as we're effectively changing ring sizes for all RX traffic * It's possible to see increased calls to alloc_pages if ring sizes aren't being set correctly * We should look out for excessive memory usage in the sfc driver due to the increased ring sizes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1964512/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1967338] Re: linux: CONFIG_SERIAL_8250_MID=y
8250_MID=y [ 1.456543] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled [ 1.458472] 8250_mid :00:1a.0: Found HSU DMA, 2 channels [ 5.714059] 8250_mid :00:1a.1: Found HSU DMA, 2 channels [ 5.728917] 8250_mid :00:1a.2: Found HSU DMA, 2 channels 8250_MID=m [ 14.017669] 8250_mid :00:1a.0: Found HSU DMA, 2 channels [ 14.035553] 8250_mid :00:1a.1: Found HSU DMA, 2 channels [ 14.052663] 8250_mid :00:1a.2: Found HSU DMA, 2 channels I was able to load with module compiled into kernel and it's loaded much earlier than with 8250_MID=m, so serial console is functional ** Changed in: linux (Ubuntu Jammy) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1967338 Title: linux: CONFIG_SERIAL_8250_MID=y Status in linux package in Ubuntu: Confirmed Status in linux source package in Jammy: Confirmed Bug description: SRU Justification [Impact] See discussion at https://lists.ubuntu.com/archives/kernel- team/2022-March/128690.html [Test Plan] Boot with serial console connected [Where things could go wrong] Not really a lot of opportunity for regression To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967338/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1961300] Re: linux-azure: Fix NUMA node assignment when kernel boots with custom NUMA topology
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-5.11 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 Released
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 1967336] Re: linux-azure: CONFIG_HIBERNATION=y
** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1967336 Title: linux-azure: CONFIG_HIBERNATION=y Status in linux-azure package in Ubuntu: Fix Committed Status in linux-azure source package in Focal: Fix Committed Status in linux-azure source package in Impish: Fix Committed Status in linux-azure source package in Jammy: Fix Committed Bug description: SRU Justification [Impact] Azure arm64 tuned kernels do not support hibernation. [Test Plan] Microsoft tested [Where things could go wrong] Hibernation may fail. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1967336/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1965618] Re: linux-azure: Focal 5.4 arm64 support
** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1965618 Title: linux-azure: Focal 5.4 arm64 support Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure source package in Focal: Fix Committed Bug description: SRU Justification [Impact] Focal linux-azure does not support arm64 [Fix] Backport/cherry-pick approximately 100 patches to support arm64 on hyperv [Where things could go wrong] A number of the patches reorganize hyperv CPU support. Therefore amd64 could be affected. [Other Info] SF: #00310705 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1965618/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1964512] Re: Low RX performance for 40G Solarflare NICs
Validated for Ubuntu Focal with the current kernel from focal-proposed. Tested on a 10G NIC that's affected by this patch (device ID 0x0903). iperf3 shows that we're able to almost saturate the NIC successfully in both standard and reverse sender mode: [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-10.00 sec 10.3 GBytes 8.83 Gbits/sec 266 sender [ 5] 0.00-10.00 sec 10.3 GBytes 8.82 Gbits/sec receiver [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-10.00 sec 10.8 GBytes 9.30 Gbits/sec0 sender [ 5] 0.00-10.00 sec 10.8 GBytes 9.30 Gbits/sec receiver ubuntu@duduo:~$ uname -rv 5.4.0-109-generic #123-Ubuntu SMP Fri Apr 8 09:10:54 UTC 2022 ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1964512 Title: Low RX performance for 40G Solarflare NICs Status in linux package in Ubuntu: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Impish: Fix Committed Status in linux source package in Jammy: Fix Committed Bug description: [Impact] * Some 40G Solarflare NICs have low RX performance in some cases, due low RX recycle ring size * RX recycle ring size is either 4096 for IOMMU, 16 for NOIOMMU * The low fixed sizes can cause a high number of calls to alloc_pages, tanking performance for higher link speeds [Test Plan] * Users report that iperf3 is sufficient to showcase the bad RX performance * For some setups, RX performance was around 15Gbps while TX stayed consistently above 30Gbps [Fix] * This patch sets the RX recycle ring size according to an adapter's maximum link speed * Fix was introduced by commit: 000fe940e51f "sfc: The size of the RX recycle ring should be more flexible" * --!-- Commit is from net-next --!-- [Regression Potential] * Regressions would show primarily as performance issues, as we're effectively changing ring sizes for all RX traffic * It's possible to see increased calls to alloc_pages if ring sizes aren't being set correctly * We should look out for excessive memory usage in the sfc driver due to the increased ring sizes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1964512/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1958918] Re: dependency on crda obsolete according to Debian
This bug was fixed in the package linux-raspi - 5.15.0-1005.5 --- linux-raspi (5.15.0-1005.5) jammy; urgency=medium * jammy/linux-raspi: 5.15.0-1005.5 -proposed tracker (LP: #1966493) * jammy/linux-raspi: Update to upstream raspberrypi rpi-5.15.y (2022-04-04) (LP: #1967733) - bcm2835-codec: /dev/video31 as interface to image_encode JPEG encoder - media: entity: Skip non-data links in graph iteration - media: media.h: Add new media link type - media: entity: Add link_type_name() helper - media: entity: Add support for ancillary links - media: v4l2-async: Create links during v4l2_async_match_notify() - dt-bindings: media: i2c: Add binding for ad5398 VCM - media: i2c: Add driver for AD5398 VCM lens driver - media: i2c: ov5647: Use v4l2_async_register_subdev_sensor for lens binding - defconfigs: Add AD5398 VCM to all Pi defconfigs - dtoverlays: Add VCM option to imx219 - dtoverlay: Add VCM option to ov5647 overlay - media: i2c: Rename ad5398 to ad5398_vcm - drm/object: Add drm_object_property_get_default_value() function - drm/object: Add default zpos value at reset - drm/object: Add default color encoding and range value at reset - drm/vc4: Support zpos on all planes - CM3 cam1_reg and cam1_reg_gpio fix - overlays: Fix cam*_reg_gpio parameter on CM1 - overlays: iqs550: Enable interrupt pull-down - dtoverlays: Connect the backlight to the pitft35 display - drm/vc4: hdmi: Add CSC for BT601/709/2020 limited and full range output - Revert "usb: xhci: expand the scope of XHCI_VLI_SS_BULK_OUT_BUG" - vc4/drm: vc4_plane: Keep fractional source coords inside state - vc4/drm: Handle fractional coordinates using the phase field - drm: Add chroma siting properties - vc4/drm:plane: Make use of chroma siting parameter - drivers: staging: bcm2835-isp: Clear LS table handle in the firmware - dt-bindings: display: add bindings for MIPI DBI compatible SPI panels - drm/modes: Add of_get_drm_panel_display_mode() - drm/mipi-dbi: Add driver_private member to struct mipi_dbi_dev - drm/tiny: Add MIPI DBI compatible SPI driver - configs: Add MIPI DBI display driver - overlays: Add overlay for MIPI DBI displays - audioinjector.net: stereo and zero, use dev_err_probe, report success - Revert "update rpi-display-overlay.dts pins for 5.10+" - overlays/rpi-display: Add support for DRM driver - bcm2835-codec: Return empty buffers to the VPU instead of queueing to vbuf2 - mm,page_alloc,cma: introduce a customisable threshold for allocating pages in cma - pinctrl: bcm2835: Only return non-GPIOs to inputs - ARM: dts: Enable PMU on Cortex-A72 in AArch32 state - drm/panel: ilitek-ili9881c: Clean up on mipi_dsi_attach failure - drm/panel: panel-ilitek9881c: Add prepare_upstream_first flag - brcmfmac: Restore ISO3166 and 0 rev as a fallback - drm/vc4: Force trigger of dlist update on margins change (#4970) - configs: Re-enable all GSPCA camera modules * dependency on crda obsolete according to Debian (LP: #1958918) - [Packaging] switch dependency from crda to wireless-regdb * Miscellaneous Ubuntu changes - [Config] raspi: Enable additional modules [ Ubuntu: 5.15.0-25.25 ] * jammy/linux: 5.15.0-25.25 -proposed tracker (LP: #1967146) * Miscellaneous Ubuntu changes - SAUCE: Revert "scsi: core: Reallocate device's budget map on queue depth change" [ Ubuntu: 5.15.0-24.24 ] * jammy/linux: 5.15.0-24.24 -proposed tracker (LP: #1966305) * Update OS policy capability handshake (LP: #1966089) - thermal: int340x: Update OS policy capability handshake * Jammy update: v5.15.30 upstream stable release (LP: #1966057) - Revert "xfrm: state and policy should fail if XFRMA_IF_ID 0" - arm64: dts: rockchip: fix rk3399-puma-haikou USB OTG mode - xfrm: Check if_id in xfrm_migrate - xfrm: Fix xfrm migrate issues when address family changes - arm64: dts: rockchip: fix rk3399-puma eMMC HS400 signal integrity - arm64: dts: rockchip: align pl330 node name with dtschema - arm64: dts: rockchip: reorder rk3399 hdmi clocks - arm64: dts: agilex: use the compatible "intel,socfpga-agilex-hsotg" - ARM: dts: rockchip: reorder rk322x hmdi clocks - ARM: dts: rockchip: fix a typo on rk3288 crypto-controller - mac80211: refuse aggregations sessions before authorized - MIPS: smp: fill in sibling and core maps earlier - ARM: 9178/1: fix unmet dependency on BITREVERSE for HAVE_ARCH_BITREVERSE - Bluetooth: hci_core: Fix leaking sent_cmd skb - can: rcar_canfd: rcar_canfd_channel_probe(): register the CAN device when fully ready - atm: firestream: check the return value of ioremap() in fs_init() - iwlwifi: don't advertise TWT support - drm/vrr: Set VRR capable prop only if it is attached to connector - nl80211: Update bss channel on channel switch for
[Kernel-packages] [Bug 1966499] Re: Recent 5.13 kernel has broken KVM support
Thanks for your feedback, I have submitted the patch for SRU: https://lists.ubuntu.com/archives/kernel-team/2022-April/129362.html ** Description changed: + [Impact] + This is caused by commit 08335308 "KVM: x86: check PIR even for vCPUs + with disabled APICv", this patch needs 7e1901f6c "KVM: VMX: prepare + sync_pir_to_irr for running with APICv disabled" otherwise if APICv + is disabled in this vcpu it will trigger warning messages in + vmx_sync_pir_to_irr() of vmx.c: + WARN_ON(!vcpu->arch.apicv_active); + + With warnings like: + [ cut here ] + WARNING: CPU: 13 PID: 6997 at arch/x86/kvm/vmx/vmx.c:6336 vmx_sync_pir_to_irr+0x9e/0xc0 [kvm_intel] + ? xfer_to_guest_mode_work+0xe2/0x110 + Modules linked in: vhost_net vhost vhost_iotlb tap xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp nft_compat nft_chain_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nft_counter nf_tables nfnetlink bridge stp llc nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua intel_rapl_msr intel_rapl_common sb_edac x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm joydev input_leds ioatdma rapl intel_cstate efi_pstore ipmi_si mei_me mei mac_hid acpi_pad + vcpu_run+0x4d/0x220 [kvm] + acpi_power_meter sch_fq_codel ipmi_devintf ipmi_msghandler msr ip_tables x_tables autofs4 btrfs blake2b_generic zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear hid_generic usbhid hid mgag200 i2c_algo_bit drm_kms_helper crct10dif_pclmul syscopyarea crc32_pclmul sysfillrect sysimgblt ghash_clmulni_intel fb_sys_fops ixgbe cec aesni_intel rc_core crypto_simd xfrm_algo cryptd drm ahci dca i2c_i801 xhci_pci mdio libahci i2c_smbus lpc_ich xhci_pci_renesas wmi + CPU: 13 PID: 6997 Comm: qemu-system-x86 Tainted: G W I 5.13.0-39-generic #44-Ubuntu + Hardware name: Intel Corporation S2600WTT/S2600WTT, BIOS SE5C610.86B.01.01.1008.031920151331 03/19/2015 + kvm_arch_vcpu_ioctl_run+0xc5/0x4f0 [kvm] + RIP: 0010:vmx_sync_pir_to_irr+0x9e/0xc0 [kvm_intel] + Code: e8 47 f5 18 00 8b 93 00 03 00 00 89 45 ec 83 e2 20 85 d2 74 dc 48 8b 55 f0 65 48 2b 14 25 28 00 00 00 75 1d 48 8b 5d f8 c9 c3 <0f> 0b eb 87 f0 80 4b 39 40 8b 93 00 03 00 00 8b 45 ec 83 e2 20 eb + RSP: 0018:ae4d8d107c98 EFLAGS: 00010046 + RAX: RBX: 99c552942640 RCX: 99c5043a72f0 + RDX: 99c552942640 RSI: 0001 RDI: 99c552942640 + RBP: ae4d8d107cb0 R08: 99c86f6a7140 R09: 00027100 + R10: 4228 R11: 000a R12: 99c552942640 + R13: R14: ae4d8d1a63e0 R15: 99c552942640 + FS: 7f6ae9be7640() GS:99c86f68() knlGS: + CS: 0010 DS: ES: CR0: 80050033 + CR2: CR3: 00010b8a6006 CR4: 001726e0 + Call Trace: + + kvm_vcpu_ioctl+0x243/0x5e0 [kvm] + vcpu_enter_guest+0x383/0xf50 [kvm] + ? xfer_to_guest_mode_work+0xe2/0x110 + ? kvm_vm_ioctl+0x364/0x730 [kvm] + ? __fget_files+0x86/0xc0 + vcpu_run+0x4d/0x220 [kvm] + __x64_sys_ioctl+0x91/0xc0 + do_syscall_64+0x61/0xb0 + ? fput+0x13/0x20 + ? exit_to_user_mode_prepare+0x37/0xb0 + ? syscall_exit_to_user_mode+0x27/0x50 + ? do_syscall_64+0x6e/0xb0 + ? syscall_exit_to_user_mode+0x27/0x50 + ? do_syscall_64+0x6e/0xb0 + ? do_syscall_64+0x6e/0xb0 + ? do_syscall_64+0x6e/0xb0 + entry_SYSCALL_64_after_hwframe+0x44/0xae + RIP: 0033:0x7f6aebce1a2b + Code: ff ff ff 85 c0 79 8b 49 c7 c4 ff ff ff ff 5b 5d 4c 89 e0 41 5c c3 66 0f 1f 84 00 00 00 00 00 f3 0f 1e fa b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d d5 f3 0f 00 f7 d8 64 89 01 48 + RSP: 002b:7f6ae8ffe3f8 EFLAGS: 0246 ORIG_RAX: 0010 + RAX: ffda RBX: ae80 RCX: 7f6aebce1a2b + RDX: RSI: ae80 RDI: 000c + RBP: 557d3b429b90 R08: 557d3a4ebff0 R09: + kvm_arch_vcpu_ioctl_run+0xc5/0x4f0 [kvm] + R10: 0001 R11: 0246 R12: + R13: 0001 R14: 3000 R15: + + ---[ end trace 5b722d71a78069b1 ]--- + + This warning message will be flooding in system log files and + eventually eat up all the disk space then crash the server. + + This issue will gone by either reverting it or adding the fixes below. + + Reference: + https://patchwork.kernel.org/project/kvm/patch/2028072531.1534938-1-pbonz...@redhat.com/ + + [Fixes] + * 0b8f11737 KVM: Add infrastructure and macro to mark VM as bugged + * 673692735 KVM: x86: Use KVM_BUG/KVM_BUG_ON to handle bugs that are fatal to the VM + * 7e1901f6c KVM: VMX: prepare sync_pir_to_irr for running with APICv disabled + + The fix comes in two fold, the first two patches will fix the warning + message flooding issue, make it only gets printed once. The third + patch will change the prevent this to happen. + + The first patch needs to be backported
[Kernel-packages] [Bug 1967733] Re: jammy/linux-raspi: Update to upstream raspberrypi rpi-5.15.y (2022-04-04)
This bug was fixed in the package linux-raspi - 5.15.0-1005.5 --- linux-raspi (5.15.0-1005.5) jammy; urgency=medium * jammy/linux-raspi: 5.15.0-1005.5 -proposed tracker (LP: #1966493) * jammy/linux-raspi: Update to upstream raspberrypi rpi-5.15.y (2022-04-04) (LP: #1967733) - bcm2835-codec: /dev/video31 as interface to image_encode JPEG encoder - media: entity: Skip non-data links in graph iteration - media: media.h: Add new media link type - media: entity: Add link_type_name() helper - media: entity: Add support for ancillary links - media: v4l2-async: Create links during v4l2_async_match_notify() - dt-bindings: media: i2c: Add binding for ad5398 VCM - media: i2c: Add driver for AD5398 VCM lens driver - media: i2c: ov5647: Use v4l2_async_register_subdev_sensor for lens binding - defconfigs: Add AD5398 VCM to all Pi defconfigs - dtoverlays: Add VCM option to imx219 - dtoverlay: Add VCM option to ov5647 overlay - media: i2c: Rename ad5398 to ad5398_vcm - drm/object: Add drm_object_property_get_default_value() function - drm/object: Add default zpos value at reset - drm/object: Add default color encoding and range value at reset - drm/vc4: Support zpos on all planes - CM3 cam1_reg and cam1_reg_gpio fix - overlays: Fix cam*_reg_gpio parameter on CM1 - overlays: iqs550: Enable interrupt pull-down - dtoverlays: Connect the backlight to the pitft35 display - drm/vc4: hdmi: Add CSC for BT601/709/2020 limited and full range output - Revert "usb: xhci: expand the scope of XHCI_VLI_SS_BULK_OUT_BUG" - vc4/drm: vc4_plane: Keep fractional source coords inside state - vc4/drm: Handle fractional coordinates using the phase field - drm: Add chroma siting properties - vc4/drm:plane: Make use of chroma siting parameter - drivers: staging: bcm2835-isp: Clear LS table handle in the firmware - dt-bindings: display: add bindings for MIPI DBI compatible SPI panels - drm/modes: Add of_get_drm_panel_display_mode() - drm/mipi-dbi: Add driver_private member to struct mipi_dbi_dev - drm/tiny: Add MIPI DBI compatible SPI driver - configs: Add MIPI DBI display driver - overlays: Add overlay for MIPI DBI displays - audioinjector.net: stereo and zero, use dev_err_probe, report success - Revert "update rpi-display-overlay.dts pins for 5.10+" - overlays/rpi-display: Add support for DRM driver - bcm2835-codec: Return empty buffers to the VPU instead of queueing to vbuf2 - mm,page_alloc,cma: introduce a customisable threshold for allocating pages in cma - pinctrl: bcm2835: Only return non-GPIOs to inputs - ARM: dts: Enable PMU on Cortex-A72 in AArch32 state - drm/panel: ilitek-ili9881c: Clean up on mipi_dsi_attach failure - drm/panel: panel-ilitek9881c: Add prepare_upstream_first flag - brcmfmac: Restore ISO3166 and 0 rev as a fallback - drm/vc4: Force trigger of dlist update on margins change (#4970) - configs: Re-enable all GSPCA camera modules * dependency on crda obsolete according to Debian (LP: #1958918) - [Packaging] switch dependency from crda to wireless-regdb * Miscellaneous Ubuntu changes - [Config] raspi: Enable additional modules [ Ubuntu: 5.15.0-25.25 ] * jammy/linux: 5.15.0-25.25 -proposed tracker (LP: #1967146) * Miscellaneous Ubuntu changes - SAUCE: Revert "scsi: core: Reallocate device's budget map on queue depth change" [ Ubuntu: 5.15.0-24.24 ] * jammy/linux: 5.15.0-24.24 -proposed tracker (LP: #1966305) * Update OS policy capability handshake (LP: #1966089) - thermal: int340x: Update OS policy capability handshake * Jammy update: v5.15.30 upstream stable release (LP: #1966057) - Revert "xfrm: state and policy should fail if XFRMA_IF_ID 0" - arm64: dts: rockchip: fix rk3399-puma-haikou USB OTG mode - xfrm: Check if_id in xfrm_migrate - xfrm: Fix xfrm migrate issues when address family changes - arm64: dts: rockchip: fix rk3399-puma eMMC HS400 signal integrity - arm64: dts: rockchip: align pl330 node name with dtschema - arm64: dts: rockchip: reorder rk3399 hdmi clocks - arm64: dts: agilex: use the compatible "intel,socfpga-agilex-hsotg" - ARM: dts: rockchip: reorder rk322x hmdi clocks - ARM: dts: rockchip: fix a typo on rk3288 crypto-controller - mac80211: refuse aggregations sessions before authorized - MIPS: smp: fill in sibling and core maps earlier - ARM: 9178/1: fix unmet dependency on BITREVERSE for HAVE_ARCH_BITREVERSE - Bluetooth: hci_core: Fix leaking sent_cmd skb - can: rcar_canfd: rcar_canfd_channel_probe(): register the CAN device when fully ready - atm: firestream: check the return value of ioremap() in fs_init() - iwlwifi: don't advertise TWT support - drm/vrr: Set VRR capable prop only if it is attached to connector - nl80211: Update bss channel on channel switch for
[Kernel-packages] [Bug 1950778] Re: Ubuntu 20.04.3 generates IO error message during FIO stress.
** Changed in: linux (Ubuntu) Status: Expired => 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/1950778 Title: Ubuntu 20.04.3 generates IO error message during FIO stress. Status in linux package in Ubuntu: Incomplete Bug description: With fio stress on Powerstore fcoe drives (lun) attached by using Qlogic QL41000 series controller, ubuntu 20.04.3 on MX740c blade server generates below mentioned i/o errors. Nov 11 20:25:17 e2e-l10-058234 kernel: [:3b:00.3]:[qedf_process_error_detect:1523]:13: Error detection CQE, xid=0x7bd Nov 11 20:25:17 e2e-l10-058234 kernel: [:3b:00.3]:[qedf_process_error_detect:1525]:13: err_warn_bitmap=0040: Nov 11 20:25:17 e2e-l10-058234 kernel: [:3b:00.3]:[qedf_process_error_detect:1529]:13: tx_buff_off=, rx_buff_off=, rx_id=041b Nov 11 20:25:19 e2e-l10-058234 kernel: [:3b:00.2]:[qedf_process_error_detect:1523]:3: Error detection CQE, xid=0x34d Nov 11 20:25:19 e2e-l10-058234 kernel: [:3b:00.2]:[qedf_process_error_detect:1525]:3: err_warn_bitmap=0040: Nov 11 20:25:19 e2e-l10-058234 kernel: [:3b:00.2]:[qedf_process_error_detect:1529]:3: tx_buff_off=, rx_buff_off=, rx_id=01f7 Steps to reproduce. 1. Configure QL41000 series controller on MX MX740c blade server. 2. Configure APM3246 array directly connected to chassis module MX9116n. 3. Install Ubuntu 20.04.3 in any local drive. 4. start I/O by using fio : # fio FileSystemCreateSingle/fio_test.cfg then we can observe error message in syslog To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950778/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1961819] Re: CT: Offload only ASSURED connections
This bug is awaiting verification that the linux-bluefield/5.4.0-1033.36 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/1961819 Title: CT: Offload only ASSURED connections Status in linux-bluefield package in Ubuntu: Invalid Status in linux-bluefield source package in Focal: Fix Committed Bug description: * Explain the feature Assured connections are those connections which deemed of "higher quality" and less like to expire than non-assured connections, as they passed some stricter rule (e.g in udp reply + connection lasting more than 2 seconds). This feature offloads only those connections. * How to test Create OVS bridge with 2 devices mlx5 rep devices. Enable HW offload and configure regular connection tracking OpenFlow rules: e.g: ovs-ofctl del-flows br-ovs ovs-ofctl add-flow br-ovs arp,actions=normal ovs-ofctl add-flow br-ovs "table=0, ip,ct_state=-trk actions=ct(table=1)" ovs-ofctl add-flow br-ovs "table=1, ip,ct_state=+trk+new actions=ct(commit),normal" ovs-ofctl add-flow br-ovs "table=1, ip,ct_state=+trk+est, actions=normal" Run a short UDP connection (< 2 seconds), e.g: on mlx5 VF1 iperf -s -u on mlx5 VF2 iperf -c -t 1 -u Run longer UDP connection (> 2 seconds), e.g: on mlx5 VF1 iperf -s -u on mlx5 VF2 iperf -c -t 10 -u With the above commit quick lived UDP connections (< 2 seconds) will not be offloaded to the flow table as can be checked by cat /proc/net/nf_conntrack | grep -i offload while connections lasting more than 2 seconds (and of course double sided) will be offloaded. * What it could break. NA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1961819/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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] Re: Fix flow table lookup after ct clear or switching zones
This bug is awaiting verification that the linux-bluefield/5.4.0-1033.36 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-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: Invalid Status in linux-bluefield source package in Focal: Fix Committed 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 1964984] Re: Fix OOB handling RX packets in heavy traffic
This bug is awaiting verification that the linux-bluefield/5.4.0-1033.36 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/1964984 Title: Fix OOB handling RX packets in heavy traffic Status in linux-bluefield package in Ubuntu: Invalid Status in linux-bluefield source package in Focal: Fix Committed Bug description: SRU Justification: [Impact] This is reproducible on systems which already have heavy background traffic. On top of that, the user issues one of the 2 docker pulls below: docker pull nvcr.io/ea-doca-hbn/hbn/hbn:latest OR docker pull gitlab-master.nvidia.com:5005/dl/dgx/tritonserver:22.02-py3-qa The second one is a very large container (17GB) When they run docker pull, the OOB interface stops being pingable, the docker pull is interrupted for a very long time (>3mn) or times out. [Fix] * Update the RX_CQE_CI before updating the RX_PI to avoid a race condition where we wrongly inform HW that there is space for the WQE. * disable the RX DMA while we are handling incoming packets to avoid overflow. [Test Case] * Created a script which loops 200 times and does a docker pull in each loop: docker pull nvcr.io/ea-doca-hbn/hbn/hbn:latest OR docker pull gitlab-master.nvidia.com:5005/dl/dgx/tritonserver:22.02-py3-qa [Regression Potential] * This could result in slower handling since we are disabling/enabling the DMA periodically. * Although this fix has been tested by the people who opened the bug, QA needs to thoroughly test it to make sure it is not reproducible. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1964984/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1962490] Re: Support VF groups rate limit
This bug is awaiting verification that the linux-bluefield/5.4.0-1033.36 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/1962490 Title: Support VF groups rate limit Status in linux-bluefield package in Ubuntu: Invalid Status in linux-bluefield source package in Focal: Fix Committed Bug description: * Explain the feature Managing TX rate of VFs becomes non-trivial task when a big number of VFs are used. This issue can be handled with some grouping mechanism. Currently driver provide two ways to limit TX rate of the VF: TC police action and NDO API callback. Implementation of grouping within this two infrastructures problematic, due to the following: NDO API rate limiting is legacy feature, even though it's available in switchdev mode, and extending it with new abstraction is not good anyway; TC police action is flow based and requires net device with Qdisc on it and implementing this will bring unwanted complications. According to aforesaid devlink is the most appropriate place. * How to test Set tx_max value on the devlink port with a command. For ex.: $ devlink port function rate set pci/:82:00.0/1 tx_max 10gbit or if grouping is required, create rate group with configured tx_max value in a single command and assign port to this group: $ devlink port function rate add pci/:82:00.0/1st_group tx_max 8gbit $ devlink port function rate set pci/:82:00.0/1 tx_max 10gbit parent 1st_group Configuration is done. Run traffic and do measurement. * What it could break. As this pull request backported 130 patches from devlink/netlink, it may break some functionalities from net core layer. Also, the network drivers which are not used by BF are disabled to avoid the fix of conflicts. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1962490/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1965017] Re: Sync up gpio interrupt handling with upstreamed version
This bug is awaiting verification that the linux-bluefield/5.4.0-1033.36 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/1965017 Title: Sync up gpio interrupt handling with upstreamed version Status in linux-bluefield package in Ubuntu: Invalid Status in linux-bluefield source package in Focal: Fix Committed Bug description: SRU Justification: [Impact] Although the gpio-mlxbf2.c driver has already been upstreamed, it did not include gpio interrupt handling. We recently upstreamed the latter and as requested by maintainers, moved all gpio interrupt code from the mlxbf-gige driver to the gpio-mlxbf2.c to be conform with linux standards. IMPORTANT: during testing, make sure the latest UEFI (bootloader) is loaded on top of these changes, otherwise both the gpio driver and mlxbf-gige driver will fail to load. [Fix] * reverted 6 commits related to the gpio-mlxbf2 driver so that the canonical changes are in sync with what is upstreamed. * Cherry-picked 11 gpio-mlxbf2.c commits from the linux master branch. 10 commits are minor commits added by other maintainers. The 11th cherry-picked commit is the one adding proper interrupt support in the gpio-mlxbf2.c driver. The upstreamed version of the GPIO driver added back the dependency between the mlxbf-gige driver and gpio-mlxbf2 driver. * Added one commit on top of the above to add the driver version and fix the SPDX Licence identifier. * updated the UEFI ACPI table to reflect the above changes (so the bootloader and the linux drivers need to be in sync) * Following the generic way of writing a linux gpio driver, we created a separate driver for power handling (low power and reboot) called pwr-mlxbf.c. This driver has not been upstreamed yet but will take care of the GPIO7 software reset and the OCP3.0 GPIO low power mode. Previously all this code was integrated within the gpio-mlxbf2.c driver. [Test Case] * oob_net0 coming up after several SW_RESET or reboot * oob_net0 coming up after several powercycles * oob_net0 coming up after pushing a new Ubuntu/CentOS/Yocto * rmmod/modprobe mlxbf_gige several times * Test that GPIO7 reset still works on BlueSphere like boards [Regression Potential] Any of the test cases above could be impacted due to these changes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1965017/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1960575] Re: Pass originating device to drivers offloading ct connection so devices will filter the tuples and offload them more efficiently
This bug is awaiting verification that the linux-bluefield/5.4.0-1033.36 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/1960575 Title: Pass originating device to drivers offloading ct connection so devices will filter the tuples and offload them more efficiently Status in linux-bluefield package in Ubuntu: Invalid Status in linux-bluefield source package in Focal: Fix Committed Bug description: * Explain the feature Currently, drivers register to a ct zone that can be shared by multiple devices. This can be inefficient for the driver to offload, as it needs to handle all the cases where the tuple can come from, instead of where it's most likely will arive from. For example, consider the following tc rules: tc filter add dev dev1 ... flower action ct commit zone 5 \ action mirred egress redirect dev dev2 tc filter add dev dev2 ... flower action ct zone 5 \ action goto chain chain 2 tc filter add dev dev2 ... flower ct_state +trk+est ... \ action mirred egress redirect dev dev1 Both dev2 and dev1 register to the zone 5 flow table (created by act_ct). A tuple originating on dev1, going to dev2, will be offloaded to both devices, and both will need to offload both directions, resulting in 4 total rules. The traffic will only hit originiating tuple on dev1, and reply tuple on dev2. By passing the originating device that created the connection with the tuple, dev1 can choose to offload only the originating tuple, and dev2 only the reply tuple. Resulting in a more efficient offload. The first patch adds an act_ct nf conntrack extension, to temporarily store the originiating device from the skb before offloading the connection once the connection is established. Once sent to offload, it fills the tuple originating device. The second patch get this information from tuples which pass in openvswitch. The third patch is Mellanox driver ct offload implementation using this information to provide a hint to firmware of where this offloaded tuple packets will arrive from (LOCAL or UPLINK port), and thus increase insertion rate. * How to test Create OVS bridge with 2 devices mlx5 rep devices. Enable HW offload and configure regular connection tracking OpenFlow rules: e.g: ovs-ofctl del-flows br-ovs ovs-ofctl add-flow br-ovs arp,actions=normal ovs-ofctl add-flow br-ovs "table=0, ip,ct_state=-trk actions=ct(table=1)" ovs-ofctl add-flow br-ovs "table=1, ip,ct_state=+trk+new actions=ct(commit),normal" ovs-ofctl add-flow br-ovs "table=1, ip,ct_state=+trk+est, actions=normal" With SW steering enabled and the above commits (and up to date ofed) tuple insertion rate should be about twice as fast. This can be seen via procfs hw offloaded count while running high traffic: while true; do res=`sudo cat /proc/net/nf_conntrack | grep -i offload` && echo "$res" && echo "$res" | wc -l; done * What it could break. NA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1960575/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1967892] Re: Fix flow table lookup failure with no originating ifindex
This bug is awaiting verification that the linux-bluefield/5.4.0-1033.36 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/1967892 Title: Fix flow table lookup failure with no originating ifindex Status in linux-bluefield package in Ubuntu: Invalid Status in linux-bluefield source package in Focal: Fix Committed Bug description: * Explain the bug After the CT ifindex extension feature, flow table entries are populated with ifindex information which was intended to only be used for HW offload. This tuple ifindex is hashed in the flow table key, so it must be filled for lookup to be successful. But tuple ifindex is only relevant for the netfilter flowtables (nft), so it's not filled in act_ct flow table lookup, resulting in lookup failure, and no SW offload and no offload teardown for TCP connection FIN/RST packets. To fix this, add new tc ifindex field to tuple, which will only be used for offloading, not for lookup, as it will not be part of the tuple hash. * How to test Create OVS bridge with 2 devices mlx5 rep devices. Enable HW offload and configure regular connection tracking OpenFlow rules: e.g: ovs-ofctl del-flows br-ovs ovs-ofctl add-flow br-ovs arp,actions=normal ovs-ofctl add-flow br-ovs "table=0, ip,ct_state=-trk actions=ct(table=1)" ovs-ofctl add-flow br-ovs "table=1, ip,ct_state=+trk+new actions=ct(commit),normal" ovs-ofctl add-flow br-ovs "table=1, ip,ct_state=+trk+est, actions=normal" Generate traffic at high rate (e.g. using IXIA). The number of offloaded rules exposed in /sys/kernel/debug/mlx5/\:$BUS\:00.0/ct/offloaded should be in synch the number of generated connections. * What it could break. Perhaps nft offload – it is not part of our tests To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1967892/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1961300] Re: linux-azure: Fix NUMA node assignment when kernel boots with custom NUMA topology
This bug is awaiting verification that the linux-
azure-5.4/5.4.0-1076.79~18.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-bionic' to
'verification-done-bionic'. If the problem still exists, change the tag
'verification-needed-bionic' to 'verification-failed-bionic'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: verification-needed-bionic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-5.11 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 Released
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 1965618] Re: linux-azure: Focal 5.4 arm64 support
This bug is awaiting verification that the linux- azure-5.4/5.4.0-1076.79~18.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-bionic -- 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/1965618 Title: linux-azure: Focal 5.4 arm64 support Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure source package in Focal: Fix Committed Bug description: SRU Justification [Impact] Focal linux-azure does not support arm64 [Fix] Backport/cherry-pick approximately 100 patches to support arm64 on hyperv [Where things could go wrong] A number of the patches reorganize hyperv CPU support. Therefore amd64 could be affected. [Other Info] SF: #00310705 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1965618/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1967336] Re: linux-azure: CONFIG_HIBERNATION=y
This bug is awaiting verification that the linux- azure-5.4/5.4.0-1076.79~18.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-bionic -- 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/1967336 Title: linux-azure: CONFIG_HIBERNATION=y Status in linux-azure package in Ubuntu: Fix Committed Status in linux-azure source package in Focal: Fix Committed Status in linux-azure source package in Impish: Fix Committed Status in linux-azure source package in Jammy: Fix Committed Bug description: SRU Justification [Impact] Azure arm64 tuned kernels do not support hibernation. [Test Plan] Microsoft tested [Where things could go wrong] Hibernation may fail. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1967336/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1968564] Re: linux-azure-cvm doesn't currently support arm64
** Description changed: [Impact] The current linux-azure-cvm doesn't need to support arm64. Ensure we skip the arm64 changes from the base kernel. [Test Plan] linux-azure-cvm doesn't need to produce arm64 binaries. [Where problems could occur] - It might cause problem during the rebase of linux-azure-cvm on top of + It might cause problems during the rebase of linux-azure-cvm on top of linux-azure. ** Also affects: linux-azure-cvm (Ubuntu Focal) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure-cvm in Ubuntu. https://bugs.launchpad.net/bugs/1968564 Title: linux-azure-cvm doesn't currently support arm64 Status in linux-azure-cvm package in Ubuntu: New Status in linux-azure-cvm source package in Focal: New Bug description: [Impact] The current linux-azure-cvm doesn't need to support arm64. Ensure we skip the arm64 changes from the base kernel. [Test Plan] linux-azure-cvm doesn't need to produce arm64 binaries. [Where problems could occur] It might cause problems during the rebase of linux-azure-cvm on top of linux-azure. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure-cvm/+bug/1968564/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1965618] Re: linux-azure: Focal 5.4 arm64 support
Microsoft tested ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1965618 Title: linux-azure: Focal 5.4 arm64 support Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure source package in Focal: Fix Committed Bug description: SRU Justification [Impact] Focal linux-azure does not support arm64 [Fix] Backport/cherry-pick approximately 100 patches to support arm64 on hyperv [Where things could go wrong] A number of the patches reorganize hyperv CPU support. Therefore amd64 could be affected. [Other Info] SF: #00310705 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1965618/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1968564] [NEW] linux-azure-cvm doesn't currently support arm64
Public bug reported: [Impact] The current linux-azure-cvm doesn't need to support arm64. Ensure we skip the arm64 changes from the base kernel. [Test Plan] linux-azure-cvm doesn't need to produce arm64 binaries. [Where problems could occur] It might cause problem during the rebase of linux-azure-cvm on top of linux-azure. ** Affects: linux-azure-cvm (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure-cvm in Ubuntu. https://bugs.launchpad.net/bugs/1968564 Title: linux-azure-cvm doesn't currently support arm64 Status in linux-azure-cvm package in Ubuntu: New Bug description: [Impact] The current linux-azure-cvm doesn't need to support arm64. Ensure we skip the arm64 changes from the base kernel. [Test Plan] linux-azure-cvm doesn't need to produce arm64 binaries. [Where problems could occur] It might cause problem during the rebase of linux-azure-cvm on top of linux-azure. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure-cvm/+bug/1968564/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1967166] Re: Azure: not enough RAM under 4GB for CVM
Microsoft tested ** Tags removed: verification-needed-impish ** Tags added: verification-done-impish -- 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/1967166 Title: Azure: not enough RAM under 4GB for CVM Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure source package in Impish: Fix Committed Status in linux-azure source package in Jammy: Fix Released Bug description: SRU Justification [Impact] Can you please include one more patchset for the "no enough RAM under 4GB" issue for the v5.13 kernel (and v5.15 kernel): https://lwn.net/ml/linux-kernel/20220209122302.213882-2-ltyker...@gmail.com/ https://lwn.net/ml/linux-kernel/20220209122302.213882-3-ltyker...@gmail.com/ Without the two patches, currently the 5.13 kernel (and 5.15 kernel) can't boot as a CVM guest on Azure. :-( The background is: currently an Azure host only provides about 900 MB memory below the 4GB boundary while the swiotlb code (which is required by the CVM patchset) needs to allocate memory of a size of MIN(1GB, 6% of the total memory). There will be an Azure host update, with which the host will provide about 3GB memory below the 4GB boundary, but we still need to wait a few more weeks to know the ETA. Currently the above two patches can work around the issue from the guest side. [Test Case] Microsoft tested [Where things could go wrong] These patches could affect non-CVM instances. [Other Info] SF: #00323683 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1967166/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1961329] Re: linux-azure: Update HV support to 5.17
Microsoft tested ** Tags removed: verification-needed-impish ** Tags added: verification-done-impish -- 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/1961329 Title: linux-azure: Update HV support to 5.17 Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure source package in Focal: New Status in linux-azure source package in Impish: Fix Committed Status in linux-azure source package in Jammy: Fix Released Bug description: SRU Justification [Impact] Microsoft has requested these commits be present in all Azure tuned kernels: ac0f7d42584125dab8039e60ab4ade48cc2db61c Drivers: hv: copy from message page only what's needed a276463b7aeb6186e7e4315cccb032773fb31b5d Drivers: hv: allocate the exact needed memory for messages 5cc415001bca8fe0e3f0ee6d58a953a314dd9751 Drivers: hv: avoid passing opaque pointer to vmbus_onmessage() b0a284dc65b401a508dc2c5ed7d465884220f607 Drivers: hv: make sure that 'struct vmbus_channel_message_header' compiles correctly 52c7803f9bd4b1f0ac6e2e3e6051415198cc06bd Drivers: hv: check VMBus messages lengths 06caa778d8b2fbcb4ac3878751e39d116424ba9b hv_utils: Add validation for untrusted Hyper-V values e99c4afbee07e9323e9191a20b24d74dbf815bdf Drivers: hv: vmbus: Initialize memory to be sent to the host fe8c1b18a27de4d6ca5d99b3ffb3125dc69a5b76 Drivers: hv: vmbus: Copy the hv_message in vmbus_on_msg_dpc() e3fa4b747f085d2cda09bba0533b86fa76038635 Drivers: hv: vmbus: Avoid use-after-free in vmbus_onoffer_rescind() e4d221b42354b2e2ddb9187a806afb651eee2cda Drivers: hv: vmbus: Resolve race condition in vmbus_onoffer_rescind() adae1e931acd8b430d31141a283ea06d4b705417 Drivers: hv: vmbus: Copy packets sent by Hyper-V out of the ring buffer 9d68cd9120e4e3af38f843e165631c323b86b4e4 hv_utils: Set the maximum packet size for VSS driver to the length of the receive buffer f1940d4e9cbe6208e7e77e433c587af108152a17 Drivers: hv: vmbus: Fix kernel crash upon unbinding a device from uio_hv_generic driver 007faec014cb5d26983c1f86fd08c6539b41392e x86/sev: Expose sev_es_ghcb_hv_call() for use by HyperV 0cc4f6d9f0b9f20f3f1e1149bdb6737c0b4e134a x86/hyperv: Initialize GHCB page in Isolation VM af788f355e343373490b7d2e361016e7c24a0ffa x86/hyperv: Initialize shared memory boundary in the Isolation VM. 810a521265023a1d5c6c081ea2d216bc63d422f5 x86/hyperv: Add new hvcall guest address host visibility support d4dccf353db80e209f262e3973c834e6e48ba9a9 Drivers: hv: vmbus: Mark vmbus ring buffer visible to host in Isolation VM faff44069ff538ccdfef187c4d7ec83d22dfb3a4 x86/hyperv: Add Write/Read MSR registers via ghcb page 20c89a559e00dfe352b73e867211a669113ae881 x86/hyperv: Add ghcb hvcall support for SNP VM f2f136c05fb6093818a3b3fefcba46231ac66a62 Drivers: hv: vmbus: Add SNP support for VMbus channel initiate message 9a8797722e4239242d0cb4cc4baa805df6ac979e Drivers: hv: vmbus: Initialize VMbus ring buffer for Isolation VM 1a5e91d8375fc8369207cc0b9894a324f2bbf1d9 swiotlb: Add swiotlb bounce buffer remap function for HV IVM c789b90a69045d1924bc0802ae0dce2bba05a04e x86/hyper-v: Add hyperv Isolation VM check in the cc_platform_has() 062a5c4260cdb734a4727230c58e38accf413315 hyper-v: Enable swiotlb bounce buffer for Isolation VM 743b237c3a7b0f5b44aa704aae8a1058877b6322 scsi: storvsc: Add Isolation VM support for storvsc driver 846da38de0e8224f2f94b885125cf1fd2d7b0d39 net: netvsc: Add Isolation VM support for netvsc driver 2deb55d9f57bb7a877c0d77115cc4077e1e974ff swiotlb: Add CONFIG_HAS_IOMEM check around swiotlb_mem_remap() 6a27e396ebb149fc47baccc1957a7a9dd70049a7 Drivers: hv: vmbus: Initialize request offers message for Isolation VM 4eea5332d67d8ae6ba5717ec0f4e671fdbd222e7 scsi: storvsc: Fix storvsc_queuecommand() memory leak 96d9d1fa5cd505078534113308ced0aa56d8da58 Drivers: hv: balloon: account for vmbus packet header in max_pkt_size [Test Plan] Microsoft tested [Where things could go wrong] Hyper-V guests may not work correctly. [Other Info] SF: #00323683 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1961329/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1967336] Re: linux-azure: CONFIG_HIBERNATION=y
Microsoft tested. ** Tags removed: verification-needed-focal verification-needed-impish ** Tags added: verification-done-focal verification-done-impish -- 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/1967336 Title: linux-azure: CONFIG_HIBERNATION=y Status in linux-azure package in Ubuntu: Fix Committed Status in linux-azure source package in Focal: Fix Committed Status in linux-azure source package in Impish: Fix Committed Status in linux-azure source package in Jammy: Fix Committed Bug description: SRU Justification [Impact] Azure arm64 tuned kernels do not support hibernation. [Test Plan] Microsoft tested [Where things could go wrong] Hibernation may fail. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1967336/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1968556] Re: nvidia-kernel-source-465 465.27-0ubuntu0.20.04.2: nvidia kernel module failed to build
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-465 in Ubuntu. https://bugs.launchpad.net/bugs/1968556 Title: nvidia-kernel-source-465 465.27-0ubuntu0.20.04.2: nvidia kernel module failed to build Status in nvidia-graphics-drivers-465 package in Ubuntu: New Bug description: i dont know ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-kernel-source-465 (not installed) ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-39-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip DKMSKernelVersion: 5.13.0-39-generic Date: Mon Apr 11 06:37:30 2022 DuplicateSignature: dkms:nvidia-kernel-source-465:465.27-0ubuntu0.20.04.2:/var/lib/dkms/nvidia/465.27/build/nvidia-drm/nvidia-drm-crtc.c:454:23: error: initialization of ‘int (*)(struct drm_plane *, struct drm_atomic_state *)’ from incompatible pointer type ‘int (*)(struct drm_plane *, struct drm_plane_state *)’ [-Werror=incompatible-pointer-types] InstallationDate: Installed on 2021-06-28 (286 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageVersion: 465.27-0ubuntu0.20.04.2 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: nvidia-graphics-drivers-465 Title: nvidia-kernel-source-465 465.27-0ubuntu0.20.04.2: nvidia kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-465/+bug/1968556/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1968026] PaInfo.txt
apport information
** Attachment added: "PaInfo.txt"
https://bugs.launchpad.net/bugs/1968026/+attachment/5579309/+files/PaInfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1968026
Title:
right-Alt + PrtScn + reisub does not work with USB keyboard and reisuo
does work. All works with a PS2 keyboard
Status in linux package in Ubuntu:
Confirmed
Bug description:
Left-Alt always works.
This has been the case with Ubuntu, Kubuntu, and Lubuntu for years.
r-e-i-s-u-b, printscrn, print scrn, printscreen, print screen, SysRq, SysReq
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-shell 42~beta-1ubuntu3
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
Uname: Linux 5.15.0-23-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
CasperMD5CheckResult: pass
CasperVersion: 1.468
CurrentDesktop: ubuntu:GNOME
Date: Wed Apr 6 09:45:00 2022
DisplayManager: gdm3
GsettingsChanges:
b'org.gnome.shell' b'command-history' redacted by apport
b'org.gnome.shell' b'favorite-apps' redacted by apport
b'org.gnome.shell' b'welcome-dialog-last-shown-version' b"'42.beta'"
b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us'), ('xkb',
'au'), ('xkb', 'cm'), ('xkb', 'gb')]"
b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1)
ProcEnviron:
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: ubuntu 5673 F pulseaudio
/dev/snd/controlC1: ubuntu 5673 F pulseaudio
CasperMD5CheckResult: pass
CasperVersion: 1.468
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 22.04
LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1)
MachineType: Dell Inc. Precision WorkStation T3500
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
Package: linux (not installed)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 nouveaudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz
file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash ---
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
RelatedPackageVersions:
linux-restricted-modules-5.15.0-23-generic N/A
linux-backports-modules-5.15.0-23-generic N/A
linux-firmware 20220314.gitcd01f857-0ubuntu2
RfKill:
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
Tags: jammy
Uname: Linux 5.15.0-23-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 05/28/2013
dmi.bios.release: 0.0
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A17
dmi.board.name: 09KPNV
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 7
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvrA17:bd05/28/2013:br0.0:svnDellInc.:pnPrecisionWorkStationT3500:pvr:rvnDellInc.:rn09KPNV:rvrA00:cvnDellInc.:ct7:cvr:sku:
dmi.product.name: Precision WorkStation T3500
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1968026/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1968026] Lspci-vt.txt
apport information
** Attachment added: "Lspci-vt.txt"
https://bugs.launchpad.net/bugs/1968026/+attachment/5579305/+files/Lspci-vt.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1968026
Title:
right-Alt + PrtScn + reisub does not work with USB keyboard and reisuo
does work. All works with a PS2 keyboard
Status in linux package in Ubuntu:
Confirmed
Bug description:
Left-Alt always works.
This has been the case with Ubuntu, Kubuntu, and Lubuntu for years.
r-e-i-s-u-b, printscrn, print scrn, printscreen, print screen, SysRq, SysReq
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-shell 42~beta-1ubuntu3
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
Uname: Linux 5.15.0-23-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
CasperMD5CheckResult: pass
CasperVersion: 1.468
CurrentDesktop: ubuntu:GNOME
Date: Wed Apr 6 09:45:00 2022
DisplayManager: gdm3
GsettingsChanges:
b'org.gnome.shell' b'command-history' redacted by apport
b'org.gnome.shell' b'favorite-apps' redacted by apport
b'org.gnome.shell' b'welcome-dialog-last-shown-version' b"'42.beta'"
b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us'), ('xkb',
'au'), ('xkb', 'cm'), ('xkb', 'gb')]"
b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1)
ProcEnviron:
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: ubuntu 5673 F pulseaudio
/dev/snd/controlC1: ubuntu 5673 F pulseaudio
CasperMD5CheckResult: pass
CasperVersion: 1.468
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 22.04
LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1)
MachineType: Dell Inc. Precision WorkStation T3500
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
Package: linux (not installed)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 nouveaudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz
file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash ---
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
RelatedPackageVersions:
linux-restricted-modules-5.15.0-23-generic N/A
linux-backports-modules-5.15.0-23-generic N/A
linux-firmware 20220314.gitcd01f857-0ubuntu2
RfKill:
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
Tags: jammy
Uname: Linux 5.15.0-23-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 05/28/2013
dmi.bios.release: 0.0
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A17
dmi.board.name: 09KPNV
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 7
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvrA17:bd05/28/2013:br0.0:svnDellInc.:pnPrecisionWorkStationT3500:pvr:rvnDellInc.:rn09KPNV:rvrA00:cvnDellInc.:ct7:cvr:sku:
dmi.product.name: Precision WorkStation T3500
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1968026/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1968026] acpidump.txt
apport information
** Attachment added: "acpidump.txt"
https://bugs.launchpad.net/bugs/1968026/+attachment/5579317/+files/acpidump.txt
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1968026
Title:
right-Alt + PrtScn + reisub does not work with USB keyboard and reisuo
does work. All works with a PS2 keyboard
Status in linux package in Ubuntu:
Confirmed
Bug description:
Left-Alt always works.
This has been the case with Ubuntu, Kubuntu, and Lubuntu for years.
r-e-i-s-u-b, printscrn, print scrn, printscreen, print screen, SysRq, SysReq
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-shell 42~beta-1ubuntu3
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
Uname: Linux 5.15.0-23-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
CasperMD5CheckResult: pass
CasperVersion: 1.468
CurrentDesktop: ubuntu:GNOME
Date: Wed Apr 6 09:45:00 2022
DisplayManager: gdm3
GsettingsChanges:
b'org.gnome.shell' b'command-history' redacted by apport
b'org.gnome.shell' b'favorite-apps' redacted by apport
b'org.gnome.shell' b'welcome-dialog-last-shown-version' b"'42.beta'"
b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us'), ('xkb',
'au'), ('xkb', 'cm'), ('xkb', 'gb')]"
b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1)
ProcEnviron:
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: ubuntu 5673 F pulseaudio
/dev/snd/controlC1: ubuntu 5673 F pulseaudio
CasperMD5CheckResult: pass
CasperVersion: 1.468
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 22.04
LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1)
MachineType: Dell Inc. Precision WorkStation T3500
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
Package: linux (not installed)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 nouveaudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz
file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash ---
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
RelatedPackageVersions:
linux-restricted-modules-5.15.0-23-generic N/A
linux-backports-modules-5.15.0-23-generic N/A
linux-firmware 20220314.gitcd01f857-0ubuntu2
RfKill:
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
Tags: jammy
Uname: Linux 5.15.0-23-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 05/28/2013
dmi.bios.release: 0.0
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A17
dmi.board.name: 09KPNV
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 7
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvrA17:bd05/28/2013:br0.0:svnDellInc.:pnPrecisionWorkStationT3500:pvr:rvnDellInc.:rn09KPNV:rvrA00:cvnDellInc.:ct7:cvr:sku:
dmi.product.name: Precision WorkStation T3500
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1968026/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1968026] ProcInterrupts.txt
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1968026/+attachment/5579312/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1968026
Title:
right-Alt + PrtScn + reisub does not work with USB keyboard and reisuo
does work. All works with a PS2 keyboard
Status in linux package in Ubuntu:
Confirmed
Bug description:
Left-Alt always works.
This has been the case with Ubuntu, Kubuntu, and Lubuntu for years.
r-e-i-s-u-b, printscrn, print scrn, printscreen, print screen, SysRq, SysReq
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-shell 42~beta-1ubuntu3
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
Uname: Linux 5.15.0-23-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
CasperMD5CheckResult: pass
CasperVersion: 1.468
CurrentDesktop: ubuntu:GNOME
Date: Wed Apr 6 09:45:00 2022
DisplayManager: gdm3
GsettingsChanges:
b'org.gnome.shell' b'command-history' redacted by apport
b'org.gnome.shell' b'favorite-apps' redacted by apport
b'org.gnome.shell' b'welcome-dialog-last-shown-version' b"'42.beta'"
b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us'), ('xkb',
'au'), ('xkb', 'cm'), ('xkb', 'gb')]"
b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1)
ProcEnviron:
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: ubuntu 5673 F pulseaudio
/dev/snd/controlC1: ubuntu 5673 F pulseaudio
CasperMD5CheckResult: pass
CasperVersion: 1.468
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 22.04
LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1)
MachineType: Dell Inc. Precision WorkStation T3500
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
Package: linux (not installed)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 nouveaudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz
file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash ---
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
RelatedPackageVersions:
linux-restricted-modules-5.15.0-23-generic N/A
linux-backports-modules-5.15.0-23-generic N/A
linux-firmware 20220314.gitcd01f857-0ubuntu2
RfKill:
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
Tags: jammy
Uname: Linux 5.15.0-23-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 05/28/2013
dmi.bios.release: 0.0
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A17
dmi.board.name: 09KPNV
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 7
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvrA17:bd05/28/2013:br0.0:svnDellInc.:pnPrecisionWorkStationT3500:pvr:rvnDellInc.:rn09KPNV:rvrA00:cvnDellInc.:ct7:cvr:sku:
dmi.product.name: Precision WorkStation T3500
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1968026/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1968026] UdevDb.txt
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1968026/+attachment/5579315/+files/UdevDb.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1968026
Title:
right-Alt + PrtScn + reisub does not work with USB keyboard and reisuo
does work. All works with a PS2 keyboard
Status in linux package in Ubuntu:
Confirmed
Bug description:
Left-Alt always works.
This has been the case with Ubuntu, Kubuntu, and Lubuntu for years.
r-e-i-s-u-b, printscrn, print scrn, printscreen, print screen, SysRq, SysReq
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-shell 42~beta-1ubuntu3
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
Uname: Linux 5.15.0-23-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
CasperMD5CheckResult: pass
CasperVersion: 1.468
CurrentDesktop: ubuntu:GNOME
Date: Wed Apr 6 09:45:00 2022
DisplayManager: gdm3
GsettingsChanges:
b'org.gnome.shell' b'command-history' redacted by apport
b'org.gnome.shell' b'favorite-apps' redacted by apport
b'org.gnome.shell' b'welcome-dialog-last-shown-version' b"'42.beta'"
b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us'), ('xkb',
'au'), ('xkb', 'cm'), ('xkb', 'gb')]"
b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1)
ProcEnviron:
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: ubuntu 5673 F pulseaudio
/dev/snd/controlC1: ubuntu 5673 F pulseaudio
CasperMD5CheckResult: pass
CasperVersion: 1.468
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 22.04
LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1)
MachineType: Dell Inc. Precision WorkStation T3500
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
Package: linux (not installed)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 nouveaudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz
file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash ---
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
RelatedPackageVersions:
linux-restricted-modules-5.15.0-23-generic N/A
linux-backports-modules-5.15.0-23-generic N/A
linux-firmware 20220314.gitcd01f857-0ubuntu2
RfKill:
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
Tags: jammy
Uname: Linux 5.15.0-23-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 05/28/2013
dmi.bios.release: 0.0
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A17
dmi.board.name: 09KPNV
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 7
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvrA17:bd05/28/2013:br0.0:svnDellInc.:pnPrecisionWorkStationT3500:pvr:rvnDellInc.:rn09KPNV:rvrA00:cvnDellInc.:ct7:cvr:sku:
dmi.product.name: Precision WorkStation T3500
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1968026/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1968026] PulseList.txt
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1968026/+attachment/5579314/+files/PulseList.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1968026
Title:
right-Alt + PrtScn + reisub does not work with USB keyboard and reisuo
does work. All works with a PS2 keyboard
Status in linux package in Ubuntu:
Confirmed
Bug description:
Left-Alt always works.
This has been the case with Ubuntu, Kubuntu, and Lubuntu for years.
r-e-i-s-u-b, printscrn, print scrn, printscreen, print screen, SysRq, SysReq
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-shell 42~beta-1ubuntu3
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
Uname: Linux 5.15.0-23-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
CasperMD5CheckResult: pass
CasperVersion: 1.468
CurrentDesktop: ubuntu:GNOME
Date: Wed Apr 6 09:45:00 2022
DisplayManager: gdm3
GsettingsChanges:
b'org.gnome.shell' b'command-history' redacted by apport
b'org.gnome.shell' b'favorite-apps' redacted by apport
b'org.gnome.shell' b'welcome-dialog-last-shown-version' b"'42.beta'"
b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us'), ('xkb',
'au'), ('xkb', 'cm'), ('xkb', 'gb')]"
b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1)
ProcEnviron:
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: ubuntu 5673 F pulseaudio
/dev/snd/controlC1: ubuntu 5673 F pulseaudio
CasperMD5CheckResult: pass
CasperVersion: 1.468
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 22.04
LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1)
MachineType: Dell Inc. Precision WorkStation T3500
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
Package: linux (not installed)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 nouveaudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz
file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash ---
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
RelatedPackageVersions:
linux-restricted-modules-5.15.0-23-generic N/A
linux-backports-modules-5.15.0-23-generic N/A
linux-firmware 20220314.gitcd01f857-0ubuntu2
RfKill:
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
Tags: jammy
Uname: Linux 5.15.0-23-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 05/28/2013
dmi.bios.release: 0.0
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A17
dmi.board.name: 09KPNV
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 7
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvrA17:bd05/28/2013:br0.0:svnDellInc.:pnPrecisionWorkStationT3500:pvr:rvnDellInc.:rn09KPNV:rvrA00:cvnDellInc.:ct7:cvr:sku:
dmi.product.name: Precision WorkStation T3500
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1968026/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1968026] Lsusb.txt
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1968026/+attachment/5579306/+files/Lsusb.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1968026
Title:
right-Alt + PrtScn + reisub does not work with USB keyboard and reisuo
does work. All works with a PS2 keyboard
Status in linux package in Ubuntu:
Confirmed
Bug description:
Left-Alt always works.
This has been the case with Ubuntu, Kubuntu, and Lubuntu for years.
r-e-i-s-u-b, printscrn, print scrn, printscreen, print screen, SysRq, SysReq
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-shell 42~beta-1ubuntu3
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
Uname: Linux 5.15.0-23-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
CasperMD5CheckResult: pass
CasperVersion: 1.468
CurrentDesktop: ubuntu:GNOME
Date: Wed Apr 6 09:45:00 2022
DisplayManager: gdm3
GsettingsChanges:
b'org.gnome.shell' b'command-history' redacted by apport
b'org.gnome.shell' b'favorite-apps' redacted by apport
b'org.gnome.shell' b'welcome-dialog-last-shown-version' b"'42.beta'"
b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us'), ('xkb',
'au'), ('xkb', 'cm'), ('xkb', 'gb')]"
b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1)
ProcEnviron:
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: ubuntu 5673 F pulseaudio
/dev/snd/controlC1: ubuntu 5673 F pulseaudio
CasperMD5CheckResult: pass
CasperVersion: 1.468
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 22.04
LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1)
MachineType: Dell Inc. Precision WorkStation T3500
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
Package: linux (not installed)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 nouveaudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz
file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash ---
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
RelatedPackageVersions:
linux-restricted-modules-5.15.0-23-generic N/A
linux-backports-modules-5.15.0-23-generic N/A
linux-firmware 20220314.gitcd01f857-0ubuntu2
RfKill:
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
Tags: jammy
Uname: Linux 5.15.0-23-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 05/28/2013
dmi.bios.release: 0.0
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A17
dmi.board.name: 09KPNV
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 7
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvrA17:bd05/28/2013:br0.0:svnDellInc.:pnPrecisionWorkStationT3500:pvr:rvnDellInc.:rn09KPNV:rvrA00:cvnDellInc.:ct7:cvr:sku:
dmi.product.name: Precision WorkStation T3500
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1968026/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1968026] ProcCpuinfo.txt
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1968026/+attachment/5579310/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1968026
Title:
right-Alt + PrtScn + reisub does not work with USB keyboard and reisuo
does work. All works with a PS2 keyboard
Status in linux package in Ubuntu:
Confirmed
Bug description:
Left-Alt always works.
This has been the case with Ubuntu, Kubuntu, and Lubuntu for years.
r-e-i-s-u-b, printscrn, print scrn, printscreen, print screen, SysRq, SysReq
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-shell 42~beta-1ubuntu3
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
Uname: Linux 5.15.0-23-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
CasperMD5CheckResult: pass
CasperVersion: 1.468
CurrentDesktop: ubuntu:GNOME
Date: Wed Apr 6 09:45:00 2022
DisplayManager: gdm3
GsettingsChanges:
b'org.gnome.shell' b'command-history' redacted by apport
b'org.gnome.shell' b'favorite-apps' redacted by apport
b'org.gnome.shell' b'welcome-dialog-last-shown-version' b"'42.beta'"
b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us'), ('xkb',
'au'), ('xkb', 'cm'), ('xkb', 'gb')]"
b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1)
ProcEnviron:
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: ubuntu 5673 F pulseaudio
/dev/snd/controlC1: ubuntu 5673 F pulseaudio
CasperMD5CheckResult: pass
CasperVersion: 1.468
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 22.04
LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1)
MachineType: Dell Inc. Precision WorkStation T3500
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
Package: linux (not installed)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 nouveaudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz
file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash ---
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
RelatedPackageVersions:
linux-restricted-modules-5.15.0-23-generic N/A
linux-backports-modules-5.15.0-23-generic N/A
linux-firmware 20220314.gitcd01f857-0ubuntu2
RfKill:
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
Tags: jammy
Uname: Linux 5.15.0-23-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 05/28/2013
dmi.bios.release: 0.0
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A17
dmi.board.name: 09KPNV
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 7
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvrA17:bd05/28/2013:br0.0:svnDellInc.:pnPrecisionWorkStationT3500:pvr:rvnDellInc.:rn09KPNV:rvrA00:cvnDellInc.:ct7:cvr:sku:
dmi.product.name: Precision WorkStation T3500
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1968026/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1968026] ProcModules.txt
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1968026/+attachment/5579313/+files/ProcModules.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1968026
Title:
right-Alt + PrtScn + reisub does not work with USB keyboard and reisuo
does work. All works with a PS2 keyboard
Status in linux package in Ubuntu:
Confirmed
Bug description:
Left-Alt always works.
This has been the case with Ubuntu, Kubuntu, and Lubuntu for years.
r-e-i-s-u-b, printscrn, print scrn, printscreen, print screen, SysRq, SysReq
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-shell 42~beta-1ubuntu3
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
Uname: Linux 5.15.0-23-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
CasperMD5CheckResult: pass
CasperVersion: 1.468
CurrentDesktop: ubuntu:GNOME
Date: Wed Apr 6 09:45:00 2022
DisplayManager: gdm3
GsettingsChanges:
b'org.gnome.shell' b'command-history' redacted by apport
b'org.gnome.shell' b'favorite-apps' redacted by apport
b'org.gnome.shell' b'welcome-dialog-last-shown-version' b"'42.beta'"
b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us'), ('xkb',
'au'), ('xkb', 'cm'), ('xkb', 'gb')]"
b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1)
ProcEnviron:
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: ubuntu 5673 F pulseaudio
/dev/snd/controlC1: ubuntu 5673 F pulseaudio
CasperMD5CheckResult: pass
CasperVersion: 1.468
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 22.04
LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1)
MachineType: Dell Inc. Precision WorkStation T3500
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
Package: linux (not installed)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 nouveaudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz
file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash ---
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
RelatedPackageVersions:
linux-restricted-modules-5.15.0-23-generic N/A
linux-backports-modules-5.15.0-23-generic N/A
linux-firmware 20220314.gitcd01f857-0ubuntu2
RfKill:
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
Tags: jammy
Uname: Linux 5.15.0-23-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 05/28/2013
dmi.bios.release: 0.0
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A17
dmi.board.name: 09KPNV
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 7
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvrA17:bd05/28/2013:br0.0:svnDellInc.:pnPrecisionWorkStationT3500:pvr:rvnDellInc.:rn09KPNV:rvrA00:cvnDellInc.:ct7:cvr:sku:
dmi.product.name: Precision WorkStation T3500
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1968026/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1968026] ProcCpuinfoMinimal.txt
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1968026/+attachment/5579311/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1968026
Title:
right-Alt + PrtScn + reisub does not work with USB keyboard and reisuo
does work. All works with a PS2 keyboard
Status in linux package in Ubuntu:
Confirmed
Bug description:
Left-Alt always works.
This has been the case with Ubuntu, Kubuntu, and Lubuntu for years.
r-e-i-s-u-b, printscrn, print scrn, printscreen, print screen, SysRq, SysReq
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-shell 42~beta-1ubuntu3
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
Uname: Linux 5.15.0-23-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
CasperMD5CheckResult: pass
CasperVersion: 1.468
CurrentDesktop: ubuntu:GNOME
Date: Wed Apr 6 09:45:00 2022
DisplayManager: gdm3
GsettingsChanges:
b'org.gnome.shell' b'command-history' redacted by apport
b'org.gnome.shell' b'favorite-apps' redacted by apport
b'org.gnome.shell' b'welcome-dialog-last-shown-version' b"'42.beta'"
b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us'), ('xkb',
'au'), ('xkb', 'cm'), ('xkb', 'gb')]"
b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1)
ProcEnviron:
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: ubuntu 5673 F pulseaudio
/dev/snd/controlC1: ubuntu 5673 F pulseaudio
CasperMD5CheckResult: pass
CasperVersion: 1.468
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 22.04
LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1)
MachineType: Dell Inc. Precision WorkStation T3500
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
Package: linux (not installed)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 nouveaudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz
file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash ---
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
RelatedPackageVersions:
linux-restricted-modules-5.15.0-23-generic N/A
linux-backports-modules-5.15.0-23-generic N/A
linux-firmware 20220314.gitcd01f857-0ubuntu2
RfKill:
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
Tags: jammy
Uname: Linux 5.15.0-23-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 05/28/2013
dmi.bios.release: 0.0
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A17
dmi.board.name: 09KPNV
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 7
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvrA17:bd05/28/2013:br0.0:svnDellInc.:pnPrecisionWorkStationT3500:pvr:rvnDellInc.:rn09KPNV:rvrA00:cvnDellInc.:ct7:cvr:sku:
dmi.product.name: Precision WorkStation T3500
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1968026/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1968026] WifiSyslog.txt
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1968026/+attachment/5579316/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1968026
Title:
right-Alt + PrtScn + reisub does not work with USB keyboard and reisuo
does work. All works with a PS2 keyboard
Status in linux package in Ubuntu:
Confirmed
Bug description:
Left-Alt always works.
This has been the case with Ubuntu, Kubuntu, and Lubuntu for years.
r-e-i-s-u-b, printscrn, print scrn, printscreen, print screen, SysRq, SysReq
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-shell 42~beta-1ubuntu3
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
Uname: Linux 5.15.0-23-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
CasperMD5CheckResult: pass
CasperVersion: 1.468
CurrentDesktop: ubuntu:GNOME
Date: Wed Apr 6 09:45:00 2022
DisplayManager: gdm3
GsettingsChanges:
b'org.gnome.shell' b'command-history' redacted by apport
b'org.gnome.shell' b'favorite-apps' redacted by apport
b'org.gnome.shell' b'welcome-dialog-last-shown-version' b"'42.beta'"
b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us'), ('xkb',
'au'), ('xkb', 'cm'), ('xkb', 'gb')]"
b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1)
ProcEnviron:
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: ubuntu 5673 F pulseaudio
/dev/snd/controlC1: ubuntu 5673 F pulseaudio
CasperMD5CheckResult: pass
CasperVersion: 1.468
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 22.04
LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1)
MachineType: Dell Inc. Precision WorkStation T3500
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
Package: linux (not installed)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 nouveaudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz
file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash ---
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
RelatedPackageVersions:
linux-restricted-modules-5.15.0-23-generic N/A
linux-backports-modules-5.15.0-23-generic N/A
linux-firmware 20220314.gitcd01f857-0ubuntu2
RfKill:
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
Tags: jammy
Uname: Linux 5.15.0-23-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 05/28/2013
dmi.bios.release: 0.0
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A17
dmi.board.name: 09KPNV
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 7
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvrA17:bd05/28/2013:br0.0:svnDellInc.:pnPrecisionWorkStationT3500:pvr:rvnDellInc.:rn09KPNV:rvrA00:cvnDellInc.:ct7:cvr:sku:
dmi.product.name: Precision WorkStation T3500
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1968026/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1968026] Lsusb-v.txt
apport information
** Attachment added: "Lsusb-v.txt"
https://bugs.launchpad.net/bugs/1968026/+attachment/5579308/+files/Lsusb-v.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1968026
Title:
right-Alt + PrtScn + reisub does not work with USB keyboard and reisuo
does work. All works with a PS2 keyboard
Status in linux package in Ubuntu:
Confirmed
Bug description:
Left-Alt always works.
This has been the case with Ubuntu, Kubuntu, and Lubuntu for years.
r-e-i-s-u-b, printscrn, print scrn, printscreen, print screen, SysRq, SysReq
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-shell 42~beta-1ubuntu3
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
Uname: Linux 5.15.0-23-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
CasperMD5CheckResult: pass
CasperVersion: 1.468
CurrentDesktop: ubuntu:GNOME
Date: Wed Apr 6 09:45:00 2022
DisplayManager: gdm3
GsettingsChanges:
b'org.gnome.shell' b'command-history' redacted by apport
b'org.gnome.shell' b'favorite-apps' redacted by apport
b'org.gnome.shell' b'welcome-dialog-last-shown-version' b"'42.beta'"
b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us'), ('xkb',
'au'), ('xkb', 'cm'), ('xkb', 'gb')]"
b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1)
ProcEnviron:
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: ubuntu 5673 F pulseaudio
/dev/snd/controlC1: ubuntu 5673 F pulseaudio
CasperMD5CheckResult: pass
CasperVersion: 1.468
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 22.04
LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1)
MachineType: Dell Inc. Precision WorkStation T3500
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
Package: linux (not installed)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 nouveaudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz
file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash ---
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
RelatedPackageVersions:
linux-restricted-modules-5.15.0-23-generic N/A
linux-backports-modules-5.15.0-23-generic N/A
linux-firmware 20220314.gitcd01f857-0ubuntu2
RfKill:
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
Tags: jammy
Uname: Linux 5.15.0-23-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 05/28/2013
dmi.bios.release: 0.0
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A17
dmi.board.name: 09KPNV
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 7
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvrA17:bd05/28/2013:br0.0:svnDellInc.:pnPrecisionWorkStationT3500:pvr:rvnDellInc.:rn09KPNV:rvrA00:cvnDellInc.:ct7:cvr:sku:
dmi.product.name: Precision WorkStation T3500
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1968026/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1968026] Lsusb-t.txt
apport information
** Attachment added: "Lsusb-t.txt"
https://bugs.launchpad.net/bugs/1968026/+attachment/5579307/+files/Lsusb-t.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1968026
Title:
right-Alt + PrtScn + reisub does not work with USB keyboard and reisuo
does work. All works with a PS2 keyboard
Status in linux package in Ubuntu:
Confirmed
Bug description:
Left-Alt always works.
This has been the case with Ubuntu, Kubuntu, and Lubuntu for years.
r-e-i-s-u-b, printscrn, print scrn, printscreen, print screen, SysRq, SysReq
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-shell 42~beta-1ubuntu3
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
Uname: Linux 5.15.0-23-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
CasperMD5CheckResult: pass
CasperVersion: 1.468
CurrentDesktop: ubuntu:GNOME
Date: Wed Apr 6 09:45:00 2022
DisplayManager: gdm3
GsettingsChanges:
b'org.gnome.shell' b'command-history' redacted by apport
b'org.gnome.shell' b'favorite-apps' redacted by apport
b'org.gnome.shell' b'welcome-dialog-last-shown-version' b"'42.beta'"
b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us'), ('xkb',
'au'), ('xkb', 'cm'), ('xkb', 'gb')]"
b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1)
ProcEnviron:
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: ubuntu 5673 F pulseaudio
/dev/snd/controlC1: ubuntu 5673 F pulseaudio
CasperMD5CheckResult: pass
CasperVersion: 1.468
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 22.04
LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1)
MachineType: Dell Inc. Precision WorkStation T3500
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
Package: linux (not installed)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 nouveaudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz
file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash ---
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
RelatedPackageVersions:
linux-restricted-modules-5.15.0-23-generic N/A
linux-backports-modules-5.15.0-23-generic N/A
linux-firmware 20220314.gitcd01f857-0ubuntu2
RfKill:
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
Tags: jammy
Uname: Linux 5.15.0-23-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 05/28/2013
dmi.bios.release: 0.0
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A17
dmi.board.name: 09KPNV
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 7
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvrA17:bd05/28/2013:br0.0:svnDellInc.:pnPrecisionWorkStationT3500:pvr:rvnDellInc.:rn09KPNV:rvrA00:cvnDellInc.:ct7:cvr:sku:
dmi.product.name: Precision WorkStation T3500
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1968026/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1968026] CRDA.txt
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1968026/+attachment/5579301/+files/CRDA.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1968026
Title:
right-Alt + PrtScn + reisub does not work with USB keyboard and reisuo
does work. All works with a PS2 keyboard
Status in linux package in Ubuntu:
Confirmed
Bug description:
Left-Alt always works.
This has been the case with Ubuntu, Kubuntu, and Lubuntu for years.
r-e-i-s-u-b, printscrn, print scrn, printscreen, print screen, SysRq, SysReq
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-shell 42~beta-1ubuntu3
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
Uname: Linux 5.15.0-23-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
CasperMD5CheckResult: pass
CasperVersion: 1.468
CurrentDesktop: ubuntu:GNOME
Date: Wed Apr 6 09:45:00 2022
DisplayManager: gdm3
GsettingsChanges:
b'org.gnome.shell' b'command-history' redacted by apport
b'org.gnome.shell' b'favorite-apps' redacted by apport
b'org.gnome.shell' b'welcome-dialog-last-shown-version' b"'42.beta'"
b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us'), ('xkb',
'au'), ('xkb', 'cm'), ('xkb', 'gb')]"
b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1)
ProcEnviron:
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: ubuntu 5673 F pulseaudio
/dev/snd/controlC1: ubuntu 5673 F pulseaudio
CasperMD5CheckResult: pass
CasperVersion: 1.468
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 22.04
LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1)
MachineType: Dell Inc. Precision WorkStation T3500
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
Package: linux (not installed)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 nouveaudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz
file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash ---
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
RelatedPackageVersions:
linux-restricted-modules-5.15.0-23-generic N/A
linux-backports-modules-5.15.0-23-generic N/A
linux-firmware 20220314.gitcd01f857-0ubuntu2
RfKill:
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
Tags: jammy
Uname: Linux 5.15.0-23-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 05/28/2013
dmi.bios.release: 0.0
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A17
dmi.board.name: 09KPNV
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 7
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvrA17:bd05/28/2013:br0.0:svnDellInc.:pnPrecisionWorkStationT3500:pvr:rvnDellInc.:rn09KPNV:rvrA00:cvnDellInc.:ct7:cvr:sku:
dmi.product.name: Precision WorkStation T3500
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1968026/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1968026] Lspci.txt
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1968026/+attachment/5579304/+files/Lspci.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1968026
Title:
right-Alt + PrtScn + reisub does not work with USB keyboard and reisuo
does work. All works with a PS2 keyboard
Status in linux package in Ubuntu:
Confirmed
Bug description:
Left-Alt always works.
This has been the case with Ubuntu, Kubuntu, and Lubuntu for years.
r-e-i-s-u-b, printscrn, print scrn, printscreen, print screen, SysRq, SysReq
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-shell 42~beta-1ubuntu3
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
Uname: Linux 5.15.0-23-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
CasperMD5CheckResult: pass
CasperVersion: 1.468
CurrentDesktop: ubuntu:GNOME
Date: Wed Apr 6 09:45:00 2022
DisplayManager: gdm3
GsettingsChanges:
b'org.gnome.shell' b'command-history' redacted by apport
b'org.gnome.shell' b'favorite-apps' redacted by apport
b'org.gnome.shell' b'welcome-dialog-last-shown-version' b"'42.beta'"
b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us'), ('xkb',
'au'), ('xkb', 'cm'), ('xkb', 'gb')]"
b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1)
ProcEnviron:
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: ubuntu 5673 F pulseaudio
/dev/snd/controlC1: ubuntu 5673 F pulseaudio
CasperMD5CheckResult: pass
CasperVersion: 1.468
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 22.04
LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1)
MachineType: Dell Inc. Precision WorkStation T3500
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
Package: linux (not installed)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 nouveaudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz
file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash ---
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
RelatedPackageVersions:
linux-restricted-modules-5.15.0-23-generic N/A
linux-backports-modules-5.15.0-23-generic N/A
linux-firmware 20220314.gitcd01f857-0ubuntu2
RfKill:
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
Tags: jammy
Uname: Linux 5.15.0-23-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 05/28/2013
dmi.bios.release: 0.0
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A17
dmi.board.name: 09KPNV
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 7
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvrA17:bd05/28/2013:br0.0:svnDellInc.:pnPrecisionWorkStationT3500:pvr:rvnDellInc.:rn09KPNV:rvrA00:cvnDellInc.:ct7:cvr:sku:
dmi.product.name: Precision WorkStation T3500
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1968026/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1968026] IwConfig.txt
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1968026/+attachment/5579303/+files/IwConfig.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1968026
Title:
right-Alt + PrtScn + reisub does not work with USB keyboard and reisuo
does work. All works with a PS2 keyboard
Status in linux package in Ubuntu:
Confirmed
Bug description:
Left-Alt always works.
This has been the case with Ubuntu, Kubuntu, and Lubuntu for years.
r-e-i-s-u-b, printscrn, print scrn, printscreen, print screen, SysRq, SysReq
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-shell 42~beta-1ubuntu3
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
Uname: Linux 5.15.0-23-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
CasperMD5CheckResult: pass
CasperVersion: 1.468
CurrentDesktop: ubuntu:GNOME
Date: Wed Apr 6 09:45:00 2022
DisplayManager: gdm3
GsettingsChanges:
b'org.gnome.shell' b'command-history' redacted by apport
b'org.gnome.shell' b'favorite-apps' redacted by apport
b'org.gnome.shell' b'welcome-dialog-last-shown-version' b"'42.beta'"
b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us'), ('xkb',
'au'), ('xkb', 'cm'), ('xkb', 'gb')]"
b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1)
ProcEnviron:
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: ubuntu 5673 F pulseaudio
/dev/snd/controlC1: ubuntu 5673 F pulseaudio
CasperMD5CheckResult: pass
CasperVersion: 1.468
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 22.04
LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1)
MachineType: Dell Inc. Precision WorkStation T3500
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
Package: linux (not installed)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 nouveaudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz
file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash ---
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
RelatedPackageVersions:
linux-restricted-modules-5.15.0-23-generic N/A
linux-backports-modules-5.15.0-23-generic N/A
linux-firmware 20220314.gitcd01f857-0ubuntu2
RfKill:
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
Tags: jammy
Uname: Linux 5.15.0-23-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 05/28/2013
dmi.bios.release: 0.0
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A17
dmi.board.name: 09KPNV
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 7
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvrA17:bd05/28/2013:br0.0:svnDellInc.:pnPrecisionWorkStationT3500:pvr:rvnDellInc.:rn09KPNV:rvrA00:cvnDellInc.:ct7:cvr:sku:
dmi.product.name: Precision WorkStation T3500
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1968026/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1968026] CurrentDmesg.txt
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1968026/+attachment/5579302/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1968026
Title:
right-Alt + PrtScn + reisub does not work with USB keyboard and reisuo
does work. All works with a PS2 keyboard
Status in linux package in Ubuntu:
Confirmed
Bug description:
Left-Alt always works.
This has been the case with Ubuntu, Kubuntu, and Lubuntu for years.
r-e-i-s-u-b, printscrn, print scrn, printscreen, print screen, SysRq, SysReq
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-shell 42~beta-1ubuntu3
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
Uname: Linux 5.15.0-23-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
CasperMD5CheckResult: pass
CasperVersion: 1.468
CurrentDesktop: ubuntu:GNOME
Date: Wed Apr 6 09:45:00 2022
DisplayManager: gdm3
GsettingsChanges:
b'org.gnome.shell' b'command-history' redacted by apport
b'org.gnome.shell' b'favorite-apps' redacted by apport
b'org.gnome.shell' b'welcome-dialog-last-shown-version' b"'42.beta'"
b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us'), ('xkb',
'au'), ('xkb', 'cm'), ('xkb', 'gb')]"
b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1)
ProcEnviron:
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: ubuntu 5673 F pulseaudio
/dev/snd/controlC1: ubuntu 5673 F pulseaudio
CasperMD5CheckResult: pass
CasperVersion: 1.468
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 22.04
LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1)
MachineType: Dell Inc. Precision WorkStation T3500
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
Package: linux (not installed)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 nouveaudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz
file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash ---
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
RelatedPackageVersions:
linux-restricted-modules-5.15.0-23-generic N/A
linux-backports-modules-5.15.0-23-generic N/A
linux-firmware 20220314.gitcd01f857-0ubuntu2
RfKill:
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
Tags: jammy
Uname: Linux 5.15.0-23-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 05/28/2013
dmi.bios.release: 0.0
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A17
dmi.board.name: 09KPNV
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 7
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvrA17:bd05/28/2013:br0.0:svnDellInc.:pnPrecisionWorkStationT3500:pvr:rvnDellInc.:rn09KPNV:rvrA00:cvnDellInc.:ct7:cvr:sku:
dmi.product.name: Precision WorkStation T3500
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1968026/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
