[Kernel-packages] [Bug 2038248] Re: Slab page exclusion issue on Linux 6.2-rc1
The package in -proposed has been successfully tested:
1:1.7.0-1ubuntu0.1 in Jammy, 1:1.7.2-1ubuntu0.1 in Lunar
** Tags removed: verification-needed verification-needed-jammy
verification-needed-lunar
** Tags added: verification-done verification-done-jammy verification-done-lunar
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to makedumpfile in Ubuntu.
https://bugs.launchpad.net/bugs/2038248
Title:
Slab page exclusion issue on Linux 6.2-rc1
Status in makedumpfile package in Ubuntu:
Fix Released
Status in makedumpfile source package in Jammy:
Fix Committed
Status in makedumpfile source package in Lunar:
Fix Committed
Bug description:
[Impact]
The kernel crashdumps generated by makedumpfile on kernel 6.2
(affects Lunar, and Jammy with the HWE kernel) might not open
on crash, due to kernel changes not reflected in makedumpfile.
The Kernel commit 130d4df57390 ("mm/sl[au]b: rearrange struct slab fields to
allow larger rcu_head"), included in Linux 6.2-rc1 and later versions,
introduced a change that aligns the offset of slab.slabs with that of
page.mapping.
However, this modification unintentionally causes the makedumpfile command
with the -d 8 option, meant to exclude user data, to incorrectly exclude
certain slab pages.
Consequently, when utilizing dumpfiles generated in this manner, the "crash"
utility may encounter an error when attempting to initiate a session:
crash: page excluded: kernel virtual address: e269d428 type:
"xa_node shift"
[Fix]
An upstream fix is available.
==
commit 5f17bdd2128998a3eeeb4521d136a19fadb6
Author: Kazuhito Hagio
Date: Wed Dec 21 11:06:39 2022 +0900
[PATCH] Fix wrong exclusion of slab pages on Linux 6.2-rc1
==
[Test Plan]
1. Install the required packages and then proceed to reboot the machine.
# sudo apt install crash linux-crashdump -y
# reboot
2. To check the status of kdump, use the `kdump-config show` command.
# kdump-config show
DUMP_MODE:kdump
USE_KDUMP:1
KDUMP_COREDIR:/var/crash
crashkernel addr: 0x6400
/var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinuz-6.2.0-33-generic
kdump initrd:
/var/lib/kdump/initrd.img: symbolic link to
/var/lib/kdump/initrd.img-6.2.0-33-generic
current state:ready to kdump
kexec command:
/sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinuz-6.2.0-33-generic
root=UUID=3e72f5d5-870b-4b8e-9a0d-8ba920391379 ro console=tty1 console=ttyS0
reset_devices systemd.unit=kdump-tools-dump.service nr_cpus=1 irqpoll
usbcore.nousb" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz
3. To trigger a crash dump forcefully, execute the `echo c | sudo tee
/proc/sysrq-trigger` command.
4. Download the kernel .ddeb file, which will be used for analyzing the dump
file.
# sudo -i
# cd /var/crash
# pull-lp-ddebs linux-image-unsigned-$(uname -r)
# dpkg-deb -x linux-image-unsigned-$(uname -r)-*.ddeb dbgsym-$(uname -r)
5. Utilize the "crash" utility to parse and analyze the dump file.
# crash dbgsym-$(uname -r)/usr/lib/debug/boot/vmlinux-$(uname -r)
/dump.
...
please wait... (gathering task table data)
crash: page excluded: kernel virtual address: e269d428 type:
"xa_node shift"
[Where problems could occur]
The patch has altered the method for excluding slab pages, aligning with the
structural changes introduced in Linux 6.2-rc1.
This modification is essential for Linux kernel 6.2.
However, it's crucial to note that this change may impact the content of the
dump file, potentially leading to a situation where the "crash" utility is
unable to parse it in the worst-case scenario.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/2038248/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2029899] Re: Update firmware for hwe-6.2/oem-6.5 kernel migrations
** Changed in: linux-firmware (Ubuntu Jammy) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2029899 Title: Update firmware for hwe-6.2/oem-6.5 kernel migrations Status in linux-firmware package in Ubuntu: Invalid Status in linux-firmware source package in Jammy: Fix Committed Bug description: [SRU Justification] [Impact] When migrating to a new hwe kernel or introduced a oem kernel of a newer version, the firmware blobs might not match the expectation of the new kernel. [Fix] For linux-hwe-6.2/jammy: $ debian/scripts/list-lts-update-files \ launchpad/jammy \ launchpad/lunar \ linux-hwe-6.2/debian.hwe-6.2/abi/fwinfo | \ xargs git log --graph --oneline launchpad/jammy..launchpad/lunar -- * d02d58aae brcm: Add nvram for the Advantech MICA-071 tablet * f48fbe42c ath11k: IPQ5018 hw1.0: add to WLAN.HK.2.6.0.1-00861-QCAHKSWPL_SILICONZ-1 * 9dacec6da ath11k: IPQ5018 hw1.0: add board-2.bin * 3723b4800 brcm: add configuration files for CyberTan WC121 * e9b83572f amdgpu: updated aldebaran firmware for amd-5.4 * 9aa8db1cc rtlwifi: Add firmware v4.0 for RTL8188FU * 2c2be4215 nvidia: add GA102/GA103/GA104/GA106/GA107 signed firmware * 4ffcf980a brcm: rename Rock960 NVRAM to AP6356S and link devices to it For linux-oem-6.5/jammy: $ debian/scripts/list-lts-update-files \ launchpad/jammy \ launchpad/mantic \ linux-oem-6.5/debian.oem/abi/fwinfo | \ xargs git log --graph --oneline launchpad/jammy..launchpad/mantic -- * 41e615cf3 i915: Update ADLP DMC to v2.20 * 22fb12f2f amdgpu: add initial SMU 13.0.10 firmware * b3f512fb5 amdgpu: add initial SDMA 6.0.3 firmware * b1a7d7624 amdgpu: add initial PSP 13.0.10 firmware * d6d655ade amdgpu: add initial GC 11.0.3 firmware * b255f5b92 (tag: iwlwifi-fw-2023-06-29, korg-iwlwifi/for-upstream) iwlwifi: add new FWs from core80-39 release * 84d5550e9 amdgpu: update aldebaran firmware for amd.5.5 release * 08b854f02 rtlwifi: Add firmware v6.0 for RTL8192FU * 9f7502f1d rtw89: 8852b: update format-1 fw to v0.29.29.1 * 78a8782a9 (tag: iwlwifi-fw-2023-03-30) iwlwifi: add new FWs from core78-32 release * 7f490a9a4 Merge branch 'dmc-adlp_2.19-mtl_2.12' of git://anongit.freedesktop.org/drm/drm-firmware |\ | * 4ee236dbb i915: Update ADLP DMC to v2.19 * | 2c07f017f rtw89: 8852b: update format-1 fw to v0.29.29.0 * | b50cf9205 rtw89: 8852b: add format-1 fw v0.29.26.0 |/ * 6a55abe94 Merge https://github.com/pkshih/linux-firmware |\ | * 4cc3eda63 rtlwifi: Add firmware v16.0 for RTL8710BU aka RTL8188GU * | d02d58aae brcm: Add nvram for the Advantech MICA-071 tablet |/ * 3653d692b rtl_bt: Add firmware and config files for RTL8821CS * f48fbe42c ath11k: IPQ5018 hw1.0: add to WLAN.HK.2.6.0.1-00861-QCAHKSWPL_SILICONZ-1 * 9dacec6da ath11k: IPQ5018 hw1.0: add board-2.bin * a5046f435 (drm/dmc-adlp_2.18) i915: Add DMC v2.18 for ADLP * 3723b4800 brcm: add configuration files for CyberTan WC121 * e9b83572f amdgpu: updated aldebaran firmware for amd-5.4 * 9aa8db1cc rtlwifi: Add firmware v4.0 for RTL8188FU * 2c2be4215 nvidia: add GA102/GA103/GA104/GA106/GA107 signed firmware * 4ffcf980a brcm: rename Rock960 NVRAM to AP6356S and link devices to it [Test Case] Boot linux-oem-6.5, linux-hwe-6.2 with Jammy base system. [Where problems could occur] These firmware blobs are only referenced in the new hwe/oem kernels, and shall not have side effect. [Other Info] While there is no hwe/oem kernel planned for Lunar, so only Jammy is nominated for fix. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2029899/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2023201] Re: Add support of Smart Amplifier IC ALC1319D on Intel platforms
Thanks for the review. According to https://github.com/thesofproject/sof- bin/issues/134#issuecomment-1718183989 adding versioned directories was a mistake by upstream, so I'll mangle the backport to still use v2.2.4 in the files directories and manifest/sha256sum, so the diff will look much better for review. ** Bug watch added: github.com/thesofproject/sof-bin/issues #134 https://github.com/thesofproject/sof-bin/issues/134 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2023201 Title: Add support of Smart Amplifier IC ALC1319D on Intel platforms Status in HWE Next: New Status in firmware-sof package in Ubuntu: Fix Released Status in linux package in Ubuntu: Confirmed Status in linux-oem-6.1 package in Ubuntu: Invalid Status in firmware-sof source package in Jammy: Fix Committed Status in linux source package in Jammy: Invalid Status in linux-oem-6.1 source package in Jammy: Fix Released Status in firmware-sof source package in Lunar: Triaged Status in linux source package in Lunar: Invalid Status in linux-oem-6.1 source package in Lunar: Invalid Status in firmware-sof source package in Mantic: Fix Released Status in linux source package in Mantic: Confirmed Status in linux-oem-6.1 source package in Mantic: Invalid Bug description: SRU Justification for firmware-sof [Impact] To support Smart Amplifier IC ALC1319D, it requires sof-bin v2.2.6 [Fix] Pull sof-bin v2.2.6 and for the completeness pull in v2.2.5, too [Test Case] Install the fixes on the target platform(RPL Dell SKU 0BDA) and verify the audio function. 1. Install the firmware-sof on platform(RPL) with Audio Smart AMP IC ALC1319D 2. Make sure the audio works 3. Also try above steps on other platforms(ADL/TGL) to make sure the audio keep working. [Where problems could occur] New firmware may affect ADL, RPL, and TGL platforms, we need to verify it on not only the target platform, but other existing platforms. [Misc] https://github.com/thesofproject/sof-bin/releases/tag/v2.2.5 https://github.com/thesofproject/sof-bin/releases/tag/v2.2.6 [Impact] Speaker is not functional on some Dell machines of Intel RPL platforms [Fix] Here's the patch submitted by Intel. https://patchwork.kernel.org/project/alsa-devel/patch/20230602202225.249209-16-pierre-louis.boss...@linux.intel.com/ [Test Case] 1. Power on the machine and open the audio settings 2. Verify it's not `Dummy Output` shown on the Audio output option [Where problems could occur] Only affect specific Intel RPL platforms. The risk of regression is low. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2023201/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2031287] Re: sysdig-dkms failed to build with J-oem-6.5
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-oem-6.5 (Ubuntu Jammy) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2031287 Title: sysdig-dkms failed to build with J-oem-6.5 Status in ubuntu-kernel-tests: New Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux-oem-6.5 source package in Jammy: Confirmed Bug description: ubuntu_sysdig_smoke_test failed because of sysdig DKMS build failed with J-oem-6.5 Error! Bad return status for module build on kernel: 6.5.0-1002-oem (x86_64) Consult /var/lib/dkms/sysdig/0.27.1/build/make.log for more information. dpkg: error processing package sysdig-dkms (--configure): installed sysdig-dkms package post-installation script subprocess returned error exit status 10 Processing triggers for man-db (2.10.2-1) ... Processing triggers for libc-bin (2.35-0ubuntu3.1) ... Errors were encountered while processing: sysdig-dkms needrestart is being skipped since dpkg has failed W: --force-yes is deprecated, use one of the options starting with --allow instead. E: Sub-process /usr/bin/dpkg returned an error code (1) Running 'dkms status -m sysdig | grep installed' Running 'cat /var/lib/dkms/sysdig/*/build/make.log' DKMS make.log for sysdig-0.27.1 for kernel 6.5.0-1002-oem (x86_64) Thu Aug 10 12:17:20 UTC 2023 make: Entering directory '/usr/src/linux-headers-6.5.0-1002-oem' warning: the compiler differs from the one used to build the kernel The kernel was built by: x86_64-linux-gnu-gcc-12 (Ubuntu 12.3.0-1ubuntu1~22.04) 12.3.0 You are using: gcc-12 (Ubuntu 12.3.0-1ubuntu1~22.04) 12.3.0 CC [M] /var/lib/dkms/sysdig/0.27.1/build/main.o CC [M] /var/lib/dkms/sysdig/0.27.1/build/dynamic_params_table.o CC [M] /var/lib/dkms/sysdig/0.27.1/build/fillers_table.o CC [M] /var/lib/dkms/sysdig/0.27.1/build/flags_table.o CC [M] /var/lib/dkms/sysdig/0.27.1/build/ppm_events.o In file included from ./include/linux/linkage.h:7, from ./arch/x86/include/asm/cache.h:5, from ./include/linux/cache.h:6, from ./arch/x86/include/asm/current.h:9, from ./include/linux/sched.h:12, from ./arch/x86/include/asm/syscall.h:14, from /var/lib/dkms/sysdig/0.27.1/build/main.c:19: /var/lib/dkms/sysdig/0.27.1/build/main.c: In function ‘sysdig_init’: ./include/linux/export.h:29:22: error: passing argument 1 of ‘class_create’ from incompatible pointer type [-Werror=incompatible-pointer-types] 29 | #define THIS_MODULE (&__this_module) | ~^~~ | | | struct module * /var/lib/dkms/sysdig/0.27.1/build/main.c:2484:36: note: in expansion of macro ‘THIS_MODULE’ 2484 | g_ppm_class = class_create(THIS_MODULE, PROBE_DEVICE_NAME); |^~~ In file included from ./include/linux/device.h:31, from ./include/linux/cdev.h:8, from /var/lib/dkms/sysdig/0.27.1/build/main.c:26: ./include/linux/device/class.h:230:54: note: expected ‘const char *’ but argument is of type ‘struct module *’ 230 | struct class * __must_check class_create(const char *name); | ^~~~ /var/lib/dkms/sysdig/0.27.1/build/main.c:2484:23: error: too many arguments to function ‘class_create’ 2484 | g_ppm_class = class_create(THIS_MODULE, PROBE_DEVICE_NAME); | ^~~~ ./include/linux/device/class.h:230:29: note: declared here 230 | struct class * __must_check class_create(const char *name); | ^~~~ cc1: some warnings being treated as errors make[2]: *** [scripts/Makefile.build:251: /var/lib/dkms/sysdig/0.27.1/build/main.o] Error 1 make[2]: *** Waiting for unfinished jobs make[1]: *** [/usr/src/linux-headers-6.5.0-1002-oem/Makefile:2037: /var/lib/dkms/sysdig/0.27.1/build] Error 2 make: *** [Makefile:234: __sub-make] Error 2 make: Leaving directory '/usr/src/linux-headers-6.5.0-1002-oem' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2031287/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2039542] [NEW] Remove duplication of devm_pwmchip_add function definition
Public bug reported: SRU Justification: [Impact] * Upstream commit 88da4e8113110d5f4ebdd2f8cd0899e300cd1954 "pwm: Add a stub for devm_pwmchip_add()", was applied the second time during the latest upstream patchset (#LP: 2037005) for cycle 2023.10.02. * `git am` did not detect that the changes were applied, leading to the same function definition being duplicated. * This was not caught when the main kernel was built because this code is under CONFIG_PWM=n. The main kernel and pretty much every kernel apart from linux-kvm, has CONFIG_PWM=y. * The problem was caught when lunar:linux-kvm was cranked and build failed with the following error: ``` In file included from /build/lunar/drivers/acpi/acpi_lpss.c:23: /build/lunar/include/linux/pwm.h:486:19: error: redefinition of 'devm_pwmchip_add' 486 | static inline int devm_pwmchip_add(struct device *dev, struct pwm_chip *chip) | ^~~~ /build/lunar/include/linux/pwm.h:481:19: note: previous definition of 'devm_pwmchip_add' with type 'int(struct device *, struct pwm_chip *)' 481 | static inline int devm_pwmchip_add(struct device *dev, struct pwm_chip *chip) | ^~~~ ``` [Fix] * Revert the commit. * Because this affects only linux:kvm, it is necessary to apply this fix for lunar:linux-kvm for cycle 2023.10.02, but the main kernel can wait for the next cycle. [Test plan] * Since linux-kvm was the only kernel that had this issue, I applied the patch to kvm after I rebased the latest changes from the parent and did a build test. * I also did a build test for linux:main just to make sure [Where problems could occur] * This change is pretty non-invasive, so nowhere ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux-kvm (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu Lunar) Importance: Undecided Assignee: Roxana Nicolescu (roxanan) Status: In Progress ** Affects: linux-kvm (Ubuntu Lunar) Importance: Undecided Assignee: Roxana Nicolescu (roxanan) Status: In Progress ** Tags: sru-20231002 ** Also affects: linux-kvm (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: linux-kvm (Ubuntu Lunar) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => Invalid ** Changed in: linux-kvm (Ubuntu Lunar) Status: New => Invalid ** Changed in: linux (Ubuntu Lunar) Status: New => In Progress ** Changed in: linux-kvm (Ubuntu Lunar) Status: Invalid => In Progress ** Changed in: linux (Ubuntu Lunar) Assignee: (unassigned) => Roxana Nicolescu (roxanan) ** Changed in: linux-kvm (Ubuntu Lunar) Assignee: (unassigned) => Roxana Nicolescu (roxanan) ** Tags added: sru-20231002 ** Description changed: SRU Justification: [Impact] - * Commit 88da4e8113110d5f4ebdd2f8cd0899e300cd1954 "pwm: Add a stub for devm_pwmchip_add()" was applied the second time during the latest upstream patchset (#LP: 2037005). `git am` did not detect the changes were applied, leading to the same function definition being duplicated. - This was not caught when the main kernel was built because this code is under CONFIG_PWM=n. The main kernel and pretty much every kernel apart from kvm, has CONFIG_PWM=y. - The problem was caught when lunar:linux-kvm was cranked and build failed for the current 2023.10.02 cycle + * Upstream commit 88da4e8113110d5f4ebdd2f8cd0899e300cd1954 "pwm: Add a stub for devm_pwmchip_add()", was applied the second time during the latest upstream patchset (#LP: 2037005) for cycle 2023.10.02. + * `git am` did not detect that the changes were applied, leading to the same function definition being duplicated. + * This was not caught when the main kernel was built because this code is under CONFIG_PWM=n. The main kernel and pretty much every kernel apart from linux-kvm, has CONFIG_PWM=y. + * The problem was caught when lunar:linux-kvm was cranked and build failed with the following error: + + ``` + In file included from /build/lunar/drivers/acpi/acpi_lpss.c:23: + /build/lunar/include/linux/pwm.h:486:19: error: redefinition of 'devm_pwmchip_add' + 486 | static inline int devm_pwmchip_add(struct device *dev, struct pwm_chip *chip) + | ^~~~ + /build/lunar/include/linux/pwm.h:481:19: note: previous definition of 'devm_pwmchip_add' with type 'int(struct device *, struct pwm_chip *)' + 481 | static inline int devm_pwmchip_add(struct device *dev, struct pwm_chip *chip) + | ^~~~ + + ``` [Fix] - * Revert the commit + * Revert the commit. [Test plan] * Since linux-kvm was the only kernel that had this issue, I applied the patch to kvm after I rebased the latest changes from the parent and did a build test. - * I
[Kernel-packages] [Bug 1852071] Re: [HP ZBook Studio G5, Ubuntu 18.04.3 LTS] Brightness function keys works as microphone mute function keys
Hi, I have the exact same problem with the latest BIOS : the brightness keys work after power reset but when booting to Windows ( where all keys work ) and back to Linux, the keys for brightness switch the microphone. -- 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/1852071 Title: [HP ZBook Studio G5, Ubuntu 18.04.3 LTS] Brightness function keys works as microphone mute function keys Status in OEM Priority Project: Triaged Status in linux package in Ubuntu: Confirmed Bug description: 1. Press fn+F3. Ubuntu shows "Internal microphone" turned off OSD pop-up. Should turn the brightness down. 2. Press fn+F3 again. Ubuntu shows "Internal microphone" turned on OSD pop-up. Should turn the brightness down. 1. Press fn+F4. Ubuntu shows "Internal microphone" turned off OSD pop-up. Should turn the brightness up. 2. Press fn+F4 again. Ubuntu shows "Internal microphone" turned on OSD pop-up. Should turn the brightness up. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21 Uname: Linux 5.0.0-32-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Nov 11 13:23:56 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:8428] InstallationDate: Installed on 2019-04-02 (223 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 138a:00ab Validity Sensors, Inc. Bus 001 Device 002: ID 05c8:0808 Cheng Uei Precision Industry Co., Ltd (Foxlink) Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP ZBook Studio G5 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-32-generic root=UUID=d12790df-696c-4d0c-aefa-b0e53712e2ce ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/15/2019 dmi.bios.vendor: HP dmi.bios.version: Q71 Ver. 01.08.00 dmi.board.name: 8427 dmi.board.vendor: HP dmi.board.version: KBC Version 16.3A.00 dmi.chassis.asset.tag: 5CD91018X5 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrQ71Ver.01.08.00:bd07/15/2019:svnHP:pnHPZBookStudioG5:pvr:rvnHP:rn8427:rvrKBCVersion16.3A.00:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN HP ZBook Studio dmi.product.name: HP ZBook Studio G5 dmi.product.sku: 2YN61AV dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1852071/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2022361] Re: Please enable Renesas RZ platform serial installer
Hi
I've tested the kernel changes to enable Renesas RZ platform serial
installer. This is working now.
Please note that this change affects the installation media to install
them on Renesas RZ platform.
Please include the changes into the source code and change the status to
'verification-done-jammy-linux-nvidia-6.2'.
Best Regards
John
--
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/2022361
Title:
Please enable Renesas RZ platform serial installer
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Focal:
Fix Released
Status in linux source package in Jammy:
Fix Released
Status in linux source package in Lunar:
Fix Released
Status in linux source package in Mantic:
Fix Released
Bug description:
[Impact]
The ubuntu installer does not work via serial ports for Renesas boards like
RZ/G2M-HiHope
(https://www.renesas.com/us/en/products/microcontrollers-microprocessors/rz-mpus/rzg2m-hihope-rzg2m-reference-board,
RZ/G2L, RZ/G2LC, RZ/G2UL SMARC Board
(https://renesas.info/wiki/RZ-G/RZ-G2L_SMARC).
The installation can be done using HDMI ports, but it would be nice to
support installation via serial port as well.
[Test case]
Try to install Ubuntu on a Renesas board.
[Fix]
Statically build SuperH SCI(F) serial port support (with
earlyconsole).
[Regression potential]
Statically building an additional driver in the kernel can make the
kernel image bigger, potentially causing boot issues in small (arm64 /
armhf) platforms.
[Original bug report]
Package: linux
Version: Ubuntu-6.2.0-21.21
Severity: normal
File: /mantic/debian.master/config/annotations
Dear Maintainer,
The ubuntu kernel is missing a few configuration options for Renesas
RZ/G2M MPU as below:
#Modify the following config from m to y.
CONFIG_SERIAL_SH_SCI=y
#add below configuration
CONFIG_SERIAL_SH_SCI_CONSOLE=y
CONFIG_SERIAL_SH_SCI_EARLYCON=y
The above changes are required in annotations file:
"/mantic/debian.master/config/annotations"
code location:
https://git.launchpad.net/~ubuntu-
kernel/ubuntu/+source/linux/+git/mantic/tree/debian.master/config/annotations#n11372
#Modify the following line (change 'm' to 'y')
CONFIG_SERIAL_SH_SCI policy<{'arm64': 'y', 'armhf': 'y'}>
#Add the following lines:
CONFIG_SERIAL_SH_SCI_CONSOLE policy<{'arm64': 'y', 'armhf': 'y'}>
CONFIG_SERIAL_SH_SCI_EARLYCON policy<{'arm64': 'y', 'armhf': 'y'}>
Could you please add those configuration options to the Ubuntu kernel?
Best Regards
John
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2022361/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2039549] [NEW] rtw89_8852be 0000:04:00.0: Direct firmware load for rtw89/rtw8852b_fw-1.bin failed with error -2
Public bug reported: [Impact] [Fix] [Test case] [Where problems could occur] ** Affects: linux-firmware (Ubuntu) Importance: Undecided Assignee: AceLan Kao (acelankao) Status: In Progress ** Affects: linux-firmware (Ubuntu Jammy) Importance: Undecided Assignee: AceLan Kao (acelankao) Status: In Progress ** Affects: linux-firmware (Ubuntu Lunar) Importance: Undecided Assignee: AceLan Kao (acelankao) Status: In Progress ** Affects: linux-firmware (Ubuntu Mantic) Importance: Undecided Assignee: AceLan Kao (acelankao) Status: In Progress ** Also affects: linux-firmware (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-firmware (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: linux-firmware (Ubuntu Lunar) Importance: Undecided Status: New ** Changed in: linux-firmware (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux-firmware (Ubuntu Lunar) Status: New => In Progress ** Changed in: linux-firmware (Ubuntu Mantic) Status: New => In Progress ** Changed in: linux-firmware (Ubuntu Jammy) Assignee: (unassigned) => AceLan Kao (acelankao) ** Changed in: linux-firmware (Ubuntu Lunar) Assignee: (unassigned) => AceLan Kao (acelankao) ** Changed in: linux-firmware (Ubuntu Mantic) Assignee: (unassigned) => AceLan Kao (acelankao) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2039549 Title: rtw89_8852be :04:00.0: Direct firmware load for rtw89/rtw8852b_fw-1.bin failed with error -2 Status in linux-firmware package in Ubuntu: In Progress Status in linux-firmware source package in Jammy: In Progress Status in linux-firmware source package in Lunar: In Progress Status in linux-firmware source package in Mantic: In Progress Bug description: [Impact] [Fix] [Test case] [Where problems could occur] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2039549/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2039561] [NEW] mlxbf_pmc: Replace sauce patches with upstream commits
Public bug reported: SRU Justification: [Impact] The mlxbf_pmc BlueField platform driver in the Jammy repo consists of some SAUCE patches. These need to be replaced. [Fix] The fix is to revert the four SAUCE patches, replacing them with upstream commits for the same functionality. 2 patches are from upstream linux, while the 3rd is from linux-next. [Test Case] * Boot BF2/BF3 platform, verify no new errors * Test sysfs interface exposed by driver for programming various counters and events. [Regression Potential] The upstream commits are not exactly the same as the SAUCE patches, so technically there is a chance of regression, but its been well-tested and the functionality is the same. [Other] n/a ** Affects: linux-bluefield (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/2039561 Title: mlxbf_pmc: Replace sauce patches with upstream commits Status in linux-bluefield package in Ubuntu: New Bug description: SRU Justification: [Impact] The mlxbf_pmc BlueField platform driver in the Jammy repo consists of some SAUCE patches. These need to be replaced. [Fix] The fix is to revert the four SAUCE patches, replacing them with upstream commits for the same functionality. 2 patches are from upstream linux, while the 3rd is from linux-next. [Test Case] * Boot BF2/BF3 platform, verify no new errors * Test sysfs interface exposed by driver for programming various counters and events. [Regression Potential] The upstream commits are not exactly the same as the SAUCE patches, so technically there is a chance of regression, but its been well-tested and the functionality is the same. [Other] n/a To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2039561/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2034477] Re: Keyboard and Touchpad Not Working in New Lenovo V15 Gen4 Laptop
Endre, i don't know what "these guys" are doing, but now we're have temporary fix for it. Tested but can be unstable. Mario, Boris and Hans keep working on it. https://bugzilla.kernel.org/attachment.cgi?id=305236&action=diff Working keyboard/trackpad and suspend with this kernel patch. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/2034477 Title: Keyboard and Touchpad Not Working in New Lenovo V15 Gen4 Laptop Status in linux-signed package in Ubuntu: Confirmed Status in linux-signed-hwe-6.2 package in Ubuntu: Confirmed Status in Fedora: New Bug description: Hello. Ubuntu 22.04.3 with (later upgraded to kernel 6.2.0-32-generic) was installed in rewly purchased LENOVO V15 GEN4 AMN (AMD Ryzen 5 7520u) laptop and it was noticed that keyboard, touchpad and microphone are not working. The keyboard and touchpad work fine in BIOS setup and till GRUB (command line). It was found that when external devices such as keyboard, mouse and microphone are connected through USB and 3.5 jack, respectively, these work just fine. To confirm these are not hardware problems, Microsoft Windows 11 (Home) was installed in another disk partition and observed all these working alright. Hence a bug is being reported to draw attention of the concerned team and I request them to refer this issue and do the needful at the earliest. Regards, Pradip Kumar Das ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-32-generic 6.2.0-32.32~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-32.32~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Sep 6 08:04:42 2023 InstallationDate: Installed on 2023-08-14 (22 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/2034477/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2039439] Re: linux-tools-common should depend on hwdata
** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Mantic) Importance: Undecided Status: Incomplete ** Also affects: linux (Ubuntu Lunar) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2039439 Title: linux-tools-common should depend on hwdata Status in linux package in Ubuntu: Incomplete Status in linux source package in Jammy: New Status in linux source package in Lunar: New Status in linux source package in Mantic: Incomplete Bug description: usbip wants hwdata so linux-tools-common should depend on it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2039439/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2039439] Re: linux-tools-common should depend on hwdata
** Description changed: - usbip wants hwdata so linux-tools-common should depend on it. + [Impact] + + usbip from linux-tools tries to access which is provided by the hwdata + package which is not installed by default. + + [Test Case] + + $ apt install linux-tools- + $ usbip + + [Fix] + + Make hwdata a dependency of linux-tools-common. + + [Regression Potential] + + A trivial package (hwdata) is installed as a dependency. Can't think of + any problems this could cause other than a theoretical package + installation failure. ** Description changed: [Impact] - usbip from linux-tools tries to access which is provided by the hwdata - package which is not installed by default. + usbip from linux-tools tries to access /usr/share/hwdata/usb.ids which + is provided by the hwdata package which is not installed by default. [Test Case] $ apt install linux-tools- $ usbip [Fix] Make hwdata a dependency of linux-tools-common. [Regression Potential] A trivial package (hwdata) is installed as a dependency. Can't think of any problems this could cause other than a theoretical package installation failure. ** Summary changed: - linux-tools-common should depend on hwdata + usbip: error: failed to open /usr/share/hwdata//usb.ids ** Description changed: [Impact] usbip from linux-tools tries to access /usr/share/hwdata/usb.ids which is provided by the hwdata package which is not installed by default. + $ usbip list -l + usbip: error: failed to open /usr/share/hwdata//usb.ids + - busid 1-1.1.1 (0424:7800) +unknown vendor : unknown product (0424:7800) + [Test Case] $ apt install linux-tools- - $ usbip + $ usbip list -l + $ [Fix] Make hwdata a dependency of linux-tools-common. [Regression Potential] A trivial package (hwdata) is installed as a dependency. Can't think of any problems this could cause other than a theoretical package installation failure. ** Description changed: [Impact] usbip from linux-tools tries to access /usr/share/hwdata/usb.ids which is provided by the hwdata package which is not installed by default. $ usbip list -l usbip: error: failed to open /usr/share/hwdata//usb.ids - - busid 1-1.1.1 (0424:7800) -unknown vendor : unknown product (0424:7800) + - busid 1-1.1.1 (0424:7800) + unknown vendor : unknown product (0424:7800) [Test Case] $ apt install linux-tools- $ usbip list -l - $ + - busid 1-1.1.1 (0424:7800) +Microchip Technology, Inc. (formerly SMSC) : unknown product (0424:7800) [Fix] Make hwdata a dependency of linux-tools-common. [Regression Potential] A trivial package (hwdata) is installed as a dependency. Can't think of any problems this could cause other than a theoretical package installation failure. -- 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/2039439 Title: usbip: error: failed to open /usr/share/hwdata//usb.ids Status in linux package in Ubuntu: Incomplete Status in linux source package in Jammy: New Status in linux source package in Lunar: New Status in linux source package in Mantic: Incomplete Bug description: [Impact] usbip from linux-tools tries to access /usr/share/hwdata/usb.ids which is provided by the hwdata package which is not installed by default. $ usbip list -l usbip: error: failed to open /usr/share/hwdata//usb.ids - busid 1-1.1.1 (0424:7800) unknown vendor : unknown product (0424:7800) [Test Case] $ apt install linux-tools- $ usbip list -l - busid 1-1.1.1 (0424:7800) Microchip Technology, Inc. (formerly SMSC) : unknown product (0424:7800) [Fix] Make hwdata a dependency of linux-tools-common. [Regression Potential] A trivial package (hwdata) is installed as a dependency. Can't think of any problems this could cause other than a theoretical package installation failure. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2039439/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2029899] Please test proposed package
Hello You-Sheng, or anyone else affected, Accepted linux-firmware into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/linux- firmware/20220329.git681281e4-0ubuntu3.22 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2029899 Title: Update firmware for hwe-6.2/oem-6.5 kernel migrations Status in linux-firmware package in Ubuntu: Invalid Status in linux-firmware source package in Jammy: Fix Committed Bug description: [SRU Justification] [Impact] When migrating to a new hwe kernel or introduced a oem kernel of a newer version, the firmware blobs might not match the expectation of the new kernel. [Fix] For linux-hwe-6.2/jammy: $ debian/scripts/list-lts-update-files \ launchpad/jammy \ launchpad/lunar \ linux-hwe-6.2/debian.hwe-6.2/abi/fwinfo | \ xargs git log --graph --oneline launchpad/jammy..launchpad/lunar -- * d02d58aae brcm: Add nvram for the Advantech MICA-071 tablet * f48fbe42c ath11k: IPQ5018 hw1.0: add to WLAN.HK.2.6.0.1-00861-QCAHKSWPL_SILICONZ-1 * 9dacec6da ath11k: IPQ5018 hw1.0: add board-2.bin * 3723b4800 brcm: add configuration files for CyberTan WC121 * e9b83572f amdgpu: updated aldebaran firmware for amd-5.4 * 9aa8db1cc rtlwifi: Add firmware v4.0 for RTL8188FU * 2c2be4215 nvidia: add GA102/GA103/GA104/GA106/GA107 signed firmware * 4ffcf980a brcm: rename Rock960 NVRAM to AP6356S and link devices to it For linux-oem-6.5/jammy: $ debian/scripts/list-lts-update-files \ launchpad/jammy \ launchpad/mantic \ linux-oem-6.5/debian.oem/abi/fwinfo | \ xargs git log --graph --oneline launchpad/jammy..launchpad/mantic -- * 41e615cf3 i915: Update ADLP DMC to v2.20 * 22fb12f2f amdgpu: add initial SMU 13.0.10 firmware * b3f512fb5 amdgpu: add initial SDMA 6.0.3 firmware * b1a7d7624 amdgpu: add initial PSP 13.0.10 firmware * d6d655ade amdgpu: add initial GC 11.0.3 firmware * b255f5b92 (tag: iwlwifi-fw-2023-06-29, korg-iwlwifi/for-upstream) iwlwifi: add new FWs from core80-39 release * 84d5550e9 amdgpu: update aldebaran firmware for amd.5.5 release * 08b854f02 rtlwifi: Add firmware v6.0 for RTL8192FU * 9f7502f1d rtw89: 8852b: update format-1 fw to v0.29.29.1 * 78a8782a9 (tag: iwlwifi-fw-2023-03-30) iwlwifi: add new FWs from core78-32 release * 7f490a9a4 Merge branch 'dmc-adlp_2.19-mtl_2.12' of git://anongit.freedesktop.org/drm/drm-firmware |\ | * 4ee236dbb i915: Update ADLP DMC to v2.19 * | 2c07f017f rtw89: 8852b: update format-1 fw to v0.29.29.0 * | b50cf9205 rtw89: 8852b: add format-1 fw v0.29.26.0 |/ * 6a55abe94 Merge https://github.com/pkshih/linux-firmware |\ | * 4cc3eda63 rtlwifi: Add firmware v16.0 for RTL8710BU aka RTL8188GU * | d02d58aae brcm: Add nvram for the Advantech MICA-071 tablet |/ * 3653d692b rtl_bt: Add firmware and config files for RTL8821CS * f48fbe42c ath11k: IPQ5018 hw1.0: add to WLAN.HK.2.6.0.1-00861-QCAHKSWPL_SILICONZ-1 * 9dacec6da ath11k: IPQ5018 hw1.0: add board-2.bin * a5046f435 (drm/dmc-adlp_2.18) i915: Add DMC v2.18 for ADLP * 3723b4800 brcm: add configuration files for CyberTan WC121 * e9b83572f amdgpu: updated aldebaran firmware for amd-5.4 * 9aa8db1cc rtlwifi: Add firmware v4.0 for RTL8188FU * 2c2be4215 nvidia: add GA102/GA103/GA104/GA106/GA107 signed firmware * 4ffcf980a brcm: rename Rock960 NVRAM to AP6356S and link devices to it [Test Case] Boot linux-oem-6.5, linux-hwe-6.2 with Jammy base system. [Where problems could occur] These firmware blobs are only referenced in the new hwe/oem kernels, and shall not have side effect. [Other Info] While there is no hwe/oem kernel planned for Lunar, so only Jammy is nominated for fix. To manage notifications about this bug go to: https://bugs.launc
[Kernel-packages] [Bug 2037716] Re: Core 22 is missing Realtek and TI drivers, that were previously in 20
Hey paul, this issue is about missing kernel modules, not about anything in the core22 snap ... Part of the kernel stuff is being handled already in https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/2024443 though ... ** Summary changed: - Core 22 is missing Realtek and TI drivers, that were previously in 20 + Core 22 kernel is missing Realtek and TI drivers, that were previously in 20 ** Also 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/2037716 Title: Core 22 kernel is missing Realtek and TI drivers, that were previously in 20 Status in Ubuntu: Invalid Status in linux-raspi package in Ubuntu: New Bug description: Please, do not exclude drivers previuosly included in IoT Core 20. IoT requires communication, mainly drivers. Add at least /realtek/rtl818x /realtek/rtl818x/rtl8187 /realtek/rtl8192cu /realtek/rtl8xxxu /realtek/rtlwifi /realtek/rtlwifi/rtl8188ee /realtek/rtlwifi/rtl8192c /realtek/rtlwifi/rtl8192cu and /ti/wl1251 /ti/wl12xx /ti/wl18xx /ti/wlcore To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2037716/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2039570] Re: Fullscreen in any Wayland/Xwayland window shows a blank screen
I add here lspci-vnvn just in case.
** Attachment added: "lspci-vnvn.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2039570/+attachment/5710299/+files/lspci-vnvn.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/2039570
Title:
Fullscreen in any Wayland/Xwayland window shows a blank screen
Status in linux package in Ubuntu:
New
Bug description:
When I go into "fullscreen" watching a video while browsing in Firefox
or when playing a game through Steam (fullscreen mode), the screen
goes black.
The workaround I have discovered to get back is to enter the gdm from
"Ctrl + alt + F1" and then return to the session you were in
(normally, "Ctrl + alt + F2).
MSI laptop.
CPU: AMD Ryzen 7 Series 4000
GPU: AMD Radeon RX 5600m
RAM: 16GB
NVM: 1TB.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-9-generic 6.5.0-9.9
ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
Uname: Linux 6.5.0-9-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: noctis 2095 F wireplumber
/dev/snd/controlC0: noctis 2095 F wireplumber
/dev/snd/seq:noctis 2090 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Oct 17 15:00:55 2023
InstallationDate: Installed on 2023-10-13 (4 days ago)
InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Release amd64 (20231011)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=es_ES.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcFB:
0 amdgpudrmfb
1 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-9-generic
root=UUID=fb325c2c-11c5-43e3-aceb-e921d5a7b323 ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-6.5.0-9-generic N/A
linux-backports-modules-6.5.0-9-generic N/A
linux-firmware 20230919.git3672ccab-0ubuntu2.1
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/26/2020
dmi.bios.release: 1.1
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: E17EKAMS.101
dmi.board.asset.tag: Default string
dmi.board.name: MS-17EK
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: REV:1.0
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 10
dmi.chassis.vendor: Micro-Star International Co., Ltd.
dmi.chassis.version: Default string
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrE17EKAMS.101:bd10/26/2020:br1.1:svnMicro-StarInternationalCo.,Ltd.:pnAlpha17A4DEK:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-17EK:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrDefaultstring:sku17EK.1:
dmi.product.family: Al
dmi.product.name: Alpha 17 A4DEK
dmi.product.sku: 17EK.1
dmi.product.version: REV:1.0
dmi.sys.vendor: Micro-Star International Co., Ltd.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2039570/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2039570] [NEW] Fullscreen in any Wayland/Xwayland window shows a blank screen
Public bug reported:
When I go into "fullscreen" watching a video while browsing in Firefox
or when playing a game through Steam (fullscreen mode), the screen goes
black.
The workaround I have discovered to get back is to enter the gdm from
"Ctrl + alt + F1" and then return to the session you were in (normally,
"Ctrl + alt + F2).
MSI laptop.
CPU: AMD Ryzen 7 Series 4000
GPU: AMD Radeon RX 5600m
RAM: 16GB
NVM: 1TB.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-9-generic 6.5.0-9.9
ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
Uname: Linux 6.5.0-9-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: noctis 2095 F wireplumber
/dev/snd/controlC0: noctis 2095 F wireplumber
/dev/snd/seq:noctis 2090 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Oct 17 15:00:55 2023
InstallationDate: Installed on 2023-10-13 (4 days ago)
InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Release amd64 (20231011)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=es_ES.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcFB:
0 amdgpudrmfb
1 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-9-generic
root=UUID=fb325c2c-11c5-43e3-aceb-e921d5a7b323 ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-6.5.0-9-generic N/A
linux-backports-modules-6.5.0-9-generic N/A
linux-firmware 20230919.git3672ccab-0ubuntu2.1
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/26/2020
dmi.bios.release: 1.1
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: E17EKAMS.101
dmi.board.asset.tag: Default string
dmi.board.name: MS-17EK
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: REV:1.0
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 10
dmi.chassis.vendor: Micro-Star International Co., Ltd.
dmi.chassis.version: Default string
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrE17EKAMS.101:bd10/26/2020:br1.1:svnMicro-StarInternationalCo.,Ltd.:pnAlpha17A4DEK:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-17EK:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrDefaultstring:sku17EK.1:
dmi.product.family: Al
dmi.product.name: Alpha 17 A4DEK
dmi.product.sku: 17EK.1
dmi.product.version: REV:1.0
dmi.sys.vendor: Micro-Star International Co., Ltd.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug mantic wayland-session
** Attachment added: "/proc/version_signature"
https://bugs.launchpad.net/bugs/2039570/+attachment/5710281/+files/version.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/2039570
Title:
Fullscreen in any Wayland/Xwayland window shows a blank screen
Status in linux package in Ubuntu:
New
Bug description:
When I go into "fullscreen" watching a video while browsing in Firefox
or when playing a game through Steam (fullscreen mode), the screen
goes black.
The workaround I have discovered to get back is to enter the gdm from
"Ctrl + alt + F1" and then return to the session you were in
(normally, "Ctrl + alt + F2).
MSI laptop.
CPU: AMD Ryzen 7 Series 4000
GPU: AMD Radeon RX 5600m
RAM: 16GB
NVM: 1TB.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-9-generic 6.5.0-9.9
ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
Uname: Linux 6.5.0-9-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: noctis 2095 F wireplumber
/dev/snd/controlC0: noctis 2095 F wireplumber
/dev/snd/seq:noctis 2090 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Oct 17 15:00:55 2023
InstallationDate: Installed on 2023-10-13 (4 days ago)
InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Release amd64 (20231011)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=es_ES.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcFB:
0 amdgpudrmfb
1 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-9-generic
root=UUID=fb325c2c-11c5-43e3-aceb-e921d5a7b323 ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-6.5.0-9-generic N/A
linux-backports-modules-6.5.0-9-generic N/A
linux-firmware 20230919.git3672ccab-0ubuntu2.1
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/26/2020
dmi.bios.release: 1.1
dmi.bios.vendor: American Meg
[Kernel-packages] [Bug 2039542] Re: Remove duplication of devm_pwmchip_add function definition
** Changed in: linux (Ubuntu Lunar) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/2039542 Title: Remove duplication of devm_pwmchip_add function definition Status in linux package in Ubuntu: Invalid Status in linux-kvm package in Ubuntu: New Status in linux source package in Lunar: Fix Committed Status in linux-kvm source package in Lunar: In Progress Bug description: SRU Justification: [Impact] * Upstream commit 88da4e8113110d5f4ebdd2f8cd0899e300cd1954 "pwm: Add a stub for devm_pwmchip_add()", was applied the second time during the latest upstream patchset (#LP: 2037005) for cycle 2023.10.02. * `git am` did not detect that the changes were applied, leading to the same function definition being duplicated. * This was not caught when the main kernel was built because this code is under CONFIG_PWM=n. The main kernel and pretty much every kernel apart from linux-kvm, has CONFIG_PWM=y. * The problem was caught when lunar:linux-kvm was cranked and build failed with the following error: ``` In file included from /build/lunar/drivers/acpi/acpi_lpss.c:23: /build/lunar/include/linux/pwm.h:486:19: error: redefinition of 'devm_pwmchip_add' 486 | static inline int devm_pwmchip_add(struct device *dev, struct pwm_chip *chip) | ^~~~ /build/lunar/include/linux/pwm.h:481:19: note: previous definition of 'devm_pwmchip_add' with type 'int(struct device *, struct pwm_chip *)' 481 | static inline int devm_pwmchip_add(struct device *dev, struct pwm_chip *chip) | ^~~~ ``` [Fix] * Revert the commit. * Because this affects only linux:kvm, it is necessary to apply this fix for lunar:linux-kvm for cycle 2023.10.02, but the main kernel can wait for the next cycle. [Test plan] * Since linux-kvm was the only kernel that had this issue, I applied the patch to kvm after I rebased the latest changes from the parent and did a build test. * I also did a build test for linux:main just to make sure [Where problems could occur] * This change is pretty non-invasive, so nowhere To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2039542/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2039382] Re: Kernel cannot detect the full memory
Hi Matthew, I appreciate your help. I try to repair this problem. First, I diagnostic from the BIOS but it doesn't work. Second, I try to unplug my wireless mouse then reboot the laptop more than five times. The memory allocation looks good. Maybe the bug comes from the bios. Do you have any suggestions to deal with this bug? Tank you very much. Ray -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2039382 Title: Kernel cannot detect the full memory Status in linux-signed-hwe-6.2 package in Ubuntu: New Bug description: Hi ubuntu, I use ubuntu22.04 in my laptop. When I open the laptop, sometimes ubuntu cannot detect all memory. My laptop has 16GB memory, sometimes ubuntu detect 2.5GB. I already use memtest86 test the health of the memory. It doesn’t show any error. I think this problem is from the OS. Please help me! Thank you very much Ray PS. uname -a: Linux ubuntu 6.2.0-34-generic #34~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Thu Sep 7 13:12:03 UTC 2 x86_64 x86_64 x86_64 GNU/Linux lshw -C memory: *-firmware description: BIOS vendor: Dell Inc. physical id: 0 version: 1.26.0 date: 06/13/2023 size: 64KiB capacity: 16MiB capabilities: pci pnp upgrade shadowing cdboot bootselect edd int13floppynec int13floppy1200 int13floppy720 int13floppy2880 int5printscreen int9keyboard int14serial int17printer acpi usb smartbattery biosbootspecification netboot uefi *-memory description: System Memory physical id: 41 slot: System board or motherboard size: 16GiB *-bank:0 description: DIMM [empty] physical id: 0 slot: ChannelA-DIMM0 *-bank:1 description: SODIMM DDR4 Synchronous Unbuffered (Unregistered) 2400 MHz (0.4 ns) product: HMA82GS6AFR8N-UH vendor: Hynix Semiconductor (Hyundai Electronics) physical id: 1 serial: 4247000D slot: DIMM B size: 16GiB width: 64 bits clock: 2400MHz (0.4ns) *-cache:0 description: L1 cache physical id: 45 slot: L1 Cache size: 256KiB capacity: 256KiB capabilities: synchronous internal write-back unified configuration: level=1 *-cache:1 description: L2 cache physical id: 46 slot: L2 Cache size: 1MiB capacity: 1MiB capabilities: synchronous internal write-back unified configuration: level=2 *-cache:2 description: L3 cache physical id: 47 slot: L3 Cache size: 6MiB capacity: 6MiB capabilities: synchronous internal write-back unified configuration: level=3 *-memory UNCLAIMED description: Memory controller product: Sunrise Point-LP PMC vendor: Intel Corporation physical id: 1f.2 bus info: pci@:00:1f.2 version: 21 width: 32 bits clock: 33MHz (30.3ns) configuration: latency=0 resources: memory:df42c000-df42 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-34-generic 6.2.0-34.34~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-34.34~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-34-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Oct 15 17:53:09 2023 InstallationDate: Installed on 2023-10-08 (7 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.2/+bug/2039382/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2039570] 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/2039570
Title:
Fullscreen in any Wayland/Xwayland window shows a blank screen
Status in linux package in Ubuntu:
Confirmed
Bug description:
When I go into "fullscreen" watching a video while browsing in Firefox
or when playing a game through Steam (fullscreen mode), the screen
goes black.
The workaround I have discovered to get back is to enter the gdm from
"Ctrl + alt + F1" and then return to the session you were in
(normally, "Ctrl + alt + F2).
MSI laptop.
CPU: AMD Ryzen 7 Series 4000
GPU: AMD Radeon RX 5600m
RAM: 16GB
NVM: 1TB.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-9-generic 6.5.0-9.9
ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
Uname: Linux 6.5.0-9-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: noctis 2095 F wireplumber
/dev/snd/controlC0: noctis 2095 F wireplumber
/dev/snd/seq:noctis 2090 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Oct 17 15:00:55 2023
InstallationDate: Installed on 2023-10-13 (4 days ago)
InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Release amd64 (20231011)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=es_ES.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcFB:
0 amdgpudrmfb
1 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-9-generic
root=UUID=fb325c2c-11c5-43e3-aceb-e921d5a7b323 ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-6.5.0-9-generic N/A
linux-backports-modules-6.5.0-9-generic N/A
linux-firmware 20230919.git3672ccab-0ubuntu2.1
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/26/2020
dmi.bios.release: 1.1
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: E17EKAMS.101
dmi.board.asset.tag: Default string
dmi.board.name: MS-17EK
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: REV:1.0
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 10
dmi.chassis.vendor: Micro-Star International Co., Ltd.
dmi.chassis.version: Default string
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrE17EKAMS.101:bd10/26/2020:br1.1:svnMicro-StarInternationalCo.,Ltd.:pnAlpha17A4DEK:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-17EK:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrDefaultstring:sku17EK.1:
dmi.product.family: Al
dmi.product.name: Alpha 17 A4DEK
dmi.product.sku: 17EK.1
dmi.product.version: REV:1.0
dmi.sys.vendor: Micro-Star International Co., Ltd.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2039570/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2039542] Re: Remove duplication of devm_pwmchip_add function definition
** Changed in: linux-kvm (Ubuntu Lunar) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/2039542 Title: Remove duplication of devm_pwmchip_add function definition Status in linux package in Ubuntu: Invalid Status in linux-kvm package in Ubuntu: New Status in linux source package in Lunar: Fix Committed Status in linux-kvm source package in Lunar: Fix Committed Bug description: SRU Justification: [Impact] * Upstream commit 88da4e8113110d5f4ebdd2f8cd0899e300cd1954 "pwm: Add a stub for devm_pwmchip_add()", was applied the second time during the latest upstream patchset (#LP: 2037005) for cycle 2023.10.02. * `git am` did not detect that the changes were applied, leading to the same function definition being duplicated. * This was not caught when the main kernel was built because this code is under CONFIG_PWM=n. The main kernel and pretty much every kernel apart from linux-kvm, has CONFIG_PWM=y. * The problem was caught when lunar:linux-kvm was cranked and build failed with the following error: ``` In file included from /build/lunar/drivers/acpi/acpi_lpss.c:23: /build/lunar/include/linux/pwm.h:486:19: error: redefinition of 'devm_pwmchip_add' 486 | static inline int devm_pwmchip_add(struct device *dev, struct pwm_chip *chip) | ^~~~ /build/lunar/include/linux/pwm.h:481:19: note: previous definition of 'devm_pwmchip_add' with type 'int(struct device *, struct pwm_chip *)' 481 | static inline int devm_pwmchip_add(struct device *dev, struct pwm_chip *chip) | ^~~~ ``` [Fix] * Revert the commit. * Because this affects only linux:kvm, it is necessary to apply this fix for lunar:linux-kvm for cycle 2023.10.02, but the main kernel can wait for the next cycle. [Test plan] * Since linux-kvm was the only kernel that had this issue, I applied the patch to kvm after I rebased the latest changes from the parent and did a build test. * I also did a build test for linux:main just to make sure [Where problems could occur] * This change is pretty non-invasive, so nowhere To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2039542/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2039280] Re: Support IP address protocol
Thank you! I confirmed that the added distro-patches match the upstream
patches. The feature looks useful, but it's not very common to backport
new features as part of an SRU... So I'll leave that decision to the SRU
team.
In either way, this should probably first be fixed in the current
"devel" series, i.e. by merging iproute2 v6.4+ from Debian unstable.
Once that is accomplished, we can consider this patch for SRU. Would you
be interested in working on that merge?
Nitpick: When aiming for SRU, you should consider updating the SRU
template in the bug description to the latest version (although, the one
you used might also be accepted as-is) and also change the version
number according to
https://wiki.ubuntu.com/SecurityTeam/UpdatePreparation#Update_the_packaging,
e.g.: 6.1.0-1ubuntu2.1
https://wiki.ubuntu.com/StableReleaseUpdates#SRU_Bug_Template
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to iproute2 in Ubuntu.
Matching subscriptions: iproute2
https://bugs.launchpad.net/bugs/2039280
Title:
Support IP address protocol
Status in iproute2 package in Ubuntu:
Confirmed
Status in iproute2 source package in Mantic:
Confirmed
Bug description:
[Impact]
IPv4 and IPv6 addresses can be assigned a protocol value that indicates the
provenance of the IP address. The attribute is modeled after ip route
protocols, and essentially allows the administrator or userspace stack to
tag addresses in some way that makes sense to the actor in question.
Support for this feature was merged with commit 47f0bd503210 ("net: Add new
protocol attribute to IP addresses"), for kernel 5.18.
In this patch, add support for setting the protocol attribute at IP address
addition, replacement, and listing requests.
[Fix]
Apply the attached patch
[How to test]
$ cat << EOF > test.sh
#!/bin/sh
addr=192.0.2.1/28
addr2=${addr%/*}2/${addr#*/}
ifr=test-dummy123
sudo ip link add name "$ifr" type dummy
sudo ip link set "$ifr" up
sudo ip address add dev "$ifr" "$addr2" proto 0x99
sudo ip link del "$ifr"
EOF
$chmod +x test.sh
$test.sh
$ echo $?
0
if you get an error instead, like:
Error: either "local" is duplicate, or "proto" is a garbage.
your iproute2 is not patched.
Alternativerly, you could download Linux v6.5 source code and run:
$ cd linux
$ sudo ./tools/testing/selftests/net/rtnetlink.sh -t kci_test_address_proto
[Regression potential]
Two clean upstream cherry-picks, regression potential should be low.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/2039280/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2038249] Re: The dump file parsing issue arises from structural changes in Linux kernel 6.2
Marking Jammy as affected due to the 6.2+ HWE kernel from Lunar (and later). ** Also affects: crash (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: crash (Ubuntu Jammy) Status: New => In Progress ** Changed in: crash (Ubuntu Jammy) Assignee: (unassigned) => Chengen Du (chengendu) ** Changed in: crash (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: crash (Ubuntu Lunar) Importance: Undecided => Medium ** Changed in: crash (Ubuntu Mantic) Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to crash in Ubuntu. https://bugs.launchpad.net/bugs/2038249 Title: The dump file parsing issue arises from structural changes in Linux kernel 6.2 Status in crash package in Ubuntu: In Progress Status in crash source package in Jammy: In Progress Status in crash source package in Lunar: In Progress Status in crash source package in Mantic: In Progress Bug description: [Impact] Linux kernel 6.2 includes patches with structural changes that may render the crash utility unable to parse the dump file. == d122019bf061 mm: Split slab into its own type 401fb12c68c2 mm: Differentiate struct slab fields by sl*b implementations 07f910f9b729 mm: Remove slab from struct page 0d9b1ffefabe arm64: mm: make vabits_actual a build time constant if possible e36ce448a08d mm/slab: use kmalloc_node() for off slab freelist_idx_t array allocation 130d4df57390 mm/sl[au]b: rearrange struct slab fields to allow larger rcu_head ac3b43283923 module: replace module_layout with module_memory b69f0aeb0689 pid: Replace struct pid 1-element array with flex-array == [Fix] It is advisable to adopt commits that address the structural changes issue. == [v8.0.0] 14f8c460473c memory: Handle struct slab changes on Linux 5.17-rc1 and later 5f390ed811b0 Fix for "kmem -s|-S" and "bt -F[F]" on Linux 5.17-rc1 b89f9ccf511a Fix for "kmem -s|-S" on Linux 5.17+ with CONFIG_SLAB [v8.0.1] f02c8e87fccb arm64: use TCR_EL1_T1SZ to get the correct info if vabits_actual is missing [v8.0.2] d83df2fb66cd SLUB: Fix for offset change of struct slab members on Linux 6.2-rc1 df1f0cba729f x86_64: Fix for move of per-cpu variables into struct pcpu_hot 120d6e89fc14 SLAB: Fix for "kmem -s|-S" options on Linux 6.1 and later ac96e17d1de5 SLAB: Fix for "kmem -s|-S" options on Linux 6.2-rc1 and later 7750e61fdb2a Support module memory layout change on Linux 6.4 88580068b7dd Fix failure of gathering task table on Linux 6.5-rc1 and later 4ee56105881d Fix compilation error due to new strlcpy function that glibc added == [Test Plan] 1. Install the required packages and then proceed to reboot the machine. # sudo apt install crash linux-crashdump -y # reboot 2. To check the status of kdump, use the `kdump-config show` command. # kdump-config show DUMP_MODE:kdump USE_KDUMP:1 KDUMP_COREDIR:/var/crash crashkernel addr: 0x6400 /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinuz-6.2.0-33-generic kdump initrd: /var/lib/kdump/initrd.img: symbolic link to /var/lib/kdump/initrd.img-6.2.0-33-generic current state:ready to kdump kexec command: /sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinuz-6.2.0-33-generic root=UUID=3e72f5d5-870b-4b8e-9a0d-8ba920391379 ro console=tty1 console=ttyS0 reset_devices systemd.unit=kdump-tools-dump.service nr_cpus=1 irqpoll usbcore.nousb" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz 3. To trigger a crash dump forcefully, execute the `echo c | sudo tee /proc/sysrq-trigger` command. 4. Download the kernel .ddeb file, which will be used for analyzing the dump file. # sudo -i # cd /var/crash # pull-lp-ddebs linux-image-unsigned-$(uname -r) # dpkg-deb -x linux-image-unsigned-$(uname -r)-*.ddeb dbgsym-$(uname -r) 5. Utilize the "crash" utility to parse and analyze the dump file. crash 8.0.0 Copyright (C) 2002-2021 Red Hat, Inc. Copyright (C) 2004, 2005, 2006, 2010 IBM Corporation Copyright (C) 1999-2006 Hewlett-Packard Co Copyright (C) 2005, 2006, 2011, 2012 Fujitsu Limited Copyright (C) 2006, 2007 VA Linux Systems Japan K.K. Copyright (C) 2005, 2011, 2020-2021 NEC Corporation Copyright (C) 1999, 2002, 2007 Silicon Graphics, Inc. Copyright (C) 1999, 2000, 2001, 2002 Mission Critical Linux, Inc. Copyright (C) 2015, 2021 VMware, Inc. This program is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Enter "help copying" to see the conditions. This program has absolutely no warranty. Enter "help warranty" for details. WARNING: VA_BITS: calculated: 46 vmcoreinfo: 48 GNU gdb (GDB) 10.2 Copyright (C) 2021 Free Software Foundation, Inc. License GPLv3+: GNU G
[Kernel-packages] [Bug 1876687] Re: func_traceonoff_triggers.tc from ubuntu_kselftests_ftrace flaky (Tracing file is still changing)
Seen on f/aws-fips with version 5.4.0-1112.121+fips1 during cycle s2023.09.04 on the m5a.large instance. -- 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/1876687 Title: func_traceonoff_triggers.tc from ubuntu_kselftests_ftrace flaky (Tracing file is still changing) Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Bug description: Issue found on Focal 5.4.0-29.33 with node amaura (passed on rizzo, rizzo failed with other failures) Running './ftracetest -vvv test.d/ftrace/func_traceonoff_triggers.tc' [stdout] === Ftrace unit tests === [stderr] + initialize_ftrace [stderr] + disable_tracing [stderr] + echo 0 [stderr] + reset_tracer [stderr] + echo nop [stderr] + reset_trigger [stderr] + [ -d events/synthetic ] (long output skipped) [stderr] + read line (long output skipped) [stderr] + read line (long output skipped) [stderr] + reset_events_filter [stderr] + read line (long output skipped) [stderr] + reset_ftrace_filter [stderr] + [ ! -f set_ftrace_filter ] [stderr] + echo [stderr] + grep -v ^# set_ftrace_filter [stderr] + read t [stderr] + disable_events [stderr] + echo 0 [stderr] + [ -f set_event_pid ] [stderr] + echo [stderr] + [ -f set_ftrace_pid ] [stdout] [1] ftrace - test for function traceon/off triggers [stderr] + echo [stderr] + [ -f set_ftrace_notrace ] [stderr] + echo [stderr] + [ -f set_graph_function ] [stderr] + tee set_graph_function set_graph_notrace [stderr] + echo [stderr] + [ -f stack_trace_filter ] [stderr] + echo [stderr] + [ -f kprobe_events ] [stderr] + echo [stderr] + [ -f uprobe_events ] [stderr] + echo [stderr] + [ -f synthetic_events ] [stderr] + echo [stderr] + [ -f snapshot ] [stderr] + echo 0 [stderr] + clear_trace [stdout] Testing function probes with enabling disabling tracing: [stdout] ** DISABLE TRACING [stderr] + echo [stderr] + enable_tracing [stderr] + echo 1 [stderr] + . /home/ubuntu/autotest/client/tmp/ubuntu_kselftests_ftrace/src/linux/tools/testing/selftests/ftrace/test.d/ftrace/func_traceonoff_triggers.tc [stderr] + [ ! -f set_ftrace_filter ] [stderr] + SLEEP_TIME=.1 [stderr] + echo Testing function probes with enabling disabling tracing: [stderr] + echo ** DISABLE TRACING [stderr] + disable_tracing [stderr] + echo 0 [stderr] + clear_trace [stderr] + echo [stderr] + cnt_trace [stderr] + + grep -v ^# trace [stderr] wc -l [stdout] ** ENABLE EVENTS [stderr] + cnt=0 [stderr] + [ 0 -ne 0 ] [stderr] + echo ** ENABLE EVENTS [stderr] + echo 1 [stdout] ** ENABLE TRACING [stderr] + echo ** ENABLE TRACING [stderr] + enable_tracing [stderr] + echo 1 [stderr] + cnt_trace [stderr] + wc -l [stderr] + grep -v ^# trace [stderr] + cnt=4077 [stderr] + [ 4077 -eq 0 ] [stderr] + func=schedule [stderr] + available_file=available_filter_functions [stderr] + [ -d ../../instances -a -f ../../available_filter_functions ] [stderr] + grep ^\.schedule$ available_filter_functions [stderr] + wc -l [stdout] ** SET TRACEOFF [stderr] + x=0 [stderr] + [ 0 -eq 1 ] [stderr] + echo ** SET TRACEOFF [stderr] + echo schedule:traceoff [stderr] + [ -d ../../instances ] [stderr] + + wc -l [stderr] grep schedule set_ftrace_filter [stderr] + cnt=1 [stderr] + [ 1 -ne 1 ] [stderr] + cnt_trace [stderr] + wc -l [stderr] + grep -v ^# trace [stderr] + cnt=21814 [stderr] + sleep .1 [stderr] + cnt_trace [stderr] + grep+ wc -v ^# trace [stderr] -l [stderr] + cnt2=21814 [stderr] + [ 21814 -ne 21814 ] [stderr] + cat tracing_on [stderr] + on=0 [stderr] + [ 0 != 0 ] [stderr] + md5sum trace [stderr] + csum1=c6e4ee60fb108d69d9bbfe7e1db1063e trace [stderr] + sleep .1 [stderr] + md5sum trace [stderr] + csum2=e4031c9f7b2a802822472087feacd82f trace [stderr] + [ c6e4ee60fb108d69d9bbfe7e1db1063e trace != e4031c9f7b2a802822472087feacd82f trace ] [stderr] + fail Tracing file is still changing [stderr] + echo Tracing file is still changing [stderr] + exit_fail [stderr] + exit 1 [stdout] Tracing file is still changing [stdout] [FAIL] [stderr] + initialize_ftrace [stderr] + disable_tracing [stderr] + echo 0 [stderr] + reset_tracer [stderr] + echo nop [stderr] + reset_trigger [stderr] + [ -d events/synthetic ] (long output skipped) [stderr] + read line (long output skipped) [stderr] + read line (long output skipped) [stderr] + reset_events_filter [stderr] + read line (long output skipped) [stderr] + reset_ftrace_filter [stderr] + [ ! -f set_ftrace_filter ] [stderr] + echo [stderr] + read t [stderr] + grep -v ^# set_ftrace_filter [stderr] + disable_events [stderr] + echo 0 [stderr] + [ -f set_event_pid ] [stderr] + echo [stderr] + [ -f set_ftrace_pid ] [stderr] + echo [stderr] + [ -f set_ftrace_no
[Kernel-packages] [Bug 2039561] Re: mlxbf_pmc: Replace sauce patches with upstream commits
** Also affects: linux-bluefield (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux-bluefield (Ubuntu) Status: New => Invalid -- 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/2039561 Title: mlxbf_pmc: Replace sauce patches with upstream commits Status in linux-bluefield package in Ubuntu: Invalid Status in linux-bluefield source package in Jammy: New Bug description: SRU Justification: [Impact] The mlxbf_pmc BlueField platform driver in the Jammy repo consists of some SAUCE patches. These need to be replaced. [Fix] The fix is to revert the four SAUCE patches, replacing them with upstream commits for the same functionality. 2 patches are from upstream linux, while the 3rd is from linux-next. [Test Case] * Boot BF2/BF3 platform, verify no new errors * Test sysfs interface exposed by driver for programming various counters and events. [Regression Potential] The upstream commits are not exactly the same as the SAUCE patches, so technically there is a chance of regression, but its been well-tested and the functionality is the same. [Other] n/a To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2039561/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2039437] Re: linux-tools- should provide linux-tools
** Also affects: linux-meta-raspi (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-meta-raspi (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: linux-meta-raspi (Ubuntu Lunar) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-raspi in Ubuntu. https://bugs.launchpad.net/bugs/2039437 Title: linux-tools- should provide linux-tools Status in linux-meta-raspi package in Ubuntu: New Status in linux-meta-raspi source package in Jammy: New Status in linux-meta-raspi source package in Lunar: New Status in linux-meta-raspi source package in Mantic: New Bug description: Missing 'Provides: linux-tools', results in: $ sudo apt install linux-tools Reading package lists... Done Building dependency tree... Done Reading state information... Done Package linux-tools is a virtual package provided by: linux-tools-virtual-hwe-22.04-edge 6.5.0.9.11 linux-tools-virtual-hwe-22.04 6.5.0.9.11 linux-tools-virtual 6.5.0.9.11 linux-tools-generic-hwe-22.04-edge 6.5.0.9.11 linux-tools-generic-hwe-22.04 6.5.0.9.11 linux-tools-generic 6.5.0.9.11 You should explicitly select one to install. E: Package 'linux-tools' has no installation candidate The above should list linux-tools-raspi. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-raspi/+bug/2039437/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2037716] Re: Core 22 kernel is missing Realtek and TI drivers, that were previously in 20
*** This bug is a duplicate of bug 2037938 *** https://bugs.launchpad.net/bugs/2037938 ** This bug has been marked a duplicate of bug 2037938 Include USB drivers in linux-modules -- 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/2037716 Title: Core 22 kernel is missing Realtek and TI drivers, that were previously in 20 Status in Ubuntu: Invalid Status in linux-raspi package in Ubuntu: New Bug description: Please, do not exclude drivers previuosly included in IoT Core 20. IoT requires communication, mainly drivers. Add at least /realtek/rtl818x /realtek/rtl818x/rtl8187 /realtek/rtl8192cu /realtek/rtl8xxxu /realtek/rtlwifi /realtek/rtlwifi/rtl8188ee /realtek/rtlwifi/rtl8192c /realtek/rtlwifi/rtl8192cu and /ti/wl1251 /ti/wl12xx /ti/wl18xx /ti/wlcore To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2037716/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2039575] [NEW] [UBUNTU 22.04] SMC stats: Wrong bucket calculation for payload of exactly 4096 bytes.
You have been subscribed to a public bug:
Bug description by Nils H.:
Overview:
The following line in the SMC stats code (net/smc/smc_stats.h) caught my
attention when using a payload of exactly 4096 bytes:
#define SMC_STAT_PAYLOAD_SUB(_smc_stats, _tech, key, _len, _rc) \
do { \
typeof(_smc_stats) stats = (_smc_stats); \
typeof(_tech) t = (_tech); \
typeof(_len) l = (_len); \
int _pos = fls64((l) >> 13); \
typeof(_rc) r = (_rc); \
int m = SMC_BUF_MAX - 1; \
this_cpu_inc((*stats).smc[t].key ## _cnt); \
if (r <= 0) \
break; \
_pos = (_pos < m) ? ((l == 1 << (_pos + 12)) ? _pos - 1 : _pos) : m; \
<---
this_cpu_inc((*stats).smc[t].key ## _pd.buf[_pos]); \
this_cpu_add((*stats).smc[t].key ## _bytes, r); \
} \
while (0)
With l = 4096, _pos evaluates to -1.
Checking with the following uperf profile:
# cat rr1c-4kx4k---1.xml
smcd stats output:
# smcd -d stats reset
SMC-D Connections Summary
Total connections handled 2
SMC connections 2 (client 2, server 0)
v1 0
v2 2
Handshake errors 0 (client 0, server 0)
Avg requests per SMC conn14.0
TCP fallback 0 (client 0, server 0)
RX Stats
Data transmitted (Bytes) 5796 (5.796K)
Total requests9
Buffer full 0 (0.00%)
Buffer downgrades 0
Buffer reuses 0
8KB16KB32KB64KB 128KB 256KB 512KB >512KB
Bufs0 0 0 2 0 0 0 1
Reqs8 0 0 0 0 0 0 0
TX Stats
Data transmitted (Bytes) 9960 (9.960K)
Total requests 19
Buffer full 0 (0.00%)
Buffer full (remote) 0 (0.00%)
Buffer too small 0 (0.00%)
Buffer too small (remote) 0 (0.00%)
Buffer downgrades 0
Buffer reuses 0
8KB16KB32KB64KB 128KB 256KB 512KB >512KB
Bufs0 2 0 0 0 0 0 0
Reqs 18 0 0 0 0 0 0 1
Extras
Special socket calls 0
cork0
nodelay 0
sendpage0
splice 0
urgent data 0
Instead of including the payload in the wrong >512KB buckets, output should be
to have 19 reqs in the 8KB buckets for TX stats and 9 reqs in the 8KB bucket
for RX stats.
Repro:
0. Install uperf.
1. Reset SMC-D stats on client and server.
2. Start uperf at server side: "uperf -vs".
3. Update profile with remote IP (server IP) and start uperf at client: "uperf
-vai 5 -m rr1c-4kx4k---1.xml" (uperf profile, see above)
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: Skipper Bug Screeners (skipper-screen-team)
Status: New
** Tags: architecture-s39064 bugnameltc-203868 severity-medium
targetmilestone-inin---
--
[UBUNTU 22.04] SMC stats: Wrong bucket calculation for payload of exactly 4096
bytes.
https://bugs.launchpad.net/bugs/2039575
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 2038981] Re: No external output when hotplugging to a DP monitor after the monitor went to sleep for AMD 6300 GPU
This bug is awaiting verification that the linux-oem-6.1/6.1.0-1025.25 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-jammy-linux-oem-6.1' to 'verification-done- jammy-linux-oem-6.1'. If the problem still exists, change the tag 'verification-needed-jammy-linux-oem-6.1' to 'verification-failed-jammy- linux-oem-6.1'. 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: kernel-spammed-jammy-linux-oem-6.1-v2 verification-needed-jammy-linux-oem-6.1 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2038981 Title: No external output when hotplugging to a DP monitor after the monitor went to sleep for AMD 6300 GPU Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.1 source package in Jammy: In Progress Status in linux-oem-6.5 source package in Jammy: Fix Committed Status in linux source package in Mantic: In Progress Status in linux-oem-6.1 source package in Mantic: Invalid Status in linux-oem-6.5 source package in Mantic: Invalid Bug description: [Impact] With ADM 6300 GPU, there is no external output when plug in a DP monitor after the monitor went to sleep [Fix] Mario provides a patch to fix the issue https://patchwork.kernel.org/project/linux-usb/list/?series=790399 And also below commit is required 134b8c5d8674 drm/amd: Fix detection of _PR3 on the PCIe root port [Test case] 1. Boot up the system with AMD 6300 GPU and plug DP monitor on the card 2. Unplug the DP cable and wait the monitor sleeps 3. Plug in the DP cable again and it should wake up the monitor correctly and output the screen to the monitor [Where problems could occur] The PR3 patch only affects AMD dGPU and should fix AMD BOCO detection logic, and UCSI patch try to set the correct power supply scope which should do no harm to the existing systems. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2038981/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2038263] Re: Add SoF topology support on Intel RaptorLake DELL SKU 0C11
This bug is awaiting verification that the linux-oem-6.1/6.1.0-1025.25 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-jammy-linux-oem-6.1' to 'verification-done- jammy-linux-oem-6.1'. If the problem still exists, change the tag 'verification-needed-jammy-linux-oem-6.1' to 'verification-failed-jammy- linux-oem-6.1'. 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: kernel-spammed-jammy-linux-oem-6.1-v2 verification-needed-jammy-linux-oem-6.1 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2038263 Title: Add SoF topology support on Intel RaptorLake DELL SKU 0C11 Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.1 package in Ubuntu: New Status in linux-oem-6.5 package in Ubuntu: New Status in linux source package in Jammy: New Status in linux-oem-6.1 source package in Jammy: Fix Committed Status in linux-oem-6.5 source package in Jammy: Fix Committed Status in linux source package in Mantic: In Progress Status in linux-oem-6.1 source package in Mantic: New Status in linux-oem-6.5 source package in Mantic: New Bug description: SRU Jusitification for firmware-sof [Impact] To support audio functions on RPL Dell SKU 0C11, it requires the topology file from sof-tplg-v2.2.7 [Fix] Pull the sof-rpl-rt711-l0-rt1316-l12.tplg from https://github.com/thesofproject/sof-bin/releases/tag/v2023.09 [Test Case] Install the fixes on the target platform(RPL Dell SKU 0C11) and verify the audio function. 1. Install the firmware-sof on platform(RPL) Dell SKU 0C11 2. Make sure the audio output/input devices are not dummy in audio settings. [Where problems could occur] New firmware is only for the RPL platforms which requires the specific topology file. [Misc] https://github.com/thesofproject/sof-bin/releases/tag/v2023.09 [Impact] Audio play/capture are not functional on specific Dell machines of Intel RPL platforms [Fix] Backport the fix from Intel in https://github.com/thesofproject/linux [Test Case] 1. Power on the machine and open the audio settings 2. Verify it's not `Dummy` shown on the Audio output/input option [Where problems could occur] Only affect specific Intel RPL platforms. The risk of regression is low. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2038263/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2036515] Re: Fix system boot hang caused by devlink
This bug is awaiting verification that the linux-oem-6.1/6.1.0-1025.25
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-jammy-linux-oem-6.1' to 'verification-done-
jammy-linux-oem-6.1'. If the problem still exists, change the tag
'verification-needed-jammy-linux-oem-6.1' to 'verification-failed-jammy-
linux-oem-6.1'.
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: kernel-spammed-jammy-linux-oem-6.1-v2
verification-needed-jammy-linux-oem-6.1
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.1 in Ubuntu.
https://bugs.launchpad.net/bugs/2036515
Title:
Fix system boot hang caused by devlink
Status in HWE Next:
New
Status in linux package in Ubuntu:
Fix Released
Status in linux-oem-6.1 package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Won't Fix
Status in linux-oem-6.1 source package in Jammy:
Fix Committed
Status in linux source package in Lunar:
Confirmed
Status in linux-oem-6.1 source package in Lunar:
Invalid
Bug description:
[Impact]
System stuck at boot when Intel 7560 is in use, because devlink
is waiting for reference to be released.
[Fix]
Commit "devlink: remove the registration guarantee of references"
weakens the refcount requirement for devlink {,un}registering,
[Test]
System reboots over 2000 times when the fix is applied.
[Where problems could occur]
devlink is part of net core API, so it has many users, therefore all of
devlink users can be affected by this fix. However, all the devlink
users can be affected by the same issue (i.e. waiting for reference to
decrease to 0), hence this is still a desirable fix.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2036515/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2039575] [NEW] [UBUNTU 22.04] SMC stats: Wrong bucket calculation for payload of exactly 4096 bytes.
Public bug reported:
Bug description by Nils H.:
Overview:
The following line in the SMC stats code (net/smc/smc_stats.h) caught my
attention when using a payload of exactly 4096 bytes:
#define SMC_STAT_PAYLOAD_SUB(_smc_stats, _tech, key, _len, _rc) \
do { \
typeof(_smc_stats) stats = (_smc_stats); \
typeof(_tech) t = (_tech); \
typeof(_len) l = (_len); \
int _pos = fls64((l) >> 13); \
typeof(_rc) r = (_rc); \
int m = SMC_BUF_MAX - 1; \
this_cpu_inc((*stats).smc[t].key ## _cnt); \
if (r <= 0) \
break; \
_pos = (_pos < m) ? ((l == 1 << (_pos + 12)) ? _pos - 1 : _pos) : m; \
<---
this_cpu_inc((*stats).smc[t].key ## _pd.buf[_pos]); \
this_cpu_add((*stats).smc[t].key ## _bytes, r); \
} \
while (0)
With l = 4096, _pos evaluates to -1.
Checking with the following uperf profile:
# cat rr1c-4kx4k---1.xml
smcd stats output:
# smcd -d stats reset
SMC-D Connections Summary
Total connections handled 2
SMC connections 2 (client 2, server 0)
v1 0
v2 2
Handshake errors 0 (client 0, server 0)
Avg requests per SMC conn14.0
TCP fallback 0 (client 0, server 0)
RX Stats
Data transmitted (Bytes) 5796 (5.796K)
Total requests9
Buffer full 0 (0.00%)
Buffer downgrades 0
Buffer reuses 0
8KB16KB32KB64KB 128KB 256KB 512KB >512KB
Bufs0 0 0 2 0 0 0 1
Reqs8 0 0 0 0 0 0 0
TX Stats
Data transmitted (Bytes) 9960 (9.960K)
Total requests 19
Buffer full 0 (0.00%)
Buffer full (remote) 0 (0.00%)
Buffer too small 0 (0.00%)
Buffer too small (remote) 0 (0.00%)
Buffer downgrades 0
Buffer reuses 0
8KB16KB32KB64KB 128KB 256KB 512KB >512KB
Bufs0 2 0 0 0 0 0 0
Reqs 18 0 0 0 0 0 0 1
Extras
Special socket calls 0
cork0
nodelay 0
sendpage0
splice 0
urgent data 0
Instead of including the payload in the wrong >512KB buckets, output should be
to have 19 reqs in the 8KB buckets for TX stats and 9 reqs in the 8KB bucket
for RX stats.
Repro:
0. Install uperf.
1. Reset SMC-D stats on client and server.
2. Start uperf at server side: "uperf -vs".
3. Update profile with remote IP (server IP) and start uperf at client: "uperf
-vai 5 -m rr1c-4kx4k---1.xml" (uperf profile, see above)
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: Skipper Bug Screeners (skipper-screen-team)
Status: New
** Tags: architecture-s39064 bugnameltc-203868 severity-medium
targetmilestone-inin---
** Tags added: architecture-s39064 bugnameltc-203868 severity-medium
targetmilestone-inin---
** Changed in: ubuntu
Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team)
** 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/2039575
Title:
[UBUNTU 22.04] SMC stats: Wrong bucket calculation for payload of
exactly 4096 bytes.
Status in linux package in Ubuntu:
New
Bug description:
Bug description by Nils H.:
Overview:
The following line in the SMC stats code (net/smc/smc_stats.h) caught my
attention when using a payload of exactly 4096 bytes:
#define SMC_STAT_PAYLOAD_SUB(_smc_stats, _tech, key, _len, _rc) \
do { \
typeof(_smc_stats) stats = (_smc_stats); \
typeof(_tech) t = (_tech); \
typeof(_len) l = (_len); \
int _pos = fls64((l) >> 13); \
typeof(_rc) r = (_rc); \
int m = SMC_BUF_MAX - 1; \
this_cpu_inc((*stats).smc[t].key ## _cnt); \
if (r <= 0) \
break; \
_pos = (_pos < m) ? ((l == 1 << (_pos + 12)) ? _pos - 1 : _pos) : m; \
<---
this_cpu_inc((*stats).smc[t].key ## _pd.buf[_pos]); \
this_cpu_add((*stats).smc[t].key ## _bytes, r); \
}
[Kernel-packages] [Bug 1919154] Re: Enable CONFIG_NO_HZ_FULL on supported architectures
jammy hwe kernel (6.2) with NO_HZ_FULL: https://launchpad.net/~gerald-yang-tw/+archive/ubuntu/no-hz-full-6.2 -- 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/1919154 Title: Enable CONFIG_NO_HZ_FULL on supported architectures Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: In Progress Status in linux source package in Groovy: Won't Fix Status in linux source package in Hirsute: In Progress Status in linux source package in Jammy: In Progress Status in linux source package in Lunar: In Progress Status in linux source package in Mantic: In Progress Bug description: [Impact] The CONFIG_NO_HZ_FULL=y Kconfig option causes the kernel to avoid sending scheduling-clock interrupts to CPUs with a single runnable task, and such CPUs are said to be "adaptive-ticks CPUs". This is important for applications with aggressive real-time response constraints because it allows them to improve their worst-case response times by the maximum duration of a scheduling-clock interrupt. It is also important for computationally intensive short-iteration workloads: If any CPU is delayed during a given iteration, all the other CPUs will be forced to wait idle while the delayed CPU finishes. Thus, the delay is multiplied by one less than the number of CPUs. In these situations, there is again strong motivation to avoid sending scheduling-clock interrupts. [Test Plan] In order to verify the change will not cause performance issues in context switch we should compare the results for: ./stress-ng --seq 0 --metrics-brief -t 15 Running on a dedicated machine and with the following services disabled: smartd.service, iscsid.service, apport.service, cron.service, anacron.timer, apt-daily.timer, apt-daily-upgrade.timer, fstrim.timer, logrotate.timer, motd-news.timer, man-db.timer. The results didn't show any performance regression: https://kernel.ubuntu.com/~mhcerri/lp1919154/ [Where problems could occur] Performance degradation might happen for workloads with intensive context switching. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1919154/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2039575] Comment bridged from LTC Bugzilla
--- Comment From boris.m...@de.ibm.com 2023-10-17 10:23 EDT--- --- MATTHEW R. commented --- I encountered this issue recently while verifying a KVM feature. It's worth noting that if a kernel has UBSAN enabled (https://docs.kernel.org/dev-tools/ubsan.html) then rather than silently updating an incorrect stats counter you will also get a UBSAN array- index-out-of-bounds warning every time this occurs. In my case, I bumped into this because I was using an Ubuntu kernel which came with UBSAN enabled. Example of the warning: [ 26.335369] [ 26.335381] UBSAN: array-index-out-of-bounds in /build/linux-O6Qi7m/linux-5.15.0/net/smc/af_smc.c:2402:3 [ 26.335385] index -1 is out of range for type 'u64 [9]' [ 26.335388] CPU: 0 PID: 274 Comm: iperf3 Tainted: GE 5.15.0-79-generic #86-Ubuntu [ 26.335391] Hardware name: IBM 8561 T01 772 (KVM/Linux) [ 26.335393] Call Trace: [ 26.335397] [] dump_stack_lvl+0x62/0x80 [ 26.335404] [ ] ubsan_epilogue+0x1c/0x48 [ 26.335406] [ ] __ubsan_handle_out_of_bounds+0x94/0xa0 [ 26.335411] [<03ff8033f9da>] smc_sendmsg+0x2aa/0x2d0 [smc] [ 26.335425] [ ] sock_sendmsg+0x64/0x80 [ 26.335431] [ ] sock_write_iter+0x72/0xa0 [ 26.335433] [ ] new_sync_write+0x100/0x190 [ 26.335438] [ ] vfs_write+0x1e8/0x280 [ 26.335440] [ ] ksys_write+0xb4/0x100 [ 26.335442] [ ] __do_syscall+0x1bc/0x1f0 [ 26.335446] [ ] system_call+0x78/0xa0 This makes the issue much more visible. Worse, if you have panic_on_warn enabled (like I did) then this warning will subsequently trigger a kernel panic. -- 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/2039575 Title: [UBUNTU 22.04] SMC stats: Wrong bucket calculation for payload of exactly 4096 bytes. Status in linux package in Ubuntu: New Bug description: Bug description by Nils H.: Overview: The following line in the SMC stats code (net/smc/smc_stats.h) caught my attention when using a payload of exactly 4096 bytes: #define SMC_STAT_PAYLOAD_SUB(_smc_stats, _tech, key, _len, _rc) \ do { \ typeof(_smc_stats) stats = (_smc_stats); \ typeof(_tech) t = (_tech); \ typeof(_len) l = (_len); \ int _pos = fls64((l) >> 13); \ typeof(_rc) r = (_rc); \ int m = SMC_BUF_MAX - 1; \ this_cpu_inc((*stats).smc[t].key ## _cnt); \ if (r <= 0) \ break; \ _pos = (_pos < m) ? ((l == 1 << (_pos + 12)) ? _pos - 1 : _pos) : m; \ <--- this_cpu_inc((*stats).smc[t].key ## _pd.buf[_pos]); \ this_cpu_add((*stats).smc[t].key ## _bytes, r); \ } \ while (0) With l = 4096, _pos evaluates to -1. Checking with the following uperf profile: # cat rr1c-4kx4k---1.xml smcd stats output: # smcd -d stats reset SMC-D Connections Summary Total connections handled 2 SMC connections 2 (client 2, server 0) v1 0 v2 2 Handshake errors 0 (client 0, server 0) Avg requests per SMC conn14.0 TCP fallback 0 (client 0, server 0) RX Stats Data transmitted (Bytes) 5796 (5.796K) Total requests9 Buffer full 0 (0.00%) Buffer downgrades 0 Buffer reuses 0 8KB16KB32KB64KB 128KB 256KB 512KB >512KB Bufs0 0 0 2 0 0 0 1 Reqs8 0 0 0 0 0 0 0 TX Stats Data transmitted (Bytes) 9960 (9.960K) Total requests 19 Buffer full 0 (0.00%) Buffer full (remote) 0 (0.00%) Buffer too small 0 (0.00%) Buffer too small (remote) 0 (0.00%) Buffer downgrades 0 Buffer reuses 0 8KB16KB32KB64KB 128KB 256KB 512KB >512KB Bufs0 2 0 0 0 0 0 0 Reqs 18 0 0 0 0 0 0 1 Extras Special socket calls 0 cork
[Kernel-packages] [Bug 2039576] [NEW] Enabling CONFIG_CRYPTO_STATS causes significant fscrypt performance degradation
Public bug reported: CONFIG_CRYPTO_STATS is enabled in Jammy 5.15.0-xx as well as 6.2.0-xx kernel by default. # uname -r 5.15.0-69-generic root@r100:~# grep CONFIG_CRYPTO_STATS /boot/config-5.15.0-69-generic CONFIG_CRYPTO_STATS=y However, that CONFIG_CRYPTO_STATS makes big negative performance impacts. Lustre (http://www.lustre.com Open source parallel filesystem) supports client encryption based on fscrypt. I ran some benchmarks of Lustre client encryption on Lustre client with Ubuntu 6.2.0-34-generic kernel below. 1 x client(2 x Gold 6438Y+, 512GB RAM, 2 x HDR200) Ubuntu22.04 (6.2.0-34-generic) # fio -name=iotest-w -ioengine=sync -rw=write -blocksize=16m -iodepth=1 -direct=1 -fallocate=none -size=200g -numjobs=128 -group_reporting -directory=/lustre/encrypted -create_serialize=0 -fiename_format='f.$jobnum.$filenum' -scramble_buffers=0 -runtime=60 6.2.0-34-generic, no encryption 48.5GB/s 6.2.0-34-generic, encryption 21.7GB/s 6.2.0-34-generic-noCryptStats, encryption 48.2GB/s When Lustre client encryption enabled, there were 65% performance degradations compared to non encryption's performance. (21.7GB/s vs 48.5GB/s) I also tested on 6.2.0-34-generic-noCryptStats which I built custom 6.2.0-34-generic kernel with disabling CONFIG_CRYPTO_STATS. The result was pretty good. The performance did boost and it was almost same speed against non encryption case. (48.2GB/s vs 48.5GB/s) I also found same fscrypt performance problem reported in Ceph with RHEL kernel below. https://lists.ceph.io/hyperkitty/list/ceph-us...@ceph.io/thread/44GMO5UGOXDZKFSOQMCPPHYTREUEA3ZI/ Eventually, Redhat disabled CONFIG_CRYPTO_STATS in latest RHEL9 kernel https://gitlab.com/redhat/centos-stream/src/kernel/centos-stream-9/-/merge_requests/2947 Kernel config option CONFIG_CRYPTO_STATS should be disabled until it is enhanced (BZ#2231850) - https://access.redhat.com/errata/RHSA-2023:5069 I would disable CONFIG_CRYPTO_STATS in all Jammy kernels until proper fixes and new solution is available in upstream kernel. ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2039576 Title: Enabling CONFIG_CRYPTO_STATS causes significant fscrypt performance degradation Status in linux package in Ubuntu: New Bug description: CONFIG_CRYPTO_STATS is enabled in Jammy 5.15.0-xx as well as 6.2.0-xx kernel by default. # uname -r 5.15.0-69-generic root@r100:~# grep CONFIG_CRYPTO_STATS /boot/config-5.15.0-69-generic CONFIG_CRYPTO_STATS=y However, that CONFIG_CRYPTO_STATS makes big negative performance impacts. Lustre (http://www.lustre.com Open source parallel filesystem) supports client encryption based on fscrypt. I ran some benchmarks of Lustre client encryption on Lustre client with Ubuntu 6.2.0-34-generic kernel below. 1 x client(2 x Gold 6438Y+, 512GB RAM, 2 x HDR200) Ubuntu22.04 (6.2.0-34-generic) # fio -name=iotest-w -ioengine=sync -rw=write -blocksize=16m -iodepth=1 -direct=1 -fallocate=none -size=200g -numjobs=128 -group_reporting -directory=/lustre/encrypted -create_serialize=0 -fiename_format='f.$jobnum.$filenum' -scramble_buffers=0 -runtime=60 6.2.0-34-generic, no encryption 48.5GB/s 6.2.0-34-generic, encryption 21.7GB/s 6.2.0-34-generic-noCryptStats, encryption 48.2GB/s When Lustre client encryption enabled, there were 65% performance degradations compared to non encryption's performance. (21.7GB/s vs 48.5GB/s) I also tested on 6.2.0-34-generic-noCryptStats which I built custom 6.2.0-34-generic kernel with disabling CONFIG_CRYPTO_STATS. The result was pretty good. The performance did boost and it was almost same speed against non encryption case. (48.2GB/s vs 48.5GB/s) I also found same fscrypt performance problem reported in Ceph with RHEL kernel below. https://lists.ceph.io/hyperkitty/list/ceph-us...@ceph.io/thread/44GMO5UGOXDZKFSOQMCPPHYTREUEA3ZI/ Eventually, Redhat disabled CONFIG_CRYPTO_STATS in latest RHEL9 kernel https://gitlab.com/redhat/centos-stream/src/kernel/centos-stream-9/-/merge_requests/2947 Kernel config option CONFIG_CRYPTO_STATS should be disabled until it is enhanced (BZ#2231850) - https://access.redhat.com/errata/RHSA-2023:5069 I would disable CONFIG_CRYPTO_STATS in all Jammy kernels until proper fixes and new solution is available in upstream kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2039576/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2039575] Comment bridged from LTC Bugzilla
--- Comment From boris.m...@de.ibm.com 2023-10-17 10:31 EDT---
There is a fix available (thanks Wenjia) to address this problem which occurs
with kernel 5.14 and above:
The fix patch "a950a5921db4 (net/smc: Fix pos miscalculation in
statistics)" is already upstream
--- Comment From boris.m...@de.ibm.com 2023-10-17 10:33 EDT---
FYI: This fix also resolves the UBSAN array-index-out-of-bounds issue mentioned
by Matthew
during the verification performed as part of IBM BZ 182254 / launchpad 1853306.
--
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/2039575
Title:
[UBUNTU 22.04] SMC stats: Wrong bucket calculation for payload of
exactly 4096 bytes.
Status in linux package in Ubuntu:
New
Bug description:
Bug description by Nils H.:
Overview:
The following line in the SMC stats code (net/smc/smc_stats.h) caught my
attention when using a payload of exactly 4096 bytes:
#define SMC_STAT_PAYLOAD_SUB(_smc_stats, _tech, key, _len, _rc) \
do { \
typeof(_smc_stats) stats = (_smc_stats); \
typeof(_tech) t = (_tech); \
typeof(_len) l = (_len); \
int _pos = fls64((l) >> 13); \
typeof(_rc) r = (_rc); \
int m = SMC_BUF_MAX - 1; \
this_cpu_inc((*stats).smc[t].key ## _cnt); \
if (r <= 0) \
break; \
_pos = (_pos < m) ? ((l == 1 << (_pos + 12)) ? _pos - 1 : _pos) : m; \
<---
this_cpu_inc((*stats).smc[t].key ## _pd.buf[_pos]); \
this_cpu_add((*stats).smc[t].key ## _bytes, r); \
} \
while (0)
With l = 4096, _pos evaluates to -1.
Checking with the following uperf profile:
# cat rr1c-4kx4k---1.xml
smcd stats output:
# smcd -d stats reset
SMC-D Connections Summary
Total connections handled 2
SMC connections 2 (client 2, server 0)
v1 0
v2 2
Handshake errors 0 (client 0, server 0)
Avg requests per SMC conn14.0
TCP fallback 0 (client 0, server 0)
RX Stats
Data transmitted (Bytes) 5796 (5.796K)
Total requests9
Buffer full 0 (0.00%)
Buffer downgrades 0
Buffer reuses 0
8KB16KB32KB64KB 128KB 256KB 512KB >512KB
Bufs0 0 0 2 0 0 0 1
Reqs8 0 0 0 0 0 0 0
TX Stats
Data transmitted (Bytes) 9960 (9.960K)
Total requests 19
Buffer full 0 (0.00%)
Buffer full (remote) 0 (0.00%)
Buffer too small 0 (0.00%)
Buffer too small (remote) 0 (0.00%)
Buffer downgrades 0
Buffer reuses 0
8KB16KB32KB64KB 128KB 256KB 512KB >512KB
Bufs0 2 0 0 0 0 0 0
Reqs 18 0 0 0 0 0 0 1
Extras
Special socket calls 0
cork0
nodelay 0
sendpage0
splice 0
urgent data 0
Instead of including the payload in the wrong >512KB buckets, output should
be to have 19 reqs in the 8KB buckets for TX stats and 9 reqs in the 8KB bucket
for RX stats.
Repro:
0. Install uperf.
1. Reset SMC-D stats on client and server.
2. Start uperf at server side: "uperf -vs".
3. Update profile with remote IP (server IP) and start uperf at client:
"uperf -vai 5 -m rr1c-4kx4k---1.xml" (uperf profile, see above)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2039575/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2039576] 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 2039576 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/2039576 Title: Enabling CONFIG_CRYPTO_STATS causes significant fscrypt performance degradation Status in linux package in Ubuntu: Incomplete Bug description: CONFIG_CRYPTO_STATS is enabled in Jammy 5.15.0-xx as well as 6.2.0-xx kernel by default. # uname -r 5.15.0-69-generic root@r100:~# grep CONFIG_CRYPTO_STATS /boot/config-5.15.0-69-generic CONFIG_CRYPTO_STATS=y However, that CONFIG_CRYPTO_STATS makes big negative performance impacts. Lustre (http://www.lustre.com Open source parallel filesystem) supports client encryption based on fscrypt. I ran some benchmarks of Lustre client encryption on Lustre client with Ubuntu 6.2.0-34-generic kernel below. 1 x client(2 x Gold 6438Y+, 512GB RAM, 2 x HDR200) Ubuntu22.04 (6.2.0-34-generic) # fio -name=iotest-w -ioengine=sync -rw=write -blocksize=16m -iodepth=1 -direct=1 -fallocate=none -size=200g -numjobs=128 -group_reporting -directory=/lustre/encrypted -create_serialize=0 -fiename_format='f.$jobnum.$filenum' -scramble_buffers=0 -runtime=60 6.2.0-34-generic, no encryption 48.5GB/s 6.2.0-34-generic, encryption 21.7GB/s 6.2.0-34-generic-noCryptStats, encryption 48.2GB/s When Lustre client encryption enabled, there were 65% performance degradations compared to non encryption's performance. (21.7GB/s vs 48.5GB/s) I also tested on 6.2.0-34-generic-noCryptStats which I built custom 6.2.0-34-generic kernel with disabling CONFIG_CRYPTO_STATS. The result was pretty good. The performance did boost and it was almost same speed against non encryption case. (48.2GB/s vs 48.5GB/s) I also found same fscrypt performance problem reported in Ceph with RHEL kernel below. https://lists.ceph.io/hyperkitty/list/ceph-us...@ceph.io/thread/44GMO5UGOXDZKFSOQMCPPHYTREUEA3ZI/ Eventually, Redhat disabled CONFIG_CRYPTO_STATS in latest RHEL9 kernel https://gitlab.com/redhat/centos-stream/src/kernel/centos-stream-9/-/merge_requests/2947 Kernel config option CONFIG_CRYPTO_STATS should be disabled until it is enhanced (BZ#2231850) - https://access.redhat.com/errata/RHSA-2023:5069 I would disable CONFIG_CRYPTO_STATS in all Jammy kernels until proper fixes and new solution is available in upstream kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2039576/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2037224] Re: Multiple RTL8851BE BT stability issues
verified linux-firmware/mantic version
Ubuntu-20230919.git3672ccab-0ubuntu2.2 from local builds.
** Tags added: verification-done-mantic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/2037224
Title:
Multiple RTL8851BE BT stability issues
Status in HWE Next:
New
Status in linux-firmware package in Ubuntu:
Fix Committed
Status in linux-firmware source package in Jammy:
Fix Released
Status in linux-firmware source package in Mantic:
Fix Committed
Bug description:
[SRU Justification]
[Impact]
There are multiple stability issues for RTL8851B.
Issue-1:
After disabling BT and leaving it idle for a period, manually turning on the
RTL8851BE will fail.
Issue-2:
Failed to probe Bluetooth USB interface after resumed from suspend. There may
be
either failure to read device descriptors:
usb 1-14: device descriptor read/64, error -71
or tx command timeout:
Bluetooth: hci0: Opcode 0x2041 failed: -110
Bluetooth: hci0: command 0x2041 tx timeout
[Fix]
Upstream commit addc33924 ("rtl_bt: Update RTL8851B BT USB firmware to
0x048A_D230").
[Test Case]
$ checkbox-cli run
com.canonical.plainbox::suspend/suspend_advanced_auto
[Where problems could occur]
This updates opaque firmware blobs, so it could bring further stability issues
and/or power consumption changes.
[Other Info]
While RTL8851B is only supported in oem-6.5 and linux/mantic >= 6.4, only
jammy
and mantic are nominated for fix.
= original bug report ==
[issue 1]
After disabling BT and leaving it idle for a period, manually turning
on the RTL8851BE will fail. (Can't reproduce on Wifi functionality.)
Test step:
1. Insert RTL8851BE Wifi card and install Ubuntu 22.04 OS. (Kernel : 6.5.0)
2. Check BT function after boot into OS.
3. Manually turn OFF BT function. Then wait for 1 minute.
4. Manually turn ON the BT function.
5. Unable to enable BT function. (issue occurs)
[issue 2]
System usb got tx command timeout after suspend resume.
Log:
Got read usb descriptor fail after suspend resume.
Sep 11 16:37:37 ubuntu kernel: usb 1-14: reset full-speed USB device number 3
using xhci_hcd
Sep 11 16:37:37 ubuntu kernel: usb 1-14: device descriptor read/64, error -71
Sep 11 16:37:38 ubuntu kernel: usb 1-14: device descriptor read/64, error -71
Sep 11 16:37:38 ubuntu kernel: usb 1-14: reset full-speed USB device number 3
using xhci_hcd
Sep 11 16:37:38 ubuntu kernel: usb 1-14: device descriptor read/64, error -71
Sep 11 16:37:38 ubuntu kernel: usb 1-14: device descriptor read/64, error -71
Sep 11 16:37:39 ubuntu kernel: usb 1-14: reset full-speed USB device number 3
using xhci_hcd
And tx command timeout.
Sep 11 16:37:41 ubuntu kernel: Bluetooth: hci0: Opcode 0x2041 failed: -110
Sep 11 16:37:41 ubuntu kernel: Bluetooth: hci0: command 0x2041 tx timeout
Sep 11 16:37:41 ubuntu kernel: usb 1-14: new full-speed USB device number 4
using xhci_hcd
Sep 11 16:37:41 ubuntu kernel: usb 1-14: device descriptor read/64, error -71
Test step:
1. Install dell-bto-jammy-jellyfish-abra-X96-20230822-1.iso
2. Boot into OS
3. checkbox-cli run com.canonical.plainbox::suspend/suspend_advanced_auto
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2037224/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2019011] Re: [UBUNTU 20.04] [HPS] Kernel panic with "refcount_t: underflow" in mlx5 driver
** Tags removed: verification-needed-focal-linux-bluefield -- 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/2019011 Title: [UBUNTU 20.04] [HPS] Kernel panic with "refcount_t: underflow" in mlx5 driver Status in Ubuntu on IBM z Systems: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Released Bug description: SRU Justification: == [ Impact ] * The mlx5 driver is causing a Kernel panic with "refcount_t: underflow". * This issue occurs during a recovery when the PCI device is isolated and thus doesn't respond. [ Fix ] * This issue got solved upstream with aaf2e65cac7f aaf2e65cac7f2e1ae729c2fbc849091df9699f96 "net/mlx5: Fix handling of entry refcount when command is not issued to FW" (upstream since 6.1-rc1) * But to get aaf2e65cac7f a backport of b898ce7bccf1 b898ce7bccf13087719c021d829dab607c175246 "net/mlx5: cmdif, Avoid skipping reclaim pages if FW is not accessible" is required on top (upstream since 5.10) [ Test Plan ] * An Ubuntu Server for s390x 20.04 LPAR or z/VM installation is needed that has Mellanox cards (RoCE Express 2.1) assigned, configured and enabled and that runs a 5.4 kernel with mlx5 driver. * Create some network traffic on (one of the) RoCE device (interface ens???[d?]) for testing (e.g. with stress-ng). * Make sure the module/driver mlx5 is loaded and in use. * Trigger a recovery (via the Support Element) that will render the adapter (ports) unresponsive for a moment and should provoke a similar situation. * Alternatively the interface itself can be removed for a moment and re-added again (but this may break further things on top). * Due to the lack of RoCE Express 2.1 hardware, the verification is on IBM. [ Where problems could occur ] * The modifications are limited to the Mellanox mlx5 driver only - no other network driver is affected. * The pre-required commit (aaf2e65cac7f) can have a bad impact on (re-)claiming pages if FW is not accessible, which could cause page leaks in case done wrong. But this commit is pretty save since it's upstream since v5.10. * The fix itself (aaf2e65cac7f) mainly changes the cmd_work_handler and mlx5_cmd_comp_handler functions in a way that instead of pci_channel_offline mlx5_cmd_is_down (introiduced by b898ce7bccf1). * Actually b898ce7bccf1 started with changing from pci_channel_offline to mlx5_cmd_is_down, but looks like a few cases (in the area of refcount increate/decrease) were missed, that are now covered by aaf2e65cac7f. * It fixes now on top refcounts are now always properly increment and decrement to achieve a symmetric state for all flows. * These changes may have an impact on all cases where the mlx5 device is not responding, which can happen in case of an offline channel, interface down, reset or recovery. [ Other Info ] * Looking at the master-next git trees for jammy, kinetic and lunar showed that both fixes are already included, hence only focal is affected. __ ---Problem Description--- Kernel panic with "refcount_t: underflow" in kernel log Contact Information = rijo...@ibm.com, vineeth.vija...@ibm.com ---uname output--- 5.4.0-128-generic Machine Type = s390x ---System Hang--- Kernel panic and stack-trace as below ---Debugger--- A debugger is not configured Stack trace output: [Sat Apr 8 17:52:21 UTC 2023] Call Trace: [Sat Apr 8 17:52:21 UTC 2023] ([<002a5939a286>] refcount_warn_saturate+0xce/0x140) [Sat Apr 8 17:52:21 UTC 2023] [<03ff805f861e>] cmd_ent_put+0xe6/0xf8 [mlx5_core] [Sat Apr 8 17:52:21 UTC 2023] [<03ff805f9b6a>] mlx5_cmd_comp_handler+0x102/0x4f0 [mlx5_core] [Sat Apr 8 17:52:21 UTC 2023] [<03ff805f9f8a>] cmd_comp_notifier+0x32/0x48 [mlx5_core] [Sat Apr 8 17:52:21 UTC 2023] [<002a58ecf0c6>] notifier_call_chain+0x4e/0xa0 [Sat Apr 8 17:52:21 UTC 2023] [<002a58ecf17e>] atomic_notifier_call_chain+0x2e/0x40 [Sat Apr 8 17:52:21 UTC 2023] [<03ff805fe4fc>] mlx5_eq_async_int+0x13c/0x200 [mlx5_core] [Sat Apr 8 17:52:21 UTC 2023] [<002a58ecf0c6>] notifier_call_chain+0x4e/0xa0 [Sat Apr 8 17:52:21 UTC 2023] [<002a58ecf17e>] atomic_notifier_call_chain+0x2e/0x40 [Sat Apr 8 17:52:21 UTC 2023] [<03ff8061318e>] mlx5_irq_int_handler+0x2e/0x48 [mlx5_core] [Sat Apr 8 17:52:21 UTC 2023] [<002a58f1455a>] __handle_irq_event_percpu+0x6a/0x250 [Sat Apr 8 17:52:21 UTC 2023] [<002a58f14770>] handle_irq_event_percpu+0x30/0x78 [Sat Apr 8 17:52:21 UTC 2023] [<002a58f1a0c8>] handle_percpu_irq+0x68/0xa0 [Sat Apr 8 17:52:21 UTC 2023] [<002a58f134d2
[Kernel-packages] [Bug 2028568] Re: Ship kernel modules Zstd compressed
** Description changed: To reduce the size of the initramfs and also to speed up the boot (by only decompressing the modules that are needed), please compress the kernel modules. From size and speed perspective, either use zstd or xz. I suggest to go with zstd -19. This change is independent of the initramfs-tools version. Old initramfs-tools versions will decompress the kernel modules before putting them in the initramfs. New initramfs-tools versions will put the compressed kernel modules into an uncompressed cpio archive (see bug #2028567). See also https://lists.ubuntu.com/archives/ubuntu- devel/2023-July/042652.html and https://lists.ubuntu.com/archives/ubuntu-devel/2023-July/042707.html + + See https://discourse.ubuntu.com/t/reduce-initramfs-size-and-speed-up- + the-generation-in-ubuntu-23-10/38972 for the performance evaluation. -- 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/2028568 Title: Ship kernel modules Zstd compressed Status in linux package in Ubuntu: Fix Released Bug description: To reduce the size of the initramfs and also to speed up the boot (by only decompressing the modules that are needed), please compress the kernel modules. From size and speed perspective, either use zstd or xz. I suggest to go with zstd -19. This change is independent of the initramfs-tools version. Old initramfs-tools versions will decompress the kernel modules before putting them in the initramfs. New initramfs-tools versions will put the compressed kernel modules into an uncompressed cpio archive (see bug #2028567). See also https://lists.ubuntu.com/archives/ubuntu- devel/2023-July/042652.html and https://lists.ubuntu.com/archives/ubuntu-devel/2023-July/042707.html See https://discourse.ubuntu.com/t/reduce-initramfs-size-and-speed-up- the-generation-in-ubuntu-23-10/38972 for the performance evaluation. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2028568/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2034477] Re: Keyboard and Touchpad Not Working in New Lenovo V15 Gen4 Laptop
Hi Kyrylo, what does this mean exactly? When it will be publicly available on Ubuntu updates? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/2034477 Title: Keyboard and Touchpad Not Working in New Lenovo V15 Gen4 Laptop Status in linux-signed package in Ubuntu: Confirmed Status in linux-signed-hwe-6.2 package in Ubuntu: Confirmed Status in Fedora: New Bug description: Hello. Ubuntu 22.04.3 with (later upgraded to kernel 6.2.0-32-generic) was installed in rewly purchased LENOVO V15 GEN4 AMN (AMD Ryzen 5 7520u) laptop and it was noticed that keyboard, touchpad and microphone are not working. The keyboard and touchpad work fine in BIOS setup and till GRUB (command line). It was found that when external devices such as keyboard, mouse and microphone are connected through USB and 3.5 jack, respectively, these work just fine. To confirm these are not hardware problems, Microsoft Windows 11 (Home) was installed in another disk partition and observed all these working alright. Hence a bug is being reported to draw attention of the concerned team and I request them to refer this issue and do the needful at the earliest. Regards, Pradip Kumar Das ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-32-generic 6.2.0-32.32~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-32.32~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Sep 6 08:04:42 2023 InstallationDate: Installed on 2023-08-14 (22 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/2034477/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2039601] [NEW] [ kernel regression ] nvme not working on some laptops
Public bug reported:
With the update to Ubuntu 23.10 my nvme drive ceased to function.
Booting the old 6.2 kernel from 23.04 works, but not the newer 6.5.9.
This is a kernel bug that's been fixed in 6.5.6, any chance it could
possibly be backported?
More information: https://bugzilla.kernel.org/show_bug.cgi?id=217802
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-9-generic 6.5.0-9.9
ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
Uname: Linux 6.5.0-9-generic x86_64
NonfreeKernelModules: zfs
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: luis 3036 F wireplumber
/dev/snd/controlC1: luis 3036 F wireplumber
/dev/snd/seq:luis 3029 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Oct 17 21:05:29 2023
InstallationDate: Installed on 2023-10-16 (1 days ago)
InstallationMedia: Ubuntu Legacy 23.10 "Mantic Minotaur" - Release amd64
(20231010)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-9-generic
root=UUID=014fd29c-595e-4b8b-aedc-34e1eb9ab082 ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-6.5.0-9-generic N/A
linux-backports-modules-6.5.0-9-generic N/A
linux-firmware 20230919.git3672ccab-0ubuntu2.1
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/17/2019
dmi.bios.release: 1.18
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.18.0
dmi.board.name: 05FFDN
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr1.18.0:bd11/17/2019:br1.18:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr:sku07BE:
dmi.product.family: XPS
dmi.product.name: XPS 15 9560
dmi.product.sku: 07BE
dmi.sys.vendor: Dell Inc.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug mantic 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/2039601
Title:
[ kernel regression ] nvme not working on some laptops
Status in linux package in Ubuntu:
New
Bug description:
With the update to Ubuntu 23.10 my nvme drive ceased to function.
Booting the old 6.2 kernel from 23.04 works, but not the newer 6.5.9.
This is a kernel bug that's been fixed in 6.5.6, any chance it could
possibly be backported?
More information: https://bugzilla.kernel.org/show_bug.cgi?id=217802
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-9-generic 6.5.0-9.9
ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
Uname: Linux 6.5.0-9-generic x86_64
NonfreeKernelModules: zfs
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: luis 3036 F wireplumber
/dev/snd/controlC1: luis 3036 F wireplumber
/dev/snd/seq:luis 3029 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Oct 17 21:05:29 2023
InstallationDate: Installed on 2023-10-16 (1 days ago)
InstallationMedia: Ubuntu Legacy 23.10 "Mantic Minotaur" - Release amd64
(20231010)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-9-generic
root=UUID=014fd29c-595e-4b8b-aedc-34e1eb9ab082 ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-6.5.0-9-generic N/A
linux-backports-modules-6.5.0-9-generic N/A
linux-firmware 20230919.git3672ccab-0ubuntu2.1
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/17/2019
dmi.bios.release: 1.18
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.18.0
dmi.board.name: 05FFDN
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr1.18.0:bd11/17/2019:br1.18:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr:sku07BE:
dmi.product.family: XPS
dmi.product.name: XPS 15 9560
dmi.product.sku: 07BE
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2039601/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2039601] Re: [ kernel regression ] nvme not working on some laptops
> but not the newer 6.5.9
Sorry, I obvs meant 6.5.0-9.
--
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/2039601
Title:
[ kernel regression ] nvme not working on some laptops
Status in linux package in Ubuntu:
New
Bug description:
With the update to Ubuntu 23.10 my nvme drive ceased to function.
Booting the old 6.2 kernel from 23.04 works, but not the newer 6.5.9.
This is a kernel bug that's been fixed in 6.5.6, any chance it could
possibly be backported?
More information: https://bugzilla.kernel.org/show_bug.cgi?id=217802
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-9-generic 6.5.0-9.9
ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
Uname: Linux 6.5.0-9-generic x86_64
NonfreeKernelModules: zfs
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: luis 3036 F wireplumber
/dev/snd/controlC1: luis 3036 F wireplumber
/dev/snd/seq:luis 3029 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Oct 17 21:05:29 2023
InstallationDate: Installed on 2023-10-16 (1 days ago)
InstallationMedia: Ubuntu Legacy 23.10 "Mantic Minotaur" - Release amd64
(20231010)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-9-generic
root=UUID=014fd29c-595e-4b8b-aedc-34e1eb9ab082 ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-6.5.0-9-generic N/A
linux-backports-modules-6.5.0-9-generic N/A
linux-firmware 20230919.git3672ccab-0ubuntu2.1
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/17/2019
dmi.bios.release: 1.18
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.18.0
dmi.board.name: 05FFDN
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr1.18.0:bd11/17/2019:br1.18:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr:sku07BE:
dmi.product.family: XPS
dmi.product.name: XPS 15 9560
dmi.product.sku: 07BE
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2039601/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2038349] Re: [j:linux-intel-iotg][j:linux-intel-iot-realtime] Cannot set frame preemption
** Changed in: linux-intel-iotg (Ubuntu)
Status: In Progress => Fix Committed
** Changed in: linux-intel-iotg (Ubuntu Jammy)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-intel-iotg in Ubuntu.
https://bugs.launchpad.net/bugs/2038349
Title:
[j:linux-intel-iotg][j:linux-intel-iot-realtime] Cannot set frame
preemption
Status in linux-intel-iotg package in Ubuntu:
Fix Committed
Status in linux-intel-iotg source package in Jammy:
Fix Committed
Bug description:
This is a public version of https://bugs.launchpad.net/bugs/2034007
[Summary]
System cannot set frame preemption via the ethtool-rt from snap store[1],
will got netlink error.
[1] https://snapcraft.io/ethtool-rt
u@u-Alder-Lake-Client-Platform:~$ sudo ethtool-rt.ethtool
--set-frame-preemption enp1s0 fp on
netlink error: frame preemption settings update failed
netlink error: Invalid argument
u@u-Alder-Lake-Client-Platform:~$ echo $?
81
u@u-Alder-Lake-Client-Platform:~$ sudo ethtool-rt.ethtool
--show-frame-preemption enp1s0
Frame preemption settings for enp1s0:
enabled: not enabled
additional fragment size: 0
verified: 0
verification disabled: 1
[Steps to reproduce]
1. sudo snap install ethtool-ty --devmode --edge
2.sudo ethtool-rt.ethtool --set-frame-preemption {your ethernet interface} fp
on
3.sudo ethtool-rt.ethtool --show-frame-preemption {your ethernet interface}
[Expected result]
Set frame preemption successfully.
[Actual result]
Got netlink error.
[Failure rate]
3/3
[Additional information]
CID: 202305-31589
SKU: ADL-S
system-manufacturer: Intel Corporation
system-product-name: Alder Lake Client Platform
bios-version: RPLISFI1.R00.4081.A05.2305241419
CPU: 12th Gen Intel(R) Core(TM) i3-12100E (8x)
GPU: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device
[8086:4692] (rev 0c)
kernel-version: 5.15.0-1035-intel-iot-realtime
[Stage]
Issue reported and logs collected right after it happened
--
Philip Cox (philcox) wrote on 2023-09-07:   #4
After going through the code, it looks like this is caused by the variable
fpcmd->add_frag_size is set to 0 and in the function igc_ethtool_set_preempt()
there is the following check:
if (fpcmd->add_frag_size < 68 || fpcmd->add_frag_size > 260)
return -EINVAL;
And this is causing the the --set-frame-preemption to fail.
ubuntu@adl-p:~$ sudo ethtool-rt.ethtool --set-frame-preemption enp169s0 fp on
; echo $?
netlink error: frame preemption settings update failed
netlink error: Invalid argument
81
ubuntu@adl-p:~$
I see in igc.h that there is a #define for
IGC_I225_MIN_FRAG_SIZE_DEFAULT which is:
#define IGC_I225_MIN_FRAG_SIZE_DEFAULT 68
This is set in igc_tsn_disable_offload()
static int igc_tsn_disable_offload(struct igc_adapter *adapter)
{
...
adapter->cycle_time = 0;
adapter->add_frag_size = IGC_I225_MIN_FRAG_SIZE_DEFAULT;
...
}
but igc_tsn_disable_offload is not called, so the value is never set.
-
Lai Jun Ann (laijunann-intel) wrote 12 hours ago: #12
0001-igc-fix-frame-preemption-not-able-to-set.patch Edit (1.3 KiB, text/plain)
The patch is ready and uploaded. Below shows the testing done with the patch:
oot@ubuntu-Alder-Lake-Client-Platform:~# ethtool --show-frame-preemption
enp1s0
Frame preemption settings for enp1s0:
enabled: enabled
additional fragment size: 68
verified: 0
verification disabled: 1
root@ubuntu-Alder-Lake-Client-Platform:~#
root@ubuntu-Alder-Lake-Client-Platform:~# ethtool --set-frame-preemption
enp1s0 fp off
root@ubuntu-Alder-Lake-Client-Platform:~# ethtool --show-frame-preemption
enp1s0
Frame preemption settings for enp1s0:
enabled: not enabled
additional fragment size: 68
verified: 0
verification disabled: 1
root@ubuntu-Alder-Lake-Client-Platform:~# ethtool --set-frame-preemption
enp1s0 fp on
root@ubuntu-Alder-Lake-Client-Platform:~# ethtool --show-frame-preemption
enp1s0
Frame preemption settings for enp1s0:
enabled: enabled
additional fragment size: 68
verified: 0
verification disabled: 1
--
Philip Cox (philcox) wrote 20 minutes ago:  #13
I've tested the patch as well, and it works. Thanks.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-intel-iotg/+bug/2038349/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2039601] 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/2039601
Title:
[ kernel regression ] nvme not working on some laptops
Status in linux package in Ubuntu:
Confirmed
Bug description:
With the update to Ubuntu 23.10 my nvme drive ceased to function.
Booting the old 6.2 kernel from 23.04 works, but not the newer 6.5.9.
This is a kernel bug that's been fixed in 6.5.6, any chance it could
possibly be backported?
More information: https://bugzilla.kernel.org/show_bug.cgi?id=217802
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-9-generic 6.5.0-9.9
ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
Uname: Linux 6.5.0-9-generic x86_64
NonfreeKernelModules: zfs
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: luis 3036 F wireplumber
/dev/snd/controlC1: luis 3036 F wireplumber
/dev/snd/seq:luis 3029 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Oct 17 21:05:29 2023
InstallationDate: Installed on 2023-10-16 (1 days ago)
InstallationMedia: Ubuntu Legacy 23.10 "Mantic Minotaur" - Release amd64
(20231010)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-9-generic
root=UUID=014fd29c-595e-4b8b-aedc-34e1eb9ab082 ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-6.5.0-9-generic N/A
linux-backports-modules-6.5.0-9-generic N/A
linux-firmware 20230919.git3672ccab-0ubuntu2.1
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/17/2019
dmi.bios.release: 1.18
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.18.0
dmi.board.name: 05FFDN
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr1.18.0:bd11/17/2019:br1.18:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr:sku07BE:
dmi.product.family: XPS
dmi.product.name: XPS 15 9560
dmi.product.sku: 07BE
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2039601/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2034622] Re: NVIDIA pull requests 1017-001v3
** Tags added: verification-done-jammy-linux-nvidia-tegra -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia-tegra in Ubuntu. https://bugs.launchpad.net/bugs/2034622 Title: NVIDIA pull requests 1017-001v3 Status in linux-nvidia-tegra package in Ubuntu: New Bug description: Apply patches from NVIDIA pull request sent on 2023-09-04 to jammy:linux-nvidia-tegra. 1017-001 V3 (2023-09-14): Akhil R (1): NVIDIA: SAUCE: Revert "i2c: tegra: Allocate DMA memory for DMA engine" Andy Sobczyk (1): NVIDIA: SAUCE: arm64: config: Enable MTD_UBI Ashish Mhetre (2): NVIDIA: SAUCE: iommu: Don't reserve IOVA when address and size are zero NVIDIA: SAUCE: memory: tegra: Add SID override on resume Kartik (1): NVIDIA: SAUCE: mailbox: tegra-hsp: Add sm ops route_irq & set_irq Laxman Dewangan (2): NVIDIA: SAUCE: config: Disable CONFIG_LOCALVERSION_AUTO NVIDIA: SAUCE: arm64: config: recovery_chain: Enable KEXEC configs Mikko Perttunen (2): thermal: tegra-bpmp: Handle errors in BPMP response thermal/drivers/tegra-bpmp: Handle offline zones Mohan Kumar (1): NVIDIA: SAUCE: arch: arm64: enable HDA_INTEL config Parker Newman (1): i2c: tegra: Fix i2c-tegra DMA config option processing Penny Chiu (1): NVIDIA: SAUCE: arm64: configs: Enable BINFMT_MISC support Sumit Gupta (2): NVIDIA: SAUCE: driver: cpufreq: remove volatile as not needed cpufreq: tegra194: add online/offline hooks Vishwaroop A (1): NVIDIA: SAUCE: spi: spi-tegra114: retain the spi mode raju patel (1): NVIDIA: SAUCE: code-owners: Populate OWNERS file zuyih (1): NVIDIA: SAUCE: s25fs: Add post-get-map-id fixup for S25FS512S --- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-tegra/+bug/2034622/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2039603] [NEW] NVIDIA pull requests 1018-001v1
Public bug reported: Apply patches from NVIDIA pull request sent on 2023-10-13 to jammy:linux-nvidia-tegra. - 1018-001-v1 - Akhil R (1): NVIDIA: SAUCE: crypto: tegra: Add Kconfig to support Tegra SE Ashish Mhetre (1): NVIDIA: SAUCE: memory: tegra: Fix SID override Daniel Vetter (1): drm/vgem: use shmem helpers Gautham Srinivasan (1): NVIDIA: SAUCE: arm64: configs: enable cifs Hector Martin (1): of: Move simple-framebuffer device handling from simplefb to of Johnny Liu (2): NVIDIA: SAUCE: memory: tegra: Add bpmp_id and type for nvdla NVIDIA: SAUCE: memory: tegra: Add clients for VI in Tegra234 Jon Hunter (1): NVIDIA: SAUCE: dma-buf-map: Fix-up iosys-map integration Kartik (2): NVIDIA: SAUCE: mailbox: tegra-hsp: Add support for virtualization NVIDIA: SAUCE: fs: eventpoll: Add smp_mb() before waitqueue_active Lucas De Marchi (3): dma-buf-map: Rename to iosys-map iosys-map: Add offset to iosys_map_memcpy_to() iosys-map: Add a few more helpers Mikko Perttunen (1): NVIDIA: SAUCE: thermal: tegra-bpmp: Check if BPMP supports trip points Prathamesh Shete (1): NVIDIA: SAUCE: mmc: host: Apply post auto-tuning correction Santosh Reddy Galma (1): NVIDIA: SAUCE: simplefb: add support to parse fb-memory from DT Shunsuke Mie (1): dma-buf: Update obsoluted comments on dma_buf_vmap/vunmap() vinothkumarr (1): NVIDIA: SAUCE: mtd: spi-nor: support for GD --- ** Affects: linux-nvidia-tegra (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia-tegra in Ubuntu. https://bugs.launchpad.net/bugs/2039603 Title: NVIDIA pull requests 1018-001v1 Status in linux-nvidia-tegra package in Ubuntu: New Bug description: Apply patches from NVIDIA pull request sent on 2023-10-13 to jammy:linux-nvidia-tegra. - 1018-001-v1 - Akhil R (1): NVIDIA: SAUCE: crypto: tegra: Add Kconfig to support Tegra SE Ashish Mhetre (1): NVIDIA: SAUCE: memory: tegra: Fix SID override Daniel Vetter (1): drm/vgem: use shmem helpers Gautham Srinivasan (1): NVIDIA: SAUCE: arm64: configs: enable cifs Hector Martin (1): of: Move simple-framebuffer device handling from simplefb to of Johnny Liu (2): NVIDIA: SAUCE: memory: tegra: Add bpmp_id and type for nvdla NVIDIA: SAUCE: memory: tegra: Add clients for VI in Tegra234 Jon Hunter (1): NVIDIA: SAUCE: dma-buf-map: Fix-up iosys-map integration Kartik (2): NVIDIA: SAUCE: mailbox: tegra-hsp: Add support for virtualization NVIDIA: SAUCE: fs: eventpoll: Add smp_mb() before waitqueue_active Lucas De Marchi (3): dma-buf-map: Rename to iosys-map iosys-map: Add offset to iosys_map_memcpy_to() iosys-map: Add a few more helpers Mikko Perttunen (1): NVIDIA: SAUCE: thermal: tegra-bpmp: Check if BPMP supports trip points Prathamesh Shete (1): NVIDIA: SAUCE: mmc: host: Apply post auto-tuning correction Santosh Reddy Galma (1): NVIDIA: SAUCE: simplefb: add support to parse fb-memory from DT Shunsuke Mie (1): dma-buf: Update obsoluted comments on dma_buf_vmap/vunmap() vinothkumarr (1): NVIDIA: SAUCE: mtd: spi-nor: support for GD --- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-tegra/+bug/2039603/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2031580] Re: 6.2 kernel on Ubuntu 22.04 causes wake from suspend failures on MacBook Pro (Retina, 13-inch, Early 2015) Model Identifier: MacBookPro12, 1
I am on Ubuntu 22.04.3 LTS, but tried the 6.2.0-34-generic kernel. >From then on the PC did not fully recover from S3, and by this I mean that while the screen stays black I can switch to a terminal with a Alt + F# combination and trigger a successful reboot. As far as I can see it's not an Ubuntu specific issue, there is clearly a regression in the upstream kernel, but it would great if we could narrow this down. Of course, the problem disappears when reverting back to the 5.13.0-30-generic I was using before. I will review the logs, but in the meantime I hope it helps. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2031580 Title: 6.2 kernel on Ubuntu 22.04 causes wake from suspend failures on MacBook Pro (Retina, 13-inch, Early 2015) Model Identifier: MacBookPro12,1 Status in intel-microcode package in Ubuntu: Invalid Status in linux-hwe-6.2 package in Ubuntu: Confirmed Bug description: Disabling Wayland partially helps but eventually will cause the computer to not wake up. This occurs both when closing the lid and when leaving the computer idle for some time. Description: Ubuntu 22.04.3 LTS Release: 22.04 intel-microcode: Installed: 3.20230808.0ubuntu0.22.04.1 I expected resume from sleep/suspend to behave as it did prior. If I would open the lid or push any keys, the computer would wake up from sleep/suspend. Instead, the computer does not wake from sleep/suspend and I need to force the computer to shutdown using the power button and then turn it back on again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/2031580/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2034745] Re: [regression] Unable to initialize SGX enclaves with XFRM other than 3
So it looks like this patch was applied to linux/5.4.0-166.183, linux/5.15.0-88.98, and linux/6.2.0-36.37, but I'm not seeing a request for verification on the jammy-azure-5.15.0-1049 kernel series, and it looks like linux-azure (5.15.0-1049.56) does not include the fix. Can we get the azure kernel fixed 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/2034745 Title: [regression] Unable to initialize SGX enclaves with XFRM other than 3 Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Committed Status in linux source package in Jammy: Fix Committed Status in linux source package in Lunar: Fix Committed Bug description: SRU Justification [Impact] In 5.15.0-1045, only loading enclaves with XFRM set to 3 works, sgx_encl_init returns EINVAL. The only reason this wouldn't work properly is if sgx_drv_init thinks XSAVE isn't enabled. This works fine in 5.15.0-1043. Likely cause: 1045 adds this patch: https://github.com/torvalds/linux/commit/b81fac906a8f9e682e513ddd95697ec7a20878d4 . This later patch indicates that the former patch introduced some ordering problems. https://github.com/torvalds/linux/commit/2c66ca3949dc701da7f4c9407f2140ae425683a5 . That later patch isn't applied to 1045. [Test Plan] User test results pending, but its a fix commit so should likely be applied regardless. [Regression Potential] SGX could continue to fail. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2034745/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2039608] [NEW] Jammy update: v5.15.130 upstream stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.15.130 upstream stable release from git://git.kernel.org/ ACPI: thermal: Drop nocrt parameter module: Expose module_init_layout_section() arm64: module-plts: inline linux/moduleloader.h arm64: module: Use module_init_layout_section() to spot init sections ARM: module: Use module_init_layout_section() to spot init sections rcu: Prevent expedited GP from enabling tick on offline CPU rcu-tasks: Fix IPI failure handling in trc_wait_for_one_reader rcu-tasks: Wait for trc_read_check_handler() IPIs rcu-tasks: Add trc_inspect_reader() checks for exiting critical section Linux 5.15.130 UBUNTU: Upstream stable to v5.15.130 ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Jammy) Importance: Medium Assignee: Kamal Mostafa (kamalmostafa) Status: In Progress ** Tags: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Description changed: + SRU Justification - SRU Justification + Impact: + The upstream process for stable tree updates is quite similar + in scope to the Ubuntu SRU process, e.g., each patch has to + demonstrably fix a bug, and each patch is vetted by upstream + by originating either directly from a mainline/stable Linux tree or + a minimally backported form of that patch. The following upstream + stable patches should be included in the Ubuntu kernel: - Impact: -The upstream process for stable tree updates is quite similar -in scope to the Ubuntu SRU process, e.g., each patch has to -demonstrably fix a bug, and each patch is vetted by upstream -by originating either directly from a mainline/stable Linux tree or -a minimally backported form of that patch. The following upstream -stable patches should be included in the Ubuntu kernel: + v5.15.130 upstream stable release + from git://git.kernel.org/ -v5.15.130 upstream stable release -from git://git.kernel.org/ + ACPI: thermal: Drop nocrt parameter + module: Expose module_init_layout_section() + arm64: module-plts: inline linux/moduleloader.h + arm64: module: Use module_init_layout_section() to spot init sections + ARM: module: Use module_init_layout_section() to spot init sections + rcu: Prevent expedited GP from enabling tick on offline CPU + rcu-tasks: Fix IPI failure handling in trc_wait_for_one_reader + rcu-tasks: Wait for trc_read_check_handler() IPIs + rcu-tasks: Add trc_inspect_reader() checks for exiting critical section + Linux 5.15.130 + UBUNTU: Upstream stable to v5.15.130 ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid ** Changed in: linux (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Jammy) Assignee: (unassigned) => Kamal Mostafa (kamalmostafa) -- 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/2039608 Title: Jammy update: v5.15.130 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: In Progress Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.15.130 upstream stable release from git://git.kernel.org/ ACPI: thermal: Drop nocrt parameter module: Expose module_init_layout_section() arm64: module-plts: inline linux/moduleloader.h arm64: module: Use module_init_layout_section() to spot init sections ARM: module: Use module_init_layout_section() to spot init sections rcu: Prevent expedited GP from enabling tick on offline CPU rcu-tasks: Fix IPI failure handling in trc_wait_for_one_reader rcu-tasks: Wait for trc_read_check_handler() IPIs rcu-tasks: Add trc_inspect_reader() checks for exiting critical section Linux 5.15.130 UBUNTU: U
[Kernel-packages] [Bug 2039610] [NEW] Jammy update: v5.15.131 upstream stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.15.131 upstream stable release from git://git.kernel.org/ erofs: ensure that the post-EOF tails are all zeroed ksmbd: fix wrong DataOffset validation of create context ksmbd: replace one-element array with flex-array member in struct smb2_ea_info ARM: pxa: remove use of symbol_get() mmc: au1xmmc: force non-modular build and remove symbol_get usage net: enetc: use EXPORT_SYMBOL_GPL for enetc_phc_index rtc: ds1685: use EXPORT_SYMBOL_GPL for ds1685_rtc_poweroff modules: only allow symbol_get of EXPORT_SYMBOL_GPL modules USB: serial: option: add Quectel EM05G variant (0x030e) USB: serial: option: add FOXCONN T99W368/T99W373 product ALSA: usb-audio: Fix init call orders for UAC1 usb: dwc3: meson-g12a: do post init to fix broken usb after resumption usb: chipidea: imx: improve logic if samsung,picophy-* parameter is 0 HID: wacom: remove the battery when the EKR is off staging: rtl8712: fix race condition Bluetooth: btsdio: fix use after free bug in btsdio_remove due to race condition wifi: mt76: mt7921: do not support one stream on secondary antenna only serial: qcom-geni: fix opp vote on shutdown serial: sc16is7xx: fix broken port 0 uart init serial: sc16is7xx: fix bug when first setting GPIO direction firmware: stratix10-svc: Fix an NULL vs IS_ERR() bug in probe fsi: master-ast-cf: Add MODULE_FIRMWARE macro tcpm: Avoid soft reset when partner does not support get_status nilfs2: fix general protection fault in nilfs_lookup_dirty_data_buffers() nilfs2: fix WARNING in mark_buffer_dirty due to discarded buffer reuse pinctrl: amd: Don't show `Invalid config param` errors usb: typec: tcpci: move tcpci.h to include/linux/usb/ usb: typec: tcpci: clear the fault status bit Linux 5.15.131 UBUNTU: Upstream stable to v5.15.131 ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Jammy) Importance: Medium Assignee: Kamal Mostafa (kamalmostafa) Status: In Progress ** Tags: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid ** Changed in: linux (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Jammy) Assignee: (unassigned) => Kamal Mostafa (kamalmostafa) ** Description changed: + SRU Justification - SRU Justification + Impact: + The upstream process for stable tree updates is quite similar + in scope to the Ubuntu SRU process, e.g., each patch has to + demonstrably fix a bug, and each patch is vetted by upstream + by originating either directly from a mainline/stable Linux tree or + a minimally backported form of that patch. The following upstream + stable patches should be included in the Ubuntu kernel: - Impact: -The upstream process for stable tree updates is quite similar -in scope to the Ubuntu SRU process, e.g., each patch has to -demonstrably fix a bug, and each patch is vetted by upstream -by originating either directly from a mainline/stable Linux tree or -a minimally backported form of that patch. The following upstream -stable patches should be included in the Ubuntu kernel: + v5.15.131 upstream stable release + from git://git.kernel.org/ -v5.15.131 upstream stable release -from git://git.kernel.org/ + erofs: ensure that the post-EOF tails are all zeroed + ksmbd: fix wrong DataOffset validation of create context + ksmbd: replace one-element array with flex-array member in struct smb2_ea_info + ARM: pxa: remove use of symbol_get() + mmc: au1xmmc: force non-modular build and remove symbol_get usage + net: enetc: use EXPORT_SYMBOL_GPL for enetc_phc_index + rtc: ds1685: use EXPORT_SYMBOL_GPL for ds1685_rtc_poweroff + modules: only allow symbol_get of EXPORT_SYMBOL_GPL modules + USB: serial: option: add Quectel EM05G variant (0x030e) + USB: serial: option: add FOXCONN T99W368/T99W373 product + ALSA: usb-audio: Fix init call orders for UAC1 + usb: dwc3: meson-g12a: do post init to fix broken usb after resumption + usb: chipidea: imx: improve logic if samsung,picophy-* parameter is 0 + HID: wacom: remove the battery when the EKR is off + staging: rtl8712: fix race condition + Bluetooth: btsdio: fi
[Kernel-packages] [Bug 2039576] Re: Enabling CONFIG_CRYPTO_STATS causes significant fscrypt performance degradation
apport information ** Tags added: apport-collected jammy uec-images ** Description changed: CONFIG_CRYPTO_STATS is enabled in Jammy 5.15.0-xx as well as 6.2.0-xx kernel by default. # uname -r 5.15.0-69-generic root@r100:~# grep CONFIG_CRYPTO_STATS /boot/config-5.15.0-69-generic CONFIG_CRYPTO_STATS=y However, that CONFIG_CRYPTO_STATS makes big negative performance impacts. Lustre (http://www.lustre.com Open source parallel filesystem) supports client encryption based on fscrypt. I ran some benchmarks of Lustre client encryption on Lustre client with Ubuntu 6.2.0-34-generic kernel below. 1 x client(2 x Gold 6438Y+, 512GB RAM, 2 x HDR200) Ubuntu22.04 (6.2.0-34-generic) # fio -name=iotest-w -ioengine=sync -rw=write -blocksize=16m -iodepth=1 -direct=1 -fallocate=none -size=200g -numjobs=128 -group_reporting -directory=/lustre/encrypted -create_serialize=0 -fiename_format='f.$jobnum.$filenum' -scramble_buffers=0 -runtime=60 6.2.0-34-generic, no encryption 48.5GB/s 6.2.0-34-generic, encryption 21.7GB/s 6.2.0-34-generic-noCryptStats, encryption 48.2GB/s When Lustre client encryption enabled, there were 65% performance degradations compared to non encryption's performance. (21.7GB/s vs 48.5GB/s) I also tested on 6.2.0-34-generic-noCryptStats which I built custom 6.2.0-34-generic kernel with disabling CONFIG_CRYPTO_STATS. The result was pretty good. The performance did boost and it was almost same speed against non encryption case. (48.2GB/s vs 48.5GB/s) I also found same fscrypt performance problem reported in Ceph with RHEL kernel below. https://lists.ceph.io/hyperkitty/list/ceph-us...@ceph.io/thread/44GMO5UGOXDZKFSOQMCPPHYTREUEA3ZI/ Eventually, Redhat disabled CONFIG_CRYPTO_STATS in latest RHEL9 kernel https://gitlab.com/redhat/centos-stream/src/kernel/centos-stream-9/-/merge_requests/2947 Kernel config option CONFIG_CRYPTO_STATS should be disabled until it is enhanced (BZ#2231850) - https://access.redhat.com/errata/RHSA-2023:5069 - I would disable CONFIG_CRYPTO_STATS in all Jammy kernels until proper - fixes and new solution is available in upstream kernel. + I would disable CONFIG_CRYPTO_STATS in all Jammy kernels until proper fixes and new solution is available in upstream kernel. + --- + ProblemType: Bug + AlsaDevices: + total 0 + crw-rw 1 root audio 116, 1 Oct 17 21:41 seq + crw-rw 1 root audio 116, 33 Oct 17 21:41 timer + AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' + ApportVersion: 2.20.11-0ubuntu82.4 + Architecture: amd64 + ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' + AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: + CRDA: N/A + CasperMD5CheckResult: unknown + DistroRelease: Ubuntu 22.04 + IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' + Lsusb: + Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + Lsusb-t: + /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/10p, 1M + /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M + MachineType: Giga Computing H263-S63-AAN1-000 + Package: linux (not installed) + PciMultimedia: + + ProcEnviron: + LC_CTYPE=C.UTF-8 + TERM=vt100 + PATH=(custom, no user) + LANG=C.UTF-8 + SHELL=/bin/bash + ProcFB: 0 astdrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-34-generic root=UUID=b48b34d5-f2cf-444d-b376-0ffc987891c1 ro + ProcVersionSignature: Ubuntu 6.2.0-34.34~22.04.1-generic 6.2.16 + RelatedPackageVersions: + linux-restricted-modules-6.2.0-34-generic N/A + linux-backports-modules-6.2.0-34-generic N/A + linux-firmware20220329.git681281e4-0ubuntu3.19 + RfKill: Error: [Errno 2] No such file or directory: 'rfkill' + Tags: jammy uec-images + Uname: Linux 6.2.0-34-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: N/A + _MarkForUpload: True + dmi.bios.date: 08/09/2023 + dmi.bios.release: 5.31 + dmi.bios.vendor: GIGABYTE + dmi.bios.version: F20 + dmi.board.asset.tag: 01234567890123456789AB + dmi.board.name: MS63-HD1-000 + dmi.board.vendor: Giga Computing + dmi.board.version: 01000100 + dmi.chassis.asset.tag: 01234567890123456789AB + dmi.chassis.type: 23 + dmi.chassis.vendor: Giga Computing + dmi.chassis.version: 01234567 + dmi.modalias: dmi:bvnGIGABYTE:bvrF20:bd08/09/2023:br5.31:svnGigaComputing:pnH263-S63-AAN1-000:pvr9NH263S63DR000AAN1*:rvnGigaComputing:rnMS63-HD1-000:rvr01000100:cvnGigaComputing:ct23:cvr01234567:sku01234567890123456789AB: + dmi.product.family: Server + dmi.product.name: H263-S63-AAN1-000 + dmi.product.sku: 01234567890123456789AB + dmi.product.version: 9NH263S63DR000AAN1* + dmi.sys.vendor: Giga Computing ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/2039576/+attachment/5710490/+files/Cur
[Kernel-packages] [Bug 2039576] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/2039576/+attachment/5710491/+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/2039576 Title: Enabling CONFIG_CRYPTO_STATS causes significant fscrypt performance degradation Status in linux package in Ubuntu: Confirmed Bug description: CONFIG_CRYPTO_STATS is enabled in Jammy 5.15.0-xx as well as 6.2.0-xx kernel by default. # uname -r 5.15.0-69-generic root@r100:~# grep CONFIG_CRYPTO_STATS /boot/config-5.15.0-69-generic CONFIG_CRYPTO_STATS=y However, that CONFIG_CRYPTO_STATS makes big negative performance impacts. Lustre (http://www.lustre.com Open source parallel filesystem) supports client encryption based on fscrypt. I ran some benchmarks of Lustre client encryption on Lustre client with Ubuntu 6.2.0-34-generic kernel below. 1 x client(2 x Gold 6438Y+, 512GB RAM, 2 x HDR200) Ubuntu22.04 (6.2.0-34-generic) # fio -name=iotest-w -ioengine=sync -rw=write -blocksize=16m -iodepth=1 -direct=1 -fallocate=none -size=200g -numjobs=128 -group_reporting -directory=/lustre/encrypted -create_serialize=0 -fiename_format='f.$jobnum.$filenum' -scramble_buffers=0 -runtime=60 6.2.0-34-generic, no encryption 48.5GB/s 6.2.0-34-generic, encryption 21.7GB/s 6.2.0-34-generic-noCryptStats, encryption 48.2GB/s When Lustre client encryption enabled, there were 65% performance degradations compared to non encryption's performance. (21.7GB/s vs 48.5GB/s) I also tested on 6.2.0-34-generic-noCryptStats which I built custom 6.2.0-34-generic kernel with disabling CONFIG_CRYPTO_STATS. The result was pretty good. The performance did boost and it was almost same speed against non encryption case. (48.2GB/s vs 48.5GB/s) I also found same fscrypt performance problem reported in Ceph with RHEL kernel below. https://lists.ceph.io/hyperkitty/list/ceph-us...@ceph.io/thread/44GMO5UGOXDZKFSOQMCPPHYTREUEA3ZI/ Eventually, Redhat disabled CONFIG_CRYPTO_STATS in latest RHEL9 kernel https://gitlab.com/redhat/centos-stream/src/kernel/centos-stream-9/-/merge_requests/2947 Kernel config option CONFIG_CRYPTO_STATS should be disabled until it is enhanced (BZ#2231850) - https://access.redhat.com/errata/RHSA-2023:5069 I would disable CONFIG_CRYPTO_STATS in all Jammy kernels until proper fixes and new solution is available in upstream kernel. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Oct 17 21:41 seq crw-rw 1 root audio 116, 33 Oct 17 21:41 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: unknown DistroRelease: Ubuntu 22.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/10p, 1M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M MachineType: Giga Computing H263-S63-AAN1-000 Package: linux (not installed) PciMultimedia: ProcEnviron: LC_CTYPE=C.UTF-8 TERM=vt100 PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-34-generic root=UUID=b48b34d5-f2cf-444d-b376-0ffc987891c1 ro ProcVersionSignature: Ubuntu 6.2.0-34.34~22.04.1-generic 6.2.16 RelatedPackageVersions: linux-restricted-modules-6.2.0-34-generic N/A linux-backports-modules-6.2.0-34-generic N/A linux-firmware20220329.git681281e4-0ubuntu3.19 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: jammy uec-images Uname: Linux 6.2.0-34-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 08/09/2023 dmi.bios.release: 5.31 dmi.bios.vendor: GIGABYTE dmi.bios.version: F20 dmi.board.asset.tag: 01234567890123456789AB dmi.board.name: MS63-HD1-000 dmi.board.vendor: Giga Computing dmi.board.version: 01000100 dmi.chassis.asset.tag: 01234567890123456789AB dmi.chassis.type: 23 dmi.chassis.vendor: Giga Computing dmi.chassis.version: 01234567 dmi.modalias: dmi:bvnGIGABYTE:bvrF20:bd08/09/2023:br5.31:svnGigaComputing:pnH263-S63-AAN1-000:pvr9NH263S63DR000AAN1*:rvnGigaComputing:rnMS63-HD1-000:rvr01000100:cvnGigaComputing:ct23:cvr01234567:sku01234567890123456789AB: dmi.product.family: Server dmi.product.name: H263-S63-AAN1-000 dmi.product.sku: 0
[Kernel-packages] [Bug 2039576] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/2039576/+attachment/5710493/+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/2039576 Title: Enabling CONFIG_CRYPTO_STATS causes significant fscrypt performance degradation Status in linux package in Ubuntu: Confirmed Bug description: CONFIG_CRYPTO_STATS is enabled in Jammy 5.15.0-xx as well as 6.2.0-xx kernel by default. # uname -r 5.15.0-69-generic root@r100:~# grep CONFIG_CRYPTO_STATS /boot/config-5.15.0-69-generic CONFIG_CRYPTO_STATS=y However, that CONFIG_CRYPTO_STATS makes big negative performance impacts. Lustre (http://www.lustre.com Open source parallel filesystem) supports client encryption based on fscrypt. I ran some benchmarks of Lustre client encryption on Lustre client with Ubuntu 6.2.0-34-generic kernel below. 1 x client(2 x Gold 6438Y+, 512GB RAM, 2 x HDR200) Ubuntu22.04 (6.2.0-34-generic) # fio -name=iotest-w -ioengine=sync -rw=write -blocksize=16m -iodepth=1 -direct=1 -fallocate=none -size=200g -numjobs=128 -group_reporting -directory=/lustre/encrypted -create_serialize=0 -fiename_format='f.$jobnum.$filenum' -scramble_buffers=0 -runtime=60 6.2.0-34-generic, no encryption 48.5GB/s 6.2.0-34-generic, encryption 21.7GB/s 6.2.0-34-generic-noCryptStats, encryption 48.2GB/s When Lustre client encryption enabled, there were 65% performance degradations compared to non encryption's performance. (21.7GB/s vs 48.5GB/s) I also tested on 6.2.0-34-generic-noCryptStats which I built custom 6.2.0-34-generic kernel with disabling CONFIG_CRYPTO_STATS. The result was pretty good. The performance did boost and it was almost same speed against non encryption case. (48.2GB/s vs 48.5GB/s) I also found same fscrypt performance problem reported in Ceph with RHEL kernel below. https://lists.ceph.io/hyperkitty/list/ceph-us...@ceph.io/thread/44GMO5UGOXDZKFSOQMCPPHYTREUEA3ZI/ Eventually, Redhat disabled CONFIG_CRYPTO_STATS in latest RHEL9 kernel https://gitlab.com/redhat/centos-stream/src/kernel/centos-stream-9/-/merge_requests/2947 Kernel config option CONFIG_CRYPTO_STATS should be disabled until it is enhanced (BZ#2231850) - https://access.redhat.com/errata/RHSA-2023:5069 I would disable CONFIG_CRYPTO_STATS in all Jammy kernels until proper fixes and new solution is available in upstream kernel. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Oct 17 21:41 seq crw-rw 1 root audio 116, 33 Oct 17 21:41 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: unknown DistroRelease: Ubuntu 22.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/10p, 1M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M MachineType: Giga Computing H263-S63-AAN1-000 Package: linux (not installed) PciMultimedia: ProcEnviron: LC_CTYPE=C.UTF-8 TERM=vt100 PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-34-generic root=UUID=b48b34d5-f2cf-444d-b376-0ffc987891c1 ro ProcVersionSignature: Ubuntu 6.2.0-34.34~22.04.1-generic 6.2.16 RelatedPackageVersions: linux-restricted-modules-6.2.0-34-generic N/A linux-backports-modules-6.2.0-34-generic N/A linux-firmware20220329.git681281e4-0ubuntu3.19 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: jammy uec-images Uname: Linux 6.2.0-34-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 08/09/2023 dmi.bios.release: 5.31 dmi.bios.vendor: GIGABYTE dmi.bios.version: F20 dmi.board.asset.tag: 01234567890123456789AB dmi.board.name: MS63-HD1-000 dmi.board.vendor: Giga Computing dmi.board.version: 01000100 dmi.chassis.asset.tag: 01234567890123456789AB dmi.chassis.type: 23 dmi.chassis.vendor: Giga Computing dmi.chassis.version: 01234567 dmi.modalias: dmi:bvnGIGABYTE:bvrF20:bd08/09/2023:br5.31:svnGigaComputing:pnH263-S63-AAN1-000:pvr9NH263S63DR000AAN1*:rvnGigaComputing:rnMS63-HD1-000:rvr01000100:cvnGigaComputing:ct23:cvr01234567:sku01234567890123456789AB: dmi.product.family: Server dmi.product.name: H263-S63-AAN1-000 dmi.product.s
[Kernel-packages] [Bug 2039576] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/2039576/+attachment/5710494/+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/2039576 Title: Enabling CONFIG_CRYPTO_STATS causes significant fscrypt performance degradation Status in linux package in Ubuntu: Confirmed Bug description: CONFIG_CRYPTO_STATS is enabled in Jammy 5.15.0-xx as well as 6.2.0-xx kernel by default. # uname -r 5.15.0-69-generic root@r100:~# grep CONFIG_CRYPTO_STATS /boot/config-5.15.0-69-generic CONFIG_CRYPTO_STATS=y However, that CONFIG_CRYPTO_STATS makes big negative performance impacts. Lustre (http://www.lustre.com Open source parallel filesystem) supports client encryption based on fscrypt. I ran some benchmarks of Lustre client encryption on Lustre client with Ubuntu 6.2.0-34-generic kernel below. 1 x client(2 x Gold 6438Y+, 512GB RAM, 2 x HDR200) Ubuntu22.04 (6.2.0-34-generic) # fio -name=iotest-w -ioengine=sync -rw=write -blocksize=16m -iodepth=1 -direct=1 -fallocate=none -size=200g -numjobs=128 -group_reporting -directory=/lustre/encrypted -create_serialize=0 -fiename_format='f.$jobnum.$filenum' -scramble_buffers=0 -runtime=60 6.2.0-34-generic, no encryption 48.5GB/s 6.2.0-34-generic, encryption 21.7GB/s 6.2.0-34-generic-noCryptStats, encryption 48.2GB/s When Lustre client encryption enabled, there were 65% performance degradations compared to non encryption's performance. (21.7GB/s vs 48.5GB/s) I also tested on 6.2.0-34-generic-noCryptStats which I built custom 6.2.0-34-generic kernel with disabling CONFIG_CRYPTO_STATS. The result was pretty good. The performance did boost and it was almost same speed against non encryption case. (48.2GB/s vs 48.5GB/s) I also found same fscrypt performance problem reported in Ceph with RHEL kernel below. https://lists.ceph.io/hyperkitty/list/ceph-us...@ceph.io/thread/44GMO5UGOXDZKFSOQMCPPHYTREUEA3ZI/ Eventually, Redhat disabled CONFIG_CRYPTO_STATS in latest RHEL9 kernel https://gitlab.com/redhat/centos-stream/src/kernel/centos-stream-9/-/merge_requests/2947 Kernel config option CONFIG_CRYPTO_STATS should be disabled until it is enhanced (BZ#2231850) - https://access.redhat.com/errata/RHSA-2023:5069 I would disable CONFIG_CRYPTO_STATS in all Jammy kernels until proper fixes and new solution is available in upstream kernel. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Oct 17 21:41 seq crw-rw 1 root audio 116, 33 Oct 17 21:41 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: unknown DistroRelease: Ubuntu 22.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/10p, 1M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M MachineType: Giga Computing H263-S63-AAN1-000 Package: linux (not installed) PciMultimedia: ProcEnviron: LC_CTYPE=C.UTF-8 TERM=vt100 PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-34-generic root=UUID=b48b34d5-f2cf-444d-b376-0ffc987891c1 ro ProcVersionSignature: Ubuntu 6.2.0-34.34~22.04.1-generic 6.2.16 RelatedPackageVersions: linux-restricted-modules-6.2.0-34-generic N/A linux-backports-modules-6.2.0-34-generic N/A linux-firmware20220329.git681281e4-0ubuntu3.19 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: jammy uec-images Uname: Linux 6.2.0-34-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 08/09/2023 dmi.bios.release: 5.31 dmi.bios.vendor: GIGABYTE dmi.bios.version: F20 dmi.board.asset.tag: 01234567890123456789AB dmi.board.name: MS63-HD1-000 dmi.board.vendor: Giga Computing dmi.board.version: 01000100 dmi.chassis.asset.tag: 01234567890123456789AB dmi.chassis.type: 23 dmi.chassis.vendor: Giga Computing dmi.chassis.version: 01234567 dmi.modalias: dmi:bvnGIGABYTE:bvrF20:bd08/09/2023:br5.31:svnGigaComputing:pnH263-S63-AAN1-000:pvr9NH263S63DR000AAN1*:rvnGigaComputing:rnMS63-HD1-000:rvr01000100:cvnGigaComputing:ct23:cvr01234567:sku01234567890123456789AB: dmi.product.family: Server dmi.product.name: H263-S63-AAN1-000 dmi.p
[Kernel-packages] [Bug 2039576] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/2039576/+attachment/5710495/+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/2039576 Title: Enabling CONFIG_CRYPTO_STATS causes significant fscrypt performance degradation Status in linux package in Ubuntu: Confirmed Bug description: CONFIG_CRYPTO_STATS is enabled in Jammy 5.15.0-xx as well as 6.2.0-xx kernel by default. # uname -r 5.15.0-69-generic root@r100:~# grep CONFIG_CRYPTO_STATS /boot/config-5.15.0-69-generic CONFIG_CRYPTO_STATS=y However, that CONFIG_CRYPTO_STATS makes big negative performance impacts. Lustre (http://www.lustre.com Open source parallel filesystem) supports client encryption based on fscrypt. I ran some benchmarks of Lustre client encryption on Lustre client with Ubuntu 6.2.0-34-generic kernel below. 1 x client(2 x Gold 6438Y+, 512GB RAM, 2 x HDR200) Ubuntu22.04 (6.2.0-34-generic) # fio -name=iotest-w -ioengine=sync -rw=write -blocksize=16m -iodepth=1 -direct=1 -fallocate=none -size=200g -numjobs=128 -group_reporting -directory=/lustre/encrypted -create_serialize=0 -fiename_format='f.$jobnum.$filenum' -scramble_buffers=0 -runtime=60 6.2.0-34-generic, no encryption 48.5GB/s 6.2.0-34-generic, encryption 21.7GB/s 6.2.0-34-generic-noCryptStats, encryption 48.2GB/s When Lustre client encryption enabled, there were 65% performance degradations compared to non encryption's performance. (21.7GB/s vs 48.5GB/s) I also tested on 6.2.0-34-generic-noCryptStats which I built custom 6.2.0-34-generic kernel with disabling CONFIG_CRYPTO_STATS. The result was pretty good. The performance did boost and it was almost same speed against non encryption case. (48.2GB/s vs 48.5GB/s) I also found same fscrypt performance problem reported in Ceph with RHEL kernel below. https://lists.ceph.io/hyperkitty/list/ceph-us...@ceph.io/thread/44GMO5UGOXDZKFSOQMCPPHYTREUEA3ZI/ Eventually, Redhat disabled CONFIG_CRYPTO_STATS in latest RHEL9 kernel https://gitlab.com/redhat/centos-stream/src/kernel/centos-stream-9/-/merge_requests/2947 Kernel config option CONFIG_CRYPTO_STATS should be disabled until it is enhanced (BZ#2231850) - https://access.redhat.com/errata/RHSA-2023:5069 I would disable CONFIG_CRYPTO_STATS in all Jammy kernels until proper fixes and new solution is available in upstream kernel. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Oct 17 21:41 seq crw-rw 1 root audio 116, 33 Oct 17 21:41 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: unknown DistroRelease: Ubuntu 22.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/10p, 1M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M MachineType: Giga Computing H263-S63-AAN1-000 Package: linux (not installed) PciMultimedia: ProcEnviron: LC_CTYPE=C.UTF-8 TERM=vt100 PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-34-generic root=UUID=b48b34d5-f2cf-444d-b376-0ffc987891c1 ro ProcVersionSignature: Ubuntu 6.2.0-34.34~22.04.1-generic 6.2.16 RelatedPackageVersions: linux-restricted-modules-6.2.0-34-generic N/A linux-backports-modules-6.2.0-34-generic N/A linux-firmware20220329.git681281e4-0ubuntu3.19 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: jammy uec-images Uname: Linux 6.2.0-34-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 08/09/2023 dmi.bios.release: 5.31 dmi.bios.vendor: GIGABYTE dmi.bios.version: F20 dmi.board.asset.tag: 01234567890123456789AB dmi.board.name: MS63-HD1-000 dmi.board.vendor: Giga Computing dmi.board.version: 01000100 dmi.chassis.asset.tag: 01234567890123456789AB dmi.chassis.type: 23 dmi.chassis.vendor: Giga Computing dmi.chassis.version: 01234567 dmi.modalias: dmi:bvnGIGABYTE:bvrF20:bd08/09/2023:br5.31:svnGigaComputing:pnH263-S63-AAN1-000:pvr9NH263S63DR000AAN1*:rvnGigaComputing:rnMS63-HD1-000:rvr01000100:cvnGigaComputing:ct23:cvr01234567:sku01234567890123456789AB: dmi.product.family: Server dmi.product.name: H263-S63-AA
[Kernel-packages] [Bug 2039576] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/2039576/+attachment/5710496/+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/2039576 Title: Enabling CONFIG_CRYPTO_STATS causes significant fscrypt performance degradation Status in linux package in Ubuntu: Confirmed Bug description: CONFIG_CRYPTO_STATS is enabled in Jammy 5.15.0-xx as well as 6.2.0-xx kernel by default. # uname -r 5.15.0-69-generic root@r100:~# grep CONFIG_CRYPTO_STATS /boot/config-5.15.0-69-generic CONFIG_CRYPTO_STATS=y However, that CONFIG_CRYPTO_STATS makes big negative performance impacts. Lustre (http://www.lustre.com Open source parallel filesystem) supports client encryption based on fscrypt. I ran some benchmarks of Lustre client encryption on Lustre client with Ubuntu 6.2.0-34-generic kernel below. 1 x client(2 x Gold 6438Y+, 512GB RAM, 2 x HDR200) Ubuntu22.04 (6.2.0-34-generic) # fio -name=iotest-w -ioengine=sync -rw=write -blocksize=16m -iodepth=1 -direct=1 -fallocate=none -size=200g -numjobs=128 -group_reporting -directory=/lustre/encrypted -create_serialize=0 -fiename_format='f.$jobnum.$filenum' -scramble_buffers=0 -runtime=60 6.2.0-34-generic, no encryption 48.5GB/s 6.2.0-34-generic, encryption 21.7GB/s 6.2.0-34-generic-noCryptStats, encryption 48.2GB/s When Lustre client encryption enabled, there were 65% performance degradations compared to non encryption's performance. (21.7GB/s vs 48.5GB/s) I also tested on 6.2.0-34-generic-noCryptStats which I built custom 6.2.0-34-generic kernel with disabling CONFIG_CRYPTO_STATS. The result was pretty good. The performance did boost and it was almost same speed against non encryption case. (48.2GB/s vs 48.5GB/s) I also found same fscrypt performance problem reported in Ceph with RHEL kernel below. https://lists.ceph.io/hyperkitty/list/ceph-us...@ceph.io/thread/44GMO5UGOXDZKFSOQMCPPHYTREUEA3ZI/ Eventually, Redhat disabled CONFIG_CRYPTO_STATS in latest RHEL9 kernel https://gitlab.com/redhat/centos-stream/src/kernel/centos-stream-9/-/merge_requests/2947 Kernel config option CONFIG_CRYPTO_STATS should be disabled until it is enhanced (BZ#2231850) - https://access.redhat.com/errata/RHSA-2023:5069 I would disable CONFIG_CRYPTO_STATS in all Jammy kernels until proper fixes and new solution is available in upstream kernel. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Oct 17 21:41 seq crw-rw 1 root audio 116, 33 Oct 17 21:41 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: unknown DistroRelease: Ubuntu 22.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/10p, 1M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M MachineType: Giga Computing H263-S63-AAN1-000 Package: linux (not installed) PciMultimedia: ProcEnviron: LC_CTYPE=C.UTF-8 TERM=vt100 PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-34-generic root=UUID=b48b34d5-f2cf-444d-b376-0ffc987891c1 ro ProcVersionSignature: Ubuntu 6.2.0-34.34~22.04.1-generic 6.2.16 RelatedPackageVersions: linux-restricted-modules-6.2.0-34-generic N/A linux-backports-modules-6.2.0-34-generic N/A linux-firmware20220329.git681281e4-0ubuntu3.19 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: jammy uec-images Uname: Linux 6.2.0-34-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 08/09/2023 dmi.bios.release: 5.31 dmi.bios.vendor: GIGABYTE dmi.bios.version: F20 dmi.board.asset.tag: 01234567890123456789AB dmi.board.name: MS63-HD1-000 dmi.board.vendor: Giga Computing dmi.board.version: 01000100 dmi.chassis.asset.tag: 01234567890123456789AB dmi.chassis.type: 23 dmi.chassis.vendor: Giga Computing dmi.chassis.version: 01234567 dmi.modalias: dmi:bvnGIGABYTE:bvrF20:bd08/09/2023:br5.31:svnGigaComputing:pnH263-S63-AAN1-000:pvr9NH263S63DR000AAN1*:rvnGigaComputing:rnMS63-HD1-000:rvr01000100:cvnGigaComputing:ct23:cvr01234567:sku01234567890123456789AB: dmi.product.family: Server dmi.product.name: H263-S63-AAN1-000
[Kernel-packages] [Bug 2039576] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/2039576/+attachment/5710492/+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/2039576 Title: Enabling CONFIG_CRYPTO_STATS causes significant fscrypt performance degradation Status in linux package in Ubuntu: Confirmed Bug description: CONFIG_CRYPTO_STATS is enabled in Jammy 5.15.0-xx as well as 6.2.0-xx kernel by default. # uname -r 5.15.0-69-generic root@r100:~# grep CONFIG_CRYPTO_STATS /boot/config-5.15.0-69-generic CONFIG_CRYPTO_STATS=y However, that CONFIG_CRYPTO_STATS makes big negative performance impacts. Lustre (http://www.lustre.com Open source parallel filesystem) supports client encryption based on fscrypt. I ran some benchmarks of Lustre client encryption on Lustre client with Ubuntu 6.2.0-34-generic kernel below. 1 x client(2 x Gold 6438Y+, 512GB RAM, 2 x HDR200) Ubuntu22.04 (6.2.0-34-generic) # fio -name=iotest-w -ioengine=sync -rw=write -blocksize=16m -iodepth=1 -direct=1 -fallocate=none -size=200g -numjobs=128 -group_reporting -directory=/lustre/encrypted -create_serialize=0 -fiename_format='f.$jobnum.$filenum' -scramble_buffers=0 -runtime=60 6.2.0-34-generic, no encryption 48.5GB/s 6.2.0-34-generic, encryption 21.7GB/s 6.2.0-34-generic-noCryptStats, encryption 48.2GB/s When Lustre client encryption enabled, there were 65% performance degradations compared to non encryption's performance. (21.7GB/s vs 48.5GB/s) I also tested on 6.2.0-34-generic-noCryptStats which I built custom 6.2.0-34-generic kernel with disabling CONFIG_CRYPTO_STATS. The result was pretty good. The performance did boost and it was almost same speed against non encryption case. (48.2GB/s vs 48.5GB/s) I also found same fscrypt performance problem reported in Ceph with RHEL kernel below. https://lists.ceph.io/hyperkitty/list/ceph-us...@ceph.io/thread/44GMO5UGOXDZKFSOQMCPPHYTREUEA3ZI/ Eventually, Redhat disabled CONFIG_CRYPTO_STATS in latest RHEL9 kernel https://gitlab.com/redhat/centos-stream/src/kernel/centos-stream-9/-/merge_requests/2947 Kernel config option CONFIG_CRYPTO_STATS should be disabled until it is enhanced (BZ#2231850) - https://access.redhat.com/errata/RHSA-2023:5069 I would disable CONFIG_CRYPTO_STATS in all Jammy kernels until proper fixes and new solution is available in upstream kernel. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Oct 17 21:41 seq crw-rw 1 root audio 116, 33 Oct 17 21:41 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: unknown DistroRelease: Ubuntu 22.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/10p, 1M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M MachineType: Giga Computing H263-S63-AAN1-000 Package: linux (not installed) PciMultimedia: ProcEnviron: LC_CTYPE=C.UTF-8 TERM=vt100 PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-34-generic root=UUID=b48b34d5-f2cf-444d-b376-0ffc987891c1 ro ProcVersionSignature: Ubuntu 6.2.0-34.34~22.04.1-generic 6.2.16 RelatedPackageVersions: linux-restricted-modules-6.2.0-34-generic N/A linux-backports-modules-6.2.0-34-generic N/A linux-firmware20220329.git681281e4-0ubuntu3.19 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: jammy uec-images Uname: Linux 6.2.0-34-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 08/09/2023 dmi.bios.release: 5.31 dmi.bios.vendor: GIGABYTE dmi.bios.version: F20 dmi.board.asset.tag: 01234567890123456789AB dmi.board.name: MS63-HD1-000 dmi.board.vendor: Giga Computing dmi.board.version: 01000100 dmi.chassis.asset.tag: 01234567890123456789AB dmi.chassis.type: 23 dmi.chassis.vendor: Giga Computing dmi.chassis.version: 01234567 dmi.modalias: dmi:bvnGIGABYTE:bvrF20:bd08/09/2023:br5.31:svnGigaComputing:pnH263-S63-AAN1-000:pvr9NH263S63DR000AAN1*:rvnGigaComputing:rnMS63-HD1-000:rvr01000100:cvnGigaComputing:ct23:cvr01234567:sku01234567890123456789AB: dmi.product.family: Server dmi.product.name: H263-S63-AAN1-000 dmi.product
[Kernel-packages] [Bug 2039576] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/2039576/+attachment/5710497/+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/2039576 Title: Enabling CONFIG_CRYPTO_STATS causes significant fscrypt performance degradation Status in linux package in Ubuntu: Confirmed Bug description: CONFIG_CRYPTO_STATS is enabled in Jammy 5.15.0-xx as well as 6.2.0-xx kernel by default. # uname -r 5.15.0-69-generic root@r100:~# grep CONFIG_CRYPTO_STATS /boot/config-5.15.0-69-generic CONFIG_CRYPTO_STATS=y However, that CONFIG_CRYPTO_STATS makes big negative performance impacts. Lustre (http://www.lustre.com Open source parallel filesystem) supports client encryption based on fscrypt. I ran some benchmarks of Lustre client encryption on Lustre client with Ubuntu 6.2.0-34-generic kernel below. 1 x client(2 x Gold 6438Y+, 512GB RAM, 2 x HDR200) Ubuntu22.04 (6.2.0-34-generic) # fio -name=iotest-w -ioengine=sync -rw=write -blocksize=16m -iodepth=1 -direct=1 -fallocate=none -size=200g -numjobs=128 -group_reporting -directory=/lustre/encrypted -create_serialize=0 -fiename_format='f.$jobnum.$filenum' -scramble_buffers=0 -runtime=60 6.2.0-34-generic, no encryption 48.5GB/s 6.2.0-34-generic, encryption 21.7GB/s 6.2.0-34-generic-noCryptStats, encryption 48.2GB/s When Lustre client encryption enabled, there were 65% performance degradations compared to non encryption's performance. (21.7GB/s vs 48.5GB/s) I also tested on 6.2.0-34-generic-noCryptStats which I built custom 6.2.0-34-generic kernel with disabling CONFIG_CRYPTO_STATS. The result was pretty good. The performance did boost and it was almost same speed against non encryption case. (48.2GB/s vs 48.5GB/s) I also found same fscrypt performance problem reported in Ceph with RHEL kernel below. https://lists.ceph.io/hyperkitty/list/ceph-us...@ceph.io/thread/44GMO5UGOXDZKFSOQMCPPHYTREUEA3ZI/ Eventually, Redhat disabled CONFIG_CRYPTO_STATS in latest RHEL9 kernel https://gitlab.com/redhat/centos-stream/src/kernel/centos-stream-9/-/merge_requests/2947 Kernel config option CONFIG_CRYPTO_STATS should be disabled until it is enhanced (BZ#2231850) - https://access.redhat.com/errata/RHSA-2023:5069 I would disable CONFIG_CRYPTO_STATS in all Jammy kernels until proper fixes and new solution is available in upstream kernel. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Oct 17 21:41 seq crw-rw 1 root audio 116, 33 Oct 17 21:41 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: unknown DistroRelease: Ubuntu 22.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/10p, 1M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M MachineType: Giga Computing H263-S63-AAN1-000 Package: linux (not installed) PciMultimedia: ProcEnviron: LC_CTYPE=C.UTF-8 TERM=vt100 PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-34-generic root=UUID=b48b34d5-f2cf-444d-b376-0ffc987891c1 ro ProcVersionSignature: Ubuntu 6.2.0-34.34~22.04.1-generic 6.2.16 RelatedPackageVersions: linux-restricted-modules-6.2.0-34-generic N/A linux-backports-modules-6.2.0-34-generic N/A linux-firmware20220329.git681281e4-0ubuntu3.19 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: jammy uec-images Uname: Linux 6.2.0-34-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 08/09/2023 dmi.bios.release: 5.31 dmi.bios.vendor: GIGABYTE dmi.bios.version: F20 dmi.board.asset.tag: 01234567890123456789AB dmi.board.name: MS63-HD1-000 dmi.board.vendor: Giga Computing dmi.board.version: 01000100 dmi.chassis.asset.tag: 01234567890123456789AB dmi.chassis.type: 23 dmi.chassis.vendor: Giga Computing dmi.chassis.version: 01234567 dmi.modalias: dmi:bvnGIGABYTE:bvrF20:bd08/09/2023:br5.31:svnGigaComputing:pnH263-S63-AAN1-000:pvr9NH263S63DR000AAN1*:rvnGigaComputing:rnMS63-HD1-000:rvr01000100:cvnGigaComputing:ct23:cvr01234567:sku01234567890123456789AB: dmi.product.family: Server dmi.product.name: H263-S63-AAN1-000 dmi.p
[Kernel-packages] [Bug 2039576] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/2039576/+attachment/5710498/+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/2039576 Title: Enabling CONFIG_CRYPTO_STATS causes significant fscrypt performance degradation Status in linux package in Ubuntu: Confirmed Bug description: CONFIG_CRYPTO_STATS is enabled in Jammy 5.15.0-xx as well as 6.2.0-xx kernel by default. # uname -r 5.15.0-69-generic root@r100:~# grep CONFIG_CRYPTO_STATS /boot/config-5.15.0-69-generic CONFIG_CRYPTO_STATS=y However, that CONFIG_CRYPTO_STATS makes big negative performance impacts. Lustre (http://www.lustre.com Open source parallel filesystem) supports client encryption based on fscrypt. I ran some benchmarks of Lustre client encryption on Lustre client with Ubuntu 6.2.0-34-generic kernel below. 1 x client(2 x Gold 6438Y+, 512GB RAM, 2 x HDR200) Ubuntu22.04 (6.2.0-34-generic) # fio -name=iotest-w -ioengine=sync -rw=write -blocksize=16m -iodepth=1 -direct=1 -fallocate=none -size=200g -numjobs=128 -group_reporting -directory=/lustre/encrypted -create_serialize=0 -fiename_format='f.$jobnum.$filenum' -scramble_buffers=0 -runtime=60 6.2.0-34-generic, no encryption 48.5GB/s 6.2.0-34-generic, encryption 21.7GB/s 6.2.0-34-generic-noCryptStats, encryption 48.2GB/s When Lustre client encryption enabled, there were 65% performance degradations compared to non encryption's performance. (21.7GB/s vs 48.5GB/s) I also tested on 6.2.0-34-generic-noCryptStats which I built custom 6.2.0-34-generic kernel with disabling CONFIG_CRYPTO_STATS. The result was pretty good. The performance did boost and it was almost same speed against non encryption case. (48.2GB/s vs 48.5GB/s) I also found same fscrypt performance problem reported in Ceph with RHEL kernel below. https://lists.ceph.io/hyperkitty/list/ceph-us...@ceph.io/thread/44GMO5UGOXDZKFSOQMCPPHYTREUEA3ZI/ Eventually, Redhat disabled CONFIG_CRYPTO_STATS in latest RHEL9 kernel https://gitlab.com/redhat/centos-stream/src/kernel/centos-stream-9/-/merge_requests/2947 Kernel config option CONFIG_CRYPTO_STATS should be disabled until it is enhanced (BZ#2231850) - https://access.redhat.com/errata/RHSA-2023:5069 I would disable CONFIG_CRYPTO_STATS in all Jammy kernels until proper fixes and new solution is available in upstream kernel. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Oct 17 21:41 seq crw-rw 1 root audio 116, 33 Oct 17 21:41 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: unknown DistroRelease: Ubuntu 22.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/10p, 1M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M MachineType: Giga Computing H263-S63-AAN1-000 Package: linux (not installed) PciMultimedia: ProcEnviron: LC_CTYPE=C.UTF-8 TERM=vt100 PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-34-generic root=UUID=b48b34d5-f2cf-444d-b376-0ffc987891c1 ro ProcVersionSignature: Ubuntu 6.2.0-34.34~22.04.1-generic 6.2.16 RelatedPackageVersions: linux-restricted-modules-6.2.0-34-generic N/A linux-backports-modules-6.2.0-34-generic N/A linux-firmware20220329.git681281e4-0ubuntu3.19 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: jammy uec-images Uname: Linux 6.2.0-34-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 08/09/2023 dmi.bios.release: 5.31 dmi.bios.vendor: GIGABYTE dmi.bios.version: F20 dmi.board.asset.tag: 01234567890123456789AB dmi.board.name: MS63-HD1-000 dmi.board.vendor: Giga Computing dmi.board.version: 01000100 dmi.chassis.asset.tag: 01234567890123456789AB dmi.chassis.type: 23 dmi.chassis.vendor: Giga Computing dmi.chassis.version: 01234567 dmi.modalias: dmi:bvnGIGABYTE:bvrF20:bd08/09/2023:br5.31:svnGigaComputing:pnH263-S63-AAN1-000:pvr9NH263S63DR000AAN1*:rvnGigaComputing:rnMS63-HD1-000:rvr01000100:cvnGigaComputing:ct23:cvr01234567:sku01234567890123456789AB: dmi.product.family: Server dmi.product.name: H263-S63-AAN1-000 dmi.product.sku:
[Kernel-packages] [Bug 2039576] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/2039576/+attachment/5710499/+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/2039576 Title: Enabling CONFIG_CRYPTO_STATS causes significant fscrypt performance degradation Status in linux package in Ubuntu: Confirmed Bug description: CONFIG_CRYPTO_STATS is enabled in Jammy 5.15.0-xx as well as 6.2.0-xx kernel by default. # uname -r 5.15.0-69-generic root@r100:~# grep CONFIG_CRYPTO_STATS /boot/config-5.15.0-69-generic CONFIG_CRYPTO_STATS=y However, that CONFIG_CRYPTO_STATS makes big negative performance impacts. Lustre (http://www.lustre.com Open source parallel filesystem) supports client encryption based on fscrypt. I ran some benchmarks of Lustre client encryption on Lustre client with Ubuntu 6.2.0-34-generic kernel below. 1 x client(2 x Gold 6438Y+, 512GB RAM, 2 x HDR200) Ubuntu22.04 (6.2.0-34-generic) # fio -name=iotest-w -ioengine=sync -rw=write -blocksize=16m -iodepth=1 -direct=1 -fallocate=none -size=200g -numjobs=128 -group_reporting -directory=/lustre/encrypted -create_serialize=0 -fiename_format='f.$jobnum.$filenum' -scramble_buffers=0 -runtime=60 6.2.0-34-generic, no encryption 48.5GB/s 6.2.0-34-generic, encryption 21.7GB/s 6.2.0-34-generic-noCryptStats, encryption 48.2GB/s When Lustre client encryption enabled, there were 65% performance degradations compared to non encryption's performance. (21.7GB/s vs 48.5GB/s) I also tested on 6.2.0-34-generic-noCryptStats which I built custom 6.2.0-34-generic kernel with disabling CONFIG_CRYPTO_STATS. The result was pretty good. The performance did boost and it was almost same speed against non encryption case. (48.2GB/s vs 48.5GB/s) I also found same fscrypt performance problem reported in Ceph with RHEL kernel below. https://lists.ceph.io/hyperkitty/list/ceph-us...@ceph.io/thread/44GMO5UGOXDZKFSOQMCPPHYTREUEA3ZI/ Eventually, Redhat disabled CONFIG_CRYPTO_STATS in latest RHEL9 kernel https://gitlab.com/redhat/centos-stream/src/kernel/centos-stream-9/-/merge_requests/2947 Kernel config option CONFIG_CRYPTO_STATS should be disabled until it is enhanced (BZ#2231850) - https://access.redhat.com/errata/RHSA-2023:5069 I would disable CONFIG_CRYPTO_STATS in all Jammy kernels until proper fixes and new solution is available in upstream kernel. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Oct 17 21:41 seq crw-rw 1 root audio 116, 33 Oct 17 21:41 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: unknown DistroRelease: Ubuntu 22.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/10p, 1M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M MachineType: Giga Computing H263-S63-AAN1-000 Package: linux (not installed) PciMultimedia: ProcEnviron: LC_CTYPE=C.UTF-8 TERM=vt100 PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-34-generic root=UUID=b48b34d5-f2cf-444d-b376-0ffc987891c1 ro ProcVersionSignature: Ubuntu 6.2.0-34.34~22.04.1-generic 6.2.16 RelatedPackageVersions: linux-restricted-modules-6.2.0-34-generic N/A linux-backports-modules-6.2.0-34-generic N/A linux-firmware20220329.git681281e4-0ubuntu3.19 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: jammy uec-images Uname: Linux 6.2.0-34-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 08/09/2023 dmi.bios.release: 5.31 dmi.bios.vendor: GIGABYTE dmi.bios.version: F20 dmi.board.asset.tag: 01234567890123456789AB dmi.board.name: MS63-HD1-000 dmi.board.vendor: Giga Computing dmi.board.version: 01000100 dmi.chassis.asset.tag: 01234567890123456789AB dmi.chassis.type: 23 dmi.chassis.vendor: Giga Computing dmi.chassis.version: 01234567 dmi.modalias: dmi:bvnGIGABYTE:bvrF20:bd08/09/2023:br5.31:svnGigaComputing:pnH263-S63-AAN1-000:pvr9NH263S63DR000AAN1*:rvnGigaComputing:rnMS63-HD1-000:rvr01000100:cvnGigaComputing:ct23:cvr01234567:sku01234567890123456789AB: dmi.product.family: Server dmi.product.name: H263-S63-AAN1-000 dmi.pro
[Kernel-packages] [Bug 2039576] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/2039576/+attachment/5710500/+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/2039576 Title: Enabling CONFIG_CRYPTO_STATS causes significant fscrypt performance degradation Status in linux package in Ubuntu: Confirmed Bug description: CONFIG_CRYPTO_STATS is enabled in Jammy 5.15.0-xx as well as 6.2.0-xx kernel by default. # uname -r 5.15.0-69-generic root@r100:~# grep CONFIG_CRYPTO_STATS /boot/config-5.15.0-69-generic CONFIG_CRYPTO_STATS=y However, that CONFIG_CRYPTO_STATS makes big negative performance impacts. Lustre (http://www.lustre.com Open source parallel filesystem) supports client encryption based on fscrypt. I ran some benchmarks of Lustre client encryption on Lustre client with Ubuntu 6.2.0-34-generic kernel below. 1 x client(2 x Gold 6438Y+, 512GB RAM, 2 x HDR200) Ubuntu22.04 (6.2.0-34-generic) # fio -name=iotest-w -ioengine=sync -rw=write -blocksize=16m -iodepth=1 -direct=1 -fallocate=none -size=200g -numjobs=128 -group_reporting -directory=/lustre/encrypted -create_serialize=0 -fiename_format='f.$jobnum.$filenum' -scramble_buffers=0 -runtime=60 6.2.0-34-generic, no encryption 48.5GB/s 6.2.0-34-generic, encryption 21.7GB/s 6.2.0-34-generic-noCryptStats, encryption 48.2GB/s When Lustre client encryption enabled, there were 65% performance degradations compared to non encryption's performance. (21.7GB/s vs 48.5GB/s) I also tested on 6.2.0-34-generic-noCryptStats which I built custom 6.2.0-34-generic kernel with disabling CONFIG_CRYPTO_STATS. The result was pretty good. The performance did boost and it was almost same speed against non encryption case. (48.2GB/s vs 48.5GB/s) I also found same fscrypt performance problem reported in Ceph with RHEL kernel below. https://lists.ceph.io/hyperkitty/list/ceph-us...@ceph.io/thread/44GMO5UGOXDZKFSOQMCPPHYTREUEA3ZI/ Eventually, Redhat disabled CONFIG_CRYPTO_STATS in latest RHEL9 kernel https://gitlab.com/redhat/centos-stream/src/kernel/centos-stream-9/-/merge_requests/2947 Kernel config option CONFIG_CRYPTO_STATS should be disabled until it is enhanced (BZ#2231850) - https://access.redhat.com/errata/RHSA-2023:5069 I would disable CONFIG_CRYPTO_STATS in all Jammy kernels until proper fixes and new solution is available in upstream kernel. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Oct 17 21:41 seq crw-rw 1 root audio 116, 33 Oct 17 21:41 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: unknown DistroRelease: Ubuntu 22.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/10p, 1M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M MachineType: Giga Computing H263-S63-AAN1-000 Package: linux (not installed) PciMultimedia: ProcEnviron: LC_CTYPE=C.UTF-8 TERM=vt100 PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-34-generic root=UUID=b48b34d5-f2cf-444d-b376-0ffc987891c1 ro ProcVersionSignature: Ubuntu 6.2.0-34.34~22.04.1-generic 6.2.16 RelatedPackageVersions: linux-restricted-modules-6.2.0-34-generic N/A linux-backports-modules-6.2.0-34-generic N/A linux-firmware20220329.git681281e4-0ubuntu3.19 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: jammy uec-images Uname: Linux 6.2.0-34-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 08/09/2023 dmi.bios.release: 5.31 dmi.bios.vendor: GIGABYTE dmi.bios.version: F20 dmi.board.asset.tag: 01234567890123456789AB dmi.board.name: MS63-HD1-000 dmi.board.vendor: Giga Computing dmi.board.version: 01000100 dmi.chassis.asset.tag: 01234567890123456789AB dmi.chassis.type: 23 dmi.chassis.vendor: Giga Computing dmi.chassis.version: 01234567 dmi.modalias: dmi:bvnGIGABYTE:bvrF20:bd08/09/2023:br5.31:svnGigaComputing:pnH263-S63-AAN1-000:pvr9NH263S63DR000AAN1*:rvnGigaComputing:rnMS63-HD1-000:rvr01000100:cvnGigaComputing:ct23:cvr01234567:sku01234567890123456789AB: dmi.prod
[Kernel-packages] [Bug 2039549] Re: rtw89_8852be 0000:04:00.0: Direct firmware load for rtw89/rtw8852b_fw-1.bin failed with error -2
** Tags added: oem-priority originate-from-2039535 somerville -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2039549 Title: rtw89_8852be :04:00.0: Direct firmware load for rtw89/rtw8852b_fw-1.bin failed with error -2 Status in HWE Next: New Status in linux-firmware package in Ubuntu: In Progress Status in linux-firmware source package in Jammy: In Progress Status in linux-firmware source package in Lunar: In Progress Status in linux-firmware source package in Mantic: In Progress Bug description: [Impact] [Fix] [Test case] [Where problems could occur] To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2039549/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2039549] Re: rtw89_8852be 0000:04:00.0: Direct firmware load for rtw89/rtw8852b_fw-1.bin failed with error -2
*** This bug is a duplicate of bug 2029899 *** https://bugs.launchpad.net/bugs/2029899 ** This bug has been marked a duplicate of bug 2029899 Update firmware for hwe-6.2/oem-6.5 kernel migrations -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2039549 Title: rtw89_8852be :04:00.0: Direct firmware load for rtw89/rtw8852b_fw-1.bin failed with error -2 Status in HWE Next: New Status in linux-firmware package in Ubuntu: In Progress Status in linux-firmware source package in Jammy: In Progress Status in linux-firmware source package in Lunar: In Progress Status in linux-firmware source package in Mantic: In Progress Bug description: [Impact] [Fix] [Test case] [Where problems could occur] To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2039549/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2029899] Re: Update firmware for hwe-6.2/oem-6.5 kernel migrations
With linux-firmware 20220329.git681281e4-0ubuntu3.22, my rtw89_825be works :04:00.0 Network controller [0280]: Realtek Semiconductor Co., Ltd. Device [10ec:b852] Subsystem: Realtek Semiconductor Co., Ltd. Device [10ec:b887] Kernel driver in use: rtw89_8852be Kernel modules: rtw89_8852be It was [5.346832] rtw89_8852be :04:00.0: Direct firmware load for rtw89/rtw8852b_fw-1.bin failed with error -2 ** Tags added: oem-priority originate-from-2039535 somerville -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2029899 Title: Update firmware for hwe-6.2/oem-6.5 kernel migrations Status in HWE Next: New Status in linux-firmware package in Ubuntu: Invalid Status in linux-firmware source package in Jammy: Fix Committed Bug description: [SRU Justification] [Impact] When migrating to a new hwe kernel or introduced a oem kernel of a newer version, the firmware blobs might not match the expectation of the new kernel. [Fix] For linux-hwe-6.2/jammy: $ debian/scripts/list-lts-update-files \ launchpad/jammy \ launchpad/lunar \ linux-hwe-6.2/debian.hwe-6.2/abi/fwinfo | \ xargs git log --graph --oneline launchpad/jammy..launchpad/lunar -- * d02d58aae brcm: Add nvram for the Advantech MICA-071 tablet * f48fbe42c ath11k: IPQ5018 hw1.0: add to WLAN.HK.2.6.0.1-00861-QCAHKSWPL_SILICONZ-1 * 9dacec6da ath11k: IPQ5018 hw1.0: add board-2.bin * 3723b4800 brcm: add configuration files for CyberTan WC121 * e9b83572f amdgpu: updated aldebaran firmware for amd-5.4 * 9aa8db1cc rtlwifi: Add firmware v4.0 for RTL8188FU * 2c2be4215 nvidia: add GA102/GA103/GA104/GA106/GA107 signed firmware * 4ffcf980a brcm: rename Rock960 NVRAM to AP6356S and link devices to it For linux-oem-6.5/jammy: $ debian/scripts/list-lts-update-files \ launchpad/jammy \ launchpad/mantic \ linux-oem-6.5/debian.oem/abi/fwinfo | \ xargs git log --graph --oneline launchpad/jammy..launchpad/mantic -- * 41e615cf3 i915: Update ADLP DMC to v2.20 * 22fb12f2f amdgpu: add initial SMU 13.0.10 firmware * b3f512fb5 amdgpu: add initial SDMA 6.0.3 firmware * b1a7d7624 amdgpu: add initial PSP 13.0.10 firmware * d6d655ade amdgpu: add initial GC 11.0.3 firmware * b255f5b92 (tag: iwlwifi-fw-2023-06-29, korg-iwlwifi/for-upstream) iwlwifi: add new FWs from core80-39 release * 84d5550e9 amdgpu: update aldebaran firmware for amd.5.5 release * 08b854f02 rtlwifi: Add firmware v6.0 for RTL8192FU * 9f7502f1d rtw89: 8852b: update format-1 fw to v0.29.29.1 * 78a8782a9 (tag: iwlwifi-fw-2023-03-30) iwlwifi: add new FWs from core78-32 release * 7f490a9a4 Merge branch 'dmc-adlp_2.19-mtl_2.12' of git://anongit.freedesktop.org/drm/drm-firmware |\ | * 4ee236dbb i915: Update ADLP DMC to v2.19 * | 2c07f017f rtw89: 8852b: update format-1 fw to v0.29.29.0 * | b50cf9205 rtw89: 8852b: add format-1 fw v0.29.26.0 |/ * 6a55abe94 Merge https://github.com/pkshih/linux-firmware |\ | * 4cc3eda63 rtlwifi: Add firmware v16.0 for RTL8710BU aka RTL8188GU * | d02d58aae brcm: Add nvram for the Advantech MICA-071 tablet |/ * 3653d692b rtl_bt: Add firmware and config files for RTL8821CS * f48fbe42c ath11k: IPQ5018 hw1.0: add to WLAN.HK.2.6.0.1-00861-QCAHKSWPL_SILICONZ-1 * 9dacec6da ath11k: IPQ5018 hw1.0: add board-2.bin * a5046f435 (drm/dmc-adlp_2.18) i915: Add DMC v2.18 for ADLP * 3723b4800 brcm: add configuration files for CyberTan WC121 * e9b83572f amdgpu: updated aldebaran firmware for amd-5.4 * 9aa8db1cc rtlwifi: Add firmware v4.0 for RTL8188FU * 2c2be4215 nvidia: add GA102/GA103/GA104/GA106/GA107 signed firmware * 4ffcf980a brcm: rename Rock960 NVRAM to AP6356S and link devices to it [Test Case] Boot linux-oem-6.5, linux-hwe-6.2 with Jammy base system. [Where problems could occur] These firmware blobs are only referenced in the new hwe/oem kernels, and shall not have side effect. [Other Info] While there is no hwe/oem kernel planned for Lunar, so only Jammy is nominated for fix. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2029899/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1972728] Re: Night light not working on Nvidia Wayland
Looks like it's coming in 545: https://www.nvidia.com/download/driverResults.aspx/212964/en-us/ ** Package changed: nvidia-graphics-drivers-510 (Ubuntu) => nvidia- graphics-drivers (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-510 in Ubuntu. https://bugs.launchpad.net/bugs/1972728 Title: Night light not working on Nvidia Wayland Status in Mutter: New Status in nvidia-graphics-drivers package in Ubuntu: Triaged Bug description: On the Wayland session using an Nvidia GPU, enabling the Night Light setting in the Settings app doesn't change the screen colour temperature to a warmer hue regardless of "Sunset to Sunrise" or "Manual Schedule" being selected. Switching to the X11 session results in Night Light working as expecting. I'm currently using the Nvidia 510.60.02 driver (RTX 2080Ti). $ lsb_release -rd Description: Ubuntu 22.04 LTS Release: 22.04 $ apt-cache policy gnome-shell gnome-shell: Installed: 42.0-2ubuntu1 Candidate: 42.0-2ubuntu1 Version table: *** 42.0-2ubuntu1 500 500 http://gb.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon May 9 22:01:57 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-04-29 (10 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) RelatedPackageVersions: mutter-common 42.0-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1972728/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2034619] Re: [amdgpu] gnome-shell gets SIGKILL'd when lock screen or under heavy load in Wayland
** Changed in: mutter (Ubuntu Mantic) Status: In Progress => Fix Committed ** Tags added: fixed-in-mutter-45.1 fixed-upstream -- 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/2034619 Title: [amdgpu] gnome-shell gets SIGKILL'd when lock screen or under heavy load in Wayland Status in Linux: New Status in Mutter: Fix Released Status in X.Org X server: Fix Released Status in linux package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Fix Committed Status in linux source package in Mantic: Confirmed Status in mutter source package in Mantic: Fix Committed Bug description: [ Impact ] gnome-shell gets unceremoniously SIGKILLed on some Ryzen systems, sometimes when the screen locks, sometimes when launching particular apps. [ Workaround ] Add this to /etc/environment: MUTTER_DEBUG_KMS_THREAD_TYPE=user and then reboot. [ Test Plan ] Not all Ryzen systems (including one I just purchased) are able to reproduce the bug. We have no choice but to leave final verification to the community. Anyone affected should try locking their screen and verify they are not instantly returned to the login screen. [ Where problems could occur ] Anywhere in frame scheduling and particularly for mouse cursor movement since that's what the real-time thread exists to optimize. [ Original Description ] I have this issue on Ubuntu 23.10. Lock screen works only with an external monitor connected. Otherwise the session is ended and the user is logged out and brought to the gdm screen. All works in xorg. ProblemType: Crash DistroRelease: Ubuntu 23.10 Package: gnome-shell 45~beta.1-0ubuntu2 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Sep 6 22:32:22 2023 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2023-09-03 (3 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230901.1) ProcCmdline: /usr/bin/gnome-shell RelatedPackageVersions: mutter-common 45~beta.1-1ubuntu2 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo users separator: To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2034619/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1965303] Re: Migrate from fbdev drivers to simpledrm and DRM fbdev emulation layer
I don't quite follow why we're calling this an issue. It's an enhancement that should target 24.04 only. -- 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/1965303 Title: Migrate from fbdev drivers to simpledrm and DRM fbdev emulation layer Status in gdm: Fix Released Status in gdm3 package in Ubuntu: Fix Released Status in linux package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-470 package in Ubuntu: Fix Released Status in gdm3 source package in Jammy: In Progress Status in linux source package in Jammy: Won't Fix Status in nvidia-graphics-drivers-470 source package in Jammy: Fix Released Status in gdm3 source package in Lunar: Invalid Status in linux source package in Lunar: Won't Fix Status in nvidia-graphics-drivers-470 source package in Lunar: Fix Released Status in gdm3 source package in Mantic: Fix Released Status in linux source package in Mantic: Confirmed Status in nvidia-graphics-drivers-470 source package in Mantic: Fix Released Status in linux package in Fedora: Fix Released Bug description: [ Impact ] The fbdev subsystem has been deprecated for a long time. We should drop it in favour of using simpledrm with fbdev emulation layer. This requires Kernel config changes: FB_EFI=n FB_VESA=n fbcon will still require FB to be available, but will use the fbdev emulation layer When this stack is enabled, it changes boot timing such that some drivers may take a longer time to boot and GDM may hang in a black screen. This issue has been readily reproduced in Ubuntu and reported to upstream mutter. https://gitlab.gnome.org/GNOME/mutter/-/issues/2909 [ Test Plan ] * Ensure that a kernel with required kernel changes can boot to GDM using DRM driver (amdgpu, i915, or nouveau) [ Where Problems could occur ] * Race conditions could be exposed to DE environments * Software that expects to find DRM device at /dev/dri/card0 may have a problem. * Some older versions of NVIDIA driver might not work properly. [ Other Info ] * Fedora bug: https://bugzilla.redhat.com/show_bug.cgi?id=2022385 To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1965303/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1965303] Re: Migrate from fbdev drivers to simpledrm and DRM fbdev emulation layer
The problem is specifically when 24.04's kernel backports to 22.04 it will expose the race condition to GDM. If that kernel will never backport then it won't be a problem. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1965303 Title: Migrate from fbdev drivers to simpledrm and DRM fbdev emulation layer Status in gdm: Fix Released Status in gdm3 package in Ubuntu: Fix Released Status in linux package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-470 package in Ubuntu: Fix Released Status in gdm3 source package in Jammy: In Progress Status in linux source package in Jammy: Won't Fix Status in nvidia-graphics-drivers-470 source package in Jammy: Fix Released Status in gdm3 source package in Lunar: Invalid Status in linux source package in Lunar: Won't Fix Status in nvidia-graphics-drivers-470 source package in Lunar: Fix Released Status in gdm3 source package in Mantic: Fix Released Status in linux source package in Mantic: Confirmed Status in nvidia-graphics-drivers-470 source package in Mantic: Fix Released Status in linux package in Fedora: Fix Released Bug description: [ Impact ] The fbdev subsystem has been deprecated for a long time. We should drop it in favour of using simpledrm with fbdev emulation layer. This requires Kernel config changes: FB_EFI=n FB_VESA=n fbcon will still require FB to be available, but will use the fbdev emulation layer When this stack is enabled, it changes boot timing such that some drivers may take a longer time to boot and GDM may hang in a black screen. This issue has been readily reproduced in Ubuntu and reported to upstream mutter. https://gitlab.gnome.org/GNOME/mutter/-/issues/2909 [ Test Plan ] * Ensure that a kernel with required kernel changes can boot to GDM using DRM driver (amdgpu, i915, or nouveau) [ Where Problems could occur ] * Race conditions could be exposed to DE environments * Software that expects to find DRM device at /dev/dri/card0 may have a problem. * Some older versions of NVIDIA driver might not work properly. [ Other Info ] * Fedora bug: https://bugzilla.redhat.com/show_bug.cgi?id=2022385 To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1965303/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
