[Kernel-packages] [Bug 1926439] Re: Dependencies conflicts breaks upgrade process
Problem is still here: ~# apt show linux-modules-nvidia-470-5.4.0-90-generic Package: linux-modules-nvidia-470-5.4.0-90-generic Version: 5.4.0-90.101+1 Priority: optional Section: restricted/kernel Source: linux-restricted-modules Origin: Ubuntu Maintainer: Canonical Kernel Team Bugs: https://bugs.launchpad.net/ubuntu/+filebug Installed-Size: 32,8 kB Depends: debconf (>= 0.5) | debconf-2.0, linux-image-5.4.0-90-generic | linux-image-unsigned-5.4.0-90-generic, linux-signatures-nvidia-5.4.0-90-generic (= 5.4.0-90.101+1), linux-objects-nvidia-470-5.4.0-90-generic (= 5.4.0-90.101+1), nvidia-kernel-common-470 (<= 470.82.00-1), nvidia-kernel-common-470 (>= 470.82.00) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules in Ubuntu. https://bugs.launchpad.net/bugs/1926439 Title: Dependencies conflicts breaks upgrade process Status in linux-restricted-modules package in Ubuntu: Confirmed Bug description: Latest updates of linux-restricted-modules breaks upgrade process, updates cannot be installed without removing nvidia modules for previous kernel version, unattended-upgrade cannot do that, as result we have broken system without nvidia driver ~# apt full-upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages will be REMOVED: linux-modules-nvidia-460-5.4.0-71-generic The following NEW packages will be installed: linux-modules-nvidia-460-5.4.0-72-generic linux-objects-nvidia-460-5.4.0-72-generic linux-signatures-nvidia-5.4.0-72-generic The following packages will be upgraded: libnvidia-cfg1-460 libnvidia-compute-460 libnvidia-compute-460:i386 libnvidia-decode-460 libnvidia-decode-460:i386 libnvidia-encode-460 libnvidia-encode-460:i386 libnvidia-extra-460 libnvidia-fbc1-460 libnvidia-fbc1-460:i386 libnvidia-gl-460 libnvidia-gl-460:i386 libnvidia-ifr1-460 libnvidia-ifr1-460:i386 linux-modules-nvidia-460-generic nvidia-compute-utils-460 nvidia-driver-460 nvidia-kernel-common-460 nvidia-kernel-source-460 nvidia-utils-460 xserver-xorg-video-nvidia-460 21 upgraded, 3 newly installed, 1 to remove and 0 not upgraded. Need to get 199 MB of archives. After this operation, 45.6 MB of additional disk space will be used. Do you want to continue? [Y/n] ~# apt show linux-modules-nvidia-460-5.4.0-71-generic Package: linux-modules-nvidia-460-5.4.0-71-generic Version: 5.4.0-71.79+1 Priority: optional Section: restricted/kernel Source: linux-restricted-modules Origin: Ubuntu Maintainer: Canonical Kernel Team Bugs: https://bugs.launchpad.net/ubuntu/+filebug Installed-Size: 32.8 kB Depends: debconf (>= 0.5) | debconf-2.0, linux-image-5.4.0-71-generic | linux-image-unsigned-5.4.0-71-generic, linux-signatures-nvidia-5.4.0-71-generic (= 5.4.0-71.79+1), linux-objects-nvidia-460-5.4.0-71-generic (= 5.4.0-71.79+1), nvidia-kernel-common-460 (<= 460.56-1), nvidia-kernel-common-460 (>= 460.56) Download-Size: 7136 B APT-Manual-Installed: no APT-Sources: http://archive.pls.pbank.com.ua/ubuntu-current focal-updates/restricted amd64 Packages Description: Linux kernel nvidia modules for version 5.4.0-71 This dependencies should be removed to fix this problem: nvidia-kernel-common-460 (<= 460.56-1), nvidia-kernel-common-460 (>= 460.56) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1926439/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1950523] 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/1950523 Title: 20.04.3 ignoring settings for touchpad. Status in linux package in Ubuntu: Confirmed Bug description: Since installing 20.04.3 LTS, the touchpad settings are being ignored; I use right as primary; it has forced left as primary desite the setting being for right. It is also ignoring the scrolling direction; again, I don't like the default. the trackpad is an elan model. While the machine isn't bricked, I find the button mapping majorly problematic. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.36 ProcVersionSignature: Ubuntu 5.4.0-90.101-generic 5.4.148 Uname: Linux 5.4.0-90-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Wed Nov 10 14:12:21 2021 InstallationDate: Installed on 2021-05-01 (193 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: Upgraded to focal on 2021-05-22 (171 days ago) VarLogDistupgradeTermlog: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950523/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1950523] Re: 20.04.3 ignoring settings for touchpad.
Thank you for taking the time to report this bug and helping to make Ubuntu better. The report was tagged against `ubuntu-release-upgrader` which upgrades from one release (18.04) to a later release (20.04) which was last run 171 days ago. Bug reporting is mostly about finding & fixing problems thus preventing future users from hitting the same bug. I suspect a Support site would be more appropriate, eg. https://answers.launchpad.net/ubuntu. You can also find help with your problem in the support forum of your local Ubuntu community http://loco.ubuntu.com/ or asking at https://askubuntu.com or https://ubuntuforums.org, or for more support options please look at https://discourse.ubuntu.com/t/community-support/709 ** Package changed: ubuntu-release-upgrader (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/1950523 Title: 20.04.3 ignoring settings for touchpad. Status in linux package in Ubuntu: New Bug description: Since installing 20.04.3 LTS, the touchpad settings are being ignored; I use right as primary; it has forced left as primary desite the setting being for right. It is also ignoring the scrolling direction; again, I don't like the default. the trackpad is an elan model. While the machine isn't bricked, I find the button mapping majorly problematic. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.36 ProcVersionSignature: Ubuntu 5.4.0-90.101-generic 5.4.148 Uname: Linux 5.4.0-90-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Wed Nov 10 14:12:21 2021 InstallationDate: Installed on 2021-05-01 (193 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: Upgraded to focal on 2021-05-22 (171 days ago) VarLogDistupgradeTermlog: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950523/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1950523] [NEW] 20.04.3 ignoring settings for touchpad.
You have been subscribed to a public bug: Since installing 20.04.3 LTS, the touchpad settings are being ignored; I use right as primary; it has forced left as primary desite the setting being for right. It is also ignoring the scrolling direction; again, I don't like the default. the trackpad is an elan model. While the machine isn't bricked, I find the button mapping majorly problematic. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.36 ProcVersionSignature: Ubuntu 5.4.0-90.101-generic 5.4.148 Uname: Linux 5.4.0-90-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Wed Nov 10 14:12:21 2021 InstallationDate: Installed on 2021-05-01 (193 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: Upgraded to focal on 2021-05-22 (171 days ago) VarLogDistupgradeTermlog: ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug dist-upgrade focal -- 20.04.3 ignoring settings for touchpad. https://bugs.launchpad.net/bugs/1950523 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-hwe-5.13/5.13.0.22.22~20.04.9)
All autopkgtests for the newly accepted linux-meta-hwe-5.13 (5.13.0.22.22~20.04.9) for focal have finished running. The following regressions have been reported in tests triggered by the package: systemd/245.4-4ubuntu3.13 (ppc64el, s390x, amd64) nvidia-graphics-drivers-340/340.108-0ubuntu5.20.04.2 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#linux-meta-hwe-5.13 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Confirmed Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Invalid Status in linux-azure-edge source package in Precise: Invalid Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Invalid Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Confirmed Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packing resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1950536] Re: keyboard not working on Medion notebook s17 series
** Description changed: [Impact] - The keyboard of some medion laptops can't work under Linux. + The keyboard of some medion s17 series laptops can't work under Linux. [Fix] Backport a upstream patch, after applying the patch, the keyboard will skip the irq override from the acpi resource layer, and the keyboard could work normally. [Test] Booting the patched kernel, use the keyboard to do the input. [Where problems could occur] The patch will skip the irq override based on the DMI info, so if a medion laptop which has the same DMI info and the irq 1 needs to be overriden, this patch will introduce regression on the machine, but this possibility is very low. If this happens, we will consider to add more DMI match info in the table. + This is a bug similar to #1909814. -- 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/1950536 Title: keyboard not working on Medion notebook s17 series Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: In Progress Status in linux source package in Hirsute: In Progress Status in linux source package in Impish: In Progress Status in linux source package in Jammy: In Progress Bug description: [Impact] The keyboard of some medion s17 series laptops can't work under Linux. [Fix] Backport a upstream patch, after applying the patch, the keyboard will skip the irq override from the acpi resource layer, and the keyboard could work normally. [Test] Booting the patched kernel, use the keyboard to do the input. [Where problems could occur] The patch will skip the irq override based on the DMI info, so if a medion laptop which has the same DMI info and the irq 1 needs to be overriden, this patch will introduce regression on the machine, but this possibility is very low. If this happens, we will consider to add more DMI match info in the table. This is a bug similar to #1909814. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950536/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1950540] Re: alsa/sof: All audio jacks can't detect hotplug when only codec is suspended
** Description changed: - This bug is for tracking purpose. + [Impact] + If the codec is in rt_suspend while the controller is in rt_resume, + all audio jacks can't detect hotplug. + + [Fix] + Backport a upstream patch, this will enable WAKEEN in the period + between codec suspend and controller suspend. + + [Test] + Booting the patched kernel, add snd_sof_pci.sof_pci_debug=0x1 in + the bootargs, plug the headset to the audio jacks, the system + could detect the plug in or plug out. + + [Where problems could occur] + The patch enable the WAKEEN after codec is in rt_suspend, this + could affect the audio jack hotplug detection, if it introduces + regression, it will be on the audio jack detection, but this + possibility is very low, we already verified this patch on + many machines. -- 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/1950540 Title: alsa/sof: All audio jacks can't detect hotplug when only codec is suspended Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.13 source package in Focal: In Progress 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.13 source package in Impish: Invalid Status in linux-oem-5.14 source package in Impish: Invalid Status in linux source package in Jammy: In Progress Status in linux-oem-5.13 source package in Jammy: Invalid Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: [Impact] If the codec is in rt_suspend while the controller is in rt_resume, all audio jacks can't detect hotplug. [Fix] Backport a upstream patch, this will enable WAKEEN in the period between codec suspend and controller suspend. [Test] Booting the patched kernel, add snd_sof_pci.sof_pci_debug=0x1 in the bootargs, plug the headset to the audio jacks, the system could detect the plug in or plug out. [Where problems could occur] The patch enable the WAKEEN after codec is in rt_suspend, this could affect the audio jack hotplug detection, if it introduces regression, it will be on the audio jack detection, but this possibility is very low, we already verified this patch on many machines. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1950540/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1950471] 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 1950471 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/1950471 Title: Touchpad on HP Spectre x360 gets into unusable state Status in libinput package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: I have an HP Spectre x360 (13t-aw200) that has had problems with its touchpad since I first loaded Ubuntu onto it. When it initially starts, it's working fine, then at some point in time (it's unclear what triggers it), it gets into this state where simply doing a single-finger swipe to move the cursor no longer works. If I press down and swipe, it does move/select as expected, but when I return to not pressing down, it goes back to its previous, unworking state. Other clues: - It appears if I press HARD but don't cause a down event, it SOMETIMES moves the cursor. - If it's in this state and I'm on some scrolling window, it will scroll with a single finger (i.e. as it acts as if I have two fingers down). - It often will return to a working state for a while then go back to not working. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Nov 10 05:56:51 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- InstallationDate: Installed on 2021-10-28 (13 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/zsh SourcePackage: ubiquity Symptom: installation UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1950471/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1950540] [NEW] alsa/sof: All audio jacks can't detect hotplug when only codec is suspended
Public bug reported: This bug is for tracking purpose. ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: High Assignee: Hui Wang (hui.wang) Status: In Progress ** Affects: linux-oem-5.13 (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux-oem-5.14 (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Focal) Importance: Undecided Status: Invalid ** Affects: linux-oem-5.13 (Ubuntu Focal) Importance: High Status: In Progress ** Affects: linux-oem-5.14 (Ubuntu Focal) Importance: High Status: In Progress ** Affects: linux (Ubuntu Impish) Importance: High Status: In Progress ** Affects: linux-oem-5.13 (Ubuntu Impish) Importance: Undecided Status: Invalid ** Affects: linux-oem-5.14 (Ubuntu Impish) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Jammy) Importance: High Assignee: Hui Wang (hui.wang) Status: In Progress ** Affects: linux-oem-5.13 (Ubuntu Jammy) Importance: Undecided Status: Invalid ** Affects: linux-oem-5.14 (Ubuntu Jammy) Importance: Undecided Status: Invalid ** Tags: oem-priority originate-from-1946720 sutton ** Also affects: linux-oem-5.13 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-oem-5.14 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-oem-5.13 (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-oem-5.14 (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: linux-oem-5.13 (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: linux-oem-5.14 (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Assignee: Hui Wang (hui.wang) Status: New ** Also affects: linux-oem-5.13 (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-oem-5.14 (Ubuntu Jammy) Importance: Undecided Status: New ** Tags added: oem-priority originate-from-1946720 sutton ** Changed in: linux (Ubuntu Focal) Status: New => Invalid ** Changed in: linux-oem-5.13 (Ubuntu Impish) Status: New => Invalid ** Changed in: linux-oem-5.13 (Ubuntu Jammy) Status: New => Invalid ** Changed in: linux-oem-5.14 (Ubuntu Impish) Status: New => Invalid ** Changed in: linux-oem-5.14 (Ubuntu Jammy) Status: New => Invalid ** Changed in: linux-oem-5.13 (Ubuntu Focal) Status: New => In Progress ** Changed in: linux-oem-5.14 (Ubuntu Focal) Importance: Undecided => High ** Changed in: linux-oem-5.14 (Ubuntu Focal) Status: New => In Progress ** Changed in: linux-oem-5.13 (Ubuntu Focal) Importance: Undecided => High ** Changed in: linux (Ubuntu Impish) Importance: Undecided => High ** Changed in: linux (Ubuntu Impish) Status: New => In Progress ** Changed in: linux (Ubuntu Jammy) Importance: Undecided => High ** Changed in: linux (Ubuntu Jammy) Status: New => In Progress ** Summary changed: - alsa/sof: All audio jack can't detect hotplug when only codec is suspended + alsa/sof: All audio jacks can't detect hotplug when only codec is suspended -- 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/1950540 Title: alsa/sof: All audio jacks can't detect hotplug when only codec is suspended Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.13 source package in Focal: In Progress 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.13 source package in Impish: Invalid Status in linux-oem-5.14 source package in Impish: Invalid Status in linux source package in Jammy: In Progress Status in linux-oem-5.13 source package in Jammy: Invalid Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: This bug is for tracking purpose. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1950540/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1948862] Re: KVM emulation failure when booting into VM crash kernel with multiple CPUs
Performing verification for Bionic. I installed the current 4.15.0-162-generic kernel from -updates to a host in segmaas, and brought up my Bionic VM I installed for the reproducer. The Bionic VM has linux-crashdump configured, with nr_cpus configured to 8: ubuntu@bionic-vm:~$ kdump-config show DUMP_MODE:kdump USE_KDUMP:1 KDUMP_SYSCTL: kernel.panic_on_oops=1 KDUMP_COREDIR:/var/crash crashkernel addr: 0x /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinuz-4.15.0-159-generic kdump initrd: /var/lib/kdump/initrd.img: symbolic link to /var/lib/kdump/initrd.img-4.15.0-159-generic current state:ready to kdump kexec command: /sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinuz-4.15.0-159-generic root=UUID=5c23b432-4d00-4a01-8ecd-964803c8e10a ro console=tty1 console=ttyS0 reset_devices systemd.unit=kdump-tools-dump.service nr_cpus=8 irqpoll nousb ata_piix.prefer_ms_hyperv=0 ignore_loglevel nmi_debug=state,regs apic_extnmi=none" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz I then triggered the crashdump in the VM: $ sudo -s # echo c > /proc/sysrq-trigger On the host, we look at the tail of: $ sudo tail -f /var/log/libvirt/qemu/bionic-vm.log ... KVM internal error. Suberror: 1 emulation failure EAX=de8f EBX= ECX=008f EDX=0600 ESI= EDI= EBP= ESP=f90c EIP=cdb1 EFL=0002 [---] CPL=0 II=0 A20=1 SMM=0 HLT=0 ES = 9300 CS =f000 000f 9b00 SS =de00 000de000 9300 DS =de00 000de000 9300 FS = 9300 GS = 9300 LDT= 8200 TR = 8b00 GDT= IDT= CR0=6010 CR2= CR3=32b2a000 CR4= DR0= DR1= DR2= DR3= DR6=0ff0 DR7=0400 EFER= Code=66 83 c4 28 66 5b 66 c3 66 56 66 53 66 52 b1 8f 88 c8 e6 70 71 66 0f b6 f0 66 89 f2 67 88 54 24 03 88 c8 e6 70 66 31 db 88 d8 e6 71 66 56 66 68 1a $ virsh list IdName State 1 bionic-vm paused Okay, we can reproduce the issue. I then enabled -proposed, and installed the 4.15.0-163-generic kernel: $ uname -rv 4.15.0-163-generic #171-Ubuntu SMP Fri Nov 5 11:55:11 UTC 2021 I started the same VM, verified it has a crashkernel with nr_cpus=8: $ kdump-config show DUMP_MODE:kdump USE_KDUMP:1 KDUMP_SYSCTL: kernel.panic_on_oops=1 KDUMP_COREDIR:/var/crash crashkernel addr: 0x /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinuz-4.15.0-159-generic kdump initrd: /var/lib/kdump/initrd.img: symbolic link to /var/lib/kdump/initrd.img-4.15.0-159-generic current state:ready to kdump kexec command: /sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinuz-4.15.0-159-generic root=UUID=5c23b432-4d00-4a01-8ecd-964803c8e10a ro console=tty1 console=ttyS0 reset_devices systemd.unit=kdump-tools-dump.service nr_cpus=8 irqpoll nousb ata_piix.prefer_ms_hyperv=0 ignore_loglevel nmi_debug=state,regs apic_extnmi=none" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz I then triggered the crashdump: $ sudo -s # echo c > /proc/sysrq-trigger On the host: $ sudo tail -f /var/log/libvirt/qemu/bionic-vm.log ... 2021-11-11T02:41:45.970264Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.8001H:ECX.svm [bit 2] 2021-11-11T02:41:45.971185Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.8001H:ECX.svm [bit 2] $ virsh list IdName State 1 bionic-vm running Checking the VM, the crashdump completed successfully and restarted correctly. $ virsh console bionic-vm ... Copying data : [100.0 %] \ eta: 0s [ 12.034361] kdump-tools[874]: The dumpfile is saved to /var/crash/20210246/dump-incomplete. [ 12.036787] kdump-tools[874]: makedumpfile Completed. [ 12.038752] kdump-tools[874]: * kdump-tools: saved vmcore in /var/crash/20210246 [ 12.058489] kdump-tools[874]: * running makedumpfile --dump-dmesg /proc/vmcore /var/crash/20210246/dmesg.20210246 [ 12.069700] kdump-tools[874]: The dmesg log is saved to /var/crash/20210246/dmesg.20210246. [ 12.072574] kdump-tools[874]: makedumpfile Completed. [ 12.074245] kdump-tools[874]: * kdump-tools: saved dmesg content in /var/crash/20210246 [ 12.159319] kdump-tools[874]: Thu, 11 Nov 2021 02:46:54 + ... I then did this a further 4 times, each time the crashdump completed succesfully. I then destroyed and started the VM fresh, and kept crashdumping. It worked every time. The 4.15.0-163-generic kernel in -proposed fixes
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-oem-5.14/5.14.0.1008.8)
All autopkgtests for the newly accepted linux-meta-oem-5.14 (5.14.0.1008.8) for focal have finished running. The following regressions have been reported in tests triggered by the package: virtualbox/6.1.26-dfsg-3~ubuntu1.20.04.2 (amd64) virtualbox-hwe/6.1.26-dfsg-3~ubuntu1.20.04.2 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#linux-meta-oem-5.14 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Confirmed Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Invalid Status in linux-azure-edge source package in Precise: Invalid Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Invalid Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Confirmed Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packing resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1950487] Re: screen flickering
Thanks for the bug report. Please: 1. Edit /etc/default/grub and change: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" to GRUB_CMDLINE_LINUX_DEFAULT="quiet splash i915.enable_psr=0" 2. Run: sudo update-grub 3. Reboot. ** Package changed: xorg (Ubuntu) => linux (Ubuntu) ** Summary changed: - screen flickering + [Lenovo Y50-70] [i915] Screen flickering ** 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/1950487 Title: [Lenovo Y50-70] [i915] Screen flickering Status in linux package in Ubuntu: Incomplete Bug description: The problem is, when i start working on my pc the screen start flickering goes from black to normal, it's a matter of graphic card(nvidia) but i failed to solve it, any suggestion: *-display UNCLAIMED description: 3D controller product: GM107M [GeForce GTX 960M] vendor: NVIDIA Corporation physical id: 0 bus info: pci@:01:00.0 version: a2 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list configuration: latency=0 resources: memory:d000-d0ff memory:a000-afff memory:b000-b1ff ioport:4000(size=128) memory:b200-b207 *-display description: VGA compatible controller product: 4th Gen Core Processor Integrated Graphics Controller vendor: Intel Corporation physical id: 2 bus info: pci@:00:02.0 version: 06 width: 64 bits clock: 33MHz capabilities: msi pm vga_controller bus_master cap_list configuration: driver=i915 latency=0 resources: irq:37 memory:d100-d13f memory:c000-cfff ioport:5000(size=64) memory:c-d ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: xorg 1:7.7+22ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18 Uname: Linux 5.13.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Nov 10 17:14:48 2021 DistUpgraded: Fresh install DistroCodename: impish DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Lenovo 4th Gen Core Processor Integrated Graphics Controller [17aa:3978] Subsystem: Lenovo GM107M [GeForce GTX 960M] [17aa:3978] InstallationDate: Installed on 2021-11-10 (0 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: LENOVO 20378 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-21-generic root=UUID=eb605582-0819-4c08-a72a-63c9558e8612 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/12/2015 dmi.bios.release: 3.43 dmi.bios.vendor: LENOVO dmi.bios.version: 9ECN43WW(V3.03) dmi.board.asset.tag: 31900058WIN dmi.board.name: Lenovo Y50-70 dmi.board.vendor: LENOVO dmi.board.version: 31900058WIN dmi.chassis.asset.tag: 31900058WIN dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Y50-70 dmi.ec.firmware.release: 3.43 dmi.modalias: dmi:bvnLENOVO:bvr9ECN43WW(V3.03):bd08/12/2015:br3.43:efr3.43:svnLENOVO:pn20378:pvrLenovoY50-70:rvnLENOVO:rnLenovoY50-70:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoY50-70:skuLENOVO_MT_20378_BU_idea_FM_LenovoY50-70: dmi.product.family: IDEAPAD dmi.product.name: 20378 dmi.product.sku: LENOVO_MT_20378_BU_idea_FM_Lenovo Y50-70 dmi.product.version: Lenovo Y50-70 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950487/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1950471] Re: Touchpad on HP Spectre x360 gets into unusable state
** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1950471 Title: Touchpad on HP Spectre x360 gets into unusable state Status in libinput package in Ubuntu: New Status in linux package in Ubuntu: New Bug description: I have an HP Spectre x360 (13t-aw200) that has had problems with its touchpad since I first loaded Ubuntu onto it. When it initially starts, it's working fine, then at some point in time (it's unclear what triggers it), it gets into this state where simply doing a single-finger swipe to move the cursor no longer works. If I press down and swipe, it does move/select as expected, but when I return to not pressing down, it goes back to its previous, unworking state. Other clues: - It appears if I press HARD but don't cause a down event, it SOMETIMES moves the cursor. - If it's in this state and I'm on some scrolling window, it will scroll with a single finger (i.e. as it acts as if I have two fingers down). - It often will return to a working state for a while then go back to not working. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Nov 10 05:56:51 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- InstallationDate: Installed on 2021-10-28 (13 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/zsh SourcePackage: ubiquity Symptom: installation UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1950471/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1950536] [NEW] keyboard not working on Medion notebook s17 series
Public bug reported: [Impact] The keyboard of some medion laptops can't work under Linux. [Fix] Backport a upstream patch, after applying the patch, the keyboard will skip the irq override from the acpi resource layer, and the keyboard could work normally. [Test] Booting the patched kernel, use the keyboard to do the input. [Where problems could occur] The patch will skip the irq override based on the DMI info, so if a medion laptop which has the same DMI info and the irq 1 needs to be overriden, this patch will introduce regression on the machine, but this possibility is very low. If this happens, we will consider to add more DMI match info in the table. This is a bug similar to #1909814. ** Affects: linux (Ubuntu) Importance: Low Assignee: Hui Wang (hui.wang) Status: In Progress ** Affects: linux (Ubuntu Focal) Importance: Low Status: In Progress ** Affects: linux (Ubuntu Hirsute) Importance: Low Status: In Progress ** Affects: linux (Ubuntu Impish) Importance: Low Status: In Progress ** Affects: linux (Ubuntu Jammy) Importance: Low Assignee: Hui Wang (hui.wang) Status: In Progress ** Changed in: linux (Ubuntu) Importance: Undecided => Low ** Also affects: linux (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Low Assignee: Hui Wang (hui.wang) Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Impish) Importance: Undecided => Low ** Changed in: linux (Ubuntu Hirsute) Importance: Undecided => Low ** Changed in: linux (Ubuntu Focal) Importance: Undecided => Low ** Changed in: linux (Ubuntu Focal) Status: New => In Progress ** Changed in: linux (Ubuntu Hirsute) Status: New => In Progress ** Changed in: linux (Ubuntu Impish) Status: New => In Progress ** Changed in: linux (Ubuntu Jammy) Status: New => In Progress -- 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/1950536 Title: keyboard not working on Medion notebook s17 series Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: In Progress Status in linux source package in Hirsute: In Progress Status in linux source package in Impish: In Progress Status in linux source package in Jammy: In Progress Bug description: [Impact] The keyboard of some medion laptops can't work under Linux. [Fix] Backport a upstream patch, after applying the patch, the keyboard will skip the irq override from the acpi resource layer, and the keyboard could work normally. [Test] Booting the patched kernel, use the keyboard to do the input. [Where problems could occur] The patch will skip the irq override based on the DMI info, so if a medion laptop which has the same DMI info and the irq 1 needs to be overriden, this patch will introduce regression on the machine, but this possibility is very low. If this happens, we will consider to add more DMI match info in the table. This is a bug similar to #1909814. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950536/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1950410] Re: PS4 DualShock wireless controller connected/disconnected/unusable
** Summary changed: - 21.10-Bad wireless(bluetooth) gamepad integration. Connected/Disconnected/unusable + PS4 DualShock wireless controller connected/disconnected/unusable ** Changed in: ubuntu-mate Status: Incomplete => New ** Changed in: blueman (Ubuntu) Status: Incomplete => New ** Changed in: bluez (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1950410 Title: PS4 DualShock wireless controller connected/disconnected/unusable Status in Ubuntu MATE: New Status in blueman package in Ubuntu: New Status in bluez package in Ubuntu: New Bug description: Using a laptop running 21.10-latest, using a Sony Wireless Controller Model CUH-ZCT2U (The PS4 model), it seems impossible to connect via bluetooth to my laptop. Even though both hcitool & bluetooth manager are able to see the device, bonus mission bluetooth devices can also connect to it, but this is fairly short as it automatically disconnects. Here is what dmesg had to say about this. ``` [ 2479.109487] sony 0005:054C:09CC.0002: unknown main item tag 0x0 [ 2479.123654] input: Wireless Controller Touchpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:5/0005:054C:09CC.0002/input/input28 [ 2479.124094] input: Wireless Controller Motion Sensors as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:5/0005:054C:09CC.0002/input/input29 [ 2479.124676] input: Wireless Controller as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:5/0005:054C:09CC.0002/input/input27 [ 2479.125046] sony 0005:054C:09CC.0002: input,hidraw1: BLUETOOTH HID v81.00 Gamepad [Wireless Controller] on 9c:b6:d0:8f:c1:70 [ 2490.957043] sony 0005:054C:09CC.0003: unknown main item tag 0x0 [ 2490.971080] input: Wireless Controller Touchpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:4/0005:054C:09CC.0003/input/input31 [ 2490.971525] input: Wireless Controller Motion Sensors as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:4/0005:054C:09CC.0003/input/input32 [ 2490.972397] input: Wireless Controller as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:4/0005:054C:09CC.0003/input/input30 [ 2490.973740] sony 0005:054C:09CC.0003: input,hidraw1: BLUETOOTH HID v81.00 Gamepad [Wireless Controller] on 9c:b6:d0:8f:c1:70 [ 2498.688287] sony 0005:054C:09CC.0004: unknown main item tag 0x0 [ 2498.699789] input: Wireless Controller Touchpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:5/0005:054C:09CC.0004/input/input34 [ 2498.700142] input: Wireless Controller Motion Sensors as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:5/0005:054C:09CC.0004/input/input35 [ 2498.700962] input: Wireless Controller as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:5/0005:054C:09CC.0004/input/input33 [ 2498.701415] sony 0005:054C:09CC.0004: input,hidraw1: BLUETOOTH HID v81.00 Gamepad [Wireless Controller] on 9c:b6:d0:8f:c1:70 [ 2511.533433] sony 0005:054C:09CC.0005: unknown main item tag 0x0 [ 2511.543132] input: Wireless Controller Touchpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:6/0005:054C:09CC.0005/input/input37 [ 2511.543793] input: Wireless Controller Motion Sensors as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:6/0005:054C:09CC.0005/input/input38 [ 2511.544577] input: Wireless Controller as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:6/0005:054C:09CC.0005/input/input36 [ 2511.545359] sony 0005:054C:09CC.0005: input,hidraw1: BLUETOOTH HID v81.00 Gamepad [Wireless Controller] on 9c:b6:d0:8f:c1:70 [ 2517.758693] sony 0005:054C:09CC.0006: unknown main item tag 0x0 [ 2517.766837] input: Wireless Controller Touchpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:7/0005:054C:09CC.0006/input/input40 [ 2517.767834] input: Wireless Controller Motion Sensors as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:7/0005:054C:09CC.0006/input/input41 [ 2517.768642] input: Wireless Controller as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:7/0005:054C:09CC.0006/input/input39 [ 2517.769168] sony 0005:054C:09CC.0006: input,hidraw1: BLUETOOTH HID v81.00 Gamepad [Wireless Controller] on 9c:b6:d0:8f:c1:70 [ 2522.932282] sony 0005:054C:09CC.0007: unknown main item tag 0x0 [ 2522.947350] input: Wireless Controller Touchpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:8/0005:054C:09CC.0007/input/input43 [ 2522.947965] input: Wireless Controller Motion Sensors as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:8/0005:054C:09CC.0007/input/input44 [
[Kernel-packages] [Bug 1950487] [NEW] screen flickering
You have been subscribed to a public bug: The problem is, when i start working on my pc the screen start flickering goes from black to normal, it's a matter of graphic card(nvidia) but i failed to solve it, any suggestion: *-display UNCLAIMED description: 3D controller product: GM107M [GeForce GTX 960M] vendor: NVIDIA Corporation physical id: 0 bus info: pci@:01:00.0 version: a2 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list configuration: latency=0 resources: memory:d000-d0ff memory:a000-afff memory:b000-b1ff ioport:4000(size=128) memory:b200-b207 *-display description: VGA compatible controller product: 4th Gen Core Processor Integrated Graphics Controller vendor: Intel Corporation physical id: 2 bus info: pci@:00:02.0 version: 06 width: 64 bits clock: 33MHz capabilities: msi pm vga_controller bus_master cap_list configuration: driver=i915 latency=0 resources: irq:37 memory:d100-d13f memory:c000-cfff ioport:5000(size=64) memory:c-d ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: xorg 1:7.7+22ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18 Uname: Linux 5.13.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Nov 10 17:14:48 2021 DistUpgraded: Fresh install DistroCodename: impish DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Lenovo 4th Gen Core Processor Integrated Graphics Controller [17aa:3978] Subsystem: Lenovo GM107M [GeForce GTX 960M] [17aa:3978] InstallationDate: Installed on 2021-11-10 (0 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: LENOVO 20378 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-21-generic root=UUID=eb605582-0819-4c08-a72a-63c9558e8612 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/12/2015 dmi.bios.release: 3.43 dmi.bios.vendor: LENOVO dmi.bios.version: 9ECN43WW(V3.03) dmi.board.asset.tag: 31900058WIN dmi.board.name: Lenovo Y50-70 dmi.board.vendor: LENOVO dmi.board.version: 31900058WIN dmi.chassis.asset.tag: 31900058WIN dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Y50-70 dmi.ec.firmware.release: 3.43 dmi.modalias: dmi:bvnLENOVO:bvr9ECN43WW(V3.03):bd08/12/2015:br3.43:efr3.43:svnLENOVO:pn20378:pvrLenovoY50-70:rvnLENOVO:rnLenovoY50-70:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoY50-70:skuLENOVO_MT_20378_BU_idea_FM_LenovoY50-70: dmi.product.family: IDEAPAD dmi.product.name: 20378 dmi.product.sku: LENOVO_MT_20378_BU_idea_FM_Lenovo Y50-70 dmi.product.version: Lenovo Y50-70 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1 ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug corruption impish ubuntu wayland-session -- screen flickering https://bugs.launchpad.net/bugs/1950487 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 1950042] Re: Let NVMe with HMB use native power control again
Verified pass on focal that the system can enter PC10 and SLP_S0. On 5.14.0-1007-oem: turbostat --quiet -S --show Pkg%pc2,Pkg%pc3,Pk%pc10,CPU%LPI,SYS%LPI rtcwake -m freeze -s 15 | tee s0ix-diag.txt rtcwake: assuming RTC uses UTC ... rtcwake: wakeup from "freeze" using /dev/rtc0 at Thu Nov 11 01:39:29 2021 16.659672 sec Pkg%pc2 Pkg%pc3 Pk%pc10 CPU%LPI SYS%LPI 1.5986.66 0.000.000.00 On 5.14.0-1008-oem (proposed): turbostat --quiet -S --show Pkg%pc2,Pkg%pc3,Pk%pc10,CPU%LPI,SYS%LPI rtcwake -m freeze -s 15 | tee s0ix-diag.txt rtcwake: assuming RTC uses UTC ... rtcwake: wakeup from "freeze" using /dev/rtc0 at Thu Nov 11 01:53:24 2021 16.661935 sec Pkg%pc2 Pkg%pc3 Pk%pc10 CPU%LPI SYS%LPI 0.821.9686.22 87.40 85.27 ** 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-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1950042 Title: Let NVMe with HMB use native power control again Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.13 package in Ubuntu: Invalid 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.10 source package in Focal: Confirmed Status in linux-oem-5.13 source package in Focal: Confirmed Status in linux-oem-5.14 source package in Focal: Fix Committed Status in linux source package in Hirsute: Confirmed Status in linux-oem-5.10 source package in Hirsute: Invalid Status in linux-oem-5.13 source package in Hirsute: Invalid Status in linux-oem-5.14 source package in Hirsute: Invalid Status in linux source package in Impish: Confirmed Status in linux-oem-5.10 source package in Impish: Invalid Status in linux-oem-5.13 source package in Impish: Invalid Status in linux-oem-5.14 source package in Impish: Invalid Bug description: Impact] NVMe with HMB may still do DMA during suspend, so there was a commit that put the NVMe to PCI D3 during suspend to prevent DMA activities. However, this makes them consumes much more power because modern NVMe requires to stay at PCI D0 to make its natve power control work. [Fix] Instead of put the NVMe to PCI D3 and reset it afterward, simply disable HMB and re-enable HMB, for suspend and resume respectively. [Test] On affected system, Intel SoC can only reach PC3 during suspend. With the SRU applied, the Intel SoC can reach PC10 and SLP_S0 and use significant less power. [Where problems could occur] The original approach, i.e. disable NVMe and put it to PCI D3 to prevent DMA activies, was just a precaution. There wasn't any case that indicates it happens in practice. This is a different approach to the same problem, which is a theoretical problem. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1950042/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1922334] Re: External monitor does not wake up on Titan Ridge laptops when docked (9500, TB16)
@Georgi, could try these 1. prime-select intel and reboot, check the issue. 2. prime-select nvidia and reboot, check the issue. please remove "i915.enable_psr=0 i915.modeset=1 nvidia_drm.modeset=1" from cmdline -- 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/1922334 Title: External monitor does not wake up on Titan Ridge laptops when docked (9500, TB16) Status in Dell Sputnik: New Status in linux package in Ubuntu: In Progress Status in linux-meta-oem-5.6 package in Ubuntu: New Status in linux-oem-5.10 package in Ubuntu: New Status in linux-oem-5.13 package in Ubuntu: New Status in linux-oem-5.14 package in Ubuntu: New Bug description: I've recently upgraded my workhorse from XPS 9560 (2016) to a newer generation XPS 9500 (2020) and ran into several things that feel like regressions, but are probably related to hardware changes. This is one of them. tl;dr: When using XPS 9500 with a TB16 dock and an external monitor (Benq EX2780Q) connected to the dock via USB-C to USB-C (DP alternate mode), most of the time the monitor fails to wake up after going blank. details: Simplest way to reproduce is for hit Super+L, wait for the monitor to properly go in standby, then type something in or move the mouse to wake it up. 8 times out of 10 it does not wake up when using XPS 9500. Most of the time this can be fixed by power cycling the monitor, however this has a seemingly random chance of triggering two other issues: 1. The system to lose sight of the monitor for a brief period of time, which sometimes causes it to hang with a black screen and needs some combination of restarting the monitor, the dock, and the laptop, because there is a separate USB issue making hot-plugging unusable. 2. The monitor itself gets stuck in a weird standby state where it stops reacting to button presses and I need to hold the power button a bit longer for it to sort of hard reset? Notably, it wakes up fine every time when using XPS 9560 or Precision 5520 in the same setup which I have been using for ages. This becomes particularly troublesome when screens go into short-lived standby during boot: after the Dell logo, after entering the LUKS password, after logging in. Each of these points has a chance of triggering the bug, because it looks like there is some sort of mode change and waking signal submission happening between them that triggers it. I had to disable screen timeout as a temporary workaround to be able to work on this system at all without having to play "monitor wake lottery" every time I go brew a cuppa. The workaround at boot time is to either re-roll the lottery, or boot with the dock connected and lid open, then close the lid and keep working from there. The dock, the monitor, all USB peripherals are the same in both cases - it's literally just the TB16 cable plugged into a different laptop. I have attempted 5.8 Ubuntu generic, 5.6 OEM (-20.04) and 5.10 OEM (-20.04b and -20.04-edge) kernels on the 9500 with same results. I have attempted disabling USB autosuspend via a GRUB kernel parameter to usbcore. I have attempted both NVidia and Intel GPUs. I have attempted playing with BIOS settings: wake on dell usb-c docks, disable early sign of life for both checkboxes, disabling SGX and SMM, checking all 3 boxes for Thunderbolt and switching off Thunderbolt security. None of these make a noticeable difference. Since it was fine with 9560, 5520 and a friend with a 9570 has no issues either, my gut feeling is that this is due to the upgrade from Alpine Ridge to a Titan Ridge Thunderbolt controller that happened in this generation - something wrong with the driver, or the firmware may have missed some of the "lessons learned" in Alpine Ridge and caused this regression. That would also make it applicable to 9300, which has a "developer edition" option under Project Sputnik and several reports of the same problem scattered across the internet: https://www.dell.com/community/XPS/XPS-13-9300-with-WD19TB-External-display-not-coming-on-after/td-p/7676922 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1889342 (may be a duplicate, but for WD19TB dock on 9300, so may be slightly different too) https://www.reddit.com/r/linuxquestions/comments/ka0w2j/monitor_doesnt_wake_from_sleep/ etc etc. Those reports suggest high bandwidth usage sometimes affects it, so it's worth noting that my external monitor is a 1440p 144Hz one that uses tons of bandwidth indeed. The only hint in terms of logs seems to be this message in dmesg that I see when power cycling the monitor and getting back into the system: [ 250.777684] pcieport :09:04.0: pciehp: Slot(0-1): Card not present [ 250.777695] xhci_hcd :0b:00.0: can't change power state from D3cold to D0 (config space
[Kernel-packages] [Bug 1949245] Re: AMD ACP 6.x DMIC Supports
** 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-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1949245 Title: AMD ACP 6.x DMIC Supports Status in HWE Next: In Progress 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] AMD's Yellow carp platforms will have an updated ACP IP block (ACP 6.x) which will not work with existing ACP drivers. [Fix] Backport the new driver that is now in linux-next (to be in 5.16) [Test] This is requested by AMD. [Where problems could occur] Low risk. This is a stand-alone driver that does not affect others devices and platforms. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1949245/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1950013] Re: Add s0i3 RTC wake up for AMD systems
** 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-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1950013 Title: Add s0i3 RTC wake up for AMD systems Status in HWE Next: New 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] RTC based wakeup is not supported natively by the hardware for s0i3. [Fix] A firmware and driver updates were implemented. The driver passes wakeup time to SMU to to enable RTC from S0i3. Note this s0i3 RTC wake up also requires new firmware. The first patch is the prerequisite actual fix (patch 2 and 3). [Test] This is requested by AMD and tested by an AMD developer as below: Testing a suspend run with RTC for 15 seconds and then 30 seconds: ``` $ sudo rtcwake --seconds 15 -m mem rtcwake: assuming RTC uses UTC ... rtcwake: wakeup from "mem" using /dev/rtc0 at Fri Nov 5 02:31:45 2021 $ sudo rtcwake --seconds 30 -m mem rtcwake: assuming RTC uses UTC ... rtcwake: wakeup from "mem" using /dev/rtc0 at Fri Nov 5 02:33:13 2021 $ sudo cat /sys/kernel/debug/amd_pmc/s0ix_stats === S0ix statistics === S0ix Entry Time: 4793618285 S0ix Exit Time: 6209036738 Residency Time: 29487884 ``` Residency divided by 100 is 29.4 seconds. Reading idle mask works fine too. [Where problems could occur] Low risk. First patch only exports Idlemask value. The actual fix only affects a specific AMD CPU (CZN). To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1950013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1949245] Re: AMD ACP 6.x DMIC Supports
This bug is awaiting verification that the linux-oem-5.14/5.14.0-1008.8 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/1949245 Title: AMD ACP 6.x DMIC Supports Status in HWE Next: In Progress 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] AMD's Yellow carp platforms will have an updated ACP IP block (ACP 6.x) which will not work with existing ACP drivers. [Fix] Backport the new driver that is now in linux-next (to be in 5.16) [Test] This is requested by AMD. [Where problems could occur] Low risk. This is a stand-alone driver that does not affect others devices and platforms. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1949245/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1950042] Re: Let NVMe with HMB use native power control again
This bug is awaiting verification that the linux-oem-5.14/5.14.0-1008.8 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/1950042 Title: Let NVMe with HMB use native power control again Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.13 package in Ubuntu: Invalid 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.10 source package in Focal: Confirmed Status in linux-oem-5.13 source package in Focal: Confirmed Status in linux-oem-5.14 source package in Focal: Fix Committed Status in linux source package in Hirsute: Confirmed Status in linux-oem-5.10 source package in Hirsute: Invalid Status in linux-oem-5.13 source package in Hirsute: Invalid Status in linux-oem-5.14 source package in Hirsute: Invalid Status in linux source package in Impish: Confirmed Status in linux-oem-5.10 source package in Impish: Invalid Status in linux-oem-5.13 source package in Impish: Invalid Status in linux-oem-5.14 source package in Impish: Invalid Bug description: Impact] NVMe with HMB may still do DMA during suspend, so there was a commit that put the NVMe to PCI D3 during suspend to prevent DMA activities. However, this makes them consumes much more power because modern NVMe requires to stay at PCI D0 to make its natve power control work. [Fix] Instead of put the NVMe to PCI D3 and reset it afterward, simply disable HMB and re-enable HMB, for suspend and resume respectively. [Test] On affected system, Intel SoC can only reach PC3 during suspend. With the SRU applied, the Intel SoC can reach PC10 and SLP_S0 and use significant less power. [Where problems could occur] The original approach, i.e. disable NVMe and put it to PCI D3 to prevent DMA activies, was just a precaution. There wasn't any case that indicates it happens in practice. This is a different approach to the same problem, which is a theoretical problem. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1950042/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1950013] Re: Add s0i3 RTC wake up for AMD systems
This bug is awaiting verification that the linux-oem-5.14/5.14.0-1008.8 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/1950013 Title: Add s0i3 RTC wake up for AMD systems Status in HWE Next: New 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] RTC based wakeup is not supported natively by the hardware for s0i3. [Fix] A firmware and driver updates were implemented. The driver passes wakeup time to SMU to to enable RTC from S0i3. Note this s0i3 RTC wake up also requires new firmware. The first patch is the prerequisite actual fix (patch 2 and 3). [Test] This is requested by AMD and tested by an AMD developer as below: Testing a suspend run with RTC for 15 seconds and then 30 seconds: ``` $ sudo rtcwake --seconds 15 -m mem rtcwake: assuming RTC uses UTC ... rtcwake: wakeup from "mem" using /dev/rtc0 at Fri Nov 5 02:31:45 2021 $ sudo rtcwake --seconds 30 -m mem rtcwake: assuming RTC uses UTC ... rtcwake: wakeup from "mem" using /dev/rtc0 at Fri Nov 5 02:33:13 2021 $ sudo cat /sys/kernel/debug/amd_pmc/s0ix_stats === S0ix statistics === S0ix Entry Time: 4793618285 S0ix Exit Time: 6209036738 Residency Time: 29487884 ``` Residency divided by 100 is 29.4 seconds. Reading idle mask works fine too. [Where problems could occur] Low risk. First patch only exports Idlemask value. The actual fix only affects a specific AMD CPU (CZN). To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1950013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1945565] Re: [SRU] Revert amdgpu/renoir firmware
Here's the submission to stable: https://lore.kernel.org/stable/2020232554.2190-1-mario.limoncie...@amd.com/ -- 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/1945565 Title: [SRU] Revert amdgpu/renoir firmware Status in OEM Priority Project: Fix Committed Status in linux-firmware package in Ubuntu: Won't Fix Status in linux-firmware source package in Focal: Fix Released Bug description: [Impact] The USB-type-C port is useless when uplug the USB-type-C <-> DP/HDMI/VGA Dongle after the system resumed from S3. [Fix] Revert below change, this issue is gone. commit a543b9c1bfd12e60d962acd48108234481a8581f Author: Alex Deucher Date: Thu Jul 1 12:23:11 2021 +0800 amdgpu: update renoir firmware from 21.20 BugLink: https://bugs.launchpad.net/bugs/1934014 From internal git commit: 8b05e03570818d047d7ea0a7388c89c4192fd20b Signed-off-by: Alex Deucher Signed-off-by: Josh Boyer (backported from commit 56ef642160203f8be7e1334feca4a76852c74bc0) [khfeng: Squashed multiple updates into one commit] Signed-off-by: Kai-Heng Feng Signed-off-by: Timo Aaltonen [Test] Verify S3 on renoir's platforms. [Where problems could occur] Renoir based systems can't resume from s2idle. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1945565/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1950525] [NEW] Touchpad is not detected by Ubuntu in "Lenovo V15 - IIL" after OS install
Public bug reported: After install Ubuntu 20.04 in a Lenovo V15-IIL the touchpad is not detected. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.11.0-40-generic 5.11.0-40.44~20.04.2 ProcVersionSignature: Ubuntu 5.11.0-40.44~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Nov 10 18:26:15 2021 InstallationDate: Installed on 2021-10-25 (16 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: linux-signed-hwe-5.11 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe-5.11 (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-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1950525 Title: Touchpad is not detected by Ubuntu in "Lenovo V15 - IIL" after OS install Status in linux-signed-hwe-5.11 package in Ubuntu: New Bug description: After install Ubuntu 20.04 in a Lenovo V15-IIL the touchpad is not detected. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.11.0-40-generic 5.11.0-40.44~20.04.2 ProcVersionSignature: Ubuntu 5.11.0-40.44~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Nov 10 18:26:15 2021 InstallationDate: Installed on 2021-10-25 (16 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: linux-signed-hwe-5.11 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.11/+bug/1950525/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1945531] Re: kernel panic at boot
This bug is on the verge of being fixed. See: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945590 -- 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/1945531 Title: kernel panic at boot Status in Ubuntu MATE: Confirmed Status in linux package in Ubuntu: Incomplete Bug description: On do-release-upgrade to Impish with the 5.13 kernel the boot messages stop scrolling at: fb0: switching to amdgpudrmfb from EFI VGA The system may be continuing to boot but the screen stops updating. The 5.11 and 5.12 kernels both boot correctly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1945531/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1950410] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1950410/+attachment/5539764/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1950410 Title: 21.10-Bad wireless(bluetooth) gamepad integration. Connected/Disconnected/unusable Status in Ubuntu MATE: Incomplete Status in blueman package in Ubuntu: Incomplete Status in bluez package in Ubuntu: Incomplete Bug description: Using a laptop running 21.10-latest, using a Sony Wireless Controller Model CUH-ZCT2U (The PS4 model), it seems impossible to connect via bluetooth to my laptop. Even though both hcitool & bluetooth manager are able to see the device, bonus mission bluetooth devices can also connect to it, but this is fairly short as it automatically disconnects. Here is what dmesg had to say about this. ``` [ 2479.109487] sony 0005:054C:09CC.0002: unknown main item tag 0x0 [ 2479.123654] input: Wireless Controller Touchpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:5/0005:054C:09CC.0002/input/input28 [ 2479.124094] input: Wireless Controller Motion Sensors as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:5/0005:054C:09CC.0002/input/input29 [ 2479.124676] input: Wireless Controller as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:5/0005:054C:09CC.0002/input/input27 [ 2479.125046] sony 0005:054C:09CC.0002: input,hidraw1: BLUETOOTH HID v81.00 Gamepad [Wireless Controller] on 9c:b6:d0:8f:c1:70 [ 2490.957043] sony 0005:054C:09CC.0003: unknown main item tag 0x0 [ 2490.971080] input: Wireless Controller Touchpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:4/0005:054C:09CC.0003/input/input31 [ 2490.971525] input: Wireless Controller Motion Sensors as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:4/0005:054C:09CC.0003/input/input32 [ 2490.972397] input: Wireless Controller as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:4/0005:054C:09CC.0003/input/input30 [ 2490.973740] sony 0005:054C:09CC.0003: input,hidraw1: BLUETOOTH HID v81.00 Gamepad [Wireless Controller] on 9c:b6:d0:8f:c1:70 [ 2498.688287] sony 0005:054C:09CC.0004: unknown main item tag 0x0 [ 2498.699789] input: Wireless Controller Touchpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:5/0005:054C:09CC.0004/input/input34 [ 2498.700142] input: Wireless Controller Motion Sensors as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:5/0005:054C:09CC.0004/input/input35 [ 2498.700962] input: Wireless Controller as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:5/0005:054C:09CC.0004/input/input33 [ 2498.701415] sony 0005:054C:09CC.0004: input,hidraw1: BLUETOOTH HID v81.00 Gamepad [Wireless Controller] on 9c:b6:d0:8f:c1:70 [ 2511.533433] sony 0005:054C:09CC.0005: unknown main item tag 0x0 [ 2511.543132] input: Wireless Controller Touchpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:6/0005:054C:09CC.0005/input/input37 [ 2511.543793] input: Wireless Controller Motion Sensors as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:6/0005:054C:09CC.0005/input/input38 [ 2511.544577] input: Wireless Controller as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:6/0005:054C:09CC.0005/input/input36 [ 2511.545359] sony 0005:054C:09CC.0005: input,hidraw1: BLUETOOTH HID v81.00 Gamepad [Wireless Controller] on 9c:b6:d0:8f:c1:70 [ 2517.758693] sony 0005:054C:09CC.0006: unknown main item tag 0x0 [ 2517.766837] input: Wireless Controller Touchpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:7/0005:054C:09CC.0006/input/input40 [ 2517.767834] input: Wireless Controller Motion Sensors as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:7/0005:054C:09CC.0006/input/input41 [ 2517.768642] input: Wireless Controller as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:7/0005:054C:09CC.0006/input/input39 [ 2517.769168] sony 0005:054C:09CC.0006: input,hidraw1: BLUETOOTH HID v81.00 Gamepad [Wireless Controller] on 9c:b6:d0:8f:c1:70 [ 2522.932282] sony 0005:054C:09CC.0007: unknown main item tag 0x0 [ 2522.947350] input: Wireless Controller Touchpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:8/0005:054C:09CC.0007/input/input43 [ 2522.947965] input: Wireless Controller Motion Sensors as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:8/0005:054C:09CC.0007/input/input44 [ 2522.948593] input: Wireless Controller as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:8/0005:054C:09CC.0007/input/input42 [ 2522.951519] sony
[Kernel-packages] [Bug 1950410] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1950410/+attachment/5539763/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1950410 Title: 21.10-Bad wireless(bluetooth) gamepad integration. Connected/Disconnected/unusable Status in Ubuntu MATE: Incomplete Status in blueman package in Ubuntu: Incomplete Status in bluez package in Ubuntu: Incomplete Bug description: Using a laptop running 21.10-latest, using a Sony Wireless Controller Model CUH-ZCT2U (The PS4 model), it seems impossible to connect via bluetooth to my laptop. Even though both hcitool & bluetooth manager are able to see the device, bonus mission bluetooth devices can also connect to it, but this is fairly short as it automatically disconnects. Here is what dmesg had to say about this. ``` [ 2479.109487] sony 0005:054C:09CC.0002: unknown main item tag 0x0 [ 2479.123654] input: Wireless Controller Touchpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:5/0005:054C:09CC.0002/input/input28 [ 2479.124094] input: Wireless Controller Motion Sensors as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:5/0005:054C:09CC.0002/input/input29 [ 2479.124676] input: Wireless Controller as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:5/0005:054C:09CC.0002/input/input27 [ 2479.125046] sony 0005:054C:09CC.0002: input,hidraw1: BLUETOOTH HID v81.00 Gamepad [Wireless Controller] on 9c:b6:d0:8f:c1:70 [ 2490.957043] sony 0005:054C:09CC.0003: unknown main item tag 0x0 [ 2490.971080] input: Wireless Controller Touchpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:4/0005:054C:09CC.0003/input/input31 [ 2490.971525] input: Wireless Controller Motion Sensors as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:4/0005:054C:09CC.0003/input/input32 [ 2490.972397] input: Wireless Controller as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:4/0005:054C:09CC.0003/input/input30 [ 2490.973740] sony 0005:054C:09CC.0003: input,hidraw1: BLUETOOTH HID v81.00 Gamepad [Wireless Controller] on 9c:b6:d0:8f:c1:70 [ 2498.688287] sony 0005:054C:09CC.0004: unknown main item tag 0x0 [ 2498.699789] input: Wireless Controller Touchpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:5/0005:054C:09CC.0004/input/input34 [ 2498.700142] input: Wireless Controller Motion Sensors as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:5/0005:054C:09CC.0004/input/input35 [ 2498.700962] input: Wireless Controller as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:5/0005:054C:09CC.0004/input/input33 [ 2498.701415] sony 0005:054C:09CC.0004: input,hidraw1: BLUETOOTH HID v81.00 Gamepad [Wireless Controller] on 9c:b6:d0:8f:c1:70 [ 2511.533433] sony 0005:054C:09CC.0005: unknown main item tag 0x0 [ 2511.543132] input: Wireless Controller Touchpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:6/0005:054C:09CC.0005/input/input37 [ 2511.543793] input: Wireless Controller Motion Sensors as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:6/0005:054C:09CC.0005/input/input38 [ 2511.544577] input: Wireless Controller as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:6/0005:054C:09CC.0005/input/input36 [ 2511.545359] sony 0005:054C:09CC.0005: input,hidraw1: BLUETOOTH HID v81.00 Gamepad [Wireless Controller] on 9c:b6:d0:8f:c1:70 [ 2517.758693] sony 0005:054C:09CC.0006: unknown main item tag 0x0 [ 2517.766837] input: Wireless Controller Touchpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:7/0005:054C:09CC.0006/input/input40 [ 2517.767834] input: Wireless Controller Motion Sensors as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:7/0005:054C:09CC.0006/input/input41 [ 2517.768642] input: Wireless Controller as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:7/0005:054C:09CC.0006/input/input39 [ 2517.769168] sony 0005:054C:09CC.0006: input,hidraw1: BLUETOOTH HID v81.00 Gamepad [Wireless Controller] on 9c:b6:d0:8f:c1:70 [ 2522.932282] sony 0005:054C:09CC.0007: unknown main item tag 0x0 [ 2522.947350] input: Wireless Controller Touchpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:8/0005:054C:09CC.0007/input/input43 [ 2522.947965] input: Wireless Controller Motion Sensors as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:8/0005:054C:09CC.0007/input/input44 [ 2522.948593] input: Wireless Controller as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:8/0005:054C:09CC.0007/input/input42 [ 2522.951519] sony
[Kernel-packages] [Bug 1950410] Re: 21.10-Bad wireless(bluetooth) gamepad integration. Connected/Disconnected/unusable
apport information ** Tags added: apport-collected ** Description changed: Using a laptop running 21.10-latest, using a Sony Wireless Controller Model CUH-ZCT2U (The PS4 model), it seems impossible to connect via bluetooth to my laptop. Even though both hcitool & bluetooth manager are able to see the device, bonus mission bluetooth devices can also connect to it, but this is fairly short as it automatically disconnects. Here is what dmesg had to say about this. ``` [ 2479.109487] sony 0005:054C:09CC.0002: unknown main item tag 0x0 [ 2479.123654] input: Wireless Controller Touchpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:5/0005:054C:09CC.0002/input/input28 [ 2479.124094] input: Wireless Controller Motion Sensors as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:5/0005:054C:09CC.0002/input/input29 [ 2479.124676] input: Wireless Controller as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:5/0005:054C:09CC.0002/input/input27 [ 2479.125046] sony 0005:054C:09CC.0002: input,hidraw1: BLUETOOTH HID v81.00 Gamepad [Wireless Controller] on 9c:b6:d0:8f:c1:70 [ 2490.957043] sony 0005:054C:09CC.0003: unknown main item tag 0x0 [ 2490.971080] input: Wireless Controller Touchpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:4/0005:054C:09CC.0003/input/input31 [ 2490.971525] input: Wireless Controller Motion Sensors as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:4/0005:054C:09CC.0003/input/input32 [ 2490.972397] input: Wireless Controller as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:4/0005:054C:09CC.0003/input/input30 [ 2490.973740] sony 0005:054C:09CC.0003: input,hidraw1: BLUETOOTH HID v81.00 Gamepad [Wireless Controller] on 9c:b6:d0:8f:c1:70 [ 2498.688287] sony 0005:054C:09CC.0004: unknown main item tag 0x0 [ 2498.699789] input: Wireless Controller Touchpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:5/0005:054C:09CC.0004/input/input34 [ 2498.700142] input: Wireless Controller Motion Sensors as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:5/0005:054C:09CC.0004/input/input35 [ 2498.700962] input: Wireless Controller as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:5/0005:054C:09CC.0004/input/input33 [ 2498.701415] sony 0005:054C:09CC.0004: input,hidraw1: BLUETOOTH HID v81.00 Gamepad [Wireless Controller] on 9c:b6:d0:8f:c1:70 [ 2511.533433] sony 0005:054C:09CC.0005: unknown main item tag 0x0 [ 2511.543132] input: Wireless Controller Touchpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:6/0005:054C:09CC.0005/input/input37 [ 2511.543793] input: Wireless Controller Motion Sensors as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:6/0005:054C:09CC.0005/input/input38 [ 2511.544577] input: Wireless Controller as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:6/0005:054C:09CC.0005/input/input36 [ 2511.545359] sony 0005:054C:09CC.0005: input,hidraw1: BLUETOOTH HID v81.00 Gamepad [Wireless Controller] on 9c:b6:d0:8f:c1:70 [ 2517.758693] sony 0005:054C:09CC.0006: unknown main item tag 0x0 [ 2517.766837] input: Wireless Controller Touchpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:7/0005:054C:09CC.0006/input/input40 [ 2517.767834] input: Wireless Controller Motion Sensors as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:7/0005:054C:09CC.0006/input/input41 [ 2517.768642] input: Wireless Controller as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:7/0005:054C:09CC.0006/input/input39 [ 2517.769168] sony 0005:054C:09CC.0006: input,hidraw1: BLUETOOTH HID v81.00 Gamepad [Wireless Controller] on 9c:b6:d0:8f:c1:70 [ 2522.932282] sony 0005:054C:09CC.0007: unknown main item tag 0x0 [ 2522.947350] input: Wireless Controller Touchpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:8/0005:054C:09CC.0007/input/input43 [ 2522.947965] input: Wireless Controller Motion Sensors as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:8/0005:054C:09CC.0007/input/input44 [ 2522.948593] input: Wireless Controller as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:8/0005:054C:09CC.0007/input/input42 [ 2522.951519] sony 0005:054C:09CC.0007: input,hidraw1: BLUETOOTH HID v81.00 Gamepad [Wireless Controller] on 9c:b6:d0:8f:c1:70 ``` - When I plug the same controller via USB it's not only automatically - recognized but I can also use the track mouse on the controller just - fine. + When I plug the same controller via USB it's not only automatically recognized but I can also use the track mouse on the controller just fine. + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu71 + Architecture:
[Kernel-packages] [Bug 1950492] 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 1950492 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/1950492 Title: wifi stops working on Dell XPS 9310 Status in linux package in Ubuntu: Incomplete Bug description: After updating to linux 5.13.0-22 wifi stops working on Dell XPS 9310 with QCA6390. There are two errors in dmesg: 1. mhi: qcom_mhi_qrtr mhi0_IPCR: invalid ipcrouter packet 2. ath11k ath11k_pci :72:00.0: failed to register fw indication: -110 ath11k_pci :72:00.0: failed to send qmi firmware indication: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950492/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1950492] Re: wifi stops working on Dell XPS 9310
** 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/1950492 Title: wifi stops working on Dell XPS 9310 Status in linux package in Ubuntu: New Bug description: After updating to linux 5.13.0-22 wifi stops working on Dell XPS 9310 with QCA6390. There are two errors in dmesg: 1. mhi: qcom_mhi_qrtr mhi0_IPCR: invalid ipcrouter packet 2. ath11k ath11k_pci :72:00.0: failed to register fw indication: -110 ath11k_pci :72:00.0: failed to send qmi firmware indication: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950492/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1950516] [NEW] Hirsute update: upstream stable patchset 2021-11-10
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2021-11-10 Ported from the following upstream stable releases: v5.10.71, v5.14.10 from git://git.kernel.org/ tty: Fix out-of-bound vmalloc access in imageblit cpufreq: schedutil: Use kobject release() method to free sugov_tunables scsi: qla2xxx: Changes to support kdump kernel for NVMe BFS cpufreq: schedutil: Destroy mutex before kobject_put() frees the memory usb: cdns3: fix race condition before setting doorbell ACPI: NFIT: Use fallback node id when numa info in NFIT table is incorrect fs-verity: fix signed integer overflow with i_size near S64_MAX hwmon: (tmp421) handle I2C errors hwmon: (w83793) Fix NULL pointer dereference by removing unnecessary structure field hwmon: (w83792d) Fix NULL pointer dereference by removing unnecessary structure field hwmon: (w83791d) Fix NULL pointer dereference by removing unnecessary structure field gpio: pca953x: do not ignore i2c errors scsi: ufs: Fix illegal offset in UPIU event trace mac80211: fix use-after-free in CCMP/GCMP RX x86/kvmclock: Move this_cpu_pvti into kvmclock.h KVM: x86: Fix stack-out-of-bounds memory access from ioapic_write_indirect() KVM: x86: nSVM: don't copy virt_ext from vmcb12 KVM: nVMX: Filter out all unsupported controls when eVMCS was activated media: ir_toy: prevent device from hanging during transmit RDMA/cma: Do not change route.addr.src_addr.ss_family drm/amd/display: Pass PCI deviceid into DC drm/amdgpu: correct initial cp_hqd_quantum for gfx9 ipvs: check that ip_vs_conn_tab_bits is between 8 and 20 bpf: Handle return value of BPF_PROG_TYPE_STRUCT_OPS prog IB/cma: Do not send IGMP leaves for sendonly Multicast groups RDMA/cma: Fix listener leak in rdma_cma_listen_on_all() failure bpf, mips: Validate conditional branch offsets hwmon: (mlxreg-fan) Return non-zero value when fan current state is enforced from sysfs mac80211: Fix ieee80211_amsdu_aggregate frag_tail bug mac80211: limit injected vht mcs/nss in ieee80211_parse_tx_radiotap mac80211: mesh: fix potentially unaligned access mac80211-hwsim: fix late beacon hrtimer handling sctp: break out if skb_header_pointer returns NULL in sctp_rcv_ootb mptcp: don't return sockets in foreign netns hwmon: (tmp421) report /PVLD condition as fault hwmon: (tmp421) fix rounding for negative values net: enetc: fix the incorrect clearing of IF_MODE bits net: ipv4: Fix rtnexthop len when RTA_FLOW is present smsc95xx: fix stalled rx after link change drm/i915/request: fix early tracepoints dsa: mv88e6xxx: 6161: Use chip wide MAX MTU dsa: mv88e6xxx: Fix MTU definition dsa: mv88e6xxx: Include tagger overhead when setting MTU for DSA and CPU ports e100: fix length calculation in e100_get_regs_len e100: fix buffer overrun in e100_get_regs bpf: Exempt CAP_BPF from checks against bpf_jit_limit selftests, bpf: Fix makefile dependencies on libbpf selftests, bpf: test_lwt_ip_encap: Really disable rp_filter UBUNTU: [Config] updateconfigs for ks8851 modules net: ks8851: fix link error scsi: csiostor: Add module softdep on cxgb4 ixgbe: Fix NULL pointer dereference in ixgbe_xdp_setup net: hns3: do not allow call hns3_nic_net_open repeatedly net: hns3: fix mixed flag HCLGE_FLAG_MQPRIO_ENABLE and HCLGE_FLAG_DCB_ENABLE net: hns3: fix show wrong state when add existing uc mac address net: hns3: fix prototype warning net: hns3: reconstruct function hns3_self_test net: hns3: fix always enable rx vlan filter problem after selftest net: phy: bcm7xxx: Fixed indirect MMD operations net: sched: flower: protect fl_walk() with rcu af_unix: fix races in sk_peer_pid and sk_peer_cred accesses perf/x86/intel: Update event constraints for ICX hwmon: (pmbus/mp2975) Add missed POUT attribute for page 1 mp2975 controller nvme: add command id quirk for apple controllers elf: don't use MAP_FIXED_NOREPLACE for elf interpreter mappings debugfs: debugfs_create_file_size(): use IS_ERR to check for error ipack: ipoctal: fix stack information leak ipack: ipoctal: fix tty registration race ipack: ipoctal: fix tty-registration error handling ipack: ipoctal: fix missing allocation-failure check ipack: ipoctal: fix module reference leak ext4: fix loff_t overflow in ext4_max_bitmap_size() ext4: limit the number of blocks in one ADD_RANGE TLV ext4: fix reserved space counter leakage ext4: add error checking to ext4_ext_replay_set_iblocks() ext4: fix potential infinite loop in ext4_dx_readdir() HID: u2fzero: ignore incomplete packets without data net: udp: annotate data race around udp_sk(sk)->corkflag
[Kernel-packages] [Bug 1950492] [NEW] wifi stops working on Dell XPS 9310
You have been subscribed to a public bug: After updating to linux 5.13.0-22 wifi stops working on Dell XPS 9310 with QCA6390. There are two errors in dmesg: 1. mhi: qcom_mhi_qrtr mhi0_IPCR: invalid ipcrouter packet 2. ath11k ath11k_pci :72:00.0: failed to register fw indication: -110 ath11k_pci :72:00.0: failed to send qmi firmware indication: ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- wifi stops working on Dell XPS 9310 https://bugs.launchpad.net/bugs/1950492 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 1950515] [NEW] WiFi Killer AX500s DBS stopped working in kernel 5.13.0-21-generic on Dell XPS 13 9310 and others
Public bug reported: In the 5.13.0-21 kernel, the device fails: $ lshw -c network *-network description: Network controller product: QCA6390 Wireless Network Adapter [AX500-DBS (2x2)] vendor: Qualcomm physical id: 0 bus info: pci@:72:00.0 version: 01 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list configuration: driver=ath11k_pci latency=0 resources: irq:182 memory:a250-a25f $ lspci | grep Qualcomm 72:00.0 Network controller: Qualcomm QCA6390 Wireless Network Adapter [AX500-DBS (2x2)] (rev 01) $ sudo modprobe ath11k_pci $ sudo dmesg | grep ath [4.611544] ath11k_pci :72:00.0: BAR 0: assigned [mem 0xa250-0xa25f 64bit] [4.611573] ath11k_pci :72:00.0: enabling device ( -> 0002) [4.612103] ath11k_pci :72:00.0: qca6390 hw2.0 [ 10.337672] ath11k_pci :72:00.0: failed to register fw indication: -110 [ 10.337692] ath11k_pci :72:00.0: failed to send qmi firmware indication: -110 [ 39.931711] ath11k_pci :72:00.0: link down error during global reset [ 45.574642] ath11k_pci :72:00.0: BAR 0: assigned [mem 0xa250-0xa25f 64bit] [ 45.575668] ath11k_pci :72:00.0: qca6390 hw2.0 [ 45.630047] ath11k_pci :72:00.0: failed to set pcie link register 0x01e0c0ac: 0x != 0x0010 [ 45.630054] ath11k_pci :72:00.0: failed to set sysclk: -110 [ 45.650253] ath11k_pci :72:00.0: link down error during global reset $ rfkill list all 0: hci0: Bluetooth Soft blocked: no Hard blocked: no In the 5.13.0-20 kernel, the device works: $ sudo dmesg | grep ath [ 4.804410] ath11k_pci :72:00.0: BAR 0: assigned [mem 0xa250-0xa25f 64bit] [ 4.804440] ath11k_pci :72:00.0: enabling device ( -> 0002) [ 4.808036] ath11k_pci :72:00.0: qca6390 hw2.0 [ 5.085678] ath11k_pci :72:00.0: chip_id 0x0 chip_family 0xb board_id 0xff soc_id 0x [ 5.085684] ath11k_pci :72:00.0: fw_version 0x101c06cc fw_build_timestamp 2020-06-24 19:50 fw_build_id [ 5.258202] ath11k_pci :72:00.0 wlp114s0: renamed from wlan0 [ 351.080712] ath11k_pci :72:00.0: link down error during global reset [ 356.511270] ath11k_pci :72:00.0: BAR 0: assigned [mem 0xa250-0xa25f 64bit] [ 356.512356] ath11k_pci :72:00.0: qca6390 hw2.0 ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-21-generic 5.13.0-21.21 ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18 Uname: Linux 5.13.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Nov 10 15:23:07 2021 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85 InstallationDate: Installed on 2021-05-04 (190 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Dell Inc. XPS 13 9310 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.13.0-21-generic root=UUID=676fbdd4-8566-4457-8530-0f412d28b48f ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.13.0-21-generic N/A linux-backports-modules-5.13.0-21-generic N/A linux-firmware 1.201.1 SourcePackage: linux UpgradeStatus: Upgraded to impish on 2021-10-19 (22 days ago) dmi.bios.date: 09/30/2021 dmi.bios.release: 3.2 dmi.bios.vendor: Dell Inc. dmi.bios.version: 3.2.0 dmi.board.name: 0MRT12 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr3.2.0:bd09/30/2021:br3.2:svnDellInc.:pnXPS139310:pvr:rvnDellInc.:rn0MRT12:rvrA00:cvnDellInc.:ct10:cvr:sku0991: dmi.product.family: XPS dmi.product.name: XPS 13 9310 dmi.product.sku: 0991 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug impish -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1950515 Title: WiFi Killer AX500s DBS stopped working in kernel 5.13.0-21-generic on Dell XPS 13 9310 and others Status in linux package in Ubuntu: Confirmed Bug description: In the 5.13.0-21 kernel, the device fails: $ lshw -c network *-network description: Network controller product: QCA6390 Wireless Network Adapter [AX500-DBS (2x2)] vendor: Qualcomm physical id: 0 bus info: pci@:72:00.0 version: 01 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master
[Kernel-packages] [Bug 1950515] 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/1950515 Title: WiFi Killer AX500s DBS stopped working in kernel 5.13.0-21-generic on Dell XPS 13 9310 and others Status in linux package in Ubuntu: Confirmed Bug description: In the 5.13.0-21 kernel, the device fails: $ lshw -c network *-network description: Network controller product: QCA6390 Wireless Network Adapter [AX500-DBS (2x2)] vendor: Qualcomm physical id: 0 bus info: pci@:72:00.0 version: 01 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list configuration: driver=ath11k_pci latency=0 resources: irq:182 memory:a250-a25f $ lspci | grep Qualcomm 72:00.0 Network controller: Qualcomm QCA6390 Wireless Network Adapter [AX500-DBS (2x2)] (rev 01) $ sudo modprobe ath11k_pci $ sudo dmesg | grep ath [4.611544] ath11k_pci :72:00.0: BAR 0: assigned [mem 0xa250-0xa25f 64bit] [4.611573] ath11k_pci :72:00.0: enabling device ( -> 0002) [4.612103] ath11k_pci :72:00.0: qca6390 hw2.0 [ 10.337672] ath11k_pci :72:00.0: failed to register fw indication: -110 [ 10.337692] ath11k_pci :72:00.0: failed to send qmi firmware indication: -110 [ 39.931711] ath11k_pci :72:00.0: link down error during global reset [ 45.574642] ath11k_pci :72:00.0: BAR 0: assigned [mem 0xa250-0xa25f 64bit] [ 45.575668] ath11k_pci :72:00.0: qca6390 hw2.0 [ 45.630047] ath11k_pci :72:00.0: failed to set pcie link register 0x01e0c0ac: 0x != 0x0010 [ 45.630054] ath11k_pci :72:00.0: failed to set sysclk: -110 [ 45.650253] ath11k_pci :72:00.0: link down error during global reset $ rfkill list all 0: hci0: Bluetooth Soft blocked: no Hard blocked: no In the 5.13.0-20 kernel, the device works: $ sudo dmesg | grep ath [ 4.804410] ath11k_pci :72:00.0: BAR 0: assigned [mem 0xa250-0xa25f 64bit] [ 4.804440] ath11k_pci :72:00.0: enabling device ( -> 0002) [ 4.808036] ath11k_pci :72:00.0: qca6390 hw2.0 [ 5.085678] ath11k_pci :72:00.0: chip_id 0x0 chip_family 0xb board_id 0xff soc_id 0x [ 5.085684] ath11k_pci :72:00.0: fw_version 0x101c06cc fw_build_timestamp 2020-06-24 19:50 fw_build_id [ 5.258202] ath11k_pci :72:00.0 wlp114s0: renamed from wlan0 [ 351.080712] ath11k_pci :72:00.0: link down error during global reset [ 356.511270] ath11k_pci :72:00.0: BAR 0: assigned [mem 0xa250-0xa25f 64bit] [ 356.512356] ath11k_pci :72:00.0: qca6390 hw2.0 ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-21-generic 5.13.0-21.21 ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18 Uname: Linux 5.13.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Nov 10 15:23:07 2021 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85 InstallationDate: Installed on 2021-05-04 (190 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Dell Inc. XPS 13 9310 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.13.0-21-generic root=UUID=676fbdd4-8566-4457-8530-0f412d28b48f ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.13.0-21-generic N/A linux-backports-modules-5.13.0-21-generic N/A linux-firmware 1.201.1 SourcePackage: linux UpgradeStatus: Upgraded to impish on 2021-10-19 (22 days ago) dmi.bios.date: 09/30/2021 dmi.bios.release: 3.2 dmi.bios.vendor: Dell Inc. dmi.bios.version: 3.2.0 dmi.board.name: 0MRT12 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr3.2.0:bd09/30/2021:br3.2:svnDellInc.:pnXPS139310:pvr:rvnDellInc.:rn0MRT12:rvrA00:cvnDellInc.:ct10:cvr:sku0991: dmi.product.family: XPS dmi.product.name: XPS 13 9310 dmi.product.sku: 0991 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950515/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe :
[Kernel-packages] [Bug 1950439] Re: NetXtreme BCM5764M Gigabit Ethernet PCIe (rev 10) does not work
** Attachment removed: "WifiSyslog.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950439/+attachment/5539517/+files/WifiSyslog.txt ** Attachment removed: "CurrentDmesg.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950439/+attachment/5539504/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1950439 Title: NetXtreme BCM5764M Gigabit Ethernet PCIe (rev 10) does not work Status in linux package in Ubuntu: Confirmed Bug description: problem in 5.4.0-90-generic 5.4.0-89-generic works fine ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-90-generic 5.4.0-90.101 ProcVersionSignature: Ubuntu 5.4.0-89.100-generic 5.4.143 Uname: Linux 5.4.0-89-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.4.0-89-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D2p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CasperMD5CheckResult: skip Date: Wed Nov 10 11:01:20 2021 InstallationDate: Installed on 2021-05-11 (182 days ago) InstallationMedia: Ubuntu-Server 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 002: ID 24ae:2010 RAPOO Rapoo 2.4G Wireless Device 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 MachineType: Dell Inc. OptiPlex 160 ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-89-generic root=UUID=b067f1b4-b25f-4395-b69e-9c200d7337b0 ro RelatedPackageVersions: linux-restricted-modules-5.4.0-89-generic N/A linux-backports-modules-5.4.0-89-generic N/A linux-firmware1.187.20 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/19/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: 0H7TGR dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA10:bd01/19/2012:svnDellInc.:pnOptiPlex160:pvrNotSpecified:rvnDellInc.:rn0H7TGR:rvrA00:cvnDellInc.:ct3:cvrNotSpecified: dmi.product.name: OptiPlex 160 dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950439/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1950503] [NEW] package linux-modules-nvidia-390-5.11.0-40-generic 5.11.0-40.44~20.04.2+1 failed to install/upgrade: installed linux-modules-nvidia-390-5.11.0-40-generic package
Public bug reported: System encountered an error warning message ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-modules-nvidia-390-5.11.0-40-generic 5.11.0-40.44~20.04.2+1 ProcVersionSignature: Ubuntu 5.11.0-40.44~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia wl ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Nov 10 11:04:14 2021 ErrorMessage: installed linux-modules-nvidia-390-5.11.0-40-generic package post-installation script subprocess returned error exit status 1 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: linux-restricted-modules-hwe-5.11 Title: package linux-modules-nvidia-390-5.11.0-40-generic 5.11.0-40.44~20.04.2+1 failed to install/upgrade: installed linux-modules-nvidia-390-5.11.0-40-generic package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-restricted-modules-hwe-5.11 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal need-duplicate-check -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1950503 Title: package linux-modules-nvidia-390-5.11.0-40-generic 5.11.0-40.44~20.04.2+1 failed to install/upgrade: installed linux- modules-nvidia-390-5.11.0-40-generic package post-installation script subprocess returned error exit status 1 Status in linux-restricted-modules-hwe-5.11 package in Ubuntu: New Bug description: System encountered an error warning message ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-modules-nvidia-390-5.11.0-40-generic 5.11.0-40.44~20.04.2+1 ProcVersionSignature: Ubuntu 5.11.0-40.44~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia wl ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Nov 10 11:04:14 2021 ErrorMessage: installed linux-modules-nvidia-390-5.11.0-40-generic package post-installation script subprocess returned error exit status 1 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: linux-restricted-modules-hwe-5.11 Title: package linux-modules-nvidia-390-5.11.0-40-generic 5.11.0-40.44~20.04.2+1 failed to install/upgrade: installed linux-modules-nvidia-390-5.11.0-40-generic package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules-hwe-5.11/+bug/1950503/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1921829] Re: RTL8821CE 802.11ac PCIe [10ec:c821] subsystem [17aa:c024] Bluetooth not working
Bug still present, I can enable Bluetooth but it's not connecting to 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/1921829 Title: RTL8821CE 802.11ac PCIe [10ec:c821] subsystem [17aa:c024] Bluetooth not working Status in linux package in Ubuntu: Incomplete Status in rtl8821ce package in Ubuntu: New Bug description: It's impossible to activate the Bluetooth, putting the switch to ON does nothing, when re-entering the Bluetooth settings it's still OFF. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-control-center 1:3.38.5-1ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 Uname: Linux 5.11.0-11-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Mar 30 08:11:43 2021 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2020-09-15 (195 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to hirsute on 2021-03-19 (10 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1921829/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1950010] Re: Upgrading to 1.187.20 results in missing firmware, Nvidia 1650 MaxQ
This is a duplicate of https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1938983 -- 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/1950010 Title: Upgrading to 1.187.20 results in missing firmware, Nvidia 1650 MaxQ Status in linux-firmware package in Ubuntu: Confirmed Bug description: On a fresh install of Kubuntu 20.04, I ran sudo apt upgrade, which results in the the following warnings: Setting up linux-firmware (1.187.20) ... update-initramfs: Generating /boot/initrd.img-5.11.0-38-generic W: Possible missing firmware /lib/firmware/i915/skl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/bxt_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/kbl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/glk_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/kbl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/kbl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/cml_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/icl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/ehl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/ehl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/tgl_huc_7.5.0.bin for module i915 W: Possible missing firmware /lib/firmware/i915/tgl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/tgl_huc_7.5.0.bin for module i915 W: Possible missing firmware /lib/firmware/i915/tgl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/dg1_dmc_ver2_02.bin for module i915 update-initramfs: Generating /boot/initrd.img-5.11.0-27-generic W: Possible missing firmware /lib/firmware/i915/skl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/bxt_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/kbl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/glk_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/kbl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/kbl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/cml_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/icl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/ehl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/ehl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/tgl_huc_7.5.0.bin for module i915 W: Possible missing firmware /lib/firmware/i915/tgl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/tgl_huc_7.5.0.bin for module i915 W: Possible missing firmware /lib/firmware/i915/tgl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/dg1_dmc_ver2_02.bin for module i915 Booting to the last installed kernel, 5.11.0-27-generic will allow me to boot into the desktop - however if I were to use a Nvidia driver (460 and 470, non-server), I will have issues getting the computer to sleep, and on one boot I the shutdown greeter kept crashing The following packages were part of the upgrade: esme@Esme-Prestige-14:~$ sudo apt upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages were automatically installed and are no longer required: libatomic1:i386 libbsd0:i386 libdpkg-perl libdrm-amdgpu1:i386 libdrm-intel1:i386 libdrm-nouveau2:i386 libdrm-radeon1:i386 libdrm2:i386 libedit2:i386 libelf1:i386 libexpat1:i386 libffi7:i386 libfile-fcntllock-perl libglvnd0:i386 libllvm12:i386 libnvidia-cfg1-470 libnvidia-common-470 libnvidia-compute-470:i386 libnvidia-decode-470 libnvidia-decode-470:i386 libnvidia-encode-470 libnvidia-encode-470:i386 libnvidia-extra-470 libnvidia-fbc1-470 libnvidia-gl-470 libnvidia-gl-470:i386 libnvidia-ifr1-470 libpciaccess0:i386 libsensors5:i386 libstdc++6:i386 libvulkan1:i386 libwayland-client0:i386 libx11-6:i386 libx11-xcb1:i386 libxau6:i386 libxcb-dri2-0:i386 libxcb-dri3-0:i386 libxcb-glx0:i386 libxcb-present0:i386 libxcb-randr0:i386 libxcb-shm0:i386 libxcb-sync1:i386 libxcb-xfixes0:i386 libxcb1:i386 libxdmcp6:i386 libxext6:i386 libxfixes3:i386 libxnvctrl0 libxshmfence1:i386 libxxf86vm1:i386 mesa-vulkan-drivers:i386 nvidia-compute-utils-470 nvidia-kernel-source-470 nvidia-prime nvidia-settings nvidia-utils-470 pkg-config screen-resolution-extra
[Kernel-packages] [Bug 1943464] Re: Reassign I/O Path of ConnectX-5 Port 1 before Port 2 causes NULL dereference
Thank you Niklas for the verification on focal - I'm updating the tag accordingly... ** 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/1943464 Title: Reassign I/O Path of ConnectX-5 Port 1 before Port 2 causes NULL dereference Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Committed Status in linux source package in Hirsute: Fix Committed Status in linux source package in Impish: Fix Committed Status in linux source package in Jammy: Fix Released Bug description: SRU Justification: [Impact] * After reassigning a PCHID of a ConnectX-5 based RoCE Adapter from one physical LPAR to another, running Ubuntu 20.04 with kernel 5.4 (latest), a lifetime issue occurs. * Subsequent testing on newer kernels now shows that a NULL pointer dereference in the zPCI code happens (causing a hard crash) that was previously hidden by leaking the struct pci_dev. * For a more detailed root cause analysis, see the below original bug description. [Fix] The following three commits fix this issue in focal: * upstream (since v5.12-rc4): 0b13525c20febcfecccf6fc1db5969727401317d 0b13525c20fe "s390/pci: fix leak of PCI device structure" backport: https://launchpadlibrarian.net/566161494/0001-s390-pci-fix-leak-of-PCI-device-structure.patch * upstream (since v5.14-rc7): 2a671f77ee49f3e78997b77fdee139467ff6a598 2a671f77ee49 "s390/pci: fix use after free of zpci_dev" backport: https://launchpadlibrarian.net/566161496/0002-s390-pci-fix-use-after-free-of-zpci_dev.patch * upstream (since v5.15-rc5): a46044a92add6a400f4dada7b943b30221f7cc80 a46044a92add "s390/pci: fix zpci_zdev_put() on reserve" backport: https://launchpadlibrarian.net/566161497/0003-s390-pci-fix-zpci_zdev_put-on-reserve.patch * Commit 0b13525c20fe fixes a lifetime issue of the struct pci_dev that was not released on removal, commit 2a671f77ee49 fixes the 'NULL pointer dereference' (causing the hard crash) itself. and commit a46044a92add fixes the handling of multiple events for a single reserve state transition of the device. Without this, the NULL dereference can still be triggered as Reassign I/O Path causes a redudant second removal event. * Since none of the three upstream commits does apply cleanly to focal master-next by just cherry-picking them (mainly due to changes in the context), the above backports are needed. [Test Case] * Two z15 or LinuxONE III LPARs, one with a Connect-X5 based RoCE adapter attached. * LPARs need to run Ubuntu 20.04 with kernel 5.4 to hit the lifetime issue (that hides the also potential existing 'NULL pointer dereference') - with Hirsute and kernel 5.11 the 'NULL pointer dereference' crash occurs. * Now change the PCHID (physical channel identifier) to a different one from the 2nd LPAR (at the HMC?). * Verify if the reassignment worked properly (by checking the PCHID) and monitor the kernel ring buffer dmesg (diagnostic messages) for "Krnl PSW" crash (caused by NULL pointer) (for more error details, please see below original bug description). * Due hardware availability reasons (the ConnectX-5 cards are only used in special cases), the testing needs to be done by IBM. [Regression Potential / What can go wrong] * What can go wrong with: 2a671f77ee49 "s390/pci: fix use after free of zpci_dev" * The reference count to the struct zpci_dev got increased while it is used by the PCI core. This could cause a leak if not properly released. * Hot-plug of there Connect-X5 devices could be broken on s390x entirely, in case the new pointer handing is erroneous. * This may even have an impact on "cold plug", too. * Fortunately the modifications are quite minimal and thereby traceable, * and affect /arch/s390/pci/pci.c and arch/s390/pci/pci_bus.h only, hence are specific to the s390x platform only and there again to "plugging" of zPCI devices. * What can go wrong with: 0b13525c20fe "s390/pci: fix leak of PCI device structure" * The function zpci_remove_device got expanded with an additional set_error argument, and the internal flow got significantly changed. In case handled in a wrong way, this may harm the entire remove/release logic. * The calls of zpci_remove_device need to be adjusted (as part of the new arg), failures here will most likely be identified at compile time. * The initialization of the pci_dev struct got improved, * and the flow in __zpci_event_availability carefully changed to reflect the device slot/bus remove characteristics. However, issues here may lead again to general zpci hotplug removal
[Kernel-packages] [Bug 1947453] Re: [amdgpu] wayland black screen with white flashes, display corruption, kernel 5.13
** Changed in: linux (Ubuntu) Status: Fix Released => 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/1947453 Title: [amdgpu] wayland black screen with white flashes, display corruption, kernel 5.13 Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: After upgrade from ubuntu 21.04 to ubuntu 21.10 I am seeing black screen in wayland session and screen corruption in Xorg session ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: xorg 1:7.7+22ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 BootLog: Error: [Errno 13] Отказано в доступе: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Oct 16 15:49:45 2021 DistUpgraded: 2021-10-16 08:19:20,349 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: impish DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Stoney [Radeon R2/R3/R4/R5 Graphics] [1002:98e4] (rev da) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Stoney [Radeon R2/R3/R4/R5 Graphics] [1043:1b70] InstallationDate: Installed on 2020-11-20 (329 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: ASUSTeK COMPUTER INC. X505BA ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-19-generic root=UUID=40f47434-863f-48cf-9af2-41e67323cb0c ro iommu=soft quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to impish on 2021-10-16 (0 days ago) dmi.bios.date: 04/02/2020 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X505BA.317 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X505BA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX505BA.317:bd04/02/2020:br5.12:svnASUSTeKCOMPUTERINC.:pnX505BA:pvr1.0:sku:rvnASUSTeKCOMPUTERINC.:rnX505BA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: VivoBook dmi.product.name: X505BA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.2-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: eugene 2026 F pulseaudio /dev/snd/controlC0: eugene 2026 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2020-11-20 (329 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: ASUSTeK COMPUTER INC. X505BA Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-19-generic root=UUID=40f47434-863f-48cf-9af2-41e67323cb0c ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 RelatedPackageVersions: linux-restricted-modules-5.13.0-19-generic N/A linux-backports-modules-5.13.0-19-generic N/A linux-firmware 1.201 Tags: impish wayland-session Uname: Linux 5.13.0-19-generic x86_64 UpgradeStatus: Upgraded to impish on 2021-10-16 (0 days ago) UserGroups: adm cdrom dip kvm libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/02/2020 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X505BA.317 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X505BA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK
[Kernel-packages] [Bug 1943464] Comment bridged from LTC Bugzilla
In other words: having /focal-proposed enabled, and installing linux- generic 5.4.0.91.95 will install the kernel that needs the verification. --- Comment From niklas.schne...@ibm.com 2021-11-10 12:30 EDT--- Ah ok didn't know that, thanks for the explanation. I tried the test scenario with this kernel and actually saw the behavior of the common PCI core keeping a reference to the removed function 0 that I didn't see in some previous kernels. This could also be due to other circumstances in testing but it does mean that without this fix the kernel would likely have crashed in my test. It did not and the /sys/kernel/debug/s390dbf/pci_msg/sprintf prints added with the fix showed that it worked as designed. In summary the fix is working in the proposed kernel and we do definitely need it to prevent NULL pointer dereference and subsequent kernel crash in the test scenario. The "FW pages counter is 43318 after reclaiming all pages" warning is still there as expected though. I did a quick search but I'm not sure which upstream commit in the Mellanox driver would get rid of that too but at least this doesn't lead to a panic. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1943464 Title: Reassign I/O Path of ConnectX-5 Port 1 before Port 2 causes NULL dereference Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Committed Status in linux source package in Hirsute: Fix Committed Status in linux source package in Impish: Fix Committed Status in linux source package in Jammy: Fix Released Bug description: SRU Justification: [Impact] * After reassigning a PCHID of a ConnectX-5 based RoCE Adapter from one physical LPAR to another, running Ubuntu 20.04 with kernel 5.4 (latest), a lifetime issue occurs. * Subsequent testing on newer kernels now shows that a NULL pointer dereference in the zPCI code happens (causing a hard crash) that was previously hidden by leaking the struct pci_dev. * For a more detailed root cause analysis, see the below original bug description. [Fix] The following three commits fix this issue in focal: * upstream (since v5.12-rc4): 0b13525c20febcfecccf6fc1db5969727401317d 0b13525c20fe "s390/pci: fix leak of PCI device structure" backport: https://launchpadlibrarian.net/566161494/0001-s390-pci-fix-leak-of-PCI-device-structure.patch * upstream (since v5.14-rc7): 2a671f77ee49f3e78997b77fdee139467ff6a598 2a671f77ee49 "s390/pci: fix use after free of zpci_dev" backport: https://launchpadlibrarian.net/566161496/0002-s390-pci-fix-use-after-free-of-zpci_dev.patch * upstream (since v5.15-rc5): a46044a92add6a400f4dada7b943b30221f7cc80 a46044a92add "s390/pci: fix zpci_zdev_put() on reserve" backport: https://launchpadlibrarian.net/566161497/0003-s390-pci-fix-zpci_zdev_put-on-reserve.patch * Commit 0b13525c20fe fixes a lifetime issue of the struct pci_dev that was not released on removal, commit 2a671f77ee49 fixes the 'NULL pointer dereference' (causing the hard crash) itself. and commit a46044a92add fixes the handling of multiple events for a single reserve state transition of the device. Without this, the NULL dereference can still be triggered as Reassign I/O Path causes a redudant second removal event. * Since none of the three upstream commits does apply cleanly to focal master-next by just cherry-picking them (mainly due to changes in the context), the above backports are needed. [Test Case] * Two z15 or LinuxONE III LPARs, one with a Connect-X5 based RoCE adapter attached. * LPARs need to run Ubuntu 20.04 with kernel 5.4 to hit the lifetime issue (that hides the also potential existing 'NULL pointer dereference') - with Hirsute and kernel 5.11 the 'NULL pointer dereference' crash occurs. * Now change the PCHID (physical channel identifier) to a different one from the 2nd LPAR (at the HMC?). * Verify if the reassignment worked properly (by checking the PCHID) and monitor the kernel ring buffer dmesg (diagnostic messages) for "Krnl PSW" crash (caused by NULL pointer) (for more error details, please see below original bug description). * Due hardware availability reasons (the ConnectX-5 cards are only used in special cases), the testing needs to be done by IBM. [Regression Potential / What can go wrong] * What can go wrong with: 2a671f77ee49 "s390/pci: fix use after free of zpci_dev" * The reference count to the struct zpci_dev got increased while it is used by the PCI core. This could cause a leak if not properly released. * Hot-plug of there Connect-X5 devices could be broken on s390x entirely, in case the new pointer handing is erroneous. * This may even have an impact on "cold plug",
[Kernel-packages] [Bug 1950355] Re: Intense screen flickering, vertical rainbow bars, display problems on Ubuntu 20.04, Lenovo X1 Carbon
Update: I got the same issue on Ubuntu 20.04.2. Looks like this isn't a kernel issue after all. Thanks a ton for the pointer Daniel, I'll return the machine or dig into the hardware. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1950355 Title: Intense screen flickering, vertical rainbow bars, display problems on Ubuntu 20.04, Lenovo X1 Carbon Status in linux-hwe-5.11 package in Ubuntu: Incomplete Bug description: (Initial post on ask ubuntu, copy pasted: https://askubuntu.com/questions/1359955/intense-screen-flickering- vertical-rainbow-bars-display-problems-on-ubuntu-20) Starting today (Aug 24) I observed intense screen flickering and tearing on my Ubuntu 20.04.3 on the Lenovo X1 Carbon. As far as I know, there were no shutdowns, updates, or changes. I observed this behavior once the machine started up from sleep. Throughout the day I have restarted (and powered down) the machine several times, but the problem persists. Here is a video example: https://photos.app.goo.gl/516nAe7AUUYnAHzd7 Here is an image: https://i.stack.imgur.com/RgLvB.jpg This video was taken from a clean Ubuntu install USB, so I don't think it has to do with anything I've installed or updated in the past. The system does not have any other operating systems on it (its not dual booted). I'm using basic integrated graphics (Mesa Intel® UHD Graphics 620 (WHL GT2)). System has 16gb of RAM and a Intel® Core™ i7-8665U CPU @ 1.90GHz × 8 processor, so I don't think the issue is available processing power (although the integrated graphics could be bad). I'm already using Wayland. I tried everything in the following links: Ubuntu screen flickering https://www.reddit.com/r/Ubuntu/comments/g78o4e/screen_tearing_in_ubuntu_2004/ The flickering is most noticeable in Chrome/Firefox (regardless of enabling/disabling hardware acceleration or setting any chrome://flags). However, I've also observed it with just editing Vim in terminal. EDIT: A month later, still experiencing this issue. This problem really seems to come and go -- it will go days without issue, and then have days again where it is constant. I've noticed it on all browsers. I've noticed that closing the webbrowser seems to resolve the issue most of the time. I've noticed that this is not an issue on any extended screens, just the main screen. --- Since the above post, I tried booting into a clean live disk running Ubuntu 20.04.2. This actually worked fine, and I did not observe any strange graphical effects. As per the reply on ask ubuntu, I decided to file this bug. --- Ubuntu release Description: Ubuntu 20.04.3 LTS Release: 20.04 xorg package version: xorg: Installed: 1:7.7+19ubuntu14 Candidate: 1:7.7+19ubuntu14 Version table: *** 1:7.7+19ubuntu14 500 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.11.0-38.42~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Nov 9 13:16:35 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.26, 5.11.0-37-generic, x86_64: installed virtualbox, 6.1.26, 5.11.0-38-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 620 (Whiskey Lake) [17aa:2292] InstallationDate: Installed on 2021-03-15 (239 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: LENOVO 20QDS3B800 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-38-generic root=UUID=9213d3af-1e40-4621-9964-1212d1070372 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/24/2020 dmi.bios.release: 1.38 dmi.bios.vendor: LENOVO dmi.bios.version: N2HET55W (1.38 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QDS3B800 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 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.20 dmi.modalias:
[Kernel-packages] [Bug 1945590] Re: Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled
Works for me, too. uname -a Linux e15g2 5.13.0-22-generic #22+arighi2020+1 SMP Wed Nov 10 15:41:33 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Thank you Andrea! -- 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/1945590 Title: Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled Status in linux package in Ubuntu: Confirmed Status in linux source package in Impish: Confirmed Status in linux source package in Jammy: Confirmed Bug description: I installed the Ubuntu 21.10 beta and as soon as I boot I get the kernel panic that I am attaching. I also installed Ubuntu 21.04 and upgraded, as soon as I boot with the 5.13 kernel I get the same problem, disabling the trackpad and trackpoint in the bios the problem disappears. Everything works with the 5.11 kernel. I remain available for further details and sorry for my lack of experience. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-16-generic 5.13.0-16.16 ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pietro 1810 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Sep 30 10:26:10 2021 InstallationDate: Installed on 2021-09-29 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: LENOVO 20TA0033IX ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-16-generic root=UUID=b5ea9465-4cd9-408b-8e30-458acf90181b ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.13.0-16-generic N/A linux-backports-modules-5.13.0-16-generic N/A linux-firmware 1.201 SourcePackage: linux UpgradeStatus: Upgraded to impish on 2021-09-29 (0 days ago) dmi.bios.date: 09/02/2021 dmi.bios.release: 1.43 dmi.bios.vendor: LENOVO dmi.bios.version: R1EET43W(1.43 ) dmi.board.asset.tag: Not Available dmi.board.name: 20TA0033IX 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.43 dmi.modalias: dmi:bvnLENOVO:bvrR1EET43W(1.43):bd09/02/2021:br1.43:efr1.43:svnLENOVO:pn20TA0033IX:pvrThinkPadE14Gen2:skuLENOVO_MT_20TA_BU_Think_FM_ThinkPadE14Gen2:rvnLENOVO:rn20TA0033IX:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad E14 Gen 2 dmi.product.name: 20TA0033IX dmi.product.sku: LENOVO_MT_20TA_BU_Think_FM_ThinkPad E14 Gen 2 dmi.product.version: ThinkPad E14 Gen 2 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945590/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1945590] Re: Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled
Thanks for testing @randombop! I also sent the fix upstream: https://lore.kernel.org/lkml/2020165943.45010-1-andrea.ri...@canonical.com/T/#u As soon as I get a positive feedback I'll make sure that this fix will be included in the affected Ubuntu kernels. ** Also affects: linux (Ubuntu Jammy) Importance: High Status: Confirmed ** Changed in: linux (Ubuntu Jammy) Assignee: (unassigned) => Andrea Righi (arighi) -- 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/1945590 Title: Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled Status in linux package in Ubuntu: Confirmed Status in linux source package in Impish: Confirmed Status in linux source package in Jammy: Confirmed Bug description: I installed the Ubuntu 21.10 beta and as soon as I boot I get the kernel panic that I am attaching. I also installed Ubuntu 21.04 and upgraded, as soon as I boot with the 5.13 kernel I get the same problem, disabling the trackpad and trackpoint in the bios the problem disappears. Everything works with the 5.11 kernel. I remain available for further details and sorry for my lack of experience. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-16-generic 5.13.0-16.16 ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pietro 1810 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Sep 30 10:26:10 2021 InstallationDate: Installed on 2021-09-29 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: LENOVO 20TA0033IX ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-16-generic root=UUID=b5ea9465-4cd9-408b-8e30-458acf90181b ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.13.0-16-generic N/A linux-backports-modules-5.13.0-16-generic N/A linux-firmware 1.201 SourcePackage: linux UpgradeStatus: Upgraded to impish on 2021-09-29 (0 days ago) dmi.bios.date: 09/02/2021 dmi.bios.release: 1.43 dmi.bios.vendor: LENOVO dmi.bios.version: R1EET43W(1.43 ) dmi.board.asset.tag: Not Available dmi.board.name: 20TA0033IX 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.43 dmi.modalias: dmi:bvnLENOVO:bvrR1EET43W(1.43):bd09/02/2021:br1.43:efr1.43:svnLENOVO:pn20TA0033IX:pvrThinkPadE14Gen2:skuLENOVO_MT_20TA_BU_Think_FM_ThinkPadE14Gen2:rvnLENOVO:rn20TA0033IX:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad E14 Gen 2 dmi.product.name: 20TA0033IX dmi.product.sku: LENOVO_MT_20TA_BU_Think_FM_ThinkPad E14 Gen 2 dmi.product.version: ThinkPad E14 Gen 2 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945590/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1950239] Re: creat09 from ubuntu_ltp_syscalls and cve-2018-13405 from ubuntu_ltp/cve failed with XFS
Found also on 2021.11.08/focal/linux-azure/5.4.0-1064.67 ** Tags added: 5.4 -- 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/1950239 Title: creat09 from ubuntu_ltp_syscalls and cve-2018-13405 from ubuntu_ltp/cve failed with XFS Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Confirmed Status in linux source package in Focal: Confirmed Status in linux source package in Hirsute: Confirmed Status in linux source package in Impish: Fix Released Bug description: These two tests, creat09 from ubuntu_ltp_syscalls and cve-2018-13405 from ubuntu_ltp/cve are actually the same test. Issue found on F-oem-5.10.0-1051.53 With LTP upstream head SHA1 2ac54d426 This is not a regression, it's because of a recent update that enables this test on different filesystems: https://github.com/linux-test-project/ltp/commit/433b6cf7ade3d5e3bd4b85ac89b164c53312e65a Test failed on XFS with: tst_test.c:1431: TINFO: Testing on xfs tst_test.c:932: TINFO: Formatting /dev/loop3 with xfs opts='' extra opts='' tst_test.c:1363: TINFO: Timeout per run is 0h 05m 00s creat09.c:55: TINFO: User nobody: uid = 65534, gid = 65534 creat09.c:57: TINFO: Found unused GID 11: SUCCESS (0) creat09.c:88: TPASS: mntpoint/testdir/creat.tmp: Owned by correct group creat09.c:92: TFAIL: mntpoint/testdir/creat.tmp: Setgid bit is set creat09.c:88: TPASS: mntpoint/testdir/open.tmp: Owned by correct group creat09.c:92: TFAIL: mntpoint/testdir/open.tmp: Setgid bit is set Test log: Checking for required user/group ids 'nobody' user id and group found. 'bin' user id and group found. 'daemon' user id and group found. Users group found. Sys group found. Required users/groups exist. no big block device was specified on commandline. Tests which require a big block device are disabled. You can specify it with option -z INFO: Test start time: Mon Nov 8 10:00:06 UTC 2021 COMMAND:/opt/ltp/bin/ltp-pan -q -e -S -a 61758 -n 61758 -f /tmp/ltp-shLYORuoRT/alltests -l /dev/null -C /dev/null -T /dev/null LOG File: /dev/null FAILED COMMAND File: /dev/null TCONF COMMAND File: /dev/null Running tests... tst_device.c:88: TINFO: Found free device 3 '/dev/loop3' tst_supported_fs_types.c:88: TINFO: Kernel supports ext2 tst_supported_fs_types.c:50: TINFO: mkfs.ext2 does exist tst_supported_fs_types.c:88: TINFO: Kernel supports ext3 tst_supported_fs_types.c:50: TINFO: mkfs.ext3 does exist tst_supported_fs_types.c:88: TINFO: Kernel supports ext4 tst_supported_fs_types.c:50: TINFO: mkfs.ext4 does exist tst_supported_fs_types.c:88: TINFO: Kernel supports xfs tst_supported_fs_types.c:50: TINFO: mkfs.xfs does exist tst_supported_fs_types.c:88: TINFO: Kernel supports btrfs tst_supported_fs_types.c:50: TINFO: mkfs.btrfs does exist tst_supported_fs_types.c:146: TINFO: Skipping vfat as requested by the test tst_supported_fs_types.c:146: TINFO: Skipping exfat as requested by the test tst_supported_fs_types.c:88: TINFO: Kernel supports tmpfs tst_supported_fs_types.c:37: TINFO: mkfs is not needed for tmpfs tst_test.c:1431: TINFO: Testing on ext2 tst_test.c:932: TINFO: Formatting /dev/loop3 with ext2 opts='' extra opts='' mke2fs 1.45.5 (07-Jan-2020) tst_test.c:1363: TINFO: Timeout per run is 0h 05m 00s creat09.c:55: TINFO: User nobody: uid = 65534, gid = 65534 creat09.c:57: TINFO: Found unused GID 11: SUCCESS (0) creat09.c:88: TPASS: mntpoint/testdir/creat.tmp: Owned by correct group creat09.c:94: TPASS: mntpoint/testdir/creat.tmp: Setgid bit not set creat09.c:88: TPASS: mntpoint/testdir/open.tmp: Owned by correct group creat09.c:94: TPASS: mntpoint/testdir/open.tmp: Setgid bit not set tst_test.c:1431: TINFO: Testing on ext3 tst_test.c:932: TINFO: Formatting /dev/loop3 with ext3 opts='' extra opts='' mke2fs 1.45.5 (07-Jan-2020) tst_test.c:1363: TINFO: Timeout per run is 0h 05m 00s creat09.c:55: TINFO: User nobody: uid = 65534, gid = 65534 creat09.c:57: TINFO: Found unused GID 11: SUCCESS (0) creat09.c:88: TPASS: mntpoint/testdir/creat.tmp: Owned by correct group creat09.c:94: TPASS: mntpoint/testdir/creat.tmp: Setgid bit not set creat09.c:88: TPASS: mntpoint/testdir/open.tmp: Owned by correct group creat09.c:94: TPASS: mntpoint/testdir/open.tmp: Setgid bit not set tst_test.c:1431: TINFO: Testing on ext4 tst_test.c:932: TINFO: Formatting /dev/loop3 with ext4 opts='' extra opts='' mke2fs 1.45.5 (07-Jan-2020) tst_test.c:1363: TINFO: Timeout per run is 0h 05m 00s creat09.c:55: TINFO: User nobody: uid = 65534, gid = 65534 creat09.c:57: TINFO: Found unused GID 11: SUCCESS (0) creat09.c:88: TPASS: mntpoint/testdir/creat.tmp: Owned by correct group creat09.c:94: TPASS: mntpoint/testdir/creat.tmp: Setgid bit not set creat09.c:88: TPASS:
[Kernel-packages] [Bug 1945590] Re: Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled
Boots ok with this fix: uname -a: Linux miles 5.13.0-22-generic #22+arighi2020+1 SMP Wed Nov 10 15:41:33 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux -- 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/1945590 Title: Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled Status in linux package in Ubuntu: Confirmed Status in linux source package in Impish: Confirmed Bug description: I installed the Ubuntu 21.10 beta and as soon as I boot I get the kernel panic that I am attaching. I also installed Ubuntu 21.04 and upgraded, as soon as I boot with the 5.13 kernel I get the same problem, disabling the trackpad and trackpoint in the bios the problem disappears. Everything works with the 5.11 kernel. I remain available for further details and sorry for my lack of experience. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-16-generic 5.13.0-16.16 ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pietro 1810 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Sep 30 10:26:10 2021 InstallationDate: Installed on 2021-09-29 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: LENOVO 20TA0033IX ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-16-generic root=UUID=b5ea9465-4cd9-408b-8e30-458acf90181b ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.13.0-16-generic N/A linux-backports-modules-5.13.0-16-generic N/A linux-firmware 1.201 SourcePackage: linux UpgradeStatus: Upgraded to impish on 2021-09-29 (0 days ago) dmi.bios.date: 09/02/2021 dmi.bios.release: 1.43 dmi.bios.vendor: LENOVO dmi.bios.version: R1EET43W(1.43 ) dmi.board.asset.tag: Not Available dmi.board.name: 20TA0033IX 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.43 dmi.modalias: dmi:bvnLENOVO:bvrR1EET43W(1.43):bd09/02/2021:br1.43:efr1.43:svnLENOVO:pn20TA0033IX:pvrThinkPadE14Gen2:skuLENOVO_MT_20TA_BU_Think_FM_ThinkPadE14Gen2:rvnLENOVO:rn20TA0033IX:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad E14 Gen 2 dmi.product.name: 20TA0033IX dmi.product.sku: LENOVO_MT_20TA_BU_Think_FM_ThinkPad E14 Gen 2 dmi.product.version: ThinkPad E14 Gen 2 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945590/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1939347] Re: Ubuntu 20.04 freeze since kernel 5.11
Hello, kernel 5.8.0-63-generic #71~20.04.1-Ubuntu works for me. I recall that the problem for me first occurred under fedora which caused me to abandon this distribution. -- 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/1939347 Title: Ubuntu 20.04 freeze since kernel 5.11 Status in linux package in Ubuntu: Confirmed Bug description: Since the last kernel update 5.11.0-25-generic, the system freezes in a few seconds or minutes, sometimes even on the login screen. The machine is a recent dell latitude 7490. The graphics card is Intel Corporation UHD Graphics 620 (rev 07). No multiboot. No problem with the previous kernel 5.8.0-63. I had the same problem with fedora a few months ago, which forced me to switch to ubuntu without any problems so far. Thanks for your help. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: plawrence 1996 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-06-21 (414 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 1bcf:2b96 Sunplus Innovation Technology Inc. Integrated_Webcam_HD Bus 001 Device 004: ID 0a5c:5834 Broadcom Corp. 5880 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Latitude 7490 Package: linux (not installed) 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/vmlinuz-5.11.0-25-generic root=UUID=01fd281b-07d7-45f2-846b-d5b79ed5d431 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-25-generic N/A linux-backports-modules-5.11.0-25-generic N/A linux-firmware 1.187.15 Tags: focal Uname: Linux 5.11.0-25-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: 02/23/2021 dmi.bios.release: 1.19 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.19.0 dmi.board.name: 0KP0FT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.19.0:bd02/23/2021:br1.19:svnDellInc.:pnLatitude7490:pvr:rvnDellInc.:rn0KP0FT:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 7490 dmi.product.sku: 081C dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1939347/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1932539] Re: Support thunderbolt on Intel Alder Lake P
what's the status here? -- 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/1932539 Title: Support thunderbolt on Intel Alder Lake P Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.14 source package in Focal: Incomplete Bug description: Thunderbolt device probe failure on ADL: thunderbolt: probe of :00:0d.2 failed with error -110 thunderbolt: probe of :00:0d.3 failed with error -110 00:0d.2 USB controller [0c03]: Intel Corporation Device [8086:463e] (prog-if 40) Subsystem: Intel Corporation Device [8086:7270] 00:0d.3 USB controller [0c03]: Intel Corporation Device [8086:466d] (prog-if 40) Subsystem: Intel Corporation Device [8086:7270] --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.17 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-05-09 (39 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) IwConfig: lono wireless extensions. enx00e04c6801fa no wireless extensions. MachineType: Intel Corporation Alder Lake Client Platform Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-1004-oem root=UUID=fc4454dd-6eb1-4b3c-ae7f-c0b5ede8f9f7 ro module_blacklist=btintel,btusb,iwlwifi,e1000e i915.force_probe=46a0 ProcVersionSignature: Ubuntu 5.13.0-1004.4-oem 5.13.0-rc6 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.13.0-1004-oem N/A linux-backports-modules-5.13.0-1004-oem N/A linux-firmware 1.187.15 RfKill: Tags: focal Uname: Linux 5.13.0-1004-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 03/26/2021 dmi.bios.vendor: Intel Corporation dmi.bios.version: ADLPFWI1.R00.2127.A00.2103261115 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: AlderLake-P DDR5 RVP dmi.board.vendor: Intel Corporation dmi.board.version: 1 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 0.1 dmi.ec.firmware.release: 1.31 dmi.modalias: dmi:bvnIntelCorporation:bvrADLPFWI1.R00.2127.A00.2103261115:bd03/26/2021:efr1.31:svnIntelCorporation:pnAlderLakeClientPlatform:pvr0.1:sku0012:rvnIntelCorporation:rnAlderLake-PDDR5RVP:rvr1:cvnIntelCorporation:ct9:cvr0.1: dmi.product.family: Alder Lake Client System dmi.product.name: Alder Lake Client Platform dmi.product.sku: 0012 dmi.product.version: 0.1 dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.14/+bug/1932539/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1950339] Re: Screen stays black after going idle or waking up from suspend on AMD laptop
Possibly related: https://bugzilla.kernel.org/show_bug.cgi?id=213779 https://bbs.archlinux.org/viewtopic.php?id=267874 ** Bug watch added: Linux Kernel Bug Tracker #213779 https://bugzilla.kernel.org/show_bug.cgi?id=213779 -- 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/1950339 Title: Screen stays black after going idle or waking up from suspend on AMD laptop Status in linux-signed-hwe-5.13 package in Ubuntu: New Bug description: Upon upgrading to the latest HWE edge kernel (from 5.11 to 5.13) on 20.04, I found that my screen won't work if my laptop goes idle (screen off) or wakes up from suspend. Reverting to 5.11 resolves this for me. This seems to be a common issue across many distributions and appears to have been fixed in 5.14. I'm using a ThinkPad P14s AMD Gen 1 with Ryzen 7 4750u (integrated graphics). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.13.0-21-generic 5.13.0-21.21~20.04.1 ProcVersionSignature: Ubuntu 5.13.0-21.21~20.04.1-generic 5.13.18 Uname: Linux 5.13.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Nov 9 10:46:08 2021 InstallationDate: Installed on 2021-07-08 (123 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) 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/1950339/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1945590] Re: Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled
Uploaded another test kernel (5.13.0-22.22+arighi2020+1): https://kernel.ubuntu.com/~arighi/lp1945590/ However, looking more at the KASAN error, it seems that the reported error is actually an out-of-bound read... so that still doesn't explain the stack corruption, but it's still something that needs to be fixed (and the fix above should address this issue). Anyway, let's see how this new test kernel works, if it's still crashing we may need to re-enable KASAN and do an additional test with this fix applied. -- 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/1945590 Title: Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled Status in linux package in Ubuntu: Confirmed Status in linux source package in Impish: Confirmed Bug description: I installed the Ubuntu 21.10 beta and as soon as I boot I get the kernel panic that I am attaching. I also installed Ubuntu 21.04 and upgraded, as soon as I boot with the 5.13 kernel I get the same problem, disabling the trackpad and trackpoint in the bios the problem disappears. Everything works with the 5.11 kernel. I remain available for further details and sorry for my lack of experience. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-16-generic 5.13.0-16.16 ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pietro 1810 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Sep 30 10:26:10 2021 InstallationDate: Installed on 2021-09-29 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: LENOVO 20TA0033IX ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-16-generic root=UUID=b5ea9465-4cd9-408b-8e30-458acf90181b ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.13.0-16-generic N/A linux-backports-modules-5.13.0-16-generic N/A linux-firmware 1.201 SourcePackage: linux UpgradeStatus: Upgraded to impish on 2021-09-29 (0 days ago) dmi.bios.date: 09/02/2021 dmi.bios.release: 1.43 dmi.bios.vendor: LENOVO dmi.bios.version: R1EET43W(1.43 ) dmi.board.asset.tag: Not Available dmi.board.name: 20TA0033IX 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.43 dmi.modalias: dmi:bvnLENOVO:bvrR1EET43W(1.43):bd09/02/2021:br1.43:efr1.43:svnLENOVO:pn20TA0033IX:pvrThinkPadE14Gen2:skuLENOVO_MT_20TA_BU_Think_FM_ThinkPadE14Gen2:rvnLENOVO:rn20TA0033IX:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad E14 Gen 2 dmi.product.name: 20TA0033IX dmi.product.sku: LENOVO_MT_20TA_BU_Think_FM_ThinkPad E14 Gen 2 dmi.product.version: ThinkPad E14 Gen 2 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945590/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1950483] 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/1950483 Title: package linux-libc-dev 5.4.0-89.100 failed to install/upgrade: unable to open '/usr/share/doc/linux-libc-dev/copyright.dpkg-new': Operation not permitted Status in linux package in Ubuntu: Confirmed Bug description: An update to Kernel 5.11.0.40 fails on several PCs. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-libc-dev 5.4.0-89.100 ProcVersionSignature: Ubuntu 5.11.0-38.42~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rene 2192 F pulseaudio /dev/snd/controlC1: rene 2192 F pulseaudio CasperMD5CheckResult: skip Date: Wed Nov 10 16:38:00 2021 Dependencies: DuplicateSignature: package:linux-libc-dev:5.4.0-89.100 Unpacking linux-modules-extra-5.11.0-40-generic (5.11.0-40.44~20.04.2) ... dpkg: error processing archive /tmp/apt-dpkg-install-lJjrC6/2-linux-modules-extra-5.11.0-40-generic_5.11.0-40.44~20.04.2_amd64.deb (--unpack): unable to create new file '/var/lib/dpkg/info/linux-modules-extra-5.11.0-40-generic.list-new': Operation not permitted ErrorMessage: unable to open '/usr/share/doc/linux-libc-dev/copyright.dpkg-new': Operation not permitted InstallationDate: Installed on 2021-10-26 (15 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: Dell Inc. XPS 8700 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-38-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 SourcePackage: linux Title: package linux-libc-dev 5.4.0-89.100 failed to install/upgrade: unable to open '/usr/share/doc/linux-libc-dev/copyright.dpkg-new': Operation not permitted UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/31/2019 dmi.bios.release: 64.14 dmi.bios.vendor: Dell Inc. dmi.bios.version: A14 dmi.board.name: 0KWVT8 dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA14:bd05/31/2019:br64.14:svnDellInc.:pnXPS8700:pvr:sku0x05B7:rvnDellInc.:rn0KWVT8:rvrA03:cvnDellInc.:ct3:cvr: dmi.product.family: To be filled by O.E.M. dmi.product.name: XPS 8700 dmi.product.sku: 0x05B7 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950483/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1932539] Re: Support thunderbolt on Intel Alder Lake P
** Changed in: linux-oem-5.14 (Ubuntu) Status: New => 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/1932539 Title: Support thunderbolt on Intel Alder Lake P Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.14 source package in Focal: Incomplete Bug description: Thunderbolt device probe failure on ADL: thunderbolt: probe of :00:0d.2 failed with error -110 thunderbolt: probe of :00:0d.3 failed with error -110 00:0d.2 USB controller [0c03]: Intel Corporation Device [8086:463e] (prog-if 40) Subsystem: Intel Corporation Device [8086:7270] 00:0d.3 USB controller [0c03]: Intel Corporation Device [8086:466d] (prog-if 40) Subsystem: Intel Corporation Device [8086:7270] --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.17 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-05-09 (39 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) IwConfig: lono wireless extensions. enx00e04c6801fa no wireless extensions. MachineType: Intel Corporation Alder Lake Client Platform Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-1004-oem root=UUID=fc4454dd-6eb1-4b3c-ae7f-c0b5ede8f9f7 ro module_blacklist=btintel,btusb,iwlwifi,e1000e i915.force_probe=46a0 ProcVersionSignature: Ubuntu 5.13.0-1004.4-oem 5.13.0-rc6 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.13.0-1004-oem N/A linux-backports-modules-5.13.0-1004-oem N/A linux-firmware 1.187.15 RfKill: Tags: focal Uname: Linux 5.13.0-1004-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 03/26/2021 dmi.bios.vendor: Intel Corporation dmi.bios.version: ADLPFWI1.R00.2127.A00.2103261115 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: AlderLake-P DDR5 RVP dmi.board.vendor: Intel Corporation dmi.board.version: 1 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 0.1 dmi.ec.firmware.release: 1.31 dmi.modalias: dmi:bvnIntelCorporation:bvrADLPFWI1.R00.2127.A00.2103261115:bd03/26/2021:efr1.31:svnIntelCorporation:pnAlderLakeClientPlatform:pvr0.1:sku0012:rvnIntelCorporation:rnAlderLake-PDDR5RVP:rvr1:cvnIntelCorporation:ct9:cvr0.1: dmi.product.family: Alder Lake Client System dmi.product.name: Alder Lake Client Platform dmi.product.sku: 0012 dmi.product.version: 0.1 dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.14/+bug/1932539/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1950485] [NEW] package linux-headers-5.11.0-40-generic (not installed) failed to install/upgrade: unable to open '/usr/src/linux-headers-5.11.0-40-generic/tools/bpf/resolve_btfi
Public bug reported: An update to Kernel 5.11.0.40 fails on several PCs. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-headers-5.11.0-40-generic (not installed) ProcVersionSignature: Ubuntu 5.11.0-38.42~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Nov 10 16:54:14 2021 DuplicateSignature: package:linux-headers-5.11.0-40-generic:(not installed) Unpacking linux-modules-5.11.0-40-generic (5.11.0-40.44~20.04.2) ... dpkg: error processing archive /tmp/apt-dpkg-install-P2FhAv/0-linux-modules-5.11.0-40-generic_5.11.0-40.44~20.04.2_amd64.deb (--unpack): unable to create new file '/var/lib/dpkg/info/linux-modules-5.11.0-40-generic.list-new': Operation not permitted ErrorMessage: unable to open '/usr/src/linux-headers-5.11.0-40-generic/tools/bpf/resolve_btfids/libbpf/libbpf.a.dpkg-new': Operation not permitted InstallationDate: Installed on 2021-02-09 (273 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: linux-hwe-5.11 Title: package linux-headers-5.11.0-40-generic (not installed) failed to install/upgrade: unable to open '/usr/src/linux-headers-5.11.0-40-generic/tools/bpf/resolve_btfids/libbpf/libbpf.a.dpkg-new': Operation not permitted UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-hwe-5.11 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal need-duplicate-check -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1950485 Title: package linux-headers-5.11.0-40-generic (not installed) failed to install/upgrade: unable to open '/usr/src/linux- headers-5.11.0-40-generic/tools/bpf/resolve_btfids/libbpf/libbpf.a.dpkg- new': Operation not permitted Status in linux-hwe-5.11 package in Ubuntu: New Bug description: An update to Kernel 5.11.0.40 fails on several PCs. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-headers-5.11.0-40-generic (not installed) ProcVersionSignature: Ubuntu 5.11.0-38.42~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Nov 10 16:54:14 2021 DuplicateSignature: package:linux-headers-5.11.0-40-generic:(not installed) Unpacking linux-modules-5.11.0-40-generic (5.11.0-40.44~20.04.2) ... dpkg: error processing archive /tmp/apt-dpkg-install-P2FhAv/0-linux-modules-5.11.0-40-generic_5.11.0-40.44~20.04.2_amd64.deb (--unpack): unable to create new file '/var/lib/dpkg/info/linux-modules-5.11.0-40-generic.list-new': Operation not permitted ErrorMessage: unable to open '/usr/src/linux-headers-5.11.0-40-generic/tools/bpf/resolve_btfids/libbpf/libbpf.a.dpkg-new': Operation not permitted InstallationDate: Installed on 2021-02-09 (273 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: linux-hwe-5.11 Title: package linux-headers-5.11.0-40-generic (not installed) failed to install/upgrade: unable to open '/usr/src/linux-headers-5.11.0-40-generic/tools/bpf/resolve_btfids/libbpf/libbpf.a.dpkg-new': Operation not permitted UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.11/+bug/1950485/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1945590] Re: Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled
@marco-098 sorry I had to disable zfs, because it doesn't build
correctly with CONFIG_KASAN enabled.
However, thanks to @randombop dmesg.txt now I think I see a potential
stack corruption in the elantech code!
IIRC param[] in elantech_cahnge_report_id must be at least 3 bytes,
because elantech_read_reg_params() is calling ps2_command() with
PSMOUSE_CMD_GETINFO, that is going to write 3 bytes into param[], but
it's defined in the stack as an array of 2 bytes, therefore we can
definitely corrupt the stack here.
Basically the fix that I'd like to test is the following:
diff --git a/drivers/input/mouse/elantech.c b/drivers/input/mouse/elantech.c
index 2d0bc029619f..172a3c5db58f 100644
--- a/drivers/input/mouse/elantech.c
+++ b/drivers/input/mouse/elantech.c
@@ -1575,7 +1575,7 @@ static const struct dmi_system_id no_hw_res_dmi_table[] =
{
*/
static int elantech_change_report_id(struct psmouse *psmouse)
{
- unsigned char param[2] = { 0x10, 0x03 };
+ unsigned char param[3] = { 0x10, 0x03 };
if (elantech_write_reg_params(psmouse, 0x7, param) ||
elantech_read_reg_params(psmouse, 0x7, param) ||
I'm already preparing another test kernel (without KSASAN this time), let's see
if it fixes the problem.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1945590
Title:
Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Impish:
Confirmed
Bug description:
I installed the Ubuntu 21.10 beta and as soon as I boot I get the
kernel panic that I am attaching.
I also installed Ubuntu 21.04 and upgraded, as soon as I boot with the
5.13 kernel I get the same problem, disabling the trackpad and
trackpoint in the bios the problem disappears.
Everything works with the 5.11 kernel.
I remain available for further details and sorry for my lack of experience.
ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: linux-image-5.13.0-16-generic 5.13.0-16.16
ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13
Uname: Linux 5.13.0-16-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu69
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: pietro 1810 F pulseaudio
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Thu Sep 30 10:26:10 2021
InstallationDate: Installed on 2021-09-29 (0 days ago)
InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
MachineType: LENOVO 20TA0033IX
ProcEnviron:
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=it_IT.UTF-8
SHELL=/bin/bash
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-16-generic
root=UUID=b5ea9465-4cd9-408b-8e30-458acf90181b ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-5.13.0-16-generic N/A
linux-backports-modules-5.13.0-16-generic N/A
linux-firmware 1.201
SourcePackage: linux
UpgradeStatus: Upgraded to impish on 2021-09-29 (0 days ago)
dmi.bios.date: 09/02/2021
dmi.bios.release: 1.43
dmi.bios.vendor: LENOVO
dmi.bios.version: R1EET43W(1.43 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20TA0033IX
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.43
dmi.modalias:
dmi:bvnLENOVO:bvrR1EET43W(1.43):bd09/02/2021:br1.43:efr1.43:svnLENOVO:pn20TA0033IX:pvrThinkPadE14Gen2:skuLENOVO_MT_20TA_BU_Think_FM_ThinkPadE14Gen2:rvnLENOVO:rn20TA0033IX:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad E14 Gen 2
dmi.product.name: 20TA0033IX
dmi.product.sku: LENOVO_MT_20TA_BU_Think_FM_ThinkPad E14 Gen 2
dmi.product.version: ThinkPad E14 Gen 2
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945590/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1939347] Re: Ubuntu 20.04 freeze since kernel 5.11
Hello Kleber, I tried kernels 5.11.0-40 and 5.13.0-21. My machine freezes with both. Freezes happen randomly, maybe a few seconds after ubuntu boots, maybe after few minutes. Kernel 5.4.0-90 works. My version is Ubuntu 20.04.3 LTS. Machine is a Dell Latitude 7390 with Intel i7-8650U, Intel UHD Graphics 620, standard settings and firmware updated to latest version. -- 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/1939347 Title: Ubuntu 20.04 freeze since kernel 5.11 Status in linux package in Ubuntu: Confirmed Bug description: Since the last kernel update 5.11.0-25-generic, the system freezes in a few seconds or minutes, sometimes even on the login screen. The machine is a recent dell latitude 7490. The graphics card is Intel Corporation UHD Graphics 620 (rev 07). No multiboot. No problem with the previous kernel 5.8.0-63. I had the same problem with fedora a few months ago, which forced me to switch to ubuntu without any problems so far. Thanks for your help. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: plawrence 1996 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-06-21 (414 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 1bcf:2b96 Sunplus Innovation Technology Inc. Integrated_Webcam_HD Bus 001 Device 004: ID 0a5c:5834 Broadcom Corp. 5880 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Latitude 7490 Package: linux (not installed) 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/vmlinuz-5.11.0-25-generic root=UUID=01fd281b-07d7-45f2-846b-d5b79ed5d431 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-25-generic N/A linux-backports-modules-5.11.0-25-generic N/A linux-firmware 1.187.15 Tags: focal Uname: Linux 5.11.0-25-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: 02/23/2021 dmi.bios.release: 1.19 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.19.0 dmi.board.name: 0KP0FT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.19.0:bd02/23/2021:br1.19:svnDellInc.:pnLatitude7490:pvr:rvnDellInc.:rn0KP0FT:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 7490 dmi.product.sku: 081C dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1939347/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1950483] [NEW] package linux-libc-dev 5.4.0-89.100 failed to install/upgrade: unable to open '/usr/share/doc/linux-libc-dev/copyright.dpkg-new': Operation not permitted
Public bug reported: An update to Kernel 5.11.0.40 fails on several PCs. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-libc-dev 5.4.0-89.100 ProcVersionSignature: Ubuntu 5.11.0-38.42~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rene 2192 F pulseaudio /dev/snd/controlC1: rene 2192 F pulseaudio CasperMD5CheckResult: skip Date: Wed Nov 10 16:38:00 2021 Dependencies: DuplicateSignature: package:linux-libc-dev:5.4.0-89.100 Unpacking linux-modules-extra-5.11.0-40-generic (5.11.0-40.44~20.04.2) ... dpkg: error processing archive /tmp/apt-dpkg-install-lJjrC6/2-linux-modules-extra-5.11.0-40-generic_5.11.0-40.44~20.04.2_amd64.deb (--unpack): unable to create new file '/var/lib/dpkg/info/linux-modules-extra-5.11.0-40-generic.list-new': Operation not permitted ErrorMessage: unable to open '/usr/share/doc/linux-libc-dev/copyright.dpkg-new': Operation not permitted InstallationDate: Installed on 2021-10-26 (15 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: Dell Inc. XPS 8700 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-38-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 SourcePackage: linux Title: package linux-libc-dev 5.4.0-89.100 failed to install/upgrade: unable to open '/usr/share/doc/linux-libc-dev/copyright.dpkg-new': Operation not permitted UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/31/2019 dmi.bios.release: 64.14 dmi.bios.vendor: Dell Inc. dmi.bios.version: A14 dmi.board.name: 0KWVT8 dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA14:bd05/31/2019:br64.14:svnDellInc.:pnXPS8700:pvr:sku0x05B7:rvnDellInc.:rn0KWVT8:rvrA03:cvnDellInc.:ct3:cvr: dmi.product.family: To be filled by O.E.M. dmi.product.name: XPS 8700 dmi.product.sku: 0x05B7 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal need-duplicate-check -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1950483 Title: package linux-libc-dev 5.4.0-89.100 failed to install/upgrade: unable to open '/usr/share/doc/linux-libc-dev/copyright.dpkg-new': Operation not permitted Status in linux package in Ubuntu: New Bug description: An update to Kernel 5.11.0.40 fails on several PCs. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-libc-dev 5.4.0-89.100 ProcVersionSignature: Ubuntu 5.11.0-38.42~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rene 2192 F pulseaudio /dev/snd/controlC1: rene 2192 F pulseaudio CasperMD5CheckResult: skip Date: Wed Nov 10 16:38:00 2021 Dependencies: DuplicateSignature: package:linux-libc-dev:5.4.0-89.100 Unpacking linux-modules-extra-5.11.0-40-generic (5.11.0-40.44~20.04.2) ... dpkg: error processing archive /tmp/apt-dpkg-install-lJjrC6/2-linux-modules-extra-5.11.0-40-generic_5.11.0-40.44~20.04.2_amd64.deb (--unpack): unable to create new file '/var/lib/dpkg/info/linux-modules-extra-5.11.0-40-generic.list-new': Operation not permitted ErrorMessage: unable to open '/usr/share/doc/linux-libc-dev/copyright.dpkg-new': Operation not permitted InstallationDate: Installed on 2021-10-26 (15 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: Dell Inc. XPS 8700 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-38-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 SourcePackage: linux Title: package linux-libc-dev 5.4.0-89.100 failed to install/upgrade: unable to open '/usr/share/doc/linux-libc-dev/copyright.dpkg-new': Operation not permitted UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/31/2019 dmi.bios.release: 64.14 dmi.bios.vendor: Dell Inc. dmi.bios.version: A14 dmi.board.name:
[Kernel-packages] [Bug 1950239] Re: creat09 from ubuntu_ltp_syscalls and cve-2018-13405 from ubuntu_ltp/cve failed with XFS
Found also on 2021.11.08/bionic/linux-azure-fips/4.15.0-2039.43 ** Tags added: azure ** Tags added: hinted -- 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/1950239 Title: creat09 from ubuntu_ltp_syscalls and cve-2018-13405 from ubuntu_ltp/cve failed with XFS Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Confirmed Status in linux source package in Focal: Confirmed Status in linux source package in Hirsute: Confirmed Status in linux source package in Impish: Fix Released Bug description: These two tests, creat09 from ubuntu_ltp_syscalls and cve-2018-13405 from ubuntu_ltp/cve are actually the same test. Issue found on F-oem-5.10.0-1051.53 With LTP upstream head SHA1 2ac54d426 This is not a regression, it's because of a recent update that enables this test on different filesystems: https://github.com/linux-test-project/ltp/commit/433b6cf7ade3d5e3bd4b85ac89b164c53312e65a Test failed on XFS with: tst_test.c:1431: TINFO: Testing on xfs tst_test.c:932: TINFO: Formatting /dev/loop3 with xfs opts='' extra opts='' tst_test.c:1363: TINFO: Timeout per run is 0h 05m 00s creat09.c:55: TINFO: User nobody: uid = 65534, gid = 65534 creat09.c:57: TINFO: Found unused GID 11: SUCCESS (0) creat09.c:88: TPASS: mntpoint/testdir/creat.tmp: Owned by correct group creat09.c:92: TFAIL: mntpoint/testdir/creat.tmp: Setgid bit is set creat09.c:88: TPASS: mntpoint/testdir/open.tmp: Owned by correct group creat09.c:92: TFAIL: mntpoint/testdir/open.tmp: Setgid bit is set Test log: Checking for required user/group ids 'nobody' user id and group found. 'bin' user id and group found. 'daemon' user id and group found. Users group found. Sys group found. Required users/groups exist. no big block device was specified on commandline. Tests which require a big block device are disabled. You can specify it with option -z INFO: Test start time: Mon Nov 8 10:00:06 UTC 2021 COMMAND:/opt/ltp/bin/ltp-pan -q -e -S -a 61758 -n 61758 -f /tmp/ltp-shLYORuoRT/alltests -l /dev/null -C /dev/null -T /dev/null LOG File: /dev/null FAILED COMMAND File: /dev/null TCONF COMMAND File: /dev/null Running tests... tst_device.c:88: TINFO: Found free device 3 '/dev/loop3' tst_supported_fs_types.c:88: TINFO: Kernel supports ext2 tst_supported_fs_types.c:50: TINFO: mkfs.ext2 does exist tst_supported_fs_types.c:88: TINFO: Kernel supports ext3 tst_supported_fs_types.c:50: TINFO: mkfs.ext3 does exist tst_supported_fs_types.c:88: TINFO: Kernel supports ext4 tst_supported_fs_types.c:50: TINFO: mkfs.ext4 does exist tst_supported_fs_types.c:88: TINFO: Kernel supports xfs tst_supported_fs_types.c:50: TINFO: mkfs.xfs does exist tst_supported_fs_types.c:88: TINFO: Kernel supports btrfs tst_supported_fs_types.c:50: TINFO: mkfs.btrfs does exist tst_supported_fs_types.c:146: TINFO: Skipping vfat as requested by the test tst_supported_fs_types.c:146: TINFO: Skipping exfat as requested by the test tst_supported_fs_types.c:88: TINFO: Kernel supports tmpfs tst_supported_fs_types.c:37: TINFO: mkfs is not needed for tmpfs tst_test.c:1431: TINFO: Testing on ext2 tst_test.c:932: TINFO: Formatting /dev/loop3 with ext2 opts='' extra opts='' mke2fs 1.45.5 (07-Jan-2020) tst_test.c:1363: TINFO: Timeout per run is 0h 05m 00s creat09.c:55: TINFO: User nobody: uid = 65534, gid = 65534 creat09.c:57: TINFO: Found unused GID 11: SUCCESS (0) creat09.c:88: TPASS: mntpoint/testdir/creat.tmp: Owned by correct group creat09.c:94: TPASS: mntpoint/testdir/creat.tmp: Setgid bit not set creat09.c:88: TPASS: mntpoint/testdir/open.tmp: Owned by correct group creat09.c:94: TPASS: mntpoint/testdir/open.tmp: Setgid bit not set tst_test.c:1431: TINFO: Testing on ext3 tst_test.c:932: TINFO: Formatting /dev/loop3 with ext3 opts='' extra opts='' mke2fs 1.45.5 (07-Jan-2020) tst_test.c:1363: TINFO: Timeout per run is 0h 05m 00s creat09.c:55: TINFO: User nobody: uid = 65534, gid = 65534 creat09.c:57: TINFO: Found unused GID 11: SUCCESS (0) creat09.c:88: TPASS: mntpoint/testdir/creat.tmp: Owned by correct group creat09.c:94: TPASS: mntpoint/testdir/creat.tmp: Setgid bit not set creat09.c:88: TPASS: mntpoint/testdir/open.tmp: Owned by correct group creat09.c:94: TPASS: mntpoint/testdir/open.tmp: Setgid bit not set tst_test.c:1431: TINFO: Testing on ext4 tst_test.c:932: TINFO: Formatting /dev/loop3 with ext4 opts='' extra opts='' mke2fs 1.45.5 (07-Jan-2020) tst_test.c:1363: TINFO: Timeout per run is 0h 05m 00s creat09.c:55: TINFO: User nobody: uid = 65534, gid = 65534 creat09.c:57: TINFO: Found unused GID 11: SUCCESS (0) creat09.c:88: TPASS: mntpoint/testdir/creat.tmp: Owned by correct group creat09.c:94: TPASS: mntpoint/testdir/creat.tmp: Setgid bit
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-azure/5.4.0.1064.62)
All autopkgtests for the newly accepted linux-meta-azure (5.4.0.1064.62) for focal have finished running. The following regressions have been reported in tests triggered by the package: v4l2loopback/0.12.3-1ubuntu0.4 (amd64) dahdi-linux/1:2.11.1~dfsg-1ubuntu6.3 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#linux-meta-azure [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Confirmed Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Invalid Status in linux-azure-edge source package in Precise: Invalid Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Invalid Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Confirmed Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packing resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1945590] Re: Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled
here's dmesg after starting with Andrea's kernel, need any more information? ** Attachment added: "dmesg.2020.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945590/+attachment/5539604/+files/dmesg.2020.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/1945590 Title: Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled Status in linux package in Ubuntu: Confirmed Status in linux source package in Impish: Confirmed Bug description: I installed the Ubuntu 21.10 beta and as soon as I boot I get the kernel panic that I am attaching. I also installed Ubuntu 21.04 and upgraded, as soon as I boot with the 5.13 kernel I get the same problem, disabling the trackpad and trackpoint in the bios the problem disappears. Everything works with the 5.11 kernel. I remain available for further details and sorry for my lack of experience. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-16-generic 5.13.0-16.16 ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pietro 1810 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Sep 30 10:26:10 2021 InstallationDate: Installed on 2021-09-29 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: LENOVO 20TA0033IX ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-16-generic root=UUID=b5ea9465-4cd9-408b-8e30-458acf90181b ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.13.0-16-generic N/A linux-backports-modules-5.13.0-16-generic N/A linux-firmware 1.201 SourcePackage: linux UpgradeStatus: Upgraded to impish on 2021-09-29 (0 days ago) dmi.bios.date: 09/02/2021 dmi.bios.release: 1.43 dmi.bios.vendor: LENOVO dmi.bios.version: R1EET43W(1.43 ) dmi.board.asset.tag: Not Available dmi.board.name: 20TA0033IX 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.43 dmi.modalias: dmi:bvnLENOVO:bvrR1EET43W(1.43):bd09/02/2021:br1.43:efr1.43:svnLENOVO:pn20TA0033IX:pvrThinkPadE14Gen2:skuLENOVO_MT_20TA_BU_Think_FM_ThinkPadE14Gen2:rvnLENOVO:rn20TA0033IX:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad E14 Gen 2 dmi.product.name: 20TA0033IX dmi.product.sku: LENOVO_MT_20TA_BU_Think_FM_ThinkPad E14 Gen 2 dmi.product.version: ThinkPad E14 Gen 2 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945590/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1936295] Re: Faulty Elantech Trackpoint firmware unusable as it causes sudden cursor jump to an edge/corner on Lenovo Thinkpad X13, T14s, A475 --> Apply kernel patch to mitigate
Hello the patch was merged in the kernel maintainer's branch yesterday: https://git.kernel.org/pub/scm/linux/kernel/git/dtor/input.git/commit/?id=be896bd3b72b44126c55768f14c22a8729b0992e I confirm that it works in Linux 5.14 and 5.15 -- 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/1936295 Title: Faulty Elantech Trackpoint firmware unusable as it causes sudden cursor jump to an edge/corner on Lenovo Thinkpad X13, T14s, A475 --> Apply kernel patch to mitigate the FW bug Status in linux package in Ubuntu: Confirmed Bug description: *Problem description:* On Lenovo Thinkpad T14s, X13, A475 (and probably more models) the Elantech Trackpoint firmware is defective. The trackpoint cursor often suddenly jumps to an edge/corner, because the hardware/firmware sometimes reports wrong coordinates / loses sync. Currently, the Trackpoint is barely usable and it's impossible to productively work using it. For a long while, Elantech has not yet put forward (nor confirmed) a firmware update. However, there is a Linux kernel patch mitigating the firmware bug. The kernel bugfix discards the wrongly reported packages by the Elantech hardware. This solves the problem for the user. *Solution:* Please apply existing kernel patch here. https://bugzilla.kernel.org/show_bug.cgi?id=209167 Bug entry in the Linux Kernel.org Bugzilla https://bugzilla.kernel.org/attachment.cgi?id=295733=diff Diff of bugfix *T14s and X13 are Ubuntu certified:* The Lenovo Thinkpad T14s and X13 are Ubuntu certified, but apparently this hardware issue has slipped the Ubuntu certification process! https://ubuntu.com/certified/202006-27978 and https://ubuntu.com/certified/202006-27979 *Further information:* https://forums.lenovo.com/t5/Fedora/T14s-AMD-Trackpoint-almost-unusable/m-p/5064952?page=1 Discussion on the bug in the Lenovo forum. E.g. see comment 18 by Lenovo employee MarkRHPearson *My System:* Lenovo Thinkpad T14s (AMD) 20ujs00k00 Ubuntu 21.04 and 20.04 see entries in kernel.org bugzilla for logs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1936295/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-azure-4.15/4.15.0.1127.100)
All autopkgtests for the newly accepted linux-meta-azure-4.15 (4.15.0.1127.100) for bionic have finished running. The following regressions have been reported in tests triggered by the package: systemd/237-3ubuntu10.52 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-meta-azure-4.15 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Confirmed Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Invalid Status in linux-azure-edge source package in Precise: Invalid Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Invalid Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Confirmed Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packing resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1950472] Re: The wifi adapter is not detected anymore during boot
This is most likely the same bug as: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950448 which is already reported here: https://bugzilla.kernel.org/show_bug.cgi?id=214455 and traced back to commit: 3f38cc1ba1e289306f52cb7238406f38ecbfa21a net: qrtr: make checks in qrtr_endpoint_post() stricter ** Bug watch added: Linux Kernel Bug Tracker #214455 https://bugzilla.kernel.org/show_bug.cgi?id=214455 -- 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/1950472 Title: The wifi adapter is not detected anymore during boot Status in linux package in Ubuntu: Confirmed Bug description: Last working version: 5.13.0-20-generic Not working: 5.13.0-21-generic Notebook: Dell XPS 15 Wifi adapter: Qualcomm QCA6390 Wireless Network Adapter [AX500-DBS (2x2)] (rev 01) After booting 5.13.0-21-generic the wifi adapter is not detected anymore (missing from lspci). I have to turn off the computer and boot an older kernel. Simple restart doesn't work. With 5.13.0-20-generic the driver is just loaded fine: lsmod | grep ath11k ath11k_pci 24576 0 ath11k413696 1 ath11k_pci qmi_helpers28672 1 ath11k mac80211 1024000 1 ath11k cfg80211 892928 2 ath11k,mac80211 mhi73728 2 ath11k_pci,qrtr_mhi ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-20-generic 5.13.0-20.20 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Uname: Linux 5.13.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tim 17241 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Nov 10 15:02:43 2021 InstallationDate: Installed on 2021-11-01 (9 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: Dell Inc. XPS 15 9500 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-20-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.13.0-20-generic N/A linux-backports-modules-5.13.0-20-generic N/A linux-firmware 1.201.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/11/2021 dmi.bios.release: 1.9 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.9.1 dmi.board.name: 0XWT2F dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.9.1:bd08/11/2021:br1.9:svnDellInc.:pnXPS159500:pvr:sku097D:rvnDellInc.:rn0XWT2F:rvrA02:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9500 dmi.product.sku: 097D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950472/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1950388] Re: Impish update: upstream stable patchset 2021-11-09
** Changed in: linux (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 in Ubuntu. https://bugs.launchpad.net/bugs/1950388 Title: Impish update: upstream stable patchset 2021-11-09 Status in linux package in Ubuntu: Invalid Status in linux source package in Impish: 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 2021-11-09 Ported from the following upstream stable releases: v5.10.71, v5.14.10 from git://git.kernel.org/ tty: Fix out-of-bound vmalloc access in imageblit cpufreq: schedutil: Use kobject release() method to free sugov_tunables scsi: qla2xxx: Changes to support kdump kernel for NVMe BFS cpufreq: schedutil: Destroy mutex before kobject_put() frees the memory ACPI: NFIT: Use fallback node id when numa info in NFIT table is incorrect fs-verity: fix signed integer overflow with i_size near S64_MAX hwmon: (tmp421) handle I2C errors hwmon: (w83793) Fix NULL pointer dereference by removing unnecessary structure field hwmon: (w83792d) Fix NULL pointer dereference by removing unnecessary structure field hwmon: (w83791d) Fix NULL pointer dereference by removing unnecessary structure field gpio: pca953x: do not ignore i2c errors scsi: ufs: Fix illegal offset in UPIU event trace mac80211: fix use-after-free in CCMP/GCMP RX x86/kvmclock: Move this_cpu_pvti into kvmclock.h KVM: x86: Fix stack-out-of-bounds memory access from ioapic_write_indirect() KVM: x86: nSVM: don't copy virt_ext from vmcb12 KVM: nVMX: Filter out all unsupported controls when eVMCS was activated media: ir_toy: prevent device from hanging during transmit RDMA/cma: Do not change route.addr.src_addr.ss_family drm/amd/display: Pass PCI deviceid into DC drm/amdgpu: correct initial cp_hqd_quantum for gfx9 ipvs: check that ip_vs_conn_tab_bits is between 8 and 20 bpf: Handle return value of BPF_PROG_TYPE_STRUCT_OPS prog IB/cma: Do not send IGMP leaves for sendonly Multicast groups RDMA/cma: Fix listener leak in rdma_cma_listen_on_all() failure bpf, mips: Validate conditional branch offsets hwmon: (mlxreg-fan) Return non-zero value when fan current state is enforced from sysfs mac80211: Fix ieee80211_amsdu_aggregate frag_tail bug mac80211: limit injected vht mcs/nss in ieee80211_parse_tx_radiotap mac80211: mesh: fix potentially unaligned access mac80211-hwsim: fix late beacon hrtimer handling sctp: break out if skb_header_pointer returns NULL in sctp_rcv_ootb mptcp: don't return sockets in foreign netns hwmon: (tmp421) report /PVLD condition as fault hwmon: (tmp421) fix rounding for negative values net: enetc: fix the incorrect clearing of IF_MODE bits net: ipv4: Fix rtnexthop len when RTA_FLOW is present smsc95xx: fix stalled rx after link change drm/i915/request: fix early tracepoints dsa: mv88e6xxx: 6161: Use chip wide MAX MTU dsa: mv88e6xxx: Fix MTU definition dsa: mv88e6xxx: Include tagger overhead when setting MTU for DSA and CPU ports e100: fix length calculation in e100_get_regs_len e100: fix buffer overrun in e100_get_regs bpf: Exempt CAP_BPF from checks against bpf_jit_limit selftests, bpf: Fix makefile dependencies on libbpf selftests, bpf: test_lwt_ip_encap: Really disable rp_filter UBUNTU: [Config] updateconfigs for ks8851 modules net: ks8851: fix link error scsi: csiostor: Add module softdep on cxgb4 ixgbe: Fix NULL pointer dereference in ixgbe_xdp_setup net: hns3: do not allow call hns3_nic_net_open repeatedly net: hns3: fix mixed flag HCLGE_FLAG_MQPRIO_ENABLE and HCLGE_FLAG_DCB_ENABLE net: hns3: fix show wrong state when add existing uc mac address net: hns3: reconstruct function hns3_self_test net: hns3: fix always enable rx vlan filter problem after selftest net: phy: bcm7xxx: Fixed indirect MMD operations net: sched: flower: protect fl_walk() with rcu af_unix: fix races in sk_peer_pid and sk_peer_cred accesses perf/x86/intel: Update event constraints for ICX hwmon: (pmbus/mp2975) Add missed POUT attribute for page 1 mp2975 controller nvme: add command id quirk for apple controllers elf: don't use MAP_FIXED_NOREPLACE for elf interpreter mappings debugfs: debugfs_create_file_size(): use IS_ERR to check for error ipack: ipoctal: fix stack information leak ipack: ipoctal: fix tty registration race ipack: ipoctal: fix tty-registration error
[Kernel-packages] [Bug 1950472] 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/1950472 Title: The wifi adapter is not detected anymore during boot Status in linux package in Ubuntu: Confirmed Bug description: Last working version: 5.13.0-20-generic Not working: 5.13.0-21-generic Notebook: Dell XPS 15 Wifi adapter: Qualcomm QCA6390 Wireless Network Adapter [AX500-DBS (2x2)] (rev 01) After booting 5.13.0-21-generic the wifi adapter is not detected anymore (missing from lspci). I have to turn off the computer and boot an older kernel. Simple restart doesn't work. With 5.13.0-20-generic the driver is just loaded fine: lsmod | grep ath11k ath11k_pci 24576 0 ath11k413696 1 ath11k_pci qmi_helpers28672 1 ath11k mac80211 1024000 1 ath11k cfg80211 892928 2 ath11k,mac80211 mhi73728 2 ath11k_pci,qrtr_mhi ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-20-generic 5.13.0-20.20 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Uname: Linux 5.13.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tim 17241 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Nov 10 15:02:43 2021 InstallationDate: Installed on 2021-11-01 (9 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: Dell Inc. XPS 15 9500 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-20-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.13.0-20-generic N/A linux-backports-modules-5.13.0-20-generic N/A linux-firmware 1.201.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/11/2021 dmi.bios.release: 1.9 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.9.1 dmi.board.name: 0XWT2F dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.9.1:bd08/11/2021:br1.9:svnDellInc.:pnXPS159500:pvr:sku097D:rvnDellInc.:rn0XWT2F:rvrA02:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9500 dmi.product.sku: 097D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950472/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1950472] [NEW] The wifi adapter is not detected anymore during boot
Public bug reported: Last working version: 5.13.0-20-generic Not working: 5.13.0-21-generic Notebook: Dell XPS 15 Wifi adapter: Qualcomm QCA6390 Wireless Network Adapter [AX500-DBS (2x2)] (rev 01) After booting 5.13.0-21-generic the wifi adapter is not detected anymore (missing from lspci). I have to turn off the computer and boot an older kernel. Simple restart doesn't work. With 5.13.0-20-generic the driver is just loaded fine: lsmod | grep ath11k ath11k_pci 24576 0 ath11k413696 1 ath11k_pci qmi_helpers28672 1 ath11k mac80211 1024000 1 ath11k cfg80211 892928 2 ath11k,mac80211 mhi73728 2 ath11k_pci,qrtr_mhi ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-20-generic 5.13.0-20.20 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Uname: Linux 5.13.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tim 17241 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Nov 10 15:02:43 2021 InstallationDate: Installed on 2021-11-01 (9 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: Dell Inc. XPS 15 9500 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-20-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.13.0-20-generic N/A linux-backports-modules-5.13.0-20-generic N/A linux-firmware 1.201.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/11/2021 dmi.bios.release: 1.9 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.9.1 dmi.board.name: 0XWT2F dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.9.1:bd08/11/2021:br1.9:svnDellInc.:pnXPS159500:pvr:sku097D:rvnDellInc.:rn0XWT2F:rvrA02:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9500 dmi.product.sku: 097D dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish 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/1950472 Title: The wifi adapter is not detected anymore during boot Status in linux package in Ubuntu: New Bug description: Last working version: 5.13.0-20-generic Not working: 5.13.0-21-generic Notebook: Dell XPS 15 Wifi adapter: Qualcomm QCA6390 Wireless Network Adapter [AX500-DBS (2x2)] (rev 01) After booting 5.13.0-21-generic the wifi adapter is not detected anymore (missing from lspci). I have to turn off the computer and boot an older kernel. Simple restart doesn't work. With 5.13.0-20-generic the driver is just loaded fine: lsmod | grep ath11k ath11k_pci 24576 0 ath11k413696 1 ath11k_pci qmi_helpers28672 1 ath11k mac80211 1024000 1 ath11k cfg80211 892928 2 ath11k,mac80211 mhi73728 2 ath11k_pci,qrtr_mhi ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-20-generic 5.13.0-20.20 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Uname: Linux 5.13.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tim 17241 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Nov 10 15:02:43 2021 InstallationDate: Installed on 2021-11-01 (9 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: Dell Inc. XPS 15 9500 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-20-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.13.0-20-generic N/A linux-backports-modules-5.13.0-20-generic N/A linux-firmware 1.201.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/11/2021 dmi.bios.release: 1.9 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.9.1 dmi.board.name: 0XWT2F dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.9.1:bd08/11/2021:br1.9:svnDellInc.:pnXPS159500:pvr:sku097D:rvnDellInc.:rn0XWT2F:rvrA02:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9500 dmi.product.sku: 097D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go
[Kernel-packages] [Bug 1937078] Re: Drivers: hv: vmbus: Fix duplicate CPU assignments within a device
Microsoft verified the patch in
(https://lists.ubuntu.com/archives/kernel-
team/2021-November/125347.html) fixes the bug.
** Tags removed: verification-needed-focal
** Tags added: verification-done-focal
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1937078
Title:
Drivers: hv: vmbus: Fix duplicate CPU assignments within a device
Status in linux-azure package in Ubuntu:
Incomplete
Status in linux-azure source package in Focal:
Fix Committed
Status in linux-azure source package in Hirsute:
Fix Released
Bug description:
SRU Justification
[Impact]
Customers have degraded network performance on Hyper-V/Azure
This is a request to pick up a patch from the upstream, the patch
fixes an issue with Ubuntu as a hyper-v and Azure guest. This patch
need to get picked up for 20.04, 18.04. The link to the upstream patch
follows:
https://git.kernel.org/pub/scm/linux/kernel/git/hyperv/linux.git/commit/?h=hyperv-
fixes=7c9ff3d61b253715dcf968a6307af148c9b2
Description of issue and solution:
The vmbus module uses a rotational algorithm to assign target CPUs to
a device's channels. Depending on the timing of different device's channel
offers, different channels of a device may be assigned to the same CPU.
For example on a VM with 2 CPUs, if NIC A and B's channels are offered
in the following order, NIC A will have both channels on CPU0, and
NIC B will have both channels on CPU1 -- see below. This kind of
assignment causes RSS load that is spreading across different channels
to end up on the same CPU.
Timing of channel offers:
NIC A channel 0
NIC B channel 0
NIC A channel 1
NIC B channel 1
VMBUS ID 14: Class_ID = {f8615163-df3e-46c5-913f-f2d2f965ed0e} - Synthetic
network adapter
Device_ID = {cab064cd-1f31-47d5-a8b4-9d57e320cccd}
Sysfs path: /sys/bus/vmbus/devices/cab064cd-1f31-47d5-a8b4-9d57e320cccd
Rel_ID=14, target_cpu=0
Rel_ID=17, target_cpu=0
VMBUS ID 16: Class_ID = {f8615163-df3e-46c5-913f-f2d2f965ed0e} - Synthetic
network adapter
Device_ID = {244225ca-743e-4020-a17d-d7baa13d6cea}
Sysfs path: /sys/bus/vmbus/devices/244225ca-743e-4020-a17d-d7baa13d6cea
Rel_ID=16, target_cpu=1
Rel_ID=18, target_cpu=1
Update the vmbus CPU assignment algorithm to avoid duplicate CPU
assignments within a device.
The new algorithm iterates num_online_cpus + 1 times.
The existing rotational algorithm to find "next NUMA & CPU" is still here.
But if the resulting CPU is already used by the same device, it will try
the next CPU.
In the last iteration, it assigns the channel to the next available CPU
like the existing algorithm. This is not normally expected, because
during device probe, we limit the number of channels of a device to
be <= number of online CPUs.
[Test Plan]
This could be tough to test as the patch fixes a race condition.
[Where problems could occur]
Network performance issues could persist.
[Other Info]
SF:#00315347
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1937078/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1949329] Re: [SRU] alsa-lib: ucm: Regex returns correct value without matching a string
This bug was fixed in the package alsa-lib - 1.2.2-2.1ubuntu2.5 --- alsa-lib (1.2.2-2.1ubuntu2.5) focal; urgency=medium * d/p/0001-ucm-fix-regexec-REG_NOMATCH-state-handling-for-defin.patch - ucm: Fix a Regex parser bug, when there is no match, need to set err to 0, otherwise, the caller will get a wrong match instead of no match. (LP: #1949329) -- Hui Wang Mon, 01 Nov 2021 15:25:07 +0800 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1949329 Title: [SRU] alsa-lib: ucm: Regex returns correct value without matching a string Status in HWE Next: New Status in alsa-lib package in Ubuntu: Fix Released Status in alsa-lib source package in Focal: Fix Released Status in alsa-lib source package in Hirsute: Fix Released Status in alsa-lib source package in Impish: Fix Released Status in alsa-lib source package in Jammy: Fix Released Bug description: [Impact] In the Dell project, we tried to enable the audio on a machine, the machine has the soundwire audio design, it needs to load the ucm correctly, then users could see the audio devices from gnome. But on this machine, the ucm can't be loaded, through debugging, we found this machine has no headset, the Regex returns a wrong value when matching "Regex " hs:([a-z0-9]+(-sdca)?)". If let Regex returns a correct value, the ucm could be loaded successfully. [Fix] Backport a commit from upstream, this commit is merged to upstream from v1.2.5 [Test] After installed the patched libasound2, reboot, we could see the ucm is loaded succesfully on this machine, and open the gnome-sound-setting, we could see the internal mic and internal speaker, and all of them could work normally. [Where problems will occur] This change affect the Regex parser in the ucm, so if it could introduce regression, it will be on the ucm. It could make the audio not work (fail to load ucm and users can't see any audio devices from gnome) on the machines which need ucm. But this possibility is very low, since this commit is backported from upstream and we already tested this backporting on 2 lenovo machines and 2 Dell machines which all need ucm to work. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1949329/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-snapdragon/4.15.0.1116.119)
All autopkgtests for the newly accepted linux-meta-snapdragon (4.15.0.1116.119) for bionic have finished running. The following regressions have been reported in tests triggered by the package: lxd/3.0.3-0ubuntu1~18.04.1 (arm64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-meta-snapdragon [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Confirmed Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Invalid Status in linux-azure-edge source package in Precise: Invalid Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Invalid Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Confirmed Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packing resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1949329] Re: [SRU] alsa-lib: ucm: Regex returns correct value without matching a string
This bug was fixed in the package alsa-lib - 1.2.4-1.1ubuntu2.1 --- alsa-lib (1.2.4-1.1ubuntu2.1) hirsute; urgency=medium * d/p/0001-ucm-fix-regexec-REG_NOMATCH-state-handling-for-defin.patch - ucm: Fix a Regex parser bug, when there is no match, need to set err to 0, otherwise, the caller will get a wrong match instead of no match. (LP: #1949329) -- Hui Wang Mon, 01 Nov 2021 15:17:07 +0800 ** Changed in: alsa-lib (Ubuntu Hirsute) Status: Fix Committed => Fix Released ** Changed in: alsa-lib (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-lib in Ubuntu. https://bugs.launchpad.net/bugs/1949329 Title: [SRU] alsa-lib: ucm: Regex returns correct value without matching a string Status in HWE Next: New Status in alsa-lib package in Ubuntu: Fix Released Status in alsa-lib source package in Focal: Fix Released Status in alsa-lib source package in Hirsute: Fix Released Status in alsa-lib source package in Impish: Fix Released Status in alsa-lib source package in Jammy: Fix Released Bug description: [Impact] In the Dell project, we tried to enable the audio on a machine, the machine has the soundwire audio design, it needs to load the ucm correctly, then users could see the audio devices from gnome. But on this machine, the ucm can't be loaded, through debugging, we found this machine has no headset, the Regex returns a wrong value when matching "Regex " hs:([a-z0-9]+(-sdca)?)". If let Regex returns a correct value, the ucm could be loaded successfully. [Fix] Backport a commit from upstream, this commit is merged to upstream from v1.2.5 [Test] After installed the patched libasound2, reboot, we could see the ucm is loaded succesfully on this machine, and open the gnome-sound-setting, we could see the internal mic and internal speaker, and all of them could work normally. [Where problems will occur] This change affect the Regex parser in the ucm, so if it could introduce regression, it will be on the ucm. It could make the audio not work (fail to load ucm and users can't see any audio devices from gnome) on the machines which need ucm. But this possibility is very low, since this commit is backported from upstream and we already tested this backporting on 2 lenovo machines and 2 Dell machines which all need ucm to work. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1949329/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1949329] Re: [SRU] alsa-lib: ucm: Regex returns correct value without matching a string
This bug was fixed in the package alsa-lib - 1.2.4-1.1ubuntu3.1 --- alsa-lib (1.2.4-1.1ubuntu3.1) impish; urgency=medium * d/p/0001-ucm-fix-regexec-REG_NOMATCH-state-handling-for-defin.patch - ucm: Fix a Regex parser bug, when there is no match, need to set err to 0, otherwise, the caller will get a wrong match instead of no match. (LP: #1949329) -- Hui Wang Mon, 01 Nov 2021 15:05:47 +0800 ** Changed in: alsa-lib (Ubuntu Impish) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1949329 Title: [SRU] alsa-lib: ucm: Regex returns correct value without matching a string Status in HWE Next: New Status in alsa-lib package in Ubuntu: Fix Released Status in alsa-lib source package in Focal: Fix Released Status in alsa-lib source package in Hirsute: Fix Released Status in alsa-lib source package in Impish: Fix Released Status in alsa-lib source package in Jammy: Fix Released Bug description: [Impact] In the Dell project, we tried to enable the audio on a machine, the machine has the soundwire audio design, it needs to load the ucm correctly, then users could see the audio devices from gnome. But on this machine, the ucm can't be loaded, through debugging, we found this machine has no headset, the Regex returns a wrong value when matching "Regex " hs:([a-z0-9]+(-sdca)?)". If let Regex returns a correct value, the ucm could be loaded successfully. [Fix] Backport a commit from upstream, this commit is merged to upstream from v1.2.5 [Test] After installed the patched libasound2, reboot, we could see the ucm is loaded succesfully on this machine, and open the gnome-sound-setting, we could see the internal mic and internal speaker, and all of them could work normally. [Where problems will occur] This change affect the Regex parser in the ucm, so if it could introduce regression, it will be on the ucm. It could make the audio not work (fail to load ucm and users can't see any audio devices from gnome) on the machines which need ucm. But this possibility is very low, since this commit is backported from upstream and we already tested this backporting on 2 lenovo machines and 2 Dell machines which all need ucm to work. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1949329/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1949329] Update Released
The verification of the Stable Release Update for alsa-lib 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-lib in Ubuntu. https://bugs.launchpad.net/bugs/1949329 Title: [SRU] alsa-lib: ucm: Regex returns correct value without matching a string Status in HWE Next: New Status in alsa-lib package in Ubuntu: Fix Released Status in alsa-lib source package in Focal: Fix Released Status in alsa-lib source package in Hirsute: Fix Released Status in alsa-lib source package in Impish: Fix Released Status in alsa-lib source package in Jammy: Fix Released Bug description: [Impact] In the Dell project, we tried to enable the audio on a machine, the machine has the soundwire audio design, it needs to load the ucm correctly, then users could see the audio devices from gnome. But on this machine, the ucm can't be loaded, through debugging, we found this machine has no headset, the Regex returns a wrong value when matching "Regex " hs:([a-z0-9]+(-sdca)?)". If let Regex returns a correct value, the ucm could be loaded successfully. [Fix] Backport a commit from upstream, this commit is merged to upstream from v1.2.5 [Test] After installed the patched libasound2, reboot, we could see the ucm is loaded succesfully on this machine, and open the gnome-sound-setting, we could see the internal mic and internal speaker, and all of them could work normally. [Where problems will occur] This change affect the Regex parser in the ucm, so if it could introduce regression, it will be on the ucm. It could make the audio not work (fail to load ucm and users can't see any audio devices from gnome) on the machines which need ucm. But this possibility is very low, since this commit is backported from upstream and we already tested this backporting on 2 lenovo machines and 2 Dell machines which all need ucm to work. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1949329/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1949357] Re: linux-azure: make mana.ko built-in
wget https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/ppa/+files/linux-buildinfo-5.4.0-1064-azure_5.4.0-1064.67_amd64.deb dpkg -x linux-buildinfo-5.4.0-1064-azure_5.4.0-1064.67_amd64.deb . grep CONFIG_MICROSOFT_MANA usr/lib/linux/5.4.0-1064-azure/config CONFIG_MICROSOFT_MANA=y ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1949357 Title: linux-azure: make mana.ko built-in Status in linux-azure package in Ubuntu: In Progress Status in linux-azure source package in Focal: Fix Committed Status in linux-azure source package in Hirsute: Fix Committed Status in linux-azure source package in Impish: Fix Committed Status in linux-azure source package in Jammy: In Progress Bug description: SRU Justification [Impact] The new networking module mana.ko is not included with linux-modules, rather it is packaged in linux-modules-extra. Instance types that have mana.ko as a boot dependency will not work since Azure images are not created using linux-image-extra. [Test Plan] Download linux-modules and check for mana.ko [Where problems could occur] mana.ko could go missing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1949357/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1937078] Re: Drivers: hv: vmbus: Fix duplicate CPU assignments within a device
This bug is awaiting verification that the linux-azure/5.4.0-1064.67
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/1937078
Title:
Drivers: hv: vmbus: Fix duplicate CPU assignments within a device
Status in linux-azure package in Ubuntu:
Incomplete
Status in linux-azure source package in Focal:
Fix Committed
Status in linux-azure source package in Hirsute:
Fix Released
Bug description:
SRU Justification
[Impact]
Customers have degraded network performance on Hyper-V/Azure
This is a request to pick up a patch from the upstream, the patch
fixes an issue with Ubuntu as a hyper-v and Azure guest. This patch
need to get picked up for 20.04, 18.04. The link to the upstream patch
follows:
https://git.kernel.org/pub/scm/linux/kernel/git/hyperv/linux.git/commit/?h=hyperv-
fixes=7c9ff3d61b253715dcf968a6307af148c9b2
Description of issue and solution:
The vmbus module uses a rotational algorithm to assign target CPUs to
a device's channels. Depending on the timing of different device's channel
offers, different channels of a device may be assigned to the same CPU.
For example on a VM with 2 CPUs, if NIC A and B's channels are offered
in the following order, NIC A will have both channels on CPU0, and
NIC B will have both channels on CPU1 -- see below. This kind of
assignment causes RSS load that is spreading across different channels
to end up on the same CPU.
Timing of channel offers:
NIC A channel 0
NIC B channel 0
NIC A channel 1
NIC B channel 1
VMBUS ID 14: Class_ID = {f8615163-df3e-46c5-913f-f2d2f965ed0e} - Synthetic
network adapter
Device_ID = {cab064cd-1f31-47d5-a8b4-9d57e320cccd}
Sysfs path: /sys/bus/vmbus/devices/cab064cd-1f31-47d5-a8b4-9d57e320cccd
Rel_ID=14, target_cpu=0
Rel_ID=17, target_cpu=0
VMBUS ID 16: Class_ID = {f8615163-df3e-46c5-913f-f2d2f965ed0e} - Synthetic
network adapter
Device_ID = {244225ca-743e-4020-a17d-d7baa13d6cea}
Sysfs path: /sys/bus/vmbus/devices/244225ca-743e-4020-a17d-d7baa13d6cea
Rel_ID=16, target_cpu=1
Rel_ID=18, target_cpu=1
Update the vmbus CPU assignment algorithm to avoid duplicate CPU
assignments within a device.
The new algorithm iterates num_online_cpus + 1 times.
The existing rotational algorithm to find "next NUMA & CPU" is still here.
But if the resulting CPU is already used by the same device, it will try
the next CPU.
In the last iteration, it assigns the channel to the next available CPU
like the existing algorithm. This is not normally expected, because
during device probe, we limit the number of channels of a device to
be <= number of online CPUs.
[Test Plan]
This could be tough to test as the patch fixes a race condition.
[Where problems could occur]
Network performance issues could persist.
[Other Info]
SF:#00315347
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1937078/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1949357] Re: linux-azure: make mana.ko built-in
This bug is awaiting verification that the linux-azure/5.4.0-1064.67 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/1949357 Title: linux-azure: make mana.ko built-in Status in linux-azure package in Ubuntu: In Progress Status in linux-azure source package in Focal: Fix Committed Status in linux-azure source package in Hirsute: Fix Committed Status in linux-azure source package in Impish: Fix Committed Status in linux-azure source package in Jammy: In Progress Bug description: SRU Justification [Impact] The new networking module mana.ko is not included with linux-modules, rather it is packaged in linux-modules-extra. Instance types that have mana.ko as a boot dependency will not work since Azure images are not created using linux-image-extra. [Test Plan] Download linux-modules and check for mana.ko [Where problems could occur] mana.ko could go missing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1949357/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1950462] Re: Focal linux-azure: Vm crash on Dv5/Ev5
** Tags added: bot-stop-nagging -- 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/1950462 Title: Focal linux-azure: Vm crash on Dv5/Ev5 Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux source package in Focal: In Progress Status in linux-azure source package in Focal: In Progress Bug description: SRU Justification [Impact] We are seeing a below crash for Nested VM scenario in Dv5/Ev5. [ 284.769421] [ cut here ] [ 284.769422] KVM: accessing unsupported EVMCS field 2032 [ 284.769443] WARNING: CPU: 30 PID: 8426 at /build/linux-azure-5.4-YivnXz/linux-azure-5.4-5.4.0/arch/x86/kvm/vmx/evmcs.h:85 evmcs_write64+0x65/0x70 [kvm_intel] [ 284.769443] Modules linked in: vhost_net vhost tap ipt_REJECT nf_reject_ipv4 xt_tcpudp iptable_filter xt_MASQUERADE iptable_nat nf_nat bridge stp llc xt_owner xt_conntrack nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 iptable_security bpfilter udf crc_itu_t nls_iso8859_1 kvm_intel kvm serio_raw hv_balloon joydev sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear hid_generic crct10dif_pclmul hid_hyperv crc32_pclmul ghash_clmulni_intel aesni_intel crypto_simd cryptd hyperv_fb cfbfillrect glue_helper cfbimgblt hid hv_netvsc hv_utils hyperv_keyboard cfbcopyarea [ 284.769463] CPU: 30 PID: 8426 Comm: qemu-system-x86 Not tainted 5.4.0-1062-azure #65~18.04.1-Ubuntu [ 284.769464] Hardware name: Microsoft Corporation Virtual Machine/Virtual Machine, BIOS Hyper-V UEFI Release v4.1 07/22/2021 [ 284.769467] RIP: 0010:evmcs_write64+0x65/0x70 [kvm_intel] [ 284.769469] Code: c2 f7 d0 21 81 38 03 00 00 5d c3 80 3d 1c 32 03 00 00 75 f5 48 89 fe 48 c7 c7 f8 63 57 c0 c6 05 09 32 03 00 01 e8 eb d1 53 cd <0f> 0b 5d c3 0f 1f 80 00 00 00 00 0f 1f 44 00 00 48 8b 07 80 b8 ea [ 284.769469] RSP: 0018:b75a03f0fb68 EFLAGS: 00010282 [ 284.769471] RAX: RBX: 8e126a9e8000 RCX: 0006 [ 284.769471] RDX: 0007 RSI: 0082 RDI: 8e12dfb96580 [ 284.769472] RBP: b75a03f0fb68 R08: 022b R09: 0004 [ 284.769472] R10: b75a03f0fcf8 R11: 0001 R12: 001e [ 284.769473] R13: fe5fd000 R14: R15: [ 284.769474] FS: 7f4bc4c09700() GS:8e12dfb8() knlGS: [ 284.769476] CS: 0010 DS: ES: CR0: 80050033 [ 284.769477] CR2: 7f3fddb8eba0 CR3: 003f69dbe002 CR4: 00372ee0 [ 284.769478] DR0: DR1: DR2: [ 284.769478] DR3: DR6: fffe0ff0 DR7: 0400 [ 284.769479] Call Trace: [ 284.769485] vmx_vcpu_load_vmcs+0x2f9/0x440 [kvm_intel] [ 284.769488] vmx_vcpu_load+0x47/0x200 [kvm_intel] [ 284.769493] ? __memcg_kmem_charge+0x87/0x150 [ 284.769495] ? __alloc_pages_nodemask+0x246/0x320 [ 284.769499] vmx_create_vcpu+0x362/0x720 [kvm_intel] [ 284.769500] ? __get_free_pages+0x11/0x40 [ 284.769504] ? alloc_loaded_vmcs+0xa2/0x120 [kvm_intel] [ 284.769507] ? vmx_create_vcpu+0x362/0x720 [kvm_intel] [ 284.769528] kvm_arch_vcpu_create+0x4f/0x70 [kvm] [ 284.769538] kvm_vm_ioctl+0x2e2/0x980 [kvm] [ 284.769542] do_vfs_ioctl+0xa9/0x640 [ 284.769545] ? __switch_to_asm+0x40/0x70 [ 284.769546] ? __switch_to_asm+0x34/0x70 [ 284.769547] ? __switch_to_asm+0x40/0x70 [ 284.769548] ? __switch_to_asm+0x34/0x70 [ 284.769550] ? __switch_to_asm+0x40/0x70 [ 284.769551] ? __switch_to_asm+0x34/0x70 [ 284.769552] ? __switch_to_asm+0x40/0x70 [ 284.769553] ? __switch_to_asm+0x34/0x70 [ 284.769554] ? __switch_to_asm+0x40/0x70 [ 284.769555] ksys_ioctl+0x75/0x80 [ 284.769556] ? __switch_to_asm+0x34/0x70 [ 284.769557] __x64_sys_ioctl+0x1a/0x20 [ 284.769559] do_syscall_64+0x5e/0x200 [ 284.769561] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 284.769562] RIP: 0033:0x7f4bcf01d317 [ 284.769563] Code: b3 66 90 48 8b 05 71 4b 2d 00 64 c7 00 26 00 00 00 48 c7 c0 ff ff ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 41 4b 2d 00 f7 d8 64 89 01 48 [ 284.769564] RSP: 002b:7f4bc4c0 EFLAGS: 0246 ORIG_RAX: 0010 [ 284.769565] RAX: ffda RBX: ae41 RCX: 7f4bcf01d317 [ 284.769566] RDX: RSI: ae41 RDI: 000b [ 284.769566] RBP: R08: 5596f71e0ec0 R09: 5596f896c170 [ 284.769567] R10: 5596f77fb8e0 R11: 0246 R12: 5596f892ae90 [ 284.769568] R13:
[Kernel-packages] [Bug 1950462] Re: Focal linux-azure: Vm crash on Dv5/Ev5
** Changed in: linux (Ubuntu Focal) Status: Incomplete => In Progress ** Changed in: linux (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Focal) Assignee: (unassigned) => Tim Gardner (timg-tpi) ** Changed in: linux (Ubuntu) Status: Incomplete => Fix Released ** Changed in: linux-azure (Ubuntu) Status: New => Fix Released ** Changed in: linux-azure (Ubuntu Focal) Status: New => In Progress ** Changed in: linux-azure (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: linux-azure (Ubuntu Focal) Assignee: (unassigned) => Tim Gardner (timg-tpi) -- 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/1950462 Title: Focal linux-azure: Vm crash on Dv5/Ev5 Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux source package in Focal: In Progress Status in linux-azure source package in Focal: In Progress Bug description: SRU Justification [Impact] We are seeing a below crash for Nested VM scenario in Dv5/Ev5. [ 284.769421] [ cut here ] [ 284.769422] KVM: accessing unsupported EVMCS field 2032 [ 284.769443] WARNING: CPU: 30 PID: 8426 at /build/linux-azure-5.4-YivnXz/linux-azure-5.4-5.4.0/arch/x86/kvm/vmx/evmcs.h:85 evmcs_write64+0x65/0x70 [kvm_intel] [ 284.769443] Modules linked in: vhost_net vhost tap ipt_REJECT nf_reject_ipv4 xt_tcpudp iptable_filter xt_MASQUERADE iptable_nat nf_nat bridge stp llc xt_owner xt_conntrack nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 iptable_security bpfilter udf crc_itu_t nls_iso8859_1 kvm_intel kvm serio_raw hv_balloon joydev sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear hid_generic crct10dif_pclmul hid_hyperv crc32_pclmul ghash_clmulni_intel aesni_intel crypto_simd cryptd hyperv_fb cfbfillrect glue_helper cfbimgblt hid hv_netvsc hv_utils hyperv_keyboard cfbcopyarea [ 284.769463] CPU: 30 PID: 8426 Comm: qemu-system-x86 Not tainted 5.4.0-1062-azure #65~18.04.1-Ubuntu [ 284.769464] Hardware name: Microsoft Corporation Virtual Machine/Virtual Machine, BIOS Hyper-V UEFI Release v4.1 07/22/2021 [ 284.769467] RIP: 0010:evmcs_write64+0x65/0x70 [kvm_intel] [ 284.769469] Code: c2 f7 d0 21 81 38 03 00 00 5d c3 80 3d 1c 32 03 00 00 75 f5 48 89 fe 48 c7 c7 f8 63 57 c0 c6 05 09 32 03 00 01 e8 eb d1 53 cd <0f> 0b 5d c3 0f 1f 80 00 00 00 00 0f 1f 44 00 00 48 8b 07 80 b8 ea [ 284.769469] RSP: 0018:b75a03f0fb68 EFLAGS: 00010282 [ 284.769471] RAX: RBX: 8e126a9e8000 RCX: 0006 [ 284.769471] RDX: 0007 RSI: 0082 RDI: 8e12dfb96580 [ 284.769472] RBP: b75a03f0fb68 R08: 022b R09: 0004 [ 284.769472] R10: b75a03f0fcf8 R11: 0001 R12: 001e [ 284.769473] R13: fe5fd000 R14: R15: [ 284.769474] FS: 7f4bc4c09700() GS:8e12dfb8() knlGS: [ 284.769476] CS: 0010 DS: ES: CR0: 80050033 [ 284.769477] CR2: 7f3fddb8eba0 CR3: 003f69dbe002 CR4: 00372ee0 [ 284.769478] DR0: DR1: DR2: [ 284.769478] DR3: DR6: fffe0ff0 DR7: 0400 [ 284.769479] Call Trace: [ 284.769485] vmx_vcpu_load_vmcs+0x2f9/0x440 [kvm_intel] [ 284.769488] vmx_vcpu_load+0x47/0x200 [kvm_intel] [ 284.769493] ? __memcg_kmem_charge+0x87/0x150 [ 284.769495] ? __alloc_pages_nodemask+0x246/0x320 [ 284.769499] vmx_create_vcpu+0x362/0x720 [kvm_intel] [ 284.769500] ? __get_free_pages+0x11/0x40 [ 284.769504] ? alloc_loaded_vmcs+0xa2/0x120 [kvm_intel] [ 284.769507] ? vmx_create_vcpu+0x362/0x720 [kvm_intel] [ 284.769528] kvm_arch_vcpu_create+0x4f/0x70 [kvm] [ 284.769538] kvm_vm_ioctl+0x2e2/0x980 [kvm] [ 284.769542] do_vfs_ioctl+0xa9/0x640 [ 284.769545] ? __switch_to_asm+0x40/0x70 [ 284.769546] ? __switch_to_asm+0x34/0x70 [ 284.769547] ? __switch_to_asm+0x40/0x70 [ 284.769548] ? __switch_to_asm+0x34/0x70 [ 284.769550] ? __switch_to_asm+0x40/0x70 [ 284.769551] ? __switch_to_asm+0x34/0x70 [ 284.769552] ? __switch_to_asm+0x40/0x70 [ 284.769553] ? __switch_to_asm+0x34/0x70 [ 284.769554] ? __switch_to_asm+0x40/0x70 [ 284.769555] ksys_ioctl+0x75/0x80 [ 284.769556] ? __switch_to_asm+0x34/0x70 [ 284.769557] __x64_sys_ioctl+0x1a/0x20 [ 284.769559] do_syscall_64+0x5e/0x200 [ 284.769561] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 284.769562] RIP: 0033:0x7f4bcf01d317 [ 284.769563] Code: b3 66 90 48 8b 05 71 4b 2d 00 64 c7 00 26 00 00
[Kernel-packages] [Bug 1950462] 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 1950462 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 ** Changed in: linux (Ubuntu Focal) Status: New => Incomplete ** Tags added: 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/1950462 Title: Focal linux-azure: Vm crash on Dv5/Ev5 Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux source package in Focal: In Progress Status in linux-azure source package in Focal: In Progress Bug description: SRU Justification [Impact] We are seeing a below crash for Nested VM scenario in Dv5/Ev5. [ 284.769421] [ cut here ] [ 284.769422] KVM: accessing unsupported EVMCS field 2032 [ 284.769443] WARNING: CPU: 30 PID: 8426 at /build/linux-azure-5.4-YivnXz/linux-azure-5.4-5.4.0/arch/x86/kvm/vmx/evmcs.h:85 evmcs_write64+0x65/0x70 [kvm_intel] [ 284.769443] Modules linked in: vhost_net vhost tap ipt_REJECT nf_reject_ipv4 xt_tcpudp iptable_filter xt_MASQUERADE iptable_nat nf_nat bridge stp llc xt_owner xt_conntrack nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 iptable_security bpfilter udf crc_itu_t nls_iso8859_1 kvm_intel kvm serio_raw hv_balloon joydev sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear hid_generic crct10dif_pclmul hid_hyperv crc32_pclmul ghash_clmulni_intel aesni_intel crypto_simd cryptd hyperv_fb cfbfillrect glue_helper cfbimgblt hid hv_netvsc hv_utils hyperv_keyboard cfbcopyarea [ 284.769463] CPU: 30 PID: 8426 Comm: qemu-system-x86 Not tainted 5.4.0-1062-azure #65~18.04.1-Ubuntu [ 284.769464] Hardware name: Microsoft Corporation Virtual Machine/Virtual Machine, BIOS Hyper-V UEFI Release v4.1 07/22/2021 [ 284.769467] RIP: 0010:evmcs_write64+0x65/0x70 [kvm_intel] [ 284.769469] Code: c2 f7 d0 21 81 38 03 00 00 5d c3 80 3d 1c 32 03 00 00 75 f5 48 89 fe 48 c7 c7 f8 63 57 c0 c6 05 09 32 03 00 01 e8 eb d1 53 cd <0f> 0b 5d c3 0f 1f 80 00 00 00 00 0f 1f 44 00 00 48 8b 07 80 b8 ea [ 284.769469] RSP: 0018:b75a03f0fb68 EFLAGS: 00010282 [ 284.769471] RAX: RBX: 8e126a9e8000 RCX: 0006 [ 284.769471] RDX: 0007 RSI: 0082 RDI: 8e12dfb96580 [ 284.769472] RBP: b75a03f0fb68 R08: 022b R09: 0004 [ 284.769472] R10: b75a03f0fcf8 R11: 0001 R12: 001e [ 284.769473] R13: fe5fd000 R14: R15: [ 284.769474] FS: 7f4bc4c09700() GS:8e12dfb8() knlGS: [ 284.769476] CS: 0010 DS: ES: CR0: 80050033 [ 284.769477] CR2: 7f3fddb8eba0 CR3: 003f69dbe002 CR4: 00372ee0 [ 284.769478] DR0: DR1: DR2: [ 284.769478] DR3: DR6: fffe0ff0 DR7: 0400 [ 284.769479] Call Trace: [ 284.769485] vmx_vcpu_load_vmcs+0x2f9/0x440 [kvm_intel] [ 284.769488] vmx_vcpu_load+0x47/0x200 [kvm_intel] [ 284.769493] ? __memcg_kmem_charge+0x87/0x150 [ 284.769495] ? __alloc_pages_nodemask+0x246/0x320 [ 284.769499] vmx_create_vcpu+0x362/0x720 [kvm_intel] [ 284.769500] ? __get_free_pages+0x11/0x40 [ 284.769504] ? alloc_loaded_vmcs+0xa2/0x120 [kvm_intel] [ 284.769507] ? vmx_create_vcpu+0x362/0x720 [kvm_intel] [ 284.769528] kvm_arch_vcpu_create+0x4f/0x70 [kvm] [ 284.769538] kvm_vm_ioctl+0x2e2/0x980 [kvm] [ 284.769542] do_vfs_ioctl+0xa9/0x640 [ 284.769545] ? __switch_to_asm+0x40/0x70 [ 284.769546] ? __switch_to_asm+0x34/0x70 [ 284.769547] ? __switch_to_asm+0x40/0x70 [ 284.769548] ? __switch_to_asm+0x34/0x70 [ 284.769550] ? __switch_to_asm+0x40/0x70 [ 284.769551] ? __switch_to_asm+0x34/0x70 [ 284.769552] ? __switch_to_asm+0x40/0x70 [ 284.769553] ? __switch_to_asm+0x34/0x70 [ 284.769554] ? __switch_to_asm+0x40/0x70 [ 284.769555] ksys_ioctl+0x75/0x80 [ 284.769556] ? __switch_to_asm+0x34/0x70 [ 284.769557] __x64_sys_ioctl+0x1a/0x20 [ 284.769559] do_syscall_64+0x5e/0x200 [ 284.769561] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 284.769562] RIP: 0033:0x7f4bcf01d317 [ 284.769563]
[Kernel-packages] [Bug 1950205] Re: Some shaders can crash the amdgpu kernel module, tainting
Edit: Please close this bug -- it is a duplicate of an upstream issue in dxvk (https://gitlab.freedesktop.org/mesa/mesa/-/issues/4866) and not the kernel per se (although that makes life worse by clearing out vram and hard-resetting the gpu once the crash occurs, which X and DMs have no way to recover from). ** Bug watch added: gitlab.freedesktop.org/mesa/mesa/-/issues #4866 https://gitlab.freedesktop.org/mesa/mesa/-/issues/4866 -- 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/1950205 Title: Some shaders can crash the amdgpu kernel module, tainting Status in linux package in Ubuntu: Confirmed Bug description: Hi there, I am experiencing, at random, the AMD-GPU "fences timed out!" bug reported previously as being either a kernel issue (https://bugzilla.kernel.org/show_bug.cgi?id=213145) or a mesa (https://gitlab.freedesktop.org/mesa/mesa/-/issues/4866) issue. The later was apparently fixed in 21.2.4 -- I have experienced it both on the stock mesa package versions current in play in 21.10 and the "bleeding edge" git-based builds. It is difficult to reproduce deterministically. For me, at present, roleplaying game Pathfinder: Wrath of the Righteous running under proton with Lutris (0.5.8.3/wine version lutris-fshack-6.14-3-x86_64 with DXVK v1.8.1L) triggers far more infrequently on the lowest graphics settings, but occasionally absolutely deterministically at certain points (I have a save game that can do this in the highly unlikely event that anyone wants to take me up on the issue and has the GOG game -- email me at jack.mil...@physics.org). This manifests as extreme screen corruption requiring a restart of at a minimum lightdm to fix, and more likely the whole computer. Memory issues can occur either on the card or on the host, namely: [ 1208.225974] [drm:amdgpu_dm_commit_planes [amdgpu]] *ERROR* Waiting for fences timed out! [ 1213.01] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, signaled seq=112591, emitted seq=112593 [ 1213.100119] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process Wrath.exe pid 18793 thread Wrath.exe pid 18984 [ 1213.100224] amdgpu :08:00.0: amdgpu: GPU reset begin! [ 1213.349988] [drm:amdgpu_dm_commit_planes [amdgpu]] *ERROR* Waiting for fences timed out! [ 1213.350131] [drm:dce110_vblank_set [amdgpu]] *ERROR* Failed to get VBLANK! [ 1213.509424] amdgpu: cp is busy, skip halt cp [ 1213.95] amdgpu: rlc is busy, skip halt rlc [ 1213.778816] amdgpu :08:00.0: amdgpu: BACO reset [ 1214.425001] amdgpu :08:00.0: amdgpu: GPU reset succeeded, trying to resume [ 1214.427319] [drm] PCIE GART of 256M enabled (table at 0x00F4007E9000). [ 1214.427335] [drm] VRAM is lost due to GPU reset! [ 1214.600175] [ cut here ] [ 1214.600178] amdgpu :08:00.0: drm_WARN_ON(atomic_read(>refcount) == 0) [ 1214.600244] WARNING: CPU: 7 PID: 0 at drivers/gpu/drm/drm_vblank.c:1210 drm_vblank_put+0xef/0x100 [drm] [ 1214.600274] Modules linked in: xfrm_user xfrm_algo xt_addrtype br_netfilter vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) rfcomm ashmem_linux(C) binder_linux iptable_mangle xt_comment iptable_nat iptable_filter bpfilter xt_CHECKSUM xt_MASQUERADE ipt_REJECT nf_reject_ipv4 nf_conntrack_netlink xt_conntrack nft_chain_nat nf_nat xt_NFQUEUE xt_tcpudp nf_conntrack nft_compat nf_defrag_ipv6 nf_defrag_ipv4 tcp_diag inet_diag nft_counter nfnetlink_queue nf_tables nfnetlink bridge stp llc cmac algif_hash algif_skcipher af_alg bnep overlay binfmt_misc nls_iso8859_1 zfs(PO) zunicode(PO) zzstd(O) zlua(O) zavl(PO) icp(PO) zcommon(PO) snd_hda_codec_realtek intel_rapl_msr znvpair(PO) snd_hda_codec_generic intel_rapl_common spl(O) ledtrig_audio snd_hda_codec_hdmi edac_mce_amd snd_hda_intel snd_intel_dspcfg snd_intel_sdw_acpi snd_hda_codec kvm_amd snd_hda_core btusb ath9k snd_hwdep btrtl kvm ath9k_common snd_pcm btbcm btintel ath9k_hw snd_seq_midi rapl bluetooth snd_seq_midi_event ath snd_rawmidi [ 1214.600304] ecdh_generic joydev mac80211 snd_seq ecc input_leds snd_seq_device apple_mfi_fastcharge snd_timer snd eeepc_wmi soundcore ccp efi_pstore wmi_bmof cfg80211 k10temp libarc4 mac_hid sch_fq_codel nct6775 hwmon_vid msr nfsd parport_pc ppdev auth_rpcgss lp nfs_acl parport lockd grace sunrpc ip_tables x_tables autofs4 btrfs blake2b_generic zstd_compress dm_crypt raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear hid_logitech_dj hid_apple hid_logitech_hidpp hid_generic usbhid hid mfd_aaeon asus_wmi sparse_keymap amdgpu video iommu_v2 gpu_sched i2c_algo_bit drm_ttm_helper ttm crct10dif_pclmul crc32_pclmul ghash_clmulni_intel drm_kms_helper syscopyarea aesni_intel sysfillrect sysimgblt fb_sys_fops cec crypto_simd rc_core cryptd drm r8169 ahci
[Kernel-packages] [Bug 1948502] Re: TP-Link UB500 Bluetooth USB adapter not working properly
** Also affects: linux (Arch Linux) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1948502 Title: TP-Link UB500 Bluetooth USB adapter not working properly Status in linux package in Ubuntu: Confirmed Status in linux package in Arch Linux: New Bug description: I have just bought a Tp-link bluetooth 5.0 usb adapter (UB500). According to this website https://usb-ids.gowdy.us/read/UD/2357/0604 the chip is Realtek RTL8761B. It works just fine on Windows 10, but I'm having problems on Ubuntu. I'm running Ubuntu 21.10 with the 5.14.14-051414-generic kernel The adapter seems to be correctly installed and properly working, however scanning does not pick up any bluetooth device. I've tried two headsets (that I know are properly working) and my phone, with no success. When performing a scan on my phone, the computer doesn't show up, even if I've set it to visible. (I'm sorry if the information is not complete, but ubuntu-bug is not working for me) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1948502/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1950462] [NEW] Focal linux-azure: Vm crash on Dv5/Ev5
Public bug reported:
SRU Justification
[Impact]
We are seeing a below crash for Nested VM scenario in Dv5/Ev5.
[ 284.769421] [ cut here ]
[ 284.769422] KVM: accessing unsupported EVMCS field 2032
[ 284.769443] WARNING: CPU: 30 PID: 8426 at
/build/linux-azure-5.4-YivnXz/linux-azure-5.4-5.4.0/arch/x86/kvm/vmx/evmcs.h:85
evmcs_write64+0x65/0x70 [kvm_intel]
[ 284.769443] Modules linked in: vhost_net vhost tap ipt_REJECT nf_reject_ipv4
xt_tcpudp iptable_filter xt_MASQUERADE iptable_nat nf_nat bridge stp llc
xt_owner xt_conntrack nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4
iptable_security bpfilter udf crc_itu_t nls_iso8859_1 kvm_intel kvm serio_raw
hv_balloon joydev sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp
libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 btrfs
zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor
async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear hid_generic
crct10dif_pclmul hid_hyperv crc32_pclmul ghash_clmulni_intel aesni_intel
crypto_simd cryptd hyperv_fb cfbfillrect glue_helper cfbimgblt hid hv_netvsc
hv_utils hyperv_keyboard cfbcopyarea
[ 284.769463] CPU: 30 PID: 8426 Comm: qemu-system-x86 Not tainted
5.4.0-1062-azure #65~18.04.1-Ubuntu
[ 284.769464] Hardware name: Microsoft Corporation Virtual Machine/Virtual
Machine, BIOS Hyper-V UEFI Release v4.1 07/22/2021
[ 284.769467] RIP: 0010:evmcs_write64+0x65/0x70 [kvm_intel]
[ 284.769469] Code: c2 f7 d0 21 81 38 03 00 00 5d c3 80 3d 1c 32 03 00 00 75 f5
48 89 fe 48 c7 c7 f8 63 57 c0 c6 05 09 32 03 00 01 e8 eb d1 53 cd <0f> 0b 5d c3
0f 1f 80 00 00 00 00 0f 1f 44 00 00 48 8b 07 80 b8 ea
[ 284.769469] RSP: 0018:b75a03f0fb68 EFLAGS: 00010282
[ 284.769471] RAX: RBX: 8e126a9e8000 RCX: 0006
[ 284.769471] RDX: 0007 RSI: 0082 RDI: 8e12dfb96580
[ 284.769472] RBP: b75a03f0fb68 R08: 022b R09: 0004
[ 284.769472] R10: b75a03f0fcf8 R11: 0001 R12: 001e
[ 284.769473] R13: fe5fd000 R14: R15:
[ 284.769474] FS: 7f4bc4c09700() GS:8e12dfb8()
knlGS:
[ 284.769476] CS: 0010 DS: ES: CR0: 80050033
[ 284.769477] CR2: 7f3fddb8eba0 CR3: 003f69dbe002 CR4: 00372ee0
[ 284.769478] DR0: DR1: DR2:
[ 284.769478] DR3: DR6: fffe0ff0 DR7: 0400
[ 284.769479] Call Trace:
[ 284.769485] vmx_vcpu_load_vmcs+0x2f9/0x440 [kvm_intel]
[ 284.769488] vmx_vcpu_load+0x47/0x200 [kvm_intel]
[ 284.769493] ? __memcg_kmem_charge+0x87/0x150
[ 284.769495] ? __alloc_pages_nodemask+0x246/0x320
[ 284.769499] vmx_create_vcpu+0x362/0x720 [kvm_intel]
[ 284.769500] ? __get_free_pages+0x11/0x40
[ 284.769504] ? alloc_loaded_vmcs+0xa2/0x120 [kvm_intel]
[ 284.769507] ? vmx_create_vcpu+0x362/0x720 [kvm_intel]
[ 284.769528] kvm_arch_vcpu_create+0x4f/0x70 [kvm]
[ 284.769538] kvm_vm_ioctl+0x2e2/0x980 [kvm]
[ 284.769542] do_vfs_ioctl+0xa9/0x640
[ 284.769545] ? __switch_to_asm+0x40/0x70
[ 284.769546] ? __switch_to_asm+0x34/0x70
[ 284.769547] ? __switch_to_asm+0x40/0x70
[ 284.769548] ? __switch_to_asm+0x34/0x70
[ 284.769550] ? __switch_to_asm+0x40/0x70
[ 284.769551] ? __switch_to_asm+0x34/0x70
[ 284.769552] ? __switch_to_asm+0x40/0x70
[ 284.769553] ? __switch_to_asm+0x34/0x70
[ 284.769554] ? __switch_to_asm+0x40/0x70
[ 284.769555] ksys_ioctl+0x75/0x80
[ 284.769556] ? __switch_to_asm+0x34/0x70
[ 284.769557] __x64_sys_ioctl+0x1a/0x20
[ 284.769559] do_syscall_64+0x5e/0x200
[ 284.769561] entry_SYSCALL_64_after_hwframe+0x44/0xa9
[ 284.769562] RIP: 0033:0x7f4bcf01d317
[ 284.769563] Code: b3 66 90 48 8b 05 71 4b 2d 00 64 c7 00 26 00 00 00 48 c7 c0
ff ff ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 b8 10 00 00 00 0f 05 <48> 3d 01 f0
ff ff 73 01 c3 48 8b 0d 41 4b 2d 00 f7 d8 64 89 01 48
[ 284.769564] RSP: 002b:7f4bc4c0 EFLAGS: 0246 ORIG_RAX:
0010
[ 284.769565] RAX: ffda RBX: ae41 RCX: 7f4bcf01d317
[ 284.769566] RDX: RSI: ae41 RDI: 000b
[ 284.769566] RBP: R08: 5596f71e0ec0 R09: 5596f896c170
[ 284.769567] R10: 5596f77fb8e0 R11: 0246 R12: 5596f892ae90
[ 284.769568] R13: R14: 5596f896c170 R15: 7fffa5dffce0
[ 284.769569] ---[ end trace 481983b25fa8f1f4 ]---
[ 284.795366] set kvm_intel.dump_invalid_vmcs=1 to dump internal KVM state.
[Fix]
55d2eba8e7cd ("jump_label: Fix usage in module __init")
064eedf2c50f ("KVM: VMX: eVMCS: make evmcs_sanitize_exec_ctrls() work again")
[Test Case]
Create a nested VM on an Azure Dv5/Ev5 instance.
[Where things could go wrong]
KVM instance creation could fail in other unusual ways.
[Other info]
SF: #00322790
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Affects: linux-azure
[Kernel-packages] [Bug 1950448] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1950448/+attachment/5539560/+files/Lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1950448 Title: wifi stopped working on killer ax500 xps 9500 with kernel upgrade to 5.11.0-40 Status in linux package in Ubuntu: Confirmed Bug description: Hi all, after upgrading my kernel to 5.11.0-40 my wifi card (AX500 killer wifi) is no longer recognized on my xps 15 9500. When I boot into the old kernel, 5.11.0-38 it is still working. I found that this issue has been reported here: https://bugzilla.kernel.org/show_bug.cgi?id=214455 and it could be traced back to commit: 3f38cc1ba1e289306f52cb7238406f38ecbfa21a net: qrtr: make checks in qrtr_endpoint_post() stricter which was also in the patchset: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1946788 for the 5.11.0-40 release. in the bugzilla link a solution was mentioned and it generally doesn't seem too big a problem, would be awesome if someone could look into this. Thanks a lot! --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: laurenz2209 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-04-16 (207 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Dell Inc. XPS 15 9500 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-38-generic root=UUID=3c4f468c-c47a-4a25-b8f2-20610c9437b2 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-38.42~20.04.1-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-38-generic N/A linux-backports-modules-5.11.0-38-generic N/A linux-firmware 1.187.20 Tags: focal Uname: Linux 5.11.0-38-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: 08/11/2021 dmi.bios.release: 1.9 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.9.1 dmi.board.name: 0XWT2F dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.9.1:bd08/11/2021:br1.9:svnDellInc.:pnXPS159500:pvr:sku097D:rvnDellInc.:rn0XWT2F:rvrA02:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9500 dmi.product.sku: 097D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950448/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1950448] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1950448/+attachment/5539571/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1950448 Title: wifi stopped working on killer ax500 xps 9500 with kernel upgrade to 5.11.0-40 Status in linux package in Ubuntu: Confirmed Bug description: Hi all, after upgrading my kernel to 5.11.0-40 my wifi card (AX500 killer wifi) is no longer recognized on my xps 15 9500. When I boot into the old kernel, 5.11.0-38 it is still working. I found that this issue has been reported here: https://bugzilla.kernel.org/show_bug.cgi?id=214455 and it could be traced back to commit: 3f38cc1ba1e289306f52cb7238406f38ecbfa21a net: qrtr: make checks in qrtr_endpoint_post() stricter which was also in the patchset: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1946788 for the 5.11.0-40 release. in the bugzilla link a solution was mentioned and it generally doesn't seem too big a problem, would be awesome if someone could look into this. Thanks a lot! --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: laurenz2209 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-04-16 (207 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Dell Inc. XPS 15 9500 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-38-generic root=UUID=3c4f468c-c47a-4a25-b8f2-20610c9437b2 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-38.42~20.04.1-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-38-generic N/A linux-backports-modules-5.11.0-38-generic N/A linux-firmware 1.187.20 Tags: focal Uname: Linux 5.11.0-38-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: 08/11/2021 dmi.bios.release: 1.9 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.9.1 dmi.board.name: 0XWT2F dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.9.1:bd08/11/2021:br1.9:svnDellInc.:pnXPS159500:pvr:sku097D:rvnDellInc.:rn0XWT2F:rvrA02:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9500 dmi.product.sku: 097D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950448/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1950448] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1950448/+attachment/5539559/+files/Lspci-vt.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1950448 Title: wifi stopped working on killer ax500 xps 9500 with kernel upgrade to 5.11.0-40 Status in linux package in Ubuntu: Confirmed Bug description: Hi all, after upgrading my kernel to 5.11.0-40 my wifi card (AX500 killer wifi) is no longer recognized on my xps 15 9500. When I boot into the old kernel, 5.11.0-38 it is still working. I found that this issue has been reported here: https://bugzilla.kernel.org/show_bug.cgi?id=214455 and it could be traced back to commit: 3f38cc1ba1e289306f52cb7238406f38ecbfa21a net: qrtr: make checks in qrtr_endpoint_post() stricter which was also in the patchset: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1946788 for the 5.11.0-40 release. in the bugzilla link a solution was mentioned and it generally doesn't seem too big a problem, would be awesome if someone could look into this. Thanks a lot! --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: laurenz2209 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-04-16 (207 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Dell Inc. XPS 15 9500 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-38-generic root=UUID=3c4f468c-c47a-4a25-b8f2-20610c9437b2 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-38.42~20.04.1-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-38-generic N/A linux-backports-modules-5.11.0-38-generic N/A linux-firmware 1.187.20 Tags: focal Uname: Linux 5.11.0-38-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: 08/11/2021 dmi.bios.release: 1.9 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.9.1 dmi.board.name: 0XWT2F dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.9.1:bd08/11/2021:br1.9:svnDellInc.:pnXPS159500:pvr:sku097D:rvnDellInc.:rn0XWT2F:rvrA02:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9500 dmi.product.sku: 097D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950448/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1950448] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1950448/+attachment/5539567/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1950448 Title: wifi stopped working on killer ax500 xps 9500 with kernel upgrade to 5.11.0-40 Status in linux package in Ubuntu: Confirmed Bug description: Hi all, after upgrading my kernel to 5.11.0-40 my wifi card (AX500 killer wifi) is no longer recognized on my xps 15 9500. When I boot into the old kernel, 5.11.0-38 it is still working. I found that this issue has been reported here: https://bugzilla.kernel.org/show_bug.cgi?id=214455 and it could be traced back to commit: 3f38cc1ba1e289306f52cb7238406f38ecbfa21a net: qrtr: make checks in qrtr_endpoint_post() stricter which was also in the patchset: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1946788 for the 5.11.0-40 release. in the bugzilla link a solution was mentioned and it generally doesn't seem too big a problem, would be awesome if someone could look into this. Thanks a lot! --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: laurenz2209 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-04-16 (207 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Dell Inc. XPS 15 9500 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-38-generic root=UUID=3c4f468c-c47a-4a25-b8f2-20610c9437b2 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-38.42~20.04.1-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-38-generic N/A linux-backports-modules-5.11.0-38-generic N/A linux-firmware 1.187.20 Tags: focal Uname: Linux 5.11.0-38-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: 08/11/2021 dmi.bios.release: 1.9 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.9.1 dmi.board.name: 0XWT2F dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.9.1:bd08/11/2021:br1.9:svnDellInc.:pnXPS159500:pvr:sku097D:rvnDellInc.:rn0XWT2F:rvrA02:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9500 dmi.product.sku: 097D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950448/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1950448] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1950448/+attachment/5539556/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1950448 Title: wifi stopped working on killer ax500 xps 9500 with kernel upgrade to 5.11.0-40 Status in linux package in Ubuntu: Confirmed Bug description: Hi all, after upgrading my kernel to 5.11.0-40 my wifi card (AX500 killer wifi) is no longer recognized on my xps 15 9500. When I boot into the old kernel, 5.11.0-38 it is still working. I found that this issue has been reported here: https://bugzilla.kernel.org/show_bug.cgi?id=214455 and it could be traced back to commit: 3f38cc1ba1e289306f52cb7238406f38ecbfa21a net: qrtr: make checks in qrtr_endpoint_post() stricter which was also in the patchset: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1946788 for the 5.11.0-40 release. in the bugzilla link a solution was mentioned and it generally doesn't seem too big a problem, would be awesome if someone could look into this. Thanks a lot! --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: laurenz2209 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-04-16 (207 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Dell Inc. XPS 15 9500 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-38-generic root=UUID=3c4f468c-c47a-4a25-b8f2-20610c9437b2 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-38.42~20.04.1-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-38-generic N/A linux-backports-modules-5.11.0-38-generic N/A linux-firmware 1.187.20 Tags: focal Uname: Linux 5.11.0-38-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: 08/11/2021 dmi.bios.release: 1.9 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.9.1 dmi.board.name: 0XWT2F dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.9.1:bd08/11/2021:br1.9:svnDellInc.:pnXPS159500:pvr:sku097D:rvnDellInc.:rn0XWT2F:rvrA02:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9500 dmi.product.sku: 097D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950448/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1950448] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1950448/+attachment/5539566/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1950448 Title: wifi stopped working on killer ax500 xps 9500 with kernel upgrade to 5.11.0-40 Status in linux package in Ubuntu: Confirmed Bug description: Hi all, after upgrading my kernel to 5.11.0-40 my wifi card (AX500 killer wifi) is no longer recognized on my xps 15 9500. When I boot into the old kernel, 5.11.0-38 it is still working. I found that this issue has been reported here: https://bugzilla.kernel.org/show_bug.cgi?id=214455 and it could be traced back to commit: 3f38cc1ba1e289306f52cb7238406f38ecbfa21a net: qrtr: make checks in qrtr_endpoint_post() stricter which was also in the patchset: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1946788 for the 5.11.0-40 release. in the bugzilla link a solution was mentioned and it generally doesn't seem too big a problem, would be awesome if someone could look into this. Thanks a lot! --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: laurenz2209 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-04-16 (207 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Dell Inc. XPS 15 9500 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-38-generic root=UUID=3c4f468c-c47a-4a25-b8f2-20610c9437b2 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-38.42~20.04.1-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-38-generic N/A linux-backports-modules-5.11.0-38-generic N/A linux-firmware 1.187.20 Tags: focal Uname: Linux 5.11.0-38-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: 08/11/2021 dmi.bios.release: 1.9 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.9.1 dmi.board.name: 0XWT2F dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.9.1:bd08/11/2021:br1.9:svnDellInc.:pnXPS159500:pvr:sku097D:rvnDellInc.:rn0XWT2F:rvrA02:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9500 dmi.product.sku: 097D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950448/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1950448] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1950448/+attachment/5539564/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1950448 Title: wifi stopped working on killer ax500 xps 9500 with kernel upgrade to 5.11.0-40 Status in linux package in Ubuntu: Confirmed Bug description: Hi all, after upgrading my kernel to 5.11.0-40 my wifi card (AX500 killer wifi) is no longer recognized on my xps 15 9500. When I boot into the old kernel, 5.11.0-38 it is still working. I found that this issue has been reported here: https://bugzilla.kernel.org/show_bug.cgi?id=214455 and it could be traced back to commit: 3f38cc1ba1e289306f52cb7238406f38ecbfa21a net: qrtr: make checks in qrtr_endpoint_post() stricter which was also in the patchset: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1946788 for the 5.11.0-40 release. in the bugzilla link a solution was mentioned and it generally doesn't seem too big a problem, would be awesome if someone could look into this. Thanks a lot! --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: laurenz2209 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-04-16 (207 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Dell Inc. XPS 15 9500 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-38-generic root=UUID=3c4f468c-c47a-4a25-b8f2-20610c9437b2 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-38.42~20.04.1-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-38-generic N/A linux-backports-modules-5.11.0-38-generic N/A linux-firmware 1.187.20 Tags: focal Uname: Linux 5.11.0-38-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: 08/11/2021 dmi.bios.release: 1.9 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.9.1 dmi.board.name: 0XWT2F dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.9.1:bd08/11/2021:br1.9:svnDellInc.:pnXPS159500:pvr:sku097D:rvnDellInc.:rn0XWT2F:rvrA02:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9500 dmi.product.sku: 097D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950448/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1950448] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1950448/+attachment/5539563/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1950448 Title: wifi stopped working on killer ax500 xps 9500 with kernel upgrade to 5.11.0-40 Status in linux package in Ubuntu: Confirmed Bug description: Hi all, after upgrading my kernel to 5.11.0-40 my wifi card (AX500 killer wifi) is no longer recognized on my xps 15 9500. When I boot into the old kernel, 5.11.0-38 it is still working. I found that this issue has been reported here: https://bugzilla.kernel.org/show_bug.cgi?id=214455 and it could be traced back to commit: 3f38cc1ba1e289306f52cb7238406f38ecbfa21a net: qrtr: make checks in qrtr_endpoint_post() stricter which was also in the patchset: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1946788 for the 5.11.0-40 release. in the bugzilla link a solution was mentioned and it generally doesn't seem too big a problem, would be awesome if someone could look into this. Thanks a lot! --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: laurenz2209 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-04-16 (207 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Dell Inc. XPS 15 9500 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-38-generic root=UUID=3c4f468c-c47a-4a25-b8f2-20610c9437b2 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-38.42~20.04.1-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-38-generic N/A linux-backports-modules-5.11.0-38-generic N/A linux-firmware 1.187.20 Tags: focal Uname: Linux 5.11.0-38-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: 08/11/2021 dmi.bios.release: 1.9 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.9.1 dmi.board.name: 0XWT2F dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.9.1:bd08/11/2021:br1.9:svnDellInc.:pnXPS159500:pvr:sku097D:rvnDellInc.:rn0XWT2F:rvrA02:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9500 dmi.product.sku: 097D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950448/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1950448] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1950448/+attachment/5539569/+files/RfKill.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/1950448 Title: wifi stopped working on killer ax500 xps 9500 with kernel upgrade to 5.11.0-40 Status in linux package in Ubuntu: Confirmed Bug description: Hi all, after upgrading my kernel to 5.11.0-40 my wifi card (AX500 killer wifi) is no longer recognized on my xps 15 9500. When I boot into the old kernel, 5.11.0-38 it is still working. I found that this issue has been reported here: https://bugzilla.kernel.org/show_bug.cgi?id=214455 and it could be traced back to commit: 3f38cc1ba1e289306f52cb7238406f38ecbfa21a net: qrtr: make checks in qrtr_endpoint_post() stricter which was also in the patchset: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1946788 for the 5.11.0-40 release. in the bugzilla link a solution was mentioned and it generally doesn't seem too big a problem, would be awesome if someone could look into this. Thanks a lot! --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: laurenz2209 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-04-16 (207 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Dell Inc. XPS 15 9500 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-38-generic root=UUID=3c4f468c-c47a-4a25-b8f2-20610c9437b2 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-38.42~20.04.1-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-38-generic N/A linux-backports-modules-5.11.0-38-generic N/A linux-firmware 1.187.20 Tags: focal Uname: Linux 5.11.0-38-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: 08/11/2021 dmi.bios.release: 1.9 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.9.1 dmi.board.name: 0XWT2F dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.9.1:bd08/11/2021:br1.9:svnDellInc.:pnXPS159500:pvr:sku097D:rvnDellInc.:rn0XWT2F:rvrA02:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9500 dmi.product.sku: 097D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950448/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1950448] Re: wifi stopped working on killer ax500 xps 9500 with kernel upgrade to 5.11.0-40
Thanks Chris, as requested I ran apport-collect it with the last working kernel. -- 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/1950448 Title: wifi stopped working on killer ax500 xps 9500 with kernel upgrade to 5.11.0-40 Status in linux package in Ubuntu: Confirmed Bug description: Hi all, after upgrading my kernel to 5.11.0-40 my wifi card (AX500 killer wifi) is no longer recognized on my xps 15 9500. When I boot into the old kernel, 5.11.0-38 it is still working. I found that this issue has been reported here: https://bugzilla.kernel.org/show_bug.cgi?id=214455 and it could be traced back to commit: 3f38cc1ba1e289306f52cb7238406f38ecbfa21a net: qrtr: make checks in qrtr_endpoint_post() stricter which was also in the patchset: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1946788 for the 5.11.0-40 release. in the bugzilla link a solution was mentioned and it generally doesn't seem too big a problem, would be awesome if someone could look into this. Thanks a lot! --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: laurenz2209 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-04-16 (207 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Dell Inc. XPS 15 9500 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-38-generic root=UUID=3c4f468c-c47a-4a25-b8f2-20610c9437b2 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-38.42~20.04.1-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-38-generic N/A linux-backports-modules-5.11.0-38-generic N/A linux-firmware 1.187.20 Tags: focal Uname: Linux 5.11.0-38-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: 08/11/2021 dmi.bios.release: 1.9 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.9.1 dmi.board.name: 0XWT2F dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.9.1:bd08/11/2021:br1.9:svnDellInc.:pnXPS159500:pvr:sku097D:rvnDellInc.:rn0XWT2F:rvrA02:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9500 dmi.product.sku: 097D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950448/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1950448] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1950448/+attachment/5539572/+files/acpidump.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/1950448 Title: wifi stopped working on killer ax500 xps 9500 with kernel upgrade to 5.11.0-40 Status in linux package in Ubuntu: Confirmed Bug description: Hi all, after upgrading my kernel to 5.11.0-40 my wifi card (AX500 killer wifi) is no longer recognized on my xps 15 9500. When I boot into the old kernel, 5.11.0-38 it is still working. I found that this issue has been reported here: https://bugzilla.kernel.org/show_bug.cgi?id=214455 and it could be traced back to commit: 3f38cc1ba1e289306f52cb7238406f38ecbfa21a net: qrtr: make checks in qrtr_endpoint_post() stricter which was also in the patchset: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1946788 for the 5.11.0-40 release. in the bugzilla link a solution was mentioned and it generally doesn't seem too big a problem, would be awesome if someone could look into this. Thanks a lot! --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: laurenz2209 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-04-16 (207 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Dell Inc. XPS 15 9500 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-38-generic root=UUID=3c4f468c-c47a-4a25-b8f2-20610c9437b2 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-38.42~20.04.1-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-38-generic N/A linux-backports-modules-5.11.0-38-generic N/A linux-firmware 1.187.20 Tags: focal Uname: Linux 5.11.0-38-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: 08/11/2021 dmi.bios.release: 1.9 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.9.1 dmi.board.name: 0XWT2F dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.9.1:bd08/11/2021:br1.9:svnDellInc.:pnXPS159500:pvr:sku097D:rvnDellInc.:rn0XWT2F:rvrA02:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9500 dmi.product.sku: 097D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950448/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1950448] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1950448/+attachment/5539557/+files/IwConfig.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1950448 Title: wifi stopped working on killer ax500 xps 9500 with kernel upgrade to 5.11.0-40 Status in linux package in Ubuntu: Confirmed Bug description: Hi all, after upgrading my kernel to 5.11.0-40 my wifi card (AX500 killer wifi) is no longer recognized on my xps 15 9500. When I boot into the old kernel, 5.11.0-38 it is still working. I found that this issue has been reported here: https://bugzilla.kernel.org/show_bug.cgi?id=214455 and it could be traced back to commit: 3f38cc1ba1e289306f52cb7238406f38ecbfa21a net: qrtr: make checks in qrtr_endpoint_post() stricter which was also in the patchset: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1946788 for the 5.11.0-40 release. in the bugzilla link a solution was mentioned and it generally doesn't seem too big a problem, would be awesome if someone could look into this. Thanks a lot! --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: laurenz2209 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-04-16 (207 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Dell Inc. XPS 15 9500 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-38-generic root=UUID=3c4f468c-c47a-4a25-b8f2-20610c9437b2 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-38.42~20.04.1-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-38-generic N/A linux-backports-modules-5.11.0-38-generic N/A linux-firmware 1.187.20 Tags: focal Uname: Linux 5.11.0-38-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: 08/11/2021 dmi.bios.release: 1.9 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.9.1 dmi.board.name: 0XWT2F dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.9.1:bd08/11/2021:br1.9:svnDellInc.:pnXPS159500:pvr:sku097D:rvnDellInc.:rn0XWT2F:rvrA02:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9500 dmi.product.sku: 097D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950448/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1950448] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1950448/+attachment/5539561/+files/Lsusb-t.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1950448 Title: wifi stopped working on killer ax500 xps 9500 with kernel upgrade to 5.11.0-40 Status in linux package in Ubuntu: Confirmed Bug description: Hi all, after upgrading my kernel to 5.11.0-40 my wifi card (AX500 killer wifi) is no longer recognized on my xps 15 9500. When I boot into the old kernel, 5.11.0-38 it is still working. I found that this issue has been reported here: https://bugzilla.kernel.org/show_bug.cgi?id=214455 and it could be traced back to commit: 3f38cc1ba1e289306f52cb7238406f38ecbfa21a net: qrtr: make checks in qrtr_endpoint_post() stricter which was also in the patchset: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1946788 for the 5.11.0-40 release. in the bugzilla link a solution was mentioned and it generally doesn't seem too big a problem, would be awesome if someone could look into this. Thanks a lot! --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: laurenz2209 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-04-16 (207 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Dell Inc. XPS 15 9500 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-38-generic root=UUID=3c4f468c-c47a-4a25-b8f2-20610c9437b2 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-38.42~20.04.1-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-38-generic N/A linux-backports-modules-5.11.0-38-generic N/A linux-firmware 1.187.20 Tags: focal Uname: Linux 5.11.0-38-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: 08/11/2021 dmi.bios.release: 1.9 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.9.1 dmi.board.name: 0XWT2F dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.9.1:bd08/11/2021:br1.9:svnDellInc.:pnXPS159500:pvr:sku097D:rvnDellInc.:rn0XWT2F:rvrA02:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9500 dmi.product.sku: 097D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950448/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1950448] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1950448/+attachment/5539570/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1950448 Title: wifi stopped working on killer ax500 xps 9500 with kernel upgrade to 5.11.0-40 Status in linux package in Ubuntu: Confirmed Bug description: Hi all, after upgrading my kernel to 5.11.0-40 my wifi card (AX500 killer wifi) is no longer recognized on my xps 15 9500. When I boot into the old kernel, 5.11.0-38 it is still working. I found that this issue has been reported here: https://bugzilla.kernel.org/show_bug.cgi?id=214455 and it could be traced back to commit: 3f38cc1ba1e289306f52cb7238406f38ecbfa21a net: qrtr: make checks in qrtr_endpoint_post() stricter which was also in the patchset: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1946788 for the 5.11.0-40 release. in the bugzilla link a solution was mentioned and it generally doesn't seem too big a problem, would be awesome if someone could look into this. Thanks a lot! --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: laurenz2209 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-04-16 (207 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Dell Inc. XPS 15 9500 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-38-generic root=UUID=3c4f468c-c47a-4a25-b8f2-20610c9437b2 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-38.42~20.04.1-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-38-generic N/A linux-backports-modules-5.11.0-38-generic N/A linux-firmware 1.187.20 Tags: focal Uname: Linux 5.11.0-38-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: 08/11/2021 dmi.bios.release: 1.9 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.9.1 dmi.board.name: 0XWT2F dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.9.1:bd08/11/2021:br1.9:svnDellInc.:pnXPS159500:pvr:sku097D:rvnDellInc.:rn0XWT2F:rvrA02:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9500 dmi.product.sku: 097D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950448/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1950448] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1950448/+attachment/5539568/+files/PulseList.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1950448 Title: wifi stopped working on killer ax500 xps 9500 with kernel upgrade to 5.11.0-40 Status in linux package in Ubuntu: Confirmed Bug description: Hi all, after upgrading my kernel to 5.11.0-40 my wifi card (AX500 killer wifi) is no longer recognized on my xps 15 9500. When I boot into the old kernel, 5.11.0-38 it is still working. I found that this issue has been reported here: https://bugzilla.kernel.org/show_bug.cgi?id=214455 and it could be traced back to commit: 3f38cc1ba1e289306f52cb7238406f38ecbfa21a net: qrtr: make checks in qrtr_endpoint_post() stricter which was also in the patchset: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1946788 for the 5.11.0-40 release. in the bugzilla link a solution was mentioned and it generally doesn't seem too big a problem, would be awesome if someone could look into this. Thanks a lot! --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: laurenz2209 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-04-16 (207 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Dell Inc. XPS 15 9500 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-38-generic root=UUID=3c4f468c-c47a-4a25-b8f2-20610c9437b2 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-38.42~20.04.1-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-38-generic N/A linux-backports-modules-5.11.0-38-generic N/A linux-firmware 1.187.20 Tags: focal Uname: Linux 5.11.0-38-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: 08/11/2021 dmi.bios.release: 1.9 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.9.1 dmi.board.name: 0XWT2F dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.9.1:bd08/11/2021:br1.9:svnDellInc.:pnXPS159500:pvr:sku097D:rvnDellInc.:rn0XWT2F:rvrA02:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9500 dmi.product.sku: 097D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950448/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1950448] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1950448/+attachment/5539558/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1950448 Title: wifi stopped working on killer ax500 xps 9500 with kernel upgrade to 5.11.0-40 Status in linux package in Ubuntu: Confirmed Bug description: Hi all, after upgrading my kernel to 5.11.0-40 my wifi card (AX500 killer wifi) is no longer recognized on my xps 15 9500. When I boot into the old kernel, 5.11.0-38 it is still working. I found that this issue has been reported here: https://bugzilla.kernel.org/show_bug.cgi?id=214455 and it could be traced back to commit: 3f38cc1ba1e289306f52cb7238406f38ecbfa21a net: qrtr: make checks in qrtr_endpoint_post() stricter which was also in the patchset: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1946788 for the 5.11.0-40 release. in the bugzilla link a solution was mentioned and it generally doesn't seem too big a problem, would be awesome if someone could look into this. Thanks a lot! --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: laurenz2209 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-04-16 (207 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Dell Inc. XPS 15 9500 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-38-generic root=UUID=3c4f468c-c47a-4a25-b8f2-20610c9437b2 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-38.42~20.04.1-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-38-generic N/A linux-backports-modules-5.11.0-38-generic N/A linux-firmware 1.187.20 Tags: focal Uname: Linux 5.11.0-38-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: 08/11/2021 dmi.bios.release: 1.9 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.9.1 dmi.board.name: 0XWT2F dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.9.1:bd08/11/2021:br1.9:svnDellInc.:pnXPS159500:pvr:sku097D:rvnDellInc.:rn0XWT2F:rvrA02:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9500 dmi.product.sku: 097D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950448/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1950448] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1950448/+attachment/5539562/+files/Lsusb-v.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1950448 Title: wifi stopped working on killer ax500 xps 9500 with kernel upgrade to 5.11.0-40 Status in linux package in Ubuntu: Confirmed Bug description: Hi all, after upgrading my kernel to 5.11.0-40 my wifi card (AX500 killer wifi) is no longer recognized on my xps 15 9500. When I boot into the old kernel, 5.11.0-38 it is still working. I found that this issue has been reported here: https://bugzilla.kernel.org/show_bug.cgi?id=214455 and it could be traced back to commit: 3f38cc1ba1e289306f52cb7238406f38ecbfa21a net: qrtr: make checks in qrtr_endpoint_post() stricter which was also in the patchset: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1946788 for the 5.11.0-40 release. in the bugzilla link a solution was mentioned and it generally doesn't seem too big a problem, would be awesome if someone could look into this. Thanks a lot! --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: laurenz2209 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-04-16 (207 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Dell Inc. XPS 15 9500 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-38-generic root=UUID=3c4f468c-c47a-4a25-b8f2-20610c9437b2 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-38.42~20.04.1-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-38-generic N/A linux-backports-modules-5.11.0-38-generic N/A linux-firmware 1.187.20 Tags: focal Uname: Linux 5.11.0-38-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: 08/11/2021 dmi.bios.release: 1.9 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.9.1 dmi.board.name: 0XWT2F dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.9.1:bd08/11/2021:br1.9:svnDellInc.:pnXPS159500:pvr:sku097D:rvnDellInc.:rn0XWT2F:rvrA02:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9500 dmi.product.sku: 097D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950448/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1950448] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1950448/+attachment/5539565/+files/ProcEnviron.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/1950448 Title: wifi stopped working on killer ax500 xps 9500 with kernel upgrade to 5.11.0-40 Status in linux package in Ubuntu: Confirmed Bug description: Hi all, after upgrading my kernel to 5.11.0-40 my wifi card (AX500 killer wifi) is no longer recognized on my xps 15 9500. When I boot into the old kernel, 5.11.0-38 it is still working. I found that this issue has been reported here: https://bugzilla.kernel.org/show_bug.cgi?id=214455 and it could be traced back to commit: 3f38cc1ba1e289306f52cb7238406f38ecbfa21a net: qrtr: make checks in qrtr_endpoint_post() stricter which was also in the patchset: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1946788 for the 5.11.0-40 release. in the bugzilla link a solution was mentioned and it generally doesn't seem too big a problem, would be awesome if someone could look into this. Thanks a lot! --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: laurenz2209 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-04-16 (207 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Dell Inc. XPS 15 9500 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-38-generic root=UUID=3c4f468c-c47a-4a25-b8f2-20610c9437b2 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-38.42~20.04.1-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-38-generic N/A linux-backports-modules-5.11.0-38-generic N/A linux-firmware 1.187.20 Tags: focal Uname: Linux 5.11.0-38-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: 08/11/2021 dmi.bios.release: 1.9 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.9.1 dmi.board.name: 0XWT2F dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.9.1:bd08/11/2021:br1.9:svnDellInc.:pnXPS159500:pvr:sku097D:rvnDellInc.:rn0XWT2F:rvrA02:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9500 dmi.product.sku: 097D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950448/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1950448] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1950448/+attachment/5539555/+files/CRDA.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1950448 Title: wifi stopped working on killer ax500 xps 9500 with kernel upgrade to 5.11.0-40 Status in linux package in Ubuntu: Confirmed Bug description: Hi all, after upgrading my kernel to 5.11.0-40 my wifi card (AX500 killer wifi) is no longer recognized on my xps 15 9500. When I boot into the old kernel, 5.11.0-38 it is still working. I found that this issue has been reported here: https://bugzilla.kernel.org/show_bug.cgi?id=214455 and it could be traced back to commit: 3f38cc1ba1e289306f52cb7238406f38ecbfa21a net: qrtr: make checks in qrtr_endpoint_post() stricter which was also in the patchset: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1946788 for the 5.11.0-40 release. in the bugzilla link a solution was mentioned and it generally doesn't seem too big a problem, would be awesome if someone could look into this. Thanks a lot! --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: laurenz2209 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-04-16 (207 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Dell Inc. XPS 15 9500 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-38-generic root=UUID=3c4f468c-c47a-4a25-b8f2-20610c9437b2 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-38.42~20.04.1-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-38-generic N/A linux-backports-modules-5.11.0-38-generic N/A linux-firmware 1.187.20 Tags: focal Uname: Linux 5.11.0-38-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: 08/11/2021 dmi.bios.release: 1.9 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.9.1 dmi.board.name: 0XWT2F dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.9.1:bd08/11/2021:br1.9:svnDellInc.:pnXPS159500:pvr:sku097D:rvnDellInc.:rn0XWT2F:rvrA02:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9500 dmi.product.sku: 097D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950448/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
