[Kernel-packages] [Bug 1929035] Re: [22.04 FEAT] SMC-R v2 Support
This bug is awaiting verification that the linux- hwe-5.15/5.15.0-25.25~20.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1929035 Title: [22.04 FEAT] SMC-R v2 Support Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: In Progress Bug description: Feature Description: SMC-R is currently limited to traffic within a single IP subnet only. SMC-R v2 will lift this restriction. Business Case: Allow SMC to be applicable in more diverse customer environments, prereq for container support Feature will be included within kernel >=5.14. Backport info will be provided, once available To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1929035/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1929060] Re: [22.04 FEAT] smc: Add User-defined EID (Enterprise ID) Support - kernel
This bug is awaiting verification that the linux- hwe-5.15/5.15.0-25.25~20.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1929060 Title: [22.04 FEAT] smc: Add User-defined EID (Enterprise ID) Support - kernel Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: In Progress Bug description: Add a tool, tentatively titled smc_eid, to display and set EIDs. Should indicate SEIDs as such. Notes: * EIDs are uppercase only - we should silently convert to all uppercase * Check latest SLD for valid special characters. * Make sure only authorized users are allowed to modify EIDs - reading is OK for everybody, but writing requires authorization. * SEIDs can be disabled, but (obviously) not set. * EID config must be available on module load. * zOS sets the UEIDs globally, i.e. not separate SMC-D and SMC-R. Business Case: Required for users that need to strictly separate/prevent certain OS images from utilizing ISM devices for communication (Security). Furthermore, z/OS disables SEID per default, and will likely have users utilize fine-grained EIDs. Hence we need to be able to support UEIDs for compatibility. This feature is for the kernel part. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1929060/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1959547] Re: [22.04 FEAT] zcrypt DD: Exploitation Support of new IBM Z Crypto Hardware (kernel part)
This bug is awaiting verification that the linux- hwe-5.15/5.15.0-25.25~20.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1959547 Title: [22.04 FEAT] zcrypt DD: Exploitation Support of new IBM Z Crypto Hardware (kernel part) Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: In Progress Bug description: zcrypt DD: Exploitation Support of new IBM Z Crypto Hardware - kernel part To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1959547/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1958918] Re: dependency on crda obsolete according to Debian
This bug is awaiting verification that the linux- hwe-5.15/5.15.0-25.25~20.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lowlatency in Ubuntu. https://bugs.launchpad.net/bugs/1958918 Title: dependency on crda obsolete according to Debian Status in crda package in Ubuntu: New Status in linux package in Ubuntu: In Progress Status in linux-aws package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: In Progress Status in linux-gcp package in Ubuntu: In Progress Status in linux-lowlatency package in Ubuntu: In Progress Status in linux-oracle package in Ubuntu: In Progress Status in linux-raspi package in Ubuntu: In Progress Status in crda source package in Jammy: New Status in linux source package in Jammy: In Progress Status in linux-aws source package in Jammy: Fix Released Status in linux-azure source package in Jammy: In Progress Status in linux-gcp source package in Jammy: In Progress Status in linux-lowlatency source package in Jammy: In Progress Status in linux-oracle source package in Jammy: In Progress Status in linux-raspi source package in Jammy: In Progress Status in crda package in Debian: Fix Released Bug description: Debian has just removed the crda package from the archive, stating that it is obsolete with current kernels: https://bugs.debian.org/1003903 We need someone to determine if this is accurate for Ubuntu as well, and if so, update the kernel packaging to not depend on crda anymore so it can be removed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/crda/+bug/1958918/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1959532] Re: [22.04 FEAT] Transparent PCI device recovery
This bug is awaiting verification that the linux- hwe-5.15/5.15.0-25.25~20.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1959532 Title: [22.04 FEAT] Transparent PCI device recovery Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: In Progress Bug description: A Linux on Z admin can make use of PCI-based devices in case of errors without the need to perform manual recovery. Details: Use cooperative recovery strategies that allow drivers to recover from error scenarios without complete tear-down + re-init. See approach documented for Linux on Power in Linux/Documentation/PCI/pci-error-recovery.rst. Business value: Improved reliability, reduced down-times. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1959532/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1963901] Re: [22.04 FEAT] [VS2103] Set KVM_CAP_S390_MEM_OP_EXTENSION capability to 211
This bug is awaiting verification that the linux- hwe-5.15/5.15.0-25.25~20.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1963901 Title: [22.04 FEAT] [VS2103] Set KVM_CAP_S390_MEM_OP_EXTENSION capability to 211 Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: In Progress Bug description: Title: KVM: Enable storage key checking for intercepted instruction - Set Capability 211 Description: This patch is required on top of "Bug 193314 - LP#1933179 : [22.04 FEAT] [VS2103] KVM: Enable storage key checking for intercepted instruction" in order to set the to set the Capability number to 211 See this merge: https://git.kernel.org/pub/scm/virt/kvm/kvm.git/commit/?h=next=4dfc4ec2b7f5a3a27d166ac42cf8a583fa2d3284 diff --git a/include/uapi/linux/kvm.h b/include/uapi/linux/kvm.h index dbc550bbd9fa3..a02bbf8fd0f67 100644 --- a/include/uapi/linux/kvm.h +++ b/include/uapi/linux/kvm.h @@ -1140,7 +1140,8 @@ struct kvm_ppc_resize_hpt { #define KVM_CAP_VM_GPA_BITS 207 #define KVM_CAP_XSAVE2 208 #define KVM_CAP_SYS_ATTRIBUTES 209 -#define KVM_CAP_S390_MEM_OP_EXTENSION 210 +#define KVM_CAP_PPC_AIL_MODE_3 210 +#define KVM_CAP_S390_MEM_OP_EXTENSION 211 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1963901/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1964990] Re: Rotate to 2021v1 signing key
This bug is awaiting verification that the linux- hwe-5.15/5.15.0-25.25~20.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1964990 Title: Rotate to 2021v1 signing key Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Status in linux source package in Focal: In Progress Status in linux source package in Impish: In Progress Status in linux source package in Jammy: In Progress Bug description: This bug report will be used to track rotating classic kernel signing to 2021v1 signing key. # sudo keyctl list %:.blacklist | grep asymmetric 356531793: ---lswrv 0 0 asymmetric: Canonical Ltd. Secure Boot Signing (2019): c0746fd6c5da3ae827864651ad66ae47fe24b3e8 5296084: ---lswrv 0 0 asymmetric: Canonical Ltd. Secure Boot Signing (ESM 2018): 365188c1d374d6b07c3c8f240f8ef722433d6a8b 739315527: ---lswrv 0 0 asymmetric: Canonical Ltd. Secure Boot Signing: 61482aa2830d0ab2ad5af10b7250da9033ddcef0 578767986: ---lswrv 0 0 asymmetric: Canonical Ltd. Secure Boot Signing (2017): 242ade75ac4a15e50d50c84b0d45ff3eae707a03 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1964990/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1966089] Re: Update OS policy capability handshake
This bug is awaiting verification that the linux- hwe-5.15/5.15.0-25.25~20.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1966089 Title: Update OS policy capability handshake Status in linux package in Ubuntu: Incomplete Bug description: == SRU JAMMY == Update int340x OS policy capability handshake; required for full functionality in thermald 2.4.9 to improve functionality for newer H/W. == The fix == Upstream commit: commit c7ff29763989bd09c433f73fae3c1e1c15d9cda4 Author: Srinivas Pandruvada Date: Mon Mar 14 15:09:37 2022 -0700 thermal: int340x: Update OS policy capability handshake Update the firmware with OS supported policies mask, so that firmware can relinquish its internal controls. Without this update several Tiger Lake laptops gets performance limited with in few seconds of executing in turbo region. The existing way of enumerating firmware policies via IDSP method and selecting policy by directly writing those policy UUIDS via _OSC method is not supported in newer generation of hardware. There is a new UUID "B23BA85D-C8B7-3542-88DE-8DE2FFCFD698" is defined for updating policy capabilities. As part of ACPI _OSC method: Arg0 - UUID: B23BA85D-C8B7-3542-88DE-8DE2FFCFD698 Arg1 - Rev ID: 1 Arg2 - Count: 2 Arg3 - Capability buffers: Array of Arg2 DWORDS DWORD1: As defined in the ACPI 5.0 Specification - Bit 0: Query Flag - Bits 1-3: Always 0 - Bits 4-31: Reserved DWORD2 and beyond: - Bit0: set to 1 to indicate Intel(R) Dynamic Tuning is active, 0 to indicate it is disabled and legacy thermal mechanism should be enabled. - Bit1: set to 1 to indicate Intel(R) Dynamic Tuning is controlling active cooling, 0 to indicate bios shall enable legacy thermal zone with active trip point. - Bit2: set to 1 to indicate Intel(R) Dynamic Tuning is controlling passive cooling, 0 to indicate bios shall enable legacy thermal zone with passive trip point. - Bit3: set to 1 to indicate Intel(R) Dynamic Tuning is handling critical trip point, 0 to indicate bios shall enable legacy thermal zone with critical trip point. - Bits 4:31: Reserved From sysfs interface, there is an existing interface to update policy UUID using attribute "current_uuid". User space can write the same UUID for ACTIVE, PASSIVE and CRITICAL policy. Driver converts these UUIDs to DWORD2 Bit 1 to Bit 3. When any of the policy is activated by user space it is assumed that dynamic tuning is active. For example $cd /sys/bus/platform/devices/INTC1040:00/uuids To support active policy $echo "3A95C389-E4B8-4629-A526-C52C88626BAE" > current_uuid To support passive policy $echo "42A441D6-AE6A-462b-A84B-4A8CE79027D3" > current_uuid To support critical policy $echo "97C68AE7-15FA-499c-B8C9-5DA81D606E0A" > current_uuid To check all the supported policies $cat current_uuid 3A95C389-E4B8-4629-A526-C52C88626BAE 42A441D6-AE6A-462b-A84B-4A8CE79027D3 97C68AE7-15FA-499c-B8C9-5DA81D606E0A To match the bit format for DWORD2, rearranged enum int3400_thermal_uuid and int3400_thermal_uuids[] by swapping current INT3400_THERMAL_ACTIVE and INT3400_THERMAL_PASSIVE_1. If the policies are enumerated via IDSP method then legacy method is used, if not the new method is used to update policy support. Signed-off-by: Srinivas Pandruvada Signed-off-by: Rafael J. Wysocki To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1966089/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1967818] Re: display problems with wayland
*** This bug is a duplicate of bug 1967817 *** https://bugs.launchpad.net/bugs/1967817 ** This bug has been marked a duplicate of bug 1967817 display problems with wayland -- 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/1967818 Title: display problems with wayland Status in linux package in Ubuntu: Confirmed Bug description: I upgraded from 21.10 to 22.04 pre-beta. xorg isn't working (separate bug filed for that), so I switched to wayland. Using gnome, kde, and ubuntu desktops under wayland is giving problems with chrome and brave browsers. If I have a single window open, it's pretty good, but if I have multiple windows open (a half dozen for brave, 33 for chrome is typical for me), the screen frequently flickers and I get portions of the different windows showing up. In many ways this is similar to screen tearing (historically fixed with vsync updating in X), but it doesn't have a clean edge to it, and it's not a matter of top of the screen one image, bottom the other, instead it's a band (~1/4 of the screen high, not always in the same location, but tends to be ~1/3 down from the top more frequently) and in that band I see portions of other windows that are behind the forground window. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-25-generic 5.15.0-25.25 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: dlang 1895 F pulseaudio /dev/snd/controlC0: dlang 1895 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Mon Apr 4 18:40:43 2022 InstallationDate: Installed on 2021-09-20 (196 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: SYSTEM_MANUFACTURER HX90 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic root=UUID=f8f3b117-f767-4bda-9258-5e776fd90ba3 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-25-generic N/A linux-backports-modules-5.15.0-25-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-03-29 (6 days ago) dmi.bios.date: 08/05/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:bd08/05/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/1967818/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1959728] Re: trackpad doesn't work on Lenovo X1 Yoga Titanium after suspend/resume
I found this issue fixed after a Senel firmware update (v0.22.520, 28 Mar 2022): https://pcsupport.lenovo.com/us/en/products/laptops-and-netbooks/thinkpad-x-series-laptops/thinkpad-x1-titanium-type-20qa-20qb/downloads/driver-list/component?name=Mouse,%20Touchpad,%20Keyboard%20and%20Pen The update is applied in windows. -- 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/1959728 Title: trackpad doesn't work on Lenovo X1 Yoga Titanium after suspend/resume Status in linux package in Ubuntu: Confirmed Bug description: On my X1 Yoga Titanium (which has a fancy new "Sensel" trackpad with haptic response to clicks), the trackpad stops working after a suspend/resume cycle, although the red trackpoint continues to work fine for controlling the pointer. I believe this system is using S0i3 for suspend, in case that's relevant. If I boot from power off, then the trackpad works fine in both the pre-boot BIOS and in Ubuntu 22.04 (prerelease), including haptic response to clicks. After a suspend/resume cycle, the trackpad stops responding, although a lot of swiping/pressing will occasionally produce a button press event. This state persists even if I reboot out of Linux (without a power cycle) - for example the trackpad no longer works for the pre-boot BIOS configuration screen, until a full power cycle (which fixes the trackpad). Possibly relevant, the trackpad seems to be this device to the kernel: [2.016917] input: SNSL0001:00 2C2F:0006 Mouse as /devices/pci:00/:00:15.0/i2c_designware.0/i2c-1/i2c-SNSL0001:00/0018:2C2F:0006.0001/input/input6 [2.016964] input: SNSL0001:00 2C2F:0006 Touchpad as /devices/pci:00/:00:15.0/i2c_designware.0/i2c-1/i2c-SNSL0001:00/0018:2C2F:0006.0001/input/input7 [2.017027] hid-generic 0018:2C2F:0006.0001: input,hidraw0: I2C HID v1.00 Mouse [SNSL0001:00 2C2F:0006] on i2c-SNSL0001:00 and the last kernel messages before suspend are: [ 305.216189] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. [ 305.217435] printk: Suspending console(s) (use no_console_suspend to debug) [ 305.274332] i2c_designware i2c_designware.0: i2c_dw_handle_tx_abort: lost arbitration [ 306.030947] i2c_hid_acpi i2c-SNSL0001:00: failed to set a report to device. [ 306.616463] ACPI: EC: interrupt blocked [ 331.551118] ACPI: EC: interrupt unblocked ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-generic (not installed) ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu76 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bina 1543 F pipewire bina 1544 F pipewire-media- bina 1545 F pulseaudio /dev/snd/seq:bina 1543 F pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Feb 1 14:54:14 2022 InstallationDate: Installed on 2022-02-01 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220126) MachineType: LENOVO 20QA000EUS ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-18-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-18-generic N/A linux-backports-modules-5.15.0-18-generic N/A linux-firmware 20220124.git0c6a7b3b-0ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/30/2021 dmi.bios.release: 1.18 dmi.bios.vendor: LENOVO dmi.bios.version: N2MET53W (1.18 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QA000EUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.11 dmi.modalias: dmi:bvnLENOVO:bvrN2MET53W(1.18):bd09/30/2021:br1.18:efr1.11:svnLENOVO:pn20QA000EUS:pvrThinkPadX1TitaniumGen1:rvnLENOVO:rn20QA000EUS:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone:skuLENOVO_MT_20QA_BU_Think_FM_ThinkPadX1TitaniumGen1: dmi.product.family: ThinkPad X1 Titanium Gen 1 dmi.product.name: 20QA000EUS dmi.product.sku: LENOVO_MT_20QA_BU_Think_FM_ThinkPad X1 Titanium Gen 1 dmi.product.version: ThinkPad X1 Titanium Gen 1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1959728/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe :
[Kernel-packages] [Bug 1967702] Re: Enable speakup kernel modules to allow the speakup screen reader to function
** Tags added: seg -- 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/1967702 Title: Enable speakup kernel modules to allow the speakup screen reader to function Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: In Progress Bug description: BugLink: https://bugs.launchpad.net/bugs/1967702 [Impact] Blind system administrators rely on the speakup accessibility feature to be able to use screen readers in text mode, like "espeakup". Ubuntu has enabled CONFIG_SPEAKUP for a significant amount of time, although in recent releases it keeps being disabled. In Hirsute and Impish, it was accidentally disabled due to it moving from drivers/staging/ to drivers/accessibility/, and it was re-added by Tim Gardner in LP1942459. When it was recently re-enabled, the patch was never applied to ubuntu-unstable, and thus was never picked up by Jammy. We need to enable CONFIG_ACCESSIBILITY and CONFIG_SPEAKUP in Jammy and ubuntu-unstable. [Fix] We need to enable the following configuration items: CONFIG_ACCESSIBILITY=y CONFIG_SPEAKUP=m and the additional modules: CONFIG_SPEAKUP_SYNTH_ACNTSA=m CONFIG_SPEAKUP_SYNTH_APOLLO=m CONFIG_SPEAKUP_SYNTH_AUDPTR=m CONFIG_SPEAKUP_SYNTH_BNS=m CONFIG_SPEAKUP_SYNTH_DECEXT=m CONFIG_SPEAKUP_SYNTH_DECTLK=m CONFIG_SPEAKUP_SYNTH_DUMMY=m CONFIG_SPEAKUP_SYNTH_LTLK=m CONFIG_SPEAKUP_SYNTH_SOFT=m CONFIG_SPEAKUP_SYNTH_SPKOUT=m CONFIG_SPEAKUP_SYNTH_TXPRT=m [Testcase] Install the speakup accessibility tool: $ sudo apt install espeakup Check journalctl to see if it is able to load kernel modules: systemd[1]: Starting Software speech output for Speakup... modprobe[27013]: modprobe: FATAL: Module speakup_soft not found in directory /lib/modules/5.15.0-25-generic systemd[1]: espeakup.service: Control process exited, code=exited, status=1/FAILURE systemd[1]: espeakup.service: Failed with result 'exit-code'. systemd[1]: Failed to start Software speech output for Speakup. systemd[1]: espeakup.service: Scheduled restart job, restart counter is at 1. systemd[1]: Stopped Software speech output for Speakup. systemd[1]: espeakup.service: Start request repeated too quickly. systemd[1]: espeakup.service: Failed with result 'exit-code'. systemd[1]: Failed to start Software speech output for Speakup. We should see espeakup.service start correctly, instead of failing to load speakup_soft: You can also try load the modules manually: $ sudo modprobe speakup_soft There is a test package available in the following ppa: https://launchpad.net/~mruffell/+archive/ubuntu/lp1967702-test If you install the test kernel, the speakup modules should load successfully. [Where problems could occur] We are enabling CONFIG_ACCESSIBILITY for all arches apart from s390x, and this shouldn't have any affect on config items being turned on, since it simply enables the speakup submenu to be shown. Enabling CONFIG_SPEAKUP* should not have any impact on users that don't use screen reader accessibility software, as it will only be loaded by users of espeakup. If a regression were to occur, users could unload the speakup modules. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967702/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1967820] Re: Touchpad incorrectly detected as PS/2 mouse in 'Galago Pro 5' after the kernel upgrade.
In /proc/bus/input/devices, the correct info is: I: Bus=0018 Vendor=2808 Product=0101 Version=0100 N: Name="PNP0C50:00 2808:0101 Touchpad" P: Phys=i2c-PNP0C50:00 S: Sysfs=/devices/pci:00/:00:15.0/i2c_designware.0/i2c-1/i2c-PNP0C50:00/0018:2808:0101.0001/input/input16 U: Uniq= H: Handlers=mouse1 event11 B: PROP=5 B: EV=1b B: KEY=e520 1 0 0 0 0 B: ABS=2e08003 B: MSC=20 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1967820 Title: Touchpad incorrectly detected as PS/2 mouse in 'Galago Pro 5' after the kernel upgrade. Status in linux package in Ubuntu: Confirmed Bug description: Computer model 'galp5'. The issue started after updating everything, including the kernel. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-39-generic 5.13.0-39.44 ProcVersionSignature: Ubuntu 5.13.0-39.44-generic 5.13.19 Uname: Linux 5.13.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu71.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mark 1360 F pulseaudio CurrentDesktop: KDE Date: Mon Apr 4 20:24:07 2022 InstallationDate: Installed on 2022-04-03 (1 days ago) InstallationMedia: Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 5986:9102 Acer, Inc BisonCam,NB Pro Bus 001 Device 005: ID 3938:1031 MOSART Semi. 2.4G Wireless Mouse Bus 001 Device 004: ID 8087:0026 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: System76 Galago Pro ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-39-generic root=/dev/mapper/vgkubuntu-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.13.0-39-generic N/A linux-backports-modules-5.13.0-39-generic N/A linux-firmware 1.201.5 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/20/2021 dmi.bios.release: 4.13 dmi.bios.vendor: coreboot dmi.bios.version: 2021-07-20_93c2809 dmi.board.name: Galago Pro dmi.board.vendor: System76 dmi.board.version: galp5 dmi.chassis.type: 9 dmi.chassis.vendor: System76 dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvncoreboot:bvr2021-07-20_93c2809:bd07/20/2021:br4.13:efr0.0:svnSystem76:pnGalagoPro:pvrgalp5:rvnSystem76:rnGalagoPro:rvrgalp5:cvnSystem76:ct9:cvr:sku: dmi.product.name: Galago Pro dmi.product.version: galp5 dmi.sys.vendor: System76 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967820/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1967820] Re: Touchpad incorrectly detected as PS/2 mouse in 'Galago Pro 5' after the kernel upgrade.
I completely reinstalled Kubuntu, then ran: sudo apt update sudo apt upgrade sudo apt install neofetch I rebooted, and the Touchpad is still detected, ran neofetch: `.:/osssso/:. mark@mark-Galago-Pro .:oyyo:` -oyyyodMMso- OS: Kubuntu 21.10 x86_64 -syydMMyodmMMys- Host: Galago Pro galp5 oyyysdMysdMyyyo Kernel: 5.13.0-39-generic `odysyysoodyo`Uptime: 6 mins oyydsdMMysyyyoPackages: 1969 (dpkg) -dMysyysdMysyyy- Shell: bash 5.1.8 osoodMyyydysyyyo Resolution: 1920x1080 yyysdMyyysos DE: Plasma 5.22.5 yyysdMyy WM: KWin oysosdyyydysyyyo Theme: Breeze Light [Plasma], Breeze [GTK2/3] -dMysyysdMysyyy- Icons: breeze [Plasma], breeze [GTK2/3] oyydMMMysyyysdMMyoyyyoyyyoTerminal: konsole `odMMMysyyyoodyoo CPU: 11th Gen Intel i5-1135G7 (8) @ 4.200GHz oyyysyyosdMMMo GPU: Intel TigerLake-LP GT2 [Iris Xe Graphics] -sydMMMysyyydMMMyss- Memory: 1584MiB / 39969MiB -oyyydMMyyysoso- ./oyyo/. `.:/oossso/:.` Thus I do not know how to reproduce the error. -- 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/1967820 Title: Touchpad incorrectly detected as PS/2 mouse in 'Galago Pro 5' after the kernel upgrade. Status in linux package in Ubuntu: Confirmed Bug description: Computer model 'galp5'. The issue started after updating everything, including the kernel. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-39-generic 5.13.0-39.44 ProcVersionSignature: Ubuntu 5.13.0-39.44-generic 5.13.19 Uname: Linux 5.13.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu71.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mark 1360 F pulseaudio CurrentDesktop: KDE Date: Mon Apr 4 20:24:07 2022 InstallationDate: Installed on 2022-04-03 (1 days ago) InstallationMedia: Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 5986:9102 Acer, Inc BisonCam,NB Pro Bus 001 Device 005: ID 3938:1031 MOSART Semi. 2.4G Wireless Mouse Bus 001 Device 004: ID 8087:0026 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: System76 Galago Pro ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-39-generic root=/dev/mapper/vgkubuntu-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.13.0-39-generic N/A linux-backports-modules-5.13.0-39-generic N/A linux-firmware 1.201.5 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/20/2021 dmi.bios.release: 4.13 dmi.bios.vendor: coreboot dmi.bios.version: 2021-07-20_93c2809 dmi.board.name: Galago Pro dmi.board.vendor: System76 dmi.board.version: galp5 dmi.chassis.type: 9 dmi.chassis.vendor: System76 dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvncoreboot:bvr2021-07-20_93c2809:bd07/20/2021:br4.13:efr0.0:svnSystem76:pnGalagoPro:pvrgalp5:rvnSystem76:rnGalagoPro:rvrgalp5:cvnSystem76:ct9:cvr:sku: dmi.product.name: Galago Pro dmi.product.version: galp5 dmi.sys.vendor: System76 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967820/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1967702] Re: Enable speakup kernel modules to allow the speakup screen reader to function
** Summary changed: - Accessibility features have been disabled, modules like speakup_soft and others are missing + Enable speakup kernel modules to allow the speakup screen reader to function ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: Confirmed ** Changed in: linux (Ubuntu Jammy) Status: Confirmed => In Progress ** Changed in: linux (Ubuntu Jammy) Importance: Undecided => High ** Changed in: linux (Ubuntu Jammy) Assignee: (unassigned) => Matthew Ruffell (mruffell) ** Description changed: - From very old versions of Kernel for Ubuntu until version 5.13, accessibility features were enabled, allowing blind users to use screen readers in text mode, such as "speakup" via "espeakup" package. - In Kernels 5.15 packages for Ubuntu 22.04 beta, such as "linux-image-5.15.0-23-generic", accessibility features are disabled (no justification for such occurrence was listed in the file "changelog.Debian.gz"), with this the espeakup application doesn't work, it depends on the missing speakup_soft module. - Missing in the file "/boot/config-5.15.0-23-generic" comparing with the file "/boot/config-5.13.0-39-generic", the line + BugLink: https://bugs.launchpad.net/bugs/1967702 + + [Impact] + + Blind system administrators rely on the speakup accessibility feature to + be able to use screen readers in text mode, like "espeakup". + + Ubuntu has enabled CONFIG_SPEAKUP for a significant amount of time, + although in recent releases it keeps being disabled. In Hirsute and + Impish, it was accidentally disabled due to it moving from + drivers/staging/ to drivers/accessibility/, and it was re-added by Tim + Gardner in LP1942459. + + When it was recently re-enabled, the patch was never applied to ubuntu- + unstable, and thus was never picked up by Jammy. + + We need to enable CONFIG_ACCESSIBILITY and CONFIG_SPEAKUP in Jammy and + ubuntu-unstable. + + [Fix] + + We need to enable the following configuration items: + CONFIG_ACCESSIBILITY=y - and the following lines are also missing: - # - # Speakup console speech - # CONFIG_SPEAKUP=m + + and the additional modules: + CONFIG_SPEAKUP_SYNTH_ACNTSA=m CONFIG_SPEAKUP_SYNTH_APOLLO=m CONFIG_SPEAKUP_SYNTH_AUDPTR=m CONFIG_SPEAKUP_SYNTH_BNS=m + CONFIG_SPEAKUP_SYNTH_DECEXT=m CONFIG_SPEAKUP_SYNTH_DECTLK=m - CONFIG_SPEAKUP_SYNTH_DECEXT=m + CONFIG_SPEAKUP_SYNTH_DUMMY=m CONFIG_SPEAKUP_SYNTH_LTLK=m CONFIG_SPEAKUP_SYNTH_SOFT=m CONFIG_SPEAKUP_SYNTH_SPKOUT=m CONFIG_SPEAKUP_SYNTH_TXPRT=m - CONFIG_SPEAKUP_SYNTH_DUMMY=m - # end of Speakup console speech - ProblemType: Bug - DistroRelease: Ubuntu 22.04 - Package: linux-image-5.15.0-23-generic 5.15.0-23.23 - ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 - Uname: Linux 5.15.0-23-generic x86_64 - ApportVersion: 2.20.11-0ubuntu80 - Architecture: amd64 - AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: tiago 1259 F pulseaudio - /dev/snd/pcmC0D0p: tiago 1259 F...m pulseaudio - CasperMD5CheckResult: pass - CurrentDesktop: MATE - Date: Sun Apr 3 22:05:39 2022 - InstallationDate: Installed on 2022-04-03 (0 days ago) - InstallationMedia: Ubuntu-MATE 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220330) - Lsusb: - Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub - Bus 001 Device 003: ID 0c45:671e Microdia Integrated_Webcam_HD - Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver - Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson Peak (JfP) - Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub - MachineType: Dell Inc. Inspiron 3583 - ProcFB: 0 i915drmfb - ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic root=UUID=9e0e837b-49f2-4e10-945a-f7460bcc8286 ro quiet splash vt.handoff=7 - RelatedPackageVersions: - linux-restricted-modules-5.15.0-23-generic N/A - linux-backports-modules-5.15.0-23-generic N/A - linux-firmware 20220329.git681281e4-0ubuntu1 - SourcePackage: linux - UpgradeStatus: No upgrade log present (probably fresh install) - dmi.bios.date: 12/06/2021 - dmi.bios.release: 1.17 - dmi.bios.vendor: Dell Inc. - dmi.bios.version: 1.17.0 - dmi.board.name: 0KD03P - dmi.board.vendor: Dell Inc. - dmi.board.version: A03 - dmi.chassis.type: 10 - dmi.chassis.vendor: Dell Inc. - dmi.modalias: dmi:bvnDellInc.:bvr1.17.0:bd12/06/2021:br1.17:svnDellInc.:pnInspiron3583:pvr:rvnDellInc.:rn0KD03P:rvrA03:cvnDellInc.:ct10:cvr:sku08CA: - dmi.product.family: Inspiron - dmi.product.name: Inspiron 3583 - dmi.product.sku: 08CA - dmi.sys.vendor: Dell Inc. + [Testcase] + + Install the speakup accessibility tool: + + $ sudo apt install espeakup + + Check journalctl to see if it is able to load kernel modules: + + systemd[1]: Starting Software speech output for Speakup... + modprobe[27013]: modprobe: FATAL: Module speakup_soft not found in directory /lib/modules/5.15.0-25-generic + systemd[1]: espeakup.service: Control
[Kernel-packages] [Bug 1967820] 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/1967820 Title: Touchpad incorrectly detected as PS/2 mouse in 'Galago Pro 5' after the kernel upgrade. Status in linux package in Ubuntu: Confirmed Bug description: Computer model 'galp5'. The issue started after updating everything, including the kernel. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-39-generic 5.13.0-39.44 ProcVersionSignature: Ubuntu 5.13.0-39.44-generic 5.13.19 Uname: Linux 5.13.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu71.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mark 1360 F pulseaudio CurrentDesktop: KDE Date: Mon Apr 4 20:24:07 2022 InstallationDate: Installed on 2022-04-03 (1 days ago) InstallationMedia: Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 5986:9102 Acer, Inc BisonCam,NB Pro Bus 001 Device 005: ID 3938:1031 MOSART Semi. 2.4G Wireless Mouse Bus 001 Device 004: ID 8087:0026 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: System76 Galago Pro ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-39-generic root=/dev/mapper/vgkubuntu-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.13.0-39-generic N/A linux-backports-modules-5.13.0-39-generic N/A linux-firmware 1.201.5 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/20/2021 dmi.bios.release: 4.13 dmi.bios.vendor: coreboot dmi.bios.version: 2021-07-20_93c2809 dmi.board.name: Galago Pro dmi.board.vendor: System76 dmi.board.version: galp5 dmi.chassis.type: 9 dmi.chassis.vendor: System76 dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvncoreboot:bvr2021-07-20_93c2809:bd07/20/2021:br4.13:efr0.0:svnSystem76:pnGalagoPro:pvrgalp5:rvnSystem76:rnGalagoPro:rvrgalp5:cvnSystem76:ct9:cvr:sku: dmi.product.name: Galago Pro dmi.product.version: galp5 dmi.sys.vendor: System76 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967820/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1967820] [NEW] Touchpad incorrectly detected as PS/2 mouse in 'Galago Pro 5' after the kernel upgrade.
Public bug reported: Computer model 'galp5'. The issue started after updating everything, including the kernel. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-39-generic 5.13.0-39.44 ProcVersionSignature: Ubuntu 5.13.0-39.44-generic 5.13.19 Uname: Linux 5.13.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu71.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mark 1360 F pulseaudio CurrentDesktop: KDE Date: Mon Apr 4 20:24:07 2022 InstallationDate: Installed on 2022-04-03 (1 days ago) InstallationMedia: Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 5986:9102 Acer, Inc BisonCam,NB Pro Bus 001 Device 005: ID 3938:1031 MOSART Semi. 2.4G Wireless Mouse Bus 001 Device 004: ID 8087:0026 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: System76 Galago Pro ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-39-generic root=/dev/mapper/vgkubuntu-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.13.0-39-generic N/A linux-backports-modules-5.13.0-39-generic N/A linux-firmware 1.201.5 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/20/2021 dmi.bios.release: 4.13 dmi.bios.vendor: coreboot dmi.bios.version: 2021-07-20_93c2809 dmi.board.name: Galago Pro dmi.board.vendor: System76 dmi.board.version: galp5 dmi.chassis.type: 9 dmi.chassis.vendor: System76 dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvncoreboot:bvr2021-07-20_93c2809:bd07/20/2021:br4.13:efr0.0:svnSystem76:pnGalagoPro:pvrgalp5:rvnSystem76:rnGalagoPro:rvrgalp5:cvnSystem76:ct9:cvr:sku: dmi.product.name: Galago Pro dmi.product.version: galp5 dmi.sys.vendor: System76 ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug impish wayland-session ** Attachment added: "devices" https://bugs.launchpad.net/bugs/1967820/+attachment/5577121/+files/devices -- 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/1967820 Title: Touchpad incorrectly detected as PS/2 mouse in 'Galago Pro 5' after the kernel upgrade. Status in linux package in Ubuntu: Confirmed Bug description: Computer model 'galp5'. The issue started after updating everything, including the kernel. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-39-generic 5.13.0-39.44 ProcVersionSignature: Ubuntu 5.13.0-39.44-generic 5.13.19 Uname: Linux 5.13.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu71.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mark 1360 F pulseaudio CurrentDesktop: KDE Date: Mon Apr 4 20:24:07 2022 InstallationDate: Installed on 2022-04-03 (1 days ago) InstallationMedia: Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 5986:9102 Acer, Inc BisonCam,NB Pro Bus 001 Device 005: ID 3938:1031 MOSART Semi. 2.4G Wireless Mouse Bus 001 Device 004: ID 8087:0026 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: System76 Galago Pro ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-39-generic root=/dev/mapper/vgkubuntu-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.13.0-39-generic N/A linux-backports-modules-5.13.0-39-generic N/A linux-firmware 1.201.5 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/20/2021 dmi.bios.release: 4.13 dmi.bios.vendor: coreboot dmi.bios.version: 2021-07-20_93c2809 dmi.board.name: Galago Pro dmi.board.vendor: System76 dmi.board.version: galp5 dmi.chassis.type: 9 dmi.chassis.vendor: System76 dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvncoreboot:bvr2021-07-20_93c2809:bd07/20/2021:br4.13:efr0.0:svnSystem76:pnGalagoPro:pvrgalp5:rvnSystem76:rnGalagoPro:rvrgalp5:cvnSystem76:ct9:cvr:sku: dmi.product.name: Galago Pro dmi.product.version: galp5 dmi.sys.vendor: System76 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967820/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1967817] 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/1967817 Title: display problems with wayland Status in linux package in Ubuntu: Confirmed Bug description: I upgraded from 21.10 to 22.04 pre-beta. xorg isn't working (separate bug filed for that), so I switched to wayland. Using gnome, kde, and ubuntu desktops under wayland is giving problems with chrome and brave browsers. If I have a single window open, it's pretty good, but if I have multiple windows open (a half dozen for brave, 33 for chrome is typical for me), the screen frequently flickers and I get portions of the different windows showing up. In many ways this is similar to screen tearing (historically fixed with vsync updating in X), but it doesn't have a clean edge to it, and it's not a matter of top of the screen one image, bottom the other, instead it's a band (~1/4 of the screen high, not always in the same location, but tends to be ~1/3 down from the top more frequently) and in that band I see portions of other windows that are behind the forground window. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-25-generic 5.15.0-25.25 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: dlang 1895 F pulseaudio /dev/snd/controlC0: dlang 1895 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Mon Apr 4 18:40:43 2022 InstallationDate: Installed on 2021-09-20 (196 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: SYSTEM_MANUFACTURER HX90 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic root=UUID=f8f3b117-f767-4bda-9258-5e776fd90ba3 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-25-generic N/A linux-backports-modules-5.15.0-25-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-03-29 (6 days ago) dmi.bios.date: 08/05/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:bd08/05/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/1967817/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1912829] Re: nvidia-kernel-source-435 435.21-0ubuntu7: nvidia kernel module failed to build
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-graphics-drivers-455 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-455 in Ubuntu. https://bugs.launchpad.net/bugs/1912829 Title: nvidia-kernel-source-435 435.21-0ubuntu7: nvidia kernel module failed to build Status in nvidia-graphics-drivers-455 package in Ubuntu: Confirmed Bug description: i install google chrome and after install i have this error message and my wi-fi icon disappear too. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-kernel-source-435 455.45.01-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip DKMSKernelVersion: 5.8.0-38-generic Date: Fri Jan 22 10:08:06 2021 Dependencies: nvidia-kernel-source-455 460.32.03-0ubuntu0.20.04.1 nvidia-kernel-source-460 460.32.03-0ubuntu0.20.04.1 DuplicateSignature: dkms:nvidia-kernel-source-435:435.21-0ubuntu7:/var/lib/dkms/nvidia/435.21/build/common/inc/nv-linux.h:503:17: error: too many arguments to function ‘__vmalloc’ InstallationDate: Installed on 2020-10-12 (102 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageVersion: 435.21-0ubuntu7 Python3Details: /usr/local/bin/python3.6, Python 3.6.3, unpackaged PythonDetails: /usr/bin/python3.8, Python 3.8.5, unpackaged RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.4 SourcePackage: nvidia-graphics-drivers-455 Title: nvidia-kernel-source-435 435.21-0ubuntu7: nvidia kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-455/+bug/1912829/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1967818] 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/1967818 Title: display problems with wayland Status in linux package in Ubuntu: Confirmed Bug description: I upgraded from 21.10 to 22.04 pre-beta. xorg isn't working (separate bug filed for that), so I switched to wayland. Using gnome, kde, and ubuntu desktops under wayland is giving problems with chrome and brave browsers. If I have a single window open, it's pretty good, but if I have multiple windows open (a half dozen for brave, 33 for chrome is typical for me), the screen frequently flickers and I get portions of the different windows showing up. In many ways this is similar to screen tearing (historically fixed with vsync updating in X), but it doesn't have a clean edge to it, and it's not a matter of top of the screen one image, bottom the other, instead it's a band (~1/4 of the screen high, not always in the same location, but tends to be ~1/3 down from the top more frequently) and in that band I see portions of other windows that are behind the forground window. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-25-generic 5.15.0-25.25 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: dlang 1895 F pulseaudio /dev/snd/controlC0: dlang 1895 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Mon Apr 4 18:40:43 2022 InstallationDate: Installed on 2021-09-20 (196 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: SYSTEM_MANUFACTURER HX90 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic root=UUID=f8f3b117-f767-4bda-9258-5e776fd90ba3 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-25-generic N/A linux-backports-modules-5.15.0-25-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-03-29 (6 days ago) dmi.bios.date: 08/05/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:bd08/05/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/1967818/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1967818] [NEW] display problems with wayland
Public bug reported: I upgraded from 21.10 to 22.04 pre-beta. xorg isn't working (separate bug filed for that), so I switched to wayland. Using gnome, kde, and ubuntu desktops under wayland is giving problems with chrome and brave browsers. If I have a single window open, it's pretty good, but if I have multiple windows open (a half dozen for brave, 33 for chrome is typical for me), the screen frequently flickers and I get portions of the different windows showing up. In many ways this is similar to screen tearing (historically fixed with vsync updating in X), but it doesn't have a clean edge to it, and it's not a matter of top of the screen one image, bottom the other, instead it's a band (~1/4 of the screen high, not always in the same location, but tends to be ~1/3 down from the top more frequently) and in that band I see portions of other windows that are behind the forground window. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-25-generic 5.15.0-25.25 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: dlang 1895 F pulseaudio /dev/snd/controlC0: dlang 1895 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Mon Apr 4 18:40:43 2022 InstallationDate: Installed on 2021-09-20 (196 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: SYSTEM_MANUFACTURER HX90 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic root=UUID=f8f3b117-f767-4bda-9258-5e776fd90ba3 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-25-generic N/A linux-backports-modules-5.15.0-25-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-03-29 (6 days ago) dmi.bios.date: 08/05/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:bd08/05/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-bug jammy package-from-proposed wayland-session -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1967818 Title: display problems with wayland Status in linux package in Ubuntu: New Bug description: I upgraded from 21.10 to 22.04 pre-beta. xorg isn't working (separate bug filed for that), so I switched to wayland. Using gnome, kde, and ubuntu desktops under wayland is giving problems with chrome and brave browsers. If I have a single window open, it's pretty good, but if I have multiple windows open (a half dozen for brave, 33 for chrome is typical for me), the screen frequently flickers and I get portions of the different windows showing up. In many ways this is similar to screen tearing (historically fixed with vsync updating in X), but it doesn't have a clean edge to it, and it's not a matter of top of the screen one image, bottom the other, instead it's a band (~1/4 of the screen high, not always in the same location, but tends to be ~1/3 down from the top more frequently) and in that band I see portions of other windows that are behind the forground window. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-25-generic 5.15.0-25.25 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: dlang 1895 F pulseaudio /dev/snd/controlC0: dlang 1895 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Mon Apr 4 18:40:43 2022 InstallationDate: Installed on 2021-09-20 (196 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: SYSTEM_MANUFACTURER HX90 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash
[Kernel-packages] [Bug 1967817] [NEW] display problems with wayland
Public bug reported: I upgraded from 21.10 to 22.04 pre-beta. xorg isn't working (separate bug filed for that), so I switched to wayland. Using gnome, kde, and ubuntu desktops under wayland is giving problems with chrome and brave browsers. If I have a single window open, it's pretty good, but if I have multiple windows open (a half dozen for brave, 33 for chrome is typical for me), the screen frequently flickers and I get portions of the different windows showing up. In many ways this is similar to screen tearing (historically fixed with vsync updating in X), but it doesn't have a clean edge to it, and it's not a matter of top of the screen one image, bottom the other, instead it's a band (~1/4 of the screen high, not always in the same location, but tends to be ~1/3 down from the top more frequently) and in that band I see portions of other windows that are behind the forground window. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-25-generic 5.15.0-25.25 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: dlang 1895 F pulseaudio /dev/snd/controlC0: dlang 1895 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Mon Apr 4 18:40:43 2022 InstallationDate: Installed on 2021-09-20 (196 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: SYSTEM_MANUFACTURER HX90 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic root=UUID=f8f3b117-f767-4bda-9258-5e776fd90ba3 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-25-generic N/A linux-backports-modules-5.15.0-25-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-03-29 (6 days ago) dmi.bios.date: 08/05/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:bd08/05/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-bug jammy package-from-proposed wayland-session -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1967817 Title: display problems with wayland Status in linux package in Ubuntu: New Bug description: I upgraded from 21.10 to 22.04 pre-beta. xorg isn't working (separate bug filed for that), so I switched to wayland. Using gnome, kde, and ubuntu desktops under wayland is giving problems with chrome and brave browsers. If I have a single window open, it's pretty good, but if I have multiple windows open (a half dozen for brave, 33 for chrome is typical for me), the screen frequently flickers and I get portions of the different windows showing up. In many ways this is similar to screen tearing (historically fixed with vsync updating in X), but it doesn't have a clean edge to it, and it's not a matter of top of the screen one image, bottom the other, instead it's a band (~1/4 of the screen high, not always in the same location, but tends to be ~1/3 down from the top more frequently) and in that band I see portions of other windows that are behind the forground window. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-25-generic 5.15.0-25.25 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: dlang 1895 F pulseaudio /dev/snd/controlC0: dlang 1895 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Mon Apr 4 18:40:43 2022 InstallationDate: Installed on 2021-09-20 (196 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: SYSTEM_MANUFACTURER HX90 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash
[Kernel-packages] [Bug 1967818] Re: display problems with wayland
note that this does not happen on firefox (about a hald dozen windows open) -- 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/1967818 Title: display problems with wayland Status in linux package in Ubuntu: New Bug description: I upgraded from 21.10 to 22.04 pre-beta. xorg isn't working (separate bug filed for that), so I switched to wayland. Using gnome, kde, and ubuntu desktops under wayland is giving problems with chrome and brave browsers. If I have a single window open, it's pretty good, but if I have multiple windows open (a half dozen for brave, 33 for chrome is typical for me), the screen frequently flickers and I get portions of the different windows showing up. In many ways this is similar to screen tearing (historically fixed with vsync updating in X), but it doesn't have a clean edge to it, and it's not a matter of top of the screen one image, bottom the other, instead it's a band (~1/4 of the screen high, not always in the same location, but tends to be ~1/3 down from the top more frequently) and in that band I see portions of other windows that are behind the forground window. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-25-generic 5.15.0-25.25 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: dlang 1895 F pulseaudio /dev/snd/controlC0: dlang 1895 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Mon Apr 4 18:40:43 2022 InstallationDate: Installed on 2021-09-20 (196 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: SYSTEM_MANUFACTURER HX90 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic root=UUID=f8f3b117-f767-4bda-9258-5e776fd90ba3 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-25-generic N/A linux-backports-modules-5.15.0-25-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-03-29 (6 days ago) dmi.bios.date: 08/05/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:bd08/05/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/1967818/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1965618] Re: linux-azure: Focal 5.4 arm64 support
This bug is awaiting verification that the linux-azure/5.4.0-1075.78 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1965618 Title: linux-azure: Focal 5.4 arm64 support Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure source package in Focal: Fix Committed Bug description: SRU Justification [Impact] Focal linux-azure does not support arm64 [Fix] Backport/cherry-pick approximately 100 patches to support arm64 on hyperv [Where things could go wrong] A number of the patches reorganize hyperv CPU support. Therefore amd64 could be affected. [Other Info] SF: #00310705 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1965618/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1967336] Re: linux-azure: CONFIG_HIBERNATION=y
This bug is awaiting verification that the linux-azure/5.4.0-1075.78 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1967336 Title: linux-azure: CONFIG_HIBERNATION=y Status in linux-azure package in Ubuntu: Fix Committed Status in linux-azure source package in Focal: Fix Committed Status in linux-azure source package in Impish: Fix Committed Status in linux-azure source package in Jammy: Fix Committed Bug description: SRU Justification [Impact] Azure arm64 tuned kernels do not support hibernation. [Test Plan] Microsoft tested [Where things could go wrong] Hibernation may fail. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1967336/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1965080] Re: Mute/mic LEDs no function on some HP platfroms
This bug is awaiting verification that the linux-oem-5.14/5.14.0-1033.36 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1965080 Title: Mute/mic LEDs no function on some HP platfroms Status in OEM Priority Project: Confirmed Status in linux package in Ubuntu: Incomplete Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.14 source package in Focal: Fix Committed Bug description: [Impact] The mic mute/audio mute LEDS are not work on 1) HP ProBook 440 G9 Notebook PC 2) HP ProBook 450 G9 Notebook PC 3) HP EliteBook 640 G9 Notebook PC 4) HP EliteBook 650 G9 Notebook PC [Fix] It needs the specific quirk for the hardware layout. Thus, add the quirks to make it works. [Test] After applying the quirk, the audio/mic mute LEDs are working good. [Where problems could occur] If HP ships the different system boards design with the same subsystem ID of audio codec which is using different GPIO pins (different layout), then the quirk will not work (LEDs will not work when muting audio-output or microphone). To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1965080/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1966497] Re: Fix non-working MT7921 BT after reboot
This bug is awaiting verification that the linux-oem-5.14/5.14.0-1033.36 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1966497 Title: Fix non-working MT7921 BT after reboot Status in HWE Next: New Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.14 source package in Focal: Fix Committed Bug description: [Impact] There's a high chance that MT7921 BT may go out to lunch after reboot. Worse, there's no way to recover the controller unless the power cord is unplugged. [Fix] In addition to SRU "Need to reset MT7921 BT when the firmware hang or command no response", enable MSFT extension can magically solve the issue. [Test] With the patch applied, the MT7921 BT continues to work after 100 times reboots. [Where problems could occur] This fix is specific to MTK BT controllers, so the change is limited. I totally don't understand why this patch can fix the issue, other than it just does the trick. So I guess we have to accept the reality that hardwares can have their own quirks. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1966497/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1964850] Re: Choppy trackpad/USB mouse behavior with oem-1023 or above kernel version
This bug is awaiting verification that the linux-oem-5.14/5.14.0-1033.36 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1964850 Title: Choppy trackpad/USB mouse behavior with oem-1023 or above kernel version Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.14 source package in Focal: Fix Committed Status in linux source package in Jammy: Fix Released Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: [SRU Justfication] [Impact] Disjoint trackpad/mouse path found on PSR capable panels. [Fix] Two fixes from v5.17-rc6 that only turns off vblank IRQs when PSR is not enabled, originally for commit f94cf1cb1796 ("drm/amdgpu/display: set vblank_disable_immediate for DC") that was being backported to LTS stable 5.15.y, and therefore oem-5.14. [Test Case] Simply move the mouse around. [Where problems could occur] This follows for AMD platforms, the power-saving performance may not be as good as before, but while we don't have such energy-saving certificate program for AMD yet, this would become something to be fully addressed in the future. [Other Info] These fixes have been applied to v5.15.27, and oem-5.14 currently has v5.15.25 in -1028, therefore only oem-5.14 is nominated, but probably they will still be included through stable patch backport in the next release. == original bug report == Observed choppy issue for touchpad on HP Lockheed with OEM-1025 kernel, and can't smoothly drag USB mouse if connected. Rolled back to OEM-1023 kernel and observed the same issues. Can't reproduce the issue with OEM-1022 kernel. Bisect identified the problematic commits below, 021e2c1f6143 drm/amdgpu/display: set vblank_disable_immediate for DC 1a4dd5a679da drm/amd/display: check top_pipe_to_program pointer Reverting above 2 commits on the top of oem-5.14-5.14.0-1025.27, touchpad or USB mouse back to normal working behavior on HP Lockheed and we don't see choppy trackpad/mouse issue. $ git log --oneline -5 62e596025e1e (HEAD -> fm_oem-5.14-next) Revert "drm/amd/display: check top_pipe_to_program pointer" 82cab088605f Revert "drm/amdgpu/display: set vblank_disable_immediate for DC" 165041ee003c (tag: Ubuntu-oem-5.14-5.14.0-1025.27, origin/oem-5.14-next) UBUNTU: Ubuntu-oem-5.14-5.14.0-1025.27 8bdd3e2ea820 UBUNTU: [Config] Update config to match upstream stable release 43f3b8b56abe UBUNTU: debian/dkms-versions -- update from kernel-versions (main/2022.02.21) To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1964850/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1967067] Re: WCN6856 BT keep in OFF state after coldboot system
This bug is awaiting verification that the linux-oem-5.14/5.14.0-1033.36 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1967067 Title: WCN6856 BT keep in OFF state after coldboot system Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Fix Committed Status in linux source package in Focal: Invalid Status in linux-oem-5.14 source package in Focal: Fix Committed Status in linux-oem-5.17 source package in Focal: Invalid Status in linux source package in Jammy: In Progress Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Committed Bug description: [SRU Justification] [Impact] WCN6856 BT keep in OFF state after coldboot system. [Fix] Mainline commit 599ece4f8f07 ("Bluetooth: btusb: Improve stability for QCA devices") added a 100ms delay for the underlying hw to apply downloaded firmware. [Test Case] This can be reproduced and therefore verified by checkbox poweroff stress test: $ checkbox-cli run com.canonical.certification::stress/poweroff [Where problems could occur] Unlikely to have side effect so far except slowing down boot process for a tiny moment. [Other Info] While this is only in the v5.18 merge window, all the kernels in use are affected and nominated here. == original bug report == [Reproduce Steps] 1.Insert WCN6856 card to SUT. 2.Press power button to power on SUT. 3.Clean install Ubuntu 20.04. 4.Check BT function after installation is complete. 5.Coldboot system and check the BT function. 6.Repeat step5, Issue occur. 7.Only found with CB, can't reproduce on WB. [Results] Expected Result BT function work normally. Actual Result BT has no function. Can't turn ON BT function. Need CB to recover BT function. "WB" and "swicth tab" cannot restore the BT function. [Others] Wifi function work normally. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1967067/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1966841] Re: alsa/sdw: Fix the audio issue on a Dell machine without internal mic
This bug is awaiting verification that the linux-oem-5.14/5.14.0-1033.36 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1966841 Title: alsa/sdw: Fix the audio issue on a Dell machine without internal mic Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Fix Committed Status in linux source package in Focal: Invalid Status in linux-oem-5.14 source package in Focal: Fix Committed Status in linux-oem-5.17 source package in Focal: Invalid Status in linux source package in Jammy: In Progress Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Committed Bug description: [Impact] we have a Dell ADL laptop which has sdw audio, but there is no camera and no internal digital mic in this machine, the current soc driver can't work on this machine, it will load a wrong tplg without this patch, and the speaker and headset couldn't work. [Fix] Backport one patch from upstream. [Test] Boot the patched kernel on the machine, check dmesg, it loads the correct tplg, and test speaker and headset, all work well. [Where problems could occur] If it could introduce regression, it will be on the sdw codec matching for adl machines, then it will make the driver load wrong tplg and make output device and input device not work anymore. But this possibility is very low, we already tested the patch on some dell adl machines, no regression found. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1966841/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1967069] Re: Enable headset mic on Lenovo P360
This bug is awaiting verification that the linux-oem-5.14/5.14.0-1033.36 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1967069 Title: Enable headset mic on Lenovo P360 Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.14 source package in Focal: Fix Committed Status in linux source package in Jammy: Confirmed Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: [Impact] Headset microphone can't be detected when headset is plugged to front panel port. [Fix] Apply Realtek ALC897 quirk to enable headset mic. [Test] Once the fix is applied, the headset mic can be detected and it also works. [Where problems could occur] Audio quirk which applies to only one specific system, so there's no chance to regress existing systems. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1967069/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1942624] Re: NVME "can't change power state from D3Cold to D0 (config space inaccessible)"
FYI - this was CC'ed into stable, and went to 5.15.y stable. Here is the reference for it: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/drivers/acpi/power.c?h=linux-5.15.y=bc28368596436e6e81ffc48c815b8225d96121c0 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1942624 Title: NVME "can't change power state from D3Cold to D0 (config space inaccessible)" Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.14 package in Ubuntu: In Progress Status in linux source package in Focal: Invalid Status in linux-oem-5.14 source package in Focal: In Progress Status in linux source package in Impish: In Progress Status in linux-oem-5.14 source package in Impish: Invalid Bug description: Bug with kernels after version 5.11.0-18 on Lenovo Ideapad 330-15ICH. The NVME drive with my root partition cannot be mounted at boot with an error "can't change power state from D3Cold to D0 (config space inaccessible)". I'm willing to help find a root cause if I don't need to spent too many hours. All Ubuntu kernels after 5.11.0-18 exhibit this bug, but I could boot properly with the official linux kernel 5.13.0. Thanks a lot for your help ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-18-generic 5.11.0-18.19 ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: chris 7503 F pulseaudio /dev/snd/pcmC0D0p: chris 7503 F...m pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Sep 3 18:46:35 2021 InstallationDate: Installed on 2019-07-17 (779 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 5986:210e Acer, Inc EasyCamera Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bluetooth wireless interface Bus 001 Device 007: ID 1050:0407 Yubico.com Yubikey 4/5 OTP+U2F+CCID Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 81FK ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-18-generic root=UUID=9d963312-3a16-428d-8efd-f1323c6528f1 ro quiet nosplash crashkernel=512M-:192M RelatedPackageVersions: linux-restricted-modules-5.11.0-18-generic N/A linux-backports-modules-5.11.0-18-generic N/A linux-firmware 1.197.3 SourcePackage: linux UpgradeStatus: Upgraded to hirsute on 2021-06-03 (92 days ago) dmi.bios.date: 10/24/2018 dmi.bios.release: 1.29 dmi.bios.vendor: LENOVO dmi.bios.version: 7ZCN29WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 330-15ICH dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvr7ZCN29WW:bd10/24/2018:br1.29:efr1.29:svnLENOVO:pn81FK:pvrLenovoideapad330-15ICH:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoideapad330-15ICH: dmi.product.family: ideapad 330-15ICH dmi.product.name: 81FK dmi.product.sku: LENOVO_MT_81FK_BU_idea_FM_ideapad 330-15ICH dmi.product.version: Lenovo ideapad 330-15ICH dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1942624/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1967814] proposed backport
Default Comment by Bridge ** Attachment added: "proposed backport" https://bugs.launchpad.net/bugs/1967814/+attachment/5577049/+files/backport_qemu-4.2.mbox ** Changed in: ubuntu Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team) ** Package changed: ubuntu => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1967814 Title: Ubuntu 20.04.3 - ilzlnx3g1 - virtio-scsi devs on KVM guest having miscompares on disktests when there is a failed path. Status in linux package in Ubuntu: New Bug description: == Comment: #63 - Halil Pasic - 2022-03-28 17:33:34 == I'm pretty confident I've figured out what is going on. From the guest side, the decision whether the SCSI command was completed successfully or not comes down to looking at the sense data. Prior to commit a108557bbf ("scsi: inline sg_io_sense_from_errno() into the callers."), we don't build sense data as a response to seeing a host status presented by the host SCSI stack (e.g. kernel). Thus when the kernel tells us that a given SCSI command did not get completed via SCSI_HOST_TRANSPORT_DISRUPTED or SCSI_HOST_NO_LUN, we end up fooling the guest into believing that the command completed successfully. The guest kernel, and especially virtio and multipath are at no fault (AFAIU). Given these facts, it isn't all that surprising, that we end up with corruptions. All we have to do is do backports for QEMU (when necessary). I didn't investigate vhost-scsi -- my guess is, that it ain't affected. How do we want to handle the back-ports? == Comment: #66 - Halil Pasic - 2022-04-04 05:36:33 == This is a proposed backport containing 7 patches in mbox format. I tried to pick patches sanely, and all I had to do was basically resolving merge conflicts. I have to admit I have no extensive experience in doing such invasive backports, and my knowledge of the QEMU SCSI stack is very limited. I would be happy if the Ubuntu folks would have a good look at this, and if possible improve on it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967814/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1967814] [NEW] Ubuntu 20.04.3 - ilzlnx3g1 - virtio-scsi devs on KVM guest having miscompares on disktests when there is a failed path.
You have been subscribed to a public bug: == Comment: #63 - Halil Pasic - 2022-03-28 17:33:34 == I'm pretty confident I've figured out what is going on. >From the guest side, the decision whether the SCSI command was completed >successfully or not comes down to looking at the sense data. Prior to commit a108557bbf ("scsi: inline sg_io_sense_from_errno() into the callers."), we don't build sense data as a response to seeing a host status presented by the host SCSI stack (e.g. kernel). Thus when the kernel tells us that a given SCSI command did not get completed via SCSI_HOST_TRANSPORT_DISRUPTED or SCSI_HOST_NO_LUN, we end up fooling the guest into believing that the command completed successfully. The guest kernel, and especially virtio and multipath are at no fault (AFAIU). Given these facts, it isn't all that surprising, that we end up with corruptions. All we have to do is do backports for QEMU (when necessary). I didn't investigate vhost-scsi -- my guess is, that it ain't affected. How do we want to handle the back-ports? == Comment: #66 - Halil Pasic - 2022-04-04 05:36:33 == This is a proposed backport containing 7 patches in mbox format. I tried to pick patches sanely, and all I had to do was basically resolving merge conflicts. I have to admit I have no extensive experience in doing such invasive backports, and my knowledge of the QEMU SCSI stack is very limited. I would be happy if the Ubuntu folks would have a good look at this, and if possible improve on it. ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Skipper Bug Screeners (skipper-screen-team) Status: New ** Tags: architecture-s39064 bugnameltc-195744 severity-high targetmilestone-inin--- -- Ubuntu 20.04.3 - ilzlnx3g1 - virtio-scsi devs on KVM guest having miscompares on disktests when there is a failed path. https://bugs.launchpad.net/bugs/1967814 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1967188] Re: Trackpoint not working on Thinkpad X1 tablet Gen 2 after boot, but after suspend
Tried with a live medium of Ubuntu Jammy Beta. Also reproducable here. -- 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/1967188 Title: Trackpoint not working on Thinkpad X1 tablet Gen 2 after boot, but after suspend Status in linux package in Ubuntu: Confirmed Bug description: I have Thinkpad X1 Gen 2 and the Trackpoint is not working directly after boot. I am aware that there was a bug which is fixed in current kernels. But I believe this bug is different. I am running KDE Neon which is based on Ubuntu 20.04, but I have also tested this with Kubuntu 20.04. Both running with current HWE-Kernel 5.13.0.39.44~20.04.24 I would also liked to have tested it with current 22.04 daily iso's but I could not get a booting live image with multisystem. What is the difference to the formerly known bugs: It is possible to get the Trackpoint working by sending the system into suspend and waking it up again. After this the Trackpoint works without a problem. So the problem might have something to do with the driver not correctly loaded at boot, but this is done correctly when the system wakes up from suspend. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kubuntu3913 F pulseaudio CasperMD5CheckResult: pass CasperVersion: 1.468 CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 LiveMediaBuild: Kubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) Lsusb: Bus 002 Device 002: ID 0781:55ab SanDisk Corp. SanDisk 3.2Gen1 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bluetooth wireless interface Bus 001 Device 002: ID 17ef:6085 Lenovo ThinkPad X1 Tablet Thin Keyboard Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20JBCTO1WW Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash --- ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 RelatedPackageVersions: linux-restricted-modules-5.15.0-23-generic N/A linux-backports-modules-5.15.0-23-generic N/A linux-firmware 20220314.gitcd01f857-0ubuntu2 StagingDrivers: ipu3_imgu Tags: jammy staging Uname: Linux 5.15.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/29/2021 dmi.bios.release: 1.43 dmi.bios.vendor: LENOVO dmi.bios.version: N1OET58W (1.43 ) dmi.board.asset.tag: Not Available dmi.board.name: 20JBCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0K17763 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 32 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.23 dmi.modalias: dmi:bvnLENOVO:bvrN1OET58W(1.43):bd11/29/2021:br1.43:efr1.23:svnLENOVO:pn20JBCTO1WW:pvrThinkPadX1TabletGen2:rvnLENOVO:rn20JBCTO1WW:rvrSDK0K17763WIN:cvnLENOVO:ct32:cvrNone:skuLENOVO_MT_20JB_BU_Think_FM_ThinkPad: dmi.product.family: ThinkPad dmi.product.name: 20JBCTO1WW dmi.product.sku: LENOVO_MT_20JB_BU_Think_FM_ThinkPad dmi.product.version: ThinkPad X1 Tablet Gen 2 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967188/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1937295] Re: [SRU]PCI: vmd: Do not disable MSI-X remapping if interrupt remapping is enabled by IOMMU
** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1937295 Title: [SRU]PCI: vmd: Do not disable MSI-X remapping if interrupt remapping is enabled by IOMMU Status in subiquity: Invalid Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Invalid Status in linux source package in Focal: In Progress Status in linux source package in Impish: Fix Released Status in linux source package in Jammy: Fix Released Bug description: [Impact] A hardware partner discovered they were unable to install Ubuntu on some servers using VROC setups. They point to this issue involving DMAR that is blocking discovery of the VROC RAID devices: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=2565e5b69c44b4e42469afea3cc5a97e74d1ed45 `git bisect` points to this offending commit ee81ee84f873 ("PCI: vmd: Disable MSI-X remapping when possible"), which disables VMD MSI remapping. The IOMMU hardware blocks the compatibility format interrupt request because Interrupt Remapping Enable Status (IRES) and Extended Interrupt Mode Enable (EIME) are enabled. Please refer to section "5.1.4 Interrupt-Remapping Hardware Operation" in Intel VT-d spec. To fix the issue, VMD driver still enables the interrupt remapping irrespective of VMD_FEAT_CAN_BYPASS_MSI_REMAP if the IOMMU subsystem enables the interrupt remapping. [Fix] 2565e5b69c44 PCI: vmd: Do not disable MSI-X remapping if interrupt remapping is enabled by IOMMU [Test Plan] 1. Boot into VRoC controller in uEFI Setup and create a raid10 disk. 2. Install affected Ubuntu release on the RAID10. 3. The system hangs at "Partitions formatting 33%". [Where problems could occur] The fix itself is a very small change to drivers/pci/controller/vmd.c and problems should not occur. The root cause was discovered by the hardware partner's engineers, who tested and submitted it upstream where it was accepted and landed in 5.16. That said, I doubt this will fix 18.04.6 as it would require a respin to get the patched kernel onto the ISO. 20.04 should pick it up in ISO in 20.04.5, so there could still be the initial issue since those ISOs would be lacking the patched kernel. [Other Info] As noted, this would need to not only land in the kernel but land in the kernel in the ISO to resolve the issue in the installation process. I'll bring this back as far as Focal with the expectation that while 20.04.4 is too late, it will be present using the GA kernel in 20.04.5 later on. * Original Bug Summary: A hardware partner has been testing 18.04 subiquity images on their servers with VROC enabled and configured in a RAID 10 setup. In their own words: Steps to reproduce: 1. Boot into VRoC controller in uEFI Setup and create a raid10 disk. 2. Install Ubuntu 18.04.5 on the RAID10. 3. The system hangs at "Partitions formatting 33%". After looking at the launchpad (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1896578/), the fix was included in the updated kernel. [Quotes from the launchpad] The released kernels are: Hirsute: 5.11.0-22-generic Groovy: 5.8.0-59-generic Focal: 5.4.0-77-generic Bionic: 4.15.0-147-generic I've asked them to also confirm this on 20.04.2, and check that 20.04.3 dailies fix the issue. It is at least a very reasonable hypothesis that this will also break on all current ISO installs as none of them are respun once released to include updated SRUs in the installation media. This currently affects 20.04.2 but that will be resolved shortly when 20.04.3 releases as the GA and HWE kernels in that image should have the SRU that fixes this issue. However, 18.04 has no further releases, and even the 18.04.5 daily-live and daily images on cdimages.ubuntu.com are not built after 18.04.5 was released. To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1937295/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1966066] Re: audio from external sound card is distorted
Same issue with Yamaha THR5 through USB on Ubuntu Studio 20.04.1. Disabled JACK and was able to fix the stutter. Edit in /etc/pulse/daemon.conf for 5.13.0-37 did not fix distorted audio. 5.13.0-39 exhibiting same problem. -- 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/1966066 Title: audio from external sound card is distorted Status in linux package in Ubuntu: Fix Committed Status in linux-signed-hwe-5.13 package in Ubuntu: Invalid Status in linux source package in Impish: In Progress Status in linux-signed-hwe-5.13 source package in Impish: Invalid Status in linux source package in Jammy: Fix Committed Status in linux-signed-hwe-5.13 source package in Jammy: Invalid Bug description: [Impact] Commit d215f63d49da ("ALSA: usb-audio: Check available frames for the next packet size") landed in 5.13.0-35 introduced regression to USB audio device. It's because this patch introduced the available frame size check, but the conversion forgot to initialize the temporary variable properly. A workaround is to modify /etc/pulse/daemon.conf, set the default-sample-rate to 48000, uncomment it by removing the semicolon at the beginning of the line. And restart pulseaudio with: systemctl --user restart pulseaudio.service [Fix] * 23939115 ALSA: usb-audio: Fix packet size calculation regression This patch can be cherry-picked into Impish kernel, and it's already in the master-next branch of Jammy tree. [Test] Test kernels built with 5.13.0-37 + this patch, can be found in: * Focal-5.13 - https://people.canonical.com/~phlin/kernel/lp-1966066-usb-audio/focal/ * Impish-5.13 - https://people.canonical.com/~phlin/kernel/lp-1966066-usb-audio/impish/ Both kernels were tested by affected users and they're working as expected. [Where problems could occur] If this patch is incorrect, it might affect USB audio devices. [Original Bug Report] The sound card is a Focusrite Scarlett 2i2. The sound is distorted everywhere. Sound via HDMI works. Seen others having the same problem: (Edit because of previously wrong link here) https://askubuntu.com/questions/1398614/upgrading-to-5-13-0-37-generic-breaks-audio-with-external-audio-card ubuntu release: Ubuntu 20.04.4 LTS package name involved in bug: linux-image-5.13.0-37-generic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.13.0-37-generic 5.13.0-37.42~20.04.1 ProcVersionSignature: Ubuntu 5.13.0-35.40~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-35-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Mar 23 12:56:02 2022 InstallationDate: Installed on 2020-12-18 (459 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/+bug/1966066/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1962359] Re: Hibernation fails due to resource busy during swap file check
Same here. I have 48GB Ram and 76GB swap partition. Where did you see the error code -16 is EBUSY? -- 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/1962359 Title: Hibernation fails due to resource busy during swap file check Status in linux package in Ubuntu: Confirmed Bug description: Hopefully, the automatically collected information is useful. The issue manifests when I try to hibernate the device. I see the following in the logs: ~$ journalctl --no-hostname -b -1 | tail -6 Feb 25 08:23:54 systemd[1]: nvidia-hibernate.service: Deactivated successfully. Feb 25 08:23:54 systemd[1]: Finished NVIDIA system hibernate actions. Feb 25 08:23:54 systemd[1]: Starting Hibernate... Feb 25 08:23:54 kernel: PM: Image not found (code -16) Feb 25 08:23:54 systemd-sleep[50360]: Entering sleep state 'hibernate'... Feb 25 08:23:54 kernel: PM: hibernation: hibernation entry I looked up error code 16 as EBUSY. This happens when using pm- hibernate or "systemctl hibernate". I played qaround with the nvidia systemd hibernate units but it didn't help. Hibernate used to work before I upgraded to jammy. I was on focal and bionic before that. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-18-generic 5.15.0-18.18 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Feb 26 09:27:29 2022 InstallationDate: Installed on 2019-08-07 (933 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Gigabyte Technology Co., Ltd. X399 AORUS XTREME ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-18-generic root=UUID=08f6326a-30f9-4f23-bab7-72a48afad354 ro quiet splash resume=UUID=08f6326a-30f9-4f23-bab7-72a48afad354 resume_offset=34816 vt.handoff=7 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.15.0-18-generic N/A linux-backports-modules-5.15.0-18-generic N/A linux-firmware 20220217.git6342082c-0ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/11/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F5 dmi.board.asset.tag: Default string dmi.board.name: X399 AORUS XTREME-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF5:bd12/11/2019:br5.14:svnGigabyteTechnologyCo.,Ltd.:pnX399AORUSXTREME:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX399AORUSXTREME-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: Default string dmi.product.name: X399 AORUS XTREME dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1962359/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1967336] Re: linux-azure: CONFIG_HIBERNATION=y
** Changed in: linux-azure (Ubuntu Impish) Status: In Progress => Fix Committed ** Changed in: linux-azure (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-azure in Ubuntu. https://bugs.launchpad.net/bugs/1967336 Title: linux-azure: CONFIG_HIBERNATION=y Status in linux-azure package in Ubuntu: Fix Committed Status in linux-azure source package in Focal: Fix Committed Status in linux-azure source package in Impish: Fix Committed Status in linux-azure source package in Jammy: Fix Committed Bug description: SRU Justification [Impact] Azure arm64 tuned kernels do not support hibernation. [Test Plan] Microsoft tested [Where things could go wrong] Hibernation may fail. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1967336/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1967166] Re: Azure: not enough RAM under 4GB for CVM
** Changed in: linux-azure (Ubuntu Impish) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1967166 Title: Azure: not enough RAM under 4GB for CVM Status in linux-azure package in Ubuntu: Fix Committed Status in linux-azure source package in Impish: Fix Committed Status in linux-azure source package in Jammy: Fix Committed Bug description: SRU Justification [Impact] Can you please include one more patchset for the "no enough RAM under 4GB" issue for the v5.13 kernel (and v5.15 kernel): https://lwn.net/ml/linux-kernel/20220209122302.213882-2-ltyker...@gmail.com/ https://lwn.net/ml/linux-kernel/20220209122302.213882-3-ltyker...@gmail.com/ Without the two patches, currently the 5.13 kernel (and 5.15 kernel) can't boot as a CVM guest on Azure. :-( The background is: currently an Azure host only provides about 900 MB memory below the 4GB boundary while the swiotlb code (which is required by the CVM patchset) needs to allocate memory of a size of MIN(1GB, 6% of the total memory). There will be an Azure host update, with which the host will provide about 3GB memory below the 4GB boundary, but we still need to wait a few more weeks to know the ETA. Currently the above two patches can work around the issue from the guest side. [Test Case] Microsoft tested [Where things could go wrong] These patches could affect non-CVM instances. [Other Info] SF: #00323683 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1967166/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1939638] Re: [regression] USB device is not detected during boot
The log I attached in comment #15 is from a cold boot, but I'm seeing all four combinations of outcomes: cold boot -> failing cold boot -> working warm boot -> failing warm boot -> working on ~40 Focal servers with identical hardware. (Except for a different RAID controller in three of them which doesn't seem to matter.) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1939638 Title: [regression] USB device is not detected during boot Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-intel package in Ubuntu: Confirmed Status in linux-intel-5.13 package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Released Status in linux-intel source package in Focal: Confirmed Status in linux-intel-5.13 source package in Focal: Fix Released Status in linux source package in Hirsute: Fix Released Status in linux-intel source package in Hirsute: Invalid Status in linux-intel-5.13 source package in Hirsute: Invalid Bug description: [SRU Justification] [Impact] The USB devices (keyboard, storage...) are failed to be detected when connecting to the problematic root hubs which need longer PowerOn-to-PowerGood delay than it claims in the hub descriptor. It's caused by the upstream fix 90d28fb53d4a ("usb: core: reduce power-on-good delay time of root hub"). [Fix] Reverting the upstream fix until a formal fix been placed. [Test Case] 1. Plug the USB device to the ports of problematic root hub. 2. Power on the machine. 3. Check if the USB device can work or not after boot. [Regression Potential] Low. The longer delay is proven safe in old kernels. == Original Bug Description == [Summary] The USB devices (keyboard, storage...) are failed to be detected during boot after upgrade to UBUNTU focal kernel 5.4.0-78 and hirsute 5.11.0-26. However, they will be detected and working ok after re-plugging. The kernel output shows as down below during boot [ 39.350435] hub 1-0:1.0: USB hub found [ 39.398835] hub 1-0:1.0: 12 ports detected [ 39.622744] usb usb1-port3: couldn't allocate usb_device And when I plug out then plug in the same device, it shows [57210.794140] usb 1-3: new low-speed USB device number 4 using xhci_hcd [57210.951289] usb 1-3: New USB device found, idVendor=17ef, idProduct=6099, bcdDevice= 1.14 [57210.951293] usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=0 After doing kernel bisecting, we found the upstream commit https://github.com/torvalds/linux/commit/90d28fb53d4a51299ff324dede015d5cb11b88a2 makes the difference. It indicates that the delay for the root hub from power_on to power_good is not long enough. There was no problem if the delay is 100 ms. From the Hub Descriptor of the root hub, the value is 10 * 2 milliseconds. And the XHCI spec also says in section 5.4.8 """ The host is required to have power stable to the port within 20 milliseconds of the '0' to '1' transition of PP. If PPC = '1', software is responsible for waiting 20ms. """ The commit seems to follow the SPEC but could cause problems on some hubs. [Reproduce Steps] 1. Plug the USB device to the physical port #1 and #4 which belongs to high-speed hub. 2. Power on the machine. 3. Check if the USB device can work or not after boot. [Results] Expected: All usb devices connect to the hub should work OK. Actual: USB devices connects to high-speed hub can not be probed. [Additional Information] Kernel Version: focal 5.4.0-78 and hirsute 5.11.0-26 [Upstream bug] https://bugzilla.kernel.org/show_bug.cgi?id=214021 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1939638/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1967783] [NEW] Tocuhpad not getting recognized at all in Lenovo Ideapad Slim 3 after kernel upgrade
Public bug reported: Description:Ubuntu 20.04.4 LTS Release:20.04 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.13.0-30-generic 5.13.0-30.33~20.04.1 ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Apr 4 22:28:54 2022 InstallationDate: Installed on 2022-02-17 (46 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: linux-signed-hwe-5.13 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe-5.13 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "devices" https://bugs.launchpad.net/bugs/1967783/+attachment/5576971/+files/devices -- 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/1967783 Title: Tocuhpad not getting recognized at all in Lenovo Ideapad Slim 3 after kernel upgrade Status in linux-signed-hwe-5.13 package in Ubuntu: New Bug description: Description: Ubuntu 20.04.4 LTS Release: 20.04 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.13.0-30-generic 5.13.0-30.33~20.04.1 ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Apr 4 22:28:54 2022 InstallationDate: Installed on 2022-02-17 (46 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) 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/1967783/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1902464] Re: The rear panel of Lenovo P620 doesn't support more than one audio device at the same time
** Changed in: oem-priority Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/1902464 Title: The rear panel of Lenovo P620 doesn't support more than one audio device at the same time Status in HWE Next: New Status in OEM Priority Project: Fix Released Status in alsa-ucm-conf package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: Fix Released Status in alsa-ucm-conf source package in Focal: Fix Released Status in pulseaudio source package in Focal: Fix Released Bug description: == SRU Justification == [Impact] On P620, only single port can work on rear panel. For example, when the Line-Out is plugged, the Mic won't work anymore. [Fix] Use upstream version of UCM to handle port priority correctly, instead of separate ports into different profiles. [Test] Once the UCM is in place, all three ports of rear panel work correctly. [Where problems could occur] UCM is not a static thing - it's actually interpreted differently at higher level. So any change in userspace daemons other than PulseAudio may not like the change and can interpret the UCM in another way. == Original Bug Report == After backporting following patches from PA and alsa-ucm-conf and then it works. https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/290 https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/354 https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/355 https://github.com/alsa-project/alsa-ucm-conf/tree/master/ucm2/USB- Audio [landed by aa74f4c12eefcc98582572d2fc48982cf7478b51] Here is the test PPA: https://launchpad.net/~os369510/+archive/ubuntu/oem-package-test Since the upstream not yet accepted those patches, the regression potential may quite high. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1902464/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1967613] Re: Gnome session reset after docking station disconnects
Another logs, this time the message I see during startup, for a very short time. It takes place when laptop is attached to docking station. I think it is related to the issue. (there could be some typo due to wrong OCR or just normal typo; photo of the log attached) /dev/nvme1n1p5: clean, 3254465/44933420 files, 164533712/179704576 blocks [4.432458] ACPI Error: No handler for Region [ECSI] (a9c48894) [EmbeddedControl] (20210331/evregion-130) [4.432474] ACPI Error: Region EmbeddedControl (ID=3) has no handler (20210331/exfldio-261) [4.432495) ACPI Error: Aborting method \_SB.UBTC.ECRD due to previous error (AE_NOT_EXIST) (20210331/psparse-529) [4.432509] ACPI Error: Aborting method \_SB.UBTC._DSM due to previous error (AE_NOT_EXIST) (20210331/psparse-529) [4.432529] ucsi_acpi USBC000:00: ucsi_acpi_dsm: failed to evaluate _DSM 2 [5.103721] (drm:drm_dp_mst_dpcd_read [drm_kms_helper]] *ERROR* mstb f980abd7 port 1: DPCD read on addr 0x60 for 1 bytes NAKed ** Attachment added: "startup log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967613/+attachment/5576949/+files/vlcsnap-2022-04-04-17h27m33s118-2.png -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1967613 Title: Gnome session reset after docking station disconnects Status in linux package in Ubuntu: Confirmed Bug description: From time to time, GNOME session gets reset when usb-c cable from docking station gets disconnected. All applications gets closed and completely new, fresh GNOME session is created. This is not happening every single time, when the cable gets disconnected but in about 1/3 of cases. As I remember it's happening only when laptop is suspended or have screen locked. When the laptop is working, and screen isn't locked, it's not happening (I could be wrong but this is my observation). The bug is highly unpleasant because it's closing every single app on the computer, and every single process running in the current session. I'm almost sure it was happening for several last kernels, this is not a new issue, I had this problem for a long time (at least for 6 months). Attachment (20211018_210936.jpg) is related to it, it's the info I see on the screen when the bug occurs. Short info: Laptop: Thinkpad E14 Gen2 AMD, Ryzen 5 4500u, Sysytem: Ubuntu 21.10, GNOME 40.4.0, X11, kernel 5.13.0-39-generic, Docking station: Thinkpad USB-C Dock Gen2, 40AS, 20/06, 0090EU Logs: --- CASE 1 --- [Wed Mar 16 17:41:58 2022] sda: detected capacity change from 0 to 62333952 [Wed Mar 16 17:41:58 2022] sda: sda1 [Wed Mar 16 17:44:14 2022] usb 1-1: USB disconnect, device number 23 [Wed Mar 16 17:44:14 2022] usb 1-1.2: USB disconnect, device number 24 [Wed Mar 16 17:44:14 2022] usb 1-1.2.1: USB disconnect, device number 26 [Wed Mar 16 17:44:14 2022] [drm] DM_MST: stopping TM on aconnector: e676af82 [id: 89] [Wed Mar 16 17:44:14 2022] usb 2-1: USB disconnect, device number 14 [Wed Mar 16 17:44:14 2022] usb 2-1.1: USB disconnect, device number 15 [Wed Mar 16 17:44:14 2022] r8152 2-1.1:1.0 enx482ae38dc78a: Tx status -108 [Wed Mar 16 17:44:14 2022] kauditd_printk_skb: 10 callbacks suppressed [Wed Mar 16 17:44:14 2022] audit: type=1326 audit(1647449054.614:415): auid=1000 uid=1000 gid=1000 ses=3 subj=snap.snap-store.ubuntu-software pid=6236 comm="pool-org.gnome." exe="/snap/snap-store/558/usr/bin/snap-store" sig=0 arch=c03e syscall=251 compat=0 ip=0x7fbdde51d76d code=0x5 [Wed Mar 16 17:44:14 2022] audit: type=1326 audit(1647449054.614:416): auid=1000 uid=1000 gid=1000 ses=3 subj=snap.snap-store.ubuntu-software pid=6236 comm="pool-org.gnome." exe="/snap/snap-store/558/usr/bin/snap-store" sig=0 arch=c03e syscall=251 compat=0 ip=0x7fbdde51d76d code=0x5 [Wed Mar 16 17:44:14 2022] usb 2-1.2: USB disconnect, device number 16 [Wed Mar 16 17:44:14 2022] usb 2-1.3: USB disconnect, device number 17 [Wed Mar 16 17:44:14 2022] usb 2-1.3.4: USB disconnect, device number 18 [Wed Mar 16 17:44:14 2022] usb 1-1.3: USB disconnect, device number 25 [Wed Mar 16 17:44:14 2022] usb 1-1.3.3: USB disconnect, device number 27 [Wed Mar 16 17:44:14 2022] usb 1-1.3.3.1: USB disconnect, device number 48 [Wed Mar 16 17:44:14 2022] usb 1-1.3.3.2: USB disconnect, device number 29 [Wed Mar 16 17:44:14 2022] usb 1-1.3.3.3: USB disconnect, device number 30 [Wed Mar 16 17:44:14 2022] usb 1-1.3.3.4: USB disconnect, device number 31 [Wed Mar 16 17:44:14 2022] ACPI Error: No handler for Region [ECSI] (89f11df8) [EmbeddedControl] (20210331/evregion-130) [Wed Mar 16 17:44:14 2022] ACPI Error: Region EmbeddedControl (ID=3) has no handler (20210331/exfldio-261) [Wed Mar 16 17:44:14 2022] No Local Variables are initialized for Method [ECRD] [Wed Mar 16 17:44:14 2022] No
[Kernel-packages] [Bug 1964711] Re: [amdgpu] Locked Ubuntu is frozen and cannot be unlocked
I have now tested whether the issue is still resolved and it luckily is. So both after installing a version of amdgpu-pro and also after uninstalling this proprietary driver again, unlocking the system works again. Once the stable version of Ubuntu 22.04 is published, I will upgrade and try again. At this point, I don’t want to try a pre-release version to avoid having my only personal computer become inoperable. Also, I have yet to find a way to restore the resolution during the boot process. Specifically, the default resolution is used during the cryptsetup decryption stage and before (when only the mainboard manufacturer logo is shown). The BIOS configuration seems to be in order and is set to use the primary PCIe slot to which my monitor is connected. It’s not terrible that this is so, but I’d like to fix it. My internet searches have been unsuccessful though. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1964711 Title: [amdgpu] Locked Ubuntu is frozen and cannot be unlocked Status in linux-hwe-5.13 package in Ubuntu: Incomplete Bug description: After locking Ubuntu and leaving it unattended for a while, the operating system cannot be unlocked anymore. No means of user input (e.g. typing on the keyboard, moving the mouse) produce the lock screen and I have to shut down my computer by pressing down the power button. The attached monitor does not receive a signal from the computer during these attempts. This started to happen several weeks ago and worked without a problem before then. Due to the nature of this issue, I can neither report any errors occurring nor can I observe any other out of the ordinary things from happening. Thus, I don’t know which package is causing the issue. Also, this issue happens every time I leave the computer unattended for a longer time and lock it. However, locking it and triggering an input immediately after does produce the lock screen, so the lock screen seems to work in principle. Description: Ubuntu 20.04.4 LTS Release: 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.13/+bug/1964711/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1967750] Re: Intel: enable x86 AMX
** Changed in: linux (Ubuntu) Status: Incomplete => Triaged -- 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/1967750 Title: Intel: enable x86 AMX Status in linux package in Ubuntu: Triaged Bug description: [Impact] Enable AMX (aka TMUL) new instructions on the 5.15 kernel. [Test case] Tests have been performed directly by Intel. [Fix] Apply the following upstream commits: 20df73756148 ("selftests/x86/amx: Update the ARCH_REQ_XCOMP_PERM test") 063452fd94d1 ("x86/fpu/xstate: Fix the ARCH_REQ_XCOMP_PERM implementation") fa31a4d669bd ("x86/cpufeatures: Put the AMX macros in the word 18 block") 6c3118c32129 ("signal: Skip the altstack update when not needed") 52d0b8b18776 ("x86/fpu/signal: Initialize sw_bytes in save_xstate_epilog()") d7a9590f608d ("Documentation/x86: Add documentation for using dynamic XSTATE features") 101c669d165d ("selftests/x86/amx: Add context switch test") 6a3e0651b4a0 ("selftests/x86/amx: Add test cases for AMX state management") 2308ee57d93d ("x86/fpu/amx: Enable the AMX feature in 64-bit mode") db3e7321b4b8 ("x86/fpu: Add XFD handling for dynamic states") 2ae996e0c1a3 ("x86/fpu: Calculate the default sizes independently") eec2113eabd9 ("x86/fpu/amx: Define AMX state components and have it used for boot-time checks") 70c3f1671b0c ("x86/fpu/xstate: Prepare XSAVE feature table for gaps in state component numbers") 500afbf645a0 ("x86/fpu/xstate: Add fpstate_realloc()/free()") 783e87b40495 ("x86/fpu/xstate: Add XFD #NM handler") 672365477ae8 ("x86/fpu: Update XFD state where required") 5529acf47ec3 ("x86/fpu: Add sanity checks for XFD") 8bf26758ca96 ("x86/fpu: Add XFD state to fpstate") dae1bd583896 ("x86/msr-index: Add MSRs for XFD") c351101678ce ("x86/cpufeatures: Add eXtended Feature Disabling (XFD) feature bit") e61d6310a0f8 ("x86/fpu: Reset permission and fpstate on exec()") 9e798e9aa14c ("x86/fpu: Prepare fpu_clone() for dynamically enabled features") 53599b4d54b9 ("x86/fpu/signal: Prepare for variable sigframe length") 4b7ca609a33d ("x86/signal: Use fpu::__state_user_size for sigalt stack validation") 23686ef25d4a ("x86/fpu: Add basic helpers for dynamically enabled features") db8268df0983 ("x86/arch_prctl: Add controls for dynamic XSTATE components") c33f0a81a2cf ("x86/fpu: Add fpu_state_config::legacy_features") 6f6a7c09c406 ("x86/fpu: Add members to struct fpu to cache permission information") 84e4dccc8fce ("x86/fpu/xstate: Provide xstate_calculate_size()") 3aac3ebea08f ("x86/signal: Implement sigaltstack size validation") 1bdda24c4af6 ("signal: Add an optional check for altstack size") 582b01b6ab27 ("x86/fpu: Remove old KVM FPU interface") d69c1382e1b7 ("x86/kvm: Convert FPU handling to a single swap buffer") 69f6ed1d14c6 ("x86/fpu: Provide infrastructure for KVM FPU cleanup") 75c52dad5e32 ("x86/fpu: Prepare for sanitizing KVM FPU code") d72c87018d00 ("x86/fpu/xstate: Move remaining xfeature helpers to core") eda32f4f93b4 ("x86/fpu: Rework restore_regs_from_fpstate()") daddee247319 ("x86/fpu: Mop up xfeatures_mask_uabi()") 1c253ff2287f ("x86/fpu: Move xstate feature masks to fpu_*_cfg") 2bd264bce238 ("x86/fpu: Move xstate size to fpu_*_cfg") cd9ae7617449 ("x86/fpu/xstate: Cleanup size calculations") 617473acdfe4 ("x86/fpu: Cleanup fpu__init_system_xstate_size_legacy()") 578971f4e228 ("x86/fpu: Provide struct fpu_config") 5509cc78080d ("x86/fpu/signal: Use fpstate for size and features") 49e4eb4125d5 ("x86/fpu/xstate: Use fpstate for copy_uabi_to_xstate()") 3ac8d75778fc ("x86/fpu: Use fpstate in __copy_xstate_to_uabi_buf()") ad6ede407aae ("x86/fpu: Use fpstate in fpu_copy_kvm_uabi_to_fpstate()") 0b2d39aa0357 ("x86/fpu/xstate: Use fpstate for xsave_to_user_sigframe()") 073e627a4537 ("x86/fpu/xstate: Use fpstate for os_xsave()") be31dfdfd75b ("x86/fpu: Use fpstate::size") 248452ce21ae ("x86/fpu: Add size and mask information to fpstate") 2dd8eedc80b1 ("x86/process: Move arch_thread_struct_whitelist() out of line") f0cbc8b3cdf7 ("x86/fpu: Do not leak fpstate pointer on fork") 2f27b5034244 ("x86/fpu: Remove fpu::state") 63d6bdf36ce1 ("x86/math-emu: Convert to fpstate") c20942ce5128 ("x86/fpu/core: Convert to fpstate") 7e049e8b7459 ("x86/fpu/signal: Convert to fpstate") caee31a36c33 ("x86/fpu/regset: Convert to fpstate") cceb496420fa ("x86/fpu: Convert tracing to fpstate") 1c57572d754f ("x86/KVM: Convert to fpstate") 087df48c298c ("x86/fpu: Replace KVMs xstate component clearing") 18b3fa1ad15f ("x86/fpu: Convert restore_fpregs_from_fpstate() to struct fpstate") f83ac56acdad ("x86/fpu: Convert fpstate_init() to struct fpstate") 87d0e5be0fac ("x86/fpu: Provide struct fpstate") bf5d00470787 ("x86/fpu: Replace KVMs home brewed FPU copy to user") 079ec41b22b9 ("x86/fpu: Provide a proper function for
[Kernel-packages] [Bug 1934620] Re: NVIDIA A100-80GB GPU fails to initialize in R750xa, BAR Address setup failed if SR-IOV is disabled in BIOS
Hi Jeff, Original repro machine had ~1TB memory. Previously attached log snip: Memory: 1055972180K/1073051196K available (14339K kernel code, 2400K rwdata, 5008K rodata, 2736K init, 4964K bss, 17079016K reserved, 0K cma-reserved) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1934620 Title: NVIDIA A100-80GB GPU fails to initialize in R750xa, BAR Address setup failed if SR-IOV is disabled in BIOS Status in dellserver: Won't Fix Status in linux package in Ubuntu: Confirmed Bug description: Installing NVidia A100-80GB GPUs in R750XA fails to initialize BAR memory space for GPUs. Multiple error messages in kernel.log file. Summary: * Dell prefers to set SRIOV to disabled in bios globally * This bug does not occur IF: SRIOV is enabled in BIOS OR "pci=realloc=off" is passed to the kernel at boot time * This bug only affects systems with NVIDIA A100-80GB GPUs, it does not affect systems with NVIDIA A100-40GB GPUs To manage notifications about this bug go to: https://bugs.launchpad.net/dellserver/+bug/1934620/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1967613] Re: Gnome session reset after docking station disconnects
@seb128, sure, attachment "log.txt" (journalctl -b 0) contains what you request, and it was taken just after the issue. More or less, at ~17:05 I detached docking station, and after this I logged in and fresh GNOME session appeared to my eyes. Immediately after logging in I gathered the log.txt. ** Attachment added: "log, journalctl -b 0" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967613/+attachment/5576926/+files/log.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1967613 Title: Gnome session reset after docking station disconnects Status in linux package in Ubuntu: Confirmed Bug description: From time to time, GNOME session gets reset when usb-c cable from docking station gets disconnected. All applications gets closed and completely new, fresh GNOME session is created. This is not happening every single time, when the cable gets disconnected but in about 1/3 of cases. As I remember it's happening only when laptop is suspended or have screen locked. When the laptop is working, and screen isn't locked, it's not happening (I could be wrong but this is my observation). The bug is highly unpleasant because it's closing every single app on the computer, and every single process running in the current session. I'm almost sure it was happening for several last kernels, this is not a new issue, I had this problem for a long time (at least for 6 months). Attachment (20211018_210936.jpg) is related to it, it's the info I see on the screen when the bug occurs. Short info: Laptop: Thinkpad E14 Gen2 AMD, Ryzen 5 4500u, Sysytem: Ubuntu 21.10, GNOME 40.4.0, X11, kernel 5.13.0-39-generic, Docking station: Thinkpad USB-C Dock Gen2, 40AS, 20/06, 0090EU Logs: --- CASE 1 --- [Wed Mar 16 17:41:58 2022] sda: detected capacity change from 0 to 62333952 [Wed Mar 16 17:41:58 2022] sda: sda1 [Wed Mar 16 17:44:14 2022] usb 1-1: USB disconnect, device number 23 [Wed Mar 16 17:44:14 2022] usb 1-1.2: USB disconnect, device number 24 [Wed Mar 16 17:44:14 2022] usb 1-1.2.1: USB disconnect, device number 26 [Wed Mar 16 17:44:14 2022] [drm] DM_MST: stopping TM on aconnector: e676af82 [id: 89] [Wed Mar 16 17:44:14 2022] usb 2-1: USB disconnect, device number 14 [Wed Mar 16 17:44:14 2022] usb 2-1.1: USB disconnect, device number 15 [Wed Mar 16 17:44:14 2022] r8152 2-1.1:1.0 enx482ae38dc78a: Tx status -108 [Wed Mar 16 17:44:14 2022] kauditd_printk_skb: 10 callbacks suppressed [Wed Mar 16 17:44:14 2022] audit: type=1326 audit(1647449054.614:415): auid=1000 uid=1000 gid=1000 ses=3 subj=snap.snap-store.ubuntu-software pid=6236 comm="pool-org.gnome." exe="/snap/snap-store/558/usr/bin/snap-store" sig=0 arch=c03e syscall=251 compat=0 ip=0x7fbdde51d76d code=0x5 [Wed Mar 16 17:44:14 2022] audit: type=1326 audit(1647449054.614:416): auid=1000 uid=1000 gid=1000 ses=3 subj=snap.snap-store.ubuntu-software pid=6236 comm="pool-org.gnome." exe="/snap/snap-store/558/usr/bin/snap-store" sig=0 arch=c03e syscall=251 compat=0 ip=0x7fbdde51d76d code=0x5 [Wed Mar 16 17:44:14 2022] usb 2-1.2: USB disconnect, device number 16 [Wed Mar 16 17:44:14 2022] usb 2-1.3: USB disconnect, device number 17 [Wed Mar 16 17:44:14 2022] usb 2-1.3.4: USB disconnect, device number 18 [Wed Mar 16 17:44:14 2022] usb 1-1.3: USB disconnect, device number 25 [Wed Mar 16 17:44:14 2022] usb 1-1.3.3: USB disconnect, device number 27 [Wed Mar 16 17:44:14 2022] usb 1-1.3.3.1: USB disconnect, device number 48 [Wed Mar 16 17:44:14 2022] usb 1-1.3.3.2: USB disconnect, device number 29 [Wed Mar 16 17:44:14 2022] usb 1-1.3.3.3: USB disconnect, device number 30 [Wed Mar 16 17:44:14 2022] usb 1-1.3.3.4: USB disconnect, device number 31 [Wed Mar 16 17:44:14 2022] ACPI Error: No handler for Region [ECSI] (89f11df8) [EmbeddedControl] (20210331/evregion-130) [Wed Mar 16 17:44:14 2022] ACPI Error: Region EmbeddedControl (ID=3) has no handler (20210331/exfldio-261) [Wed Mar 16 17:44:14 2022] No Local Variables are initialized for Method [ECRD] [Wed Mar 16 17:44:14 2022] No Arguments are initialized for method [ECRD] [Wed Mar 16 17:44:14 2022] ACPI Error: Aborting method \_SB.UBTC.ECRD due to previous error (AE_NOT_EXIST) (20210331/psparse-529) [Wed Mar 16 17:44:14 2022] ACPI Error: Aborting method \_SB.UBTC.NTFY due to previous error (AE_NOT_EXIST) (20210331/psparse-529) [Wed Mar 16 17:44:14 2022] ACPI Error: Aborting method \_SB.PCI0.LPC0.EC0._Q4F due to previous error (AE_NOT_EXIST) (20210331/psparse-529) [Wed Mar 16 17:44:15 2022] audit: type=1326 audit(1647449056.306:417): auid=1000 uid=1000 gid=1000 ses=3 subj=snap.snap-store.ubuntu-software pid=6236 comm="pool-org.gnome." exe="/snap/snap-store/558/usr/bin/snap-store" sig=0 arch=c03e syscall=251
[Kernel-packages] [Bug 1962349] Re: Bolt doesn't work with native USB4 hosts
** Changed in: linux-oem-5.14 (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1962349 Title: Bolt doesn't work with native USB4 hosts Status in OEM Priority Project: New Status in bolt package in Ubuntu: Fix Released Status in linux package in Ubuntu: In Progress Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: In Progress Status in bolt source package in Focal: Fix Released Status in linux source package in Focal: Won't Fix Status in linux-oem-5.14 source package in Focal: Fix Committed Status in linux-oem-5.17 source package in Focal: Invalid Status in bolt source package in Impish: Fix Released Status in linux source package in Impish: Won't Fix Status in linux-oem-5.14 source package in Impish: Invalid Status in linux-oem-5.17 source package in Impish: Invalid Status in bolt source package in Jammy: Fix Released Status in linux source package in Jammy: In Progress Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: In Progress Bug description: [Impact] * AMD Yellow Carp provides integrated USB4 host controllers * When plugging in a Thunderbolt3 or USB4 device, users are unable to authorize it using the GUI due to an error message: "parent not authorized, deferring" [Test Plan] AMD Yellow Carp Host (issue this bug is about) -- * Plug in USB4 device or TBT3 to AMD Yellow Carp host * Ensure that PCI topology has populated * Observe that /sys/bus/thunderbolt/devices/DEVICE/authorized is "0" * Try to run `boltctl enroll $UUID` Alpine Ridge / Titan Ridge host (discrete controller) -- Start out on a host with discrete controller (Alpine Ridge or Titan Ridge) 1. sudo boltctl forget -a 2. Plug in dock 3. Make sure 'boltctl list' enumerates dock. 4. Check /sys/bus/thunderbolt/devices/domain0/iommu_dma_protection (value dependent upon host) - If 0; try to manually enroll using 'boltctl enroll $UUID' - If 1; ensure that device automatically enrolled with bolt. GUI Check - Ensure that devices show up in the Settings GUI and are now able to authorize. Note: for AMD platforms enumerating PCIe devices is a separate problem from BOLT handled by kernel tasks. GUI check is only about "authorization". [Where problems could occur] * Intel USB4 or TBT3 hosts also use bolt. They could have a problem with the new version of bolt. * This is very unlikely however since there is a through test suite, and up until now the entire industry has been using bolt on Intel controllers for a long time. * There haven't been any significant bugs reported upstream or in Ubuntu since 0.9.1 release. [Other Info] * This bug also occurs on Intel controllers from ICL, TGL or ALD, but in many cases they are automatically authorized to an iommu DMA policy. * It is fixed in bolt 0.9.1 or later release. * To solve the SRU, will backport 0.9.1 release from Impish. * I did look into backporting just the commit(s) for fixing this, but it's not a trivial backport. Quoting the changelog (https://gitlab.freedesktop.org/bolt/bolt/-/blob/master/CHANGELOG.md): "Additionally the unique_id of said host controller changes with every boot, which breaks one of the fundamental assumptions in boltd". To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1962349/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1774817] Re: Temperature sensors on x470 not reporting correctly
The new ASUS EC sensor (asus-ec-sensors) driver might help you - see https://www.phoronix.com/scan.php?page=news_item=Linux-5.18-HWMON for more information. This driver has been included in the first release candidate of the upcoming Linux 5.18 kernel (5.18-rc1). You can download this 5.18-rc1 kernel from https://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D and instructions on how to install and uninstall it are at https://wiki.ubuntu.com/Kernel/MainlineBuilds -- 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/1774817 Title: Temperature sensors on x470 not reporting correctly Status in linux package in Ubuntu: Triaged Bug description: x470-I ROG strix motherboard and Ryzen 2700 After sudo sensors-detect and answering yes to all the probes the net result is: "Sorry, no sensors were detected. Either your system has no sensors, or they are not supported, or they are connected to an I2C or SMBus adapter that is not supported." sensors output lists: asus-isa- Adapter: ISA adapter cpu_fan:0 RPM nouveau-pci-0900 Adapter: PCI adapter fan1: 0 RPM temp1:+65.0°C (high = +95.0°C, hyst = +3.0°C) (crit = +105.0°C, hyst = +5.0°C) (emerg = +135.0°C, hyst = +5.0°C) k10temp-pci-00c3 Adapter: PCI adapter temp1:+94.2°C (high = +70.0°C) Where the cpu fan is patently wrong and the k10temp likewise. The nouveau-pci-0900 appears to be the actual CPU temperature. May be related to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1740736 Other info: Description: Ubuntu 18.04 LTS Release: 18.04 version log: Ubuntu 4.15.0-22.24-generic 4.15.17 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774817/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1934620] Re: NVIDIA A100-80GB GPU fails to initialize in R750xa, BAR Address setup failed if SR-IOV is disabled in BIOS
HI Sujith, can you tell us what server this is, and how much RAM is in it? Just wondering. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1934620 Title: NVIDIA A100-80GB GPU fails to initialize in R750xa, BAR Address setup failed if SR-IOV is disabled in BIOS Status in dellserver: Won't Fix Status in linux package in Ubuntu: Confirmed Bug description: Installing NVidia A100-80GB GPUs in R750XA fails to initialize BAR memory space for GPUs. Multiple error messages in kernel.log file. Summary: * Dell prefers to set SRIOV to disabled in bios globally * This bug does not occur IF: SRIOV is enabled in BIOS OR "pci=realloc=off" is passed to the kernel at boot time * This bug only affects systems with NVIDIA A100-80GB GPUs, it does not affect systems with NVIDIA A100-40GB GPUs To manage notifications about this bug go to: https://bugs.launchpad.net/dellserver/+bug/1934620/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1967123] Re: Hang on boot after 'fb0: switching to inteldrmfb from EFI VGA'
This also happens with the kernel in xubuntu-22.04-beta-desktop- amd64.iso, so it will block me upgrading that machine to Jammy when it's released. Is there anything I can do to help? I'm not familiar with debugging kernel drivers, but I'm a competent general developer, and I'm prepared to put in some effort if given some guidance on where to start. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1967123 Title: Hang on boot after 'fb0: switching to inteldrmfb from EFI VGA' Status in linux-signed-oem-5.14 package in Ubuntu: New Bug description: I'm running Ubuntu 20.04 with HWE kernels. The 5.11 kernel stream has been working fine for me (and supported the network device on my reasonably recent PC, which 20.04's default kernel didn't). But the 5.13 and 5.14 kernels all hang on boot. If I edit the GRUB boot commands to let me see the boot messages, the hang occurs immediately after printing the message [1.044456] fb0: switching to inteldrmfb from EFI VGA I can boot this kernel fine if I add 'nomodeset' to the kernel command line. But then I get unusably low screen resolution. Instead, my workaround is to manually select a 5.11 kernel from the GRUB menu on every boot. I'm not able to provide a full set of kernel messages from a failed boot attempt, because of course the kernel doesn't boot to a point where I can save them to a file. But I attach a screenshot of the last screenful of messages before the hang, in case those are useful. I'll also attach dmesg logs from a successful boot of the 5.14 kernel with nomodeset, and from a boot of the 5.11 kernel which gives me full functionality. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.14.0-1031-oem 5.14.0-1031.34 ProcVersionSignature: Ubuntu 5.11.0-46.51~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Mar 30 12:47:47 2022 InstallationDate: Installed on 2013-06-01 (3223 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: linux-signed-oem-5.14 UpgradeStatus: Upgraded to focal on 2020-08-31 (575 days ago) modified.conffile..etc.default.apport: [modified] mtime.conffile..etc.default.apport: 2013-06-02T15:20:08.886312 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-oem-5.14/+bug/1967123/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1967562] Re: jammy beta (220330) arm iso kernel panic during pxe boot
** Changed in: subiquity (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/1967562 Title: jammy beta (220330) arm iso kernel panic during pxe boot Status in linux package in Ubuntu: Incomplete Status in subiquity package in Ubuntu: Incomplete Bug description: = Description = Platforms: Ampere Mt. Jade Altra (bizzy), Cavium thunderX crb2s (recht) Image: Jammy Beta (220330) I setup my pxe server to provision jammy beta and got the following kernel panic message after grub stage: log from console log [1.176614] integrity: Couldn't parse dbx signatures: -74^M [1.371630] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)^M [1.379891] CPU: 42 PID: 1 Comm: swapper/0 Not tainted 5.15.0-23-generic #23-Ubuntu^M [1.387535] Hardware name: WIWYNN Mt.Jade Server System B81.030Z1.0007/Mt.Jade Motherboard, BIOS 1.6.20210526 (SCP: 1.06.20210526) 2021/05/26^M [1.400215] Call trace:^M [1.402649] dump_backtrace+0x0/0x1ec^M [1.406310] show_stack+0x24/0x30^M [1.409614] dump_stack_lvl+0x68/0x84^M [1.413271] dump_stack+0x18/0x34^M [1.416573] panic+0x18c/0x39c^M [1.419616] mount_block_root+0x160/0x210^M [1.423622] mount_root+0x12c/0x14c^M [1.427097] prepare_namespace+0x140/0x1a0^M [1.431182] kernel_init_freeable+0x1c8/0x214^M [1.435527] kernel_init+0x30/0x160^M [1.439006] ret_from_fork+0x10/0x20^M [1.442573] SMP: stopping secondary CPUs^M [1.447323] Kernel Offset: 0x55263ee9 from 0x8800^M [1.453404] PHYS_OFFSET: 0x8000^M [1.456879] CPU features: 0x85c1,a3302e42^M [1.461225] Memory Limit: none^M [1.464271] ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) ]---^M = Steps to Reproduce = 1. Followed this guide to setup the pxe server https://discourse.ubuntu.com/t/netbooting-the-live-server-installer-via-uefi-pxe-on-arm-aarch64-arm64-and-x86-64-amd64/19240 with the jammy beta image (220330) http://cdimage.ubuntu.com/ubuntu-server/daily-live/20220330/jammy-live-server-arm64.iso 1-1. You may use this script to perform the set-up https://github.com/tai271828/ubuntu-autoinstall-pxe-server by invoking: `sudo ./setup-pxe-server.sh --url http://cdimage.ubuntu.com/ubuntu-server/daily-live/20220330/jammy-live-server-arm64.iso` 2. Boot the system via PXE 3. Select Ubuntu at Grub menu = Expected Result = The image is loaded to the system locally via PXE, and subiquity is launched = Actual Result = Console log simply shows nothing for 10 seconds and then the kernel panic shows up. = Additional Information = - If we install via the virtual CD of the server, subiquity could be launched and the installation process completes successfully. - MAAS could deploy Jammy to the Mt. Jade server as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967562/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1967754] Re: ubuntu 22.04 jammy, mlx5, can't change flow steering mode
https://lore.kernel.org/netdev/cover.1632565508.git.leo...@nvidia.com/ It seems jammy kernel needs cf530217408e ("devlink: Notify users when objects are accessible") from v5.16-rc1 (see link) the old devlink_register (before cf530217408e) implementation do not publish the params so we cannot erase the calls to devlink_params_publish. i'll update once finished testing with cf530217408e ported. -- 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/1967754 Title: ubuntu 22.04 jammy, mlx5, can't change flow steering mode Status in linux package in Ubuntu: Incomplete Bug description: on kernel 5.15.0-23-generic devlink cannot show/change flow steering mode [test case] # devlink dev param show pci/:24:00.0 name flow_steering_mode pci/:24:00.0: name flow_steering_mode type driver-specific values: (flow steering mode description is missing beneath "values:") # devlink dev param set pci/:24:00.0 name flow_steering_mode value smfs cmode runtime Segmentation fault (core dumped) and also with upstream iproute # ./iproute2/devlink/devlink dev param set pci/:24:00.0 name flow_steering_mode value smfs cmode runtime Configuration mode not supported this issue is a degradation introduced by commit from jammy tree 76385c47db37 ("net/mlx5: Accept devlink user input after driver initialization complete") issue do not repro on v5.15.0 or when the above commit is reverted. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967754/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1967754] Re: ubuntu 22.04 jammy, mlx5, can't change flow steering mode
** Description changed: - - on kernel 5.15.0-23-generic devlink cannot show/change flow steering mode + on kernel 5.15.0-23-generic devlink cannot show/change flow steering + mode [test case] # devlink dev param show pci/:24:00.0 name flow_steering_mode pci/:24:00.0: - name flow_steering_mode type driver-specific - values: - - (flow steering mode description is missing beneath values) + name flow_steering_mode type driver-specific + values: + (flow steering mode description is missing beneath "values:") # devlink dev param set pci/:24:00.0 name flow_steering_mode value smfs cmode runtime Segmentation fault (core dumped) and also with upstream iproute # ./iproute2/devlink/devlink dev param set pci/:24:00.0 name flow_steering_mode value smfs cmode runtime Configuration mode not supported this issue is a degradation introduced by commit from jammy tree 76385c47db37 ("net/mlx5: Accept devlink user input after driver initialization complete") issue do not repro on v5.15.0 or when the above commit is reverted. -- 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/1967754 Title: ubuntu 22.04 jammy, mlx5, can't change flow steering mode Status in linux package in Ubuntu: Incomplete Bug description: on kernel 5.15.0-23-generic devlink cannot show/change flow steering mode [test case] # devlink dev param show pci/:24:00.0 name flow_steering_mode pci/:24:00.0: name flow_steering_mode type driver-specific values: (flow steering mode description is missing beneath "values:") # devlink dev param set pci/:24:00.0 name flow_steering_mode value smfs cmode runtime Segmentation fault (core dumped) and also with upstream iproute # ./iproute2/devlink/devlink dev param set pci/:24:00.0 name flow_steering_mode value smfs cmode runtime Configuration mode not supported this issue is a degradation introduced by commit from jammy tree 76385c47db37 ("net/mlx5: Accept devlink user input after driver initialization complete") issue do not repro on v5.15.0 or when the above commit is reverted. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967754/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1967562] Re: jammy beta (220330) arm iso kernel panic during pxe boot
@Paolo , thanks for verifying. Right, MAAS deployment looks good (see my comment of "Additional Information" in the bug description) as what Dann pointed out. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1967562 Title: jammy beta (220330) arm iso kernel panic during pxe boot Status in linux package in Ubuntu: Incomplete Status in subiquity package in Ubuntu: New Bug description: = Description = Platforms: Ampere Mt. Jade Altra (bizzy), Cavium thunderX crb2s (recht) Image: Jammy Beta (220330) I setup my pxe server to provision jammy beta and got the following kernel panic message after grub stage: log from console log [1.176614] integrity: Couldn't parse dbx signatures: -74^M [1.371630] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)^M [1.379891] CPU: 42 PID: 1 Comm: swapper/0 Not tainted 5.15.0-23-generic #23-Ubuntu^M [1.387535] Hardware name: WIWYNN Mt.Jade Server System B81.030Z1.0007/Mt.Jade Motherboard, BIOS 1.6.20210526 (SCP: 1.06.20210526) 2021/05/26^M [1.400215] Call trace:^M [1.402649] dump_backtrace+0x0/0x1ec^M [1.406310] show_stack+0x24/0x30^M [1.409614] dump_stack_lvl+0x68/0x84^M [1.413271] dump_stack+0x18/0x34^M [1.416573] panic+0x18c/0x39c^M [1.419616] mount_block_root+0x160/0x210^M [1.423622] mount_root+0x12c/0x14c^M [1.427097] prepare_namespace+0x140/0x1a0^M [1.431182] kernel_init_freeable+0x1c8/0x214^M [1.435527] kernel_init+0x30/0x160^M [1.439006] ret_from_fork+0x10/0x20^M [1.442573] SMP: stopping secondary CPUs^M [1.447323] Kernel Offset: 0x55263ee9 from 0x8800^M [1.453404] PHYS_OFFSET: 0x8000^M [1.456879] CPU features: 0x85c1,a3302e42^M [1.461225] Memory Limit: none^M [1.464271] ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) ]---^M = Steps to Reproduce = 1. Followed this guide to setup the pxe server https://discourse.ubuntu.com/t/netbooting-the-live-server-installer-via-uefi-pxe-on-arm-aarch64-arm64-and-x86-64-amd64/19240 with the jammy beta image (220330) http://cdimage.ubuntu.com/ubuntu-server/daily-live/20220330/jammy-live-server-arm64.iso 1-1. You may use this script to perform the set-up https://github.com/tai271828/ubuntu-autoinstall-pxe-server by invoking: `sudo ./setup-pxe-server.sh --url http://cdimage.ubuntu.com/ubuntu-server/daily-live/20220330/jammy-live-server-arm64.iso` 2. Boot the system via PXE 3. Select Ubuntu at Grub menu = Expected Result = The image is loaded to the system locally via PXE, and subiquity is launched = Actual Result = Console log simply shows nothing for 10 seconds and then the kernel panic shows up. = Additional Information = - If we install via the virtual CD of the server, subiquity could be launched and the installation process completes successfully. - MAAS could deploy Jammy to the Mt. Jade server as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967562/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1967562] Re: jammy beta (220330) arm iso kernel panic during pxe boot
@dann , I checked the grub entry prior to filing this bug. For now the pxe server is used for the other purpose. Let me reproduce the post- mortem information later on. Thanks for the tip! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1967562 Title: jammy beta (220330) arm iso kernel panic during pxe boot Status in linux package in Ubuntu: Incomplete Status in subiquity package in Ubuntu: New Bug description: = Description = Platforms: Ampere Mt. Jade Altra (bizzy), Cavium thunderX crb2s (recht) Image: Jammy Beta (220330) I setup my pxe server to provision jammy beta and got the following kernel panic message after grub stage: log from console log [1.176614] integrity: Couldn't parse dbx signatures: -74^M [1.371630] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)^M [1.379891] CPU: 42 PID: 1 Comm: swapper/0 Not tainted 5.15.0-23-generic #23-Ubuntu^M [1.387535] Hardware name: WIWYNN Mt.Jade Server System B81.030Z1.0007/Mt.Jade Motherboard, BIOS 1.6.20210526 (SCP: 1.06.20210526) 2021/05/26^M [1.400215] Call trace:^M [1.402649] dump_backtrace+0x0/0x1ec^M [1.406310] show_stack+0x24/0x30^M [1.409614] dump_stack_lvl+0x68/0x84^M [1.413271] dump_stack+0x18/0x34^M [1.416573] panic+0x18c/0x39c^M [1.419616] mount_block_root+0x160/0x210^M [1.423622] mount_root+0x12c/0x14c^M [1.427097] prepare_namespace+0x140/0x1a0^M [1.431182] kernel_init_freeable+0x1c8/0x214^M [1.435527] kernel_init+0x30/0x160^M [1.439006] ret_from_fork+0x10/0x20^M [1.442573] SMP: stopping secondary CPUs^M [1.447323] Kernel Offset: 0x55263ee9 from 0x8800^M [1.453404] PHYS_OFFSET: 0x8000^M [1.456879] CPU features: 0x85c1,a3302e42^M [1.461225] Memory Limit: none^M [1.464271] ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) ]---^M = Steps to Reproduce = 1. Followed this guide to setup the pxe server https://discourse.ubuntu.com/t/netbooting-the-live-server-installer-via-uefi-pxe-on-arm-aarch64-arm64-and-x86-64-amd64/19240 with the jammy beta image (220330) http://cdimage.ubuntu.com/ubuntu-server/daily-live/20220330/jammy-live-server-arm64.iso 1-1. You may use this script to perform the set-up https://github.com/tai271828/ubuntu-autoinstall-pxe-server by invoking: `sudo ./setup-pxe-server.sh --url http://cdimage.ubuntu.com/ubuntu-server/daily-live/20220330/jammy-live-server-arm64.iso` 2. Boot the system via PXE 3. Select Ubuntu at Grub menu = Expected Result = The image is loaded to the system locally via PXE, and subiquity is launched = Actual Result = Console log simply shows nothing for 10 seconds and then the kernel panic shows up. = Additional Information = - If we install via the virtual CD of the server, subiquity could be launched and the installation process completes successfully. - MAAS could deploy Jammy to the Mt. Jade server as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967562/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1967579] Re: harden indirect calls against BHI attacks
** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: Incomplete ** Changed in: linux (Ubuntu Jammy) Status: Incomplete => In Progress ** Changed in: linux (Ubuntu Jammy) Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo) ** Changed in: linux (Ubuntu Jammy) 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/1967579 Title: harden indirect calls against BHI attacks Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: In Progress Bug description: [Impact] Branch History Injection is made easier when all indirect calls are funneled through very few points where the retpolines were. By replacing the retpoline jumps by indirect calls whenever retpolines are disabled, BHI attacks are more difficult to execute as the BTB is not as fixed as before. [Fixes] Though there are fixes that allow retpoline,lfence to be directly replaced in the indirect calls, given that mitigation is not recommended for most of the situations, that hardening is not as important as the one that works for the spectre_v2=off option (the default one for systems with eIBRS). This latter one is present starting with 5.13, but backporting to 5.4 might be a good measure. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967579/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1967750] 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 1967750 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/1967750 Title: Intel: enable x86 AMX Status in linux package in Ubuntu: Incomplete Bug description: [Impact] Enable AMX (aka TMUL) new instructions on the 5.15 kernel. [Test case] Tests have been performed directly by Intel. [Fix] Apply the following upstream commits: 20df73756148 ("selftests/x86/amx: Update the ARCH_REQ_XCOMP_PERM test") 063452fd94d1 ("x86/fpu/xstate: Fix the ARCH_REQ_XCOMP_PERM implementation") fa31a4d669bd ("x86/cpufeatures: Put the AMX macros in the word 18 block") 6c3118c32129 ("signal: Skip the altstack update when not needed") 52d0b8b18776 ("x86/fpu/signal: Initialize sw_bytes in save_xstate_epilog()") d7a9590f608d ("Documentation/x86: Add documentation for using dynamic XSTATE features") 101c669d165d ("selftests/x86/amx: Add context switch test") 6a3e0651b4a0 ("selftests/x86/amx: Add test cases for AMX state management") 2308ee57d93d ("x86/fpu/amx: Enable the AMX feature in 64-bit mode") db3e7321b4b8 ("x86/fpu: Add XFD handling for dynamic states") 2ae996e0c1a3 ("x86/fpu: Calculate the default sizes independently") eec2113eabd9 ("x86/fpu/amx: Define AMX state components and have it used for boot-time checks") 70c3f1671b0c ("x86/fpu/xstate: Prepare XSAVE feature table for gaps in state component numbers") 500afbf645a0 ("x86/fpu/xstate: Add fpstate_realloc()/free()") 783e87b40495 ("x86/fpu/xstate: Add XFD #NM handler") 672365477ae8 ("x86/fpu: Update XFD state where required") 5529acf47ec3 ("x86/fpu: Add sanity checks for XFD") 8bf26758ca96 ("x86/fpu: Add XFD state to fpstate") dae1bd583896 ("x86/msr-index: Add MSRs for XFD") c351101678ce ("x86/cpufeatures: Add eXtended Feature Disabling (XFD) feature bit") e61d6310a0f8 ("x86/fpu: Reset permission and fpstate on exec()") 9e798e9aa14c ("x86/fpu: Prepare fpu_clone() for dynamically enabled features") 53599b4d54b9 ("x86/fpu/signal: Prepare for variable sigframe length") 4b7ca609a33d ("x86/signal: Use fpu::__state_user_size for sigalt stack validation") 23686ef25d4a ("x86/fpu: Add basic helpers for dynamically enabled features") db8268df0983 ("x86/arch_prctl: Add controls for dynamic XSTATE components") c33f0a81a2cf ("x86/fpu: Add fpu_state_config::legacy_features") 6f6a7c09c406 ("x86/fpu: Add members to struct fpu to cache permission information") 84e4dccc8fce ("x86/fpu/xstate: Provide xstate_calculate_size()") 3aac3ebea08f ("x86/signal: Implement sigaltstack size validation") 1bdda24c4af6 ("signal: Add an optional check for altstack size") 582b01b6ab27 ("x86/fpu: Remove old KVM FPU interface") d69c1382e1b7 ("x86/kvm: Convert FPU handling to a single swap buffer") 69f6ed1d14c6 ("x86/fpu: Provide infrastructure for KVM FPU cleanup") 75c52dad5e32 ("x86/fpu: Prepare for sanitizing KVM FPU code") d72c87018d00 ("x86/fpu/xstate: Move remaining xfeature helpers to core") eda32f4f93b4 ("x86/fpu: Rework restore_regs_from_fpstate()") daddee247319 ("x86/fpu: Mop up xfeatures_mask_uabi()") 1c253ff2287f ("x86/fpu: Move xstate feature masks to fpu_*_cfg") 2bd264bce238 ("x86/fpu: Move xstate size to fpu_*_cfg") cd9ae7617449 ("x86/fpu/xstate: Cleanup size calculations") 617473acdfe4 ("x86/fpu: Cleanup fpu__init_system_xstate_size_legacy()") 578971f4e228 ("x86/fpu: Provide struct fpu_config") 5509cc78080d ("x86/fpu/signal: Use fpstate for size and features") 49e4eb4125d5 ("x86/fpu/xstate: Use fpstate for copy_uabi_to_xstate()") 3ac8d75778fc ("x86/fpu: Use fpstate in __copy_xstate_to_uabi_buf()") ad6ede407aae ("x86/fpu: Use fpstate in fpu_copy_kvm_uabi_to_fpstate()") 0b2d39aa0357 ("x86/fpu/xstate: Use fpstate for xsave_to_user_sigframe()") 073e627a4537 ("x86/fpu/xstate: Use fpstate for os_xsave()") be31dfdfd75b ("x86/fpu: Use fpstate::size") 248452ce21ae ("x86/fpu: Add size and mask information to fpstate") 2dd8eedc80b1 ("x86/process: Move arch_thread_struct_whitelist() out of line") f0cbc8b3cdf7 ("x86/fpu: Do not leak fpstate pointer on fork") 2f27b5034244 ("x86/fpu: Remove fpu::state") 63d6bdf36ce1 ("x86/math-emu: Convert to fpstate") c20942ce5128 ("x86/fpu/core: Convert to fpstate") 7e049e8b7459 ("x86/fpu/signal: Convert to fpstate") caee31a36c33
[Kernel-packages] [Bug 1967754] 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 1967754 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/1967754 Title: ubuntu 22.04 jammy, mlx5, can't change flow steering mode Status in linux package in Ubuntu: Incomplete Bug description: on kernel 5.15.0-23-generic devlink cannot show/change flow steering mode [test case] # devlink dev param show pci/:24:00.0 name flow_steering_mode pci/:24:00.0: name flow_steering_mode type driver-specific values: (flow steering mode description is missing beneath values) # devlink dev param set pci/:24:00.0 name flow_steering_mode value smfs cmode runtime Segmentation fault (core dumped) and also with upstream iproute # ./iproute2/devlink/devlink dev param set pci/:24:00.0 name flow_steering_mode value smfs cmode runtime Configuration mode not supported this issue is a degradation introduced by commit from jammy tree 76385c47db37 ("net/mlx5: Accept devlink user input after driver initialization complete") issue do not repro on v5.15.0 or when the above commit is reverted. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967754/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1967754] [NEW] ubuntu 22.04 jammy, mlx5, can't change flow steering mode
Public bug reported: on kernel 5.15.0-23-generic devlink cannot show/change flow steering mode [test case] # devlink dev param show pci/:24:00.0 name flow_steering_mode pci/:24:00.0: name flow_steering_mode type driver-specific values: (flow steering mode description is missing beneath values) # devlink dev param set pci/:24:00.0 name flow_steering_mode value smfs cmode runtime Segmentation fault (core dumped) and also with upstream iproute # ./iproute2/devlink/devlink dev param set pci/:24:00.0 name flow_steering_mode value smfs cmode runtime Configuration mode not supported this issue is a degradation introduced by commit from jammy tree 76385c47db37 ("net/mlx5: Accept devlink user input after driver initialization complete") issue do not repro on v5.15.0 or when the above commit is reverted. ** Affects: linux (Ubuntu) Importance: Undecided Status: 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/1967754 Title: ubuntu 22.04 jammy, mlx5, can't change flow steering mode Status in linux package in Ubuntu: Incomplete Bug description: on kernel 5.15.0-23-generic devlink cannot show/change flow steering mode [test case] # devlink dev param show pci/:24:00.0 name flow_steering_mode pci/:24:00.0: name flow_steering_mode type driver-specific values: (flow steering mode description is missing beneath values) # devlink dev param set pci/:24:00.0 name flow_steering_mode value smfs cmode runtime Segmentation fault (core dumped) and also with upstream iproute # ./iproute2/devlink/devlink dev param set pci/:24:00.0 name flow_steering_mode value smfs cmode runtime Configuration mode not supported this issue is a degradation introduced by commit from jammy tree 76385c47db37 ("net/mlx5: Accept devlink user input after driver initialization complete") issue do not repro on v5.15.0 or when the above commit is reverted. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967754/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1961329] Re: linux-azure: Update HV support to 5.17
** Changed in: linux-azure (Ubuntu Impish) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1961329 Title: linux-azure: Update HV support to 5.17 Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure source package in Focal: New Status in linux-azure source package in Impish: Fix Committed Status in linux-azure source package in Jammy: Fix Released Bug description: SRU Justification [Impact] Microsoft has requested these commits be present in all Azure tuned kernels: ac0f7d42584125dab8039e60ab4ade48cc2db61c Drivers: hv: copy from message page only what's needed a276463b7aeb6186e7e4315cccb032773fb31b5d Drivers: hv: allocate the exact needed memory for messages 5cc415001bca8fe0e3f0ee6d58a953a314dd9751 Drivers: hv: avoid passing opaque pointer to vmbus_onmessage() b0a284dc65b401a508dc2c5ed7d465884220f607 Drivers: hv: make sure that 'struct vmbus_channel_message_header' compiles correctly 52c7803f9bd4b1f0ac6e2e3e6051415198cc06bd Drivers: hv: check VMBus messages lengths 06caa778d8b2fbcb4ac3878751e39d116424ba9b hv_utils: Add validation for untrusted Hyper-V values e99c4afbee07e9323e9191a20b24d74dbf815bdf Drivers: hv: vmbus: Initialize memory to be sent to the host fe8c1b18a27de4d6ca5d99b3ffb3125dc69a5b76 Drivers: hv: vmbus: Copy the hv_message in vmbus_on_msg_dpc() e3fa4b747f085d2cda09bba0533b86fa76038635 Drivers: hv: vmbus: Avoid use-after-free in vmbus_onoffer_rescind() e4d221b42354b2e2ddb9187a806afb651eee2cda Drivers: hv: vmbus: Resolve race condition in vmbus_onoffer_rescind() adae1e931acd8b430d31141a283ea06d4b705417 Drivers: hv: vmbus: Copy packets sent by Hyper-V out of the ring buffer 9d68cd9120e4e3af38f843e165631c323b86b4e4 hv_utils: Set the maximum packet size for VSS driver to the length of the receive buffer f1940d4e9cbe6208e7e77e433c587af108152a17 Drivers: hv: vmbus: Fix kernel crash upon unbinding a device from uio_hv_generic driver 007faec014cb5d26983c1f86fd08c6539b41392e x86/sev: Expose sev_es_ghcb_hv_call() for use by HyperV 0cc4f6d9f0b9f20f3f1e1149bdb6737c0b4e134a x86/hyperv: Initialize GHCB page in Isolation VM af788f355e343373490b7d2e361016e7c24a0ffa x86/hyperv: Initialize shared memory boundary in the Isolation VM. 810a521265023a1d5c6c081ea2d216bc63d422f5 x86/hyperv: Add new hvcall guest address host visibility support d4dccf353db80e209f262e3973c834e6e48ba9a9 Drivers: hv: vmbus: Mark vmbus ring buffer visible to host in Isolation VM faff44069ff538ccdfef187c4d7ec83d22dfb3a4 x86/hyperv: Add Write/Read MSR registers via ghcb page 20c89a559e00dfe352b73e867211a669113ae881 x86/hyperv: Add ghcb hvcall support for SNP VM f2f136c05fb6093818a3b3fefcba46231ac66a62 Drivers: hv: vmbus: Add SNP support for VMbus channel initiate message 9a8797722e4239242d0cb4cc4baa805df6ac979e Drivers: hv: vmbus: Initialize VMbus ring buffer for Isolation VM 1a5e91d8375fc8369207cc0b9894a324f2bbf1d9 swiotlb: Add swiotlb bounce buffer remap function for HV IVM c789b90a69045d1924bc0802ae0dce2bba05a04e x86/hyper-v: Add hyperv Isolation VM check in the cc_platform_has() 062a5c4260cdb734a4727230c58e38accf413315 hyper-v: Enable swiotlb bounce buffer for Isolation VM 743b237c3a7b0f5b44aa704aae8a1058877b6322 scsi: storvsc: Add Isolation VM support for storvsc driver 846da38de0e8224f2f94b885125cf1fd2d7b0d39 net: netvsc: Add Isolation VM support for netvsc driver 2deb55d9f57bb7a877c0d77115cc4077e1e974ff swiotlb: Add CONFIG_HAS_IOMEM check around swiotlb_mem_remap() 6a27e396ebb149fc47baccc1957a7a9dd70049a7 Drivers: hv: vmbus: Initialize request offers message for Isolation VM 4eea5332d67d8ae6ba5717ec0f4e671fdbd222e7 scsi: storvsc: Fix storvsc_queuecommand() memory leak 96d9d1fa5cd505078534113308ced0aa56d8da58 Drivers: hv: balloon: account for vmbus packet header in max_pkt_size [Test Plan] Microsoft tested [Where things could go wrong] Hyper-V guests may not work correctly. [Other Info] SF: #00323683 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1961329/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1967750] [NEW] Intel: enable x86 AMX
Public bug reported: [Impact] Enable AMX (aka TMUL) new instructions on the 5.15 kernel. [Test case] Tests have been performed directly by Intel. [Fix] Apply the following upstream commits: 20df73756148 ("selftests/x86/amx: Update the ARCH_REQ_XCOMP_PERM test") 063452fd94d1 ("x86/fpu/xstate: Fix the ARCH_REQ_XCOMP_PERM implementation") fa31a4d669bd ("x86/cpufeatures: Put the AMX macros in the word 18 block") 6c3118c32129 ("signal: Skip the altstack update when not needed") 52d0b8b18776 ("x86/fpu/signal: Initialize sw_bytes in save_xstate_epilog()") d7a9590f608d ("Documentation/x86: Add documentation for using dynamic XSTATE features") 101c669d165d ("selftests/x86/amx: Add context switch test") 6a3e0651b4a0 ("selftests/x86/amx: Add test cases for AMX state management") 2308ee57d93d ("x86/fpu/amx: Enable the AMX feature in 64-bit mode") db3e7321b4b8 ("x86/fpu: Add XFD handling for dynamic states") 2ae996e0c1a3 ("x86/fpu: Calculate the default sizes independently") eec2113eabd9 ("x86/fpu/amx: Define AMX state components and have it used for boot-time checks") 70c3f1671b0c ("x86/fpu/xstate: Prepare XSAVE feature table for gaps in state component numbers") 500afbf645a0 ("x86/fpu/xstate: Add fpstate_realloc()/free()") 783e87b40495 ("x86/fpu/xstate: Add XFD #NM handler") 672365477ae8 ("x86/fpu: Update XFD state where required") 5529acf47ec3 ("x86/fpu: Add sanity checks for XFD") 8bf26758ca96 ("x86/fpu: Add XFD state to fpstate") dae1bd583896 ("x86/msr-index: Add MSRs for XFD") c351101678ce ("x86/cpufeatures: Add eXtended Feature Disabling (XFD) feature bit") e61d6310a0f8 ("x86/fpu: Reset permission and fpstate on exec()") 9e798e9aa14c ("x86/fpu: Prepare fpu_clone() for dynamically enabled features") 53599b4d54b9 ("x86/fpu/signal: Prepare for variable sigframe length") 4b7ca609a33d ("x86/signal: Use fpu::__state_user_size for sigalt stack validation") 23686ef25d4a ("x86/fpu: Add basic helpers for dynamically enabled features") db8268df0983 ("x86/arch_prctl: Add controls for dynamic XSTATE components") c33f0a81a2cf ("x86/fpu: Add fpu_state_config::legacy_features") 6f6a7c09c406 ("x86/fpu: Add members to struct fpu to cache permission information") 84e4dccc8fce ("x86/fpu/xstate: Provide xstate_calculate_size()") 3aac3ebea08f ("x86/signal: Implement sigaltstack size validation") 1bdda24c4af6 ("signal: Add an optional check for altstack size") 582b01b6ab27 ("x86/fpu: Remove old KVM FPU interface") d69c1382e1b7 ("x86/kvm: Convert FPU handling to a single swap buffer") 69f6ed1d14c6 ("x86/fpu: Provide infrastructure for KVM FPU cleanup") 75c52dad5e32 ("x86/fpu: Prepare for sanitizing KVM FPU code") d72c87018d00 ("x86/fpu/xstate: Move remaining xfeature helpers to core") eda32f4f93b4 ("x86/fpu: Rework restore_regs_from_fpstate()") daddee247319 ("x86/fpu: Mop up xfeatures_mask_uabi()") 1c253ff2287f ("x86/fpu: Move xstate feature masks to fpu_*_cfg") 2bd264bce238 ("x86/fpu: Move xstate size to fpu_*_cfg") cd9ae7617449 ("x86/fpu/xstate: Cleanup size calculations") 617473acdfe4 ("x86/fpu: Cleanup fpu__init_system_xstate_size_legacy()") 578971f4e228 ("x86/fpu: Provide struct fpu_config") 5509cc78080d ("x86/fpu/signal: Use fpstate for size and features") 49e4eb4125d5 ("x86/fpu/xstate: Use fpstate for copy_uabi_to_xstate()") 3ac8d75778fc ("x86/fpu: Use fpstate in __copy_xstate_to_uabi_buf()") ad6ede407aae ("x86/fpu: Use fpstate in fpu_copy_kvm_uabi_to_fpstate()") 0b2d39aa0357 ("x86/fpu/xstate: Use fpstate for xsave_to_user_sigframe()") 073e627a4537 ("x86/fpu/xstate: Use fpstate for os_xsave()") be31dfdfd75b ("x86/fpu: Use fpstate::size") 248452ce21ae ("x86/fpu: Add size and mask information to fpstate") 2dd8eedc80b1 ("x86/process: Move arch_thread_struct_whitelist() out of line") f0cbc8b3cdf7 ("x86/fpu: Do not leak fpstate pointer on fork") 2f27b5034244 ("x86/fpu: Remove fpu::state") 63d6bdf36ce1 ("x86/math-emu: Convert to fpstate") c20942ce5128 ("x86/fpu/core: Convert to fpstate") 7e049e8b7459 ("x86/fpu/signal: Convert to fpstate") caee31a36c33 ("x86/fpu/regset: Convert to fpstate") cceb496420fa ("x86/fpu: Convert tracing to fpstate") 1c57572d754f ("x86/KVM: Convert to fpstate") 087df48c298c ("x86/fpu: Replace KVMs xstate component clearing") 18b3fa1ad15f ("x86/fpu: Convert restore_fpregs_from_fpstate() to struct fpstate") f83ac56acdad ("x86/fpu: Convert fpstate_init() to struct fpstate") 87d0e5be0fac ("x86/fpu: Provide struct fpstate") bf5d00470787 ("x86/fpu: Replace KVMs home brewed FPU copy to user") 079ec41b22b9 ("x86/fpu: Provide a proper function for ex_handler_fprestore()") b56d2795b297 ("x86/fpu: Replace the includes of fpu/internal.h") 6415bb809263 ("x86/fpu: Mop up the internal.h leftovers") ff0c37e191f2 ("x86/sev: Include fpu/xcr.h") 0ae67cc34f76 ("x86/fpu: Remove internal.h dependency from fpu/signal.h") 90489f1dee8b ("x86/fpu: Move fpstate functions to api.h") d9d005f32aac ("x86/fpu: Move mxcsr related code to core") 9848fb96839b ("x86/fpu: Move fpregs_restore_userregs() to core") cdcb6fa14e14
[Kernel-packages] [Bug 1967748] 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/1967748 Title: kswapd0 take 100% processor Status in linux package in Ubuntu: Confirmed Bug description: Hello I don't know if this is normal operation or if it is possible to configure KSWAPD0. I installed version 22.04 (jammy) choosing encrypted ZFS partitioning in an external disk. The installation chose to assign the swap partition to SDC2. On reboot, this partition does not exist. Depending on how I reboot it is either seen as SDA2 or SDB2. So I deactivated and opened a bug (https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1962409) However, this does not seem to block me. So I decided to continue using ZFS. My first decision was to copy the contents of my personal data partition to a directory under rpool/USERDATA with the RSYNC command This action lasts several hours and requires a lot of inputs and outputs. I noticed that firefox stopped responding. Every second, a message asking if I want to wait is displayed. I also saw that the KSWAPD0 process almost permanently consumes a processor. All this seems to me to be related to the copy. ( time sudo rsync -av --exclude {'.Trash*','Downloads','$RECYCLE.BIN'} /media/Common /Common ) I know that ZFS wants to use the full RAM (6GB) to be able to maximally compress the data. So my question is whether this is completely normal. I would still like to be able to consult the Internet while copying a directory. I post under KSWAP0 without knowing if he is entirely responsible. thank you ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-23-generic 5.15.0-23.23 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: a 3727 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Apr 4 14:27:55 2022 HibernationDevice: RESUME=none InstallationDate: Installed on 2022-04-01 (2 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) MachineType: TOSHIBA SATELLITE S70t-A ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_b4yff9@/vmlinuz-5.15.0-23-generic root=ZFS=rpool/ROOT/ubuntu_b4yff9 ro RelatedPackageVersions: linux-restricted-modules-5.15.0-23-generic N/A linux-backports-modules-5.15.0-23-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/18/2014 dmi.bios.release: 1.30 dmi.bios.vendor: Insyde Corp. dmi.bios.version: 1.30 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Type2 - Board Product Name1 dmi.board.vendor: Type2 - Board Vendor Name1 dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: OEM Chassis Manufacturer dmi.chassis.version: OEM Chassis Version dmi.ec.firmware.release: 1.30 dmi.modalias: dmi:bvnInsydeCorp.:bvr1.30:bd04/18/2014:br1.30:efr1.30:svnTOSHIBA:pnSATELLITES70t-A:pvrPSKN6E-01C00KFR:rvnType2-BoardVendorName1:rnType2-BoardProductName1:rvrType2-BoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:skuPSKN6E: dmi.product.family: Type1Family dmi.product.name: SATELLITE S70t-A dmi.product.sku: PSKN6E dmi.product.version: PSKN6E-01C00KFR dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967748/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1967130] Re: rcu_sched detected stalls on CPUs/tasks
I have a workaround for this: UBUNTU: SAUCE: riscv: Disable VMAP_STACK since it fails with efi When VMAP_STACK is enabled, kernel threads have their stacks in the vmalloc region. So when The kworker responsible for handling efi work queue (efi_call_rts) calls efi_virtmap_load and then switch_mm, if the stack of the worker is in a vmalloc area not yet synchronized with efi_mm (since RISC-V lazily populates vmalloc area), an attempt to access this stack will trigger a fault which can't be resolved since when trying to save the context, a new trap will be triggered and so on. So disable VMAP_STACK for now until we figure out the correct fix. And I'm working on the proper fix which consists in synchronizing the efi page table with the page table of the calling thread before switching to efi mm. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-riscv in Ubuntu. https://bugs.launchpad.net/bugs/1967130 Title: rcu_sched detected stalls on CPUs/tasks Status in linux-riscv package in Ubuntu: New Bug description: When running the riscv64 live installer (https://cdimage.ubuntu.com/ubuntu-server/daily-live/20220330/jammy- live-server-riscv64.iso) on the SiFive Unmatched board we reproducibly see rcu_sched stalls related to accessing the UEFI runtime: Mar 30 11:50:47 ubuntu-server kernel: [ 1313.451647] rcu: INFO: rcu_sched detected stalls on CPUs/tasks: Mar 30 11:50:47 ubuntu-server kernel: [ 1313.451673] rcu: 3-...0: (3 GPs behind) idle=d03/1/0x4000 softirq=85648/85648 fqs=7326 Mar 30 11:50:47 ubuntu-server kernel: [ 1313.451698](detected by 0, t=15002 jiffies, g=155853, q=1286) Mar 30 11:50:47 ubuntu-server kernel: [ 1313.451712] Task dump for CPU 3: Mar 30 11:50:47 ubuntu-server kernel: [ 1313.451720] task:kworker/u8:1 state:R running task stack:0 pid: 3715 ppid: 2 flags:0x0008 Mar 30 11:50:47 ubuntu-server kernel: [ 1313.451750] Workqueue: efi_rts_wq efi_call_rts Mar 30 11:50:47 ubuntu-server kernel: [ 1313.451777] Call Trace: Mar 30 11:50:47 ubuntu-server kernel: [ 1313.451782] [] __schedule+0x226/0x644 uname -a: Linux ubuntu-server 5.15.0-1004-generic #4-Ubuntu SMP Wed Feb 9 18:17:33 UTC 2022 riscv64 riscv64 riscv64 GNU/Linux --- ProblemType: Bug Architecture: riscv64 DistroRelease: Ubuntu 22.04 Package: linux-image-generic 5.15.0.1004.4 PackageArchitecture: riscv64 ProcEnviron: TERM=vt220 PATH=(custom, no user) LANG=C.UTF-8 Uname: Linux 5.15.0-1004-generic riscv64 UserGroups: N/A _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/1967130/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1967748] [NEW] kswapd0 take 100% processor
Public bug reported: Hello I don't know if this is normal operation or if it is possible to configure KSWAPD0. I installed version 22.04 (jammy) choosing encrypted ZFS partitioning in an external disk. The installation chose to assign the swap partition to SDC2. On reboot, this partition does not exist. Depending on how I reboot it is either seen as SDA2 or SDB2. So I deactivated and opened a bug (https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1962409) However, this does not seem to block me. So I decided to continue using ZFS. My first decision was to copy the contents of my personal data partition to a directory under rpool/USERDATA with the RSYNC command This action lasts several hours and requires a lot of inputs and outputs. I noticed that firefox stopped responding. Every second, a message asking if I want to wait is displayed. I also saw that the KSWAPD0 process almost permanently consumes a processor. All this seems to me to be related to the copy. ( time sudo rsync -av --exclude {'.Trash*','Downloads','$RECYCLE.BIN'} /media/Common /Common ) I know that ZFS wants to use the full RAM (6GB) to be able to maximally compress the data. So my question is whether this is completely normal. I would still like to be able to consult the Internet while copying a directory. I post under KSWAP0 without knowing if he is entirely responsible. thank you ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-23-generic 5.15.0-23.23 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: a 3727 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Apr 4 14:27:55 2022 HibernationDevice: RESUME=none InstallationDate: Installed on 2022-04-01 (2 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) MachineType: TOSHIBA SATELLITE S70t-A ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_b4yff9@/vmlinuz-5.15.0-23-generic root=ZFS=rpool/ROOT/ubuntu_b4yff9 ro RelatedPackageVersions: linux-restricted-modules-5.15.0-23-generic N/A linux-backports-modules-5.15.0-23-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/18/2014 dmi.bios.release: 1.30 dmi.bios.vendor: Insyde Corp. dmi.bios.version: 1.30 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Type2 - Board Product Name1 dmi.board.vendor: Type2 - Board Vendor Name1 dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: OEM Chassis Manufacturer dmi.chassis.version: OEM Chassis Version dmi.ec.firmware.release: 1.30 dmi.modalias: dmi:bvnInsydeCorp.:bvr1.30:bd04/18/2014:br1.30:efr1.30:svnTOSHIBA:pnSATELLITES70t-A:pvrPSKN6E-01C00KFR:rvnType2-BoardVendorName1:rnType2-BoardProductName1:rvrType2-BoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:skuPSKN6E: dmi.product.family: Type1Family dmi.product.name: SATELLITE S70t-A dmi.product.sku: PSKN6E dmi.product.version: PSKN6E-01C00KFR dmi.sys.vendor: TOSHIBA ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session ** Attachment added: "TOP -N 1" https://bugs.launchpad.net/bugs/1967748/+attachment/5576841/+files/KSWAPD0.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1967748 Title: kswapd0 take 100% processor Status in linux package in Ubuntu: New Bug description: Hello I don't know if this is normal operation or if it is possible to configure KSWAPD0. I installed version 22.04 (jammy) choosing encrypted ZFS partitioning in an external disk. The installation chose to assign the swap partition to SDC2. On reboot, this partition does not exist. Depending on how I reboot it is either seen as SDA2 or SDB2. So I deactivated and opened a bug (https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1962409) However, this does not seem to block me. So I decided to continue using ZFS. My first decision was to copy the contents of my personal data partition to a directory under rpool/USERDATA with the RSYNC command This action lasts several hours and requires a lot of inputs and outputs. I noticed that firefox stopped responding. Every second, a message asking if I want to wait is displayed. I also saw that the KSWAPD0 process almost permanently consumes a processor. All this seems to me to be related to the copy. ( time sudo
[Kernel-packages] [Bug 1964983] Re: IPU6 camera has no function on Andrews MLK
This bug was fixed in the package linux-oem-5.14 - 5.14.0-1032.35 --- linux-oem-5.14 (5.14.0-1032.35) focal; urgency=medium * focal/linux-oem-5.14: 5.14.0-1032.35 -proposed tracker (LP: #1967284) * IPU6 camera has no function on Andrews MLK (LP: #1964983) - SAUCE: IPU6: 2022-03-11 alpha release for Andrews MLK - [Config] IPU6: enable OV02C10 sensor * Fix audio on Zbook Studio G9 (LP: #1966010) - gpiolib: acpi: Convert ACPI value of debounce to microseconds - ALSA: hda/realtek: Fix LED on Zbook Studio G9 * alsa: enable the cirrus-logic side-codec to make the speaker output sound (LP: #1965496) - ASoC: cs35l41: CS35L41 Boosted Smart Amplifier - ASoC: cs35l41: Fix use of an uninitialised variable - ASoC: cs35l41: Use regmap_read_poll_timeout to wait for OTP boot - ASoC: cs35l41: Combine adjacent register writes - ASoC: cs35l41: Don't overwrite returned error code - ASoC: cs35l41: Fixup the error messages - ASoC: cs35l41: Fix a bunch of trivial code formating/style issues - misc: cs35l41: Remove unused pdn variable - ASoC: cs35l41: Make cs35l41_remove() return void - ASoC: cs35l41: Change monitor widgets to siggens - ASoC: cs35l41: DSP Support - ASoC: cs35l41: Set the max SPI speed for the whole device - ASoC: cs35l41: Fix link problem - ASoC: cs35l41: Fix undefined reference to core functions - ASoC: cs35l41: Convert tables to shared source code - ASoC: cs35l41: Move cs35l41_otp_unpack to shared code - ASoC: cs35l41: Move power initializations to reg_sequence - ASoC: cs35l41: Create shared function for errata patches - ASoC: cs35l41: Create shared function for setting channels - ASoC: cs35l41: Create shared function for boost configuration - ASoC: cs35l41: Add cs35l51/53 IDs - ASoC: cs35l41: Remove incorrect comment - ASoC: cs35l41: Correct DSP power down - ASoC: cs35l41: Correct handling of some registers in the cache - ALSA: hda: cs35l41: Add support for CS35L41 in HDA systems - ASoC: cs35l41: Update handling of test key registers - ALSA: hda: cs35l41: fix double free on error in probe() - ALSA: hda: cs35l41: Avoid overwriting register patch - ALSA: hda: cs35l41: Add calls to newly added test key function - ALSA: hda: cs35l41: Move cs35l41* calls to its own symbol namespace - ALSA: hda: cs35l41: Add missing default cases - ALSA: hda: cs35l41: Make use of the helper function dev_err_probe() - ALSA: hda: cs35l41: Tidyup code - ALSA: hda: cs35l41: Make cs35l41_hda_remove() return void - ALSA: hda/realtek: Add support for Legion 7 16ACHg6 laptop - ALSA: hda/realtek: Add CS35L41 support for Thinkpad laptops - ALSA: hda/realtek: fix speakers and micmute on HP 855 G8 - i2c: acpi: Add an i2c_acpi_client_count() helper function - platform/x86: i2c-multi-instantiate: Use the new i2c_acpi_client_count() helper - Revert "platform/x86: i2c-multi-instantiate: Don't create platform device for INT3515 ACPI nodes" - spi: Create helper API to lookup ACPI info for spi device - spi: Support selection of the index of the ACPI Spi Resource before alloc - spi: Add API to count spi acpi resources - platform/x86: i2c-multi-instantiate: Rename it for a generic serial driver name - platform/x86: serial-multi-instantiate: Reorganize I2C functions - platform/x86: serial-multi-instantiate: Add SPI support - ALSA: hda/realtek: Add support for HP Laptops - ACPI / scan: Create platform device for CS35L41 - [Config]: Add cirruslogic side codec support * Revert drm/amd/pm: enable ASPM by default (LP: #1966680) - SAUCE: Revert "drm/amd/pm: enable ASPM by default" * Enable the mic-mute led on Dell XPS 9315 (LP: #1965846) - SAUCE: ASoC: rt715:add micmute led control for Dell XPS 9315 * e1000e reports hardware hang (LP: #1966835) - e1000e: Fix possible HW unit hang after an s0ix exit * Miscellaneous upstream changes - ASoC: cs35l41: Add support for hibernate memory retention mode -- Timo Aaltonen Thu, 31 Mar 2022 15:38:08 +0300 ** Changed in: linux-oem-5.14 (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1964983 Title: IPU6 camera has no function on Andrews MLK Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Confirmed Status in linux source package in Focal: Invalid Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux-oem-5.17 source package in Focal: Invalid Status in linux source package in Jammy: In Progress Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy:
[Kernel-packages] [Bug 1966680] Re: Revert drm/amd/pm: enable ASPM by default
This bug was fixed in the package linux-oem-5.14 - 5.14.0-1032.35 --- linux-oem-5.14 (5.14.0-1032.35) focal; urgency=medium * focal/linux-oem-5.14: 5.14.0-1032.35 -proposed tracker (LP: #1967284) * IPU6 camera has no function on Andrews MLK (LP: #1964983) - SAUCE: IPU6: 2022-03-11 alpha release for Andrews MLK - [Config] IPU6: enable OV02C10 sensor * Fix audio on Zbook Studio G9 (LP: #1966010) - gpiolib: acpi: Convert ACPI value of debounce to microseconds - ALSA: hda/realtek: Fix LED on Zbook Studio G9 * alsa: enable the cirrus-logic side-codec to make the speaker output sound (LP: #1965496) - ASoC: cs35l41: CS35L41 Boosted Smart Amplifier - ASoC: cs35l41: Fix use of an uninitialised variable - ASoC: cs35l41: Use regmap_read_poll_timeout to wait for OTP boot - ASoC: cs35l41: Combine adjacent register writes - ASoC: cs35l41: Don't overwrite returned error code - ASoC: cs35l41: Fixup the error messages - ASoC: cs35l41: Fix a bunch of trivial code formating/style issues - misc: cs35l41: Remove unused pdn variable - ASoC: cs35l41: Make cs35l41_remove() return void - ASoC: cs35l41: Change monitor widgets to siggens - ASoC: cs35l41: DSP Support - ASoC: cs35l41: Set the max SPI speed for the whole device - ASoC: cs35l41: Fix link problem - ASoC: cs35l41: Fix undefined reference to core functions - ASoC: cs35l41: Convert tables to shared source code - ASoC: cs35l41: Move cs35l41_otp_unpack to shared code - ASoC: cs35l41: Move power initializations to reg_sequence - ASoC: cs35l41: Create shared function for errata patches - ASoC: cs35l41: Create shared function for setting channels - ASoC: cs35l41: Create shared function for boost configuration - ASoC: cs35l41: Add cs35l51/53 IDs - ASoC: cs35l41: Remove incorrect comment - ASoC: cs35l41: Correct DSP power down - ASoC: cs35l41: Correct handling of some registers in the cache - ALSA: hda: cs35l41: Add support for CS35L41 in HDA systems - ASoC: cs35l41: Update handling of test key registers - ALSA: hda: cs35l41: fix double free on error in probe() - ALSA: hda: cs35l41: Avoid overwriting register patch - ALSA: hda: cs35l41: Add calls to newly added test key function - ALSA: hda: cs35l41: Move cs35l41* calls to its own symbol namespace - ALSA: hda: cs35l41: Add missing default cases - ALSA: hda: cs35l41: Make use of the helper function dev_err_probe() - ALSA: hda: cs35l41: Tidyup code - ALSA: hda: cs35l41: Make cs35l41_hda_remove() return void - ALSA: hda/realtek: Add support for Legion 7 16ACHg6 laptop - ALSA: hda/realtek: Add CS35L41 support for Thinkpad laptops - ALSA: hda/realtek: fix speakers and micmute on HP 855 G8 - i2c: acpi: Add an i2c_acpi_client_count() helper function - platform/x86: i2c-multi-instantiate: Use the new i2c_acpi_client_count() helper - Revert "platform/x86: i2c-multi-instantiate: Don't create platform device for INT3515 ACPI nodes" - spi: Create helper API to lookup ACPI info for spi device - spi: Support selection of the index of the ACPI Spi Resource before alloc - spi: Add API to count spi acpi resources - platform/x86: i2c-multi-instantiate: Rename it for a generic serial driver name - platform/x86: serial-multi-instantiate: Reorganize I2C functions - platform/x86: serial-multi-instantiate: Add SPI support - ALSA: hda/realtek: Add support for HP Laptops - ACPI / scan: Create platform device for CS35L41 - [Config]: Add cirruslogic side codec support * Revert drm/amd/pm: enable ASPM by default (LP: #1966680) - SAUCE: Revert "drm/amd/pm: enable ASPM by default" * Enable the mic-mute led on Dell XPS 9315 (LP: #1965846) - SAUCE: ASoC: rt715:add micmute led control for Dell XPS 9315 * e1000e reports hardware hang (LP: #1966835) - e1000e: Fix possible HW unit hang after an s0ix exit * Miscellaneous upstream changes - ASoC: cs35l41: Add support for hibernate memory retention mode -- Timo Aaltonen Thu, 31 Mar 2022 15:38:08 +0300 ** Changed in: linux-oem-5.14 (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1966680 Title: Revert drm/amd/pm: enable ASPM by default Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Jammy: In Progress Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: [Impact] With WX3200 and 20.04d kernel the unit freezes on resume [Fix] commit 0064b0ce85bb ("drm/amd/pm: enable ASPM by default") enabled
[Kernel-packages] [Bug 1965496] Re: alsa: enable the cirrus-logic side-codec to make the speaker output sound
This bug was fixed in the package linux-oem-5.14 - 5.14.0-1032.35 --- linux-oem-5.14 (5.14.0-1032.35) focal; urgency=medium * focal/linux-oem-5.14: 5.14.0-1032.35 -proposed tracker (LP: #1967284) * IPU6 camera has no function on Andrews MLK (LP: #1964983) - SAUCE: IPU6: 2022-03-11 alpha release for Andrews MLK - [Config] IPU6: enable OV02C10 sensor * Fix audio on Zbook Studio G9 (LP: #1966010) - gpiolib: acpi: Convert ACPI value of debounce to microseconds - ALSA: hda/realtek: Fix LED on Zbook Studio G9 * alsa: enable the cirrus-logic side-codec to make the speaker output sound (LP: #1965496) - ASoC: cs35l41: CS35L41 Boosted Smart Amplifier - ASoC: cs35l41: Fix use of an uninitialised variable - ASoC: cs35l41: Use regmap_read_poll_timeout to wait for OTP boot - ASoC: cs35l41: Combine adjacent register writes - ASoC: cs35l41: Don't overwrite returned error code - ASoC: cs35l41: Fixup the error messages - ASoC: cs35l41: Fix a bunch of trivial code formating/style issues - misc: cs35l41: Remove unused pdn variable - ASoC: cs35l41: Make cs35l41_remove() return void - ASoC: cs35l41: Change monitor widgets to siggens - ASoC: cs35l41: DSP Support - ASoC: cs35l41: Set the max SPI speed for the whole device - ASoC: cs35l41: Fix link problem - ASoC: cs35l41: Fix undefined reference to core functions - ASoC: cs35l41: Convert tables to shared source code - ASoC: cs35l41: Move cs35l41_otp_unpack to shared code - ASoC: cs35l41: Move power initializations to reg_sequence - ASoC: cs35l41: Create shared function for errata patches - ASoC: cs35l41: Create shared function for setting channels - ASoC: cs35l41: Create shared function for boost configuration - ASoC: cs35l41: Add cs35l51/53 IDs - ASoC: cs35l41: Remove incorrect comment - ASoC: cs35l41: Correct DSP power down - ASoC: cs35l41: Correct handling of some registers in the cache - ALSA: hda: cs35l41: Add support for CS35L41 in HDA systems - ASoC: cs35l41: Update handling of test key registers - ALSA: hda: cs35l41: fix double free on error in probe() - ALSA: hda: cs35l41: Avoid overwriting register patch - ALSA: hda: cs35l41: Add calls to newly added test key function - ALSA: hda: cs35l41: Move cs35l41* calls to its own symbol namespace - ALSA: hda: cs35l41: Add missing default cases - ALSA: hda: cs35l41: Make use of the helper function dev_err_probe() - ALSA: hda: cs35l41: Tidyup code - ALSA: hda: cs35l41: Make cs35l41_hda_remove() return void - ALSA: hda/realtek: Add support for Legion 7 16ACHg6 laptop - ALSA: hda/realtek: Add CS35L41 support for Thinkpad laptops - ALSA: hda/realtek: fix speakers and micmute on HP 855 G8 - i2c: acpi: Add an i2c_acpi_client_count() helper function - platform/x86: i2c-multi-instantiate: Use the new i2c_acpi_client_count() helper - Revert "platform/x86: i2c-multi-instantiate: Don't create platform device for INT3515 ACPI nodes" - spi: Create helper API to lookup ACPI info for spi device - spi: Support selection of the index of the ACPI Spi Resource before alloc - spi: Add API to count spi acpi resources - platform/x86: i2c-multi-instantiate: Rename it for a generic serial driver name - platform/x86: serial-multi-instantiate: Reorganize I2C functions - platform/x86: serial-multi-instantiate: Add SPI support - ALSA: hda/realtek: Add support for HP Laptops - ACPI / scan: Create platform device for CS35L41 - [Config]: Add cirruslogic side codec support * Revert drm/amd/pm: enable ASPM by default (LP: #1966680) - SAUCE: Revert "drm/amd/pm: enable ASPM by default" * Enable the mic-mute led on Dell XPS 9315 (LP: #1965846) - SAUCE: ASoC: rt715:add micmute led control for Dell XPS 9315 * e1000e reports hardware hang (LP: #1966835) - e1000e: Fix possible HW unit hang after an s0ix exit * Miscellaneous upstream changes - ASoC: cs35l41: Add support for hibernate memory retention mode -- Timo Aaltonen Thu, 31 Mar 2022 15:38:08 +0300 ** Changed in: linux-oem-5.14 (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1965496 Title: alsa: enable the cirrus-logic side-codec to make the speaker output sound Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Jammy: In Progress Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: [Impact] We have a couple of lenovo latops models which have cirrus-logic side codec between realtek codec
[Kernel-packages] [Bug 1965846] Re: Enable the mic-mute led on Dell XPS 9315
This bug was fixed in the package linux-oem-5.14 - 5.14.0-1032.35 --- linux-oem-5.14 (5.14.0-1032.35) focal; urgency=medium * focal/linux-oem-5.14: 5.14.0-1032.35 -proposed tracker (LP: #1967284) * IPU6 camera has no function on Andrews MLK (LP: #1964983) - SAUCE: IPU6: 2022-03-11 alpha release for Andrews MLK - [Config] IPU6: enable OV02C10 sensor * Fix audio on Zbook Studio G9 (LP: #1966010) - gpiolib: acpi: Convert ACPI value of debounce to microseconds - ALSA: hda/realtek: Fix LED on Zbook Studio G9 * alsa: enable the cirrus-logic side-codec to make the speaker output sound (LP: #1965496) - ASoC: cs35l41: CS35L41 Boosted Smart Amplifier - ASoC: cs35l41: Fix use of an uninitialised variable - ASoC: cs35l41: Use regmap_read_poll_timeout to wait for OTP boot - ASoC: cs35l41: Combine adjacent register writes - ASoC: cs35l41: Don't overwrite returned error code - ASoC: cs35l41: Fixup the error messages - ASoC: cs35l41: Fix a bunch of trivial code formating/style issues - misc: cs35l41: Remove unused pdn variable - ASoC: cs35l41: Make cs35l41_remove() return void - ASoC: cs35l41: Change monitor widgets to siggens - ASoC: cs35l41: DSP Support - ASoC: cs35l41: Set the max SPI speed for the whole device - ASoC: cs35l41: Fix link problem - ASoC: cs35l41: Fix undefined reference to core functions - ASoC: cs35l41: Convert tables to shared source code - ASoC: cs35l41: Move cs35l41_otp_unpack to shared code - ASoC: cs35l41: Move power initializations to reg_sequence - ASoC: cs35l41: Create shared function for errata patches - ASoC: cs35l41: Create shared function for setting channels - ASoC: cs35l41: Create shared function for boost configuration - ASoC: cs35l41: Add cs35l51/53 IDs - ASoC: cs35l41: Remove incorrect comment - ASoC: cs35l41: Correct DSP power down - ASoC: cs35l41: Correct handling of some registers in the cache - ALSA: hda: cs35l41: Add support for CS35L41 in HDA systems - ASoC: cs35l41: Update handling of test key registers - ALSA: hda: cs35l41: fix double free on error in probe() - ALSA: hda: cs35l41: Avoid overwriting register patch - ALSA: hda: cs35l41: Add calls to newly added test key function - ALSA: hda: cs35l41: Move cs35l41* calls to its own symbol namespace - ALSA: hda: cs35l41: Add missing default cases - ALSA: hda: cs35l41: Make use of the helper function dev_err_probe() - ALSA: hda: cs35l41: Tidyup code - ALSA: hda: cs35l41: Make cs35l41_hda_remove() return void - ALSA: hda/realtek: Add support for Legion 7 16ACHg6 laptop - ALSA: hda/realtek: Add CS35L41 support for Thinkpad laptops - ALSA: hda/realtek: fix speakers and micmute on HP 855 G8 - i2c: acpi: Add an i2c_acpi_client_count() helper function - platform/x86: i2c-multi-instantiate: Use the new i2c_acpi_client_count() helper - Revert "platform/x86: i2c-multi-instantiate: Don't create platform device for INT3515 ACPI nodes" - spi: Create helper API to lookup ACPI info for spi device - spi: Support selection of the index of the ACPI Spi Resource before alloc - spi: Add API to count spi acpi resources - platform/x86: i2c-multi-instantiate: Rename it for a generic serial driver name - platform/x86: serial-multi-instantiate: Reorganize I2C functions - platform/x86: serial-multi-instantiate: Add SPI support - ALSA: hda/realtek: Add support for HP Laptops - ACPI / scan: Create platform device for CS35L41 - [Config]: Add cirruslogic side codec support * Revert drm/amd/pm: enable ASPM by default (LP: #1966680) - SAUCE: Revert "drm/amd/pm: enable ASPM by default" * Enable the mic-mute led on Dell XPS 9315 (LP: #1965846) - SAUCE: ASoC: rt715:add micmute led control for Dell XPS 9315 * e1000e reports hardware hang (LP: #1966835) - e1000e: Fix possible HW unit hang after an s0ix exit * Miscellaneous upstream changes - ASoC: cs35l41: Add support for hibernate memory retention mode -- Timo Aaltonen Thu, 31 Mar 2022 15:38:08 +0300 ** Changed in: linux-oem-5.14 (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1965846 Title: Enable the mic-mute led on Dell XPS 9315 Status in HWE Next: New Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.14 source package in Focal: Fix Released Bug description: [Impact] On Dell's XPS 9315, the MIC-Mute function is working but the LED(on F4) state is not changed accordingly. [Fix] Dell's mic mute support in privacy mode has been upstream, but the the mic-mute led support is still SAUCE patch which is maintained with DMI based quirk. Add a new SKU for XPS 9315 until Dell's official fix for the mic-mute led.
[Kernel-packages] [Bug 1966010] Re: Fix audio on Zbook Studio G9
This bug was fixed in the package linux-oem-5.14 - 5.14.0-1032.35 --- linux-oem-5.14 (5.14.0-1032.35) focal; urgency=medium * focal/linux-oem-5.14: 5.14.0-1032.35 -proposed tracker (LP: #1967284) * IPU6 camera has no function on Andrews MLK (LP: #1964983) - SAUCE: IPU6: 2022-03-11 alpha release for Andrews MLK - [Config] IPU6: enable OV02C10 sensor * Fix audio on Zbook Studio G9 (LP: #1966010) - gpiolib: acpi: Convert ACPI value of debounce to microseconds - ALSA: hda/realtek: Fix LED on Zbook Studio G9 * alsa: enable the cirrus-logic side-codec to make the speaker output sound (LP: #1965496) - ASoC: cs35l41: CS35L41 Boosted Smart Amplifier - ASoC: cs35l41: Fix use of an uninitialised variable - ASoC: cs35l41: Use regmap_read_poll_timeout to wait for OTP boot - ASoC: cs35l41: Combine adjacent register writes - ASoC: cs35l41: Don't overwrite returned error code - ASoC: cs35l41: Fixup the error messages - ASoC: cs35l41: Fix a bunch of trivial code formating/style issues - misc: cs35l41: Remove unused pdn variable - ASoC: cs35l41: Make cs35l41_remove() return void - ASoC: cs35l41: Change monitor widgets to siggens - ASoC: cs35l41: DSP Support - ASoC: cs35l41: Set the max SPI speed for the whole device - ASoC: cs35l41: Fix link problem - ASoC: cs35l41: Fix undefined reference to core functions - ASoC: cs35l41: Convert tables to shared source code - ASoC: cs35l41: Move cs35l41_otp_unpack to shared code - ASoC: cs35l41: Move power initializations to reg_sequence - ASoC: cs35l41: Create shared function for errata patches - ASoC: cs35l41: Create shared function for setting channels - ASoC: cs35l41: Create shared function for boost configuration - ASoC: cs35l41: Add cs35l51/53 IDs - ASoC: cs35l41: Remove incorrect comment - ASoC: cs35l41: Correct DSP power down - ASoC: cs35l41: Correct handling of some registers in the cache - ALSA: hda: cs35l41: Add support for CS35L41 in HDA systems - ASoC: cs35l41: Update handling of test key registers - ALSA: hda: cs35l41: fix double free on error in probe() - ALSA: hda: cs35l41: Avoid overwriting register patch - ALSA: hda: cs35l41: Add calls to newly added test key function - ALSA: hda: cs35l41: Move cs35l41* calls to its own symbol namespace - ALSA: hda: cs35l41: Add missing default cases - ALSA: hda: cs35l41: Make use of the helper function dev_err_probe() - ALSA: hda: cs35l41: Tidyup code - ALSA: hda: cs35l41: Make cs35l41_hda_remove() return void - ALSA: hda/realtek: Add support for Legion 7 16ACHg6 laptop - ALSA: hda/realtek: Add CS35L41 support for Thinkpad laptops - ALSA: hda/realtek: fix speakers and micmute on HP 855 G8 - i2c: acpi: Add an i2c_acpi_client_count() helper function - platform/x86: i2c-multi-instantiate: Use the new i2c_acpi_client_count() helper - Revert "platform/x86: i2c-multi-instantiate: Don't create platform device for INT3515 ACPI nodes" - spi: Create helper API to lookup ACPI info for spi device - spi: Support selection of the index of the ACPI Spi Resource before alloc - spi: Add API to count spi acpi resources - platform/x86: i2c-multi-instantiate: Rename it for a generic serial driver name - platform/x86: serial-multi-instantiate: Reorganize I2C functions - platform/x86: serial-multi-instantiate: Add SPI support - ALSA: hda/realtek: Add support for HP Laptops - ACPI / scan: Create platform device for CS35L41 - [Config]: Add cirruslogic side codec support * Revert drm/amd/pm: enable ASPM by default (LP: #1966680) - SAUCE: Revert "drm/amd/pm: enable ASPM by default" * Enable the mic-mute led on Dell XPS 9315 (LP: #1965846) - SAUCE: ASoC: rt715:add micmute led control for Dell XPS 9315 * e1000e reports hardware hang (LP: #1966835) - e1000e: Fix possible HW unit hang after an s0ix exit * Miscellaneous upstream changes - ASoC: cs35l41: Add support for hibernate memory retention mode -- Timo Aaltonen Thu, 31 Mar 2022 15:38:08 +0300 ** Changed in: linux-oem-5.14 (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1966010 Title: Fix audio on Zbook Studio G9 Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Jammy: Confirmed Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: [Impact] Cirrus Logic AMP still doesn't work on Zbook Studio G9. Moreoever, The audio mute LEDs stop working after the said SRU. [Fix] Correcly interpret
[Kernel-packages] [Bug 1966835] Re: e1000e reports hardware hang
This bug was fixed in the package linux-oem-5.14 - 5.14.0-1032.35 --- linux-oem-5.14 (5.14.0-1032.35) focal; urgency=medium * focal/linux-oem-5.14: 5.14.0-1032.35 -proposed tracker (LP: #1967284) * IPU6 camera has no function on Andrews MLK (LP: #1964983) - SAUCE: IPU6: 2022-03-11 alpha release for Andrews MLK - [Config] IPU6: enable OV02C10 sensor * Fix audio on Zbook Studio G9 (LP: #1966010) - gpiolib: acpi: Convert ACPI value of debounce to microseconds - ALSA: hda/realtek: Fix LED on Zbook Studio G9 * alsa: enable the cirrus-logic side-codec to make the speaker output sound (LP: #1965496) - ASoC: cs35l41: CS35L41 Boosted Smart Amplifier - ASoC: cs35l41: Fix use of an uninitialised variable - ASoC: cs35l41: Use regmap_read_poll_timeout to wait for OTP boot - ASoC: cs35l41: Combine adjacent register writes - ASoC: cs35l41: Don't overwrite returned error code - ASoC: cs35l41: Fixup the error messages - ASoC: cs35l41: Fix a bunch of trivial code formating/style issues - misc: cs35l41: Remove unused pdn variable - ASoC: cs35l41: Make cs35l41_remove() return void - ASoC: cs35l41: Change monitor widgets to siggens - ASoC: cs35l41: DSP Support - ASoC: cs35l41: Set the max SPI speed for the whole device - ASoC: cs35l41: Fix link problem - ASoC: cs35l41: Fix undefined reference to core functions - ASoC: cs35l41: Convert tables to shared source code - ASoC: cs35l41: Move cs35l41_otp_unpack to shared code - ASoC: cs35l41: Move power initializations to reg_sequence - ASoC: cs35l41: Create shared function for errata patches - ASoC: cs35l41: Create shared function for setting channels - ASoC: cs35l41: Create shared function for boost configuration - ASoC: cs35l41: Add cs35l51/53 IDs - ASoC: cs35l41: Remove incorrect comment - ASoC: cs35l41: Correct DSP power down - ASoC: cs35l41: Correct handling of some registers in the cache - ALSA: hda: cs35l41: Add support for CS35L41 in HDA systems - ASoC: cs35l41: Update handling of test key registers - ALSA: hda: cs35l41: fix double free on error in probe() - ALSA: hda: cs35l41: Avoid overwriting register patch - ALSA: hda: cs35l41: Add calls to newly added test key function - ALSA: hda: cs35l41: Move cs35l41* calls to its own symbol namespace - ALSA: hda: cs35l41: Add missing default cases - ALSA: hda: cs35l41: Make use of the helper function dev_err_probe() - ALSA: hda: cs35l41: Tidyup code - ALSA: hda: cs35l41: Make cs35l41_hda_remove() return void - ALSA: hda/realtek: Add support for Legion 7 16ACHg6 laptop - ALSA: hda/realtek: Add CS35L41 support for Thinkpad laptops - ALSA: hda/realtek: fix speakers and micmute on HP 855 G8 - i2c: acpi: Add an i2c_acpi_client_count() helper function - platform/x86: i2c-multi-instantiate: Use the new i2c_acpi_client_count() helper - Revert "platform/x86: i2c-multi-instantiate: Don't create platform device for INT3515 ACPI nodes" - spi: Create helper API to lookup ACPI info for spi device - spi: Support selection of the index of the ACPI Spi Resource before alloc - spi: Add API to count spi acpi resources - platform/x86: i2c-multi-instantiate: Rename it for a generic serial driver name - platform/x86: serial-multi-instantiate: Reorganize I2C functions - platform/x86: serial-multi-instantiate: Add SPI support - ALSA: hda/realtek: Add support for HP Laptops - ACPI / scan: Create platform device for CS35L41 - [Config]: Add cirruslogic side codec support * Revert drm/amd/pm: enable ASPM by default (LP: #1966680) - SAUCE: Revert "drm/amd/pm: enable ASPM by default" * Enable the mic-mute led on Dell XPS 9315 (LP: #1965846) - SAUCE: ASoC: rt715:add micmute led control for Dell XPS 9315 * e1000e reports hardware hang (LP: #1966835) - e1000e: Fix possible HW unit hang after an s0ix exit * Miscellaneous upstream changes - ASoC: cs35l41: Add support for hibernate memory retention mode -- Timo Aaltonen Thu, 31 Mar 2022 15:38:08 +0300 ** Changed in: linux-oem-5.14 (Ubuntu Focal) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1966835 Title: e1000e reports hardware hang Status in HWE Next: New Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.14 source package in Focal: Fix Released Bug description: [Impact] Encounter the e1000e h/w hang while doing suspend/resume test kernel: e1000e :00:1f.6 enp0s31f6: Detected Hardware Unit Hang: TDH <4> TDT <9> next_to_use <9> next_to_clean <4>
[Kernel-packages] [Bug 1967562] Re: jammy beta (220330) arm iso kernel panic during pxe boot
Yeah, it's not a MAAS deploy issue, but a subiquity PXE install issue (MAAS deploys this system fine). @Tai this bit looks weird to me: [0.00] Kernel command line: BOOT_IMAGE=/casper/vmlinuz debug root=/dev/ram0 ramdisk_size=150 ip=dhcp url=http://10.229.56.0/jammy-live-server-arm64.iso autoinstall ds=nocloud-net;s=http://10.229.56.0/ --- [0.00] Unknown kernel command line parameters "autoinstall --- BOOT_IMAGE=/casper/vmlinuz ramdisk_size=150 ip=dhcp url=http://10.229.56.0/jammy-live-server-arm64.iso ds=nocloud-net;s=http://10.229.56.0/;, will be passed to user space. Like that there maybe two "---" delimiters. Can you provide the grub.cfg used? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1967562 Title: jammy beta (220330) arm iso kernel panic during pxe boot Status in linux package in Ubuntu: Incomplete Status in subiquity package in Ubuntu: New Bug description: = Description = Platforms: Ampere Mt. Jade Altra (bizzy), Cavium thunderX crb2s (recht) Image: Jammy Beta (220330) I setup my pxe server to provision jammy beta and got the following kernel panic message after grub stage: log from console log [1.176614] integrity: Couldn't parse dbx signatures: -74^M [1.371630] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)^M [1.379891] CPU: 42 PID: 1 Comm: swapper/0 Not tainted 5.15.0-23-generic #23-Ubuntu^M [1.387535] Hardware name: WIWYNN Mt.Jade Server System B81.030Z1.0007/Mt.Jade Motherboard, BIOS 1.6.20210526 (SCP: 1.06.20210526) 2021/05/26^M [1.400215] Call trace:^M [1.402649] dump_backtrace+0x0/0x1ec^M [1.406310] show_stack+0x24/0x30^M [1.409614] dump_stack_lvl+0x68/0x84^M [1.413271] dump_stack+0x18/0x34^M [1.416573] panic+0x18c/0x39c^M [1.419616] mount_block_root+0x160/0x210^M [1.423622] mount_root+0x12c/0x14c^M [1.427097] prepare_namespace+0x140/0x1a0^M [1.431182] kernel_init_freeable+0x1c8/0x214^M [1.435527] kernel_init+0x30/0x160^M [1.439006] ret_from_fork+0x10/0x20^M [1.442573] SMP: stopping secondary CPUs^M [1.447323] Kernel Offset: 0x55263ee9 from 0x8800^M [1.453404] PHYS_OFFSET: 0x8000^M [1.456879] CPU features: 0x85c1,a3302e42^M [1.461225] Memory Limit: none^M [1.464271] ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) ]---^M = Steps to Reproduce = 1. Followed this guide to setup the pxe server https://discourse.ubuntu.com/t/netbooting-the-live-server-installer-via-uefi-pxe-on-arm-aarch64-arm64-and-x86-64-amd64/19240 with the jammy beta image (220330) http://cdimage.ubuntu.com/ubuntu-server/daily-live/20220330/jammy-live-server-arm64.iso 1-1. You may use this script to perform the set-up https://github.com/tai271828/ubuntu-autoinstall-pxe-server by invoking: `sudo ./setup-pxe-server.sh --url http://cdimage.ubuntu.com/ubuntu-server/daily-live/20220330/jammy-live-server-arm64.iso` 2. Boot the system via PXE 3. Select Ubuntu at Grub menu = Expected Result = The image is loaded to the system locally via PXE, and subiquity is launched = Actual Result = Console log simply shows nothing for 10 seconds and then the kernel panic shows up. = Additional Information = - If we install via the virtual CD of the server, subiquity could be launched and the installation process completes successfully. - MAAS could deploy Jammy to the Mt. Jade server as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967562/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1967613] Re: Gnome session reset after docking station disconnects
Could you add a 'journalctl -b 0 > log' to the bug after getting the issue? -- 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/1967613 Title: Gnome session reset after docking station disconnects Status in linux package in Ubuntu: Confirmed Bug description: From time to time, GNOME session gets reset when usb-c cable from docking station gets disconnected. All applications gets closed and completely new, fresh GNOME session is created. This is not happening every single time, when the cable gets disconnected but in about 1/3 of cases. As I remember it's happening only when laptop is suspended or have screen locked. When the laptop is working, and screen isn't locked, it's not happening (I could be wrong but this is my observation). The bug is highly unpleasant because it's closing every single app on the computer, and every single process running in the current session. I'm almost sure it was happening for several last kernels, this is not a new issue, I had this problem for a long time (at least for 6 months). Attachment (20211018_210936.jpg) is related to it, it's the info I see on the screen when the bug occurs. Short info: Laptop: Thinkpad E14 Gen2 AMD, Ryzen 5 4500u, Sysytem: Ubuntu 21.10, GNOME 40.4.0, X11, kernel 5.13.0-39-generic, Docking station: Thinkpad USB-C Dock Gen2, 40AS, 20/06, 0090EU Logs: --- CASE 1 --- [Wed Mar 16 17:41:58 2022] sda: detected capacity change from 0 to 62333952 [Wed Mar 16 17:41:58 2022] sda: sda1 [Wed Mar 16 17:44:14 2022] usb 1-1: USB disconnect, device number 23 [Wed Mar 16 17:44:14 2022] usb 1-1.2: USB disconnect, device number 24 [Wed Mar 16 17:44:14 2022] usb 1-1.2.1: USB disconnect, device number 26 [Wed Mar 16 17:44:14 2022] [drm] DM_MST: stopping TM on aconnector: e676af82 [id: 89] [Wed Mar 16 17:44:14 2022] usb 2-1: USB disconnect, device number 14 [Wed Mar 16 17:44:14 2022] usb 2-1.1: USB disconnect, device number 15 [Wed Mar 16 17:44:14 2022] r8152 2-1.1:1.0 enx482ae38dc78a: Tx status -108 [Wed Mar 16 17:44:14 2022] kauditd_printk_skb: 10 callbacks suppressed [Wed Mar 16 17:44:14 2022] audit: type=1326 audit(1647449054.614:415): auid=1000 uid=1000 gid=1000 ses=3 subj=snap.snap-store.ubuntu-software pid=6236 comm="pool-org.gnome." exe="/snap/snap-store/558/usr/bin/snap-store" sig=0 arch=c03e syscall=251 compat=0 ip=0x7fbdde51d76d code=0x5 [Wed Mar 16 17:44:14 2022] audit: type=1326 audit(1647449054.614:416): auid=1000 uid=1000 gid=1000 ses=3 subj=snap.snap-store.ubuntu-software pid=6236 comm="pool-org.gnome." exe="/snap/snap-store/558/usr/bin/snap-store" sig=0 arch=c03e syscall=251 compat=0 ip=0x7fbdde51d76d code=0x5 [Wed Mar 16 17:44:14 2022] usb 2-1.2: USB disconnect, device number 16 [Wed Mar 16 17:44:14 2022] usb 2-1.3: USB disconnect, device number 17 [Wed Mar 16 17:44:14 2022] usb 2-1.3.4: USB disconnect, device number 18 [Wed Mar 16 17:44:14 2022] usb 1-1.3: USB disconnect, device number 25 [Wed Mar 16 17:44:14 2022] usb 1-1.3.3: USB disconnect, device number 27 [Wed Mar 16 17:44:14 2022] usb 1-1.3.3.1: USB disconnect, device number 48 [Wed Mar 16 17:44:14 2022] usb 1-1.3.3.2: USB disconnect, device number 29 [Wed Mar 16 17:44:14 2022] usb 1-1.3.3.3: USB disconnect, device number 30 [Wed Mar 16 17:44:14 2022] usb 1-1.3.3.4: USB disconnect, device number 31 [Wed Mar 16 17:44:14 2022] ACPI Error: No handler for Region [ECSI] (89f11df8) [EmbeddedControl] (20210331/evregion-130) [Wed Mar 16 17:44:14 2022] ACPI Error: Region EmbeddedControl (ID=3) has no handler (20210331/exfldio-261) [Wed Mar 16 17:44:14 2022] No Local Variables are initialized for Method [ECRD] [Wed Mar 16 17:44:14 2022] No Arguments are initialized for method [ECRD] [Wed Mar 16 17:44:14 2022] ACPI Error: Aborting method \_SB.UBTC.ECRD due to previous error (AE_NOT_EXIST) (20210331/psparse-529) [Wed Mar 16 17:44:14 2022] ACPI Error: Aborting method \_SB.UBTC.NTFY due to previous error (AE_NOT_EXIST) (20210331/psparse-529) [Wed Mar 16 17:44:14 2022] ACPI Error: Aborting method \_SB.PCI0.LPC0.EC0._Q4F due to previous error (AE_NOT_EXIST) (20210331/psparse-529) [Wed Mar 16 17:44:15 2022] audit: type=1326 audit(1647449056.306:417): auid=1000 uid=1000 gid=1000 ses=3 subj=snap.snap-store.ubuntu-software pid=6236 comm="pool-org.gnome." exe="/snap/snap-store/558/usr/bin/snap-store" sig=0 arch=c03e syscall=251 compat=0 ip=0x7fbdde51d76d code=0x5 [Wed Mar 16 17:44:15 2022] audit: type=1326 audit(1647449056.306:418): auid=1000 uid=1000 gid=1000 ses=3 subj=snap.snap-store.ubuntu-software pid=6236 comm="pool-org.gnome." exe="/snap/snap-store/558/usr/bin/snap-store" sig=0 arch=c03e syscall=251 compat=0 ip=0x7fbdde51d76d code=0x5 [Wed Mar 16 17:44:17 2022] rfkill:
[Kernel-packages] [Bug 1966969] Re: linux-aws: Xen: Issues with detaching volume
Amazon tested ** Tags removed: verification-needed-impish ** Tags added: verification-done-impish -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1966969 Title: linux-aws: Xen: Issues with detaching volume Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Impish: In Progress Bug description: SRU Justification [Impact] We are observing issue with the secondary volume stuck in detaching. This is observed with the latest Canonical, Ubuntu EKS Node OS (k8s_1.19), 20.04 LTS, amd64 focal image build on 2022-03-08 and Xen instance type( for eg : m4, t2 instance type ) AMI in eu-west-1 : ami-0f4ffbcba23a6c434 AMI in us-east-1 : ami-021feb4aa3b3c59c3 When terminating an instance with a stuck volume the shutdown process is interrupted by a xen task hanging: [ 847.895334] INFO: task xenwatch:188 blocked for more than 483 seconds. [ 847.901573] Not tainted 5.13.0-1017-aws #19~20.04.1-Ubuntu [ 847.907144] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 847.914462] task:xenwatch state:D stack: 0 pid: 188 ppid: 2 flags:0x4000 [ 847.914467] Call Trace: [ 847.914469] [ 847.914472] __schedule+0x2ee/0x900 [ 847.914478] schedule+0x4f/0xc0 [ 847.914479] schedule_preempt_disabled+0xe/0x10 [ 847.914482] __mutex_lock.isra.0+0x183/0x4d0 [ 847.914486] __mutex_lock_slowpath+0x13/0x20 [ 847.914487] mutex_lock+0x32/0x40 [ 847.914489] del_gendisk+0x90/0x200 [ 847.914493] xlvbd_release_gendisk+0x72/0xc0 [ 847.914499] blkback_changed+0x101/0x210 [ 847.914502] xenbus_otherend_changed+0x8f/0x130 [ 847.914507] backend_changed+0x13/0x20 [ 847.914510] xenwatch_thread+0xa6/0x180 [ 847.914513] ? wait_woken+0x80/0x80 [ 847.914517] ? test_reply.isra.0+0x40/0x40 [ 847.914520] kthread+0x12b/0x150 [ 847.914523] ? set_kthread_struct+0x40/0x40 [ 847.914525] ret_from_fork+0x22/0x30 [ 847.914531] this looks like it's waiting on a xen block device to be released. Following steps used to reproduce the issue: * Created a m4,t2(xen) instance with the latest ami for latest Canonical, Ubuntu EKS Node OS (k8s_1.19), 20.04 LTS, amd64 * Created a filesystem on volume * Mounted volume through OS * Unmounted volume in OS * Detached volume from AWS console * Volume gets stuck. We at the internal team observed this commit upstream: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=05d69d950d9d84218fc9beafd02dea1f6a70e09e [...] and a del_gendisk from the block device release method, which will deadlock. It has a Fixes: tag referring to a commit from 5.13 so this could be the root-cause. While testing, we observed this commit is fixing the issue. [Test Plan] Amazon tested [Where things could go wrong] Detaching volumes could fail in new and bizarre ways [Other Info] SF: #00331175 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1966969/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1967613] Re: Gnome session reset after docking station disconnects
Another case, but this time positive: laptop was suspended, docking station has been disconnected, and after waking up (which took some time, about 8s) everything was fine. But, yesterday I've installed "displaylink-driver-5.5.0-59.151.run" and I don't know if this changed the situation or nor. I don't have another "positive case" logs prior to installation of displaylink-driver. POSITIVE CASE: [Mon Apr 4 13:26:55 2022] amdgpu :05:00.0: amdgpu: ring jpeg_dec uses VM inv eng 6 on hub 1 [Mon Apr 4 13:26:57 2022] usb usb2-port1: Cannot enable. Maybe the USB cable is bad? [Mon Apr 4 13:27:01 2022] usb usb2-port1: Cannot enable. Maybe the USB cable is bad? [Mon Apr 4 13:27:03 2022] psmouse serio1: Touchpad at isa0060/serio1/input0 lost sync at byte 6 [Mon Apr 4 13:27:03 2022] psmouse serio1: Touchpad at isa0060/serio1/input0 lost synchronization, throwing 3 bytes away. [Mon Apr 4 13:27:04 2022] psmouse serio1: resync failed, issuing reconnect request [Mon Apr 4 13:27:05 2022] usb usb2-port1: Cannot enable. Maybe the USB cable is bad? [Mon Apr 4 13:27:09 2022] usb usb2-port1: Cannot enable. Maybe the USB cable is bad? [Mon Apr 4 13:27:09 2022] acpi LNXPOWER:05: Turning OFF [Mon Apr 4 13:27:09 2022] acpi LNXPOWER:03: Turning OFF [Mon Apr 4 13:27:09 2022] acpi LNXPOWER:01: Turning OFF [Mon Apr 4 13:27:09 2022] acpi LNXPOWER:00: Turning OFF [Mon Apr 4 13:27:09 2022] OOM killer enabled. [Mon Apr 4 13:27:09 2022] Restarting tasks ... [Mon Apr 4 13:27:09 2022] pci_bus :01: Allocating resources [Mon Apr 4 13:27:09 2022] pcieport :00:02.1: bridge window [io 0x1000-0x0fff] to [bus 01] add_size 1000 [Mon Apr 4 13:27:09 2022] pcieport :00:02.1: bridge window [mem 0x0010-0x000f 64bit pref] to [bus 01] add_size 20 add_align 10 [Mon Apr 4 13:27:09 2022] pci_bus :02: Allocating resources [Mon Apr 4 13:27:09 2022] pcieport :00:02.2: bridge window [mem 0x0010-0x000f 64bit pref] to [bus 02] add_size 20 add_align 10 [Mon Apr 4 13:27:09 2022] pci_bus :03: Allocating resources [Mon Apr 4 13:27:09 2022] pci_bus :04: Allocating resources [Mon Apr 4 13:27:09 2022] pcieport :00:02.4: bridge window [io 0x1000-0x0fff] to [bus 04] add_size 1000 [Mon Apr 4 13:27:09 2022] pcieport :00:02.4: bridge window [mem 0x0010-0x000f 64bit pref] to [bus 04] add_size 20 add_align 10 [Mon Apr 4 13:27:09 2022] pcieport :00:02.1: BAR 15: assigned [mem 0x63020-0x6303f 64bit pref] [Mon Apr 4 13:27:09 2022] pcieport :00:02.2: BAR 15: assigned [mem 0x63040-0x6305f 64bit pref] [Mon Apr 4 13:27:09 2022] pcieport :00:02.4: BAR 15: assigned [mem 0x63060-0x6307f 64bit pref] [Mon Apr 4 13:27:09 2022] pcieport :00:02.1: BAR 13: assigned [io 0x4000-0x4fff] [Mon Apr 4 13:27:09 2022] pcieport :00:02.4: BAR 13: assigned [io 0x5000-0x5fff] [Mon Apr 4 13:27:09 2022] pci_bus :05: Allocating resources [Mon Apr 4 13:27:09 2022] usb 2-1: USB disconnect, device number 2 [Mon Apr 4 13:27:09 2022] usb 2-1.1: USB disconnect, device number 6 [Mon Apr 4 13:27:09 2022] Bluetooth: hci0: Bootloader revision 0.3 build 0 week 24 2017 [Mon Apr 4 13:27:09 2022] Bluetooth: hci0: Device revision is 1 [Mon Apr 4 13:27:09 2022] Bluetooth: hci0: Secure boot is enabled [Mon Apr 4 13:27:09 2022] Bluetooth: hci0: OTP lock is enabled [Mon Apr 4 13:27:09 2022] Bluetooth: hci0: API lock is enabled [Mon Apr 4 13:27:09 2022] Bluetooth: hci0: Debug lock is disabled [Mon Apr 4 13:27:09 2022] Bluetooth: hci0: Minimum firmware build 1 week 10 2014 [Mon Apr 4 13:27:09 2022] Bluetooth: hci0: Found device firmware: intel/ibt-20-1-3.sfi [Mon Apr 4 13:27:09 2022] usb 1-1: USB disconnect, device number 2 [Mon Apr 4 13:27:09 2022] usb 1-1.2: USB disconnect, device number 4 [Mon Apr 4 13:27:09 2022] usb 1-1.2.2: USB disconnect, device number 6 [Mon Apr 4 13:27:09 2022] done. [Mon Apr 4 13:27:09 2022] thermal thermal_zone0: failed to read out thermal zone (-61) [Mon Apr 4 13:27:09 2022] PM: suspend exit [Mon Apr 4 13:27:09 2022] usb 1-1.3: USB disconnect, device number 5 [Mon Apr 4 13:27:09 2022] usb 1-1.3.3: USB disconnect, device number 7 [Mon Apr 4 13:27:09 2022] usb 1-1.3.3.1: USB disconnect, device number 12 [Mon Apr 4 13:27:09 2022] usb 1-1.3.3.2: USB disconnect, device number 9 [Mon Apr 4 13:27:09 2022] usb 2-1.2: USB disconnect, device number 3 [Mon Apr 4 13:27:09 2022] usb 2-1.2.3: USB disconnect, device number 5 [Mon Apr 4 13:27:09 2022] sda: detected capacity change from 62333952 to 0 [Mon Apr 4 13:27:09 2022] usb 1-1.3.3.3: USB disconnect, device number 10 [Mon Apr 4 13:27:10 2022] usb 2-1.3: USB disconnect, device number 4 [Mon Apr 4 13:27:10 2022] usb 1-1.3.3.4: USB disconnect, device number 11 [Mon Apr 4 13:27:10 2022] Generic FE-GE Realtek PHY r8169-0-200:00: attached PHY driver (mii_bus:phy_addr=r8169-0-200:00, irq=MAC) [Mon Apr 4 13:27:10 2022] r8169 :02:00.0 enp2s0:
[Kernel-packages] [Bug 1964796] Re: Fix unmatched ASMedia ASM2824 PCIe link training
Queued for stable trees https://lore.kernel.org/stable/ykgzn+ugt...@kroah.com/ ** Changed in: linux-riscv (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-riscv in Ubuntu. https://bugs.launchpad.net/bugs/1964796 Title: Fix unmatched ASMedia ASM2824 PCIe link training Status in linux-riscv package in Ubuntu: Fix Committed Bug description: https://lore.kernel.org/all/alpine.deb.2.21.2202010240190.58...@angie.orcam.me.uk/raw It has been discovered that Unmatched board ships ASMedia ASM2824 PCIe which frequently fails to complete link training and negotiate stable and fast speeds. To ensure PCIe devices on Unmatched board can operate with stable and predictable link speeds cherry-pick upstream submitted patch that resolves the issue. It is currently applied as a SAUCE patch, whilst the upstream inclusion review is ongoing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/1964796/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1967593] Re: kernel modules going missing after reboot
** Also affects: ubuntu-meta (Ubuntu) Importance: Undecided Status: New ** Changed in: ubuntu-meta (Ubuntu) Importance: Undecided => Critical ** Changed in: ubuntu-meta (Ubuntu) Milestone: None => ubuntu-22.04 ** Tags added: rls-ff-incoming ** Tags removed: rls-ff-incoming ** Tags added: rls-jj-incoming -- 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/1967593 Title: kernel modules going missing after reboot Status in cloud-initramfs-tools package in Ubuntu: Confirmed Status in linux-kvm package in Ubuntu: New Status in linux-lowlatency package in Ubuntu: New Status in ubuntu-meta package in Ubuntu: New Bug description: EDIT: There are no accurate results in the package search, but it is for the kernel shown below Linux 5.15.0-23-generic x86_64. Also for the low latency kernel and other versions 5.4, 5.13, 5.14, 5.17. So it is not kernel specific. It must be a problem with configuration, but reinstalling doesnt fix it. EDIT2: it turns out this is caused by the cloud-initramfs-copymods package mounting over modules locations. Removed it and reinstalled kernel modules package (extras didnt seem necessary, but probably prudent too). This affects several different kernels I've tried in 22.04. This post basically sums it up: https://unix.stackexchange.com/questions/405146/removed-lib-modules-folder-after-every-reboot detailed answer: https://unix.stackexchange.com/a/499580/346155 And this one from upgrading from 20.04 to 22.04: https://askubuntu.com/questions/1400470/kernel-module-not-getting-installed-after-upgrade Basically, for some reason the kernel modules are being mounted over after reboot. My image was built on top of a cloud-init image, but removing the recommeded package "cloud-initramfs-copymods" that mounts over modules didnt work for me. Adding the snd_hda_intel module to the boot config /etc/initramfs-tools/modules did fix my issue for this module. But how many others will not be available? --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 2189 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 IwConfig: lono wireless extensions. enp1s0no wireless extensions. virbr0no wireless extensions. Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 480M MachineType: QEMU Standard PC (Q35 + ICH9, 2009) Package: linux (not installed) ProcFB: 0 virtio_gpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic root=UUID=5d51cbd2-a1de-48f6-b8b6-00709c787fa0 ro ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 RelatedPackageVersions: linux-restricted-modules-5.15.0-23-generic N/A linux-backports-modules-5.15.0-23-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 RfKill: Tags: jammy uec-images Uname: Linux 5.15.0-23-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-01 (1 days ago) UserGroups: libvirt sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 04/01/2014 dmi.bios.release: 0.0 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.13.0-1ubuntu1.1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-4.2 dmi.modalias: dmi:bvnSeaBIOS:bvr1.13.0-1ubuntu1.1:bd04/01/2014:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-4.2:cvnQEMU:ct1:cvrpc-q35-4.2:sku: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-4.2 dmi.sys.vendor: QEMU --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 2189 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 IwConfig: lono wireless extensions. enp1s0no wireless extensions. virbr0no wireless extensions. Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001
[Kernel-packages] [Bug 1967707] Re: Nvidia Wayland sessions sometimes flood the log with [clutter_frame_clock_notify_presented: code should not be reached]
It appears the main cause of this is presently bug 1959888 when you log in with a secondary monitor on a secondary (Nvidia) GPU. So the log messages stop once you have that fix. Although I would still like to understand it better because that's the second bug I've seen trigger the same messages. ** Changed in: mutter (Ubuntu) Importance: Undecided => Medium ** Changed in: mutter (Ubuntu) Status: New => In Progress ** No longer affects: nvidia-graphics-drivers-510 (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-510 in Ubuntu. https://bugs.launchpad.net/bugs/1967707 Title: Nvidia Wayland sessions sometimes flood the log with [clutter_frame_clock_notify_presented: code should not be reached] Status in mutter package in Ubuntu: In Progress Bug description: Nvidia Wayland sessions sometimes flood the log with: [ 13.105877] computer gnome-shell[1264]: (../clutter/clutter/clutter-frame-clock.c:332):clutter_frame_clock_notify_presented: code should not be reached [ 13.106163] computer gnome-shell[1264]: (../clutter/clutter/clutter-frame-clock.c:332):clutter_frame_clock_notify_presented: code should not be reached [ 13.112490] computer gnome-shell[1264]: (../clutter/clutter/clutter-frame-clock.c:332):clutter_frame_clock_notify_presented: code should not be reached [ 13.125302] computer gnome-shell[1264]: (../clutter/clutter/clutter-frame-clock.c:332):clutter_frame_clock_notify_presented: code should not be reached [ 13.142242] computer gnome-shell[1264]: (../clutter/clutter/clutter-frame-clock.c:332):clutter_frame_clock_notify_presented: code should not be reached I've been seeing the issue for months although it only seems to happen *after* something has gone wrong in mutter. Not by default. Then when the messages start, restarting gnome-shell won't fix it. You have to reboot the whole machine so it seems like something has latched in the nvidia-drm kernel driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1967707/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1967733] [NEW] jammy/linux-raspi: Update to upstream raspberrypi rpi-5.15.y (2022-04-04)
Public bug reported: Upstream raspberrypi patchset 2022-04-04 Ported from the following raspberrypi branch: rpi-5.15.y from https://github.com/raspberrypi/linux.git configs: Re-enable all GSPCA camera modules drm/vc4: Force trigger of dlist update on margins change (#4970) brcmfmac: Restore ISO3166 and 0 rev as a fallback drm/panel: panel-ilitek9881c: Add prepare_upstream_first flag drm/panel: ilitek-ili9881c: Clean up on mipi_dsi_attach failure ARM: dts: Enable PMU on Cortex-A72 in AArch32 state pinctrl: bcm2835: Only return non-GPIOs to inputs mm,page_alloc,cma: introduce a customisable threshold for allocating pages in cma bcm2835-codec: Return empty buffers to the VPU instead of queueing to vbuf2 overlays/rpi-display: Add support for DRM driver Revert "update rpi-display-overlay.dts pins for 5.10+" audioinjector.net: stereo and zero, use dev_err_probe, report success overlays: Add overlay for MIPI DBI displays configs: Add MIPI DBI display driver drm/tiny: Add MIPI DBI compatible SPI driver drm/mipi-dbi: Add driver_private member to struct mipi_dbi_dev drm/modes: Add of_get_drm_panel_display_mode() dt-bindings: display: add bindings for MIPI DBI compatible SPI panels drivers: staging: bcm2835-isp: Clear LS table handle in the firmware vc4/drm:plane: Make use of chroma siting parameter drm: Add chroma siting properties vc4/drm: Handle fractional coordinates using the phase field vc4/drm: vc4_plane: Keep fractional source coords inside state Revert "usb: xhci: expand the scope of XHCI_VLI_SS_BULK_OUT_BUG" drm/vc4: hdmi: Add CSC for BT601/709/2020 limited and full range output dtoverlays: Connect the backlight to the pitft35 display overlays: iqs550: Enable interrupt pull-down overlays: Fix cam*_reg_gpio parameter on CM1 CM3 cam1_reg and cam1_reg_gpio fix drm/vc4: Support zpos on all planes drm/object: Add default color encoding and range value at reset drm/object: Add default zpos value at reset drm/object: Add drm_object_property_get_default_value() function media: i2c: Rename ad5398 to ad5398_vcm dtoverlay: Add VCM option to ov5647 overlay dtoverlays: Add VCM option to imx219 defconfigs: Add AD5398 VCM to all Pi defconfigs media: i2c: ov5647: Use v4l2_async_register_subdev_sensor for lens binding media: i2c: Add driver for AD5398 VCM lens driver dt-bindings: media: i2c: Add binding for ad5398 VCM media: v4l2-async: Create links during v4l2_async_match_notify() media: entity: Add support for ancillary links media: entity: Add link_type_name() helper media: media.h: Add new media link type media: entity: Skip non-data links in graph iteration bcm2835-codec: /dev/video31 as interface to image_encode JPEG encoder ** Affects: linux-raspi (Ubuntu) Importance: Undecided Assignee: Juerg Haefliger (juergh) Status: In Progress ** Affects: linux-raspi (Ubuntu Jammy) Importance: Undecided Assignee: Juerg Haefliger (juergh) Status: In Progress ** Changed in: linux-raspi (Ubuntu) Status: New => Confirmed ** Also affects: linux-raspi (Ubuntu Jammy) Importance: Undecided Status: Confirmed ** Description changed: - Upstream raspberrypi patchset 2022-04-04 - Ported from the following raspberrypi branch: - rpi-5.15.y - from https://github.com/raspberrypi/linux.git + Ported from the following raspberrypi branch: + rpi-5.15.y + from https://github.com/raspberrypi/linux.git + + configs: Re-enable all GSPCA camera modules + drm/vc4: Force trigger of dlist update on margins change (#4970) + brcmfmac: Restore ISO3166 and 0 rev as a fallback + drm/panel: panel-ilitek9881c: Add prepare_upstream_first flag + drm/panel: ilitek-ili9881c: Clean up on mipi_dsi_attach failure + ARM: dts: Enable PMU on Cortex-A72 in AArch32 state + pinctrl: bcm2835: Only return non-GPIOs to inputs + mm,page_alloc,cma: introduce a customisable threshold for allocating pages in cma + bcm2835-codec: Return empty buffers to the VPU instead of queueing to vbuf2 + overlays/rpi-display: Add support for DRM driver + Revert "update rpi-display-overlay.dts pins for 5.10+" + audioinjector.net: stereo and zero, use dev_err_probe, report success + overlays: Add overlay for MIPI DBI displays + configs: Add MIPI DBI display driver + drm/tiny: Add MIPI DBI compatible SPI driver + drm/mipi-dbi: Add driver_private member to struct mipi_dbi_dev + drm/modes: Add of_get_drm_panel_display_mode() + dt-bindings: display: add bindings for MIPI DBI compatible SPI panels + drivers: staging: bcm2835-isp: Clear LS table handle in the firmware + vc4/drm:plane: Make use of chroma siting parameter + drm: Add chroma siting properties + vc4/drm: Handle fractional coordinates using the phase field + vc4/drm: vc4_plane: Keep fractional source coords inside state + Revert "usb: xhci: expand the scope of XHCI_VLI_SS_BULK_OUT_BUG" + drm/vc4: hdmi: Add CSC for BT601/709/2020 limited and full range output + dtoverlays: Connect the backlight to the pitft35 display + overlays: iqs550: Enable
[Kernel-packages] [Bug 1967562] Re: jammy beta (220330) arm iso kernel panic during pxe boot
I just deployed Jammy on recht (using MAAS) and it seems fine: ... ubuntu@recht:~$ uname -a Linux recht 5.15.0-23-generic #23-Ubuntu SMP Fri Mar 11 14:57:40 UTC 2022 aarch64 aarch64 aarch64 GNU/Linux ubuntu@recht:~$ lsb_release -d Description:Ubuntu Jammy Jellyfish (development branch) ubuntu@recht:~$ sudo dmesg | grep "Machine model" [0.00] Machine model: cavium,thunder-88xx ... -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1967562 Title: jammy beta (220330) arm iso kernel panic during pxe boot Status in linux package in Ubuntu: Incomplete Status in subiquity package in Ubuntu: New Bug description: = Description = Platforms: Ampere Mt. Jade Altra (bizzy), Cavium thunderX crb2s (recht) Image: Jammy Beta (220330) I setup my pxe server to provision jammy beta and got the following kernel panic message after grub stage: log from console log [1.176614] integrity: Couldn't parse dbx signatures: -74^M [1.371630] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)^M [1.379891] CPU: 42 PID: 1 Comm: swapper/0 Not tainted 5.15.0-23-generic #23-Ubuntu^M [1.387535] Hardware name: WIWYNN Mt.Jade Server System B81.030Z1.0007/Mt.Jade Motherboard, BIOS 1.6.20210526 (SCP: 1.06.20210526) 2021/05/26^M [1.400215] Call trace:^M [1.402649] dump_backtrace+0x0/0x1ec^M [1.406310] show_stack+0x24/0x30^M [1.409614] dump_stack_lvl+0x68/0x84^M [1.413271] dump_stack+0x18/0x34^M [1.416573] panic+0x18c/0x39c^M [1.419616] mount_block_root+0x160/0x210^M [1.423622] mount_root+0x12c/0x14c^M [1.427097] prepare_namespace+0x140/0x1a0^M [1.431182] kernel_init_freeable+0x1c8/0x214^M [1.435527] kernel_init+0x30/0x160^M [1.439006] ret_from_fork+0x10/0x20^M [1.442573] SMP: stopping secondary CPUs^M [1.447323] Kernel Offset: 0x55263ee9 from 0x8800^M [1.453404] PHYS_OFFSET: 0x8000^M [1.456879] CPU features: 0x85c1,a3302e42^M [1.461225] Memory Limit: none^M [1.464271] ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) ]---^M = Steps to Reproduce = 1. Followed this guide to setup the pxe server https://discourse.ubuntu.com/t/netbooting-the-live-server-installer-via-uefi-pxe-on-arm-aarch64-arm64-and-x86-64-amd64/19240 with the jammy beta image (220330) http://cdimage.ubuntu.com/ubuntu-server/daily-live/20220330/jammy-live-server-arm64.iso 1-1. You may use this script to perform the set-up https://github.com/tai271828/ubuntu-autoinstall-pxe-server by invoking: `sudo ./setup-pxe-server.sh --url http://cdimage.ubuntu.com/ubuntu-server/daily-live/20220330/jammy-live-server-arm64.iso` 2. Boot the system via PXE 3. Select Ubuntu at Grub menu = Expected Result = The image is loaded to the system locally via PXE, and subiquity is launched = Actual Result = Console log simply shows nothing for 10 seconds and then the kernel panic shows up. = Additional Information = - If we install via the virtual CD of the server, subiquity could be launched and the installation process completes successfully. - MAAS could deploy Jammy to the Mt. Jade server as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967562/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1965177] Re: Kernel crash when plugging in dock
So you're saying it's a regression due to a kernel upgrade? Do you have older oem kernels still installed to boot with to verify if they still work? The bug seems to be in the ethernet driver (igc). [ 7253.607665] Call Trace: [ 7253.607667] [ 7253.607672] igc_get_hw_semaphore_i225+0x34/0x180 [igc] [ 7253.607684] igc_acquire_swfw_sync_i225+0x5a/0xd0 [igc] [ 7253.607696] igc_acquire_phy_base+0x14/0x20 [igc] [ 7253.607706] igc_read_phy_reg_gpy+0x38/0x1a0 [igc] [ 7253.607718] igc_phy_has_link+0x74/0x170 [igc] [ 7253.607730] igc_check_for_copper_link+0x63/0xe0 [igc] [ 7253.607740] igc_has_link+0x2b/0x80 [igc] [ 7253.607748] igc_watchdog_task+0x3e/0x2a0 [igc] [ 7253.607758] process_one_work+0x21d/0x3c0 [ 7253.607766] worker_thread+0x4d/0x3f0 [ 7253.607770] ? process_one_work+0x3c0/0x3c0 [ 7253.607775] kthread+0x127/0x150 [ 7253.607778] ? set_kthread_struct+0x40/0x40 [ 7253.607782] ret_from_fork+0x1f/0x30 [ 7253.607790] ** Changed in: linux-oem-5.14 (Ubuntu Focal) Status: New => Incomplete ** Changed in: linux-oem-5.14 (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1965177 Title: Kernel crash when plugging in dock Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.14 source package in Focal: Incomplete Bug description: Recently, my laptop started hanging when plugging into the dock. The mouse continues to move but I cannot do anything else. I was able to ssh in and save dmesg which I have attached below. System Information Manufacturer: LENOVO Product Name: 20XW003JUS Version: ThinkPad X1 Carbon Gen 9 Serial Number: PF3JW2P5 UUID: 3685757e-689b-11ec-80f1-88a4c23141b3 Wake-up Type: Power Switch SKU Number: LENOVO_MT_20XW_BU_Think_FM_ThinkPad X1 Carbon Gen 9 Family: ThinkPad X1 Carbon Gen 9 Ubuntu release: Description: Ubuntu 20.04.4 LTS Release: 20.04 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: asamson1682 F pulseaudio /dev/snd/controlC0: asamson1682 F pulseaudio CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2022-02-11 (33 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: LENOVO 20XW003JUS Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-1027-oem root=UUID=e392f02a-309f-4f70-9d04-0cf071b6d357 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.14.0-1027.30-oem 5.14.21 RelatedPackageVersions: linux-restricted-modules-5.14.0-1027-oem N/A linux-backports-modules-5.14.0-1027-oem N/A linux-firmware 1.187.27 Tags: focal Uname: Linux 5.14.0-1027-oem x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: False dmi.bios.date: 12/02/2021 dmi.bios.release: 1.51 dmi.bios.vendor: LENOVO dmi.bios.version: N32ET75W (1.51 ) dmi.board.asset.tag: Not Available dmi.board.name: 20XW003JUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.32 dmi.modalias: dmi:bvnLENOVO:bvrN32ET75W(1.51):bd12/02/2021:br1.51:efr1.32:svnLENOVO:pn20XW003JUS:pvrThinkPadX1CarbonGen9:rvnLENOVO:rn20XW003JUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20XW_BU_Think_FM_ThinkPadX1CarbonGen9: dmi.product.family: ThinkPad X1 Carbon Gen 9 dmi.product.name: 20XW003JUS dmi.product.sku: LENOVO_MT_20XW_BU_Think_FM_ThinkPad X1 Carbon Gen 9 dmi.product.version: ThinkPad X1 Carbon Gen 9 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.14/+bug/1965177/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1965737] Re: Focal update: upstream stable patchset 2022-03-21
** Changed in: linux-oem-5.14 (Ubuntu Focal) Status: Confirmed => Fix Committed ** Changed in: linux-oem-5.14 (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1965737 Title: Focal update: upstream stable patchset 2022-03-21 Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.14 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: upstream stable patchset 2022-03-21 from git://git.kernel.org/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.14/+bug/1965737/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1966497] Re: Fix non-working MT7921 BT after reboot
** Changed in: linux-oem-5.14 (Ubuntu Focal) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1966497 Title: Fix non-working MT7921 BT after reboot Status in HWE Next: New Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.14 source package in Focal: Fix Committed Bug description: [Impact] There's a high chance that MT7921 BT may go out to lunch after reboot. Worse, there's no way to recover the controller unless the power cord is unplugged. [Fix] In addition to SRU "Need to reset MT7921 BT when the firmware hang or command no response", enable MSFT extension can magically solve the issue. [Test] With the patch applied, the MT7921 BT continues to work after 100 times reboots. [Where problems could occur] This fix is specific to MTK BT controllers, so the change is limited. I totally don't understand why this patch can fix the issue, other than it just does the trick. So I guess we have to accept the reality that hardwares can have their own quirks. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1966497/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1966841] Re: alsa/sdw: Fix the audio issue on a Dell machine without internal mic
** Changed in: linux-oem-5.14 (Ubuntu Focal) Status: In Progress => Fix Committed ** Also affects: linux-oem-5.17 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-oem-5.17 (Ubuntu Focal) Status: New => Invalid ** Changed in: linux-oem-5.17 (Ubuntu Jammy) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1966841 Title: alsa/sdw: Fix the audio issue on a Dell machine without internal mic Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Fix Committed Status in linux source package in Focal: Invalid Status in linux-oem-5.14 source package in Focal: Fix Committed Status in linux-oem-5.17 source package in Focal: Invalid Status in linux source package in Jammy: In Progress Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Committed Bug description: [Impact] we have a Dell ADL laptop which has sdw audio, but there is no camera and no internal digital mic in this machine, the current soc driver can't work on this machine, it will load a wrong tplg without this patch, and the speaker and headset couldn't work. [Fix] Backport one patch from upstream. [Test] Boot the patched kernel on the machine, check dmesg, it loads the correct tplg, and test speaker and headset, all work well. [Where problems could occur] If it could introduce regression, it will be on the sdw codec matching for adl machines, then it will make the driver load wrong tplg and make output device and input device not work anymore. But this possibility is very low, we already tested the patch on some dell adl machines, no regression found. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1966841/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1967069] Re: Enable headset mic on Lenovo P360
** Changed in: linux-oem-5.14 (Ubuntu Focal) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1967069 Title: Enable headset mic on Lenovo P360 Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.14 source package in Focal: Fix Committed Status in linux source package in Jammy: Confirmed Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: [Impact] Headset microphone can't be detected when headset is plugged to front panel port. [Fix] Apply Realtek ALC897 quirk to enable headset mic. [Test] Once the fix is applied, the headset mic can be detected and it also works. [Where problems could occur] Audio quirk which applies to only one specific system, so there's no chance to regress existing systems. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1967069/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1967067] Re: WCN6856 BT keep in OFF state after coldboot system
** Changed in: linux-oem-5.17 (Ubuntu Jammy) Status: In Progress => Fix Committed ** Changed in: linux-oem-5.14 (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1967067 Title: WCN6856 BT keep in OFF state after coldboot system Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Fix Committed Status in linux source package in Focal: Invalid Status in linux-oem-5.14 source package in Focal: Fix Committed Status in linux-oem-5.17 source package in Focal: Invalid Status in linux source package in Jammy: In Progress Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Committed Bug description: [SRU Justification] [Impact] WCN6856 BT keep in OFF state after coldboot system. [Fix] Mainline commit 599ece4f8f07 ("Bluetooth: btusb: Improve stability for QCA devices") added a 100ms delay for the underlying hw to apply downloaded firmware. [Test Case] This can be reproduced and therefore verified by checkbox poweroff stress test: $ checkbox-cli run com.canonical.certification::stress/poweroff [Where problems could occur] Unlikely to have side effect so far except slowing down boot process for a tiny moment. [Other Info] While this is only in the v5.18 merge window, all the kernels in use are affected and nominated here. == original bug report == [Reproduce Steps] 1.Insert WCN6856 card to SUT. 2.Press power button to power on SUT. 3.Clean install Ubuntu 20.04. 4.Check BT function after installation is complete. 5.Coldboot system and check the BT function. 6.Repeat step5, Issue occur. 7.Only found with CB, can't reproduce on WB. [Results] Expected Result BT function work normally. Actual Result BT has no function. Can't turn ON BT function. Need CB to recover BT function. "WB" and "swicth tab" cannot restore the BT function. [Others] Wifi function work normally. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1967067/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1967727] 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/1967727 Title: Random screen blanks with "CPU pipe B FIFO underrun" error Status in linux package in Ubuntu: Confirmed Bug description: On a clean 22.04 install, the screen randomly blanks once in a while for a couple of seconds, then comes back. I see the following message in dmesg when it happens: [ 6614.338572] i915 :00:02.0: [drm] *ERROR* CPU pipe B FIFO underrun ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-23-generic 5.15.0-23.23 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME Date: Mon Apr 4 10:16:27 2022 InstallationDate: Installed on 2022-04-03 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) MachineType: LENOVO 20F6CTO1WW ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-23-generic root=/dev/mapper/ubuntu-root ro rootflags=subvol=@ quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-23-generic N/A linux-backports-modules-5.15.0-23-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/08/2019 dmi.bios.release: 1.44 dmi.bios.vendor: LENOVO dmi.bios.version: R02ET71W (1.44 ) dmi.board.asset.tag: Not Available dmi.board.name: 20F6CTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.12 dmi.modalias: dmi:bvnLENOVO:bvrR02ET71W(1.44):bd05/08/2019:br1.44:efr1.12:svnLENOVO:pn20F6CTO1WW:pvrThinkPadX260:rvnLENOVO:rn20F6CTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20F6_BU_Think_FM_ThinkPadX260: dmi.product.family: ThinkPad X260 dmi.product.name: 20F6CTO1WW dmi.product.sku: LENOVO_MT_20F6_BU_Think_FM_ThinkPad X260 dmi.product.version: ThinkPad X260 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967727/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1902464] Re: The rear panel of Lenovo P620 doesn't support more than one audio device at the same time
This bug was fixed in the package alsa-ucm-conf - 1.2.2-1ubuntu0.13 --- alsa-ucm-conf (1.2.2-1ubuntu0.13) focal; urgency=medium * d/p/0035-Revert-PATCH-ucm2-USB-Audio-Add-more-support-to-Leno.patch d/p/0036-Revert-PATCH-Add-support-for-Lenovo-ThinkStation-P62.patch d/p/0037-Add-support-for-Lenovo-ThinkStation-P620-Main-Audio.patch d/p/0038-ucm2-USB-Audio-Add-support-for-Lenovo-ThinkStation-P.patch d/p/0039-ucm2-USB-Audio-Add-CaptureMixerElem-for-Lenovo-Think.patch Replace Lenovo P620 UCM files with upstream version to make port selection in PulseAudio work properly. (LP: #1902464) -- Kai-Heng Feng Tue, 22 Mar 2022 20:43:51 +0800 ** Changed in: alsa-ucm-conf (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/1902464 Title: The rear panel of Lenovo P620 doesn't support more than one audio device at the same time Status in HWE Next: New Status in OEM Priority Project: Confirmed Status in alsa-ucm-conf package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: Fix Released Status in alsa-ucm-conf source package in Focal: Fix Released Status in pulseaudio source package in Focal: Fix Released Bug description: == SRU Justification == [Impact] On P620, only single port can work on rear panel. For example, when the Line-Out is plugged, the Mic won't work anymore. [Fix] Use upstream version of UCM to handle port priority correctly, instead of separate ports into different profiles. [Test] Once the UCM is in place, all three ports of rear panel work correctly. [Where problems could occur] UCM is not a static thing - it's actually interpreted differently at higher level. So any change in userspace daemons other than PulseAudio may not like the change and can interpret the UCM in another way. == Original Bug Report == After backporting following patches from PA and alsa-ucm-conf and then it works. https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/290 https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/354 https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/355 https://github.com/alsa-project/alsa-ucm-conf/tree/master/ucm2/USB- Audio [landed by aa74f4c12eefcc98582572d2fc48982cf7478b51] Here is the test PPA: https://launchpad.net/~os369510/+archive/ubuntu/oem-package-test Since the upstream not yet accepted those patches, the regression potential may quite high. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1902464/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1962349] Re: Bolt doesn't work with native USB4 hosts
This bug was fixed in the package bolt - 0.9.1-2~ubuntu20.04.1 --- bolt (0.9.1-2~ubuntu20.04.1) focal; urgency=medium * SRU into Ubuntu 20.04. - Add support for integrated USB4 controllers (LP: #1962349) -- Mario Limonciello Fri, 25 Feb 2022 16:20:33 -0600 ** Changed in: bolt (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1962349 Title: Bolt doesn't work with native USB4 hosts Status in OEM Priority Project: New Status in bolt package in Ubuntu: Fix Released Status in linux package in Ubuntu: In Progress Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: In Progress Status in bolt source package in Focal: Fix Released Status in linux source package in Focal: Won't Fix Status in linux-oem-5.14 source package in Focal: In Progress Status in linux-oem-5.17 source package in Focal: Invalid Status in bolt source package in Impish: Fix Released Status in linux source package in Impish: Won't Fix Status in linux-oem-5.14 source package in Impish: Invalid Status in linux-oem-5.17 source package in Impish: Invalid Status in bolt source package in Jammy: Fix Released Status in linux source package in Jammy: In Progress Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: In Progress Bug description: [Impact] * AMD Yellow Carp provides integrated USB4 host controllers * When plugging in a Thunderbolt3 or USB4 device, users are unable to authorize it using the GUI due to an error message: "parent not authorized, deferring" [Test Plan] AMD Yellow Carp Host (issue this bug is about) -- * Plug in USB4 device or TBT3 to AMD Yellow Carp host * Ensure that PCI topology has populated * Observe that /sys/bus/thunderbolt/devices/DEVICE/authorized is "0" * Try to run `boltctl enroll $UUID` Alpine Ridge / Titan Ridge host (discrete controller) -- Start out on a host with discrete controller (Alpine Ridge or Titan Ridge) 1. sudo boltctl forget -a 2. Plug in dock 3. Make sure 'boltctl list' enumerates dock. 4. Check /sys/bus/thunderbolt/devices/domain0/iommu_dma_protection (value dependent upon host) - If 0; try to manually enroll using 'boltctl enroll $UUID' - If 1; ensure that device automatically enrolled with bolt. GUI Check - Ensure that devices show up in the Settings GUI and are now able to authorize. Note: for AMD platforms enumerating PCIe devices is a separate problem from BOLT handled by kernel tasks. GUI check is only about "authorization". [Where problems could occur] * Intel USB4 or TBT3 hosts also use bolt. They could have a problem with the new version of bolt. * This is very unlikely however since there is a through test suite, and up until now the entire industry has been using bolt on Intel controllers for a long time. * There haven't been any significant bugs reported upstream or in Ubuntu since 0.9.1 release. [Other Info] * This bug also occurs on Intel controllers from ICL, TGL or ALD, but in many cases they are automatically authorized to an iommu DMA policy. * It is fixed in bolt 0.9.1 or later release. * To solve the SRU, will backport 0.9.1 release from Impish. * I did look into backporting just the commit(s) for fixing this, but it's not a trivial backport. Quoting the changelog (https://gitlab.freedesktop.org/bolt/bolt/-/blob/master/CHANGELOG.md): "Additionally the unique_id of said host controller changes with every boot, which breaks one of the fundamental assumptions in boltd". To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1962349/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1967727] [NEW] Random screen blanks with "CPU pipe B FIFO underrun" error
Public bug reported: On a clean 22.04 install, the screen randomly blanks once in a while for a couple of seconds, then comes back. I see the following message in dmesg when it happens: [ 6614.338572] i915 :00:02.0: [drm] *ERROR* CPU pipe B FIFO underrun ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-23-generic 5.15.0-23.23 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME Date: Mon Apr 4 10:16:27 2022 InstallationDate: Installed on 2022-04-03 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) MachineType: LENOVO 20F6CTO1WW ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-23-generic root=/dev/mapper/ubuntu-root ro rootflags=subvol=@ quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-23-generic N/A linux-backports-modules-5.15.0-23-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/08/2019 dmi.bios.release: 1.44 dmi.bios.vendor: LENOVO dmi.bios.version: R02ET71W (1.44 ) dmi.board.asset.tag: Not Available dmi.board.name: 20F6CTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.12 dmi.modalias: dmi:bvnLENOVO:bvrR02ET71W(1.44):bd05/08/2019:br1.44:efr1.12:svnLENOVO:pn20F6CTO1WW:pvrThinkPadX260:rvnLENOVO:rn20F6CTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20F6_BU_Think_FM_ThinkPadX260: dmi.product.family: ThinkPad X260 dmi.product.name: 20F6CTO1WW dmi.product.sku: LENOVO_MT_20F6_BU_Think_FM_ThinkPad X260 dmi.product.version: ThinkPad X260 dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1967727 Title: Random screen blanks with "CPU pipe B FIFO underrun" error Status in linux package in Ubuntu: New Bug description: On a clean 22.04 install, the screen randomly blanks once in a while for a couple of seconds, then comes back. I see the following message in dmesg when it happens: [ 6614.338572] i915 :00:02.0: [drm] *ERROR* CPU pipe B FIFO underrun ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-23-generic 5.15.0-23.23 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME Date: Mon Apr 4 10:16:27 2022 InstallationDate: Installed on 2022-04-03 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) MachineType: LENOVO 20F6CTO1WW ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-23-generic root=/dev/mapper/ubuntu-root ro rootflags=subvol=@ quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-23-generic N/A linux-backports-modules-5.15.0-23-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/08/2019 dmi.bios.release: 1.44 dmi.bios.vendor: LENOVO dmi.bios.version: R02ET71W (1.44 ) dmi.board.asset.tag: Not Available dmi.board.name: 20F6CTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.12 dmi.modalias: dmi:bvnLENOVO:bvrR02ET71W(1.44):bd05/08/2019:br1.44:efr1.12:svnLENOVO:pn20F6CTO1WW:pvrThinkPadX260:rvnLENOVO:rn20F6CTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20F6_BU_Think_FM_ThinkPadX260: dmi.product.family: ThinkPad X260 dmi.product.name: 20F6CTO1WW dmi.product.sku: LENOVO_MT_20F6_BU_Think_FM_ThinkPad X260 dmi.product.version: ThinkPad X260 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967727/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1966870] Re: Focal 20.04.4 5.13.0-27-generic crashing disabling CPUs
This is actually fixed already in 5.13.0.39.44 as shown above, but the root cause that I'm facing is that edge-Kernel is behind non -egde: $ rmadison -a amd64 -u ubuntu linux-image-generic-hwe-20.04-edge | grep focal linux-image-generic-hwe-20.04-edge | 5.13.0.27.29~20.04.13 | focal-security | amd64 linux-image-generic-hwe-20.04-edge | 5.13.0.27.29~20.04.13 | focal-updates | amd64 linux-image-generic-hwe-20.04-edge | 5.15.0.23.23~20.04.5 | focal-proposed | amd64 $ rmadison -a amd64 -u ubuntu linux-image-generic-hwe-20.04 | grep focal linux-image-generic-hwe-20.04 | 5.4.0.26.32 | focal | amd64 linux-image-generic-hwe-20.04 | 5.13.0.39.44~20.04.24 | focal-security | amd64 linux-image-generic-hwe-20.04 | 5.13.0.39.44~20.04.24 | focal-updates | amd64 And I see that this is not updated https://launchpad.net/ubuntu/+source/linux-meta-hwe-5.13 While this is stuck in proposed https://launchpad.net/ubuntu/+source/linux-meta-hwe-5.15 And never anyone levft proposed https://launchpad.net/ubuntu/+source/linux-meta-hwe-5.15/+publishinghistory Stuck in proposed, but as long as 5.15 is stuck 5.13 should continue. I do not have a perfect solution, but somehow edge should not fall behind non-edge. -- 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/1966870 Title: Focal 20.04.4 5.13.0-27-generic crashing disabling CPUs Status in linux package in Ubuntu: Confirmed Bug description: Hi I'm facing the following crash now two times in a row while runnign the same test - so somewhat reproducible it seems: [ 1444.399448] BUG: kernel NULL pointer dereference, address: 0008 [ 1444.431172] #PF: supervisor write access in kernel mode [ 1444.454715] #PF: error_code(0x0002) - not-present page [ 1444.478052] PGD 0 P4D 0 [ 1444.489448] Oops: 0002 [#1] SMP PTI [ 1444.505120] CPU: 6 PID: 26233 Comm: chcpu Tainted: PW O 5.13.0-27-generic #29~20.04.1-Ubuntu [ 1444.549884] Hardware name: HP ProLiant DL360 Gen9/ProLiant DL360 Gen9, BIOS P89 01/22/2018 [ 1444.587322] RIP: 0010:blk_mq_hctx_notify_dead+0xc7/0x190 [ 1444.611352] Code: 04 49 8d 54 05 08 4c 01 e8 48 8b 48 08 48 39 ca 74 66 48 8b 48 08 48 39 ca 74 21 48 8b 3a 48 8b 4d c8 48 8b 72 08 48 89 7d c8 <4c> 89 77 08 48 89 0e 48 89 71 08 48 89 12 48 89 50 10 41 0f b7 84 [ 1444.696490] RSP: 0018:bf5d818dbbf0 EFLAGS: 00010282 [ 1444.720510] RAX: df5d7fb788c0 RBX: RCX: bf5d818dbbf0 [ 1444.752719] RDX: df5d7fb788c8 RSI: RDI: [ 1444.784978] RBP: bf5d818dbc28 R08: R09: bf5d818dbae8 [ 1444.816712] R10: 0001 R11: 0001 R12: 983d939b [ 1444.848844] R13: df5d7fb788c0 R14: bf5d818dbbf0 R15: 0005 [ 1444.881389] FS: 7f1c8fe88580() GS:9844dfb8() knlGS: [ 1444.918201] CS: 0010 DS: ES: CR0: 80050033 [ 1444.944633] CR2: 0008 CR3: 00064ddf6006 CR4: 001706e0 [ 1444.977001] Call Trace: [ 1444.988071] ? blk_mq_exit_hctx+0x160/0x160 [ 1445.007037] cpuhp_invoke_callback+0x179/0x430 [ 1445.027179] cpuhp_invoke_callback_range+0x44/0x80 [ 1445.048737] _cpu_down+0x109/0x310 [ 1445.064062] cpu_down+0x36/0x60 [ 1445.077882] cpu_device_down+0x16/0x20 [ 1445.094741] cpu_subsys_offline+0xe/0x10 [ 1445.112439] device_offline+0x8e/0xc0 [ 1445.129064] online_store+0x4c/0x90 [ 1445.144835] dev_attr_store+0x17/0x30 [ 1445.161307] sysfs_kf_write+0x3e/0x50 [ 1445.177856] kernfs_fop_write_iter+0x138/0x1c0 [ 1445.198036] new_sync_write+0x117/0x1b0 [ 1445.215386] vfs_write+0x185/0x250 [ 1445.230649] ksys_write+0x67/0xe0 [ 1445.245565] __x64_sys_write+0x1a/0x20 [ 1445.262448] do_syscall_64+0x61/0xb0 [ 1445.278585] ? do_syscall_64+0x6e/0xb0 [ 1445.295940] ? asm_exc_page_fault+0x8/0x30 [ 1445.314969] entry_SYSCALL_64_after_hwframe+0x44/0xae [ 1445.338356] RIP: 0033:0x7f1c8fda30a7 [ 1445.355062] Code: 64 89 02 48 c7 c0 ff ff ff ff eb bb 0f 1f 80 00 00 00 00 f3 0f 1e fa 64 8b 04 25 18 00 00 00 85 c0 75 10 b8 01 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 51 c3 48 83 ec 28 48 89 54 24 18 48 89 74 24 [ 1445.440161] RSP: 002b:7fffed1c4418 EFLAGS: 0246 ORIG_RAX: 0001 [ 1445.474829] RAX: ffda RBX: 0040 RCX: 7f1c8fda30a7 [ 1445.507219] RDX: 0001 RSI: 559369f25869 RDI: 0004 [ 1445.539438] RBP: 7f1c8fe88500 R08: R09: 7fffed1c43c0 [ 1445.572547] R10: R11: 0246 R12: 0004 [ 1445.604842] R13: 7fffed1c4420 R14: 559369f25869 R15: 0001 [ 1445.636897] Modules linked in: vhost_net tap ebtable_filter ebtables veth nbd xt_comment zfs(PO) zunicode(PO) zzstd(O)
[Kernel-packages] [Bug 1902464] Update Released
The verification of the Stable Release Update for alsa-ucm-conf has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/1902464 Title: The rear panel of Lenovo P620 doesn't support more than one audio device at the same time Status in HWE Next: New Status in OEM Priority Project: Confirmed Status in alsa-ucm-conf package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: Fix Released Status in alsa-ucm-conf source package in Focal: Fix Committed Status in pulseaudio source package in Focal: Fix Released Bug description: == SRU Justification == [Impact] On P620, only single port can work on rear panel. For example, when the Line-Out is plugged, the Mic won't work anymore. [Fix] Use upstream version of UCM to handle port priority correctly, instead of separate ports into different profiles. [Test] Once the UCM is in place, all three ports of rear panel work correctly. [Where problems could occur] UCM is not a static thing - it's actually interpreted differently at higher level. So any change in userspace daemons other than PulseAudio may not like the change and can interpret the UCM in another way. == Original Bug Report == After backporting following patches from PA and alsa-ucm-conf and then it works. https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/290 https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/354 https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/355 https://github.com/alsa-project/alsa-ucm-conf/tree/master/ucm2/USB- Audio [landed by aa74f4c12eefcc98582572d2fc48982cf7478b51] Here is the test PPA: https://launchpad.net/~os369510/+archive/ubuntu/oem-package-test Since the upstream not yet accepted those patches, the regression potential may quite high. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1902464/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1967726] [NEW] Disabled S3 ACPI standby state on DELL Precision M3560
Public bug reported: Device information for https://answers.launchpad.net/ubuntu- certification/+question/701164 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.14.0-1031-oem 5.14.0-1031.34 ProcVersionSignature: Ubuntu 5.14.0-1031.34-oem 5.14.21 Uname: Linux 5.14.0-1031-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Apr 4 09:58:28 2022 InstallationDate: Installed on 2021-12-06 (118 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: linux-signed-oem-5.14 UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.cron.daily.apport: [deleted] ** Affects: linux-signed-oem-5.14 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1967726 Title: Disabled S3 ACPI standby state on DELL Precision M3560 Status in linux-signed-oem-5.14 package in Ubuntu: New Bug description: Device information for https://answers.launchpad.net/ubuntu- certification/+question/701164 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.14.0-1031-oem 5.14.0-1031.34 ProcVersionSignature: Ubuntu 5.14.0-1031.34-oem 5.14.21 Uname: Linux 5.14.0-1031-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Apr 4 09:58:28 2022 InstallationDate: Installed on 2021-12-06 (118 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: linux-signed-oem-5.14 UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.cron.daily.apport: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-oem-5.14/+bug/1967726/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1962349] Update Released
The verification of the Stable Release Update for bolt has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1962349 Title: Bolt doesn't work with native USB4 hosts Status in OEM Priority Project: New Status in bolt package in Ubuntu: Fix Released Status in linux package in Ubuntu: In Progress Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: In Progress Status in bolt source package in Focal: Fix Committed Status in linux source package in Focal: Won't Fix Status in linux-oem-5.14 source package in Focal: In Progress Status in linux-oem-5.17 source package in Focal: Invalid Status in bolt source package in Impish: Fix Released Status in linux source package in Impish: Won't Fix Status in linux-oem-5.14 source package in Impish: Invalid Status in linux-oem-5.17 source package in Impish: Invalid Status in bolt source package in Jammy: Fix Released Status in linux source package in Jammy: In Progress Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: In Progress Bug description: [Impact] * AMD Yellow Carp provides integrated USB4 host controllers * When plugging in a Thunderbolt3 or USB4 device, users are unable to authorize it using the GUI due to an error message: "parent not authorized, deferring" [Test Plan] AMD Yellow Carp Host (issue this bug is about) -- * Plug in USB4 device or TBT3 to AMD Yellow Carp host * Ensure that PCI topology has populated * Observe that /sys/bus/thunderbolt/devices/DEVICE/authorized is "0" * Try to run `boltctl enroll $UUID` Alpine Ridge / Titan Ridge host (discrete controller) -- Start out on a host with discrete controller (Alpine Ridge or Titan Ridge) 1. sudo boltctl forget -a 2. Plug in dock 3. Make sure 'boltctl list' enumerates dock. 4. Check /sys/bus/thunderbolt/devices/domain0/iommu_dma_protection (value dependent upon host) - If 0; try to manually enroll using 'boltctl enroll $UUID' - If 1; ensure that device automatically enrolled with bolt. GUI Check - Ensure that devices show up in the Settings GUI and are now able to authorize. Note: for AMD platforms enumerating PCIe devices is a separate problem from BOLT handled by kernel tasks. GUI check is only about "authorization". [Where problems could occur] * Intel USB4 or TBT3 hosts also use bolt. They could have a problem with the new version of bolt. * This is very unlikely however since there is a through test suite, and up until now the entire industry has been using bolt on Intel controllers for a long time. * There haven't been any significant bugs reported upstream or in Ubuntu since 0.9.1 release. [Other Info] * This bug also occurs on Intel controllers from ICL, TGL or ALD, but in many cases they are automatically authorized to an iommu DMA policy. * It is fixed in bolt 0.9.1 or later release. * To solve the SRU, will backport 0.9.1 release from Impish. * I did look into backporting just the commit(s) for fixing this, but it's not a trivial backport. Quoting the changelog (https://gitlab.freedesktop.org/bolt/bolt/-/blob/master/CHANGELOG.md): "Additionally the unique_id of said host controller changes with every boot, which breaks one of the fundamental assumptions in boltd". To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1962349/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1967649] Re: package linux-firmware 1.187.29 failed to install/upgrade: trying to overwrite '/lib/firmware/RTL8192E/boot.img', which is also in package firmware-realtek 20210818
You have firmware files that are provided by two different packages. You have firmware-realtek 20210818-1 installed which is not an Ubuntu package but a Debian package. You should not install Debian packages on an Ubuntu system. ** Changed in: linux-firmware (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1967649 Title: package linux-firmware 1.187.29 failed to install/upgrade: trying to overwrite '/lib/firmware/RTL8192E/boot.img', which is also in package firmware-realtek 20210818-1 Status in linux-firmware package in Ubuntu: Invalid Bug description: everytime i start os got this error ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-firmware 1.187.29 ProcVersionSignature: Ubuntu 5.8.0-59.66~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-59-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sarif 1115 F pulseaudio /dev/snd/controlC2: sarif 1115 F pulseaudio /dev/snd/controlC0: sarif 1115 F pulseaudio CasperMD5CheckResult: skip Date: Sun Apr 3 08:00:21 2022 Dependencies: ErrorMessage: trying to overwrite '/lib/firmware/RTL8192E/boot.img', which is also in package firmware-realtek 20210818-1 InstallationDate: Installed on 2021-01-24 (433 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Micro-Star International Co., Ltd. MS-7B89 PackageArchitecture: all ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-59-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.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.04-1ubuntu26.13 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux-firmware Title: package linux-firmware 1.187.29 failed to install/upgrade: trying to overwrite '/lib/firmware/RTL8192E/boot.img', which is also in package firmware-realtek 20210818-1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/10/2020 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.80 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:bvnAmericanMegatrendsInc.:bvr2.80:bd06/10/2020:br5.14:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B89:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450MMORTARMAX(MS-7B89):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0: 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-firmware/+bug/1967649/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1967679] Re: THOMSON GEN360-4C128BK touchscreen does not work
** Summary changed: - touchscreen + THOMSON GEN360-4C128BK touchscreen does not work ** Package changed: xorg (Ubuntu) => linux-hwe-5.13 (Ubuntu) ** Summary changed: - THOMSON GEN360-4C128BK touchscreen does not work + Thomson Neo 360 X (GEN360-4C128BK) touchscreen does not work -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1967679 Title: Thomson Neo 360 X (GEN360-4C128BK) touchscreen does not work Status in linux-hwe-5.13 package in Ubuntu: New Bug description: touchscreen does not work at any time ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Apr 3 16:06:33 2022 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation UHD Graphics 605 [8086:3185] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Device [0501:02f3] Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 1902:8301 Generic HD camera Bus 001 Device 002: ID 8087:0a2a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: THOMSON GEN360-4C128BK ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-30-generic root=UUID=461ced2f-89f8-4a9c-a1ec-fe9520b392d8 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/06/2021 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GP12_THOMSON_0_04 dmi.board.asset.tag: Default string dmi.board.name: GP12 dmi.board.vendor: MX dmi.board.version: V300 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGP12_THOMSON_0_04:bd09/06/2021:br5.13:svnTHOMSON:pnGEN360-4C128BK:pvrV300:rvnMX:rnGP12:rvrV300:cvnDefaultstring:ct3:cvrDefaultstring:skuGEN360-4C128BK: dmi.product.family: MIPI PC dmi.product.name: GEN360-4C128BK dmi.product.sku: GEN360-4C128BK dmi.product.version: V300 dmi.sys.vendor: THOMSON version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.13/+bug/1967679/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1967679] [NEW] THOMSON GEN360-4C128BK touchscreen does not work
You have been subscribed to a public bug: touchscreen does not work at any time ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Apr 3 16:06:33 2022 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation UHD Graphics 605 [8086:3185] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Device [0501:02f3] Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 1902:8301 Generic HD camera Bus 001 Device 002: ID 8087:0a2a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: THOMSON GEN360-4C128BK ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-30-generic root=UUID=461ced2f-89f8-4a9c-a1ec-fe9520b392d8 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/06/2021 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GP12_THOMSON_0_04 dmi.board.asset.tag: Default string dmi.board.name: GP12 dmi.board.vendor: MX dmi.board.version: V300 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGP12_THOMSON_0_04:bd09/06/2021:br5.13:svnTHOMSON:pnGEN360-4C128BK:pvrV300:rvnMX:rnGP12:rvrV300:cvnDefaultstring:ct3:cvrDefaultstring:skuGEN360-4C128BK: dmi.product.family: MIPI PC dmi.product.name: GEN360-4C128BK dmi.product.sku: GEN360-4C128BK dmi.product.version: V300 dmi.sys.vendor: THOMSON version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: linux-hwe-5.13 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu -- THOMSON GEN360-4C128BK touchscreen does not work https://bugs.launchpad.net/bugs/1967679 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.13 in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1967721] 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/1967721 Title: Laptop never resuming from standby Status in linux package in Ubuntu: Confirmed Bug description: On a Lenovo Thinkpad X260 with 22.04 and 5.15.0-23-generic kernel, after suspending the laptop, it's never possible to wake it up. Neither keyboard nor power button work, only way is to long-press to force poweroff and restart. This did not happen with 21.10. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-23-generic 5.15.0-23.23 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME Date: Mon Apr 4 08:30:52 2022 InstallationDate: Installed on 2022-04-03 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) MachineType: LENOVO 20F6CTO1WW ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-23-generic root=/dev/mapper/ubuntu-root ro rootflags=subvol=@ quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-23-generic N/A linux-backports-modules-5.15.0-23-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/08/2019 dmi.bios.release: 1.44 dmi.bios.vendor: LENOVO dmi.bios.version: R02ET71W (1.44 ) dmi.board.asset.tag: Not Available dmi.board.name: 20F6CTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.12 dmi.modalias: dmi:bvnLENOVO:bvrR02ET71W(1.44):bd05/08/2019:br1.44:efr1.12:svnLENOVO:pn20F6CTO1WW:pvrThinkPadX260:rvnLENOVO:rn20F6CTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20F6_BU_Think_FM_ThinkPadX260: dmi.product.family: ThinkPad X260 dmi.product.name: 20F6CTO1WW dmi.product.sku: LENOVO_MT_20F6_BU_Think_FM_ThinkPad X260 dmi.product.version: ThinkPad X260 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967721/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1967721] [NEW] Laptop never resuming from standby
Public bug reported: On a Lenovo Thinkpad X260 with 22.04 and 5.15.0-23-generic kernel, after suspending the laptop, it's never possible to wake it up. Neither keyboard nor power button work, only way is to long-press to force poweroff and restart. This did not happen with 21.10. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-23-generic 5.15.0-23.23 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME Date: Mon Apr 4 08:30:52 2022 InstallationDate: Installed on 2022-04-03 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) MachineType: LENOVO 20F6CTO1WW ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-23-generic root=/dev/mapper/ubuntu-root ro rootflags=subvol=@ quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-23-generic N/A linux-backports-modules-5.15.0-23-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/08/2019 dmi.bios.release: 1.44 dmi.bios.vendor: LENOVO dmi.bios.version: R02ET71W (1.44 ) dmi.board.asset.tag: Not Available dmi.board.name: 20F6CTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.12 dmi.modalias: dmi:bvnLENOVO:bvrR02ET71W(1.44):bd05/08/2019:br1.44:efr1.12:svnLENOVO:pn20F6CTO1WW:pvrThinkPadX260:rvnLENOVO:rn20F6CTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20F6_BU_Think_FM_ThinkPadX260: dmi.product.family: ThinkPad X260 dmi.product.name: 20F6CTO1WW dmi.product.sku: LENOVO_MT_20F6_BU_Think_FM_ThinkPad X260 dmi.product.version: ThinkPad X260 dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1967721 Title: Laptop never resuming from standby Status in linux package in Ubuntu: New Bug description: On a Lenovo Thinkpad X260 with 22.04 and 5.15.0-23-generic kernel, after suspending the laptop, it's never possible to wake it up. Neither keyboard nor power button work, only way is to long-press to force poweroff and restart. This did not happen with 21.10. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-23-generic 5.15.0-23.23 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME Date: Mon Apr 4 08:30:52 2022 InstallationDate: Installed on 2022-04-03 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) MachineType: LENOVO 20F6CTO1WW ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-23-generic root=/dev/mapper/ubuntu-root ro rootflags=subvol=@ quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-23-generic N/A linux-backports-modules-5.15.0-23-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/08/2019 dmi.bios.release: 1.44 dmi.bios.vendor: LENOVO dmi.bios.version: R02ET71W (1.44 ) dmi.board.asset.tag: Not Available dmi.board.name: 20F6CTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.12 dmi.modalias: dmi:bvnLENOVO:bvrR02ET71W(1.44):bd05/08/2019:br1.44:efr1.12:svnLENOVO:pn20F6CTO1WW:pvrThinkPadX260:rvnLENOVO:rn20F6CTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20F6_BU_Think_FM_ThinkPadX260: dmi.product.family: ThinkPad X260 dmi.product.name: 20F6CTO1WW dmi.product.sku: LENOVO_MT_20F6_BU_Think_FM_ThinkPad X260 dmi.product.version: ThinkPad X260 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967721/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp