[Kernel-packages] [Bug 2018443] 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 2018443 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/2018443 Title: Cannot setup status IPv6 address for the specific network during installation Status in linux package in Ubuntu: Incomplete Bug description: Try to install Ubuntu server 20.04/22.04 and setup static IPv4/IPv6 address via kernel parameters for the specific network MAC address, below solution can work for IPv4, but IPv6 will be failed with the message “ipconfig: can’t parse IP address ‘ens3f1,[2002”， please help to check if is the usage for IPv6 incorrect or provide the solution about IPv6. Kernel parameters for IPv4(Pass): ksdevice=bootif BOOTIF=68:05:ca:44:03:87 ip=10.10.10.120::10.10.10.1:255.255.255.010.10.10.1 ds=nocloud- net;s=http://XX.XX.XX.XX/ Kernel parameters for IPv6(Fail): ksdevice=bootif BOOTIF=68:05:ca:44:03:87 ip=[2002:97b:c2bb:830:10:240:210:31]:::64::eno1:none To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2018443/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2018420] 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 2018420 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/2018420 Title: linux kerkel 6.2.0.20-generic failed to install Status in linux package in Ubuntu: Incomplete Bug description: Setting up linux-image-6.2.0-20-generic (6.2.0-20.20) ... Setting up linux-headers-6.2.0-20-generic (6.2.0-20.20) ... /etc/kernel/header_postinst.d/dkms: * dkms: running auto installation service for kernel 6.2.0-20-generic Sign command: /usr/bin/kmodsign Signing key: /var/lib/shim-signed/mok/MOK.priv Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der Building module: Cleaning build area... make -j4 KERNELRELEASE=6.2.0-20-generic...(bad exit status: 2) Error! Bad return status for module build on kernel: 6.2.0-20-generic (x86_64) Consult /var/lib/dkms/vhba/20200106/build/make.log for more information. Error! One or more modules failed to install during autoinstall. Refer to previous errors for more information. ...fail! run-parts: /etc/kernel/header_postinst.d/dkms exited with return code 11 dpkg: error processing package linux-headers-6.2.0-20-generic (--configure): installed linux-headers-6.2.0-20-generic package post-installation script subprocess returned error exit status 1 dpkg: dependency problems prevent configuration of linux-headers-generic: linux-headers-generic depends on linux-headers-6.2.0-20-generic; however: Package linux-headers-6.2.0-20-generic is not configured yet. dpkg: error processing package linux-headers-generic (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of linux-generic: linux-generic depends on linux-headers-generic (= 6.2.0.20.20); however: Package linux-headers-generic is not configured yet. dpkg: error processing package linux-generic (--configure): dependency problems - leaving unconfigured Processing triggers for libc-bin (2.37-0ubuntu2) ... No apport report written because the error message indicates its a followup error from a previous failure. No apport report written because the error message indicates its a followup error from a previous failure. Processing triggers for man-db (2.11.2-1) ... Processing triggers for mailcap (3.70+nmu1ubuntu1) ... Processing triggers for bamfdaemon (0.5.6+22.04.20220217-0ubuntu1) ... Rebuilding /usr/share/applications/bamf-2.index... Processing triggers for desktop-file-utils (0.26-1ubuntu5) ... Processing triggers for gnome-menus (3.36.0-1.1ubuntu1) ... Processing triggers for linux-image-6.2.0-20-generic (6.2.0-20.20) ... /etc/kernel/postinst.d/dkms: * dkms: running auto installation service for kernel 6.2.0-20-generic Sign command: /usr/bin/kmodsign Signing key: /var/lib/shim-signed/mok/MOK.priv Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der Building module: Cleaning build area... make -j4 KERNELRELEASE=6.2.0-20-generic...(bad exit status: 2) ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/vhba-dkms.0.crash' Error! Bad return status for module build on kernel: 6.2.0-20-generic (x86_64) Consult /var/lib/dkms/vhba/20200106/build/make.log for more information. Error! One or more modules failed to install during autoinstall. Refer to previous errors for more information. ...fail! run-parts: /etc/kernel/postinst.d/dkms exited with return code 11 dpkg: error processing package linux-image-6.2.0-20-generic (--configure): installed linux-image-6.2.0-20-generic package post-installation script subprocess returned error exit status 1 No apport report written because MaxReports is reached already Errors were encountered while processing: linux-headers-6.2.0-20-generic linux-headers-generic linux-generic linux-image-6.2.0-20-generic E: Sub-process /usr/bin/dpkg returned an error code (1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2018420/+subscriptions -- Mailing list:
[Kernel-packages] [Bug 2018420] Re: linux kerkel 6.2.0.20-generic failed to install
** Project changed: launchpad => 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/2018420 Title: linux kerkel 6.2.0.20-generic failed to install Status in linux package in Ubuntu: New Bug description: Setting up linux-image-6.2.0-20-generic (6.2.0-20.20) ... Setting up linux-headers-6.2.0-20-generic (6.2.0-20.20) ... /etc/kernel/header_postinst.d/dkms: * dkms: running auto installation service for kernel 6.2.0-20-generic Sign command: /usr/bin/kmodsign Signing key: /var/lib/shim-signed/mok/MOK.priv Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der Building module: Cleaning build area... make -j4 KERNELRELEASE=6.2.0-20-generic...(bad exit status: 2) Error! Bad return status for module build on kernel: 6.2.0-20-generic (x86_64) Consult /var/lib/dkms/vhba/20200106/build/make.log for more information. Error! One or more modules failed to install during autoinstall. Refer to previous errors for more information. ...fail! run-parts: /etc/kernel/header_postinst.d/dkms exited with return code 11 dpkg: error processing package linux-headers-6.2.0-20-generic (--configure): installed linux-headers-6.2.0-20-generic package post-installation script subprocess returned error exit status 1 dpkg: dependency problems prevent configuration of linux-headers-generic: linux-headers-generic depends on linux-headers-6.2.0-20-generic; however: Package linux-headers-6.2.0-20-generic is not configured yet. dpkg: error processing package linux-headers-generic (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of linux-generic: linux-generic depends on linux-headers-generic (= 6.2.0.20.20); however: Package linux-headers-generic is not configured yet. dpkg: error processing package linux-generic (--configure): dependency problems - leaving unconfigured Processing triggers for libc-bin (2.37-0ubuntu2) ... No apport report written because the error message indicates its a followup error from a previous failure. No apport report written because the error message indicates its a followup error from a previous failure. Processing triggers for man-db (2.11.2-1) ... Processing triggers for mailcap (3.70+nmu1ubuntu1) ... Processing triggers for bamfdaemon (0.5.6+22.04.20220217-0ubuntu1) ... Rebuilding /usr/share/applications/bamf-2.index... Processing triggers for desktop-file-utils (0.26-1ubuntu5) ... Processing triggers for gnome-menus (3.36.0-1.1ubuntu1) ... Processing triggers for linux-image-6.2.0-20-generic (6.2.0-20.20) ... /etc/kernel/postinst.d/dkms: * dkms: running auto installation service for kernel 6.2.0-20-generic Sign command: /usr/bin/kmodsign Signing key: /var/lib/shim-signed/mok/MOK.priv Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der Building module: Cleaning build area... make -j4 KERNELRELEASE=6.2.0-20-generic...(bad exit status: 2) ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/vhba-dkms.0.crash' Error! Bad return status for module build on kernel: 6.2.0-20-generic (x86_64) Consult /var/lib/dkms/vhba/20200106/build/make.log for more information. Error! One or more modules failed to install during autoinstall. Refer to previous errors for more information. ...fail! run-parts: /etc/kernel/postinst.d/dkms exited with return code 11 dpkg: error processing package linux-image-6.2.0-20-generic (--configure): installed linux-image-6.2.0-20-generic package post-installation script subprocess returned error exit status 1 No apport report written because MaxReports is reached already Errors were encountered while processing: linux-headers-6.2.0-20-generic linux-headers-generic linux-generic linux-image-6.2.0-20-generic E: Sub-process /usr/bin/dpkg returned an error code (1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2018420/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2018443] [NEW] Cannot setup status IPv6 address for the specific network during installation
Public bug reported: Try to install Ubuntu server 20.04/22.04 and setup static IPv4/IPv6 address via kernel parameters for the specific network MAC address, below solution can work for IPv4, but IPv6 will be failed with the message “ipconfig: can’t parse IP address ‘ens3f1,[2002”， please help to check if is the usage for IPv6 incorrect or provide the solution about IPv6. Kernel parameters for IPv4(Pass): ksdevice=bootif BOOTIF=68:05:ca:44:03:87 ip=10.10.10.120::10.10.10.1:255.255.255.010.10.10.1 ds=nocloud- net;s=http://XX.XX.XX.XX/ Kernel parameters for IPv6(Fail): ksdevice=bootif BOOTIF=68:05:ca:44:03:87 ip=[2002:97b:c2bb:830:10:240:210:31]:::64::eno1:none ** 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/2018443 Title: Cannot setup status IPv6 address for the specific network during installation Status in linux package in Ubuntu: New Bug description: Try to install Ubuntu server 20.04/22.04 and setup static IPv4/IPv6 address via kernel parameters for the specific network MAC address, below solution can work for IPv4, but IPv6 will be failed with the message “ipconfig: can’t parse IP address ‘ens3f1,[2002”， please help to check if is the usage for IPv6 incorrect or provide the solution about IPv6. Kernel parameters for IPv4(Pass): ksdevice=bootif BOOTIF=68:05:ca:44:03:87 ip=10.10.10.120::10.10.10.1:255.255.255.010.10.10.1 ds=nocloud- net;s=http://XX.XX.XX.XX/ Kernel parameters for IPv6(Fail): ksdevice=bootif BOOTIF=68:05:ca:44:03:87 ip=[2002:97b:c2bb:830:10:240:210:31]:::64::eno1:none To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2018443/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1956104] Re: firmware-sof description is inaccurate and misleading
https://git.launchpad.net/ubuntu/+source/firmware- sof/tree/debian/control >Description: Intel SOF firmware - signed Provides the Intel SOF audio firmware and topology needed for audio functionality on some Intel system. ** Tags added: bitesize mantic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to firmware-sof in Ubuntu. https://bugs.launchpad.net/bugs/1956104 Title: firmware-sof description is inaccurate and misleading Status in firmware-sof package in Ubuntu: Confirmed Bug description: Package description says Intel firmware. https://thesofproject.github.io/latest/platforms/index.html https://www.cadence.com/en_US/home/tools/ip/tensilica-ip/tensilica- xtensa-controllers-and-extensible-processors.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firmware-sof/+bug/1956104/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2001599] Re: Lost display on built-in monitor after suspend
** Changed in: linux (Ubuntu) Status: In Progress => Invalid ** Changed in: linux (Ubuntu) Assignee: AceLan Kao (acelankao) => (unassigned) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.0 in Ubuntu. https://bugs.launchpad.net/bugs/2001599 Title: Lost display on built-in monitor after suspend Status in HWE Next: New Status in linux package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.0 source package in Jammy: Won't Fix Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux source package in Lunar: In Progress Status in linux-oem-6.0 source package in Lunar: Invalid Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [Impact] On some laptops, the eDP blinking slowly after resuming from S3 [Fix] The series of patches which were in drp-tip fix the isue https://patchwork.freedesktop.org/series/110693/ In v6.3-rc1 4c0eb35fc103 drm/i915: Improve PPS debugs ed5509d1d451 drm/i915: Fix whitespace 1e47e035bb73 drm/i915: Print the PPS registers using consistent format ba21bb24810f drm/i915: Reject unusable power sequencers d83804f22d85 drm/i915: Extend dual PPS handlind for ICP+ bf38bba3e7d6 drm/i915: Try to use the correct power sequencer intiially on bxt/glk 209074fd5a82 drm/i915: Generalize the PPS vlv_pipe_check() stuff 3f9ffce5765d drm/i915: Do panel VBT init early if the VBT declares an explicit panel type f70f8153e364 drm/i915: Introduce intel_panel_init_alloc() [Test] ODM and I confirmed the issue is fixed after the patches have been applied. [Where problems may occur] This series of patches fixes a dedicate issue and change the power sequence for the eDP panel. eDP panel may stay blank if the rules are wrong. Our QA will help us to verify this kind of issue. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2001599/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2018438] [NEW] Jammy update: v5.15.99 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.99 upstream stable release from git://git.kernel.org/ HID: asus: use spinlock to protect concurrent accesses HID: asus: use spinlock to safely schedule workers powerpc/mm: Rearrange if-else block to avoid clang warning ARM: OMAP2+: Fix memory leak in realtime_counter_init() arm64: dts: qcom: qcs404: use symbol names for PCIe resets arm64: dts: qcom: msm8996-tone: Fix USB taking 6 minutes to wake up arm64: dts: qcom: sm8150-kumano: Panel framebuffer is 2.5k instead of 4k arm64: dts: qcom: sm6125: Reorder HSUSB PHY clocks to match bindings arm64: dts: imx8m: Align SoC unique ID node unit address ARM: zynq: Fix refcount leak in zynq_early_slcr_init arm64: dts: mediatek: mt8183: Fix systimer 13 MHz clock description arm64: dts: qcom: sdm845-db845c: fix audio codec interrupt pin name arm64: dts: qcom: sc7180: correct SPMI bus address cells arm64: dts: qcom: sc7280: correct SPMI bus address cells arm64: dts: meson-gx: Fix Ethernet MAC address unit name arm64: dts: meson-g12a: Fix internal Ethernet PHY unit name arm64: dts: meson-gx: Fix the SCPI DVFS node name and unit address arm64: dts: msm8992-bullhead: add memory hole region arm64: dts: qcom: msm8992-bullhead: Fix cont_splash_mem size arm64: dts: qcom: msm8992-bullhead: Disable dfps_data_mem arm64: dts: qcom: ipq8074: correct USB3 QMP PHY-s clock output names arm64: dts: qcom: Fix IPQ8074 PCIe PHY nodes arm64: dts: qcom: ipq8074: fix PCIe PHY serdes size arm64: dts: qcom: ipq8074: fix Gen3 PCIe QMP PHY arm64: dts: qcom: ipq8074: correct Gen2 PCIe ranges arm64: dts: qcom: ipq8074: fix Gen3 PCIe node arm64: dts: qcom: ipq8074: correct PCIe QMP PHY output clock names arm64: dts: meson: remove CPU opps below 1GHz for G12A boards ARM: OMAP1: call platform_device_put() in error case in omap1_dm_timer_init() ARM: bcm2835_defconfig: Enable the framebuffer ARM: s3c: fix s3c64xx_set_timer_source prototype arm64: dts: ti: k3-j7200: Fix wakeup pinmux range ARM: dts: exynos: correct wr-active property in Exynos3250 Rinato ARM: imx: Call ida_simple_remove() for ida_simple_get arm64: dts: amlogic: meson-gx: fix SCPI clock dvfs node name arm64: dts: amlogic: meson-axg: fix SCPI clock dvfs node name arm64: dts: amlogic: meson-gx: add missing SCPI sensors compatible arm64: dts: amlogic: meson-gxl-s905d-sml5442tw: drop invalid clock-names property arm64: dts: amlogic: meson-gx: add missing unit address to rng node name arm64: dts: amlogic: meson-gxl: add missing unit address to eth-phy-mux node name arm64: dts: amlogic: meson-gx-libretech-pc: fix update button name arm64: dts: amlogic: meson-sm1-bananapi-m5: fix adc keys node names arm64: dts: amlogic: meson-gxl-s905d-phicomm-n1: fix led node name arm64: dts: amlogic: meson-gxbb-kii-pro: fix led node name arm64: dts: amlogic: meson-sm1-odroid-hc4: fix active fan thermal trip locking/rwsem: Optimize down_read_trylock() under highly contended case locking/rwsem: Disable preemption in all down_read*() and up_read() code paths arm64: dts: renesas: beacon-renesom: Fix gpio expander reference arm64: dts: meson: bananapi-m5: switch VDDIO_C pin to OPEN_DRAIN ARM: dts: sun8i: nanopi-duo2: Fix regulator GPIO reference ARM: dts: imx7s: correct iomuxc gpr mux controller cells arm64: dts: mt8192: Fix CPU map for single-cluster SoC arm64: dts: mediatek: mt7622: Add missing pwm-cells to pwm node blk-mq: avoid sleep in blk_mq_alloc_request_hctx blk-mq: remove stale comment for blk_mq_sched_mark_restart_hctx blk-mq: correct stale comment of .get_budget arm64: dts: qcom: msm8992-lg-bullhead: Correct memory overlaps with the SMEM and MPSS memory regions s390/dasd: Fix potential memleak in dasd_eckd_init() sched/deadline,rt: Remove unused parameter from pick_next_[rt|dl]_entity() sched/rt: pick_next_rt_entity(): check list_entry x86/perf/zhaoxin: Add stepping check for ZXC KEYS: asymmetric: Fix ECDSA use via keyctl uapi arm64: dts: qcom: pmk8350: Specify PBS register for PON arm64: dts: qcom: pmk8350: Use the correct PON compatible block: bio-integrity: Copy flags when bio_integrity_payload is cloned wifi: rsi: Fix memory leak in rsi_coex_attach() wifi: rtlwifi: rtl8821ae: don't call kfree_skb() under spin_lock_irqsave() wifi: rtlwifi: rtl8188ee: don't call kfree_skb() under spin_lock_irqsave() wifi: rtlwifi: rtl8723be: don't call kfree_skb() under spin_lock_irqsave() wifi: iwlegacy: common: don't call dev_kfree_skb() under spin_lock_irqsave() wifi: libertas: fix memory leak in lbs_init_adapter() wifi: rtl8xxxu: don't call dev_kfree_skb() under
[Kernel-packages] [Bug 2017328] Re: package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to install/upgrade: installed linux-headers-6.2.0-20-generic package post-installation script subprocess r
*** This bug is a duplicate of bug 2018226 *** https://bugs.launchpad.net/bugs/2018226 Thanks for your efforts. I was able to use the system by booting into an older kernel version (5.19). I removed quite a number of older kernels (and headers), which lead to initrd image being newly built and from then on I was on kernel 6.2 Problem is solved for me. Would have been grave if I were just a casual user. Rudimentary linux knowledge kept me going. Once more: thanks to all of you working so hard to make this great system. -- 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/2017328 Title: package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to install/upgrade: installed linux-headers-6.2.0-20-generic package post-installation script subprocess returned error exit status 1 Status in linux package in Ubuntu: Confirmed Bug description: While upgrading to ubuntu 23.04 System status reported as "possibly unstable" not good ProblemType: Package DistroRelease: Ubuntu 23.04 Package: linux-headers-6.2.0-20-generic 6.2.0-20.20 ProcVersionSignature: Ubuntu 5.19.0-40.41-generic 5.19.17 Uname: Linux 5.19.0-40-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown Date: Sat Apr 22 06:39:48 2023 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+italia-whl+X37+italia-whl+X37.1+italia-+X37.2 ErrorMessage: installed linux-headers-6.2.0-20-generic package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2019-09-23 (1306 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 MachineType: Dell Inc. XPS 13 9380 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-40-generic root=UUID=19d37003-0d66-4336-ba14-e62e0854596d ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: grub-pc N/A SourcePackage: linux Title: package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to install/upgrade: installed linux-headers-6.2.0-20-generic package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to lunar on 2023-04-22 (0 days ago) dmi.bios.date: 12/08/2021 dmi.bios.release: 1.17 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.17.0 dmi.board.name: 0KTW76 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.17.0:bd12/08/2021:br1.17:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn0KTW76:rvrA00:cvnDellInc.:ct10:cvr:sku08AF: dmi.product.family: XPS dmi.product.name: XPS 13 9380 dmi.product.sku: 08AF dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2017328/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2008774] Re: Ubuntu 22.04 not waking up after second suspend
It looks like the latest Ubuntu 23.04 with linux kernel 6.2.0 solved the problem (for me ,ThinkPad T14 with AMD CPU, at least). Sleep works out- of-the-box without having to do amdgpu-install trick. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2008774 Title: Ubuntu 22.04 not waking up after second suspend Status in linux-signed-hwe-5.19 package in Ubuntu: Confirmed Bug description: After the first suspend it wakes up just fine - it's the second suspend after which the screen stays blank and keyboard doesn't react (although the power LED starts glowing). It happens if I close the laptop's lid or do a manual suspend via the system menu. It happens only recently (I think after some kernel update, but I'm not sure about this) - before it worked fine for month (since I installed Ubuntu). I have a recent Thinkpad T14s with a Ryzen CPU, Ubuntu 22.04 is the only OS (if that's important). What I tried: * turn off security chip in the BIOS (https://askubuntu.com/a/1412049/424896) * turn off Wayland and enable X11 (https://askubuntu.com/a/1412032/424896) * I looked through the logs in /var/log but couldn't find anything obvious to me (but I'm not a Linux guru). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-32-generic 5.19.0-32.33~22.04.1 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Feb 28 11:02:36 2023 InstallationDate: Installed on 2022-06-14 (258 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: linux-signed-hwe-5.19 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.19/+bug/2008774/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2018431] 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/2018431 Title: package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to install/upgrade: installed linux-headers-6.2.0-20-generic package post-installation script subprocess returned error exit status 1 Status in linux package in Ubuntu: Confirmed Bug description: During upgrade from kinetic to lunar ProblemType: Package DistroRelease: Ubuntu 23.04 Package: linux-headers-6.2.0-20-generic 6.2.0-20.20 ProcVersionSignature: Ubuntu 5.19.0-38.39-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mark 1639 F wireplumber /dev/snd/controlC1: mark 1639 F wireplumber /dev/snd/seq:mark 1636 F pipewire CRDA: N/A CasperMD5CheckMismatches: ./preseed/ubuntu.seed ./pool/restricted/n/nvidia-graphics-drivers-515/nvidia-kernel-common-515_515.76+really.515.65.01-0ubuntu1_amd64.deb ./pool/restricted/n/nvidia-graphics-drivers-515/nvidia-kernel-source-515_515.76+really.515.65.01-0ubuntu1_amd64.deb ./pool/restricted/n/nvidia-graphics-drivers-515/nvidia-utils-515_515.76+really.515.65.01-0ubuntu1_amd64.deb ./pool/restricted/n/nvidia-graphics-drivers-515/xserver-xorg-video-nvidia-515_515.76+really.515.65.01-0ubuntu1_amd64.deb CasperMD5CheckResult: fail Date: Wed May 3 21:56:24 2023 ErrorMessage: installed linux-headers-6.2.0-20-generic package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2022-11-01 (183 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) MachineType: SYSTEM_MANUFACTURER HX90 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-38-generic root=UUID=887b3140-4d95-48d5-aec2-39d52a18cd30 ro quiet splash Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1 PythonDetails: /usr/bin/python3.11, Python 3.11.2, python-is-python3, 3.11.1-3 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: grub-pc 2.06-2ubuntu16 SourcePackage: linux Title: package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to install/upgrade: installed linux-headers-6.2.0-20-generic package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to lunar on 2023-05-03 (0 days ago) dmi.bios.date: 10/11/2021 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 5.19 dmi.board.asset.tag: Default string dmi.board.name: HX90 dmi.board.vendor: Default string dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr5.19:bd10/11/2021:br5.19:svnSYSTEM_MANUFACTURER:pnHX90:pvrDefaultstring:rvnDefaultstring:rnHX90:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: Default string dmi.product.name: HX90 dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: SYSTEM_MANUFACTURER To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2018431/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2018431] Re: package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to install/upgrade: installed linux-headers-6.2.0-20-generic package post-installation script subprocess r
** Tags removed: need-duplicate-check -- 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/2018431 Title: package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to install/upgrade: installed linux-headers-6.2.0-20-generic package post-installation script subprocess returned error exit status 1 Status in linux package in Ubuntu: New Bug description: During upgrade from kinetic to lunar ProblemType: Package DistroRelease: Ubuntu 23.04 Package: linux-headers-6.2.0-20-generic 6.2.0-20.20 ProcVersionSignature: Ubuntu 5.19.0-38.39-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mark 1639 F wireplumber /dev/snd/controlC1: mark 1639 F wireplumber /dev/snd/seq:mark 1636 F pipewire CRDA: N/A CasperMD5CheckMismatches: ./preseed/ubuntu.seed ./pool/restricted/n/nvidia-graphics-drivers-515/nvidia-kernel-common-515_515.76+really.515.65.01-0ubuntu1_amd64.deb ./pool/restricted/n/nvidia-graphics-drivers-515/nvidia-kernel-source-515_515.76+really.515.65.01-0ubuntu1_amd64.deb ./pool/restricted/n/nvidia-graphics-drivers-515/nvidia-utils-515_515.76+really.515.65.01-0ubuntu1_amd64.deb ./pool/restricted/n/nvidia-graphics-drivers-515/xserver-xorg-video-nvidia-515_515.76+really.515.65.01-0ubuntu1_amd64.deb CasperMD5CheckResult: fail Date: Wed May 3 21:56:24 2023 ErrorMessage: installed linux-headers-6.2.0-20-generic package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2022-11-01 (183 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) MachineType: SYSTEM_MANUFACTURER HX90 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-38-generic root=UUID=887b3140-4d95-48d5-aec2-39d52a18cd30 ro quiet splash Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1 PythonDetails: /usr/bin/python3.11, Python 3.11.2, python-is-python3, 3.11.1-3 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: grub-pc 2.06-2ubuntu16 SourcePackage: linux Title: package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to install/upgrade: installed linux-headers-6.2.0-20-generic package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to lunar on 2023-05-03 (0 days ago) dmi.bios.date: 10/11/2021 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 5.19 dmi.board.asset.tag: Default string dmi.board.name: HX90 dmi.board.vendor: Default string dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr5.19:bd10/11/2021:br5.19:svnSYSTEM_MANUFACTURER:pnHX90:pvrDefaultstring:rvnDefaultstring:rnHX90:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: Default string dmi.product.name: HX90 dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: SYSTEM_MANUFACTURER To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2018431/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2018431] [NEW] package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to install/upgrade: installed linux-headers-6.2.0-20-generic package post-installation script subprocess
Public bug reported: During upgrade from kinetic to lunar ProblemType: Package DistroRelease: Ubuntu 23.04 Package: linux-headers-6.2.0-20-generic 6.2.0-20.20 ProcVersionSignature: Ubuntu 5.19.0-38.39-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mark 1639 F wireplumber /dev/snd/controlC1: mark 1639 F wireplumber /dev/snd/seq:mark 1636 F pipewire CRDA: N/A CasperMD5CheckMismatches: ./preseed/ubuntu.seed ./pool/restricted/n/nvidia-graphics-drivers-515/nvidia-kernel-common-515_515.76+really.515.65.01-0ubuntu1_amd64.deb ./pool/restricted/n/nvidia-graphics-drivers-515/nvidia-kernel-source-515_515.76+really.515.65.01-0ubuntu1_amd64.deb ./pool/restricted/n/nvidia-graphics-drivers-515/nvidia-utils-515_515.76+really.515.65.01-0ubuntu1_amd64.deb ./pool/restricted/n/nvidia-graphics-drivers-515/xserver-xorg-video-nvidia-515_515.76+really.515.65.01-0ubuntu1_amd64.deb CasperMD5CheckResult: fail Date: Wed May 3 21:56:24 2023 ErrorMessage: installed linux-headers-6.2.0-20-generic package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2022-11-01 (183 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) MachineType: SYSTEM_MANUFACTURER HX90 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-38-generic root=UUID=887b3140-4d95-48d5-aec2-39d52a18cd30 ro quiet splash Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1 PythonDetails: /usr/bin/python3.11, Python 3.11.2, python-is-python3, 3.11.1-3 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: grub-pc 2.06-2ubuntu16 SourcePackage: linux Title: package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to install/upgrade: installed linux-headers-6.2.0-20-generic package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to lunar on 2023-05-03 (0 days ago) dmi.bios.date: 10/11/2021 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 5.19 dmi.board.asset.tag: Default string dmi.board.name: HX90 dmi.board.vendor: Default string dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr5.19:bd10/11/2021:br5.19:svnSYSTEM_MANUFACTURER:pnHX90:pvrDefaultstring:rvnDefaultstring:rnHX90:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: Default string dmi.product.name: HX90 dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: SYSTEM_MANUFACTURER ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package lunar -- 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/2018431 Title: package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to install/upgrade: installed linux-headers-6.2.0-20-generic package post-installation script subprocess returned error exit status 1 Status in linux package in Ubuntu: New Bug description: During upgrade from kinetic to lunar ProblemType: Package DistroRelease: Ubuntu 23.04 Package: linux-headers-6.2.0-20-generic 6.2.0-20.20 ProcVersionSignature: Ubuntu 5.19.0-38.39-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mark 1639 F wireplumber /dev/snd/controlC1: mark 1639 F wireplumber /dev/snd/seq:mark 1636 F pipewire CRDA: N/A CasperMD5CheckMismatches: ./preseed/ubuntu.seed ./pool/restricted/n/nvidia-graphics-drivers-515/nvidia-kernel-common-515_515.76+really.515.65.01-0ubuntu1_amd64.deb ./pool/restricted/n/nvidia-graphics-drivers-515/nvidia-kernel-source-515_515.76+really.515.65.01-0ubuntu1_amd64.deb ./pool/restricted/n/nvidia-graphics-drivers-515/nvidia-utils-515_515.76+really.515.65.01-0ubuntu1_amd64.deb ./pool/restricted/n/nvidia-graphics-drivers-515/xserver-xorg-video-nvidia-515_515.76+really.515.65.01-0ubuntu1_amd64.deb CasperMD5CheckResult: fail Date: Wed May 3 21:56:24 2023 ErrorMessage: installed linux-headers-6.2.0-20-generic package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2022-11-01 (183 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) MachineType: SYSTEM_MANUFACTURER HX90 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-38-generic root=UUID=887b3140-4d95-48d5-aec2-39d52a18cd30 ro quiet splash
[Kernel-packages] [Bug 2018429] [NEW] A lot of messages in logs "Window manager warning"
Public bug reported: There's a lot of messages like this: May 3 22:16:59 home gnome-shell[1687]: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11). Often the browser freezes and does not respond to the mouse (browser: Goolge Chrome). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-41-generic 5.19.0-41.42~22.04.1 ProcVersionSignature: Ubuntu 5.19.0-41.42~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed May 3 22:20:49 2023 InstallationDate: Installed on 2021-11-13 (535 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) SourcePackage: linux-signed-hwe-5.19 UpgradeStatus: Upgraded to jammy on 2022-11-24 (160 days ago) ** Affects: linux-signed-hwe-5.19 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2018429 Title: A lot of messages in logs "Window manager warning" Status in linux-signed-hwe-5.19 package in Ubuntu: New Bug description: There's a lot of messages like this: May 3 22:16:59 home gnome-shell[1687]: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11). Often the browser freezes and does not respond to the mouse (browser: Goolge Chrome). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-41-generic 5.19.0-41.42~22.04.1 ProcVersionSignature: Ubuntu 5.19.0-41.42~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed May 3 22:20:49 2023 InstallationDate: Installed on 2021-11-13 (535 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) SourcePackage: linux-signed-hwe-5.19 UpgradeStatus: Upgraded to jammy on 2022-11-24 (160 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.19/+bug/2018429/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2017774] Re: both dell_backlight and nvidia_0 backlight interface appear, and can't adjust the display brightness
This bug is awaiting verification that the linux-oem-6.0/6.0.0-1015.15 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' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. 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.0 verification-needed-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.0 in Ubuntu. https://bugs.launchpad.net/bugs/2017774 Title: both dell_backlight and nvidia_0 backlight interface appear, and can't adjust the display brightness Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.0 source package in Jammy: In Progress Bug description: [Impact] When switched to discrete mode in the BIOS, nvidia driver will create its own backlight interface(nvidia_0) to control the backlight, but at the same time dell-laptop creates its own backlight interface(dell_backlight), too. In discrete mode, dell_backlight interface doesn't work, and it leads to gnome chooses the wrong interface(dell_backlight) to control the backlight and then leads to the issue. [Fix] The acpi_video_backlight_use_native() helper function is introduced after v6.1 and nvidia driver will call this function if kernel provides it. This helper tells video_detect module that nvidia controls the backlight, so that dell-laptop won't create another backlight interface when it's loaded Below commits are all from v6.1-rc1 fb1836c91317 ACPI: video: Prefer native over vendor a5df42521f32 ACPI: video: Simplify __acpi_video_get_backlight_type()454d61a56d5e ACPI: video: Make acpi_video_backlight_use_native() always return true b39be9f441f9 ACPI: video: Refactor acpi_video_get_backlight_type() a bit a2fc3c899bb0 ACPI: video: Drop backlight_device_get_by_type() call from acpi_video_get_backlight_type() 2600bfa3df99 ACPI: video: Add acpi_video_backlight_use_native() helper [Test] Verified on the target machine and confirmed dell_backlight interface is not generated. [Where problem could occur] All changes are in __acpi_video_get_backlight_type() function and to make it smarter to decide which type of backlight interface should be created. The final result is pretty similar to the latest mainline version, if it introduce any regression we can add quirk to list those misjudged machines. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2017774/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2016388] Re: Kernel Panic on shutdown / reboot on NUC8I3BEH
The issue persists with 5.4.0-148 -- 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/2016388 Title: Kernel Panic on shutdown / reboot on NUC8I3BEH Status in linux package in Ubuntu: Confirmed Bug description: Kernel 5.4.0-146 panics on power-down (e.g. shutdown -P now) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-146-generic 5.4.0-146.163 ProcVersionSignature: Ubuntu 5.4.0-144.161-generic 5.4.229 Uname: Linux 5.4.0-144-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.26 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bbogart1051 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Sat Apr 15 09:07:33 2023 InstallationDate: Installed on 2019-02-09 (1526 days ago) InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Intel(R) Client Systems NUC8i3BEH ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-144-generic root=UUID=9c982b36-8142-4719-810a-e06f81cab223 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-144-generic N/A linux-backports-modules-5.4.0-144-generic N/A linux-firmware 1.187.38 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2022-06-30 (289 days ago) dmi.bios.date: 02/14/2023 dmi.bios.vendor: Intel Corp. dmi.bios.version: BECFL357.86A.0092.2023.0214.1114 dmi.board.name: NUC8BEB dmi.board.vendor: Intel Corporation dmi.board.version: J72693-304 dmi.chassis.type: 3 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrBECFL357.86A.0092.2023.0214.1114:bd02/14/2023:svnIntel(R)ClientSystems:pnNUC8i3BEH:pvrJ72753-303:rvnIntelCorporation:rnNUC8BEB:rvrJ72693-304:cvnIntelCorporation:ct3:cvr2.0: dmi.product.family: Intel NUC dmi.product.name: NUC8i3BEH dmi.product.sku: BOXNUC8i3BEH dmi.product.version: J72753-303 dmi.sys.vendor: Intel(R) Client Systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2016388/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2018330] Re: routel script gives shift errors
Web form kept defaulting to package "avahi" no matter how many times I typed in iproute2... ** Package changed: avahi (Ubuntu) => iproute2 (Ubuntu) -- 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/2018330 Title: routel script gives shift errors Status in iproute2 package in Ubuntu: New Bug description: The routel(8) shell script is meant to format the output of ip(8) commands for human viewing, but the script is not robust enough. Running 22.04.2 LTS jammy jellyfish, freshly installed on an AWS EC2 instance and then "apt upgrade"d. (It's headless and remote, so it can't submit bug reports. I generated an apport file, but have no other Ubuntu system that could re-parse it to submit the report. But it's here if it would be useful.) The iproute2 package is: iproute2: Installed: 5.15.0-1ubuntu2 Candidate: 5.15.0-1ubuntu2 Version table: *** 5.15.0-1ubuntu2 500 500 http://us-east-2.ec2.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status Here's the raw output of ip(8): $ ip route list table 0 default via 10.37.67.1 dev eth0 proto dhcp src 10.37.67.187 metric 100 10.37.64.2 via 10.37.67.1 dev eth0 proto dhcp src 10.37.67.187 metric 100 10.37.64.231 via 10.37.67.1 dev eth0 proto dhcp src 10.37.67.187 metric 100 10.37.65.30 via 10.37.67.1 dev eth0 proto dhcp src 10.37.67.187 metric 100 10.37.67.0/24 dev eth0 proto kernel scope link src 10.37.67.187 metric 100 10.37.67.1 dev eth0 proto dhcp scope link src 10.37.67.187 metric 100 local 10.37.67.187 dev eth0 table local proto kernel scope host src 10.37.67.187 broadcast 10.37.67.255 dev eth0 table local proto kernel scope link src 10.37.67.187 local 127.0.0.0/8 dev lo table local proto kernel scope host src 127.0.0.1 local 127.0.0.1 dev lo table local proto kernel scope host src 127.0.0.1 broadcast 127.255.255.255 dev lo table local proto kernel scope link src 127.0.0.1 ::1 dev lo proto kernel metric 256 pref medium fe80::/64 dev eth0 proto kernel metric 256 pref medium local ::1 dev lo table local proto kernel metric 0 pref medium local fe80::458:96ff:fe61:6829 dev eth0 table local proto kernel metric 0 pref medium multicast ff00::/8 dev eth0 table local proto kernel metric 256 pref medium Running routel, however, yields this: $ routel targetgateway sourceprotoscopedev tbl default 10.37.67.110.37.67.187 dhcpeth0 10.37.64.2 10.37.67.110.37.67.187 dhcpeth0 10.37.64.231 10.37.67.110.37.67.187 dhcpeth0 10.37.65.30 10.37.67.110.37.67.187 dhcpeth0 10.37.67.0/ 2410.37.67.187 kernel link eth0 10.37.67.1 10.37.67.187 dhcp link eth0 10.37.67.187 local10.37.67.187 kernel host eth0 local 10.37.67.255 broadcast10.37.67.187 kernel link eth0 local 127.0.0.0/ 8local 127.0.0.1 kernel host lo local 127.0.0.1 local 127.0.0.1 kernel host lo local 127.255.255.255 broadcast 127.0.0.1 kernel link lo local /usr/bin/routel: 48: shift: ::1 kernel lo fe80::/ 64 kerneleth0 ::1 local kernel lo local fe80::458:96ff:fe61:6829 local kernel eth0 local can't shift that many Splitting stdout and stderr for readability: $ routel 2> /tmp/err targetgateway sourceprotoscopedev tbl default 10.37.67.110.37.67.187 dhcpeth0 10.37.64.2 10.37.67.110.37.67.187 dhcpeth0 10.37.64.231 10.37.67.110.37.67.187 dhcpeth0 10.37.65.30 10.37.67.110.37.67.187 dhcpeth0 10.37.67.0/ 2410.37.67.187 kernel link eth0 10.37.67.1 10.37.67.187 dhcp link eth0 10.37.67.187 local10.37.67.187 kernel host eth0 local 10.37.67.255 broadcast10.37.67.187 kernel link eth0 local 127.0.0.0/ 8local 127.0.0.1 kernel host lo local 127.0.0.1 local 127.0.0.1 kernel host lo local 127.255.255.255 broadcast 127.0.0.1 kernel link lo local ::1 kernel lo
[Kernel-packages] [Bug 2018352] Re: Resolution wrong on external display when setting 100% scaling
** Also affects: nvidia-graphics-drivers-525 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-525 in Ubuntu. https://bugs.launchpad.net/bugs/2018352 Title: Resolution wrong on external display when setting 100% scaling Status in nvidia-graphics-drivers-525 package in Ubuntu: New Status in xorg package in Ubuntu: New Bug description: Resolution on external display is wrong when setting 100% scaling on it. It becomes too big, bigger than when set to 125% This happens with Xorg on Ubuntu 23.04 with NVIDIA GPU set as only GPU in the system ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 525.105.17 Tue Mar 28 18:02:59 UTC 2023 GCC version: gcc version 12.2.0 (Ubuntu 12.2.0-17ubuntu1) ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed May 3 08:27:32 2023 DistUpgraded: 2023-04-20 10:00:59,509 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: lunar DistroVariant: ubuntu DkmsStatus: nvidia/525.105.17, 6.2.0-20-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GA104M [GeForce RTX 3080 Mobile / Max-Q 8GB/16GB] [10de:24dc] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo GA104M [GeForce RTX 3080 Mobile / Max-Q 8GB/16GB] [17aa:3a58] InstallationDate: Installed on 2023-02-09 (82 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) MachineType: LENOVO 82N6 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic root=UUID=2a43fd27-b65c-4d7a-bc19-b001521b0771 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to lunar on 2023-04-20 (12 days ago) dmi.bios.date: 03/07/2023 dmi.bios.release: 1.60 dmi.bios.vendor: LENOVO dmi.bios.version: GKCN60WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0T76461 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion 7 16ACHg6 dmi.ec.firmware.release: 1.60 dmi.modalias: dmi:bvnLENOVO:bvrGKCN60WW:bd03/07/2023:br1.60:efr1.60:svnLENOVO:pn82N6:pvrLegion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0T76461WIN:cvnLENOVO:ct10:cvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6: dmi.product.family: Legion 7 16ACHg6 dmi.product.name: 82N6 dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6 dmi.product.version: Legion 7 16ACHg6 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.114-1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 23.0.2-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-525/+bug/2018352/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2018413] [NEW] package linux-headers-generic-hwe-22.04 6.2.0.20.20 failed to install/upgrade: problemas de dependencias - se deja sin configurar
Public bug reported: no carga de correctamente el kernel 6.2 ProblemType: Package DistroRelease: Ubuntu 23.04 Package: linux-headers-generic-hwe-22.04 6.2.0.20.20 ProcVersionSignature: Ubuntu 5.19.0-41.42-generic 5.19.17 Uname: Linux 5.19.0-41-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: luis 1012 F wireplumber /dev/snd/seq:luis 1009 F pipewire CRDA: N/A CasperMD5CheckResult: pass Date: Wed May 3 09:38:48 2023 ErrorMessage: problemas de dependencias - se deja sin configurar InstallationDate: Installed on 2022-06-27 (310 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: GPU Company GWTN156-11 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-41-generic root=UUID=a03bb4b3-88e7-4cb8-87ce-7b204ed63df4 ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.06-2ubuntu16 SourcePackage: linux-meta Title: package linux-headers-generic-hwe-22.04 6.2.0.20.20 failed to install/upgrade: problemas de dependencias - se deja sin configurar UpgradeStatus: Upgraded to lunar on 2023-05-02 (0 days ago) dmi.bios.date: 06/18/2021 dmi.bios.release: 0.5 dmi.bios.vendor: GPU Company dmi.bios.version: V0.5.0_P21S0M2E0F0L3B0T0P2G00A0U0D601_ENE dmi.board.asset.tag: Default string dmi.board.name: GPU Company dmi.board.vendor: GPU Company dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.ec.firmware.release: 1.5 dmi.modalias: dmi:bvnGPUCompany:bvrV0.5.0_P21S0M2E0F0L3B0T0P2G00A0U0D601_ENE:bd06/18/2021:br0.5:efr1.5:svnGPUCompany:pnGWTN156-11:pvrDefaultstring:rvnGPUCompany:rnGPUCompany:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring:sku: dmi.product.family: GWTN156-11 N Series dmi.product.name: GWTN156-11 dmi.product.sku: dmi.product.version: Default string dmi.sys.vendor: GPU Company ** Affects: linux-meta (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package lunar -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/2018413 Title: package linux-headers-generic-hwe-22.04 6.2.0.20.20 failed to install/upgrade: problemas de dependencias - se deja sin configurar Status in linux-meta package in Ubuntu: New Bug description: no carga de correctamente el kernel 6.2 ProblemType: Package DistroRelease: Ubuntu 23.04 Package: linux-headers-generic-hwe-22.04 6.2.0.20.20 ProcVersionSignature: Ubuntu 5.19.0-41.42-generic 5.19.17 Uname: Linux 5.19.0-41-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: luis 1012 F wireplumber /dev/snd/seq:luis 1009 F pipewire CRDA: N/A CasperMD5CheckResult: pass Date: Wed May 3 09:38:48 2023 ErrorMessage: problemas de dependencias - se deja sin configurar InstallationDate: Installed on 2022-06-27 (310 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: GPU Company GWTN156-11 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-41-generic root=UUID=a03bb4b3-88e7-4cb8-87ce-7b204ed63df4 ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.06-2ubuntu16 SourcePackage: linux-meta Title: package linux-headers-generic-hwe-22.04 6.2.0.20.20 failed to install/upgrade: problemas de dependencias - se deja sin configurar UpgradeStatus: Upgraded to lunar on 2023-05-02 (0 days ago) dmi.bios.date: 06/18/2021 dmi.bios.release: 0.5 dmi.bios.vendor: GPU Company dmi.bios.version: V0.5.0_P21S0M2E0F0L3B0T0P2G00A0U0D601_ENE dmi.board.asset.tag: Default string dmi.board.name: GPU Company dmi.board.vendor: GPU Company dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.ec.firmware.release: 1.5 dmi.modalias: dmi:bvnGPUCompany:bvrV0.5.0_P21S0M2E0F0L3B0T0P2G00A0U0D601_ENE:bd06/18/2021:br0.5:efr1.5:svnGPUCompany:pnGWTN156-11:pvrDefaultstring:rvnGPUCompany:rnGPUCompany:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring:sku: dmi.product.family: GWTN156-11 N Series dmi.product.name:
[Kernel-packages] [Bug 1812194] Re: rtnetlink.sh in net from ubuntu_kernel_selftests failed on KVM kernels (config not enabled)
** Merge proposal unlinked: https://code.launchpad.net/~agherzan/+git/adt-matrix-hints/+merge/442275 -- 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/1812194 Title: rtnetlink.sh in net from ubuntu_kernel_selftests failed on KVM kernels (config not enabled) Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux-kvm package in Ubuntu: New Status in linux source package in Bionic: Incomplete Status in linux-kvm source package in Bionic: New Status in linux source package in Focal: New Status in linux-kvm source package in Focal: New Status in linux source package in Groovy: New Status in linux-kvm source package in Groovy: New Status in linux source package in Hirsute: Won't Fix Status in linux-kvm source package in Hirsute: Won't Fix Bug description: This test failed because of the unsuccessful attempt to add a dummy device with ip link command: # devdummy="test-dummy0" # ip link add name "$devdummy" type dummy RTNETLINK answers: Operation not supported selftests: rtnetlink.sh RTNETLINK answers: Operation not supported Cannot find device "test-dummy0" FAIL: cannot add dummy interface not ok 1..10 selftests: rtnetlink.sh [FAIL] ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-1028-kvm 4.15.0-1028.28 ProcVersionSignature: User Name 4.15.0-1028.28-kvm 4.15.18 Uname: Linux 4.15.0-1028-kvm x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 Date: Thu Jan 17 10:21:02 2019 SourcePackage: linux-kvm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1812194/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1932549] Re: seltests/net: devlink port split failing in H-5.11 KVM kernels (Error sending command: devlink -j dev show)
** Merge proposal unlinked: https://code.launchpad.net/~agherzan/+git/adt-matrix-hints/+merge/442275 -- 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/1932549 Title: seltests/net: devlink port split failing in H-5.11 KVM kernels (Error sending command: devlink -j dev show) Status in ubuntu-kernel-tests: Confirmed Status in linux-kvm package in Ubuntu: Confirmed Status in linux-kvm source package in Hirsute: Won't Fix Bug description: Got the following selftests/net failure in Hirsute, cycle sru-20210531 : 03:28:51 DEBUG| [stdout] # selftests: net: devlink_port_split.py 03:28:51 DEBUG| [stdout] # Error sending command: devlink -j dev show 03:28:51 DEBUG| [stdout] # 03:28:51 DEBUG| [stdout] # Failed to connect to devlink Netlink 03:28:51 DEBUG| [stdout] # 03:28:51 DEBUG| [stdout] # Traceback (most recent call last): 03:28:51 DEBUG| [stdout] # File "/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/./devlink_port_split.py", line 277, in 03:28:51 DEBUG| [stdout] # main() 03:28:51 DEBUG| [stdout] # File "/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/./devlink_port_split.py", line 239, in main 03:28:51 DEBUG| [stdout] # assert stderr == "" 03:28:51 DEBUG| [stdout] # AssertionError 03:28:51 DEBUG| [stdout] not ok 43 selftests: net: devlink_port_split.py # exit=1 Noticed that it also failed in previous cycles (I'm not sure why I couldn't find a report...) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1932549/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1977827] Re: ftrace in ubuntu_kernel_selftests failed with "check if duplicate events are caught" on J-5.15 P9 / J-kvm
** Merge proposal unlinked: https://code.launchpad.net/~agherzan/+git/adt-matrix-hints/+merge/442275 -- 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/1977827 Title: ftrace in ubuntu_kernel_selftests failed with "check if duplicate events are caught" on J-5.15 P9 / J-kvm Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Jammy: Incomplete Bug description: Issue found on Jammy 5.15.0-36.37 with Power9 node baltar Test failed with: # [15] Generic dynamic event - check if duplicate events are caught [FAIL] Test Log: make: Entering directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/ftrace' TAP version 13 1..1 # selftests: ftrace: ftracetest # === Ftrace unit tests === # [1] Basic trace file check [PASS] # [2] Basic test for tracers [PASS] # [3] Basic trace clock test [PASS] # [4] Basic event tracing check [PASS] # [5] Change the ringbuffer size [PASS] # [6] Snapshot and tracing setting [PASS] # [7] trace_pipe and trace_marker[PASS] # [8] Test ftrace direct functions against tracers [UNRESOLVED] # [9] Test ftrace direct functions against kprobes [UNRESOLVED] # [10] Generic dynamic event - add/remove eprobe events [PASS] # [11] Generic dynamic event - add/remove kprobe events [PASS] # [12] Generic dynamic event - add/remove synthetic events [PASS] # [13] Generic dynamic event - selective clear (compatibility) [PASS] # [14] Generic dynamic event - generic clear event [PASS] # [15] Generic dynamic event - check if duplicate events are caught [FAIL] # [16] event tracing - enable/disable with event level files [PASS] # [17] event tracing - restricts events based on pid notrace filtering [PASS] # [18] event tracing - restricts events based on pid [PASS] # [19] event tracing - enable/disable with subsystem level files [PASS] # [20] event tracing - enable/disable with top level files [PASS] # [21] Test trace_printk from module [PASS] # [22] ftrace - function graph filters with stack tracer [PASS] # [23] ftrace - function graph filters [PASS] # [24] ftrace - function pid notrace filters [PASS] # [25] ftrace - function pid filters [PASS] # [26] ftrace - stacktrace filter command[PASS] # [27] ftrace - function trace with cpumask [PASS] # [28] ftrace - test for function event triggers [PASS] # [29] ftrace - function trace on module [PASS] # [30] ftrace - function profiling [PASS] # [31] ftrace - function profiler with function tracing [PASS] # [32] ftrace - test reading of set_ftrace_filter[PASS] # [33] ftrace - test for function traceon/off triggers [PASS] # [34] ftrace - test tracing error log support [PASS] # [35] Test creation and deletion of trace instances while setting an event [PASS] # [36] Test creation and deletion of trace instances [PASS] # [37] Kprobe dynamic event - adding and removing[PASS] # [38] Kprobe dynamic event - busy event check [PASS] # [39] Kprobe dynamic event with arguments [PASS] # [40] Kprobe event with comm arguments [PASS] # [41] Kprobe event string type argument [PASS] # [42] Kprobe event symbol argument [PASS] # [43] Kprobe event argument syntax [PASS] # [44] Kprobes event arguments with types[PASS] # [45] Kprobe event user-memory access [UNSUPPORTED] # [46] Kprobe event auto/manual naming [PASS] # [47] Kprobe dynamic event with function tracer [PASS] # [48] Create/delete multiprobe on kprobe event [PASS] # [49] Kprobe event parser error log check [PASS] # [50] Kretprobe dynamic event with arguments[PASS] # [51] Kretprobe dynamic event with maxactive[PASS] # [52] Kretprobe %return suffix test [PASS] # [53] Register/unregister many kprobe events[PASS] # [54] Kprobe profile[PASS] # [55] Uprobe event parser error log check [PASS] # [56] test for the preemptirqsoff tracer[UNSUPPORTED] # [57] Meta-selftest: Checkbashisms [PASS] # [58] Test wakeup tracer[PASS] # [59] Test wakeup RT tracer [PASS] # [60] event trigger - test inter-event histogram trigger expected fail actions [XFAIL] # [61] event trigger - test field variable support [PASS] # [62] event trigger - test multiple actions on hist trigger [PASS] # [63] event trigger - test inter-event histogram trigger onchange action [PASS] # [64] event trigger - test inter-event histogram trigger onmatch action [PASS] # [65] event trigger - test inter-event histogram trigger onmatch-onmax action [PASS] # [66] event trigger - test inter-event histogram trigger onmax action
[Kernel-packages] [Bug 2016920] Comment bridged from LTC Bugzilla
--- Comment From boris.m...@de.ibm.com 2023-05-03 11:10 EDT--- After further investigation, it looks like a backport of the fix to Ubuntu 22.04 would be too big in terms of size and effort (touching up to 59 files with around 4000 insertions/deletions). The only "easy" option would be a version bump to s390-tools v2.22 which is not possible for SRUs. Therefore, we are closing this bug as "will not fix" ==> Changing the status to CLOSED -- 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/2016920 Title: [UBUNTU 22.04] Standalone dump does not work on NVMe device Status in Ubuntu on IBM z Systems: Incomplete Status in linux package in Ubuntu: New Status in s390-tools package in Ubuntu: New Status in linux source package in Jammy: New Status in s390-tools source package in Jammy: New Status in linux source package in Kinetic: New Status in s390-tools source package in Kinetic: New Status in linux source package in Lunar: New Status in s390-tools source package in Lunar: New Bug description: Problem Description: I installed Ubuntu 22.04.1. and created a dump partition on an NVMe disk. However, this dump partition is not able to capture a dump: [414340.280553] kdump-tools[15167]: * unloaded kdump kernel [414376.146205] sysrq: Trigger a crash [414376.146215] Kernel panic - not syncing: sysrq triggered crash [414376.146218] CPU: 13 PID: 16009 Comm: bash Not tainted 5.15.0-69-generic #76-Ubuntu [414376.146222] Hardware name: IBM 3931 A01 704 (LPAR) [414376.146224] Call Trace: [414376.146225] [<000176c3e31a>] dump_stack_lvl+0x62/0x80 [414376.146233] [<000176c3913a>] panic+0x152/0x340 [414376.146237] [<0001768d5cfe>] sysrq_handle_crash+0x2e/0x30 [414376.146242] [<0001768d6952>] __handle_sysrq+0xf2/0x280 [414376.146245] [<0001768d7244>] write_sysrq_trigger+0x54/0x70 [414376.146248] [<000176597faa>] proc_reg_write+0x9a/0xf0 [414376.146252] [<0001764e64dc>] vfs_write+0xbc/0x280 [414376.146255] [<0001764e8a18>] ksys_write+0x68/0x100 [414376.146258] [<000176c4288c>] __do_syscall+0x1bc/0x1f0 [414376.146261] [<000176c4fc98>] system_call+0x78/0xa0 System version 9. Watchdog enabled. Running 'ZBootLoader' version '3.1.5' level 'D51C.D51C_328.13'. OK Success [2.131284] zdump: The dump process started for a 64-bit operating system Linux System Dumper starting Version 3.0 (64 bit) Linux version 5.15.27 (buildd@bos02-s390x-003) (gcc (Ubuntu 11.2.0-18ubuntu1) 11.2.0, GNU ld (GNU Binutils for Ubuntu) 2.38) #1 SMP Mon Mar 21 16:33:41 UTC 2022 ERROR: open /sys/firmware/ipl/device failed No such file or directory ERROR: Could not enable dump device Dump failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2016920/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2017929] Re: Kernel 5.15.0-71 fails to boot on Ubuntu 22.04 (possibly specific to Ryzen APUs)
I can confirm the issue as well. 5.15.0-70 boots fine, -71 stops with above error. System details: sudo inxi -v 2 System: Host: xxx Kernel: 5.15.0-70-generic x86_64 bits: 64 Desktop: GNOME 42.5 Distro: Ubuntu 22.04.2 LTS (Jammy Jellyfish) Machine: Type: Desktop Mobo: Micro-Star model: B450M MORTAR (MS-7B89) v: 1.0 serial: I816012785 UEFI: American Megatrends LLC. v: 1.I0 date: 07/27/2022 CPU: Info: quad core AMD Ryzen 5 2400G with Radeon Vega Graphics [MT MCP] speed (MHz): avg: 1600 min/max: 1600/3600 -- 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/2017929 Title: Kernel 5.15.0-71 fails to boot on Ubuntu 22.04 (possibly specific to Ryzen APUs) Status in linux package in Ubuntu: Confirmed Bug description: Since upgrading to 5.15.0-71 a couple of days ago, my PC sporadically fails to boot. I see the following error messages: "error: cannot allocate kernel buffer error: you need to load the kernel first. Press any key to continue..._ " I am then returned to the GRUB boot menu. This has also been experienced by two other AskUbuntu users: https://askubuntu.com/questions/1465460/after-kernel-update-error- cannot-allocate-kernel-buffer-you-need-to-load-kern . The common theme appears to be Ryzen APUs; two of us have 3400Gs and one has a 7600. In my case, the issue appears to be more likely to occur when I have to force-reboot because the system is frozen (due to a separate bug which I will link when I can find it again). But I have not yet reproduced it. Also the log files attached to this report may not contain relevant information as the last couple of boots worked correctly. I will try to capture a relevant kernel log now that I know this is a kernel issue. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-71-generic 5.15.0-71.78 ProcVersionSignature: Ubuntu 5.15.0-71.78-generic 5.15.92 Uname: Linux 5.15.0-71-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: matthew1288 F pulseaudio /dev/snd/controlC0: matthew1288 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Thu Apr 27 17:49:11 2023 InstallationDate: Installed on 2022-01-14 (467 days ago) InstallationMedia: Kubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: Micro-Star International Co., Ltd. MS-7B89 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-71-generic root=UUID=7348d288-7351-45cd-8da2-592c59a4f7dd ro quiet splash RelatedPackageVersions: linux-restricted-modules-5.15.0-71-generic N/A linux-backports-modules-5.15.0-71-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.12 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-05-26 (336 days ago) dmi.bios.date: 09/28/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 2.E3 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B450M MORTAR MAX (MS-7B89) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr2.E3:bd09/28/2021:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B89:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450MMORTARMAX(MS-7B89):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7B89 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 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/2017929/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1827980] Re: hyperv_synic in ubuntu_kvm_unit_tests timeout on B-KVM / openstack instance
Faced it on linux-kvm: SRU Cycle: 2023.04.17 Series: jammy Package: linux-kvm Version: 5.15.0-1033.38 Cloud: openstack Instance: cpu4-ram4-disk20 Region: scalingstack_bos02 Operation: sru ** Tags added: sru-20230417 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1827980 Title: hyperv_synic in ubuntu_kvm_unit_tests timeout on B-KVM / openstack instance Status in ubuntu-kernel-tests: New Status in linux-kvm package in Ubuntu: Confirmed Status in linux-oracle package in Ubuntu: Confirmed Bug description: Test timeout. # TESTNAME=hyperv_synic TIMEOUT=90s ACCEL= ./x86/run x86/hyperv_synic.flat -smp 2 -cpu kvm64,hv_vpindex,hv_synic -device hyperv-testdev timeout -k 1s --foreground 90s /usr/bin/qemu-system-x86_64 -nodefaults -device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial stdio -device pci-testdev -machine accel=kvm -kernel x86/hyperv_synic.flat -smp 2 -cpu kvm64,hv_vpindex,hv_synic -device hyperv-testdev # -initrd /tmp/tmp.LeYhxJZmHV qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:EDX.vme [bit 1] qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:EDX.vme [bit 1] enabling apic enabling apic paging enabled cr0 = 80010011 cr3 = 459000 cr4 = 20 enabling apic ncpus = 2 prepare qemu-system-x86_64: terminating on signal 15 from pid 1658 (timeout) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-1032-kvm 4.15.0-1032.32 ProcVersionSignature: User Name 4.15.0-1032.32-kvm 4.15.18 Uname: Linux 4.15.0-1032-kvm x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 Date: Tue May 7 03:36:32 2019 SourcePackage: linux-kvm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1827980/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1812194] Re: rtnetlink.sh in net from ubuntu_kernel_selftests failed on KVM kernels (config not enabled)
** Merge proposal linked: https://code.launchpad.net/~agherzan/+git/adt-matrix-hints/+merge/442275 -- 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/1812194 Title: rtnetlink.sh in net from ubuntu_kernel_selftests failed on KVM kernels (config not enabled) Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux-kvm package in Ubuntu: New Status in linux source package in Bionic: Incomplete Status in linux-kvm source package in Bionic: New Status in linux source package in Focal: New Status in linux-kvm source package in Focal: New Status in linux source package in Groovy: New Status in linux-kvm source package in Groovy: New Status in linux source package in Hirsute: Won't Fix Status in linux-kvm source package in Hirsute: Won't Fix Bug description: This test failed because of the unsuccessful attempt to add a dummy device with ip link command: # devdummy="test-dummy0" # ip link add name "$devdummy" type dummy RTNETLINK answers: Operation not supported selftests: rtnetlink.sh RTNETLINK answers: Operation not supported Cannot find device "test-dummy0" FAIL: cannot add dummy interface not ok 1..10 selftests: rtnetlink.sh [FAIL] ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-1028-kvm 4.15.0-1028.28 ProcVersionSignature: User Name 4.15.0-1028.28-kvm 4.15.18 Uname: Linux 4.15.0-1028-kvm x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 Date: Thu Jan 17 10:21:02 2019 SourcePackage: linux-kvm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1812194/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1932549] Re: seltests/net: devlink port split failing in H-5.11 KVM kernels (Error sending command: devlink -j dev show)
** Merge proposal linked: https://code.launchpad.net/~agherzan/+git/adt-matrix-hints/+merge/442275 -- 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/1932549 Title: seltests/net: devlink port split failing in H-5.11 KVM kernels (Error sending command: devlink -j dev show) Status in ubuntu-kernel-tests: Confirmed Status in linux-kvm package in Ubuntu: Confirmed Status in linux-kvm source package in Hirsute: Won't Fix Bug description: Got the following selftests/net failure in Hirsute, cycle sru-20210531 : 03:28:51 DEBUG| [stdout] # selftests: net: devlink_port_split.py 03:28:51 DEBUG| [stdout] # Error sending command: devlink -j dev show 03:28:51 DEBUG| [stdout] # 03:28:51 DEBUG| [stdout] # Failed to connect to devlink Netlink 03:28:51 DEBUG| [stdout] # 03:28:51 DEBUG| [stdout] # Traceback (most recent call last): 03:28:51 DEBUG| [stdout] # File "/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/./devlink_port_split.py", line 277, in 03:28:51 DEBUG| [stdout] # main() 03:28:51 DEBUG| [stdout] # File "/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/./devlink_port_split.py", line 239, in main 03:28:51 DEBUG| [stdout] # assert stderr == "" 03:28:51 DEBUG| [stdout] # AssertionError 03:28:51 DEBUG| [stdout] not ok 43 selftests: net: devlink_port_split.py # exit=1 Noticed that it also failed in previous cycles (I'm not sure why I couldn't find a report...) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1932549/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1977827] Re: ftrace in ubuntu_kernel_selftests failed with "check if duplicate events are caught" on J-5.15 P9 / J-kvm
** Merge proposal linked: https://code.launchpad.net/~agherzan/+git/adt-matrix-hints/+merge/442275 -- 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/1977827 Title: ftrace in ubuntu_kernel_selftests failed with "check if duplicate events are caught" on J-5.15 P9 / J-kvm Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Jammy: Incomplete Bug description: Issue found on Jammy 5.15.0-36.37 with Power9 node baltar Test failed with: # [15] Generic dynamic event - check if duplicate events are caught [FAIL] Test Log: make: Entering directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/ftrace' TAP version 13 1..1 # selftests: ftrace: ftracetest # === Ftrace unit tests === # [1] Basic trace file check [PASS] # [2] Basic test for tracers [PASS] # [3] Basic trace clock test [PASS] # [4] Basic event tracing check [PASS] # [5] Change the ringbuffer size [PASS] # [6] Snapshot and tracing setting [PASS] # [7] trace_pipe and trace_marker[PASS] # [8] Test ftrace direct functions against tracers [UNRESOLVED] # [9] Test ftrace direct functions against kprobes [UNRESOLVED] # [10] Generic dynamic event - add/remove eprobe events [PASS] # [11] Generic dynamic event - add/remove kprobe events [PASS] # [12] Generic dynamic event - add/remove synthetic events [PASS] # [13] Generic dynamic event - selective clear (compatibility) [PASS] # [14] Generic dynamic event - generic clear event [PASS] # [15] Generic dynamic event - check if duplicate events are caught [FAIL] # [16] event tracing - enable/disable with event level files [PASS] # [17] event tracing - restricts events based on pid notrace filtering [PASS] # [18] event tracing - restricts events based on pid [PASS] # [19] event tracing - enable/disable with subsystem level files [PASS] # [20] event tracing - enable/disable with top level files [PASS] # [21] Test trace_printk from module [PASS] # [22] ftrace - function graph filters with stack tracer [PASS] # [23] ftrace - function graph filters [PASS] # [24] ftrace - function pid notrace filters [PASS] # [25] ftrace - function pid filters [PASS] # [26] ftrace - stacktrace filter command[PASS] # [27] ftrace - function trace with cpumask [PASS] # [28] ftrace - test for function event triggers [PASS] # [29] ftrace - function trace on module [PASS] # [30] ftrace - function profiling [PASS] # [31] ftrace - function profiler with function tracing [PASS] # [32] ftrace - test reading of set_ftrace_filter[PASS] # [33] ftrace - test for function traceon/off triggers [PASS] # [34] ftrace - test tracing error log support [PASS] # [35] Test creation and deletion of trace instances while setting an event [PASS] # [36] Test creation and deletion of trace instances [PASS] # [37] Kprobe dynamic event - adding and removing[PASS] # [38] Kprobe dynamic event - busy event check [PASS] # [39] Kprobe dynamic event with arguments [PASS] # [40] Kprobe event with comm arguments [PASS] # [41] Kprobe event string type argument [PASS] # [42] Kprobe event symbol argument [PASS] # [43] Kprobe event argument syntax [PASS] # [44] Kprobes event arguments with types[PASS] # [45] Kprobe event user-memory access [UNSUPPORTED] # [46] Kprobe event auto/manual naming [PASS] # [47] Kprobe dynamic event with function tracer [PASS] # [48] Create/delete multiprobe on kprobe event [PASS] # [49] Kprobe event parser error log check [PASS] # [50] Kretprobe dynamic event with arguments[PASS] # [51] Kretprobe dynamic event with maxactive[PASS] # [52] Kretprobe %return suffix test [PASS] # [53] Register/unregister many kprobe events[PASS] # [54] Kprobe profile[PASS] # [55] Uprobe event parser error log check [PASS] # [56] test for the preemptirqsoff tracer[UNSUPPORTED] # [57] Meta-selftest: Checkbashisms [PASS] # [58] Test wakeup tracer[PASS] # [59] Test wakeup RT tracer [PASS] # [60] event trigger - test inter-event histogram trigger expected fail actions [XFAIL] # [61] event trigger - test field variable support [PASS] # [62] event trigger - test multiple actions on hist trigger [PASS] # [63] event trigger - test inter-event histogram trigger onchange action [PASS] # [64] event trigger - test inter-event histogram trigger onmatch action [PASS] # [65] event trigger - test inter-event histogram trigger onmatch-onmax action [PASS] # [66] event trigger - test inter-event histogram trigger onmax action [PASS]
[Kernel-packages] [Bug 1988711] Re: Update Broadcom Emulex FC HBA lpfc driver to 14.2.0.5
Hi Ketan, I found that the following patches are currently in our tree and revert the patches listed below. Revert Revert "scsi: lpfc: SLI path split: Refactor lpfc_iocbq" Revert "scsi: lpfc: SLI path split: Refactor fast and slow paths to native SLI4" Revert "scsi: lpfc: SLI path split: Refactor SCSI paths" Revert "scsi: lpfc: Fix locking for lpfc_sli_iocbq_lookup()" Revert "scsi: lpfc: Fix element offset in __lpfc_sli_release_iocbq_s4()" Revert "scsi: lpfc: Resolve some cleanup issues following SLI path refactoring" Patches not needed: a680a9298e7b scsi: lpfc: SLI path split: Refactor lpfc_iocbq 1b64aa9eae28 scsi: lpfc: SLI path split: Refactor fast and slow paths to native SLI4 3512ac094293 scsi: lpfc: SLI path split: Refactor SCSI paths c26bd6602e1d scsi: lpfc: Fix locking for lpfc_sli_iocbq_lookup() 84c6f99e3907 scsi: lpfc: Fix element offset in __lpfc_sli_release_iocbq_s4() e27f05147bff scsi: lpfc: Resolve some cleanup issues following SLI path refactoring Are there any other patches that have been reverted upstream that I need to know about? Most of the issues that I am seeing now are with iocb_cmpl being changed to cmd_cmpl. The "Revert" patches do the opposite and I doing the same. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1988711 Title: Update Broadcom Emulex FC HBA lpfc driver to 14.2.0.5 Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: In Progress Status in linux source package in Kinetic: Fix Released Bug description: [IMPACT/Justification] There are numerous bug fixes included in the more recent version of lpfc That Broadcom has asked to pull into Jammy and Kinetic to better support customers in the field who are using the GA kernel and cant or wont move to the HWE kernels. These all are limited to the lpfc driver itself, no patches to core code are requested. [FIX] A few of these were already landed in Jammy, and all but 6 (ones landed in 6.0 upstream) were already in Kinetic. b3d11f195cbb scsi: lpfc: Copyright updates for 14.2.0.5 patches 71faf8d30fdb scsi: lpfc: Update lpfc version to 14.2.0.5 b21c9deb1479 scsi: lpfc: Refactor lpfc_nvmet_prep_abort_wqe() into lpfc_sli_prep_abort_xri() ffc566411ade scsi: lpfc: Revert RSCN_MEMENTO workaround for misbehaved configuration ea92e173dc55 scsi: lpfc: Fix lost NVMe paths during LIF bounce stress test 2f67dc7970bc scsi: lpfc: Fix possible memory leak when failing to issue CMF WQE 0948a9c53860 scsi: lpfc: Remove extra atomic_inc on cmd_pending in queuecommand after VMID 35251b4d79db scsi: lpfc: Set PU field when providing D_ID in XMIT_ELS_RSP64_CX iocb f8191d40aa61 scsi: lpfc: Prevent buffer overflow crashes in debugfs with malformed user input 4ecc9b0271a7 scsi: lpfc: Fix uninitialized cqe field in lpfc_nvme_cancel_iocb() 1af48fffd7ff scsi: lpfc: Update lpfc version to 14.2.0.4 2e7e9c0c1ec0 scsi: lpfc: Allow reduced polling rate for nvme_admin_async_event cmd completion ea7bd1f39331 scsi: lpfc: Add more logging of cmd and cqe information for aborted NVMe cmds 336d63615466 scsi: lpfc: Fix port stuck in bypassed state after LIP in PT2PT topology b1b3440f437b scsi: lpfc: Resolve NULL ptr dereference after an ELS LOGO is aborted 6f808bd78e82 scsi: lpfc: Address NULL pointer dereference after starget_to_rport() e27f05147bff scsi: lpfc: Resolve some cleanup issues following SLI path refactoring 24e1f056677e scsi: lpfc: Resolve some cleanup issues following abort path refactoring 44ba9786b673 scsi: lpfc: Correct BDE type for XMIT_SEQ64_WQE in lpfc_ct_reject_event() a5b168efba21 scsi: lpfc: Add support for ATTO Fibre Channel devices 348efeca7487 scsi: lpfc: Rework lpfc_vmid_get_appid() to be protocol independent ed913cf4a533 scsi: lpfc: Commonize VMID code location fcb9e738667c scsi: lpfc: Update lpfc version to 14.2.0.3 a14396b6d139 scsi: lpfc: Use sg_dma_address() and sg_dma_len() macros for NVMe I/O e6f510414502 scsi: lpfc: Alter FPIN stat accounting logic de3ec318fee3 scsi: lpfc: Rework FDMI initialization after link up 5099478e436f scsi: lpfc: Change VMID registration to be based on fabric parameters dc8a71bd414f scsi: lpfc: Decrement outstanding gidft_inp counter if lpfc_err_lost_link() 4a0f4aff3ce5 scsi: lpfc: Use list_for_each_entry_safe() in rscn_recovery_check() 596fc8adb171 scsi: lpfc: Fix dmabuf ptr assignment in lpfc_ct_reject_event() ead76d4c09b8 scsi: lpfc: Inhibit aborts if external loopback plug is inserted b7e952cbc63c scsi: lpfc: Fix ndlp put following a LOGO completion ba3d58a1df46 scsi: lpfc: Fill in missing ndlp kref puts in error paths 84c6f99e3907 scsi: lpfc: Fix element offset in __lpfc_sli_release_iocbq_s4() 775266207105 scsi: lpfc: Correct BDE DMA address assignment for GEN_REQ_WQE cc28fac16ab7 scsi: lpfc: Fix split code for FLOGI on FCoE
[Kernel-packages] [Bug 2016065] Re: Internal 'Genesys Logic, Inc. Hub' disconnects from ASUS PN50 during boot
** Tags added: 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/2016065 Title: Internal 'Genesys Logic, Inc. Hub' disconnects from ASUS PN50 during boot Status in linux package in Ubuntu: Confirmed Bug description: Description: Ubuntu Lunar Lobster (development branch) Release: 23.04 libinput-bin: Installed: 1.22.1-1 Candidate: 1.22.1-1 Version table: *** 1.22.1-1 500 500 http://gb.archive.ubuntu.com/ubuntu lunar/main amd64 Packages 100 /var/lib/dpkg/status linux-image-generic: Installed: 6.2.0.20.20 Candidate: 6.2.0.20.20 Version table: *** 6.2.0.20.20 500 500 http://gb.archive.ubuntu.com/ubuntu lunar/main amd64 Packages 100 /var/lib/dpkg/status After upgrading to the 23.04 beta from 22.10 the system (an ASUS PN-50 mini-PC) became unresponsive to any (USB) keyboard or mouse input. This is still the case when the Ubuntu recovery option is chosen in the boot menu. Different USB keyboards and mice/plugging unplugging etc have no effect. The system boots all the way to the Ubuntu login screen and can be accessed via ssh. When booted into Windows all is still functioning correctly Unclear if this is a libinput problem, or lies elsewhere (kernel?) ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: libinput-bin 1.22.1-1 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown Date: Thu Apr 13 09:00:56 2023 DistUpgraded: 2023-04-10 16:30:22,175 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: lunar DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev c3) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Renoir [1043:87e7] InstallationDate: Installed on 2020-11-14 (879 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: ASUSTeK COMPUTER INC. MINIPC PN50 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic root=UUID=4837ff80-a59b-47c0-ae9d-811d54bad076 ro quiet splash vt.handoff=7 SourcePackage: libinput UpgradeStatus: Upgraded to lunar on 2023-04-10 (2 days ago) dmi.bios.date: 07/06/2022 dmi.bios.release: 6.24 dmi.bios.vendor: ASUSTeK COMPUTER INC. dmi.bios.version: 0624 dmi.board.asset.tag: Default string dmi.board.name: PN50 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: Default string dmi.chassis.type: 35 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnASUSTeKCOMPUTERINC.:bvr0624:bd07/06/2022:br6.24:svnASUSTeKCOMPUTERINC.:pnMINIPCPN50:pvr0624:rvnASUSTeKCOMPUTERINC.:rnPN50:rvrTobefilledbyO.E.M.:cvnDefaultstring:ct35:cvrDefaultstring:sku: dmi.product.family: Vivo PC dmi.product.name: MINIPC PN50 dmi.product.version: 0624 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.114-1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 23.0.2-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2016065/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2015827] Re: NFS performance issue while clearing the file access cache upon login
Hi @kleber-souza, @chengendu Thanks for your attention. Allow me give my perception of the impact of fixing "bug" LP: #2003053. The original patchset introduced *two* regressions. One, (NFS deathlock) that hit everybody - fixed by #2009325, but the remaining one, are now hitting those of use spawning new user processes frequently, causing new "login times" to be created and access cache zapped. As a result we are looking at 300-400% increase in *overall* NFS operations, making the current kernels unusable for production. We do not have that kind of head-room on our NFS servers. The result is, we are simply stuck with kernels prior to #2003053 fixes. With recent CVE fixes in current kernel, we have now also resorted to the option of building our own kernels. This is very counter-productive. I understand the use case for the changes that went into "bug" #20003053. The reason why I call this a "bug" (in quotes) is due to the fact, that the behaviour has been around for more than 15 years. While age alone is not a qualifier, I am just saying that this has been an accepted behaviour for that long. Furthermore #2003053 will only apply in environments where the NFS-server has a knowledge of users and their secondary groups and validates them for ACCESS calls. (ours don't) >From the original upstream commit message 0eb43812c0270ee3d005ff32f91f7d0a6c4943af : "While it is reasonable to expect that such group membership changes are rare, and that we do not want to optimise the cache to accommodate them, it is also not unreasonable for the user to expect that if they log out and log back in again, that the staleness would clear up". It is clear that a trade-off was considered, however the use case being a "user" (a physical interactive person), and not any service of any kind. I am quite certain that with a use case with a regression of 3-4x increase in NFS ops, this would not have gone in the way it was. I understand why sometimes there is are strong reasons to cherry-pick changes from upstream - or making your own changes. IMHO, I do not think the use case for #20003053 was strong enough to justify that. The main regression assessment for #20003053 was considered low, as it was upstream changes. We now know, this was not the case. And with that knowledge, and comparing it to the weak use case the changes was trying to address, it should have been the right decision to revert the changes. The suggested upstream changes to introduce a mount option to address this, should should be turned around. The option should be added for those wanting to zap/re-validate their access caches on re-login, but leave the default behaviour as is. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2015827 Title: NFS performance issue while clearing the file access cache upon login Status in linux package in Ubuntu: In Progress Bug description: The performance issue that has been observed may be attributed to an increase in NFS ACCESS operations, possibly due to a new mechanism introduced in the Linux 6.2-rc3 NFS client side. This mechanism clears the access cache as soon as the cache timestamp becomes older than the user's login time, with the primary objective of preventing the NFS client's access cache from becoming stale due to any changes made to the user's group membership on the server after the user has already logged in on the client. It's worth noting that POSIX only refreshes the user's supplementary group information upon login. Upstream has taken into consideration that users may reasonably expect the access cache to be cleared when they log out and log back in again, with all behavior returning to normal after the replacement. The performance overhead can be particularly noticeable when applications or users switch to other privileged users via commands such as "su" to operate on NFS-mounted folders. In such cases, the privileged user's login time will be renewed, and NFS ACCESS operations will need to be re-sent, potentially leading to performance degradation. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2015827/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2012661] Re: kernel BUG at lib/assoc_array.c:652!
Still seeing this with linux-image-5.15.0-71-generic5.15.0-71.78 -- 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/2012661 Title: kernel BUG at lib/assoc_array.c:652! Status in linux package in Ubuntu: Confirmed Bug description: I am seeing this in Ubuntu 22.04 with kernel 5.15.0-67.74: Mar 23 12:38:32 box kernel: [13399.080589] [ cut here ] Mar 23 12:38:32 box kernel: [13399.080596] kernel BUG at lib/assoc_array.c:652! Mar 23 12:38:32 box kernel: [13399.082833] invalid opcode: [#1] SMP PTI Mar 23 12:38:32 box kernel: [13399.084912] CPU: 27 PID: 3746279 Comm: kworker/27:3 Tainted: G OE 5.15.0-67-generic #74-Ubuntu Mar 23 12:38:32 box kernel: [13399.087091] Hardware name: HP ProLiant DL380 Gen9/ProLiant DL380 Gen9, BIOS P89 07/18/2022 Mar 23 12:38:32 box kernel: [13399.089195] Workqueue: cifsiod cifs_resolve_server [cifs] Mar 23 12:38:32 box kernel: [13399.091379] RIP: 0010:assoc_array_insert_into_terminal_node.isra.0+0x806/0xc20 Mar 23 12:38:32 box kernel: [13399.093480] Code: 4c 63 e2 44 8d 6a 01 49 83 fc 10 0f 87 d7 01 00 00 4c 8b 4d b8 44 89 ea 4b 8d 4c e1 10 e9 a7 fc ff ff 0f 0b 0f 0b 0f 0b 0f 0b <0f> 0b 0f 0b 48 c7 c7 e0 cf 4b 9c e8 ba 37 03 00 e9 53 f8 ff ff 0f Mar 23 12:38:32 box kernel: [13399.097735] RSP: 0018:c08e7a66fa20 EFLAGS: 00010286 Mar 23 12:38:32 box kernel: [13399.099790] RAX: 0002 RBX: RCX: 0001 Mar 23 12:38:32 box kernel: [13399.101871] RDX: 9d2275968000 RSI: 000f RDI: 0001 Mar 23 12:38:32 box kernel: [13399.103963] RBP: c08e7a66faa0 R08: 9d31e7cbda00 R09: 9d2275969b00 Mar 23 12:38:32 box kernel: [13399.106111] R10: 9cb6cfc93800 R11: 000c R12: 0001 Mar 23 12:38:32 box kernel: [13399.108209] R13: 000f R14: R15: 9d2275969b00 Mar 23 12:38:32 box kernel: [13399.110292] FS: () GS:9d14bfc4() knlGS: Mar 23 12:38:32 box kernel: [13399.112355] CS: 0010 DS: ES: CR0: 80050033 Mar 23 12:38:32 box kernel: [13399.114411] CR2: 7f3a9b9e4a58 CR3: 0012c8810005 CR4: 001706e0 Mar 23 12:38:32 box kernel: [13399.116461] Call Trace: Mar 23 12:38:32 box kernel: [13399.118452] Mar 23 12:38:32 box kernel: [13399.120455] assoc_array_insert+0x153/0x170 Mar 23 12:38:32 box kernel: [13399.122422] ? _raw_spin_lock+0x22/0x30 Mar 23 12:38:32 box kernel: [13399.124357] ? key_alloc+0x2e6/0x550 Mar 23 12:38:32 box kernel: [13399.126273] __key_link_begin+0x4c/0xb0 Mar 23 12:38:32 box kernel: [13399.128153] construct_alloc_key+0xdb/0x270 Mar 23 12:38:32 box kernel: [13399.130032] request_key_and_link+0x22c/0x320 Mar 23 12:38:32 box kernel: [13399.131867] ? dns_resolver_read+0x30/0x30 Mar 23 12:38:32 box kernel: [13399.133689] ? key_default_cmp+0x30/0x30 Mar 23 12:38:32 box kernel: [13399.135469] request_key_tag+0x49/0x90 Mar 23 12:38:32 box kernel: [13399.137241] dns_query+0x13d/0x250 Mar 23 12:38:32 box kernel: [13399.138989] dns_resolve_server_name_to_ip+0xb7/0x310 [cifs] Mar 23 12:38:32 box kernel: [13399.141130] ? scnprintf+0x4d/0x90 Mar 23 12:38:32 box kernel: [13399.142866] reconn_set_ipaddr_from_hostname+0x86/0x2b0 [cifs] Mar 23 12:38:32 box kernel: [13399.144654] ? finish_task_switch.isra.0+0x7e/0x280 Mar 23 12:38:32 box kernel: [13399.146412] cifs_resolve_server+0x2c/0x90 [cifs] Mar 23 12:38:32 box kernel: [13399.148176] process_one_work+0x22b/0x3d0 Mar 23 12:38:32 box kernel: [13399.149845] worker_thread+0x53/0x420 Mar 23 12:38:32 box kernel: [13399.151459] ? process_one_work+0x3d0/0x3d0 Mar 23 12:38:32 box kernel: [13399.153061] kthread+0x12a/0x150 Mar 23 12:38:32 box kernel: [13399.154631] ? set_kthread_struct+0x50/0x50 Mar 23 12:38:32 box kernel: [13399.156181] ret_from_fork+0x22/0x30 Mar 23 12:38:32 box kernel: [13399.157716] Mar 23 12:38:32 box kernel: [13399.159565] Modules linked in: xt_REDIRECT xt_state ip_vs_rr xt_ipvs ip_vs vxlan ip6_udp_tunnel udp_tunnel xt_policy xt_mark xt_u32 veth xt_nat xt_tcpudp xt_conntrack nft_chain_nat xt_MASQUERADE nf_nat nf_conntrack_netlink nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 xfrm_user xfrm_algo nft_counter xt_addrtype nft_compat nf_tables nfnetlink br_netfilter bridge stp llc cmac nls_utf8 cifs cifs_arc4 cifs_md4 binfmt_misc nfsv3 rpcsec_gss_krb5 nfsv4 nfs fscache netfs cpuid eset_rtp(OE-) overlay hpwdt nls_iso8859_1 intel_rapl_msr intel_rapl_common sb_edac ipmi_ssif x86_pkg_temp_thermal intel_powerclamp kvm_intel kvm crct10dif_pclmul ghash_clmulni_intel aesni_intel crypto_simd cryptd rapl intel_cstate mgag200 drm_kms_helper cec rc_core i2c_algo_bit fb_sys_fops syscopyarea sysfillrect ioatdma input_leds joydev hpilo sysimgblt dca acpi_ipmi
[Kernel-packages] [Bug 2015827] Re: NFS performance issue while clearing the file access cache upon login
** Tags added: patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2015827 Title: NFS performance issue while clearing the file access cache upon login Status in linux package in Ubuntu: In Progress Bug description: The performance issue that has been observed may be attributed to an increase in NFS ACCESS operations, possibly due to a new mechanism introduced in the Linux 6.2-rc3 NFS client side. This mechanism clears the access cache as soon as the cache timestamp becomes older than the user's login time, with the primary objective of preventing the NFS client's access cache from becoming stale due to any changes made to the user's group membership on the server after the user has already logged in on the client. It's worth noting that POSIX only refreshes the user's supplementary group information upon login. Upstream has taken into consideration that users may reasonably expect the access cache to be cleared when they log out and log back in again, with all behavior returning to normal after the replacement. The performance overhead can be particularly noticeable when applications or users switch to other privileged users via commands such as "su" to operate on NFS-mounted folders. In such cases, the privileged user's login time will be renewed, and NFS ACCESS operations will need to be re-sent, potentially leading to performance degradation. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2015827/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2008583] Re: VMware nested under KVM stopped working on 5.19 kernel on Ryzen: Invalid VMCB.
you can check it with bpftrace on kernel 5.19.0-41-generic #42~22.04.1-Ubuntu:
sudo bpftrace -e 'kprobe:__nested_vmcb_check_controls { printf("tlb_ctl: %d\n",
*((uint8 *)arg1+60) )}'
and it ends like this:
...
tlb_ctl: 1
tlb_ctl: 0
tlb_ctl: 0
tlb_ctl: 0
tlb_ctl: 0
tlb_ctl: 0
tlb_ctl: 0
tlb_ctl: 0
tlb_ctl: 3 <<
--
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/2008583
Title:
VMware nested under KVM stopped working on 5.19 kernel on Ryzen:
Invalid VMCB.
Status in linux package in Ubuntu:
Confirmed
Bug description:
My setup:
Host: Ubuntu Linux 22.04.1, kernel 5.15, Ryzen 5900x
Hypervisor: KVM
Windows VM with VMware Workstation 16
Running nested VMs in VMware works ok.
It fails if Linux host kernel is updated to 5.19 (22.04.2) with
MONITOR PANIC: Invalid VMCB.
VMware Workstation unrecoverable error: (vcpu-0)
vcpu-0:Invalid VMCB.
If I update to Workstation 17 it fails with
2023-02-24T15:21:35.112Z In(05) vmx The following features are required for
SVM support in VMware Workstation; however, these features are not available on
this host:
2023-02-24T15:21:35.112Z In(05) vmxFlush by ASID.
This host supports AMD-V, but the AMD-V implementation is incompatible with
VMware Workstation.
VMware Workstation does not support the user level monitor on this host.
Module 'MonitorMode' power on failed.
The same VM works ok on 5.19 kernel on my Intel PC.
So it has to do with updated Linux kernel and AMD virtualization and
VMware.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2008583/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2017929] Re: Kernel 5.15.0-71 fails to boot on Ubuntu 22.04 (possibly specific to Ryzen APUs)
AMD Ryzen 9 7950X, 16x 4.50GHz, 64MB L3-Cache (Zen4) | AM5 Gigabyte X670 Aorus Elite AX | AMD X670 | AM5 NVIDIA GeForce RTX 4090 24GB | MSI Gaming X Trio 64GB DDR5-5200 CL40 Corsair Vengeance LPX | 2x 32GB 1TB Samsung 980 PRO PCIe 4.0 | M.2 SSD 4TB Seagate IronWolf | 5.900 RPM | SATA3 1000W - Corsair HX Series HX1000i 2022 | 80Plus Platinum Ubuntu 22.04 LTS (jammy) [22.04.2] GNU/Linux 5.15.0-71-generic x86_64 Would consistently hang in the GRUB menu with the error of the bug report Would consistently boot fine after single CTRL-ALT-DEL I did the following things and now it boots normally again: apport-collect -p linux 2017929 [this fails to send for me with some bug] sudo nano /etc/default/grub [I changed one line "GRUB_TIMEOUT=0" to "GRUB_TIMEOUT=5"] sudo update-grub sudo update-initramfs -uk 'all' sudo shutdown -h now -- 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/2017929 Title: Kernel 5.15.0-71 fails to boot on Ubuntu 22.04 (possibly specific to Ryzen APUs) Status in linux package in Ubuntu: Confirmed Bug description: Since upgrading to 5.15.0-71 a couple of days ago, my PC sporadically fails to boot. I see the following error messages: "error: cannot allocate kernel buffer error: you need to load the kernel first. Press any key to continue..._ " I am then returned to the GRUB boot menu. This has also been experienced by two other AskUbuntu users: https://askubuntu.com/questions/1465460/after-kernel-update-error- cannot-allocate-kernel-buffer-you-need-to-load-kern . The common theme appears to be Ryzen APUs; two of us have 3400Gs and one has a 7600. In my case, the issue appears to be more likely to occur when I have to force-reboot because the system is frozen (due to a separate bug which I will link when I can find it again). But I have not yet reproduced it. Also the log files attached to this report may not contain relevant information as the last couple of boots worked correctly. I will try to capture a relevant kernel log now that I know this is a kernel issue. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-71-generic 5.15.0-71.78 ProcVersionSignature: Ubuntu 5.15.0-71.78-generic 5.15.92 Uname: Linux 5.15.0-71-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: matthew1288 F pulseaudio /dev/snd/controlC0: matthew1288 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Thu Apr 27 17:49:11 2023 InstallationDate: Installed on 2022-01-14 (467 days ago) InstallationMedia: Kubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: Micro-Star International Co., Ltd. MS-7B89 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-71-generic root=UUID=7348d288-7351-45cd-8da2-592c59a4f7dd ro quiet splash RelatedPackageVersions: linux-restricted-modules-5.15.0-71-generic N/A linux-backports-modules-5.15.0-71-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.12 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-05-26 (336 days ago) dmi.bios.date: 09/28/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 2.E3 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B450M MORTAR MAX (MS-7B89) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr2.E3:bd09/28/2021:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B89:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450MMORTARMAX(MS-7B89):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7B89 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 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/2017929/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1959215] Re: unshare test in ubuntu_stress_smoke_tests triggers "BUG: unable to handle page fault for address: 0000000000001cc8" on Impish with node vought
** Changed in: stress-ng Status: New => Won't Fix ** Changed in: stress-ng Status: Won't Fix => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1959215 Title: unshare test in ubuntu_stress_smoke_tests triggers "BUG: unable to handle page fault for address: 1cc8" on Impish with node vought Status in Stress-ng: Invalid Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Impish: Won't Fix Bug description: Issue found on Intel node "vought" with: * 5.13.0-28.31 * 5.13.0-27 * And possibly the 5.13.0-23 from the last cycle (this test didn't finish properly and marked as "Incomplete" back then, just like this cycle). For more earlier Impish kernels, this system was not tested with this test on them. The test will hang with unshare test in ubuntu_stress_smoke_tests: 12:39:39 DEBUG| [stdout] udp RETURNED 0 12:39:39 DEBUG| [stdout] udp PASSED 12:39:39 DEBUG| [stdout] udp-flood STARTING 12:39:41 DEBUG| [stdout] udp-flood RETURNED 0 12:39:41 DEBUG| [stdout] udp-flood PASSED 12:39:41 DEBUG| [stdout] unshare STARTING (Test hangs here) And eventually the test will be killed because of the timeout setting. stress-ng Test suite HEAD SHA1: b81116c Error can be found in dmesg: [ 2371.109961] BUG: unable to handle page fault for address: 1cc8 [ 2371.110074] #PF: supervisor read access in kernel mode [ 2371.114323] #PF: error_code(0x) - not-present page [ 2371.119931] PGD 0 P4D 0 [ 2371.125257] Oops: [#1] SMP NOPTI [ 2371.129247] CPU: 51 PID: 207256 Comm: stress-ng Tainted: P O 5.13.0-27-generic #29-Ubuntu [ 2371.133203] Hardware name: Intel Corporation S2600WFD/S2600WFD, BIOS SE5C620.86B.0D.01.0395.022720191340 02/27/2019 [ 2371.135887] RIP: 0010:__next_zones_zonelist+0x6/0x50 [ 2371.138525] Code: d0 0f 4e d0 3d ff 03 00 00 7f 0d 48 63 d2 5d 48 8b 04 d5 60 e5 35 af c3 31 c0 5d c3 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 55 <8b> 4f 08 48 89 f8 48 89 e5 48 85 d2 75 10 eb 1d 48 63 49 50 48 0f [ 2371.143813] RSP: 0018:a9c8b399fac0 EFLAGS: 00010282 [ 2371.146078] RAX: RBX: RCX: [ 2371.148293] RDX: 9c98e894ea98 RSI: 0002 RDI: 1cc0 [ 2371.150477] RBP: a9c8b399fb28 R08: R09: [ 2371.152650] R10: 0002 R11: d9bfbfcc5600 R12: 00052cc0 [ 2371.154778] R13: 0002 R14: 0001 R15: 00152cc0 [ 2371.156876] FS: 7fcbd141d740() GS:9cc14ccc() knlGS: [ 2371.158936] CS: 0010 DS: ES: CR0: 80050033 [ 2371.160958] CR2: 1cc8 CR3: 00059f292001 CR4: 007706e0 [ 2371.162950] DR0: DR1: DR2: [ 2371.164888] DR3: DR6: fffe0ff0 DR7: 0400 [ 2371.166811] PKRU: 5554 [ 2371.168694] Call Trace: [ 2371.170544] ? __alloc_pages+0x2f1/0x330 [ 2371.172386] kmalloc_large_node+0x45/0xb0 [ 2371.174222] __kmalloc_node+0x276/0x300 [ 2371.176036] ? queue_delayed_work_on+0x39/0x60 [ 2371.177853] kvmalloc_node+0x5a/0x90 [ 2371.179622] expand_one_shrinker_info+0x82/0x190 [ 2371.181382] prealloc_shrinker+0x175/0x1d0 [ 2371.183091] alloc_super+0x2bf/0x330 [ 2371.184764] ? __fput_sync+0x30/0x30 [ 2371.186384] sget_fc+0x74/0x2e0 [ 2371.187951] ? set_anon_super+0x50/0x50 [ 2371.189473] ? mqueue_create+0x20/0x20 [ 2371.190944] get_tree_keyed+0x34/0xd0 [ 2371.192363] mqueue_get_tree+0x1c/0x20 [ 2371.193734] vfs_get_tree+0x2a/0xc0 [ 2371.195105] fc_mount+0x13/0x50 [ 2371.196409] mq_init_ns+0x10a/0x1b0 [ 2371.197667] copy_ipcs+0x130/0x220 [ 2371.198899] create_new_namespaces+0xa6/0x2e0 [ 2371.200113] unshare_nsproxy_namespaces+0x5a/0xb0 [ 2371.201303] ksys_unshare+0x1db/0x3c0 [ 2371.202480] __x64_sys_unshare+0x12/0x20 [ 2371.203649] do_syscall_64+0x61/0xb0 [ 2371.204804] ? exit_to_user_mode_loop+0xec/0x160 [ 2371.205966] ? exit_to_user_mode_prepare+0x37/0xb0 [ 2371.207102] ? syscall_exit_to_user_mode+0x27/0x50 [ 2371.208222] ? __x64_sys_close+0x11/0x40 [ 2371.209336] ? do_syscall_64+0x6e/0xb0 [ 2371.210438] ? asm_exc_page_fault+0x8/0x30 [ 2371.211545] entry_SYSCALL_64_after_hwframe+0x44/0xae [ 2371.212641] RIP: 0033:0x7fcbd1562c4b [ 2371.213698] Code: 73 01 c3 48 8b 0d e5 e1 0e 00 f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa b8 10 01 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d b5 e1 0e 00 f7 d8 64 89 01 48 [ 2371.215851] RSP: 002b:7ffc5d8eb878 EFLAGS: 0246 ORIG_RAX: 0110 [ 2371.216846] RAX: ffda RBX: 7ffc5d8eba20 RCX:
[Kernel-packages] [Bug 1961076] Re: linux-hwe-5.4 ADT test failure (ubuntu_stress_smoke_test) with linux-hwe-5.4/5.4.0-100.113~18.04.1
** Changed in: stress-ng Status: New => Fix Released ** Changed in: stress-ng Assignee: (unassigned) => Colin Ian King (colin-king) ** Changed in: stress-ng Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.4 in Ubuntu. https://bugs.launchpad.net/bugs/1961076 Title: linux-hwe-5.4 ADT test failure (ubuntu_stress_smoke_test) with linux- hwe-5.4/5.4.0-100.113~18.04.1 Status in Stress-ng: Fix Released Status in ubuntu-kernel-tests: New Status in linux-hwe-5.4 package in Ubuntu: New Status in linux-hwe-5.4 source package in Bionic: New Bug description: The 'dev-shm' stress-ng test is failing with bionic/linux-hwe-5.4 5.4.0-100.113~18.04.1 on ADT, only on ppc64el. Testing failed on: ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/ppc64el/l/linux-hwe-5.4/20220216_115416_c1d6c@/log.gz 11:35:08 DEBUG| [stdout] stress-ng: debug: [26897] stress-ng 0.13.11 g48be8ff4ffc4 11:35:08 DEBUG| [stdout] stress-ng: debug: [26897] system: Linux autopkgtest 5.4.0-100-generic #113~18.04.1-Ubuntu SMP Mon Feb 7 15:02:55 UTC 2022 ppc64le 11:35:08 DEBUG| [stdout] stress-ng: debug: [26897] RAM total: 7.9G, RAM free: 3.3G, swap free: 1023.9M 11:35:08 DEBUG| [stdout] stress-ng: debug: [26897] 4 processors online, 4 processors configured 11:35:08 DEBUG| [stdout] stress-ng: info: [26897] setting to a 5 second run per stressor 11:35:08 DEBUG| [stdout] stress-ng: info: [26897] dispatching hogs: 4 dev-shm 11:35:08 DEBUG| [stdout] stress-ng: debug: [26897] cache allocate: using cache maximum level L1 11:35:08 DEBUG| [stdout] stress-ng: debug: [26897] cache allocate: shared cache buffer size: 32K 11:35:08 DEBUG| [stdout] stress-ng: debug: [26897] starting stressors 11:35:08 DEBUG| [stdout] stress-ng: debug: [26899] stress-ng-dev-shm: started [26899] (instance 0) 11:35:08 DEBUG| [stdout] stress-ng: debug: [26900] stress-ng-dev-shm: started [26900] (instance 1) 11:35:08 DEBUG| [stdout] stress-ng: debug: [26901] stress-ng-dev-shm: started [26901] (instance 2) 11:35:08 DEBUG| [stdout] stress-ng: debug: [26902] stress-ng-dev-shm: started [26902] (instance 3) 11:35:08 DEBUG| [stdout] stress-ng: debug: [26897] 4 stressors started 11:35:08 DEBUG| [stdout] stress-ng: debug: [26899] stress-ng-dev-shm: assuming killed by OOM killer, restarting again (instance 0) 11:35:08 DEBUG| [stdout] stress-ng: debug: [26902] stress-ng-dev-shm: assuming killed by OOM killer, restarting again (instance 3) 11:35:08 DEBUG| [stdout] stress-ng: debug: [26901] stress-ng-dev-shm: assuming killed by OOM killer, restarting again (instance 2) 11:35:08 DEBUG| [stdout] stress-ng: debug: [26900] stress-ng-dev-shm: assuming killed by OOM killer, restarting again (instance 1) 11:35:08 DEBUG| [stdout] stress-ng: debug: [26897] process [26899] (stress-ng-dev-shm) terminated on signal: 9 (Killed) 11:35:08 DEBUG| [stdout] stress-ng: debug: [26897] process [26899] (stress-ng-dev-shm) was killed by the OOM killer 11:35:08 DEBUG| [stdout] stress-ng: debug: [26897] process [26899] terminated 11:35:08 DEBUG| [stdout] stress-ng: debug: [26897] process [26900] (stress-ng-dev-shm) terminated on signal: 9 (Killed) 11:35:08 DEBUG| [stdout] stress-ng: debug: [26897] process [26900] (stress-ng-dev-shm) was possibly killed by the OOM killer 11:35:08 DEBUG| [stdout] stress-ng: debug: [26897] process [26900] terminated 11:35:08 DEBUG| [stdout] stress-ng: debug: [26901] stress-ng-dev-shm: exited [26901] (instance 2) 11:35:08 DEBUG| [stdout] stress-ng: debug: [26897] process [26901] terminated 11:35:08 DEBUG| [stdout] stress-ng: debug: [26897] process [26902] (stress-ng-dev-shm) terminated on signal: 9 (Killed) 11:35:08 DEBUG| [stdout] stress-ng: debug: [26897] process [26902] (stress-ng-dev-shm) was killed by the OOM killer 11:35:08 DEBUG| [stdout] stress-ng: debug: [26897] process [26902] terminated 11:35:08 DEBUG| [stdout] stress-ng: info: [26897] successful run completed in 5.06s 11:35:08 DEBUG| [stdout] stress-ng: fail: [26897] dev_shm instance 0 corrupted bogo-ops counter, 14 vs 0 11:35:08 DEBUG| [stdout] stress-ng: fail: [26897] dev_shm instance 0 hash error in bogo-ops counter and run flag, 2146579844 vs 0 11:35:08 DEBUG| [stdout] stress-ng: fail: [26897] dev_shm instance 1 corrupted bogo-ops counter, 13 vs 0 11:35:08 DEBUG| [stdout] stress-ng: fail: [26897] dev_shm instance 1 hash error in bogo-ops counter and run flag, 1093487894 vs 0 11:35:08 DEBUG| [stdout] stress-ng: fail: [26897] dev_shm instance 3 corrupted bogo-ops counter, 13 vs 0 11:35:08 DEBUG| [stdout] info: 5 failures reached, aborting stress process 11:35:08 DEBUG| [stdout] stress-ng: fail: [26897] dev_shm instance 3 hash error in bogo-ops counter and run flag, 1093487894 vs 0 11:35:08 DEBUG| [stdout] stress-ng: fail: [26897] metrics-check:
[Kernel-packages] [Bug 1999731] Re: disk stress test failing with code 7
** Changed in: stress-ng Status: In Progress => Fix Released ** Changed in: stress-ng Assignee: (unassigned) => Colin Ian King (colin-king) ** Changed in: stress-ng Importance: Undecided => Medium -- 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/1999731 Title: disk stress test failing with code 7 Status in Stress-ng: Fix Released Status in linux package in Ubuntu: Invalid Status in stress-ng package in Ubuntu: Fix Released Bug description: Since mid of November we see lots of disk stress test failing with multiple Ubuntu kernel e.g. bionic-hwe, focal, focal-hwe. Most of them are with lockofd stressor and system are still alive after stress test. 05 Nov 08:51: Running stress-ng lockofd stressor for 240 seconds... ** stress-ng exited with code 7 To manage notifications about this bug go to: https://bugs.launchpad.net/stress-ng/+bug/1999731/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1968361] Re: rawsock test BUG: soft lockup
** Changed in: stress-ng
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1968361
Title:
rawsock test BUG: soft lockup
Status in Linux:
Fix Released
Status in Stress-ng:
Fix Released
Status in linux package in Ubuntu:
Invalid
Bug description:
When running the rawsock stressor on large system with 32 CPUs and
above, I always hit soft lockup in the kernel, and sometime it will
lock up the system if running it for longtime. This issue is on all
major OSes that I tested: Ubunutu 20.04. RHEL7,8, SUSE 15
my system:
stress-ng V0.13.03-5-g9093bce7
#lscpu | grep CPU
CPU(s): 64
On-line CPU(s) list: 0-63
NUMA node0 CPU(s): 0-63
# ./stress-ng --rawsock 20 -t 5
stress-ng: info: [49748] setting to a 5 second run per stressor
stress-ng: info: [49748] dispatching hogs: 20 rawsock
Message from syslogd@rain65 at Apr 8 12:18:26 ...
kernel:watchdog: BUG: soft lockup - CPU#4 stuck for 22s! [stress-ng:49781]
If I run with --timeout 60 secs, it will lock up the systems.
The issue is lock starvation in the kernel:
- when stressor create an instance, forking a new child/client and
parent/server processes, recreating sockets for these processes. The kernel
acquires the Write lock for adding them to raw sock hash table.
- the client process immediately starts sending data in a do while {} loop.
The kernel acquires the Read Lock for accessing raw sock hash table, and
cloning the data packets for all raw socket processes.
- The main stress-ng process may still continue to create the rest of
instances. The kernel may hit the lock starvation (as error shown above)
- similar to it, when the timeout expires, the parents would try to close
their sockets, which the kernel also try to acquire the Write Lock, before
sending SIGKILL to their child processes. We may hit the lock starvation, since
clients have not closed their sockets and continue sending data.
I'm not sure this is intended, but to avoid the kernel lock starvation
in raw socket, I propose the simple patch attached. I has tested it a
large system with 128 CPUs without hitting any BUG: soft lock up.
Thanks,
Thinh Tran
To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1968361/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2015827] Re: NFS performance issue while clearing the file access cache upon login
The NFS patchset did resolve the issue our user encountered, but unfortunately introduced some performance overhead that may have significant impacts in certain scenarios. We wanted to let you know that we have submitted a patch (https://patchwork.kernel.org/project/linux-nfs/patch/20230411030248.53356-1-chengen...@canonical.com/) that we propose to address the issue. We are currently awaiting a response from the 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/2015827 Title: NFS performance issue while clearing the file access cache upon login Status in linux package in Ubuntu: In Progress Bug description: The performance issue that has been observed may be attributed to an increase in NFS ACCESS operations, possibly due to a new mechanism introduced in the Linux 6.2-rc3 NFS client side. This mechanism clears the access cache as soon as the cache timestamp becomes older than the user's login time, with the primary objective of preventing the NFS client's access cache from becoming stale due to any changes made to the user's group membership on the server after the user has already logged in on the client. It's worth noting that POSIX only refreshes the user's supplementary group information upon login. Upstream has taken into consideration that users may reasonably expect the access cache to be cleared when they log out and log back in again, with all behavior returning to normal after the replacement. The performance overhead can be particularly noticeable when applications or users switch to other privileged users via commands such as "su" to operate on NFS-mounted folders. In such cases, the privileged user's login time will be renewed, and NFS ACCESS operations will need to be re-sent, potentially leading to performance degradation. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2015827/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2015827] Re: NFS performance issue while clearing the file access cache upon login
Hello @kleber-souza. The regression was not fixed. There have only been mitigations. Please see our comments in the other bug report. All information required is available in the previous bug report, but I have attached a patchset that actually fixes the regression. ** Patch added: "Reverts upstream commits 21fd9e8700de86d1169f6336e97d7a74916ed04a, 029085b8949f5d269ae2bbd14915407dd0c7f902, and 0eb43812c0270ee3d005ff32f91f7d0a6c4943af" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2015827/+attachment/5670602/+files/nfs-regression-fix-1.diff -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2015827 Title: NFS performance issue while clearing the file access cache upon login Status in linux package in Ubuntu: In Progress Bug description: The performance issue that has been observed may be attributed to an increase in NFS ACCESS operations, possibly due to a new mechanism introduced in the Linux 6.2-rc3 NFS client side. This mechanism clears the access cache as soon as the cache timestamp becomes older than the user's login time, with the primary objective of preventing the NFS client's access cache from becoming stale due to any changes made to the user's group membership on the server after the user has already logged in on the client. It's worth noting that POSIX only refreshes the user's supplementary group information upon login. Upstream has taken into consideration that users may reasonably expect the access cache to be cleared when they log out and log back in again, with all behavior returning to normal after the replacement. The performance overhead can be particularly noticeable when applications or users switch to other privileged users via commands such as "su" to operate on NFS-mounted folders. In such cases, the privileged user's login time will be renewed, and NFS ACCESS operations will need to be re-sent, potentially leading to performance degradation. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2015827/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2017706] Re: Focal update: Focal update: v5.4.235 upstream stable release
** Changed in: linux (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2017706 Title: Focal update: Focal update: v5.4.235 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: Focal update: v5.4.235 upstream stable release from git://git.kernel.org/ HID: asus: Remove check for same LED brightness on set HID: asus: use spinlock to protect concurrent accesses HID: asus: use spinlock to safely schedule workers ARM: OMAP2+: Fix memory leak in realtime_counter_init() arm64: dts: qcom: qcs404: use symbol names for PCIe resets ARM: zynq: Fix refcount leak in zynq_early_slcr_init arm64: dts: meson-gx: Fix Ethernet MAC address unit name arm64: dts: meson-g12a: Fix internal Ethernet PHY unit name arm64: dts: meson-gx: Fix the SCPI DVFS node name and unit address arm64: dts: meson: remove CPU opps below 1GHz for G12A boards ARM: OMAP1: call platform_device_put() in error case in omap1_dm_timer_init() ARM: dts: exynos: correct wr-active property in Exynos3250 Rinato ARM: imx: Call ida_simple_remove() for ida_simple_get arm64: dts: amlogic: meson-gx: fix SCPI clock dvfs node name arm64: dts: amlogic: meson-axg: fix SCPI clock dvfs node name arm64: dts: amlogic: meson-gx: add missing SCPI sensors compatible arm64: dts: amlogic: meson-gx: add missing unit address to rng node name arm64: dts: amlogic: meson-gxl: add missing unit address to eth-phy-mux node name arm64: dts: amlogic: meson-gxl-s905d-phicomm-n1: fix led node name ARM: dts: imx7s: correct iomuxc gpr mux controller cells arm64: dts: mediatek: mt7622: Add missing pwm-cells to pwm node Revert "scsi: core: run queue if SCSI device queue isn't ready and queue is idle" block: Limit number of items taken from the I/O scheduler in one go blk-mq: remove stale comment for blk_mq_sched_mark_restart_hctx blk-mq: wait on correct sbitmap_queue in blk_mq_mark_tag_wait blk-mq: correct stale comment of .get_budget s390/dasd: Prepare for additional path event handling s390/dasd: Fix potential memleak in dasd_eckd_init() sched/deadline,rt: Remove unused parameter from pick_next_[rt|dl]_entity() sched/rt: pick_next_rt_entity(): check list_entry block: bio-integrity: Copy flags when bio_integrity_payload is cloned wifi: rsi: Fix memory leak in rsi_coex_attach() net/wireless: Delete unnecessary checks before the macro call “dev_kfree_skb” wifi: iwlegacy: common: don't call dev_kfree_skb() under spin_lock_irqsave() wifi: libertas: fix memory leak in lbs_init_adapter() wifi: rtl8xxxu: don't call dev_kfree_skb() under spin_lock_irqsave() rtlwifi: fix -Wpointer-sign warning wifi: rtlwifi: Fix global-out-of-bounds bug in _rtl8812ae_phy_set_txpower_limit() ipw2x00: switch from 'pci_' to 'dma_' API wifi: ipw2x00: don't call dev_kfree_skb() under spin_lock_irqsave() wifi: ipw2200: fix memory leak in ipw_wdev_init() wilc1000: let wilc_mac_xmit() return NETDEV_TX_OK wifi: wilc1000: fix potential memory leak in wilc_mac_xmit() wifi: brcmfmac: fix potential memory leak in brcmf_netdev_start_xmit() wifi: brcmfmac: unmap dma buffer in brcmf_msgbuf_alloc_pktid() wifi: libertas_tf: don't call kfree_skb() under spin_lock_irqsave() wifi: libertas: if_usb: don't call kfree_skb() under spin_lock_irqsave() wifi: libertas: main: don't call kfree_skb() under spin_lock_irqsave() wifi: libertas: cmdresp: don't call kfree_skb() under spin_lock_irqsave() wifi: wl3501_cs: don't call kfree_skb() under spin_lock_irqsave() crypto: x86/ghash - fix unaligned access in ghash_setkey() ACPICA: Drop port I/O validation for some regions genirq: Fix the return type of kstat_cpu_irqs_sum() lib/mpi: Fix buffer overrun when SG is too long ACPICA: nsrepair: handle cases without a return value correctly wifi: orinoco: check return value of hermes_write_wordrec() wifi: ath9k: htc_hst: free skb in ath9k_htc_rx_msg() if there is no callback function ath9k: hif_usb: simplify if-if to if-else ath9k: htc: clean up statistics macros wifi: ath9k: hif_usb: clean up skbs if ath9k_hif_usb_rx_stream() fails wifi: ath9k: Fix potential stack-out-of-bounds write in ath9k_wmi_rsp_callback() ACPI: battery: Fix missing NUL-termination with large strings crypto: ccp - Failure on
[Kernel-packages] [Bug 2009243] Re: kernel 5.19.0-35 clobbers Creative S/B AE-7 Sound Card
Soundcard detected and worked well on 6.0.0 OEM kernel. On older 5.19.0-41 not detected. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2009243 Title: kernel 5.19.0-35 clobbers Creative S/B AE-7 Sound Card Status in linux package in Ubuntu: Confirmed Status in linux-hwe-5.19 package in Ubuntu: Confirmed Bug description: 2023-03-03 Attempted install of kernel 5.19.0-35 using the Linux Mint package installer LM 21.1 Vera, release 21.1). Clobbered my Sound Blaster AE-7. Could not even locate the device using Sound manager utility on Linux Mint Panel (the enumerated device showed up as the embedded sound chip on the mobo which I had previously disabled in the UEFI setup). Uninstalled kernel and reverted back to 5.19.0-32 using Timeshift restore feature which worked fine before the update to 5.19.0-35. Tried again to install 5.19.0-35 the same way, just to be sure. The SB AE-7 got clobbered again. So restored back to 5.19.0-32 generic one more time, using Timeshift. SB AE-7 works fine now with this lower version kernel. Current hardware config: Asus Prime Z790-P wifi mobo. Intel Core i3-13100 processor (with Intel UHD 730 graphics). Corsair Vengeance DDR5 32gb (2x16) ram, 5200Mhz. 3 x Nvme SSD. Boot drive is Western Digital Black SN770 500gb. Asus Nvidia RTX-3050 PCIe graphics card. Creative Labs Sound Blaster AE-7 audio card (PCIe). On-board audio chip (Realtek 7.1 Surround Sound High Definition Audio) is disabled in UEFI. UEFI is AMI/BIOS, revision 0812. Linux Mint 21.1 is running on barebones hardware, no VM involved. No other O/S's are installed on the machine. - Running sudo lspci -vnvn > lspci-vnvn.log gave the following error message... pcilib: sysfs_read_vpd: read failed: No such device --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: mikey 4106 F wireplumber /dev/snd/controlC0: mikey 4106 F wireplumber /dev/snd/seq:mikey 4105 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 21.1 InstallationDate: Installed on 2023-01-31 (32 days ago) InstallationMedia: Linux Mint 21.1 "Vera" - Release amd64 20221217 MachineType: ASUS System Product Name NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-32-generic root=UUID=854c280c-7c5c-494d-a304-db66cf592baf ro quiet splash ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.19.0-32-generic N/A linux-backports-modules-5.19.0-32-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.10 Tags: vera Uname: Linux 5.19.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/24/2023 dmi.bios.release: 8.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0812 dmi.board.asset.tag: Default string dmi.board.name: PRIME Z790-P WIFI dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0812:bd02/24/2023:br8.12:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ790-PWIFI:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009243/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2017691] Re: Focal update: v5.4.234 upstream stable release
** Changed in: linux (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2017691 Title: Focal update: v5.4.234 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.4.234 upstream stable release from git://git.kernel.org/ arm64: dts: rockchip: drop unused LED mode property from rk3328-roc-cc ARM: dts: rockchip: add power-domains property to dp node on rk3288 ACPI: NFIT: fix a potential deadlock during NFIT teardown btrfs: send: limit number of clones and allocated memory size IB/hfi1: Assign npages earlier neigh: make sure used and confirmed times are valid HID: core: Fix deadloop in hid_apply_multiplier. bpf: bpf_fib_lookup should not return neigh in NUD_FAILED state net: Remove WARN_ON_ONCE(sk->sk_forward_alloc) from sk_stream_kill_queues(). vc_screen: don't clobber return value in vcs_read dmaengine: sh: rcar-dmac: Check for error num after dma_set_max_seg_size USB: serial: option: add support for VW/Skoda "Carstick LTE" USB: core: Don't hold device lock while reading the "descriptors" sysfs file Linux 5.4.234 UBUNTU: Upstream stable to v5.4.234 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2017691/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2018355] 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/2018355 Title: Smartpqi module build fails after upgrade to Lunar Status in linux package in Ubuntu: Confirmed Bug description: I'm using Microchip (Adaptec) SmartRAID 3101-4i controller since many versions with ubuntu-server. This is using the smartpqi-dkms drivers from Adaptec. After upgrade to Lunar (Kernel 6.2.0-20-generic) the modules fail to build, causing boot issues and errors during package updates. See attached crash log as well. Not sure if this should be addressed here or to the driver vendor. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: linux-image-6.2.0-20-generic 6.2.0-20.20 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 1 19:14 seq crw-rw 1 root audio 116, 33 May 1 19:14 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.26.1-0ubuntu2 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: pass CloudArchitecture: x86_64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config Date: Wed May 3 08:33:04 2023 InstallationDate: Installed on 2023-04-30 (2 days ago) InstallationMedia: Ubuntu-Server 23.04 "Lunar Lobster" - Release amd64 (20230415) 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 003: ID 0557:2419 ATEN International Co., Ltd Virtual mouse/keyboard device Bus 001 Device 002: ID 0557:7000 ATEN International Co., Ltd 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 |__ Port 14: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M |__ Port 1: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M |__ Port 1: Dev 3, If 1, Class=Human Interface Device, Driver=usbhid, 1.5M MachineType: Thomas-Krenn.AG 2HE Intel Single-CPU RI1204H-XE Server PciMultimedia: ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic root=UUID=40607179-83cd-4e58-9d17-318412284efb ro modprobe.blacklist=aacraid RelatedPackageVersions: linux-restricted-modules-6.2.0-20-generic N/A linux-backports-modules-6.2.0-20-generic N/A linux-firmwareN/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/17/2020 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X11SCH-LN4F dmi.board.vendor: Supermicro dmi.board.version: 1.01 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 17 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.5:bd11/17/2020:br5.13:svnThomas-Krenn.AG:pn2HEIntelSingle-CPURI1204H-XEServer:pvr0123456789:rvnSupermicro:rnX11SCH-LN4F:rvr1.01:cvnSupermicro:ct17:cvr0123456789:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: 2HE Intel Single-CPU RI1204H-XE Server dmi.product.sku: To be filled by O.E.M. dmi.product.version: 0123456789 dmi.sys.vendor: Thomas-Krenn.AG To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2018355/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2018355] [NEW] Smartpqi module build fails after upgrade to Lunar
Public bug reported: I'm using Microchip (Adaptec) SmartRAID 3101-4i controller since many versions with ubuntu-server. This is using the smartpqi-dkms drivers from Adaptec. After upgrade to Lunar (Kernel 6.2.0-20-generic) the modules fail to build, causing boot issues and errors during package updates. See attached crash log as well. Not sure if this should be addressed here or to the driver vendor. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: linux-image-6.2.0-20-generic 6.2.0-20.20 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 1 19:14 seq crw-rw 1 root audio 116, 33 May 1 19:14 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.26.1-0ubuntu2 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: pass CloudArchitecture: x86_64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config Date: Wed May 3 08:33:04 2023 InstallationDate: Installed on 2023-04-30 (2 days ago) InstallationMedia: Ubuntu-Server 23.04 "Lunar Lobster" - Release amd64 (20230415) 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 003: ID 0557:2419 ATEN International Co., Ltd Virtual mouse/keyboard device Bus 001 Device 002: ID 0557:7000 ATEN International Co., Ltd 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 |__ Port 14: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M |__ Port 1: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M |__ Port 1: Dev 3, If 1, Class=Human Interface Device, Driver=usbhid, 1.5M MachineType: Thomas-Krenn.AG 2HE Intel Single-CPU RI1204H-XE Server PciMultimedia: ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic root=UUID=40607179-83cd-4e58-9d17-318412284efb ro modprobe.blacklist=aacraid RelatedPackageVersions: linux-restricted-modules-6.2.0-20-generic N/A linux-backports-modules-6.2.0-20-generic N/A linux-firmwareN/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/17/2020 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X11SCH-LN4F dmi.board.vendor: Supermicro dmi.board.version: 1.01 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 17 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.5:bd11/17/2020:br5.13:svnThomas-Krenn.AG:pn2HEIntelSingle-CPURI1204H-XEServer:pvr0123456789:rvnSupermicro:rnX11SCH-LN4F:rvr1.01:cvnSupermicro:ct17:cvr0123456789:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: 2HE Intel Single-CPU RI1204H-XE Server dmi.product.sku: To be filled by O.E.M. dmi.product.version: 0123456789 dmi.sys.vendor: Thomas-Krenn.AG ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug lunar ** Attachment added: "smartpqi crash log" https://bugs.launchpad.net/bugs/2018355/+attachment/5670552/+files/smartpqi-dkms.0.crash -- 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/2018355 Title: Smartpqi module build fails after upgrade to Lunar Status in linux package in Ubuntu: Confirmed Bug description: I'm using Microchip (Adaptec) SmartRAID 3101-4i controller since many versions with ubuntu-server. This is using the smartpqi-dkms drivers from Adaptec. After upgrade to Lunar (Kernel 6.2.0-20-generic) the modules fail to build, causing boot issues and errors during package updates. See attached crash log as well. Not sure if this should be addressed here or to the driver vendor. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: linux-image-6.2.0-20-generic 6.2.0-20.20 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 1 19:14 seq crw-rw 1 root audio 116, 33 May 1 19:14 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
[Kernel-packages] [Bug 2015741] Re: efivarfs:efivarfs.sh in ubuntu_kernel_selftests crash L-6.2 ARM64 node dazzle (rcu_preempt detected stalls)
Closing this as the kernel bug has been marked as fixed (and dazzle is dead) ** Changed in: ubuntu-kernel-tests Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2015741 Title: efivarfs:efivarfs.sh in ubuntu_kernel_selftests crash L-6.2 ARM64 node dazzle (rcu_preempt detected stalls) Status in ubuntu-kernel-tests: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: Issue found on 6.2.0-20.20 ARM64 instances "dazzle" only. Looks like the efivarfs:efivarfs.sh will never finish properly and the whole test will be interrupted abnormally. Test log: Running 'make run_tests -C efivarfs TEST_PROGS=efivarfs.sh TEST_GEN_PROGS='' TEST_CUSTOM_PROGS=''' make: Entering directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/efivarfs' TAP version 13 1..1 # selftests: efivarfs: efivarfs.sh # # running test_create # Timer expired (5400 sec.), nuking pid 21170 This issue can be found since 6.2.0-19.19 This node was not tested with 6.2.0-18.18 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2015741/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1981590] Re: Kernel 5.15 hangs at "Loading initial ramdisk"
Same issue here. Suddenly my OS (Xubuntu 22.04) shows this issue (Kernel: 5.15.0-71-generic). But when I boot with the previous version (5.15.0-70-generic) it is OK (!). Note: my computer boot mode is set to Legacy (not UEFI). Motherboard: 'ASRock A320M-HDV R4.0' (BIOS v4.00). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1981590 Title: Kernel 5.15 hangs at "Loading initial ramdisk" Status in linux-signed-hwe-5.13 package in Ubuntu: Confirmed Status in linux-signed-hwe-5.15 package in Ubuntu: Confirmed Bug description: Updated from kernel 5.13 to 5.15 today. After rebooting the system hangs at "Loading ramdisk". I reverted to 5.13 and it started properly. More detail on the way. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.13.0-52-generic 5.13.0-52.59~20.04.1 ProcVersionSignature: Ubuntu 5.13.0-52.59~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-52-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jul 13 14:48:42 2022 InstallationDate: Installed on 2021-01-06 (553 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: linux-signed-hwe-5.13 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.13/+bug/1981590/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1989044] Re: RPL: Add INT3400 base path
** Changed in: thermald (Ubuntu Jammy) Status: New => In Progress ** Changed in: thermald (Ubuntu Jammy) Assignee: (unassigned) => koba (kobako) ** Changed in: thermald (Ubuntu) Assignee: koba (kobako) => (unassigned) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1989044 Title: RPL: Add INT3400 base path Status in thermald package in Ubuntu: New Status in thermald source package in Jammy: In Progress Bug description: [Impact] * Add INT3400 base path for Raptor Lake CPU. [Test Plan] * Use a machine with a Raptor Lake cpu. * check the thermald log. * Get the base path of INT3400. [Where problems could occur] * This change is to add path in INT3400 for Raptor Lake, which won't impact other hardware. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1989044/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2017227] Re: package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to install/upgrade: »installiertes post-installation-Skript des Paketes linux-headers-6.2.0-20-generic«-Un
Removing dkms, changing the kernel, and reinstalling it worked. Thank you. -- 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/2017227 Title: package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to install/upgrade: »installiertes post-installation-Skript des Paketes linux-headers-6.2.0-20-generic«-Unterprozess gab den Fehlerwert 1 zurück Status in linux package in Ubuntu: Invalid Bug description: I got an error message during updating from Ubuntu 22.10 to 23.04 ProblemType: Package DistroRelease: Ubuntu 23.04 Package: linux-headers-6.2.0-20-generic 6.2.0-20.20 ProcVersionSignature: Ubuntu 5.19.0-40.41-generic 5.19.17 Uname: Linux 5.19.0-40-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jaeger 2885 F wireplumber /dev/snd/seq:jaeger 2882 F pipewire CRDA: N/A CasperMD5CheckResult: pass Date: Fri Apr 21 11:52:56 2023 ErrorMessage: »installiertes post-installation-Skript des Paketes linux-headers-6.2.0-20-generic«-Unterprozess gab den Fehlerwert 1 zurück InstallationDate: Installed on 2022-12-06 (135 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Dell Inc. Latitude 5530 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-40-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1 PythonDetails: /usr/bin/python3.11, Python 3.11.2, python-is-python3, 3.11.1-3 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: grub-pc 2.06-2ubuntu16 SourcePackage: linux Title: package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to install/upgrade: »installiertes post-installation-Skript des Paketes linux-headers-6.2.0-20-generic«-Unterprozess gab den Fehlerwert 1 zurück UpgradeStatus: Upgraded to lunar on 2023-04-21 (0 days ago) dmi.bios.date: 03/17/2023 dmi.bios.release: 1.12 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.0 dmi.board.name: 0C6CYC dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.0:bd03/17/2023:br1.12:svnDellInc.:pnLatitude5530:pvr:rvnDellInc.:rn0C6CYC:rvrA00:cvnDellInc.:ct10:cvr:sku0B06: dmi.product.family: Latitude dmi.product.name: Latitude 5530 dmi.product.sku: 0B06 dmi.sys.vendor: Dell Inc. modified.conffile..etc.apport.report-ignore.README.denylist: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2017227/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2017227] Re: package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to install/upgrade: »installiertes post-installation-Skript des Paketes linux-headers-6.2.0-20-generic«-Un
** Attachment added: "make.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2017227/+attachment/5670548/+files/make.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/2017227 Title: package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to install/upgrade: »installiertes post-installation-Skript des Paketes linux-headers-6.2.0-20-generic«-Unterprozess gab den Fehlerwert 1 zurück Status in linux package in Ubuntu: Invalid Bug description: I got an error message during updating from Ubuntu 22.10 to 23.04 ProblemType: Package DistroRelease: Ubuntu 23.04 Package: linux-headers-6.2.0-20-generic 6.2.0-20.20 ProcVersionSignature: Ubuntu 5.19.0-40.41-generic 5.19.17 Uname: Linux 5.19.0-40-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jaeger 2885 F wireplumber /dev/snd/seq:jaeger 2882 F pipewire CRDA: N/A CasperMD5CheckResult: pass Date: Fri Apr 21 11:52:56 2023 ErrorMessage: »installiertes post-installation-Skript des Paketes linux-headers-6.2.0-20-generic«-Unterprozess gab den Fehlerwert 1 zurück InstallationDate: Installed on 2022-12-06 (135 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Dell Inc. Latitude 5530 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-40-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1 PythonDetails: /usr/bin/python3.11, Python 3.11.2, python-is-python3, 3.11.1-3 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: grub-pc 2.06-2ubuntu16 SourcePackage: linux Title: package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to install/upgrade: »installiertes post-installation-Skript des Paketes linux-headers-6.2.0-20-generic«-Unterprozess gab den Fehlerwert 1 zurück UpgradeStatus: Upgraded to lunar on 2023-04-21 (0 days ago) dmi.bios.date: 03/17/2023 dmi.bios.release: 1.12 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.0 dmi.board.name: 0C6CYC dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.0:bd03/17/2023:br1.12:svnDellInc.:pnLatitude5530:pvr:rvnDellInc.:rn0C6CYC:rvrA00:cvnDellInc.:ct10:cvr:sku0B06: dmi.product.family: Latitude dmi.product.name: Latitude 5530 dmi.product.sku: 0B06 dmi.sys.vendor: Dell Inc. modified.conffile..etc.apport.report-ignore.README.denylist: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2017227/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
