[Kernel-packages] [Bug 1953522] Re: Ubuntu version macros overflow with high ABI numbers
** Changed in: linux (Ubuntu Bionic) Status: Triaged => 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/1953522 Title: Ubuntu version macros overflow with high ABI numbers Status in linux package in Ubuntu: Invalid Status in lttng-modules package in Ubuntu: Confirmed Status in linux source package in Bionic: Fix Committed Status in lttng-modules source package in Bionic: Triaged Bug description: [SRU Justification] == Impact == The kernel change (which may or may not be taken back) revealed a build issue we already have with lltng-modules and our high ABI numbers for derivative/custom kernels. It should be fixed regardless of what the kernel will do. == Fix == The proposed fix changes macros which are used to do run-time adaptions of code based on the kernel version for which the DKMS modules are built for. The number keys which the macros are using are not included in the code and the way those are used will either cause build failures or produce the same code as before. == Test case == Producing DKMS modules is the test case here. I did tests with the previous bionic:linux-snapdragon (which uses the old sub-level in the kernel) and the same kernel in proposed which has the sub-level set to 255 fix). Both worked. == Regression Potential == Building DKMS modules for lttng could start to fail. --- An upstream kernel change which was introduced to avoid high sub-level numbers in 4.14.y to overflow into the minor number has uncovered a similar issue with LTTNG's macros which allow versioned code adaptions. To allow that the ABI number of the kernel is inserted as a new sub- sub-level number. Which is done by shifting the existing LINUX_VERSION_CODE by another 8 bits. But this only allows for ABI numbers up to 255. After that they overflow into the sub-level part of the kernel. This went unnoticed until the kernel side changed this number to be 255 fix. Now the overflow reaches the minor number and this breaks assumptions in the code. For example bionic:linux-snapdragon (-1117) fails to produce lttng- modules (DKMS) but the previous version would succeed. When changing the LINUX_VERSION_CODE back, this works in both cases. Since the macros are only used to make compile time decisions the proposed fix would be to extend the ABI number size to 16bit. That will work in all cases. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953522/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1953522] Re: Ubuntu version macros overflow with high ABI numbers
** Changed in: linux (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1953522 Title: Ubuntu version macros overflow with high ABI numbers Status in linux package in Ubuntu: Invalid Status in lttng-modules package in Ubuntu: Confirmed Status in linux source package in Bionic: Triaged Status in lttng-modules source package in Bionic: Triaged Bug description: [SRU Justification] == Impact == The kernel change (which may or may not be taken back) revealed a build issue we already have with lltng-modules and our high ABI numbers for derivative/custom kernels. It should be fixed regardless of what the kernel will do. == Fix == The proposed fix changes macros which are used to do run-time adaptions of code based on the kernel version for which the DKMS modules are built for. The number keys which the macros are using are not included in the code and the way those are used will either cause build failures or produce the same code as before. == Test case == Producing DKMS modules is the test case here. I did tests with the previous bionic:linux-snapdragon (which uses the old sub-level in the kernel) and the same kernel in proposed which has the sub-level set to 255 fix). Both worked. == Regression Potential == Building DKMS modules for lttng could start to fail. --- An upstream kernel change which was introduced to avoid high sub-level numbers in 4.14.y to overflow into the minor number has uncovered a similar issue with LTTNG's macros which allow versioned code adaptions. To allow that the ABI number of the kernel is inserted as a new sub- sub-level number. Which is done by shifting the existing LINUX_VERSION_CODE by another 8 bits. But this only allows for ABI numbers up to 255. After that they overflow into the sub-level part of the kernel. This went unnoticed until the kernel side changed this number to be 255 fix. Now the overflow reaches the minor number and this breaks assumptions in the code. For example bionic:linux-snapdragon (-1117) fails to produce lttng- modules (DKMS) but the previous version would succeed. When changing the LINUX_VERSION_CODE back, this works in both cases. Since the macros are only used to make compile time decisions the proposed fix would be to extend the ABI number size to 16bit. That will work in all cases. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953522/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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-raspi/5.4.0.1048.83)
All autopkgtests for the newly accepted linux-meta-raspi (5.4.0.1048.83) for focal have finished running. The following regressions have been reported in tests triggered by the package: nat-rtsp/unknown (arm64) systemd/245.4-4ubuntu3.13 (arm64) mali-midgard/unknown (arm64) r8168/unknown (arm64) evdi/unknown (arm64) west-chamber/unknown (arm64) v4l2loopback/unknown (arm64) dpdk/unknown (arm64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#linux-meta-raspi [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packing resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1867570] Re: reuseport_bpf_numa in net from ubuntu_kernel_selftests fails on ppc64le
4.15.0-165.173 node dryden selftests: reuseport_bpf_numa [PASS] ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1867570 Title: reuseport_bpf_numa in net from ubuntu_kernel_selftests fails on ppc64le Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Fix Committed Status in linux source package in Bionic: Fix Committed 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 Committed Bug description: [ Impact ] The reuseport_bpf_numa testcase in selftests/net fails on some PowerPC systems with: # selftests: net: reuseport_bpf_numa # IPv4 UDP # send node 0, receive socket 0 # libnuma: Warning: Cannot read node cpumask from sysfs # ./reuseport_bpf_numa: failed to pin to node: No such file or directory not ok 3 selftests: net: reuseport_bpf_numa # exit=1 [ Fix ] In some platforms the numa node numbers are not necessarily consecutive, so when reuseport_bpf_numa iterates on the nodes from 0 to the max available node some of those will not be available. The fix is to change the testcase so it checks whether the node is available before trying to send/receive from it. [ Test ] Run reuseport_bpf_numa from selftests/net in one of the affected test nodes. [ Where Problems Could Occur ] This is a very simple fix which relies on the libnuma exported functions and bitmaps to check whether a numa node number is available on the system. If something is not right on how this check is made or on the libnuma code itself only the reuseport_bpf_numa testcase will be affected by reporting false negatives or having a reduced test coverage. [ Original bug report ] This issue was extracted from the comment in bug 1812638, since that bug will be specific for i386 This reuseport_bpf_numa in net will fail on PowerPC with: The output on B-5.3 P8 is: # selftests: net: reuseport_bpf_numa # IPv4 UDP # send node 0, receive socket 0 # send node 1, receive socket 7 # ./reuseport_bpf_numa: node id/receive socket mismatch not ok 3 selftests: net: reuseport_bpf_numa # exit=1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1867570/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1953671] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1953671/+attachment/5546418/+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/1953671 Title: 5.15 and 5.16 arm64 kernels fail to boot in VMWare Fusion Status in linux package in Ubuntu: Confirmed Bug description: I am using VMWare Fusion Tech Preview on an Apple M1 Max MacBook Pro per: https://blogs.vmware.com/teamfusion/2021/09/fusion-for-m1-public-tech- preview-now-available.html I am successfully using the 5.14 kernel series (currently 5.14.21-051421-generic) but note this is now EOL. However whenever I try to upgrade to either the 5.15 or 5.16 series my VM hangs at boot time after: EFI stub: Booting Linux Kernel... EFI stub: EFI_RNG_PROTOCOL unavailable EFI stub: ERROR: FIRMWARE BUG: kernel image not aligned on 64k boundary EFI stub: ERROR: FIRMWARE BUG: Image BSS overlaps adjacent EFI memory region EFI stub: Using DIB from configuration table EFI stub: Exiting boot services... I see the same "hang" for both 5.15.7 and 5.16-rc4. FYI this has also been reported by others who note that the problem appears to be specific to Ubuntu: https://communities.vmware.com/t5/Fusion-for-Apple-Silicon- Tech/Anyone-have-any-luck-with-Ubuntu-5-15-kernels/m-p/2880362 Given that I can't boot using the 5.15.7 and 5.16-rc4 kernels, I can't provide the output from: cat /proc/version However I attach the output from lspci. Please let me know what other information I can provide to help diagnose this issue. Thanks --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu74 Architecture: arm64 CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-11-12 (26 days ago) InstallationMedia: Ubuntu-Server 21.10 "Impish Indri" - Release arm64 (20211013) Package: linux-image-generic 5.13.0.21.32 [origin: unknown] PackageArchitecture: arm64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash Tags: jammy uec-images third-party-packages Uname: Linux 5.14.21-051421-generic aarch64 UnreportableReason: This does not seem to be an official Ubuntu package. Please retry after updating the indexes of available packages, if that does not work then remove related third party packages and try again. UpgradeStatus: Upgraded to jammy on 2021-11-15 (23 days ago) UserGroups: N/A _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953671/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1953671] Re: 5.15 and 5.16 arm64 kernels fail to boot in VMWare Fusion
I've tried to provide some information via: $ sudo apport-collect -p linux-image-generic 1953671 If there is a better command I can run, please let me know. -- 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/1953671 Title: 5.15 and 5.16 arm64 kernels fail to boot in VMWare Fusion Status in linux package in Ubuntu: Confirmed Bug description: I am using VMWare Fusion Tech Preview on an Apple M1 Max MacBook Pro per: https://blogs.vmware.com/teamfusion/2021/09/fusion-for-m1-public-tech- preview-now-available.html I am successfully using the 5.14 kernel series (currently 5.14.21-051421-generic) but note this is now EOL. However whenever I try to upgrade to either the 5.15 or 5.16 series my VM hangs at boot time after: EFI stub: Booting Linux Kernel... EFI stub: EFI_RNG_PROTOCOL unavailable EFI stub: ERROR: FIRMWARE BUG: kernel image not aligned on 64k boundary EFI stub: ERROR: FIRMWARE BUG: Image BSS overlaps adjacent EFI memory region EFI stub: Using DIB from configuration table EFI stub: Exiting boot services... I see the same "hang" for both 5.15.7 and 5.16-rc4. FYI this has also been reported by others who note that the problem appears to be specific to Ubuntu: https://communities.vmware.com/t5/Fusion-for-Apple-Silicon- Tech/Anyone-have-any-luck-with-Ubuntu-5-15-kernels/m-p/2880362 Given that I can't boot using the 5.15.7 and 5.16-rc4 kernels, I can't provide the output from: cat /proc/version However I attach the output from lspci. Please let me know what other information I can provide to help diagnose this issue. Thanks --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu74 Architecture: arm64 CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-11-12 (26 days ago) InstallationMedia: Ubuntu-Server 21.10 "Impish Indri" - Release arm64 (20211013) Package: linux-image-generic 5.13.0.21.32 [origin: unknown] PackageArchitecture: arm64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash Tags: jammy uec-images third-party-packages Uname: Linux 5.14.21-051421-generic aarch64 UnreportableReason: This does not seem to be an official Ubuntu package. Please retry after updating the indexes of available packages, if that does not work then remove related third party packages and try again. UpgradeStatus: Upgraded to jammy on 2021-11-15 (23 days ago) UserGroups: N/A _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953671/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1953671] Re: 5.15 and 5.16 arm64 kernels fail to boot in VMWare Fusion
apport information ** Tags added: apport-collected jammy third-party-packages uec-images ** Description changed: I am using VMWare Fusion Tech Preview on an Apple M1 Max MacBook Pro per: https://blogs.vmware.com/teamfusion/2021/09/fusion-for-m1-public-tech- preview-now-available.html I am successfully using the 5.14 kernel series (currently 5.14.21-051421-generic) but note this is now EOL. However whenever I try to upgrade to either the 5.15 or 5.16 series my VM hangs at boot time after: EFI stub: Booting Linux Kernel... EFI stub: EFI_RNG_PROTOCOL unavailable EFI stub: ERROR: FIRMWARE BUG: kernel image not aligned on 64k boundary EFI stub: ERROR: FIRMWARE BUG: Image BSS overlaps adjacent EFI memory region EFI stub: Using DIB from configuration table EFI stub: Exiting boot services... I see the same "hang" for both 5.15.7 and 5.16-rc4. FYI this has also been reported by others who note that the problem appears to be specific to Ubuntu: https://communities.vmware.com/t5/Fusion-for-Apple-Silicon-Tech/Anyone- have-any-luck-with-Ubuntu-5-15-kernels/m-p/2880362 Given that I can't boot using the 5.15.7 and 5.16-rc4 kernels, I can't provide the output from: cat /proc/version However I attach the output from lspci. Please let me know what other information I can provide to help diagnose this issue. Thanks + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu74 + Architecture: arm64 + CasperMD5CheckResult: pass + DistroRelease: Ubuntu 22.04 + InstallationDate: Installed on 2021-11-12 (26 days ago) + InstallationMedia: Ubuntu-Server 21.10 "Impish Indri" - Release arm64 (20211013) + Package: linux-image-generic 5.13.0.21.32 [origin: unknown] + PackageArchitecture: arm64 + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + LANG=C.UTF-8 + SHELL=/bin/bash + Tags: jammy uec-images third-party-packages + Uname: Linux 5.14.21-051421-generic aarch64 + UnreportableReason: This does not seem to be an official Ubuntu package. Please retry after updating the indexes of available packages, if that does not work then remove related third party packages and try again. + UpgradeStatus: Upgraded to jammy on 2021-11-15 (23 days ago) + UserGroups: N/A + _MarkForUpload: True ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1953671/+attachment/5546417/+files/Dependencies.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/1953671 Title: 5.15 and 5.16 arm64 kernels fail to boot in VMWare Fusion Status in linux package in Ubuntu: Confirmed Bug description: I am using VMWare Fusion Tech Preview on an Apple M1 Max MacBook Pro per: https://blogs.vmware.com/teamfusion/2021/09/fusion-for-m1-public-tech- preview-now-available.html I am successfully using the 5.14 kernel series (currently 5.14.21-051421-generic) but note this is now EOL. However whenever I try to upgrade to either the 5.15 or 5.16 series my VM hangs at boot time after: EFI stub: Booting Linux Kernel... EFI stub: EFI_RNG_PROTOCOL unavailable EFI stub: ERROR: FIRMWARE BUG: kernel image not aligned on 64k boundary EFI stub: ERROR: FIRMWARE BUG: Image BSS overlaps adjacent EFI memory region EFI stub: Using DIB from configuration table EFI stub: Exiting boot services... I see the same "hang" for both 5.15.7 and 5.16-rc4. FYI this has also been reported by others who note that the problem appears to be specific to Ubuntu: https://communities.vmware.com/t5/Fusion-for-Apple-Silicon- Tech/Anyone-have-any-luck-with-Ubuntu-5-15-kernels/m-p/2880362 Given that I can't boot using the 5.15.7 and 5.16-rc4 kernels, I can't provide the output from: cat /proc/version However I attach the output from lspci. Please let me know what other information I can provide to help diagnose this issue. Thanks --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu74 Architecture: arm64 CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-11-12 (26 days ago) InstallationMedia: Ubuntu-Server 21.10 "Impish Indri" - Release arm64 (20211013) Package: linux-image-generic 5.13.0.21.32 [origin: unknown] PackageArchitecture: arm64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash Tags: jammy uec-images third-party-packages Uname: Linux 5.14.21-051421-generic aarch64 UnreportableReason: This does not seem to be an official Ubuntu package. Please retry after updating the indexes of available packages, if that does not work then remove related third party packages and try again. UpgradeStatus: Upgraded to jammy on 2021-11-15 (23 days ago) UserGroups: N/A _MarkForUpload: True To manage notifications about this bug go to:
[Kernel-packages] [Bug 1945221] Re: CPU frequency stuck at minimum value..again Ubuntu 20.04.3
Also monitor # cat /proc/interrupts | grep Thermal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1945221 Title: CPU frequency stuck at minimum value..again Ubuntu 20.04.3 Status in thermald package in Ubuntu: In Progress Bug description: I would really like to find out why my cpu's keep reverting back to a cpu powersave mode after I get a kernel update then reboot. I cleaned my laptops vent but this seems to happen whenever a new kernel is updated and installed. https://askubuntu.com/questions/1366090/ubuntu-20-04-3-lts- significant-throttling-of- intel-i7-processor?noredirect=1#comment2345549_1366090 Description:Ubuntu 20.04.3 LTS Release:20.04 Computer Summary Computer Processor Intel(R) Core(TM) i7-4700MQ CPU @ 2.40GHz Memory 16315MB (4407MB used) Machine TypeLaptop Operating SystemUbuntu 20.04.3 LTS User Name rt (rt) Date/Time Mon 30 Aug 2021 02:33:09 PM EDT Display Resolution 1920x1080 pixels OpenGL Renderer Mesa DRI Intel(R) HD Graphics 4600 (HSW GT2) X11 Vendor The X.Org Foundation Audio Devices Audio Adapter HDA-Intel - HDA Intel HDMI Audio Adapter HDA-Intel - HDA Intel PCH Audio Adapter USB-Audio - USB Audio Device Input Devices Power Button Sleep Button Lid Switch Power Button AT Translated Set 2 keyboard USB Audio Device ETPS/2 Elantech Touchpad Logitech Anywhere MX Video Bus HDA Intel PCH Mic HDA Intel PCH Front Headphone HDA Intel HDMI HDMI/DP,pcm:3 HDA Intel HDMI HDMI/DP,pcm:7 HDA Intel HDMI HDMI/DP,pcm:8 HDA Intel HDMI HDMI/DP,pcm:9 HDA Intel HDMI HDMI/DP,pcm:10 Printers (CUPS) OfficeJet_Pro_6978 Default SCSI Disks TSSTcorp CDDVDW SN-208DB ATA INTEL SSDMCEAC12 ATA ST1000LM014-1EJ1 Operating System Version Kernel Linux 5.4.0-81-generic (x86_64) Version #91-Ubuntu SMP Thu Jul 15 19:09:17 UTC 2021 C Library GNU C Library / (Ubuntu GLIBC 2.31-0ubuntu9.2) 2.31 DistributionUbuntu 20.04.3 LTS Current Session Computer Name sys76 User Name rt (rt) Languageen_US.UTF-8 () Home Directory /home/rt Misc Uptime 20 minutes Load Average0.83, 1.37, 1.62 Available entropy in /dev/random3649 bits (healthy) rt@sys76:~$ dpkg -l *freq* | grep ii rt@sys76:~$ rt@sys76:~$ sudo turbostat --Summary --quiet --show Busy%,Bzy_MHz,PkgTmp,PkgWatt,GFXWatt,IRQ --interval 6 Busy% Bzy_MHz IRQ PkgTmp PkgWatt GFXWatt 2.95800 334747 2.160.01 2.76800 306949 2.150.01 5.85800 512248 2.730.01 11.87 800 800847 3.410.04 8.23800 577847 2.860.05 rt@sys76:~$ lscpu Architecture:x86_64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian Address sizes: 39 bits physical, 48 bits virtual CPU(s): 8 On-line CPU(s) list: 0-7 Thread(s) per core: 2 Core(s) per socket: 4 Socket(s): 1 NUMA node(s):1 Vendor ID: GenuineIntel CPU family: 6 Model: 60 Model name: Intel(R) Core(TM) i7-4700MQ CPU @ 2.40GHz Stepping:3 CPU MHz: 798.103 CPU max MHz: 3400. CPU min MHz: 800. BogoMIPS:4788.65 Virtualization: VT-x L1d cache: 128 KiB L1i cache: 128 KiB L2 cache:1 MiB L3 cache:6 MiB NUMA node0 CPU(s): 0-7 Vulnerability Itlb multihit: KVM: Mitigation: Split huge pages Vulnerability L1tf: Mitigation; PTE Inversion; VMX conditional cache flushes, SMT vulne rable Vulnerability Mds: Mitigation; Clear CPU buffers; SMT vulnerable Vulnerability Meltdown: Mitigation; PTI Vulnerability Spec store bypass: Mitigation; Speculative Store Bypass disabled via prctl and seccomp Vulnerability Spectre v1:Mitigation; usercopy/swapgs barriers and __user pointer sanitizatio n Vulnerability Spectre v2:Mitigation; Full generic retpoline, IBPB conditional, IBRS_FW, STIB P conditional, RSB filling Vulnerability Srbds:
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-raspi/5.11.0.1024.22)
All autopkgtests for the newly accepted linux-meta-raspi (5.11.0.1024.22) for hirsute have finished running. The following regressions have been reported in tests triggered by the package: adv-17v35x/unknown (arm64) systemd/unknown (arm64) mali-midgard/unknown (arm64) v4l2loopback/unknown (arm64) r8168/unknown (arm64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/hirsute/update_excuses.html#linux-meta-raspi [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packing resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1945221] Re: CPU frequency stuck at minimum value..again Ubuntu 20.04.3
@Srinivas, could you please list the situations when the lock would be triggered? here's first, #PROCHOT is flagged -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1945221 Title: CPU frequency stuck at minimum value..again Ubuntu 20.04.3 Status in thermald package in Ubuntu: In Progress Bug description: I would really like to find out why my cpu's keep reverting back to a cpu powersave mode after I get a kernel update then reboot. I cleaned my laptops vent but this seems to happen whenever a new kernel is updated and installed. https://askubuntu.com/questions/1366090/ubuntu-20-04-3-lts- significant-throttling-of- intel-i7-processor?noredirect=1#comment2345549_1366090 Description:Ubuntu 20.04.3 LTS Release:20.04 Computer Summary Computer Processor Intel(R) Core(TM) i7-4700MQ CPU @ 2.40GHz Memory 16315MB (4407MB used) Machine TypeLaptop Operating SystemUbuntu 20.04.3 LTS User Name rt (rt) Date/Time Mon 30 Aug 2021 02:33:09 PM EDT Display Resolution 1920x1080 pixels OpenGL Renderer Mesa DRI Intel(R) HD Graphics 4600 (HSW GT2) X11 Vendor The X.Org Foundation Audio Devices Audio Adapter HDA-Intel - HDA Intel HDMI Audio Adapter HDA-Intel - HDA Intel PCH Audio Adapter USB-Audio - USB Audio Device Input Devices Power Button Sleep Button Lid Switch Power Button AT Translated Set 2 keyboard USB Audio Device ETPS/2 Elantech Touchpad Logitech Anywhere MX Video Bus HDA Intel PCH Mic HDA Intel PCH Front Headphone HDA Intel HDMI HDMI/DP,pcm:3 HDA Intel HDMI HDMI/DP,pcm:7 HDA Intel HDMI HDMI/DP,pcm:8 HDA Intel HDMI HDMI/DP,pcm:9 HDA Intel HDMI HDMI/DP,pcm:10 Printers (CUPS) OfficeJet_Pro_6978 Default SCSI Disks TSSTcorp CDDVDW SN-208DB ATA INTEL SSDMCEAC12 ATA ST1000LM014-1EJ1 Operating System Version Kernel Linux 5.4.0-81-generic (x86_64) Version #91-Ubuntu SMP Thu Jul 15 19:09:17 UTC 2021 C Library GNU C Library / (Ubuntu GLIBC 2.31-0ubuntu9.2) 2.31 DistributionUbuntu 20.04.3 LTS Current Session Computer Name sys76 User Name rt (rt) Languageen_US.UTF-8 () Home Directory /home/rt Misc Uptime 20 minutes Load Average0.83, 1.37, 1.62 Available entropy in /dev/random3649 bits (healthy) rt@sys76:~$ dpkg -l *freq* | grep ii rt@sys76:~$ rt@sys76:~$ sudo turbostat --Summary --quiet --show Busy%,Bzy_MHz,PkgTmp,PkgWatt,GFXWatt,IRQ --interval 6 Busy% Bzy_MHz IRQ PkgTmp PkgWatt GFXWatt 2.95800 334747 2.160.01 2.76800 306949 2.150.01 5.85800 512248 2.730.01 11.87 800 800847 3.410.04 8.23800 577847 2.860.05 rt@sys76:~$ lscpu Architecture:x86_64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian Address sizes: 39 bits physical, 48 bits virtual CPU(s): 8 On-line CPU(s) list: 0-7 Thread(s) per core: 2 Core(s) per socket: 4 Socket(s): 1 NUMA node(s):1 Vendor ID: GenuineIntel CPU family: 6 Model: 60 Model name: Intel(R) Core(TM) i7-4700MQ CPU @ 2.40GHz Stepping:3 CPU MHz: 798.103 CPU max MHz: 3400. CPU min MHz: 800. BogoMIPS:4788.65 Virtualization: VT-x L1d cache: 128 KiB L1i cache: 128 KiB L2 cache:1 MiB L3 cache:6 MiB NUMA node0 CPU(s): 0-7 Vulnerability Itlb multihit: KVM: Mitigation: Split huge pages Vulnerability L1tf: Mitigation; PTE Inversion; VMX conditional cache flushes, SMT vulne rable Vulnerability Mds: Mitigation; Clear CPU buffers; SMT vulnerable Vulnerability Meltdown: Mitigation; PTI Vulnerability Spec store bypass: Mitigation; Speculative Store Bypass disabled via prctl and seccomp Vulnerability Spectre v1:Mitigation; usercopy/swapgs barriers and __user pointer sanitizatio n Vulnerability Spectre v2:Mitigation; Full generic retpoline, IBPB conditional, IBRS_FW, STIB P
[Kernel-packages] [Bug 1953671] Re: 5.15 and 5.16 arm64 kernels fail to boot in VMWare Fusion
@Chris - understood. Per my most recent message, running apport-collect triggers the following warning: "It appears you are currently running a mainline kernel. It would be better to report this bug upstream at http://bugzilla.kernel.org/ so that the upstream kernel developers are aware of the issue. If you'd still like to file a bug against the Ubuntu kernel, please boot with an official Ubuntu kernel and re-file." Excuse my noob status, but what should I therefore do? I honestly thought that by running a kernel installed from https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.14.21/ I would be running an Ubuntu kernel. Thanks -- 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/1953671 Title: 5.15 and 5.16 arm64 kernels fail to boot in VMWare Fusion Status in linux package in Ubuntu: Confirmed Bug description: I am using VMWare Fusion Tech Preview on an Apple M1 Max MacBook Pro per: https://blogs.vmware.com/teamfusion/2021/09/fusion-for-m1-public-tech- preview-now-available.html I am successfully using the 5.14 kernel series (currently 5.14.21-051421-generic) but note this is now EOL. However whenever I try to upgrade to either the 5.15 or 5.16 series my VM hangs at boot time after: EFI stub: Booting Linux Kernel... EFI stub: EFI_RNG_PROTOCOL unavailable EFI stub: ERROR: FIRMWARE BUG: kernel image not aligned on 64k boundary EFI stub: ERROR: FIRMWARE BUG: Image BSS overlaps adjacent EFI memory region EFI stub: Using DIB from configuration table EFI stub: Exiting boot services... I see the same "hang" for both 5.15.7 and 5.16-rc4. FYI this has also been reported by others who note that the problem appears to be specific to Ubuntu: https://communities.vmware.com/t5/Fusion-for-Apple-Silicon- Tech/Anyone-have-any-luck-with-Ubuntu-5-15-kernels/m-p/2880362 Given that I can't boot using the 5.15.7 and 5.16-rc4 kernels, I can't provide the output from: cat /proc/version However I attach the output from lspci. Please let me know what other information I can provide to help diagnose this issue. Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953671/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1945221] Re: CPU frequency stuck at minimum value..again Ubuntu 20.04.3
As Doug correctly described, there is a active prochot situation on the system, so processor frequency is limited. Can you dump: #grep . /sys/class/powercap/intel-rapl/intel-rapl\:0/* Also if you are able to boot the system without being stuck at 800MHz, can you try #echo 1 > /sys/devices/system/cpu/intel_pstate/no_turbo and check, If BIOS has option to disable turbo you can try that. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1945221 Title: CPU frequency stuck at minimum value..again Ubuntu 20.04.3 Status in thermald package in Ubuntu: In Progress Bug description: I would really like to find out why my cpu's keep reverting back to a cpu powersave mode after I get a kernel update then reboot. I cleaned my laptops vent but this seems to happen whenever a new kernel is updated and installed. https://askubuntu.com/questions/1366090/ubuntu-20-04-3-lts- significant-throttling-of- intel-i7-processor?noredirect=1#comment2345549_1366090 Description:Ubuntu 20.04.3 LTS Release:20.04 Computer Summary Computer Processor Intel(R) Core(TM) i7-4700MQ CPU @ 2.40GHz Memory 16315MB (4407MB used) Machine TypeLaptop Operating SystemUbuntu 20.04.3 LTS User Name rt (rt) Date/Time Mon 30 Aug 2021 02:33:09 PM EDT Display Resolution 1920x1080 pixels OpenGL Renderer Mesa DRI Intel(R) HD Graphics 4600 (HSW GT2) X11 Vendor The X.Org Foundation Audio Devices Audio Adapter HDA-Intel - HDA Intel HDMI Audio Adapter HDA-Intel - HDA Intel PCH Audio Adapter USB-Audio - USB Audio Device Input Devices Power Button Sleep Button Lid Switch Power Button AT Translated Set 2 keyboard USB Audio Device ETPS/2 Elantech Touchpad Logitech Anywhere MX Video Bus HDA Intel PCH Mic HDA Intel PCH Front Headphone HDA Intel HDMI HDMI/DP,pcm:3 HDA Intel HDMI HDMI/DP,pcm:7 HDA Intel HDMI HDMI/DP,pcm:8 HDA Intel HDMI HDMI/DP,pcm:9 HDA Intel HDMI HDMI/DP,pcm:10 Printers (CUPS) OfficeJet_Pro_6978 Default SCSI Disks TSSTcorp CDDVDW SN-208DB ATA INTEL SSDMCEAC12 ATA ST1000LM014-1EJ1 Operating System Version Kernel Linux 5.4.0-81-generic (x86_64) Version #91-Ubuntu SMP Thu Jul 15 19:09:17 UTC 2021 C Library GNU C Library / (Ubuntu GLIBC 2.31-0ubuntu9.2) 2.31 DistributionUbuntu 20.04.3 LTS Current Session Computer Name sys76 User Name rt (rt) Languageen_US.UTF-8 () Home Directory /home/rt Misc Uptime 20 minutes Load Average0.83, 1.37, 1.62 Available entropy in /dev/random3649 bits (healthy) rt@sys76:~$ dpkg -l *freq* | grep ii rt@sys76:~$ rt@sys76:~$ sudo turbostat --Summary --quiet --show Busy%,Bzy_MHz,PkgTmp,PkgWatt,GFXWatt,IRQ --interval 6 Busy% Bzy_MHz IRQ PkgTmp PkgWatt GFXWatt 2.95800 334747 2.160.01 2.76800 306949 2.150.01 5.85800 512248 2.730.01 11.87 800 800847 3.410.04 8.23800 577847 2.860.05 rt@sys76:~$ lscpu Architecture:x86_64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian Address sizes: 39 bits physical, 48 bits virtual CPU(s): 8 On-line CPU(s) list: 0-7 Thread(s) per core: 2 Core(s) per socket: 4 Socket(s): 1 NUMA node(s):1 Vendor ID: GenuineIntel CPU family: 6 Model: 60 Model name: Intel(R) Core(TM) i7-4700MQ CPU @ 2.40GHz Stepping:3 CPU MHz: 798.103 CPU max MHz: 3400. CPU min MHz: 800. BogoMIPS:4788.65 Virtualization: VT-x L1d cache: 128 KiB L1i cache: 128 KiB L2 cache:1 MiB L3 cache:6 MiB NUMA node0 CPU(s): 0-7 Vulnerability Itlb multihit: KVM: Mitigation: Split huge pages Vulnerability L1tf: Mitigation; PTE Inversion; VMX conditional cache flushes, SMT vulne rable Vulnerability Mds: Mitigation; Clear CPU buffers; SMT vulnerable Vulnerability Meltdown: Mitigation; PTI Vulnerability Spec store bypass: Mitigation; Speculative Store Bypass disabled via prctl and seccomp Vulnerability
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-gcp-4.15/4.15.0.1113.132)
All autopkgtests for the newly accepted linux-meta-gcp-4.15 (4.15.0.1113.132) for bionic have finished running. The following regressions have been reported in tests triggered by the package: lttng-modules/2.10.8-1ubuntu2~18.04.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/bionic/update_excuses.html#linux-meta-gcp-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: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packing resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1938999] Re: External displays not working on Thinkpad T490 with ThinkPad Thunderbolt 3 Dock
** Changed in: linux (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1938999 Title: External displays not working on Thinkpad T490 with ThinkPad Thunderbolt 3 Dock Status in linux package in Ubuntu: Fix Released Status in linux source package in Hirsute: Fix Released Bug description: I have two external displays chained via Display port connected to the ThinkPad Thunderbolt 3 Dock. They are working with kernel 5.8.0-63 but not with the new 5.11.0-25 kernel. I could reproduce this behavior several times for both kernels, as follows: I booted up with disconnected dock, logged in, then I connected it, disconnected it, and connected it again. With the 5.11.0-25 kernel the external displays go black; the main screen turns off and on several times. Sometimes the main screen remains working, but UI is lagging. I'm attaching the logs. Two separate boots for each variant are marked 'a'/'b'. SRU Justifications: === [Impact] External displays not working on Thinkpad T490 with ThinkPad Thunderbolt 3 Dock [Fix] Some SKL systems DP output fails when AUX timeout of LTTPR detection. Disable the LTTPR detection until GLK to fix the link training. [Test] Verified on hardware, external DP work fine. Also tested on I+N GPU laptop and a iGPU only laptop, all displays with dock are good. [Where problems could occur] It may break output of external DP. This patch from 5.12-rc5, only Hirsute kernel is SRUed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1938999/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1952403] Re: Realtek 8822CE wireless card fails to work after laptop discharge in sleep
> I put the laptop to sleep
> I use the sleep button from the GUI and it works well
I guess these two sleep methods are different.
Maybe, you can try to change the behavior of laptop automatic sleep.
--
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/1952403
Title:
Realtek 8822CE wireless card fails to work after laptop discharge in
sleep
Status in linux package in Ubuntu:
Confirmed
Bug description:
I own an Asus TUF A15 FA506IV laptop with Ubuntu 21.10. After putting
it to sleep it discharged. Turning it back on the Wireless cards
doesn't work.
This is what I found in the logs that could help:
Nov 24 15:25:56 Zveri2 krunner[16146]: [11/24/21, 15:25:56:311] info: Store:
POWER_RESUMED
Nov 24 15:25:56 Zveri2 krunner[16146]: [11/24/21, 15:25:56:312] info: Store:
SET_SUSPEND_STATUS true
Nov 24 15:25:56 Zveri2 krunner[16146]: [11/24/21, 15:25:56:313] info:
[DESKTOP-SIDE-EFFECT] Update from desktop for keys ["app"]
Nov 24 15:25:56 Zveri2 kernel: [21587.358139] rtw_8822ce :03:00.0: start
vif 80:30:49:cc:98:0f on port 0
Nov 24 15:25:56 Zveri2 charon: 01[KNL] interface wlp3s0 activated
Nov 24 15:25:56 Zveri2 NetworkManager[1059]: [1637760356.4839]
manager: NetworkManager state is now CONNECTED_LOCAL
Nov 24 15:25:56 Zveri2 krunner[16146]: [11/24/21, 15:25:56:489] info:
NetworkStatus: Network check failed {
Nov 24 15:25:56 Zveri2 krunner[16146]: "error": "Failed to fetch"
Nov 24 15:25:56 Zveri2 krunner[16146]: }
Nov 24 15:25:56 Zveri2 krunner[16146]: [11/24/21, 15:25:56:490] info: Network
status check {
Nov 24 15:25:56 Zveri2 krunner[16146]: "elapsed_time_ms": 999784,
Nov 24 15:25:56 Zveri2 krunner[16146]: "navigator_online": false,
Nov 24 15:25:56 Zveri2 krunner[16146]: "api_test": "offline"
Nov 24 15:25:56 Zveri2 krunner[16146]: }
After this I am getting the following trace:
Nov 24 15:26:05 Zveri2 kernel: [21596.291200] rtw_8822ce :03:00.0: timed
out to flush pci tx ring[0]
Nov 24 15:26:05 Zveri2 kernel: [21596.291287] rtw_8822ce :03:00.0: timed
out to flush pci tx ring[1]
Nov 24 15:26:05 Zveri2 kernel: [21596.291365] rtw_8822ce :03:00.0: timed
out to flush pci tx ring[2]
Nov 24 15:26:05 Zveri2 kernel: [21596.291484] rtw_8822ce :03:00.0: timed
out to flush pci tx ring[3]
Nov 24 15:26:05 Zveri2 kernel: [21596.291570] rtw_8822ce :03:00.0: timed
out to flush pci tx ring[5]
Nov 24 15:26:05 Zveri2 kernel: [21596.291651] rtw_8822ce :03:00.0: timed
out to flush pci tx ring[6]
Nov 24 15:26:06 Zveri2 krunner[16146]: [11/24/21, 15:26:06:125] info:
[NETWORK-CONNECTIVITY] Failed to establish a connection after 10 attempt(s).
Nov 24 15:26:07 Zveri2 kernel: [21598.291806] rtw_8822ce :03:00.0: failed
to poll offset=0x5 mask=0x2 value=0x0
Nov 24 15:26:07 Zveri2 kernel: [21598.292047] [ cut here
]
Nov 24 15:26:07 Zveri2 kernel: [21598.292049] failed to read DBI register,
addr=0x0719
Nov 24 15:26:07 Zveri2 kernel: [21598.292082] WARNING: CPU: 2 PID: 17826 at
drivers/net/wireless/realtek/rtw88/pci.c:1310 rtw_dbi_read8.constprop.0+0x
aa/0xc0 [rtw88_pci]
Nov 24 15:26:07 Zveri2 kernel: [21598.292096] Modules linked in:
nf_conntrack_netlink xt_addrtype br_netfilter vboxnetadp(OE) vboxnetflt(OE)
xfrm_user
xfrm_algo vboxdrv(OE) rfcomm xt_CHECKSUM xt_MASQUERADE xt_conntrack
ipt_REJECT nf_reject_ipv4 xt_tcpudp nft_compat nft_chain_nat nf_nat nf_conntrack
nf_defrag_ipv6 nf_defrag_ipv4 nft_counter nf_tables nfnetlink bridge stp llc
cmac algif_hash algif_skcipher overlay af_alg bnep binfmt_misc zfs(PO) zu
nicode(PO) zzstd(O) zlua(O) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O)
intel_rapl_msr intel_rapl_common joydev snd_hda_codec_realtek snd_hda_code
c_generic ledtrig_audio snd_hda_codec_hdmi snd_hda_intel edac_mce_amd
snd_intel_dspcfg snd_intel_sdw_acpi uvcvideo snd_hda_codec rtw88_8822ce rtw88_88
22c videobuf2_vmalloc snd_hda_core kvm_amd snd_hwdep rtw88_pci btusb
videobuf2_memops snd_pcm btrtl rtw88_core videobuf2_v4l2 btbcm videobuf2_common
k
vm btintel snd_seq_midi bluetooth videodev snd_seq_midi_event ecdh_generic
nls_iso8859_1 mc mac80211 rapl ecc snd_rawmidi input_leds
Nov 24 15:26:07 Zveri2 kernel: [21598.292174] serio_raw efi_pstore wmi_bmof
hid_multitouch snd_seq k10temp snd_seq_device cfg80211 snd_timer ucsi_ccg
snd snd_rn_pci_acp3x libarc4 ccp snd_pci_acp3x soundcore ucsi_acpi
typec_ucsi typec asus_wireless mac_hid nvidia_uvm(POE) sch_fq_codel msr
parport_pc ppdev lp parport ip_tables x_tables autofs4 btrfs blake2b_generic
xor zstd_compress raid6_pq libcrc32c dm_crypt hid_logitech_hidpp
hid_logitech_dj nvidia_drm(POE) nvidia_modeset(POE) usbhid nvidia(POE)
hid_generic amdgpu mfd_aaeon asus_wmi sparse_keymap iommu_v2 gpu_sched
i2c_algo_bit drm_ttm_helper ttm drm_kms_helper crct10dif_pclmul crc32_pclmul
syscopyarea
[Kernel-packages] [Bug 1952385] Re: Fix missing external headset after resume problem for Cirrus CS8409 sound driver
** Changed in: linux-oem-5.13 (Ubuntu Jammy) 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/1952385 Title: Fix missing external headset after resume problem for Cirrus CS8409 sound driver Status in HWE Next: New Status in linux package in Ubuntu: Triaged 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.13 source package in Focal: Fix Released Status in linux-oem-5.14 source package in Focal: Fix Committed Status in linux source package in Jammy: Triaged Status in linux-oem-5.13 source package in Jammy: Invalid Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: [SRU Justification] [Impact] On some platforms with Cirrus CS8409 audio codec, the external headset will fail to be detected after system resume. [Fix] Cirrus released a fix and send it upstream for approval. It's trying to schedule a harmless delayed work to do jack detection to reflect the real power state after resume. [Test] Plug-in an external headset in front headset port, suspend/resume the system then check whether the headset function works as expected. [Where problem could occur] Low. It only affect the platforms with Cirrus codec CS8409 which used to have problem. == Original Bug Description == [Summary] System can't detect external headset after suspend [Steps to reproduce] 1. install manifest and boot into OS 2. plug-in an external headset in front headset port 3. un-plug external headset 4. suspend system 5. resume system from suspend 6. plug-in an external headset [Expected result] System could detect external headset after suspend [Actual result] System can't detect external headset after suspend [Failure rate] 3/3 [Additional information] CID: 202110-29567 SKU: DLPV-SFF-DVT-C1 Image: canonical-oem-somerville-focal-amd64-20200502-85+fossa-davos-adl+X152 system-manufacturer: Dell Inc. system-product-name: Vostro 3710 bios-version: 0.13.73 CPU: 12th Gen Intel(R) Core(TM) i7-12700 (20x) GPU: :00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:4680] (rev 0c) kernel-version: 5.13.0-1019-oem [Stage] Issue reported and logs collected right after it happened To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1952385/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1953400] Re: shutdown not working from GNOME
Next time the problem happens please turn the machine off and then on again and run: journalctl -b-1 > prevboot.txt and attach the resulting text file here. Please also follow the instructions in comment #1. -- 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/1953400 Title: shutdown not working from GNOME Status in linux package in Ubuntu: Incomplete Bug description: Upon using ubuntu 22.04 with latest updates. shutdown via gnome does shutdown but the power light stays on on laptop. So I have to hold the button down for ten seconds. oddly enough shutdown works in terminal correctly. sudo shutdown -h now works To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953400/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1952011] Re: [SRU] linux-firmware: add sof-firmware for adl platforms from sof-firmware-v1.9.2
For impish: enable the -proposed, and sudo apt-get update;sudo apt-get install linux-firmware; the linux-firmware-1.201.3 is installed, check the /lib/firmware/intel/sof and sof-tplg folder, we could see the files and links from v1.9.2. Verification done on Impish. ** Tags added: verification-done-hirsute verification-done-impish -- 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/1952011 Title: [SRU] linux-firmware: add sof-firmware for adl platforms from sof- firmware-v1.9.2 Status in HWE Next: New Status in linux-firmware package in Ubuntu: New Status in linux-firmware source package in Focal: Fix Committed Status in linux-firmware source package in Hirsute: Fix Committed Status in linux-firmware source package in Impish: Fix Committed Bug description: Because we plan to remove sof-firmware related files from linux-firmware of jammy and replace them with a debian package firmware-sof-signed, so this SRU is not applied to jammy. I will submit another SRU to firmware-sof-signed package later. [Impact] In the Dell oem project, we have many laptops which has sof dmic or sof soundwire audio design, they need to load firmware and topology files specific to ADL, otherwise the audio driver will fail to initialize and the whole audio can't work. [Fix] Integrate the firmware and topology files from sof-firmware-v1.9.2 [Test] Installed the patched linux-firmware and booting the patched kernel, the audio work well, all output and input devices work normally [Where problems could occur] This SRU introduces new firmware and topology files for adl, it has low possibility to introduce regression. If it could, it could possibilily affect the other machines which also need to load firmware and topology files, it could make the audio can't work on those machines, but this possibility is very low, we have tested the SRU on many laptops, no regression found. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1952011/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1952011] Re: [SRU] linux-firmware: add sof-firmware for adl platforms from sof-firmware-v1.9.2
For hirsute: enable the -proposed, and sudo apt-get update;sudo apt-get install linux-firmware; the linux-firmware-1.197.5 is installed, check the /lib/firmware/intel/sof and sof-tplg folder, we could see the files and links from v1.9.2. Verification done on Hirsute. -- 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/1952011 Title: [SRU] linux-firmware: add sof-firmware for adl platforms from sof- firmware-v1.9.2 Status in HWE Next: New Status in linux-firmware package in Ubuntu: New Status in linux-firmware source package in Focal: Fix Committed Status in linux-firmware source package in Hirsute: Fix Committed Status in linux-firmware source package in Impish: Fix Committed Bug description: Because we plan to remove sof-firmware related files from linux-firmware of jammy and replace them with a debian package firmware-sof-signed, so this SRU is not applied to jammy. I will submit another SRU to firmware-sof-signed package later. [Impact] In the Dell oem project, we have many laptops which has sof dmic or sof soundwire audio design, they need to load firmware and topology files specific to ADL, otherwise the audio driver will fail to initialize and the whole audio can't work. [Fix] Integrate the firmware and topology files from sof-firmware-v1.9.2 [Test] Installed the patched linux-firmware and booting the patched kernel, the audio work well, all output and input devices work normally [Where problems could occur] This SRU introduces new firmware and topology files for adl, it has low possibility to introduce regression. If it could, it could possibilily affect the other machines which also need to load firmware and topology files, it could make the audio can't work on those machines, but this possibility is very low, we have tested the SRU on many laptops, no regression found. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1952011/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1953671] Re: 5.15 and 5.16 arm64 kernels fail to boot in VMWare Fusion
Can you please do a kernel bisection? -- 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/1953671 Title: 5.15 and 5.16 arm64 kernels fail to boot in VMWare Fusion Status in linux package in Ubuntu: Confirmed Bug description: I am using VMWare Fusion Tech Preview on an Apple M1 Max MacBook Pro per: https://blogs.vmware.com/teamfusion/2021/09/fusion-for-m1-public-tech- preview-now-available.html I am successfully using the 5.14 kernel series (currently 5.14.21-051421-generic) but note this is now EOL. However whenever I try to upgrade to either the 5.15 or 5.16 series my VM hangs at boot time after: EFI stub: Booting Linux Kernel... EFI stub: EFI_RNG_PROTOCOL unavailable EFI stub: ERROR: FIRMWARE BUG: kernel image not aligned on 64k boundary EFI stub: ERROR: FIRMWARE BUG: Image BSS overlaps adjacent EFI memory region EFI stub: Using DIB from configuration table EFI stub: Exiting boot services... I see the same "hang" for both 5.15.7 and 5.16-rc4. FYI this has also been reported by others who note that the problem appears to be specific to Ubuntu: https://communities.vmware.com/t5/Fusion-for-Apple-Silicon- Tech/Anyone-have-any-luck-with-Ubuntu-5-15-kernels/m-p/2880362 Given that I can't boot using the 5.15.7 and 5.16-rc4 kernels, I can't provide the output from: cat /proc/version However I attach the output from lspci. Please let me know what other information I can provide to help diagnose this issue. Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953671/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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-gke-5.4/5.4.0.1057.60~18.04.22)
All autopkgtests for the newly accepted linux-meta-gke-5.4 (5.4.0.1057.60~18.04.22) for bionic have finished running. The following regressions have been reported in tests triggered by the package: kpatch/0.5.0-0ubuntu1.1 (amd64) lxc/3.0.3-0ubuntu1~18.04.1 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-meta-gke-5.4 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packing resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1953689] 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 1953689 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/1953689 Title: smartpqi: Update 20.04.4 to latest kernel.org patch level Status in linux package in Ubuntu: Incomplete Bug description: Here is a list of patches that need applied to 20.04.4 to bring the smartpqi up to date with kernel.org. 64fc9015fbeb scsi: smartpqi: Switch to attribute groups 0ca190805784 scsi: smartpqi: Call scsi_done() directly 605ae389ea02 scsi: smartpqi: Update version to 2.1.12-055 80982656b78e scsi: smartpqi: Add 3252-8i PCI id d4dc6aea93cb scsi: smartpqi: Fix duplicate device nodes for tape changers 987d35605b7e scsi: smartpqi: Fix boot failure during LUN rebuild 28ca6d876c5a scsi: smartpqi: Add extended report physical LUNs 4f3cefc3084d scsi: smartpqi: Avoid failing I/Os for offline devices be76f90668d8 scsi: smartpqi: Add TEST UNIT READY check for SANITIZE operation 6ce1ddf53252 scsi: smartpqi: Update LUN reset handler 5d1f03e6f49a scsi: smartpqi: Capture controller reason codes 9ee5d6e9ac52 scsi: smartpqi: Add controller handshake during kdump 819225b03dc7 scsi: smartpqi: Update device removal management 5f492a7aa13b scsi: smartpqi: Replace one-element array with flexible-array member To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953689/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1953671] Re: 5.15 and 5.16 arm64 kernels fail to boot in VMWare Fusion
Without full package/release details, this bug is not likely to get much attention until details have been provided (using apport tools). Please run the apport-collect using the last kernel that booted; and just note that it was run with the working kernel, and not the kernel the bug report was about. No Ubuntu release uses the 5.14 or later kernels currently; they are currently still in testing only; and no product details have yet been provided (being populated when ubuntu-bug or apport-collect are run). -- 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/1953671 Title: 5.15 and 5.16 arm64 kernels fail to boot in VMWare Fusion Status in linux package in Ubuntu: Confirmed Bug description: I am using VMWare Fusion Tech Preview on an Apple M1 Max MacBook Pro per: https://blogs.vmware.com/teamfusion/2021/09/fusion-for-m1-public-tech- preview-now-available.html I am successfully using the 5.14 kernel series (currently 5.14.21-051421-generic) but note this is now EOL. However whenever I try to upgrade to either the 5.15 or 5.16 series my VM hangs at boot time after: EFI stub: Booting Linux Kernel... EFI stub: EFI_RNG_PROTOCOL unavailable EFI stub: ERROR: FIRMWARE BUG: kernel image not aligned on 64k boundary EFI stub: ERROR: FIRMWARE BUG: Image BSS overlaps adjacent EFI memory region EFI stub: Using DIB from configuration table EFI stub: Exiting boot services... I see the same "hang" for both 5.15.7 and 5.16-rc4. FYI this has also been reported by others who note that the problem appears to be specific to Ubuntu: https://communities.vmware.com/t5/Fusion-for-Apple-Silicon- Tech/Anyone-have-any-luck-with-Ubuntu-5-15-kernels/m-p/2880362 Given that I can't boot using the 5.15.7 and 5.16-rc4 kernels, I can't provide the output from: cat /proc/version However I attach the output from lspci. Please let me know what other information I can provide to help diagnose this issue. Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953671/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1953689] [NEW] smartpqi: Update 20.04.4 to latest kernel.org patch level
Public bug reported: Here is a list of patches that need applied to 20.04.4 to bring the smartpqi up to date with kernel.org. 64fc9015fbeb scsi: smartpqi: Switch to attribute groups 0ca190805784 scsi: smartpqi: Call scsi_done() directly 605ae389ea02 scsi: smartpqi: Update version to 2.1.12-055 80982656b78e scsi: smartpqi: Add 3252-8i PCI id d4dc6aea93cb scsi: smartpqi: Fix duplicate device nodes for tape changers 987d35605b7e scsi: smartpqi: Fix boot failure during LUN rebuild 28ca6d876c5a scsi: smartpqi: Add extended report physical LUNs 4f3cefc3084d scsi: smartpqi: Avoid failing I/Os for offline devices be76f90668d8 scsi: smartpqi: Add TEST UNIT READY check for SANITIZE operation 6ce1ddf53252 scsi: smartpqi: Update LUN reset handler 5d1f03e6f49a scsi: smartpqi: Capture controller reason codes 9ee5d6e9ac52 scsi: smartpqi: Add controller handshake during kdump 819225b03dc7 scsi: smartpqi: Update device removal management 5f492a7aa13b scsi: smartpqi: Replace one-element array with flexible-array member ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: smartpqi -- 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/1953689 Title: smartpqi: Update 20.04.4 to latest kernel.org patch level Status in linux package in Ubuntu: New Bug description: Here is a list of patches that need applied to 20.04.4 to bring the smartpqi up to date with kernel.org. 64fc9015fbeb scsi: smartpqi: Switch to attribute groups 0ca190805784 scsi: smartpqi: Call scsi_done() directly 605ae389ea02 scsi: smartpqi: Update version to 2.1.12-055 80982656b78e scsi: smartpqi: Add 3252-8i PCI id d4dc6aea93cb scsi: smartpqi: Fix duplicate device nodes for tape changers 987d35605b7e scsi: smartpqi: Fix boot failure during LUN rebuild 28ca6d876c5a scsi: smartpqi: Add extended report physical LUNs 4f3cefc3084d scsi: smartpqi: Avoid failing I/Os for offline devices be76f90668d8 scsi: smartpqi: Add TEST UNIT READY check for SANITIZE operation 6ce1ddf53252 scsi: smartpqi: Update LUN reset handler 5d1f03e6f49a scsi: smartpqi: Capture controller reason codes 9ee5d6e9ac52 scsi: smartpqi: Add controller handshake during kdump 819225b03dc7 scsi: smartpqi: Update device removal management 5f492a7aa13b scsi: smartpqi: Replace one-element array with flexible-array member To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953689/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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, thanks for the notice. ** Tags removed: verification-needed-hirsute verification-needed-impish ** Tags added: verification-done-hirsute verification-done-impish -- 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: Fix Released Status in linux-oem-5.13 source package in Focal: Fix Released Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Hirsute: Fix Committed 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: Fix Committed 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 1786013] Autopkgtest regression report (linux-meta-bluefield/5.4.0.1023.24)
All autopkgtests for the newly accepted linux-meta-bluefield (5.4.0.1023.24) for focal have finished running. The following regressions have been reported in tests triggered by the package: r8168/unknown (arm64) dpdk/19.11.10-0ubuntu0.20.04.1 (arm64) dm-writeboost/unknown (arm64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#linux-meta-bluefield [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packing resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1945590] Re: Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled
@alphanor you have very different hardware and the symptoms are
different and occurring on a different os version, would likely be be
more helpful to yourself if you opened a new bug report for your issue.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/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:
[Impact]
On some thinkpads we may get a kernel panic at boot, because the
elantech driver (trakcpad) can trigger out-of-bounds access in the
stack.
[Test case]
Simply boot the kernel on one of the affected systems (e.g., Thinkpad
E14 Gen2).
[Fix]
Prevent the stack out of bound access by applying the following
upstream commit (from linux-next):
1d72d9f960cc ("Input: elantech - fix stack out of bound access in
elantech_change_report_id()")
[Regression potential]
The fix is touching the elantech driver, so we could only see
regressions with this specific trackpad/mouse driver.
[Original bug report]
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
@alphanor
probably completely unrelated, ubuntu 20.04 works fine on the thinkpad e14, not
to mention that the error is completely different and not related to the
elantech drivers
--
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:
[Impact]
On some thinkpads we may get a kernel panic at boot, because the
elantech driver (trakcpad) can trigger out-of-bounds access in the
stack.
[Test case]
Simply boot the kernel on one of the affected systems (e.g., Thinkpad
E14 Gen2).
[Fix]
Prevent the stack out of bound access by applying the following
upstream commit (from linux-next):
1d72d9f960cc ("Input: elantech - fix stack out of bound access in
elantech_change_report_id()")
[Regression potential]
The fix is touching the elantech driver, so we could only see
regressions with this specific trackpad/mouse driver.
[Original bug report]
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
Re: [Kernel-packages] [Bug 1953400] Re: shutdown not working from GNOME
Hello Dan Today I did the shutdown procedure in gnome. The prompts on the screen shutting down all the processes went fine as far as I could tell. But afterwards I noticed the screen was off but I could still see the power light on my laptop lit. I thought it may be hung up by a process so I let it sit for 10 minutes and when I came back the light was still on and the screen was off as it was before. So I can deduce that genome is shutting off the screen but some kernel process is hanging up the system. So when I do the shutdown procedure and this happens I have no choice but to hold the button down for 10 seconds to force a shutdown. I'm afraid of corrupting my journal by doing that. Well that's the update for today. Steve On December 7, 2021 9:01:05 p.m. Daniel van Vugt <1953...@bugs.launchpad.net> wrote: > Please remember to follow the instructions in comment #1. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1953400 > > Title: > shutdown not working from GNOME > > Status in linux package in Ubuntu: > Incomplete > > Bug description: > Upon using ubuntu 22.04 with latest updates. > > shutdown via gnome does shutdown but the power light stays on on > laptop. So I have to hold the button down for ten seconds. > > oddly enough > shutdown works in terminal correctly. > sudo shutdown -h now > works > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953400/+subscriptions -- 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/1953400 Title: shutdown not working from GNOME Status in linux package in Ubuntu: Incomplete Bug description: Upon using ubuntu 22.04 with latest updates. shutdown via gnome does shutdown but the power light stays on on laptop. So I have to hold the button down for ten seconds. oddly enough shutdown works in terminal correctly. sudo shutdown -h now works To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953400/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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
Hi,
I have an Acer Swift SF314-41 (laptop) with AMD Ryzen 5 3500U, Radeon Vega
Mobile Gfx and 8 GB DDR4 Ram.
I tried to install Ubuntu 20.04.3 LTS, Ubuntu 21.10, Kubuntu 21.10, Zorin OS 16
Core and with all of them when I boot I get this error: VGACON disables amdgpu
kernel modesetting.
I then tried to install Ubuntu 18.04 LTS and it boots fine but after some time
(20/30 seconds) it freezes and I can't use keyboard and mouse, i've also tried
with external peripherals, same result.
But at least it boots so I think it's related to this post. I tried to disable
trackpad and trackpoint from the BIOS to confirm my problem but there is no
option. I also tried to add commands like "amdgpu.dc=0" inside Grub but i'm not
sure that i've placed them in the right place.
Do you know if there is any way to install Ubuntu 20.04.3 LTS with an older
kernel? I'm a beginner so I might need a detailed guide, thanks. :)
--
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:
[Impact]
On some thinkpads we may get a kernel panic at boot, because the
elantech driver (trakcpad) can trigger out-of-bounds access in the
stack.
[Test case]
Simply boot the kernel on one of the affected systems (e.g., Thinkpad
E14 Gen2).
[Fix]
Prevent the stack out of bound access by applying the following
upstream commit (from linux-next):
1d72d9f960cc ("Input: elantech - fix stack out of bound access in
elantech_change_report_id()")
[Regression potential]
The fix is touching the elantech driver, so we could only see
regressions with this specific trackpad/mouse driver.
[Original bug report]
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 1950462] Re: Focal linux-azure: Vm crash on Dv5/Ev5
Microsoft tested and approved. ** 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/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: Fix Committed 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
[Kernel-packages] [Bug 1953681] 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/1953681 Title: USB-devices do not work properly Status in linux package in Ubuntu: Confirmed Bug description: I have Ubuntu 21.10. I have noticed that USB-ports do not work properly. On multiple machines for example wireless mouse might not work after a reboot and I need to unplug and plug the dongle to get it working. Then when there are multiple USB-devices connected to the computer, the USB-port might die and only reboot helps. In that case kernel dmesg shows messages like these: la joulu 4 13:53:44 2021] xhci_hcd :0f:00.3: Abort failed to stop command ring: -110 [la joulu 4 13:53:44 2021] xhci_hcd :0f:00.3: xHCI host controller not responding, assume dead [la joulu 4 13:53:44 2021] xhci_hcd :0f:00.3: HC died; cleaning up [la joulu 4 13:53:44 2021] xhci_hcd :0f:00.3: Timeout while waiting for setup device command [la joulu 4 13:53:44 2021] xhci_hcd :0f:00.3: Error while assigning device slot ID ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-22-generic 5.13.0-22.22 ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 Uname: Linux 5.13.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Dec 8 22:16:39 2021 InstallationDate: Installed on 2021-11-06 (32 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: System manufacturer System Product Name ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-22-generic root=UUID=759510b9-f553-40ec-9dd2-f102ea364d20 ro rootflags=subvol=@ quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.13.0-22-generic N/A linux-backports-modules-5.13.0-22-generic N/A linux-firmware 1.201.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: dmi.bios.date: 08/09/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4021 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX X570-E GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4021:bd08/09/2021:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXX570-EGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953681/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1953681] [NEW] USB-devices do not work properly
Public bug reported: I have Ubuntu 21.10. I have noticed that USB-ports do not work properly. On multiple machines for example wireless mouse might not work after a reboot and I need to unplug and plug the dongle to get it working. Then when there are multiple USB-devices connected to the computer, the USB-port might die and only reboot helps. In that case kernel dmesg shows messages like these: la joulu 4 13:53:44 2021] xhci_hcd :0f:00.3: Abort failed to stop command ring: -110 [la joulu 4 13:53:44 2021] xhci_hcd :0f:00.3: xHCI host controller not responding, assume dead [la joulu 4 13:53:44 2021] xhci_hcd :0f:00.3: HC died; cleaning up [la joulu 4 13:53:44 2021] xhci_hcd :0f:00.3: Timeout while waiting for setup device command [la joulu 4 13:53:44 2021] xhci_hcd :0f:00.3: Error while assigning device slot ID ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-22-generic 5.13.0-22.22 ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 Uname: Linux 5.13.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Dec 8 22:16:39 2021 InstallationDate: Installed on 2021-11-06 (32 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: System manufacturer System Product Name ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-22-generic root=UUID=759510b9-f553-40ec-9dd2-f102ea364d20 ro rootflags=subvol=@ quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.13.0-22-generic N/A linux-backports-modules-5.13.0-22-generic N/A linux-firmware 1.201.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: dmi.bios.date: 08/09/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4021 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX X570-E GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4021:bd08/09/2021:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXX570-EGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** 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/1953681 Title: USB-devices do not work properly Status in linux package in Ubuntu: Confirmed Bug description: I have Ubuntu 21.10. I have noticed that USB-ports do not work properly. On multiple machines for example wireless mouse might not work after a reboot and I need to unplug and plug the dongle to get it working. Then when there are multiple USB-devices connected to the computer, the USB-port might die and only reboot helps. In that case kernel dmesg shows messages like these: la joulu 4 13:53:44 2021] xhci_hcd :0f:00.3: Abort failed to stop command ring: -110 [la joulu 4 13:53:44 2021] xhci_hcd :0f:00.3: xHCI host controller not responding, assume dead [la joulu 4 13:53:44 2021] xhci_hcd :0f:00.3: HC died; cleaning up [la joulu 4 13:53:44 2021] xhci_hcd :0f:00.3: Timeout while waiting for setup device command [la joulu 4 13:53:44 2021] xhci_hcd :0f:00.3: Error while assigning device slot ID ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-22-generic 5.13.0-22.22 ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 Uname: Linux 5.13.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Dec 8 22:16:39 2021 InstallationDate: Installed on 2021-11-06 (32 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: System manufacturer System Product Name ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-22-generic root=UUID=759510b9-f553-40ec-9dd2-f102ea364d20 ro rootflags=subvol=@ quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.13.0-22-generic N/A linux-backports-modules-5.13.0-22-generic N/A linux-firmware 1.201.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: dmi.bios.date: 08/09/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc.
[Kernel-packages] [Bug 1916486] Re: zfs_zrele_async can cause txg sync deadlocks
** Changed in: zfs-linux (Debian) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1916486 Title: zfs_zrele_async can cause txg sync deadlocks Status in zfs-linux package in Ubuntu: Fix Released Status in zfs-linux source package in Xenial: Fix Released Status in zfs-linux source package in Bionic: Fix Released Status in zfs-linux source package in Focal: Fix Released Status in zfs-linux source package in Groovy: Fix Released Status in zfs-linux source package in Hirsute: Fix Released Status in zfs-linux package in Debian: Fix Released Bug description: [Impact] TXG sync stalls, causing ZFS workloads to hang indefinitely [Description] For certain ZFS workloads, we can see hung task timeouts in the kernel logs due to a transaction group deadlock. Userspace process will hang and display stack traces similar to the one below: [49181.619711] clnt_server D0 21699 28868 0x0320 [49181.619715] Call Trace: [49181.619725] __schedule+0x24e/0x880 [49181.619730] schedule+0x2c/0x80 [49181.619750] cv_wait_common+0x11e/0x140 [spl] [49181.619763] ? wait_woken+0x80/0x80 [49181.619775] __cv_wait+0x15/0x20 [spl] [49181.619872] zil_commit.part.14+0x80/0x8c0 [zfs] [49181.619884] ? _cond_resched+0x19/0x40 [49181.619887] ? mutex_lock+0x12/0x40 [49181.619959] zil_commit+0x17/0x20 [zfs] [49181.620026] zfs_fsync+0x77/0xe0 [zfs] [49181.620093] zpl_fsync+0x68/0xa0 [zfs] [49181.620100] vfs_fsync_range+0x51/0xb0 [49181.620105] do_fsync+0x3d/0x70 [49181.620109] SyS_fsync+0x10/0x20 [49181.620114] do_syscall_64+0x73/0x130 [49181.620119] entry_SYSCALL_64_after_hwframe+0x41/0xa6 We also might see a kworker thread blocking in the zfs writeback/evict path: [49181.881570] kworker/u17:3 D0 4915 2 0x8000 [49181.881576] Workqueue: writeback wb_workfn (flush-zfs-10) [49181.881577] Call Trace: [49181.881580] __schedule+0x24e/0x880 [49181.881582] ? atomic_t_wait+0x60/0x60 [49181.881584] schedule+0x2c/0x80 [49181.881588] bit_wait+0x11/0x60 [49181.881592] __wait_on_bit+0x4c/0x90 [49181.881596] ? atomic_t_wait+0x60/0x60 [49181.881599] __inode_wait_for_writeback+0xb9/0xf0 [49181.881601] ? bit_waitqueue+0x40/0x40 [49181.881605] inode_wait_for_writeback+0x26/0x40 [49181.881609] evict+0xb5/0x1a0 [49181.881611] iput+0x19c/0x230 [49181.881648] zfs_iput_async+0x1d/0x80 [zfs] [49181.881682] zfs_get_data+0x1d4/0x2a0 [zfs] [49181.881718] zil_commit.part.14+0x640/0x8c0 [zfs] [49181.881752] zil_commit+0x17/0x20 [zfs] [49181.881784] zpl_writepages+0xd5/0x160 [zfs] [49181.881787] do_writepages+0x4b/0xe0 [49181.881790] __writeback_single_inode+0x45/0x350 [49181.881792] ? __writeback_single_inode+0x45/0x350 [49181.881794] writeback_sb_inodes+0x1d7/0x530 [49181.881796] wb_writeback+0xfb/0x300 [49181.881799] wb_workfn+0xad/0x400 [49181.881800] ? wb_workfn+0xad/0x400 [49181.881803] ? __switch_to_asm+0x35/0x70 [49181.881809] process_one_work+0x1de/0x420 [49181.881811] worker_thread+0x32/0x410 [49181.881813] kthread+0x121/0x140 [49181.881815] ? process_one_work+0x420/0x420 [49181.881817] ? kthread_create_worker_on_cpu+0x70/0x70 [49181.881819] ret_from_fork+0x35/0x40 This is caused by a race between ZFS writeback and evict threads, usually during a transaction group sync operation. It's possible to have two iput() threads racing for the same inode: one of them scheduled async and the other executed synchronously as part of the writeback path. If the writeback thread tries to evict the inode while the async thread is running, it might re-enter the block layer for the same inode due to ZFS counters being in an inconsistent state. This then causes the kworker thread to stall the writeback, which in turn prevents the transaction group sync to complete and locks other ZFS threads. This is fixed by the upstream commit: - Fix zrele race in zrele_async that can cause hang (43eaef6de817) [0] [Test Case] Being a race condition, this issue has been hard to reproduce consistently. This has been reported on heavy I/O workloads, mixing file creation and deletion. We have some reports both from upstream and from Ubuntu users that this is usually reproducible on e.g. heavy SQL workloads or on complex ccache-enabled builds [1]. [0] https://github.com/openzfs/zfs/pull/11530 [1] https://github.com/openzfs/zfs/issues/11527 [Regression Potential] The patch has been tested in the ZFS test suite and in production environments, so the potential for further regressions should be fairly controlled. Potential regressions might arise in the ZFS writeback path, causing write hangs and eventually stalling all ZFS-backed operations indefinitely. We should monitor heavy I/O workloads that put a lot of stress
[Kernel-packages] [Bug 1950042] Re: Let NVMe with HMB use native power control again
Hi Kai-Heng. May you please verify this bug is fixed in the Hirsute and Impish kernels in -proposed? Thank you! -- 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: Fix Released Status in linux-oem-5.13 source package in Focal: Fix Released Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Hirsute: Fix Committed 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: Fix Committed 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 1953671] Re: 5.15 and 5.16 arm64 kernels fail to boot in VMWare Fusion
Per my comments in the issue description, I can't run apport-collect because I can't boot the 5.15 or 5.16 kernels. And when I try to run it for 5.14.21 it tells me I'm running a mainline kernel, despite having installed the debs from https://kernel.ubuntu.com/~kernel- ppa/mainline/v5.14.21/. Please let me know if there is any other information I can usefully provide however. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1953671 Title: 5.15 and 5.16 arm64 kernels fail to boot in VMWare Fusion Status in linux package in Ubuntu: Confirmed Bug description: I am using VMWare Fusion Tech Preview on an Apple M1 Max MacBook Pro per: https://blogs.vmware.com/teamfusion/2021/09/fusion-for-m1-public-tech- preview-now-available.html I am successfully using the 5.14 kernel series (currently 5.14.21-051421-generic) but note this is now EOL. However whenever I try to upgrade to either the 5.15 or 5.16 series my VM hangs at boot time after: EFI stub: Booting Linux Kernel... EFI stub: EFI_RNG_PROTOCOL unavailable EFI stub: ERROR: FIRMWARE BUG: kernel image not aligned on 64k boundary EFI stub: ERROR: FIRMWARE BUG: Image BSS overlaps adjacent EFI memory region EFI stub: Using DIB from configuration table EFI stub: Exiting boot services... I see the same "hang" for both 5.15.7 and 5.16-rc4. FYI this has also been reported by others who note that the problem appears to be specific to Ubuntu: https://communities.vmware.com/t5/Fusion-for-Apple-Silicon- Tech/Anyone-have-any-luck-with-Ubuntu-5-15-kernels/m-p/2880362 Given that I can't boot using the 5.15.7 and 5.16-rc4 kernels, I can't provide the output from: cat /proc/version However I attach the output from lspci. Please let me know what other information I can provide to help diagnose this issue. Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953671/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1953674] Re: Screen does not wake up from suspend/does not wake up
Other bugs about wakeup not working, but I don't reproduce their main error messages: - https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-460/+bug/1911055 - https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1946303 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu. https://bugs.launchpad.net/bugs/1953674 Title: Screen does not wake up from suspend/does not wake up Status in nvidia-graphics-drivers-470 package in Ubuntu: New Bug description: After upgrading to 21.10 from 21.04 this problem started happening. It does not happen every time I suspend, and it usually happens after suspending for a longer time. After suspending for a longer time, it tends to happen most of the time. I can SSH into the computer, so it is just the display that is not turning back on correctly. Lenovo Thinkpad P51 with an NVIDIA quadro Quadro M1200 journalctl -o short-precise -k -b -1 contained the following messages of interest, which I could not find in other reports: ``` nvidia-modeset: WARNING: GPU:0: Lost display notification (0:0x); continuing. [24307.640014] NVRM: GPU at PCI::01:00: GPU-18af74bb-7c72-ff70-e447-87d48378ea20 [24307.640018] NVRM: Xid (PCI::01:00): 79, pid=8828, GPU has fallen off the bus. [24307.640021] NVRM: GPU :01:00.0: GPU has fallen off the bus. [24328.054022] nvidia-modeset: ERROR: GPU:0: The requested configuration of display devices (LGD (DP-4)) is not supported on this GPU. [repeats several more times] [24328.056767] nvidia-modeset: ERROR: GPU:0: The requested configuration of display devices (LGD (DP-4)) is not supported on this GPU. [24328.056951] nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x927c:0:0:0x000f [24328.056955] nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x927c:1:0:0x000f [24328.056959] nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x927c:2:0:0x000f [24328.056962] nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x927c:3:0:0x000f [24328.056983] nvidia-modeset: ERROR: GPU:0: DP-4: Failed to disable DisplayPort audio stream-0 [24328.056992] nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x947d:0:0:0x000f ``` I also noticed a sudo cat /var/crash/_usr_sbin_gdm3.0.uploaded with: 5bed8a34-5852-11ec-b48c-fa163e102db1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1953674/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1953674] [NEW] Screen does not wake up from suspend/does not wake up
Public bug reported: After upgrading to 21.10 from 21.04 this problem started happening. It does not happen every time I suspend, and it usually happens after suspending for a longer time. After suspending for a longer time, it tends to happen most of the time. I can SSH into the computer, so it is just the display that is not turning back on correctly. Lenovo Thinkpad P51 with an NVIDIA quadro Quadro M1200 journalctl -o short-precise -k -b -1 contained the following messages of interest, which I could not find in other reports: ``` nvidia-modeset: WARNING: GPU:0: Lost display notification (0:0x); continuing. [24307.640014] NVRM: GPU at PCI::01:00: GPU-18af74bb-7c72-ff70-e447-87d48378ea20 [24307.640018] NVRM: Xid (PCI::01:00): 79, pid=8828, GPU has fallen off the bus. [24307.640021] NVRM: GPU :01:00.0: GPU has fallen off the bus. [24328.054022] nvidia-modeset: ERROR: GPU:0: The requested configuration of display devices (LGD (DP-4)) is not supported on this GPU. [repeats several more times] [24328.056767] nvidia-modeset: ERROR: GPU:0: The requested configuration of display devices (LGD (DP-4)) is not supported on this GPU. [24328.056951] nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x927c:0:0:0x000f [24328.056955] nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x927c:1:0:0x000f [24328.056959] nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x927c:2:0:0x000f [24328.056962] nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x927c:3:0:0x000f [24328.056983] nvidia-modeset: ERROR: GPU:0: DP-4: Failed to disable DisplayPort audio stream-0 [24328.056992] nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x947d:0:0:0x000f ``` I also noticed a sudo cat /var/crash/_usr_sbin_gdm3.0.uploaded with: 5bed8a34-5852-11ec-b48c-fa163e102db1 ** Affects: nvidia-graphics-drivers-470 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu. https://bugs.launchpad.net/bugs/1953674 Title: Screen does not wake up from suspend/does not wake up Status in nvidia-graphics-drivers-470 package in Ubuntu: New Bug description: After upgrading to 21.10 from 21.04 this problem started happening. It does not happen every time I suspend, and it usually happens after suspending for a longer time. After suspending for a longer time, it tends to happen most of the time. I can SSH into the computer, so it is just the display that is not turning back on correctly. Lenovo Thinkpad P51 with an NVIDIA quadro Quadro M1200 journalctl -o short-precise -k -b -1 contained the following messages of interest, which I could not find in other reports: ``` nvidia-modeset: WARNING: GPU:0: Lost display notification (0:0x); continuing. [24307.640014] NVRM: GPU at PCI::01:00: GPU-18af74bb-7c72-ff70-e447-87d48378ea20 [24307.640018] NVRM: Xid (PCI::01:00): 79, pid=8828, GPU has fallen off the bus. [24307.640021] NVRM: GPU :01:00.0: GPU has fallen off the bus. [24328.054022] nvidia-modeset: ERROR: GPU:0: The requested configuration of display devices (LGD (DP-4)) is not supported on this GPU. [repeats several more times] [24328.056767] nvidia-modeset: ERROR: GPU:0: The requested configuration of display devices (LGD (DP-4)) is not supported on this GPU. [24328.056951] nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x927c:0:0:0x000f [24328.056955] nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x927c:1:0:0x000f [24328.056959] nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x927c:2:0:0x000f [24328.056962] nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x927c:3:0:0x000f [24328.056983] nvidia-modeset: ERROR: GPU:0: DP-4: Failed to disable DisplayPort audio stream-0 [24328.056992] nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x947d:0:0:0x000f ``` I also noticed a sudo cat /var/crash/_usr_sbin_gdm3.0.uploaded with: 5bed8a34-5852-11ec-b48c-fa163e102db1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1953674/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1952011] Please test proposed package
Hello Hui, or anyone else affected, Accepted linux-firmware into hirsute-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/linux- firmware/1.197.5 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- hirsute to verification-done-hirsute. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-hirsute. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1952011 Title: [SRU] linux-firmware: add sof-firmware for adl platforms from sof- firmware-v1.9.2 Status in HWE Next: New Status in linux-firmware package in Ubuntu: New Status in linux-firmware source package in Focal: Fix Committed Status in linux-firmware source package in Hirsute: Fix Committed Status in linux-firmware source package in Impish: Fix Committed Bug description: Because we plan to remove sof-firmware related files from linux-firmware of jammy and replace them with a debian package firmware-sof-signed, so this SRU is not applied to jammy. I will submit another SRU to firmware-sof-signed package later. [Impact] In the Dell oem project, we have many laptops which has sof dmic or sof soundwire audio design, they need to load firmware and topology files specific to ADL, otherwise the audio driver will fail to initialize and the whole audio can't work. [Fix] Integrate the firmware and topology files from sof-firmware-v1.9.2 [Test] Installed the patched linux-firmware and booting the patched kernel, the audio work well, all output and input devices work normally [Where problems could occur] This SRU introduces new firmware and topology files for adl, it has low possibility to introduce regression. If it could, it could possibilily affect the other machines which also need to load firmware and topology files, it could make the audio can't work on those machines, but this possibility is very low, we have tested the SRU on many laptops, no regression found. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1952011/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1953587] Please test proposed package
Hello Juerg, or anyone else affected, Accepted linux-firmware into impish-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/linux- firmware/1.201.3 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- impish to verification-done-impish. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-impish. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1953587 Title: Fix sanity checker and cleanup metadata Status in linux-firmware package in Ubuntu: New Status in linux-firmware source package in Focal: Fix Committed Status in linux-firmware source package in Hirsute: Fix Committed Status in linux-firmware source package in Impish: Fix Committed Bug description: The repo contains a checker script check_whence.py that checks WHENCE data against present firmware files and flags missing files and missing WHENCE entries. It currently doesn't parse the downstream WHENCE.ubuntu file. Fix that and cleanup any errors flagged by the checker. [ Impact ] None. These are packaging changes that are not visible to the end user. [ Where Problems Could Occur ] None. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1953587/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1952011] Please test proposed package
Hello Hui, or anyone else affected, Accepted linux-firmware into impish-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/linux- firmware/1.201.3 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- impish to verification-done-impish. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-impish. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1952011 Title: [SRU] linux-firmware: add sof-firmware for adl platforms from sof- firmware-v1.9.2 Status in HWE Next: New Status in linux-firmware package in Ubuntu: New Status in linux-firmware source package in Focal: Fix Committed Status in linux-firmware source package in Hirsute: Fix Committed Status in linux-firmware source package in Impish: Fix Committed Bug description: Because we plan to remove sof-firmware related files from linux-firmware of jammy and replace them with a debian package firmware-sof-signed, so this SRU is not applied to jammy. I will submit another SRU to firmware-sof-signed package later. [Impact] In the Dell oem project, we have many laptops which has sof dmic or sof soundwire audio design, they need to load firmware and topology files specific to ADL, otherwise the audio driver will fail to initialize and the whole audio can't work. [Fix] Integrate the firmware and topology files from sof-firmware-v1.9.2 [Test] Installed the patched linux-firmware and booting the patched kernel, the audio work well, all output and input devices work normally [Where problems could occur] This SRU introduces new firmware and topology files for adl, it has low possibility to introduce regression. If it could, it could possibilily affect the other machines which also need to load firmware and topology files, it could make the audio can't work on those machines, but this possibility is very low, we have tested the SRU on many laptops, no regression found. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1952011/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1953587] Re: Fix sanity checker and cleanup metadata
Hello Juerg, or anyone else affected, Accepted linux-firmware into hirsute-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/linux- firmware/1.197.5 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- hirsute to verification-done-hirsute. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-hirsute. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: linux-firmware (Ubuntu Hirsute) Status: New => Fix Committed ** Changed in: linux-firmware (Ubuntu Impish) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1953587 Title: Fix sanity checker and cleanup metadata Status in linux-firmware package in Ubuntu: New Status in linux-firmware source package in Focal: Fix Committed Status in linux-firmware source package in Hirsute: Fix Committed Status in linux-firmware source package in Impish: Fix Committed Bug description: The repo contains a checker script check_whence.py that checks WHENCE data against present firmware files and flags missing files and missing WHENCE entries. It currently doesn't parse the downstream WHENCE.ubuntu file. Fix that and cleanup any errors flagged by the checker. [ Impact ] None. These are packaging changes that are not visible to the end user. [ Where Problems Could Occur ] None. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1953587/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1930086] 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 1930086 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/1930086 Title: [22.04 FEAT] gcc tunings for power9 Status in The Ubuntu-power-systems project: In Progress Status in gcc-11 package in Ubuntu: In Progress Status in linux package in Ubuntu: Incomplete Status in llvm-toolchain-13 package in Ubuntu: In Progress Bug description: This is an Ubuntu-power-systems 22.04 LTS feature bug to track changing the gcc configure options from --with-cpu=power8 to --with- cpu=power9. Prerequisites for this bug include power9 builder hardware in Canonical datacenter. I'm still learning my way around Debian/Ubuntu source so go easy on me if this isn't the correct branch: https://salsa.debian.org/toolchain- team/gcc/-/blob/gcc-10-debian/debian/rules2#L394 But we'll want to add some logic around line 394 to add --with- cpu=power9 for 22.04 and possibly --with-tune=? but I'll reverse mirror this bug and verify with our IBM Power toolchain architect. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1930086/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1953671] 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 1953671 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/1953671 Title: 5.15 and 5.16 arm64 kernels fail to boot in VMWare Fusion Status in linux package in Ubuntu: Incomplete Bug description: I am using VMWare Fusion Tech Preview on an Apple M1 Max MacBook Pro per: https://blogs.vmware.com/teamfusion/2021/09/fusion-for-m1-public-tech- preview-now-available.html I am successfully using the 5.14 kernel series (currently 5.14.21-051421-generic) but note this is now EOL. However whenever I try to upgrade to either the 5.15 or 5.16 series my VM hangs at boot time after: EFI stub: Booting Linux Kernel... EFI stub: EFI_RNG_PROTOCOL unavailable EFI stub: ERROR: FIRMWARE BUG: kernel image not aligned on 64k boundary EFI stub: ERROR: FIRMWARE BUG: Image BSS overlaps adjacent EFI memory region EFI stub: Using DIB from configuration table EFI stub: Exiting boot services... I see the same "hang" for both 5.15.7 and 5.16-rc4. FYI this has also been reported by others who note that the problem appears to be specific to Ubuntu: https://communities.vmware.com/t5/Fusion-for-Apple-Silicon- Tech/Anyone-have-any-luck-with-Ubuntu-5-15-kernels/m-p/2880362 Given that I can't boot using the 5.15.7 and 5.16-rc4 kernels, I can't provide the output from: cat /proc/version However I attach the output from lspci. Please let me know what other information I can provide to help diagnose this issue. Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953671/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1930086] Re: [22.04 FEAT] gcc tunings for power9
** Changed in: linux (Ubuntu) Status: Incomplete => 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/1930086 Title: [22.04 FEAT] gcc tunings for power9 Status in The Ubuntu-power-systems project: In Progress Status in gcc-11 package in Ubuntu: In Progress Status in linux package in Ubuntu: New Status in llvm-toolchain-13 package in Ubuntu: In Progress Bug description: This is an Ubuntu-power-systems 22.04 LTS feature bug to track changing the gcc configure options from --with-cpu=power8 to --with- cpu=power9. Prerequisites for this bug include power9 builder hardware in Canonical datacenter. I'm still learning my way around Debian/Ubuntu source so go easy on me if this isn't the correct branch: https://salsa.debian.org/toolchain- team/gcc/-/blob/gcc-10-debian/debian/rules2#L394 But we'll want to add some logic around line 394 to add --with- cpu=power9 for 22.04 and possibly --with-tune=? but I'll reverse mirror this bug and verify with our IBM Power toolchain architect. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1930086/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1953671] [NEW] 5.15 and 5.16 arm64 kernels fail to boot in VMWare Fusion
Public bug reported: I am using VMWare Fusion Tech Preview on an Apple M1 Max MacBook Pro per: https://blogs.vmware.com/teamfusion/2021/09/fusion-for-m1-public-tech- preview-now-available.html I am successfully using the 5.14 kernel series (currently 5.14.21-051421-generic) but note this is now EOL. However whenever I try to upgrade to either the 5.15 or 5.16 series my VM hangs at boot time after: EFI stub: Booting Linux Kernel... EFI stub: EFI_RNG_PROTOCOL unavailable EFI stub: ERROR: FIRMWARE BUG: kernel image not aligned on 64k boundary EFI stub: ERROR: FIRMWARE BUG: Image BSS overlaps adjacent EFI memory region EFI stub: Using DIB from configuration table EFI stub: Exiting boot services... I see the same "hang" for both 5.15.7 and 5.16-rc4. FYI this has also been reported by others who note that the problem appears to be specific to Ubuntu: https://communities.vmware.com/t5/Fusion-for-Apple-Silicon-Tech/Anyone- have-any-luck-with-Ubuntu-5-15-kernels/m-p/2880362 Given that I can't boot using the 5.15.7 and 5.16-rc4 kernels, I can't provide the output from: cat /proc/version However I attach the output from lspci. Please let me know what other information I can provide to help diagnose this issue. Thanks ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Attachment added: "lspci-vnvn.log" https://bugs.launchpad.net/bugs/1953671/+attachment/5546333/+files/lspci-vnvn.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1953671 Title: 5.15 and 5.16 arm64 kernels fail to boot in VMWare Fusion Status in linux package in Ubuntu: New Bug description: I am using VMWare Fusion Tech Preview on an Apple M1 Max MacBook Pro per: https://blogs.vmware.com/teamfusion/2021/09/fusion-for-m1-public-tech- preview-now-available.html I am successfully using the 5.14 kernel series (currently 5.14.21-051421-generic) but note this is now EOL. However whenever I try to upgrade to either the 5.15 or 5.16 series my VM hangs at boot time after: EFI stub: Booting Linux Kernel... EFI stub: EFI_RNG_PROTOCOL unavailable EFI stub: ERROR: FIRMWARE BUG: kernel image not aligned on 64k boundary EFI stub: ERROR: FIRMWARE BUG: Image BSS overlaps adjacent EFI memory region EFI stub: Using DIB from configuration table EFI stub: Exiting boot services... I see the same "hang" for both 5.15.7 and 5.16-rc4. FYI this has also been reported by others who note that the problem appears to be specific to Ubuntu: https://communities.vmware.com/t5/Fusion-for-Apple-Silicon- Tech/Anyone-have-any-luck-with-Ubuntu-5-15-kernels/m-p/2880362 Given that I can't boot using the 5.15.7 and 5.16-rc4 kernels, I can't provide the output from: cat /proc/version However I attach the output from lspci. Please let me know what other information I can provide to help diagnose this issue. Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953671/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1840122] Re: System fails to reboot from live session or ubiquity-dm - squashfs_read_data failed to read block
As we have a Conflicts=umount.target, then > It doesn't matter which of the two ordering dependencies is > used, because stop jobs are always ordered before start jobs literally as xnox said. I'm preparing a finalrd with Before=umount.target in a PPA. -- 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/1840122 Title: System fails to reboot from live session or ubiquity-dm - squashfs_read_data failed to read block Status in subiquity: New Status in casper package in Ubuntu: New Status in finalrd package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Status in casper source package in Bionic: Fix Released Status in finalrd source package in Bionic: New Status in linux source package in Bionic: Confirmed Status in casper source package in Eoan: Fix Released Status in finalrd source package in Eoan: New Status in linux source package in Eoan: Won't Fix Status in casper source package in Focal: Fix Released Status in finalrd source package in Focal: New Status in linux source package in Focal: New Bug description: Last known good image: Eoan Ubuntu Desktop 20190715 Similar results started to happen with new linux-hwe kernel based on eoan for 18.04.4 release. Test Case: 1. Boot eoan desktop to a live session 2. Wait a couple of minutes until snapd settles 3. Reboot the system from the system menu or from the command line Expected result: The system reboots Actual result: The systems fails to reboot or shutdown and displays some errors about failing to unmount /cdrom and squashfs errors in a loop. Unmounting /cdrom... [FAILED] Failed unmounting /cdrom. [ OK ] Started Shuts down the "li…" preinstalled system cleanly. [ OK ] Reached target Final Step. [ OK ] Started Reboot. [ OK ] Reached target Reboot. [ 115.744188] print_req_error: I/O error, dev sr0, sector 1508872 flags 80700 [ 115.768139] print_req_error: I/O error, dev sr0, sector 1508872 flags 0 [ 115.771469] print_req_error: I/O error, dev loop0, sector 1501550 flags 0 [ 115.775824] SQUASHFS error: squashfs_read_data failed to read block 0x2dd2d998 This also causes daily tests to fail and is reproducible in a VM and bare metal booted in legacy bios mode ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: casper 1.414 ProcVersionSignature: Ubuntu 5.2.0-10.11-generic 5.2.4 Uname: Linux 5.2.0-10-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CasperVersion: 1.414 CurrentDesktop: ubuntu:GNOME Date: Wed Aug 14 08:31:30 2019 LiveMediaBuild: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190813) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: casper UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CasperVersion: 1.414 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 LiveMediaBuild: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190814) Package: linux PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.2.0-10.11-generic 5.2.4 Tags: eoan Uname: Linux 5.2.0-10-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1788 F pulseaudio CasperVersion: 1.414 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 IwConfig: lono wireless extensions. ens3 no wireless extensions. LiveMediaBuild: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190814) Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 qxldrmfb ProcKernelCmdLine: file=/cdrom/preseed/username.seed initrd=/casper/initrd --- keyboard-configuration/layoutcode=fr keyboard-configuration/variantcode=oss ProcVersionSignature: Ubuntu 5.2.0-10.11-generic 5.2.4 RelatedPackageVersions: linux-restricted-modules-5.2.0-10-generic N/A linux-backports-modules-5.2.0-10-generic N/A linux-firmware
[Kernel-packages] [Bug 1930086] 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 1930086 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 ** Tags added: jammy -- 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/1930086 Title: [22.04 FEAT] gcc tunings for power9 Status in The Ubuntu-power-systems project: In Progress Status in gcc-11 package in Ubuntu: In Progress Status in linux package in Ubuntu: Incomplete Status in llvm-toolchain-13 package in Ubuntu: In Progress Bug description: This is an Ubuntu-power-systems 22.04 LTS feature bug to track changing the gcc configure options from --with-cpu=power8 to --with- cpu=power9. Prerequisites for this bug include power9 builder hardware in Canonical datacenter. I'm still learning my way around Debian/Ubuntu source so go easy on me if this isn't the correct branch: https://salsa.debian.org/toolchain- team/gcc/-/blob/gcc-10-debian/debian/rules2#L394 But we'll want to add some logic around line 394 to add --with- cpu=power9 for 22.04 and possibly --with-tune=? but I'll reverse mirror this bug and verify with our IBM Power toolchain architect. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1930086/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1930086] Re: [22.04 FEAT] gcc tunings for power9
** Changed in: linux (Ubuntu) Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: linux (Ubuntu) Status: Incomplete => 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/1930086 Title: [22.04 FEAT] gcc tunings for power9 Status in The Ubuntu-power-systems project: In Progress Status in gcc-11 package in Ubuntu: In Progress Status in linux package in Ubuntu: New Status in llvm-toolchain-13 package in Ubuntu: In Progress Bug description: This is an Ubuntu-power-systems 22.04 LTS feature bug to track changing the gcc configure options from --with-cpu=power8 to --with- cpu=power9. Prerequisites for this bug include power9 builder hardware in Canonical datacenter. I'm still learning my way around Debian/Ubuntu source so go easy on me if this isn't the correct branch: https://salsa.debian.org/toolchain- team/gcc/-/blob/gcc-10-debian/debian/rules2#L394 But we'll want to add some logic around line 394 to add --with- cpu=power9 for 22.04 and possibly --with-tune=? but I'll reverse mirror this bug and verify with our IBM Power toolchain architect. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1930086/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1953554] Re: NETDEV WATCHDOG: waneth (ax88179_178a): transmit queue 0 timed out
As side note, today I've installed Mainline kernel to test if same thing happens. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1953554 Title: NETDEV WATCHDOG: waneth (ax88179_178a): transmit queue 0 timed out Status in linux package in Ubuntu: Confirmed Bug description: Hi, I am facing this problem in Focal with the USB 3.0 Ethernet Gigabit adapter "ASIX Electronics Corp. AX88179 Gigabit Ethernet" (waneth is the name I assigned to this ethernet connected to the cable modem/router): [ cut here ] [94104.121581] NETDEV WATCHDOG: waneth (ax88179_178a): transmit queue 0 timed out [94104.121606] WARNING: CPU: 2 PID: 217952 at net/sched/sch_generic.c:467 dev_watchdog+0x24f/0x260 [94104.121615] Modules linked in: binfmt_misc xt_recent nfnetlink nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua snd_sof_pci_intel_apl snd_sof_intel_hda_common soundwire_intel soundwire_generic_allocation soundwire_cadence snd_sof_intel_hda snd_sof_pci snd_sof_xtensa_dsp snd_sof soundwire_bus snd_soc_skl snd_soc_hdac_hda snd_hda_ext_core intel_rapl_msr snd_soc_sst_ipc intel_rapl_common 8814au(OE) mei_hdcp snd_soc_sst_dsp snd_soc_acpi_intel_match snd_soc_acpi intel_pmc_bxt snd_soc_core intel_telemetry_pltdrv intel_punit_ipc snd_compress intel_telemetry_core snd_hda_codec_hdmi x86_pkg_temp_thermal intel_powerclamp snd_hda_codec_realtek coretemp snd_hda_codec_generic ac97_bus ledtrig_audio snd_pcm_dmaengine kvm_intel snd_hda_intel kvm snd_intel_dspcfg snd_intel_sdw_acpi snd_hda_codec rapl intel_cstate snd_hda_core snd_hwdep snd_pcm snd_timer ax88179_178a cfg80211 efi_pstore mei_me usbnet ee1004 snd mii soundcore mei mac_hid bridge ip6t_REJECT nf_reject_ipv6 stp llc xt_hl [94104.121696] ip6t_rt ipt_REJECT nf_reject_ipv4 xt_LOG nf_log_syslog xt_limit xt_addrtype xt_tcpudp xt_MASQUERADE iptable_nat nf_nat xt_conntrack nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 ip6table_filter ip6_tables sch_fq_codel iptable_filter bpfilter msr ip_tables x_tables autofs4 btrfs blake2b_generic zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear uas usb_storage i915 i2c_algo_bit drm_kms_helper crct10dif_pclmul crc32_pclmul ghash_clmulni_intel syscopyarea sysfillrect sysimgblt fb_sys_fops cec rc_core aesni_intel crypto_simd i2c_i801 xhci_pci i2c_smbus cryptd r8169 realtek xhci_pci_renesas drm sdhci_pci ahci cqhci sdhci libahci video [94104.121771] CPU: 2 PID: 217952 Comm: PLUGIN[cgroups] Tainted: G OE 5.13.0-22-generic #22~20.04.1-Ubuntu [94104.121775] Hardware name: GIGABYTE MZGLKDP-00/MZGLKDP-00, BIOS F1 12/21/2017 [94104.121777] RIP: 0010:dev_watchdog+0x24f/0x260 [94104.121782] Code: c7 36 fd ff eb ab 4c 89 ff c6 05 60 f1 6e 01 01 e8 86 11 fa ff 44 89 e9 4c 89 fe 48 c7 c7 20 9c ca 89 48 89 c2 e8 38 17 17 00 <0f> 0b eb 8c 66 66 2e 0f 1f 84 00 00 00 00 00 66 90 0f 1f 44 00 00 [94104.121785] RSP: 0018:b515c0138e88 EFLAGS: 00010282 [94104.121788] RAX: RBX: 91214fc45e00 RCX: 0027 [94104.121790] RDX: 0027 RSI: dfff RDI: 9124b05189c8 [94104.121792] RBP: b515c0138eb8 R08: 9124b05189c0 R09: b515c0138c60 [94104.121794] R10: 0001 R11: 0001 R12: 0001 [94104.121795] R13: R14: 912154a7d480 R15: 912154a7d000 [94104.121797] FS: 7f74619e5700() GS:9124b050() knlGS: [94104.121800] CS: 0010 DS: ES: CR0: 80050033 [94104.121802] CR2: 5635dd41b584 CR3: 00020592a000 CR4: 00350ee0 [94104.121805] Call Trace: [94104.121807] [94104.121812] ? pfifo_fast_enqueue+0x150/0x150 [94104.121816] call_timer_fn+0x2c/0x100 [94104.121821] run_timer_softirq+0x3d7/0x480 [94104.121824] ? perf_trace_softirq+0x9d/0xd0 [94104.121829] __do_softirq+0xdd/0x29b [94104.121835] irq_exit_rcu+0xa4/0xb0 [94104.121837] sysvec_apic_timer_interrupt+0x7c/0x90 [94104.121841] [94104.121843] asm_sysvec_apic_timer_interrupt+0x12/0x20 [94104.121846] RIP: 0010:errseq_sample+0x2/0x10 [94104.121850] Code: ff 48 d3 e2 48 f7 d2 48 21 d0 0f 01 ca 48 85 c0 0f 94 c0 0f b6 c0 c3 b8 01 00 00 00 c3 b8 f2 ff ff ff c3 cc cc cc cc cc 8b 07 00 00 00 00 f6 c4 10 0f 44 c2 c3 66 90 8b 17 31 c0 39 16 74 1b [94104.121853] RSP: 0018:b515c29cfb68 EFLAGS: 0286 [94104.121855] RAX: RBX: 91214298e500 RCX: 0002 [94104.121857] RDX: 0001 RSI: 0002 RDI: 91218c293c88 [94104.121859] RBP: b515c29cfba0 R08: 91221987a160 R09: 9121e1e8c180 [94104.121860] R10: 00746174 R11: 8196e1bd R12: 91218c293a98 [94104.121862]
[Kernel-packages] [Bug 1953554] Re: NETDEV WATCHDOG: waneth (ax88179_178a): transmit queue 0 timed out
apport information ** Tags added: apport-collected focal ** Description changed: Hi, I am facing this problem in Focal with the USB 3.0 Ethernet Gigabit adapter "ASIX Electronics Corp. AX88179 Gigabit Ethernet" (waneth is the name I assigned to this ethernet connected to the cable modem/router): [ cut here ] [94104.121581] NETDEV WATCHDOG: waneth (ax88179_178a): transmit queue 0 timed out [94104.121606] WARNING: CPU: 2 PID: 217952 at net/sched/sch_generic.c:467 dev_watchdog+0x24f/0x260 [94104.121615] Modules linked in: binfmt_misc xt_recent nfnetlink nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua snd_sof_pci_intel_apl snd_sof_intel_hda_common soundwire_intel soundwire_generic_allocation soundwire_cadence snd_sof_intel_hda snd_sof_pci snd_sof_xtensa_dsp snd_sof soundwire_bus snd_soc_skl snd_soc_hdac_hda snd_hda_ext_core intel_rapl_msr snd_soc_sst_ipc intel_rapl_common 8814au(OE) mei_hdcp snd_soc_sst_dsp snd_soc_acpi_intel_match snd_soc_acpi intel_pmc_bxt snd_soc_core intel_telemetry_pltdrv intel_punit_ipc snd_compress intel_telemetry_core snd_hda_codec_hdmi x86_pkg_temp_thermal intel_powerclamp snd_hda_codec_realtek coretemp snd_hda_codec_generic ac97_bus ledtrig_audio snd_pcm_dmaengine kvm_intel snd_hda_intel kvm snd_intel_dspcfg snd_intel_sdw_acpi snd_hda_codec rapl intel_cstate snd_hda_core snd_hwdep snd_pcm snd_timer ax88179_178a cfg80211 efi_pstore mei_me usbnet ee1004 snd mii soundcore mei mac_hid bridge ip6t_REJECT nf_reject_ipv6 stp llc xt_hl [94104.121696] ip6t_rt ipt_REJECT nf_reject_ipv4 xt_LOG nf_log_syslog xt_limit xt_addrtype xt_tcpudp xt_MASQUERADE iptable_nat nf_nat xt_conntrack nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 ip6table_filter ip6_tables sch_fq_codel iptable_filter bpfilter msr ip_tables x_tables autofs4 btrfs blake2b_generic zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear uas usb_storage i915 i2c_algo_bit drm_kms_helper crct10dif_pclmul crc32_pclmul ghash_clmulni_intel syscopyarea sysfillrect sysimgblt fb_sys_fops cec rc_core aesni_intel crypto_simd i2c_i801 xhci_pci i2c_smbus cryptd r8169 realtek xhci_pci_renesas drm sdhci_pci ahci cqhci sdhci libahci video [94104.121771] CPU: 2 PID: 217952 Comm: PLUGIN[cgroups] Tainted: G OE 5.13.0-22-generic #22~20.04.1-Ubuntu [94104.121775] Hardware name: GIGABYTE MZGLKDP-00/MZGLKDP-00, BIOS F1 12/21/2017 [94104.121777] RIP: 0010:dev_watchdog+0x24f/0x260 [94104.121782] Code: c7 36 fd ff eb ab 4c 89 ff c6 05 60 f1 6e 01 01 e8 86 11 fa ff 44 89 e9 4c 89 fe 48 c7 c7 20 9c ca 89 48 89 c2 e8 38 17 17 00 <0f> 0b eb 8c 66 66 2e 0f 1f 84 00 00 00 00 00 66 90 0f 1f 44 00 00 [94104.121785] RSP: 0018:b515c0138e88 EFLAGS: 00010282 [94104.121788] RAX: RBX: 91214fc45e00 RCX: 0027 [94104.121790] RDX: 0027 RSI: dfff RDI: 9124b05189c8 [94104.121792] RBP: b515c0138eb8 R08: 9124b05189c0 R09: b515c0138c60 [94104.121794] R10: 0001 R11: 0001 R12: 0001 [94104.121795] R13: R14: 912154a7d480 R15: 912154a7d000 [94104.121797] FS: 7f74619e5700() GS:9124b050() knlGS: [94104.121800] CS: 0010 DS: ES: CR0: 80050033 [94104.121802] CR2: 5635dd41b584 CR3: 00020592a000 CR4: 00350ee0 [94104.121805] Call Trace: [94104.121807] [94104.121812] ? pfifo_fast_enqueue+0x150/0x150 [94104.121816] call_timer_fn+0x2c/0x100 [94104.121821] run_timer_softirq+0x3d7/0x480 [94104.121824] ? perf_trace_softirq+0x9d/0xd0 [94104.121829] __do_softirq+0xdd/0x29b [94104.121835] irq_exit_rcu+0xa4/0xb0 [94104.121837] sysvec_apic_timer_interrupt+0x7c/0x90 [94104.121841] [94104.121843] asm_sysvec_apic_timer_interrupt+0x12/0x20 [94104.121846] RIP: 0010:errseq_sample+0x2/0x10 [94104.121850] Code: ff 48 d3 e2 48 f7 d2 48 21 d0 0f 01 ca 48 85 c0 0f 94 c0 0f b6 c0 c3 b8 01 00 00 00 c3 b8 f2 ff ff ff c3 cc cc cc cc cc 8b 07 00 00 00 00 f6 c4 10 0f 44 c2 c3 66 90 8b 17 31 c0 39 16 74 1b [94104.121853] RSP: 0018:b515c29cfb68 EFLAGS: 0286 [94104.121855] RAX: RBX: 91214298e500 RCX: 0002 [94104.121857] RDX: 0001 RSI: 0002 RDI: 91218c293c88 [94104.121859] RBP: b515c29cfba0 R08: 91221987a160 R09: 9121e1e8c180 [94104.121860] R10: 00746174 R11: 8196e1bd R12: 91218c293a98 [94104.121862] R13: R14: 91214298e510 R15: 91214298e500 [94104.121869] ? do_dentry_open+0x44/0x370 [94104.121873] vfs_open+0x2d/0x30 [94104.121877] do_open.isra.0+0x205/0x3e0 [94104.121881] path_openat+0x18e/0xc80 [94104.121884] ? do_sys_openat2+0x1/0x310 [94104.121887] ? page_counter_cancel+0x2c/0x70 [94104.121891] do_filp_open+0xa2/0x110
[Kernel-packages] [Bug 1840122] Re: System fails to reboot from live session or ubiquity-dm - squashfs_read_data failed to read block
Hmm but umount.target is special (as in systemd.special(7)), so that's not so obvious... -- 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/1840122 Title: System fails to reboot from live session or ubiquity-dm - squashfs_read_data failed to read block Status in subiquity: New Status in casper package in Ubuntu: New Status in finalrd package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Status in casper source package in Bionic: Fix Released Status in finalrd source package in Bionic: New Status in linux source package in Bionic: Confirmed Status in casper source package in Eoan: Fix Released Status in finalrd source package in Eoan: New Status in linux source package in Eoan: Won't Fix Status in casper source package in Focal: Fix Released Status in finalrd source package in Focal: New Status in linux source package in Focal: New Bug description: Last known good image: Eoan Ubuntu Desktop 20190715 Similar results started to happen with new linux-hwe kernel based on eoan for 18.04.4 release. Test Case: 1. Boot eoan desktop to a live session 2. Wait a couple of minutes until snapd settles 3. Reboot the system from the system menu or from the command line Expected result: The system reboots Actual result: The systems fails to reboot or shutdown and displays some errors about failing to unmount /cdrom and squashfs errors in a loop. Unmounting /cdrom... [FAILED] Failed unmounting /cdrom. [ OK ] Started Shuts down the "li…" preinstalled system cleanly. [ OK ] Reached target Final Step. [ OK ] Started Reboot. [ OK ] Reached target Reboot. [ 115.744188] print_req_error: I/O error, dev sr0, sector 1508872 flags 80700 [ 115.768139] print_req_error: I/O error, dev sr0, sector 1508872 flags 0 [ 115.771469] print_req_error: I/O error, dev loop0, sector 1501550 flags 0 [ 115.775824] SQUASHFS error: squashfs_read_data failed to read block 0x2dd2d998 This also causes daily tests to fail and is reproducible in a VM and bare metal booted in legacy bios mode ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: casper 1.414 ProcVersionSignature: Ubuntu 5.2.0-10.11-generic 5.2.4 Uname: Linux 5.2.0-10-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CasperVersion: 1.414 CurrentDesktop: ubuntu:GNOME Date: Wed Aug 14 08:31:30 2019 LiveMediaBuild: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190813) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: casper UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CasperVersion: 1.414 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 LiveMediaBuild: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190814) Package: linux PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.2.0-10.11-generic 5.2.4 Tags: eoan Uname: Linux 5.2.0-10-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1788 F pulseaudio CasperVersion: 1.414 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 IwConfig: lono wireless extensions. ens3 no wireless extensions. LiveMediaBuild: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190814) Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 qxldrmfb ProcKernelCmdLine: file=/cdrom/preseed/username.seed initrd=/casper/initrd --- keyboard-configuration/layoutcode=fr keyboard-configuration/variantcode=oss ProcVersionSignature: Ubuntu 5.2.0-10.11-generic 5.2.4 RelatedPackageVersions: linux-restricted-modules-5.2.0-10-generic N/A linux-backports-modules-5.2.0-10-generic N/A linux-firmware1.181 RfKill: Tags: eoan Uname: Linux 5.2.0-10-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm
[Kernel-packages] [Bug 1950903] Re: kernel package does not build nvme-tcp module
Hello, any progress on this? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1950903 Title: kernel package does not build nvme-tcp module Status in linux-aws package in Ubuntu: Confirmed Bug description: linux-image-5.4.0-1059-aws does not build nvme-tcp kernel module so there is no option to use it. The fix is trivial, just add CONFIG_NVME_TCP=m in the kernel config file used to build the kernel image. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1950903/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1953199] Re: 0-byte files created in overlay filesystem
FYI, Linux v5.10.84 (https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/log/?h=linux-5.10.y) has now been tagged with the fixes for the overlay filesystem: 1. https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=linux-5.10.y=dca4f9a581967a81cf4420bdd26162112d546031 1. https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=linux-5.10.y=bcce010f92308368ac27248342e6ccd058e8c596 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-base in Ubuntu. https://bugs.launchpad.net/bugs/1953199 Title: 0-byte files created in overlay filesystem Status in linux-base package in Ubuntu: New Bug description: Copied from https://lore.kernel.org/stable/CAMBWrQ=1mkxnmt_6jnqp_xxr7psvywpbjc6p1qcy9eny8rf...@mail.gmail.com/: A number of users have reported that under certain conditions using the overlay filesystem, copy_file_range() can unexpectedly create a 0-byte file. [0] This bug can cause significant problems because applications that copy files expect the target file to match the source immediately after the copy. After upgrading from Linux 5.4 to Linux 5.10, our Docker-based CI tests started failing due to this bug, since Ruby's IO.copy_stream uses this system call. We have worked around the problem by touching the target file before using it, but this shouldn't be necessary. Other projects, such as Rust, have added similar workarounds. [1] As discussed in the linux-fsdevel mailing list [2], the bug appears to be present in Linux 5.6 to 5.10, but not in Linux 5.11. We should be able to cherry-pick the following upstream patches to fix this. Could you cherry-pick them to 5.10.x stable? I've confirmed that these patches, applied from top to bottom to that branch, pass the reproduction test [3]: 82a763e61e2b601309d696d4fa514c77d64ee1be 9b91b6b019fda817eb52f728eb9c79b3579760bc The diffstat: fs/overlayfs/file.c | 59 +++ 1 file changed, 31 insertions(+), 28 deletions(-) Note that these patches do not pick cleanly into 5.6.x - 5.9.x stable. [0] https://github.com/docker/for-linux/issues/1015 [1] https://github.com/rust-lang/rust/blob/342db70ae4ecc3cd17e4fa6497f0a8d9534ccfeb/library/std/src/sys/unix/kernel_copy.rs#L565-L569 [2] https://marc.info/?l=linux-fsdevel=163847383311699=2 [3] https://github.com/docker/for-linux/issues/1015#issuecomment-841915668 --- I reproduced this bug in Ubuntu 18.04: ``` # bash test.sh Sending build context to Docker daemon 43.05kB Step 1/2 : FROM debian:10.8-slim ---> 115566c891d1 Step 2/2 : RUN apt update && apt install -y gcc strace ---> Using cache ---> 0dfb7ffcd427 Successfully built 0dfb7ffcd427 Successfully tagged strace:latest Local: OK Docker - mounted: Copy failed Docker - copied: OK ``` ``` root@stanhu-ubuntu-18:/home/stanhu# lsb_release -rd Description: Ubuntu 18.04.6 LTS Release: 18.04 root@stanhu-ubuntu-18:/home/stanhu# uname -r 5.4.0-1057-gcp ``` Per [the latest update on the kernel stable mailing list](https://lore.kernel.org/stable/yanx6kobwiqob...@kroah.com), the kernel backport fix for 5.10 has been queued for review and should land in the [`stable-5.10.y` branch](https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/log/?h=linux-5.10.y) soon. To avoid this bug, I'd suggest avoid Linux v5.6.0 - v5.10.83 for now, unless you backport the two patches below: 1. https://github.com/torvalds/linux/commit/@82a763e61e2b601309d696d4fa514c77d64ee1be 1. https://github.com/torvalds/linux/commit/@9b91b6b019fda817eb52f728eb9c79b3579760bc I've confirmed that 5.5.19 does NOT have this bug, and it was introduced in 5.6.0 via https://github.com/torvalds/linux/commit/1a980b8cbf0059a5308eea61522f232fd03002e2. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-base/+bug/1953199/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1953554] 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 1953554 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 ** Tags added: 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/1953554 Title: NETDEV WATCHDOG: waneth (ax88179_178a): transmit queue 0 timed out Status in linux package in Ubuntu: Incomplete Bug description: Hi, I am facing this problem in Focal with the USB 3.0 Ethernet Gigabit adapter "ASIX Electronics Corp. AX88179 Gigabit Ethernet" (waneth is the name I assigned to this ethernet connected to the cable modem/router): [ cut here ] [94104.121581] NETDEV WATCHDOG: waneth (ax88179_178a): transmit queue 0 timed out [94104.121606] WARNING: CPU: 2 PID: 217952 at net/sched/sch_generic.c:467 dev_watchdog+0x24f/0x260 [94104.121615] Modules linked in: binfmt_misc xt_recent nfnetlink nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua snd_sof_pci_intel_apl snd_sof_intel_hda_common soundwire_intel soundwire_generic_allocation soundwire_cadence snd_sof_intel_hda snd_sof_pci snd_sof_xtensa_dsp snd_sof soundwire_bus snd_soc_skl snd_soc_hdac_hda snd_hda_ext_core intel_rapl_msr snd_soc_sst_ipc intel_rapl_common 8814au(OE) mei_hdcp snd_soc_sst_dsp snd_soc_acpi_intel_match snd_soc_acpi intel_pmc_bxt snd_soc_core intel_telemetry_pltdrv intel_punit_ipc snd_compress intel_telemetry_core snd_hda_codec_hdmi x86_pkg_temp_thermal intel_powerclamp snd_hda_codec_realtek coretemp snd_hda_codec_generic ac97_bus ledtrig_audio snd_pcm_dmaengine kvm_intel snd_hda_intel kvm snd_intel_dspcfg snd_intel_sdw_acpi snd_hda_codec rapl intel_cstate snd_hda_core snd_hwdep snd_pcm snd_timer ax88179_178a cfg80211 efi_pstore mei_me usbnet ee1004 snd mii soundcore mei mac_hid bridge ip6t_REJECT nf_reject_ipv6 stp llc xt_hl [94104.121696] ip6t_rt ipt_REJECT nf_reject_ipv4 xt_LOG nf_log_syslog xt_limit xt_addrtype xt_tcpudp xt_MASQUERADE iptable_nat nf_nat xt_conntrack nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 ip6table_filter ip6_tables sch_fq_codel iptable_filter bpfilter msr ip_tables x_tables autofs4 btrfs blake2b_generic zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear uas usb_storage i915 i2c_algo_bit drm_kms_helper crct10dif_pclmul crc32_pclmul ghash_clmulni_intel syscopyarea sysfillrect sysimgblt fb_sys_fops cec rc_core aesni_intel crypto_simd i2c_i801 xhci_pci i2c_smbus cryptd r8169 realtek xhci_pci_renesas drm sdhci_pci ahci cqhci sdhci libahci video [94104.121771] CPU: 2 PID: 217952 Comm: PLUGIN[cgroups] Tainted: G OE 5.13.0-22-generic #22~20.04.1-Ubuntu [94104.121775] Hardware name: GIGABYTE MZGLKDP-00/MZGLKDP-00, BIOS F1 12/21/2017 [94104.121777] RIP: 0010:dev_watchdog+0x24f/0x260 [94104.121782] Code: c7 36 fd ff eb ab 4c 89 ff c6 05 60 f1 6e 01 01 e8 86 11 fa ff 44 89 e9 4c 89 fe 48 c7 c7 20 9c ca 89 48 89 c2 e8 38 17 17 00 <0f> 0b eb 8c 66 66 2e 0f 1f 84 00 00 00 00 00 66 90 0f 1f 44 00 00 [94104.121785] RSP: 0018:b515c0138e88 EFLAGS: 00010282 [94104.121788] RAX: RBX: 91214fc45e00 RCX: 0027 [94104.121790] RDX: 0027 RSI: dfff RDI: 9124b05189c8 [94104.121792] RBP: b515c0138eb8 R08: 9124b05189c0 R09: b515c0138c60 [94104.121794] R10: 0001 R11: 0001 R12: 0001 [94104.121795] R13: R14: 912154a7d480 R15: 912154a7d000 [94104.121797] FS: 7f74619e5700() GS:9124b050() knlGS: [94104.121800] CS: 0010 DS: ES: CR0: 80050033 [94104.121802] CR2: 5635dd41b584 CR3: 00020592a000 CR4: 00350ee0 [94104.121805] Call Trace: [94104.121807] [94104.121812] ? pfifo_fast_enqueue+0x150/0x150 [94104.121816] call_timer_fn+0x2c/0x100 [94104.121821] run_timer_softirq+0x3d7/0x480 [94104.121824] ? perf_trace_softirq+0x9d/0xd0 [94104.121829] __do_softirq+0xdd/0x29b [94104.121835] irq_exit_rcu+0xa4/0xb0 [94104.121837] sysvec_apic_timer_interrupt+0x7c/0x90 [94104.121841] [94104.121843] asm_sysvec_apic_timer_interrupt+0x12/0x20 [94104.121846] RIP: 0010:errseq_sample+0x2/0x10 [94104.121850] Code: ff 48 d3 e2 48 f7 d2 48 21 d0 0f 01 ca 48 85 c0 0f 94 c0 0f b6 c0 c3 b8 01 00 00 00 c3 b8 f2 ff ff ff c3 cc cc cc cc cc 8b 07 00
[Kernel-packages] [Bug 1952011] Re: [SRU] linux-firmware: add sof-firmware for adl platforms from sof-firmware-v1.9.2
** Changed in: linux-firmware (Ubuntu Hirsute) Status: In Progress => Fix Committed ** Changed in: linux-firmware (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-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1952011 Title: [SRU] linux-firmware: add sof-firmware for adl platforms from sof- firmware-v1.9.2 Status in HWE Next: New Status in linux-firmware package in Ubuntu: New Status in linux-firmware source package in Focal: Fix Committed Status in linux-firmware source package in Hirsute: Fix Committed Status in linux-firmware source package in Impish: Fix Committed Bug description: Because we plan to remove sof-firmware related files from linux-firmware of jammy and replace them with a debian package firmware-sof-signed, so this SRU is not applied to jammy. I will submit another SRU to firmware-sof-signed package later. [Impact] In the Dell oem project, we have many laptops which has sof dmic or sof soundwire audio design, they need to load firmware and topology files specific to ADL, otherwise the audio driver will fail to initialize and the whole audio can't work. [Fix] Integrate the firmware and topology files from sof-firmware-v1.9.2 [Test] Installed the patched linux-firmware and booting the patched kernel, the audio work well, all output and input devices work normally [Where problems could occur] This SRU introduces new firmware and topology files for adl, it has low possibility to introduce regression. If it could, it could possibilily affect the other machines which also need to load firmware and topology files, it could make the audio can't work on those machines, but this possibility is very low, we have tested the SRU on many laptops, no regression found. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1952011/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1953554] Re: NETDEV WATCHDOG: waneth (ax88179_178a): transmit queue 0 timed out
** Package changed: linux-hwe-5.13 (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/1953554 Title: NETDEV WATCHDOG: waneth (ax88179_178a): transmit queue 0 timed out Status in linux package in Ubuntu: New Bug description: Hi, I am facing this problem in Focal with the USB 3.0 Ethernet Gigabit adapter "ASIX Electronics Corp. AX88179 Gigabit Ethernet" (waneth is the name I assigned to this ethernet connected to the cable modem/router): [ cut here ] [94104.121581] NETDEV WATCHDOG: waneth (ax88179_178a): transmit queue 0 timed out [94104.121606] WARNING: CPU: 2 PID: 217952 at net/sched/sch_generic.c:467 dev_watchdog+0x24f/0x260 [94104.121615] Modules linked in: binfmt_misc xt_recent nfnetlink nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua snd_sof_pci_intel_apl snd_sof_intel_hda_common soundwire_intel soundwire_generic_allocation soundwire_cadence snd_sof_intel_hda snd_sof_pci snd_sof_xtensa_dsp snd_sof soundwire_bus snd_soc_skl snd_soc_hdac_hda snd_hda_ext_core intel_rapl_msr snd_soc_sst_ipc intel_rapl_common 8814au(OE) mei_hdcp snd_soc_sst_dsp snd_soc_acpi_intel_match snd_soc_acpi intel_pmc_bxt snd_soc_core intel_telemetry_pltdrv intel_punit_ipc snd_compress intel_telemetry_core snd_hda_codec_hdmi x86_pkg_temp_thermal intel_powerclamp snd_hda_codec_realtek coretemp snd_hda_codec_generic ac97_bus ledtrig_audio snd_pcm_dmaengine kvm_intel snd_hda_intel kvm snd_intel_dspcfg snd_intel_sdw_acpi snd_hda_codec rapl intel_cstate snd_hda_core snd_hwdep snd_pcm snd_timer ax88179_178a cfg80211 efi_pstore mei_me usbnet ee1004 snd mii soundcore mei mac_hid bridge ip6t_REJECT nf_reject_ipv6 stp llc xt_hl [94104.121696] ip6t_rt ipt_REJECT nf_reject_ipv4 xt_LOG nf_log_syslog xt_limit xt_addrtype xt_tcpudp xt_MASQUERADE iptable_nat nf_nat xt_conntrack nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 ip6table_filter ip6_tables sch_fq_codel iptable_filter bpfilter msr ip_tables x_tables autofs4 btrfs blake2b_generic zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear uas usb_storage i915 i2c_algo_bit drm_kms_helper crct10dif_pclmul crc32_pclmul ghash_clmulni_intel syscopyarea sysfillrect sysimgblt fb_sys_fops cec rc_core aesni_intel crypto_simd i2c_i801 xhci_pci i2c_smbus cryptd r8169 realtek xhci_pci_renesas drm sdhci_pci ahci cqhci sdhci libahci video [94104.121771] CPU: 2 PID: 217952 Comm: PLUGIN[cgroups] Tainted: G OE 5.13.0-22-generic #22~20.04.1-Ubuntu [94104.121775] Hardware name: GIGABYTE MZGLKDP-00/MZGLKDP-00, BIOS F1 12/21/2017 [94104.121777] RIP: 0010:dev_watchdog+0x24f/0x260 [94104.121782] Code: c7 36 fd ff eb ab 4c 89 ff c6 05 60 f1 6e 01 01 e8 86 11 fa ff 44 89 e9 4c 89 fe 48 c7 c7 20 9c ca 89 48 89 c2 e8 38 17 17 00 <0f> 0b eb 8c 66 66 2e 0f 1f 84 00 00 00 00 00 66 90 0f 1f 44 00 00 [94104.121785] RSP: 0018:b515c0138e88 EFLAGS: 00010282 [94104.121788] RAX: RBX: 91214fc45e00 RCX: 0027 [94104.121790] RDX: 0027 RSI: dfff RDI: 9124b05189c8 [94104.121792] RBP: b515c0138eb8 R08: 9124b05189c0 R09: b515c0138c60 [94104.121794] R10: 0001 R11: 0001 R12: 0001 [94104.121795] R13: R14: 912154a7d480 R15: 912154a7d000 [94104.121797] FS: 7f74619e5700() GS:9124b050() knlGS: [94104.121800] CS: 0010 DS: ES: CR0: 80050033 [94104.121802] CR2: 5635dd41b584 CR3: 00020592a000 CR4: 00350ee0 [94104.121805] Call Trace: [94104.121807] [94104.121812] ? pfifo_fast_enqueue+0x150/0x150 [94104.121816] call_timer_fn+0x2c/0x100 [94104.121821] run_timer_softirq+0x3d7/0x480 [94104.121824] ? perf_trace_softirq+0x9d/0xd0 [94104.121829] __do_softirq+0xdd/0x29b [94104.121835] irq_exit_rcu+0xa4/0xb0 [94104.121837] sysvec_apic_timer_interrupt+0x7c/0x90 [94104.121841] [94104.121843] asm_sysvec_apic_timer_interrupt+0x12/0x20 [94104.121846] RIP: 0010:errseq_sample+0x2/0x10 [94104.121850] Code: ff 48 d3 e2 48 f7 d2 48 21 d0 0f 01 ca 48 85 c0 0f 94 c0 0f b6 c0 c3 b8 01 00 00 00 c3 b8 f2 ff ff ff c3 cc cc cc cc cc 8b 07 00 00 00 00 f6 c4 10 0f 44 c2 c3 66 90 8b 17 31 c0 39 16 74 1b [94104.121853] RSP: 0018:b515c29cfb68 EFLAGS: 0286 [94104.121855] RAX: RBX: 91214298e500 RCX: 0002 [94104.121857] RDX: 0001 RSI: 0002 RDI: 91218c293c88 [94104.121859] RBP: b515c29cfba0 R08: 91221987a160 R09: 9121e1e8c180 [94104.121860] R10: 00746174 R11: 8196e1bd R12: 91218c293a98 [94104.121862] R13: R14: 91214298e510 R15: 91214298e500 [94104.121869] ?
[Kernel-packages] [Bug 1953522] 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 1953522 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/1953522 Title: Ubuntu version macros overflow with high ABI numbers Status in linux package in Ubuntu: Incomplete Status in lttng-modules package in Ubuntu: Confirmed Status in linux source package in Bionic: Triaged Status in lttng-modules source package in Bionic: Triaged Bug description: [SRU Justification] == Impact == The kernel change (which may or may not be taken back) revealed a build issue we already have with lltng-modules and our high ABI numbers for derivative/custom kernels. It should be fixed regardless of what the kernel will do. == Fix == The proposed fix changes macros which are used to do run-time adaptions of code based on the kernel version for which the DKMS modules are built for. The number keys which the macros are using are not included in the code and the way those are used will either cause build failures or produce the same code as before. == Test case == Producing DKMS modules is the test case here. I did tests with the previous bionic:linux-snapdragon (which uses the old sub-level in the kernel) and the same kernel in proposed which has the sub-level set to 255 fix). Both worked. == Regression Potential == Building DKMS modules for lttng could start to fail. --- An upstream kernel change which was introduced to avoid high sub-level numbers in 4.14.y to overflow into the minor number has uncovered a similar issue with LTTNG's macros which allow versioned code adaptions. To allow that the ABI number of the kernel is inserted as a new sub- sub-level number. Which is done by shifting the existing LINUX_VERSION_CODE by another 8 bits. But this only allows for ABI numbers up to 255. After that they overflow into the sub-level part of the kernel. This went unnoticed until the kernel side changed this number to be 255 fix. Now the overflow reaches the minor number and this breaks assumptions in the code. For example bionic:linux-snapdragon (-1117) fails to produce lttng- modules (DKMS) but the previous version would succeed. When changing the LINUX_VERSION_CODE back, this works in both cases. Since the macros are only used to make compile time decisions the proposed fix would be to extend the ABI number size to 16bit. That will work in all cases. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953522/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1953522] Re: Ubuntu version macros overflow with high ABI numbers
** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Bionic) Status: New => Triaged -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1953522 Title: Ubuntu version macros overflow with high ABI numbers Status in linux package in Ubuntu: New Status in lttng-modules package in Ubuntu: Confirmed Status in linux source package in Bionic: Triaged Status in lttng-modules source package in Bionic: Triaged Bug description: [SRU Justification] == Impact == The kernel change (which may or may not be taken back) revealed a build issue we already have with lltng-modules and our high ABI numbers for derivative/custom kernels. It should be fixed regardless of what the kernel will do. == Fix == The proposed fix changes macros which are used to do run-time adaptions of code based on the kernel version for which the DKMS modules are built for. The number keys which the macros are using are not included in the code and the way those are used will either cause build failures or produce the same code as before. == Test case == Producing DKMS modules is the test case here. I did tests with the previous bionic:linux-snapdragon (which uses the old sub-level in the kernel) and the same kernel in proposed which has the sub-level set to 255 fix). Both worked. == Regression Potential == Building DKMS modules for lttng could start to fail. --- An upstream kernel change which was introduced to avoid high sub-level numbers in 4.14.y to overflow into the minor number has uncovered a similar issue with LTTNG's macros which allow versioned code adaptions. To allow that the ABI number of the kernel is inserted as a new sub- sub-level number. Which is done by shifting the existing LINUX_VERSION_CODE by another 8 bits. But this only allows for ABI numbers up to 255. After that they overflow into the sub-level part of the kernel. This went unnoticed until the kernel side changed this number to be 255 fix. Now the overflow reaches the minor number and this breaks assumptions in the code. For example bionic:linux-snapdragon (-1117) fails to produce lttng- modules (DKMS) but the previous version would succeed. When changing the LINUX_VERSION_CODE back, this works in both cases. Since the macros are only used to make compile time decisions the proposed fix would be to extend the ABI number size to 16bit. That will work in all cases. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953522/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1930086] Re: [22.04 FEAT] gcc tunings for power9
** Package changed: gcc-defaults (Ubuntu) => gcc-11 (Ubuntu) ** Also affects: llvm-toolchain-13 (Ubuntu) Importance: Undecided Status: New ** Changed in: llvm-toolchain-13 (Ubuntu) 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/1930086 Title: [22.04 FEAT] gcc tunings for power9 Status in The Ubuntu-power-systems project: In Progress Status in gcc-11 package in Ubuntu: In Progress Status in linux package in Ubuntu: Incomplete Status in llvm-toolchain-13 package in Ubuntu: In Progress Bug description: This is an Ubuntu-power-systems 22.04 LTS feature bug to track changing the gcc configure options from --with-cpu=power8 to --with- cpu=power9. Prerequisites for this bug include power9 builder hardware in Canonical datacenter. I'm still learning my way around Debian/Ubuntu source so go easy on me if this isn't the correct branch: https://salsa.debian.org/toolchain- team/gcc/-/blob/gcc-10-debian/debian/rules2#L394 But we'll want to add some logic around line 394 to add --with- cpu=power9 for 22.04 and possibly --with-tune=? but I'll reverse mirror this bug and verify with our IBM Power toolchain architect. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1930086/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1942684] Re: Kernel 5.14.X / 5.13.14 fails to boot
New system. Ubuntu 21.10 I am on official kernel, but wanted use latest. -- 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/1942684 Title: Kernel 5.14.X / 5.13.14 fails to boot Status in linux package in Ubuntu: Confirmed Bug description: I have been testing kernels 5.14.0 and 5.14.1 since their release on https://kernel.ubuntu.com/~kernel-ppa/mainline/ and my machine fails to boot with either one. However, I am able to boot just fine with 5.14.0-rc7. journalctl -b output attached with 5.14.1 Motherboard: MSI X570 Tomahawk CPU: AMD 5900X GPU: AsusTek 6800XT OS: Hirsute 21.04 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-07-04 (62 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Tags: wayland-session hirsute Uname: Linux 5.14.0-051400rc6-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1942684/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1953287] Re: test_bpf.sh test in net of ubuntu_kernel_selftests failed on B-4.15 and variants
** Changed in: linux (Ubuntu Bionic) 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/1953287 Title: test_bpf.sh test in net of ubuntu_kernel_selftests failed on B-4.15 and variants Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Committed Bug description: [Impact] A CBPF program jumping over a large number of instructions may lead to kernel code execution. The test might fail with EINVAL or EOPNOTSUPP, which must be accounted for on different kernel versions. [Test case] Load test_bpf module. [Potential regression] Some CBPF and EBPF programs might not load. Issue found on 4.15.0-1107-ibm-gt with node onibi. This test failed without any obvious error from the test output, the summary shows there is one failure but all 344 test cases were marked as PASS: [ 1851.020315] test_bpf: #0 TAX jited:1 46 44 43 PASS [ 1851.021767] test_bpf: #1 TXA jited:1 43 46 43 PASS [ 1851.024004] test_bpf: #2 ADD_SUB_MUL_K jited:1 45 PASS [ 1851.024886] test_bpf: #3 DIV_MOD_KX jited:1 70 PASS [ 1851.026103] test_bpf: #4 AND_OR_LSH_K jited:1 39 43 PASS [ 1851.027394] test_bpf: #5 LD_IMM_0 jited:1 42 PASS [ 1851.028027] test_bpf: #6 LD_IND jited:1 85 85 85 PASS [ 1851.030687] test_bpf: #7 LD_ABS jited:1 87 85 85 PASS [ 1851.033343] test_bpf: #8 LD_ABS_LL jited:1 90 70 PASS [ 1851.035030] test_bpf: #9 LD_IND_LL jited:1 61 58 58 PASS [ 1851.036890] test_bpf: #10 LD_ABS_NET jited:1 86 70 PASS [ 1851.038590] test_bpf: #11 LD_IND_NET jited:1 77 56 56 PASS [ 1851.040573] test_bpf: #12 LD_PKTTYPE jited:1 43 43 PASS [ 1851.041582] test_bpf: #13 LD_MARK jited:1 41 42 PASS [ 1851.042494] test_bpf: #14 LD_RXHASH jited:1 42 44 PASS [ 1851.043436] test_bpf: #15 LD_QUEUE jited:1 43 43 PASS [ 1851.044379] test_bpf: #16 LD_PROTOCOL jited:1 50 50 PASS [ 1851.045457] test_bpf: #17 LD_VLAN_TAG jited:1 41 41 PASS [ 1851.046363] test_bpf: #18 LD_VLAN_TAG_PRESENT jited:1 39 41 PASS [ 1851.047238] test_bpf: #19 LD_IFINDEX jited:1 44 44 PASS [ 1851.048199] test_bpf: #20 LD_HATYPE jited:1 44 44 PASS [ 1851.049157] test_bpf: #21 LD_CPU jited:1 51 50 PASS [ 1851.050250] test_bpf: #22 LD_NLATTR jited:1 43 68 PASS [ 1851.051465] test_bpf: #23 LD_NLATTR_NEST jited:1 85 233 PASS [ 1851.054890] test_bpf: #24 LD_PAYLOAD_OFF jited:1 527 745 PASS [ 1851.067698] test_bpf: #25 LD_ANC_XOR jited:1 42 42 PASS [ 1851.069510] test_bpf: #26 SPILL_FILL jited:1 45 45 48 PASS [ 1851.071372] test_bpf: #27 JEQ jited:1 85 46 47 PASS [ 1851.073284] test_bpf: #28 JGT jited:1 85 46 49 PASS [ 1851.075260] test_bpf: #29 JGE (jt 0), test 1 jited:1 86 47 47 PASS [ 1851.077151] test_bpf: #30 JGE (jt 0), test 2 jited:1 48 45 44 PASS [ 1851.078613] test_bpf: #31 JGE jited:1 48 46 47 PASS [ 1851.080128] test_bpf: #32 JSET jited:1 45 44 54 PASS [ 1851.081667] test_bpf: #33 tcpdump port 22 jited:1 83 106 72 PASS [ 1851.084383] test_bpf: #34 tcpdump complex jited:1 83 102 93 PASS [ 1851.087279] test_bpf: #35 RET_A jited:1 41 41 PASS [ 1851.088195] test_bpf: #36 INT: ADD trivial jited:1 43 PASS [ 1851.088700] test_bpf: #37 INT: MUL_X jited:1 41 PASS [ 1851.089186] test_bpf: #38 INT: MUL_X2 jited:1 40 PASS [ 1851.089665] test_bpf: #39 INT: MUL32_X jited:1 42 PASS [ 1851.090170] test_bpf: #40 INT: ADD 64-bit jited:1 90 PASS [ 1851.091228] test_bpf: #41 INT: ADD 32-bit jited:1 91 PASS [ 1851.092232] test_bpf: #42 INT: SUB jited:1 88 PASS [ 1851.093260] test_bpf: #43 INT: XOR jited:1 56 PASS [ 1851.093920] test_bpf: #44 INT: MUL jited:1 194 PASS [ 1851.095947] test_bpf: #45 MOV REG64 jited:1 43 PASS [ 1851.096513] test_bpf: #46 MOV REG32 jited:1 45 PASS [ 1851.097471] test_bpf: #47 LD IMM64 jited:1 44 PASS [ 1851.098000] test_bpf: #48 INT: ALU MIX jited:1 73 PASS [ 1851.098807] test_bpf: #49 INT: shifts by register jited:1 53 PASS [ 1851.099421] test_bpf: #50 INT: DIV + ABS jited:1 92 54 PASS [ 1851.100960] test_bpf: #51 INT: DIV by -1 jited:1 85 50 PASS [ 1851.102431] test_bpf: #52 check: missing ret PASS [ 1851.102650] test_bpf: #53 check: div_k_0 PASS [ 1851.102660] test_bpf: #54 check: unknown insn PASS [ 1851.102674] test_bpf: #55 check: out of range spill/fill PASS [ 1851.102685] test_bpf: #56 JUMPS + HOLES jited:1 55 PASS [ 1851.103399] test_bpf: #57 check: RET X PASS [ 1851.103453] test_bpf: #58 check: LDX + RET X PASS [ 1851.103464] test_bpf: #59 M[]: alt STX + LDX jited:1 105 PASS [ 1851.104598] test_bpf: #60 M[]: full STX + full LDX jited:1 68 PASS [ 1851.105426] test_bpf: #61 check: SKF_AD_MAX PASS [ 1851.105474] test_bpf: #62 LD [SKF_AD_OFF-1] jited:1 72 PASS [ 1851.106253] test_bpf: #63 load 64-bit immediate jited:1 42 PASS [ 1851.106748]
[Kernel-packages] [Bug 1918253] Re: WWAN I XMM 7360 LTE-Advanced (Cat 9) doesn't work [8086:7360]
** Tags added: originate-from-1952923 -- 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/1918253 Title: WWAN I XMM 7360 LTE-Advanced (Cat 9) doesn't work [8086:7360] Status in OEM Priority Project: New Status in linux package in Ubuntu: Confirmed Bug description: There is no driver for it [8086:7360] when using 5.10 kernel. $ lspci -nnv -s 55:00.0 55:00.0 Wireless controller [0d40]: Intel Corporation XMM7360 LTE Advanced Modem [8086:7360] (rev 01) Subsystem: Hewlett-Packard Company XMM7360 LTE Advanced Modem [103c:8337] Flags: fast devsel, IRQ 255 Memory at 6e40 (64-bit, non-prefetchable) [disabled] [size=4K] Memory at 6e401000 (64-bit, non-prefetchable) [disabled] [size=1K] Capabilities: To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1918253/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1952011] Re: [SRU] linux-firmware: add sof-firmware for adl platforms from sof-firmware-v1.9.2
** Tags added: verification-done-focal -- 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/1952011 Title: [SRU] linux-firmware: add sof-firmware for adl platforms from sof- firmware-v1.9.2 Status in HWE Next: New Status in linux-firmware package in Ubuntu: New Status in linux-firmware source package in Focal: Fix Committed Status in linux-firmware source package in Hirsute: In Progress Status in linux-firmware source package in Impish: In Progress Bug description: Because we plan to remove sof-firmware related files from linux-firmware of jammy and replace them with a debian package firmware-sof-signed, so this SRU is not applied to jammy. I will submit another SRU to firmware-sof-signed package later. [Impact] In the Dell oem project, we have many laptops which has sof dmic or sof soundwire audio design, they need to load firmware and topology files specific to ADL, otherwise the audio driver will fail to initialize and the whole audio can't work. [Fix] Integrate the firmware and topology files from sof-firmware-v1.9.2 [Test] Installed the patched linux-firmware and booting the patched kernel, the audio work well, all output and input devices work normally [Where problems could occur] This SRU introduces new firmware and topology files for adl, it has low possibility to introduce regression. If it could, it could possibilily affect the other machines which also need to load firmware and topology files, it could make the audio can't work on those machines, but this possibility is very low, we have tested the SRU on many laptops, no regression found. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1952011/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1953613] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1953613/+attachment/5546278/+files/acpidump.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Description changed: The current versions of gpiod, libgpiod-dev and libgpiod2 (1.6.2-1) use version 1 of the GPIO character device API. However, they cannot work because the interface is disabled in the default kernel (tested with 5.13.19). After rebuilding the kernel with the option CONFIG_GPIO_CDEV_V1=y, the gpiod tools work as expected. + Thanks to Marek Szuba, who reported the same bug for Gentoo + (https://bugs.gentoo.org/807334), pointing me in the right direction. What I expect to happen: - $ gpiodetect + $ gpiodetect gpiochip0 [0-003c] (8 lines) $ gpioinfo gpiochip0 - 8 lines: - line 0: unnamed unused output active-high - line 1: unnamed unused output active-high - line 2: unnamed unused output active-high - line 3: unnamed unused output active-high - line 4: unnamed unused output active-high - line 5: unnamed unused output active-high - line 6: unnamed unused input active-high - line 7: unnamed unused input active-high + line 0: unnamed unused output active-high + line 1: unnamed unused output active-high + line 2: unnamed unused output active-high + line 3: unnamed unused output active-high + line 4: unnamed unused output active-high + line 5: unnamed unused output active-high + line 6: unnamed unused input active-high + line 7: unnamed unused input active-high $ gpioget gpiochip0 0 1 What actually happens: $ gpiodetect gpiochip0 [0-003c] (8 lines) $ gpioinfo gpioinfo: error creating line iterator: Invalid argument $ gpioget gpiochip0 0 gpioget: error reading GPIO values: Invalid argument - - $ cat /proc/version_signature + $ cat /proc/version_signature Ubuntu 5.13.0-22.22-lowlatency 5.13.19 $ apt-cache policy libgpiod2 libgpiod2: - Installed: 1.6.2-1 - Candidate: 1.6.2-1 - Version table: - *** 1.6.2-1 500 - 500 http://de.archive.ubuntu.com/ubuntu impish/universe amd64 Packages - 100 /var/lib/dpkg/status + Installed: 1.6.2-1 + Candidate: 1.6.2-1 + Version table: + *** 1.6.2-1 500 + 500 http://de.archive.ubuntu.com/ubuntu impish/universe amd64 Packages + 100 /var/lib/dpkg/status I am testing with the onboard PCA9554A on a Fujitsu D3641-S motherboard. $ lspci | grep -i smb 00:1f.4 SMBus: Intel Corporation Cannon Lake PCH SMBus Controller (rev 10) $ lspci -s 1f.4 -vvv 00:1f.4 SMBus: Intel Corporation Cannon Lake PCH SMBus Controller (rev 10) - DeviceName: Onboard - Other - Subsystem: Fujitsu Technology Solutions Cannon Lake PCH SMBus Controller - Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- - Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- TAbort- SERR- https://bugs.launchpad.net/bugs/1953613 Title: GPIO character device API not enabled in kernel Status in linux package in Ubuntu: Confirmed Bug description: The current versions of gpiod, libgpiod-dev and libgpiod2 (1.6.2-1) use version 1 of the GPIO character device API. However, they cannot work because the interface is disabled in the default kernel (tested with 5.13.19). After rebuilding the kernel with the option CONFIG_GPIO_CDEV_V1=y, the gpiod tools work as expected. Thanks to Marek Szuba, who reported the same bug for Gentoo (https://bugs.gentoo.org/807334), pointing me in the right direction. What I expect to happen: $ gpiodetect gpiochip0 [0-003c] (8 lines) $ gpioinfo gpiochip0 - 8 lines: line 0: unnamed unused output active-high line 1: unnamed unused output active-high line 2: unnamed unused output active-high line 3: unnamed unused output active-high line 4: unnamed unused output active-high line 5: unnamed unused output active-high line 6: unnamed unused input active-high line 7: unnamed unused input active-high $ gpioget gpiochip0 0 1 What actually happens: $ gpiodetect gpiochip0 [0-003c] (8 lines) $ gpioinfo gpioinfo: error creating line iterator: Invalid argument $ gpioget gpiochip0 0 gpioget: error reading GPIO values: Invalid argument $ cat /proc/version_signature Ubuntu 5.13.0-22.22-lowlatency 5.13.19 $ apt-cache policy libgpiod2 libgpiod2: Installed: 1.6.2-1 Candidate: 1.6.2-1 Version table: *** 1.6.2-1 500 500 http://de.archive.ubuntu.com/ubuntu
[Kernel-packages] [Bug 1953613] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1953613/+attachment/5546276/+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/1953613 Title: GPIO character device API not enabled in kernel Status in linux package in Ubuntu: Confirmed Bug description: The current versions of gpiod, libgpiod-dev and libgpiod2 (1.6.2-1) use version 1 of the GPIO character device API. However, they cannot work because the interface is disabled in the default kernel (tested with 5.13.19). After rebuilding the kernel with the option CONFIG_GPIO_CDEV_V1=y, the gpiod tools work as expected. Thanks to Marek Szuba, who reported the same bug for Gentoo (https://bugs.gentoo.org/807334), pointing me in the right direction. What I expect to happen: $ gpiodetect gpiochip0 [0-003c] (8 lines) $ gpioinfo gpiochip0 - 8 lines: line 0: unnamed unused output active-high line 1: unnamed unused output active-high line 2: unnamed unused output active-high line 3: unnamed unused output active-high line 4: unnamed unused output active-high line 5: unnamed unused output active-high line 6: unnamed unused input active-high line 7: unnamed unused input active-high $ gpioget gpiochip0 0 1 What actually happens: $ gpiodetect gpiochip0 [0-003c] (8 lines) $ gpioinfo gpioinfo: error creating line iterator: Invalid argument $ gpioget gpiochip0 0 gpioget: error reading GPIO values: Invalid argument $ cat /proc/version_signature Ubuntu 5.13.0-22.22-lowlatency 5.13.19 $ apt-cache policy libgpiod2 libgpiod2: Installed: 1.6.2-1 Candidate: 1.6.2-1 Version table: *** 1.6.2-1 500 500 http://de.archive.ubuntu.com/ubuntu impish/universe amd64 Packages 100 /var/lib/dpkg/status I am testing with the onboard PCA9554A on a Fujitsu D3641-S motherboard. $ lspci | grep -i smb 00:1f.4 SMBus: Intel Corporation Cannon Lake PCH SMBus Controller (rev 10) $ lspci -s 1f.4 -vvv 00:1f.4 SMBus: Intel Corporation Cannon Lake PCH SMBus Controller (rev 10) DeviceName: Onboard - Other Subsystem: Fujitsu Technology Solutions Cannon Lake PCH SMBus Controller Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953613/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1953613] Re: GPIO character device API not enabled in kernel
apport information ** Tags added: apport-collected impish ** Description changed: The current versions of gpiod, libgpiod-dev and libgpiod2 (1.6.2-1) use version 1 of the GPIO character device API. However, they cannot work because the interface is disabled in the default kernel (tested with 5.13.19). After rebuilding the kernel with the option CONFIG_GPIO_CDEV_V1=y, the gpiod tools work as expected. What I expect to happen: $ gpiodetect gpiochip0 [0-003c] (8 lines) $ gpioinfo gpiochip0 - 8 lines: line 0: unnamed unused output active-high line 1: unnamed unused output active-high line 2: unnamed unused output active-high line 3: unnamed unused output active-high line 4: unnamed unused output active-high line 5: unnamed unused output active-high line 6: unnamed unused input active-high line 7: unnamed unused input active-high $ gpioget gpiochip0 0 1 What actually happens: $ gpiodetect gpiochip0 [0-003c] (8 lines) $ gpioinfo gpioinfo: error creating line iterator: Invalid argument $ gpioget gpiochip0 0 gpioget: error reading GPIO values: Invalid argument $ cat /proc/version_signature Ubuntu 5.13.0-22.22-lowlatency 5.13.19 $ apt-cache policy libgpiod2 libgpiod2: Installed: 1.6.2-1 Candidate: 1.6.2-1 Version table: *** 1.6.2-1 500 500 http://de.archive.ubuntu.com/ubuntu impish/universe amd64 Packages 100 /var/lib/dpkg/status I am testing with the onboard PCA9554A on a Fujitsu D3641-S motherboard. $ lspci | grep -i smb 00:1f.4 SMBus: Intel Corporation Cannon Lake PCH SMBus Controller (rev 10) $ lspci -s 1f.4 -vvv 00:1f.4 SMBus: Intel Corporation Cannon Lake PCH SMBus Controller (rev 10) DeviceName: Onboard - Other Subsystem: Fujitsu Technology Solutions Cannon Lake PCH SMBus Controller Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- https://bugs.launchpad.net/bugs/1953613/+attachment/5546262/+files/AlsaInfo.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/1953613 Title: GPIO character device API not enabled in kernel Status in linux package in Ubuntu: Confirmed Bug description: The current versions of gpiod, libgpiod-dev and libgpiod2 (1.6.2-1) use version 1 of the GPIO character device API. However, they cannot work because the interface is disabled in the default kernel (tested with 5.13.19). After rebuilding the kernel with the option CONFIG_GPIO_CDEV_V1=y, the gpiod tools work as expected. Thanks to Marek Szuba, who reported the same bug for Gentoo (https://bugs.gentoo.org/807334), pointing me in the right direction. What I expect to happen: $ gpiodetect gpiochip0 [0-003c] (8 lines) $ gpioinfo gpiochip0 - 8 lines: line 0: unnamed unused output active-high line 1: unnamed unused output active-high line 2: unnamed unused output active-high line 3: unnamed unused output active-high line 4: unnamed unused output active-high line 5: unnamed unused output active-high line 6: unnamed unused input active-high line 7: unnamed unused input active-high $ gpioget gpiochip0 0 1 What actually happens: $ gpiodetect gpiochip0 [0-003c] (8 lines) $ gpioinfo gpioinfo: error creating line iterator: Invalid argument $ gpioget gpiochip0 0 gpioget: error reading GPIO values: Invalid argument $ cat /proc/version_signature Ubuntu 5.13.0-22.22-lowlatency 5.13.19 $ apt-cache policy libgpiod2 libgpiod2: Installed: 1.6.2-1 Candidate: 1.6.2-1 Version table: *** 1.6.2-1 500 500 http://de.archive.ubuntu.com/ubuntu impish/universe amd64 Packages 100 /var/lib/dpkg/status I am testing with the onboard PCA9554A on a Fujitsu D3641-S motherboard. $ lspci | grep -i smb 00:1f.4 SMBus: Intel Corporation Cannon Lake PCH SMBus Controller (rev 10) $ lspci -s 1f.4 -vvv 00:1f.4 SMBus: Intel Corporation Cannon Lake PCH SMBus Controller (rev 10) DeviceName: Onboard - Other Subsystem: Fujitsu Technology Solutions Cannon Lake PCH SMBus Controller Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953613/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe
[Kernel-packages] [Bug 1953613] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1953613/+attachment/5546268/+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/1953613 Title: GPIO character device API not enabled in kernel Status in linux package in Ubuntu: Confirmed Bug description: The current versions of gpiod, libgpiod-dev and libgpiod2 (1.6.2-1) use version 1 of the GPIO character device API. However, they cannot work because the interface is disabled in the default kernel (tested with 5.13.19). After rebuilding the kernel with the option CONFIG_GPIO_CDEV_V1=y, the gpiod tools work as expected. Thanks to Marek Szuba, who reported the same bug for Gentoo (https://bugs.gentoo.org/807334), pointing me in the right direction. What I expect to happen: $ gpiodetect gpiochip0 [0-003c] (8 lines) $ gpioinfo gpiochip0 - 8 lines: line 0: unnamed unused output active-high line 1: unnamed unused output active-high line 2: unnamed unused output active-high line 3: unnamed unused output active-high line 4: unnamed unused output active-high line 5: unnamed unused output active-high line 6: unnamed unused input active-high line 7: unnamed unused input active-high $ gpioget gpiochip0 0 1 What actually happens: $ gpiodetect gpiochip0 [0-003c] (8 lines) $ gpioinfo gpioinfo: error creating line iterator: Invalid argument $ gpioget gpiochip0 0 gpioget: error reading GPIO values: Invalid argument $ cat /proc/version_signature Ubuntu 5.13.0-22.22-lowlatency 5.13.19 $ apt-cache policy libgpiod2 libgpiod2: Installed: 1.6.2-1 Candidate: 1.6.2-1 Version table: *** 1.6.2-1 500 500 http://de.archive.ubuntu.com/ubuntu impish/universe amd64 Packages 100 /var/lib/dpkg/status I am testing with the onboard PCA9554A on a Fujitsu D3641-S motherboard. $ lspci | grep -i smb 00:1f.4 SMBus: Intel Corporation Cannon Lake PCH SMBus Controller (rev 10) $ lspci -s 1f.4 -vvv 00:1f.4 SMBus: Intel Corporation Cannon Lake PCH SMBus Controller (rev 10) DeviceName: Onboard - Other Subsystem: Fujitsu Technology Solutions Cannon Lake PCH SMBus Controller Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953613/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1953613] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1953613/+attachment/5546273/+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/1953613 Title: GPIO character device API not enabled in kernel Status in linux package in Ubuntu: Confirmed Bug description: The current versions of gpiod, libgpiod-dev and libgpiod2 (1.6.2-1) use version 1 of the GPIO character device API. However, they cannot work because the interface is disabled in the default kernel (tested with 5.13.19). After rebuilding the kernel with the option CONFIG_GPIO_CDEV_V1=y, the gpiod tools work as expected. Thanks to Marek Szuba, who reported the same bug for Gentoo (https://bugs.gentoo.org/807334), pointing me in the right direction. What I expect to happen: $ gpiodetect gpiochip0 [0-003c] (8 lines) $ gpioinfo gpiochip0 - 8 lines: line 0: unnamed unused output active-high line 1: unnamed unused output active-high line 2: unnamed unused output active-high line 3: unnamed unused output active-high line 4: unnamed unused output active-high line 5: unnamed unused output active-high line 6: unnamed unused input active-high line 7: unnamed unused input active-high $ gpioget gpiochip0 0 1 What actually happens: $ gpiodetect gpiochip0 [0-003c] (8 lines) $ gpioinfo gpioinfo: error creating line iterator: Invalid argument $ gpioget gpiochip0 0 gpioget: error reading GPIO values: Invalid argument $ cat /proc/version_signature Ubuntu 5.13.0-22.22-lowlatency 5.13.19 $ apt-cache policy libgpiod2 libgpiod2: Installed: 1.6.2-1 Candidate: 1.6.2-1 Version table: *** 1.6.2-1 500 500 http://de.archive.ubuntu.com/ubuntu impish/universe amd64 Packages 100 /var/lib/dpkg/status I am testing with the onboard PCA9554A on a Fujitsu D3641-S motherboard. $ lspci | grep -i smb 00:1f.4 SMBus: Intel Corporation Cannon Lake PCH SMBus Controller (rev 10) $ lspci -s 1f.4 -vvv 00:1f.4 SMBus: Intel Corporation Cannon Lake PCH SMBus Controller (rev 10) DeviceName: Onboard - Other Subsystem: Fujitsu Technology Solutions Cannon Lake PCH SMBus Controller Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953613/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1953613] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1953613/+attachment/5546269/+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/1953613 Title: GPIO character device API not enabled in kernel Status in linux package in Ubuntu: Confirmed Bug description: The current versions of gpiod, libgpiod-dev and libgpiod2 (1.6.2-1) use version 1 of the GPIO character device API. However, they cannot work because the interface is disabled in the default kernel (tested with 5.13.19). After rebuilding the kernel with the option CONFIG_GPIO_CDEV_V1=y, the gpiod tools work as expected. Thanks to Marek Szuba, who reported the same bug for Gentoo (https://bugs.gentoo.org/807334), pointing me in the right direction. What I expect to happen: $ gpiodetect gpiochip0 [0-003c] (8 lines) $ gpioinfo gpiochip0 - 8 lines: line 0: unnamed unused output active-high line 1: unnamed unused output active-high line 2: unnamed unused output active-high line 3: unnamed unused output active-high line 4: unnamed unused output active-high line 5: unnamed unused output active-high line 6: unnamed unused input active-high line 7: unnamed unused input active-high $ gpioget gpiochip0 0 1 What actually happens: $ gpiodetect gpiochip0 [0-003c] (8 lines) $ gpioinfo gpioinfo: error creating line iterator: Invalid argument $ gpioget gpiochip0 0 gpioget: error reading GPIO values: Invalid argument $ cat /proc/version_signature Ubuntu 5.13.0-22.22-lowlatency 5.13.19 $ apt-cache policy libgpiod2 libgpiod2: Installed: 1.6.2-1 Candidate: 1.6.2-1 Version table: *** 1.6.2-1 500 500 http://de.archive.ubuntu.com/ubuntu impish/universe amd64 Packages 100 /var/lib/dpkg/status I am testing with the onboard PCA9554A on a Fujitsu D3641-S motherboard. $ lspci | grep -i smb 00:1f.4 SMBus: Intel Corporation Cannon Lake PCH SMBus Controller (rev 10) $ lspci -s 1f.4 -vvv 00:1f.4 SMBus: Intel Corporation Cannon Lake PCH SMBus Controller (rev 10) DeviceName: Onboard - Other Subsystem: Fujitsu Technology Solutions Cannon Lake PCH SMBus Controller Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953613/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1953613] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1953613/+attachment/5546264/+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/1953613 Title: GPIO character device API not enabled in kernel Status in linux package in Ubuntu: Confirmed Bug description: The current versions of gpiod, libgpiod-dev and libgpiod2 (1.6.2-1) use version 1 of the GPIO character device API. However, they cannot work because the interface is disabled in the default kernel (tested with 5.13.19). After rebuilding the kernel with the option CONFIG_GPIO_CDEV_V1=y, the gpiod tools work as expected. Thanks to Marek Szuba, who reported the same bug for Gentoo (https://bugs.gentoo.org/807334), pointing me in the right direction. What I expect to happen: $ gpiodetect gpiochip0 [0-003c] (8 lines) $ gpioinfo gpiochip0 - 8 lines: line 0: unnamed unused output active-high line 1: unnamed unused output active-high line 2: unnamed unused output active-high line 3: unnamed unused output active-high line 4: unnamed unused output active-high line 5: unnamed unused output active-high line 6: unnamed unused input active-high line 7: unnamed unused input active-high $ gpioget gpiochip0 0 1 What actually happens: $ gpiodetect gpiochip0 [0-003c] (8 lines) $ gpioinfo gpioinfo: error creating line iterator: Invalid argument $ gpioget gpiochip0 0 gpioget: error reading GPIO values: Invalid argument $ cat /proc/version_signature Ubuntu 5.13.0-22.22-lowlatency 5.13.19 $ apt-cache policy libgpiod2 libgpiod2: Installed: 1.6.2-1 Candidate: 1.6.2-1 Version table: *** 1.6.2-1 500 500 http://de.archive.ubuntu.com/ubuntu impish/universe amd64 Packages 100 /var/lib/dpkg/status I am testing with the onboard PCA9554A on a Fujitsu D3641-S motherboard. $ lspci | grep -i smb 00:1f.4 SMBus: Intel Corporation Cannon Lake PCH SMBus Controller (rev 10) $ lspci -s 1f.4 -vvv 00:1f.4 SMBus: Intel Corporation Cannon Lake PCH SMBus Controller (rev 10) DeviceName: Onboard - Other Subsystem: Fujitsu Technology Solutions Cannon Lake PCH SMBus Controller Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953613/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1953613] PaInfo.txt
apport information ** Attachment added: "PaInfo.txt" https://bugs.launchpad.net/bugs/1953613/+attachment/5546270/+files/PaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1953613 Title: GPIO character device API not enabled in kernel Status in linux package in Ubuntu: Confirmed Bug description: The current versions of gpiod, libgpiod-dev and libgpiod2 (1.6.2-1) use version 1 of the GPIO character device API. However, they cannot work because the interface is disabled in the default kernel (tested with 5.13.19). After rebuilding the kernel with the option CONFIG_GPIO_CDEV_V1=y, the gpiod tools work as expected. Thanks to Marek Szuba, who reported the same bug for Gentoo (https://bugs.gentoo.org/807334), pointing me in the right direction. What I expect to happen: $ gpiodetect gpiochip0 [0-003c] (8 lines) $ gpioinfo gpiochip0 - 8 lines: line 0: unnamed unused output active-high line 1: unnamed unused output active-high line 2: unnamed unused output active-high line 3: unnamed unused output active-high line 4: unnamed unused output active-high line 5: unnamed unused output active-high line 6: unnamed unused input active-high line 7: unnamed unused input active-high $ gpioget gpiochip0 0 1 What actually happens: $ gpiodetect gpiochip0 [0-003c] (8 lines) $ gpioinfo gpioinfo: error creating line iterator: Invalid argument $ gpioget gpiochip0 0 gpioget: error reading GPIO values: Invalid argument $ cat /proc/version_signature Ubuntu 5.13.0-22.22-lowlatency 5.13.19 $ apt-cache policy libgpiod2 libgpiod2: Installed: 1.6.2-1 Candidate: 1.6.2-1 Version table: *** 1.6.2-1 500 500 http://de.archive.ubuntu.com/ubuntu impish/universe amd64 Packages 100 /var/lib/dpkg/status I am testing with the onboard PCA9554A on a Fujitsu D3641-S motherboard. $ lspci | grep -i smb 00:1f.4 SMBus: Intel Corporation Cannon Lake PCH SMBus Controller (rev 10) $ lspci -s 1f.4 -vvv 00:1f.4 SMBus: Intel Corporation Cannon Lake PCH SMBus Controller (rev 10) DeviceName: Onboard - Other Subsystem: Fujitsu Technology Solutions Cannon Lake PCH SMBus Controller Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953613/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1953613] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1953613/+attachment/5546272/+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/1953613 Title: GPIO character device API not enabled in kernel Status in linux package in Ubuntu: Confirmed Bug description: The current versions of gpiod, libgpiod-dev and libgpiod2 (1.6.2-1) use version 1 of the GPIO character device API. However, they cannot work because the interface is disabled in the default kernel (tested with 5.13.19). After rebuilding the kernel with the option CONFIG_GPIO_CDEV_V1=y, the gpiod tools work as expected. Thanks to Marek Szuba, who reported the same bug for Gentoo (https://bugs.gentoo.org/807334), pointing me in the right direction. What I expect to happen: $ gpiodetect gpiochip0 [0-003c] (8 lines) $ gpioinfo gpiochip0 - 8 lines: line 0: unnamed unused output active-high line 1: unnamed unused output active-high line 2: unnamed unused output active-high line 3: unnamed unused output active-high line 4: unnamed unused output active-high line 5: unnamed unused output active-high line 6: unnamed unused input active-high line 7: unnamed unused input active-high $ gpioget gpiochip0 0 1 What actually happens: $ gpiodetect gpiochip0 [0-003c] (8 lines) $ gpioinfo gpioinfo: error creating line iterator: Invalid argument $ gpioget gpiochip0 0 gpioget: error reading GPIO values: Invalid argument $ cat /proc/version_signature Ubuntu 5.13.0-22.22-lowlatency 5.13.19 $ apt-cache policy libgpiod2 libgpiod2: Installed: 1.6.2-1 Candidate: 1.6.2-1 Version table: *** 1.6.2-1 500 500 http://de.archive.ubuntu.com/ubuntu impish/universe amd64 Packages 100 /var/lib/dpkg/status I am testing with the onboard PCA9554A on a Fujitsu D3641-S motherboard. $ lspci | grep -i smb 00:1f.4 SMBus: Intel Corporation Cannon Lake PCH SMBus Controller (rev 10) $ lspci -s 1f.4 -vvv 00:1f.4 SMBus: Intel Corporation Cannon Lake PCH SMBus Controller (rev 10) DeviceName: Onboard - Other Subsystem: Fujitsu Technology Solutions Cannon Lake PCH SMBus Controller Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953613/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1953613] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1953613/+attachment/5546275/+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/1953613 Title: GPIO character device API not enabled in kernel Status in linux package in Ubuntu: Confirmed Bug description: The current versions of gpiod, libgpiod-dev and libgpiod2 (1.6.2-1) use version 1 of the GPIO character device API. However, they cannot work because the interface is disabled in the default kernel (tested with 5.13.19). After rebuilding the kernel with the option CONFIG_GPIO_CDEV_V1=y, the gpiod tools work as expected. Thanks to Marek Szuba, who reported the same bug for Gentoo (https://bugs.gentoo.org/807334), pointing me in the right direction. What I expect to happen: $ gpiodetect gpiochip0 [0-003c] (8 lines) $ gpioinfo gpiochip0 - 8 lines: line 0: unnamed unused output active-high line 1: unnamed unused output active-high line 2: unnamed unused output active-high line 3: unnamed unused output active-high line 4: unnamed unused output active-high line 5: unnamed unused output active-high line 6: unnamed unused input active-high line 7: unnamed unused input active-high $ gpioget gpiochip0 0 1 What actually happens: $ gpiodetect gpiochip0 [0-003c] (8 lines) $ gpioinfo gpioinfo: error creating line iterator: Invalid argument $ gpioget gpiochip0 0 gpioget: error reading GPIO values: Invalid argument $ cat /proc/version_signature Ubuntu 5.13.0-22.22-lowlatency 5.13.19 $ apt-cache policy libgpiod2 libgpiod2: Installed: 1.6.2-1 Candidate: 1.6.2-1 Version table: *** 1.6.2-1 500 500 http://de.archive.ubuntu.com/ubuntu impish/universe amd64 Packages 100 /var/lib/dpkg/status I am testing with the onboard PCA9554A on a Fujitsu D3641-S motherboard. $ lspci | grep -i smb 00:1f.4 SMBus: Intel Corporation Cannon Lake PCH SMBus Controller (rev 10) $ lspci -s 1f.4 -vvv 00:1f.4 SMBus: Intel Corporation Cannon Lake PCH SMBus Controller (rev 10) DeviceName: Onboard - Other Subsystem: Fujitsu Technology Solutions Cannon Lake PCH SMBus Controller Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953613/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1953613] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1953613/+attachment/5546277/+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/1953613 Title: GPIO character device API not enabled in kernel Status in linux package in Ubuntu: Confirmed Bug description: The current versions of gpiod, libgpiod-dev and libgpiod2 (1.6.2-1) use version 1 of the GPIO character device API. However, they cannot work because the interface is disabled in the default kernel (tested with 5.13.19). After rebuilding the kernel with the option CONFIG_GPIO_CDEV_V1=y, the gpiod tools work as expected. Thanks to Marek Szuba, who reported the same bug for Gentoo (https://bugs.gentoo.org/807334), pointing me in the right direction. What I expect to happen: $ gpiodetect gpiochip0 [0-003c] (8 lines) $ gpioinfo gpiochip0 - 8 lines: line 0: unnamed unused output active-high line 1: unnamed unused output active-high line 2: unnamed unused output active-high line 3: unnamed unused output active-high line 4: unnamed unused output active-high line 5: unnamed unused output active-high line 6: unnamed unused input active-high line 7: unnamed unused input active-high $ gpioget gpiochip0 0 1 What actually happens: $ gpiodetect gpiochip0 [0-003c] (8 lines) $ gpioinfo gpioinfo: error creating line iterator: Invalid argument $ gpioget gpiochip0 0 gpioget: error reading GPIO values: Invalid argument $ cat /proc/version_signature Ubuntu 5.13.0-22.22-lowlatency 5.13.19 $ apt-cache policy libgpiod2 libgpiod2: Installed: 1.6.2-1 Candidate: 1.6.2-1 Version table: *** 1.6.2-1 500 500 http://de.archive.ubuntu.com/ubuntu impish/universe amd64 Packages 100 /var/lib/dpkg/status I am testing with the onboard PCA9554A on a Fujitsu D3641-S motherboard. $ lspci | grep -i smb 00:1f.4 SMBus: Intel Corporation Cannon Lake PCH SMBus Controller (rev 10) $ lspci -s 1f.4 -vvv 00:1f.4 SMBus: Intel Corporation Cannon Lake PCH SMBus Controller (rev 10) DeviceName: Onboard - Other Subsystem: Fujitsu Technology Solutions Cannon Lake PCH SMBus Controller Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953613/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1953613] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1953613/+attachment/5546266/+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/1953613 Title: GPIO character device API not enabled in kernel Status in linux package in Ubuntu: Confirmed Bug description: The current versions of gpiod, libgpiod-dev and libgpiod2 (1.6.2-1) use version 1 of the GPIO character device API. However, they cannot work because the interface is disabled in the default kernel (tested with 5.13.19). After rebuilding the kernel with the option CONFIG_GPIO_CDEV_V1=y, the gpiod tools work as expected. Thanks to Marek Szuba, who reported the same bug for Gentoo (https://bugs.gentoo.org/807334), pointing me in the right direction. What I expect to happen: $ gpiodetect gpiochip0 [0-003c] (8 lines) $ gpioinfo gpiochip0 - 8 lines: line 0: unnamed unused output active-high line 1: unnamed unused output active-high line 2: unnamed unused output active-high line 3: unnamed unused output active-high line 4: unnamed unused output active-high line 5: unnamed unused output active-high line 6: unnamed unused input active-high line 7: unnamed unused input active-high $ gpioget gpiochip0 0 1 What actually happens: $ gpiodetect gpiochip0 [0-003c] (8 lines) $ gpioinfo gpioinfo: error creating line iterator: Invalid argument $ gpioget gpiochip0 0 gpioget: error reading GPIO values: Invalid argument $ cat /proc/version_signature Ubuntu 5.13.0-22.22-lowlatency 5.13.19 $ apt-cache policy libgpiod2 libgpiod2: Installed: 1.6.2-1 Candidate: 1.6.2-1 Version table: *** 1.6.2-1 500 500 http://de.archive.ubuntu.com/ubuntu impish/universe amd64 Packages 100 /var/lib/dpkg/status I am testing with the onboard PCA9554A on a Fujitsu D3641-S motherboard. $ lspci | grep -i smb 00:1f.4 SMBus: Intel Corporation Cannon Lake PCH SMBus Controller (rev 10) $ lspci -s 1f.4 -vvv 00:1f.4 SMBus: Intel Corporation Cannon Lake PCH SMBus Controller (rev 10) DeviceName: Onboard - Other Subsystem: Fujitsu Technology Solutions Cannon Lake PCH SMBus Controller Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953613/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1953613] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1953613/+attachment/5546267/+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/1953613 Title: GPIO character device API not enabled in kernel Status in linux package in Ubuntu: Confirmed Bug description: The current versions of gpiod, libgpiod-dev and libgpiod2 (1.6.2-1) use version 1 of the GPIO character device API. However, they cannot work because the interface is disabled in the default kernel (tested with 5.13.19). After rebuilding the kernel with the option CONFIG_GPIO_CDEV_V1=y, the gpiod tools work as expected. Thanks to Marek Szuba, who reported the same bug for Gentoo (https://bugs.gentoo.org/807334), pointing me in the right direction. What I expect to happen: $ gpiodetect gpiochip0 [0-003c] (8 lines) $ gpioinfo gpiochip0 - 8 lines: line 0: unnamed unused output active-high line 1: unnamed unused output active-high line 2: unnamed unused output active-high line 3: unnamed unused output active-high line 4: unnamed unused output active-high line 5: unnamed unused output active-high line 6: unnamed unused input active-high line 7: unnamed unused input active-high $ gpioget gpiochip0 0 1 What actually happens: $ gpiodetect gpiochip0 [0-003c] (8 lines) $ gpioinfo gpioinfo: error creating line iterator: Invalid argument $ gpioget gpiochip0 0 gpioget: error reading GPIO values: Invalid argument $ cat /proc/version_signature Ubuntu 5.13.0-22.22-lowlatency 5.13.19 $ apt-cache policy libgpiod2 libgpiod2: Installed: 1.6.2-1 Candidate: 1.6.2-1 Version table: *** 1.6.2-1 500 500 http://de.archive.ubuntu.com/ubuntu impish/universe amd64 Packages 100 /var/lib/dpkg/status I am testing with the onboard PCA9554A on a Fujitsu D3641-S motherboard. $ lspci | grep -i smb 00:1f.4 SMBus: Intel Corporation Cannon Lake PCH SMBus Controller (rev 10) $ lspci -s 1f.4 -vvv 00:1f.4 SMBus: Intel Corporation Cannon Lake PCH SMBus Controller (rev 10) DeviceName: Onboard - Other Subsystem: Fujitsu Technology Solutions Cannon Lake PCH SMBus Controller Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953613/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1953613] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1953613/+attachment/5546274/+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/1953613 Title: GPIO character device API not enabled in kernel Status in linux package in Ubuntu: Confirmed Bug description: The current versions of gpiod, libgpiod-dev and libgpiod2 (1.6.2-1) use version 1 of the GPIO character device API. However, they cannot work because the interface is disabled in the default kernel (tested with 5.13.19). After rebuilding the kernel with the option CONFIG_GPIO_CDEV_V1=y, the gpiod tools work as expected. Thanks to Marek Szuba, who reported the same bug for Gentoo (https://bugs.gentoo.org/807334), pointing me in the right direction. What I expect to happen: $ gpiodetect gpiochip0 [0-003c] (8 lines) $ gpioinfo gpiochip0 - 8 lines: line 0: unnamed unused output active-high line 1: unnamed unused output active-high line 2: unnamed unused output active-high line 3: unnamed unused output active-high line 4: unnamed unused output active-high line 5: unnamed unused output active-high line 6: unnamed unused input active-high line 7: unnamed unused input active-high $ gpioget gpiochip0 0 1 What actually happens: $ gpiodetect gpiochip0 [0-003c] (8 lines) $ gpioinfo gpioinfo: error creating line iterator: Invalid argument $ gpioget gpiochip0 0 gpioget: error reading GPIO values: Invalid argument $ cat /proc/version_signature Ubuntu 5.13.0-22.22-lowlatency 5.13.19 $ apt-cache policy libgpiod2 libgpiod2: Installed: 1.6.2-1 Candidate: 1.6.2-1 Version table: *** 1.6.2-1 500 500 http://de.archive.ubuntu.com/ubuntu impish/universe amd64 Packages 100 /var/lib/dpkg/status I am testing with the onboard PCA9554A on a Fujitsu D3641-S motherboard. $ lspci | grep -i smb 00:1f.4 SMBus: Intel Corporation Cannon Lake PCH SMBus Controller (rev 10) $ lspci -s 1f.4 -vvv 00:1f.4 SMBus: Intel Corporation Cannon Lake PCH SMBus Controller (rev 10) DeviceName: Onboard - Other Subsystem: Fujitsu Technology Solutions Cannon Lake PCH SMBus Controller Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953613/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1953613] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1953613/+attachment/5546265/+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/1953613 Title: GPIO character device API not enabled in kernel Status in linux package in Ubuntu: Confirmed Bug description: The current versions of gpiod, libgpiod-dev and libgpiod2 (1.6.2-1) use version 1 of the GPIO character device API. However, they cannot work because the interface is disabled in the default kernel (tested with 5.13.19). After rebuilding the kernel with the option CONFIG_GPIO_CDEV_V1=y, the gpiod tools work as expected. Thanks to Marek Szuba, who reported the same bug for Gentoo (https://bugs.gentoo.org/807334), pointing me in the right direction. What I expect to happen: $ gpiodetect gpiochip0 [0-003c] (8 lines) $ gpioinfo gpiochip0 - 8 lines: line 0: unnamed unused output active-high line 1: unnamed unused output active-high line 2: unnamed unused output active-high line 3: unnamed unused output active-high line 4: unnamed unused output active-high line 5: unnamed unused output active-high line 6: unnamed unused input active-high line 7: unnamed unused input active-high $ gpioget gpiochip0 0 1 What actually happens: $ gpiodetect gpiochip0 [0-003c] (8 lines) $ gpioinfo gpioinfo: error creating line iterator: Invalid argument $ gpioget gpiochip0 0 gpioget: error reading GPIO values: Invalid argument $ cat /proc/version_signature Ubuntu 5.13.0-22.22-lowlatency 5.13.19 $ apt-cache policy libgpiod2 libgpiod2: Installed: 1.6.2-1 Candidate: 1.6.2-1 Version table: *** 1.6.2-1 500 500 http://de.archive.ubuntu.com/ubuntu impish/universe amd64 Packages 100 /var/lib/dpkg/status I am testing with the onboard PCA9554A on a Fujitsu D3641-S motherboard. $ lspci | grep -i smb 00:1f.4 SMBus: Intel Corporation Cannon Lake PCH SMBus Controller (rev 10) $ lspci -s 1f.4 -vvv 00:1f.4 SMBus: Intel Corporation Cannon Lake PCH SMBus Controller (rev 10) DeviceName: Onboard - Other Subsystem: Fujitsu Technology Solutions Cannon Lake PCH SMBus Controller Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953613/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1953613] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1953613/+attachment/5546271/+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/1953613 Title: GPIO character device API not enabled in kernel Status in linux package in Ubuntu: Confirmed Bug description: The current versions of gpiod, libgpiod-dev and libgpiod2 (1.6.2-1) use version 1 of the GPIO character device API. However, they cannot work because the interface is disabled in the default kernel (tested with 5.13.19). After rebuilding the kernel with the option CONFIG_GPIO_CDEV_V1=y, the gpiod tools work as expected. Thanks to Marek Szuba, who reported the same bug for Gentoo (https://bugs.gentoo.org/807334), pointing me in the right direction. What I expect to happen: $ gpiodetect gpiochip0 [0-003c] (8 lines) $ gpioinfo gpiochip0 - 8 lines: line 0: unnamed unused output active-high line 1: unnamed unused output active-high line 2: unnamed unused output active-high line 3: unnamed unused output active-high line 4: unnamed unused output active-high line 5: unnamed unused output active-high line 6: unnamed unused input active-high line 7: unnamed unused input active-high $ gpioget gpiochip0 0 1 What actually happens: $ gpiodetect gpiochip0 [0-003c] (8 lines) $ gpioinfo gpioinfo: error creating line iterator: Invalid argument $ gpioget gpiochip0 0 gpioget: error reading GPIO values: Invalid argument $ cat /proc/version_signature Ubuntu 5.13.0-22.22-lowlatency 5.13.19 $ apt-cache policy libgpiod2 libgpiod2: Installed: 1.6.2-1 Candidate: 1.6.2-1 Version table: *** 1.6.2-1 500 500 http://de.archive.ubuntu.com/ubuntu impish/universe amd64 Packages 100 /var/lib/dpkg/status I am testing with the onboard PCA9554A on a Fujitsu D3641-S motherboard. $ lspci | grep -i smb 00:1f.4 SMBus: Intel Corporation Cannon Lake PCH SMBus Controller (rev 10) $ lspci -s 1f.4 -vvv 00:1f.4 SMBus: Intel Corporation Cannon Lake PCH SMBus Controller (rev 10) DeviceName: Onboard - Other Subsystem: Fujitsu Technology Solutions Cannon Lake PCH SMBus Controller Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953613/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1953613] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1953613/+attachment/5546263/+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/1953613 Title: GPIO character device API not enabled in kernel Status in linux package in Ubuntu: Confirmed Bug description: The current versions of gpiod, libgpiod-dev and libgpiod2 (1.6.2-1) use version 1 of the GPIO character device API. However, they cannot work because the interface is disabled in the default kernel (tested with 5.13.19). After rebuilding the kernel with the option CONFIG_GPIO_CDEV_V1=y, the gpiod tools work as expected. Thanks to Marek Szuba, who reported the same bug for Gentoo (https://bugs.gentoo.org/807334), pointing me in the right direction. What I expect to happen: $ gpiodetect gpiochip0 [0-003c] (8 lines) $ gpioinfo gpiochip0 - 8 lines: line 0: unnamed unused output active-high line 1: unnamed unused output active-high line 2: unnamed unused output active-high line 3: unnamed unused output active-high line 4: unnamed unused output active-high line 5: unnamed unused output active-high line 6: unnamed unused input active-high line 7: unnamed unused input active-high $ gpioget gpiochip0 0 1 What actually happens: $ gpiodetect gpiochip0 [0-003c] (8 lines) $ gpioinfo gpioinfo: error creating line iterator: Invalid argument $ gpioget gpiochip0 0 gpioget: error reading GPIO values: Invalid argument $ cat /proc/version_signature Ubuntu 5.13.0-22.22-lowlatency 5.13.19 $ apt-cache policy libgpiod2 libgpiod2: Installed: 1.6.2-1 Candidate: 1.6.2-1 Version table: *** 1.6.2-1 500 500 http://de.archive.ubuntu.com/ubuntu impish/universe amd64 Packages 100 /var/lib/dpkg/status I am testing with the onboard PCA9554A on a Fujitsu D3641-S motherboard. $ lspci | grep -i smb 00:1f.4 SMBus: Intel Corporation Cannon Lake PCH SMBus Controller (rev 10) $ lspci -s 1f.4 -vvv 00:1f.4 SMBus: Intel Corporation Cannon Lake PCH SMBus Controller (rev 10) DeviceName: Onboard - Other Subsystem: Fujitsu Technology Solutions Cannon Lake PCH SMBus Controller Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953613/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1840122] Re: System fails to reboot from live session or ubiquity-dm - squashfs_read_data failed to read block
From [1]: > if a unit is configured with After= on another unit, > the former is stopped before the latter if both are > shut down. so maybe we need After=umount.target in finalrd.service. [1] https://www.freedesktop.org/software/systemd/man/systemd.unit.html -- 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/1840122 Title: System fails to reboot from live session or ubiquity-dm - squashfs_read_data failed to read block Status in subiquity: New Status in casper package in Ubuntu: New Status in finalrd package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Status in casper source package in Bionic: Fix Released Status in finalrd source package in Bionic: New Status in linux source package in Bionic: Confirmed Status in casper source package in Eoan: Fix Released Status in finalrd source package in Eoan: New Status in linux source package in Eoan: Won't Fix Status in casper source package in Focal: Fix Released Status in finalrd source package in Focal: New Status in linux source package in Focal: New Bug description: Last known good image: Eoan Ubuntu Desktop 20190715 Similar results started to happen with new linux-hwe kernel based on eoan for 18.04.4 release. Test Case: 1. Boot eoan desktop to a live session 2. Wait a couple of minutes until snapd settles 3. Reboot the system from the system menu or from the command line Expected result: The system reboots Actual result: The systems fails to reboot or shutdown and displays some errors about failing to unmount /cdrom and squashfs errors in a loop. Unmounting /cdrom... [FAILED] Failed unmounting /cdrom. [ OK ] Started Shuts down the "li…" preinstalled system cleanly. [ OK ] Reached target Final Step. [ OK ] Started Reboot. [ OK ] Reached target Reboot. [ 115.744188] print_req_error: I/O error, dev sr0, sector 1508872 flags 80700 [ 115.768139] print_req_error: I/O error, dev sr0, sector 1508872 flags 0 [ 115.771469] print_req_error: I/O error, dev loop0, sector 1501550 flags 0 [ 115.775824] SQUASHFS error: squashfs_read_data failed to read block 0x2dd2d998 This also causes daily tests to fail and is reproducible in a VM and bare metal booted in legacy bios mode ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: casper 1.414 ProcVersionSignature: Ubuntu 5.2.0-10.11-generic 5.2.4 Uname: Linux 5.2.0-10-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CasperVersion: 1.414 CurrentDesktop: ubuntu:GNOME Date: Wed Aug 14 08:31:30 2019 LiveMediaBuild: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190813) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: casper UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CasperVersion: 1.414 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 LiveMediaBuild: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190814) Package: linux PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.2.0-10.11-generic 5.2.4 Tags: eoan Uname: Linux 5.2.0-10-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1788 F pulseaudio CasperVersion: 1.414 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 IwConfig: lono wireless extensions. ens3 no wireless extensions. LiveMediaBuild: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190814) Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 qxldrmfb ProcKernelCmdLine: file=/cdrom/preseed/username.seed initrd=/casper/initrd --- keyboard-configuration/layoutcode=fr keyboard-configuration/variantcode=oss ProcVersionSignature: Ubuntu 5.2.0-10.11-generic 5.2.4 RelatedPackageVersions: linux-restricted-modules-5.2.0-10-generic N/A linux-backports-modules-5.2.0-10-generic N/A linux-firmware
[Kernel-packages] [Bug 1950062] Re: Unable to access CPU i2c interfaces with AMD "Cezanne" CPU's
I am also having the same issue with a Ryzen 7 5700G -- 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/1950062 Title: Unable to access CPU i2c interfaces with AMD "Cezanne" CPU's Status in linux package in Ubuntu: Confirmed Status in Arch Linux: New Bug description: OpenRGB uses the CPU SMBus/i2c interfaces to talk to the motherboard RGB controller and the DRAM RGB controllers and after updating my system to a 5700G from a 2400G I see error messages in dmesg for each read and write attempt to the interfaces. If I swap the CPU back on the same install I am able to see and control the RGB interfaces. Another user on the OpenRGB discord with a 5600G is also seeing the same issues. 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 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: user 1654 F pulseaudio /dev/snd/pcmC1D0p: user 1654 F...m pulseaudio /dev/snd/controlC0: user 1654 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Nov 6 16:36:17 2021 InstallationDate: Installed on 2021-09-18 (49 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: TERM=xterm-256color PATH=(custom, no username) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-20-generic root=UUID=dc2e65cb-a2e0-408c-a64b-bb0ccc6fdef0 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: Upgraded to impish on 2021-10-17 (20 days ago) dmi.bios.date: 08/11/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P4.60 dmi.board.name: B450 Gaming-ITX/ac dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP4.60:bd08/11/2021:br5.17:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.:rvnASRock:rnB450Gaming-ITX/ac:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950062/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1953400] Re: shutdown not working from GNOME
Hi Dan On second thought, I'm having a bit of a hard time with my mobility. So I will get back to you when there's changes with what I'm experiencing with the shutdown procedure. Steve On December 6, 2021 8:50:51 p.m. Daniel van Vugt <1953...@bugs.launchpad.net> wrote: > Also it is fairly common for some background jobs to still be running on > shutdown. The system waits up to 90 seconds for those to complete. To > see what they are you can usually press Escape. > > ** Changed in: gnome-shell (Ubuntu) > Status: New => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1953400 > > Title: > shutdown not working from GNOME > > Status in gnome-shell package in Ubuntu: > Incomplete > > Bug description: > Upon using ubuntu 22.04 with latest updates. > > shutdown via gnome does shutdown but the power light stays on on > laptop. So I have to hold the button down for ten seconds. > > oddly enough > shutdown works in terminal correctly. > sudo shutdown -h now > works > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1953400/+subscriptions -- 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/1953400 Title: shutdown not working from GNOME Status in linux package in Ubuntu: Incomplete Bug description: Upon using ubuntu 22.04 with latest updates. shutdown via gnome does shutdown but the power light stays on on laptop. So I have to hold the button down for ten seconds. oddly enough shutdown works in terminal correctly. sudo shutdown -h now works To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953400/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1939628] Re: Fan goes full speed on resume from suspend (Lenovo ThinkPad T460)
Still a problem on 5.11.0.41-generic. -- 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/1939628 Title: Fan goes full speed on resume from suspend (Lenovo ThinkPad T460) Status in linux-signed-hwe-5.11 package in Ubuntu: Confirmed Bug description: On resume from suspend the fan goes full speed. Regression - this only happens intermittently on kernel 5.8.0-63, but happens every time on kernel 5.11.0-25. Running `sensors` after resume shows: ``` $ sensors thinkpad-isa- Adapter: ISA adapter fan1:4776 RPM temp1:N/A temp2:N/A temp3: +0.0°C temp4: +0.0°C temp5: +0.0°C temp6: +0.0°C temp7: +0.0°C temp8: +0.0°C coretemp-isa- Adapter: ISA adapter Package id 0: +30.0°C (high = +100.0°C, crit = +100.0°C) Core 0:+29.0°C (high = +100.0°C, crit = +100.0°C) Core 1:+28.0°C (high = +100.0°C, crit = +100.0°C) BAT0-acpi-0 Adapter: ACPI interface in0: 11.82 V iwlwifi_1-virtual-0 Adapter: Virtual device temp1:+31.0°C pch_skylake-virtual-0 Adapter: Virtual device temp1:+29.5°C BAT1-acpi-0 Adapter: ACPI interface in0: 11.06 V acpitz-acpi-0 Adapter: ACPI interface temp1:+48.0°C (crit = +128.0°C) ``` Using kernel 5.11.0-25, `thinkpad-isa- - temp1` shows a temperature prior to suspend, then it consistently shows `N/A` after resume. Using kernel 5.8.0-63, `thinkpad-isa- - temp1` shows a temperature when the fan control is working normally (which fails intermittently following suspend/resume) and shows `N/A` when it does not work. ``` $ cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=20.04 DISTRIB_CODENAME=focal DISTRIB_DESCRIPTION="Ubuntu 20.04.3 LTS" ``` ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.11.0-25-generic 5.11.0-25.27~20.04.1 ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Aug 12 00:47:13 2021 InstallationDate: Installed on 2020-05-02 (466 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) 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/1939628/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1953287] Re: test_bpf.sh test in net of ubuntu_kernel_selftests failed on B-4.15 and variants
This is the CVE reported for this issue: https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-25020 The fix is this upstream commit, which I have backported to bionic, and will submit after running one extra test. https://github.com/torvalds/linux/commit/050fad7c4534c13c8eb1d9c2ba66012e014773cb Thanks. Cascardo. ** Information type changed from Private to Public Security ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-25020 ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => Invalid ** Changed in: linux (Ubuntu Bionic) Status: New => In Progress ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo) ** Changed in: linux (Ubuntu Bionic) Importance: Undecided => High ** Description changed: + [Impact] + A CBPF program jumping over a large number of instructions may lead to kernel code execution. + The test might fail with EINVAL or EOPNOTSUPP, which must be accounted for on different kernel versions. + + [Test case] + Load test_bpf module. + + [Potential regression] + Some CBPF and EBPF programs might not load. + + + + + + Issue found on 4.15.0-1107-ibm-gt with node onibi. This test failed without any obvious error from the test output, the summary shows there is one failure but all 344 test cases were marked as PASS: [ 1851.020315] test_bpf: #0 TAX jited:1 46 44 43 PASS [ 1851.021767] test_bpf: #1 TXA jited:1 43 46 43 PASS [ 1851.024004] test_bpf: #2 ADD_SUB_MUL_K jited:1 45 PASS [ 1851.024886] test_bpf: #3 DIV_MOD_KX jited:1 70 PASS [ 1851.026103] test_bpf: #4 AND_OR_LSH_K jited:1 39 43 PASS [ 1851.027394] test_bpf: #5 LD_IMM_0 jited:1 42 PASS [ 1851.028027] test_bpf: #6 LD_IND jited:1 85 85 85 PASS [ 1851.030687] test_bpf: #7 LD_ABS jited:1 87 85 85 PASS [ 1851.033343] test_bpf: #8 LD_ABS_LL jited:1 90 70 PASS [ 1851.035030] test_bpf: #9 LD_IND_LL jited:1 61 58 58 PASS [ 1851.036890] test_bpf: #10 LD_ABS_NET jited:1 86 70 PASS [ 1851.038590] test_bpf: #11 LD_IND_NET jited:1 77 56 56 PASS [ 1851.040573] test_bpf: #12 LD_PKTTYPE jited:1 43 43 PASS [ 1851.041582] test_bpf: #13 LD_MARK jited:1 41 42 PASS [ 1851.042494] test_bpf: #14 LD_RXHASH jited:1 42 44 PASS [ 1851.043436] test_bpf: #15 LD_QUEUE jited:1 43 43 PASS [ 1851.044379] test_bpf: #16 LD_PROTOCOL jited:1 50 50 PASS [ 1851.045457] test_bpf: #17 LD_VLAN_TAG jited:1 41 41 PASS [ 1851.046363] test_bpf: #18 LD_VLAN_TAG_PRESENT jited:1 39 41 PASS [ 1851.047238] test_bpf: #19 LD_IFINDEX jited:1 44 44 PASS [ 1851.048199] test_bpf: #20 LD_HATYPE jited:1 44 44 PASS [ 1851.049157] test_bpf: #21 LD_CPU jited:1 51 50 PASS [ 1851.050250] test_bpf: #22 LD_NLATTR jited:1 43 68 PASS [ 1851.051465] test_bpf: #23 LD_NLATTR_NEST jited:1 85 233 PASS [ 1851.054890] test_bpf: #24 LD_PAYLOAD_OFF jited:1 527 745 PASS [ 1851.067698] test_bpf: #25 LD_ANC_XOR jited:1 42 42 PASS [ 1851.069510] test_bpf: #26 SPILL_FILL jited:1 45 45 48 PASS [ 1851.071372] test_bpf: #27 JEQ jited:1 85 46 47 PASS [ 1851.073284] test_bpf: #28 JGT jited:1 85 46 49 PASS [ 1851.075260] test_bpf: #29 JGE (jt 0), test 1 jited:1 86 47 47 PASS [ 1851.077151] test_bpf: #30 JGE (jt 0), test 2 jited:1 48 45 44 PASS [ 1851.078613] test_bpf: #31 JGE jited:1 48 46 47 PASS [ 1851.080128] test_bpf: #32 JSET jited:1 45 44 54 PASS [ 1851.081667] test_bpf: #33 tcpdump port 22 jited:1 83 106 72 PASS [ 1851.084383] test_bpf: #34 tcpdump complex jited:1 83 102 93 PASS [ 1851.087279] test_bpf: #35 RET_A jited:1 41 41 PASS [ 1851.088195] test_bpf: #36 INT: ADD trivial jited:1 43 PASS [ 1851.088700] test_bpf: #37 INT: MUL_X jited:1 41 PASS [ 1851.089186] test_bpf: #38 INT: MUL_X2 jited:1 40 PASS [ 1851.089665] test_bpf: #39 INT: MUL32_X jited:1 42 PASS [ 1851.090170] test_bpf: #40 INT: ADD 64-bit jited:1 90 PASS [ 1851.091228] test_bpf: #41 INT: ADD 32-bit jited:1 91 PASS [ 1851.092232] test_bpf: #42 INT: SUB jited:1 88 PASS [ 1851.093260] test_bpf: #43 INT: XOR jited:1 56 PASS [ 1851.093920] test_bpf: #44 INT: MUL jited:1 194 PASS [ 1851.095947] test_bpf: #45 MOV REG64 jited:1 43 PASS [ 1851.096513] test_bpf: #46 MOV REG32 jited:1 45 PASS [ 1851.097471] test_bpf: #47 LD IMM64 jited:1 44 PASS [ 1851.098000] test_bpf: #48 INT: ALU MIX jited:1 73 PASS [ 1851.098807] test_bpf: #49 INT: shifts by register jited:1 53 PASS [ 1851.099421] test_bpf: #50 INT: DIV + ABS jited:1 92 54 PASS [ 1851.100960] test_bpf: #51 INT: DIV by -1 jited:1 85 50 PASS [ 1851.102431] test_bpf: #52 check: missing ret PASS [ 1851.102650] test_bpf: #53 check: div_k_0 PASS [ 1851.102660] test_bpf: #54 check: unknown insn PASS [ 1851.102674] test_bpf: #55 check: out of range spill/fill PASS [ 1851.102685] test_bpf: #56 JUMPS +
Re: [Kernel-packages] [Bug 1953400] Re: shutdown not working from GNOME
Thanks I'll try again today. Steve On December 7, 2021 9:01:04 p.m. Daniel van Vugt <1953...@bugs.launchpad.net> wrote: > Reassigning to the kernel because GNOME has no control over shutdown > other than the part where GNOME exits. > > ** Package changed: gnome-shell (Ubuntu) => linux (Ubuntu) > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1953400 > > Title: > shutdown not working from GNOME > > Status in linux package in Ubuntu: > Incomplete > > Bug description: > Upon using ubuntu 22.04 with latest updates. > > shutdown via gnome does shutdown but the power light stays on on > laptop. So I have to hold the button down for ten seconds. > > oddly enough > shutdown works in terminal correctly. > sudo shutdown -h now > works > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953400/+subscriptions -- 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/1953400 Title: shutdown not working from GNOME Status in linux package in Ubuntu: Incomplete Bug description: Upon using ubuntu 22.04 with latest updates. shutdown via gnome does shutdown but the power light stays on on laptop. So I have to hold the button down for ten seconds. oddly enough shutdown works in terminal correctly. sudo shutdown -h now works To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953400/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1953400] Re: shutdown not working from GNOME
Hello Dan Here's exactly what I'm experiencing during the shutdown. I tried what you said, I pressed shut down in the graphical interface, I saw the regular shutdown prompts. But then after that I can hear a partial shutdown of the hard drive, but the power of light still remains on. I waited a minute or two and nothing happened, so I press the power button down for 10 seconds. Is this normal? If so could you please clarify what I can do. Any input would be greatly appreciated. Steve On December 7, 2021 9:01:05 p.m. Daniel van Vugt <1953...@bugs.launchpad.net> wrote: > Please remember to follow the instructions in comment #1. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1953400 > > Title: > shutdown not working from GNOME > > Status in linux package in Ubuntu: > Incomplete > > Bug description: > Upon using ubuntu 22.04 with latest updates. > > shutdown via gnome does shutdown but the power light stays on on > laptop. So I have to hold the button down for ten seconds. > > oddly enough > shutdown works in terminal correctly. > sudo shutdown -h now > works > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953400/+subscriptions -- 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/1953400 Title: shutdown not working from GNOME Status in linux package in Ubuntu: Incomplete Bug description: Upon using ubuntu 22.04 with latest updates. shutdown via gnome does shutdown but the power light stays on on laptop. So I have to hold the button down for ten seconds. oddly enough shutdown works in terminal correctly. sudo shutdown -h now works To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953400/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1953613] 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 1953613 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/1953613 Title: GPIO character device API not enabled in kernel Status in linux package in Ubuntu: Incomplete Bug description: The current versions of gpiod, libgpiod-dev and libgpiod2 (1.6.2-1) use version 1 of the GPIO character device API. However, they cannot work because the interface is disabled in the default kernel (tested with 5.13.19). After rebuilding the kernel with the option CONFIG_GPIO_CDEV_V1=y, the gpiod tools work as expected. What I expect to happen: $ gpiodetect gpiochip0 [0-003c] (8 lines) $ gpioinfo gpiochip0 - 8 lines: line 0: unnamed unused output active-high line 1: unnamed unused output active-high line 2: unnamed unused output active-high line 3: unnamed unused output active-high line 4: unnamed unused output active-high line 5: unnamed unused output active-high line 6: unnamed unused input active-high line 7: unnamed unused input active-high $ gpioget gpiochip0 0 1 What actually happens: $ gpiodetect gpiochip0 [0-003c] (8 lines) $ gpioinfo gpioinfo: error creating line iterator: Invalid argument $ gpioget gpiochip0 0 gpioget: error reading GPIO values: Invalid argument $ cat /proc/version_signature Ubuntu 5.13.0-22.22-lowlatency 5.13.19 $ apt-cache policy libgpiod2 libgpiod2: Installed: 1.6.2-1 Candidate: 1.6.2-1 Version table: *** 1.6.2-1 500 500 http://de.archive.ubuntu.com/ubuntu impish/universe amd64 Packages 100 /var/lib/dpkg/status I am testing with the onboard PCA9554A on a Fujitsu D3641-S motherboard. $ lspci | grep -i smb 00:1f.4 SMBus: Intel Corporation Cannon Lake PCH SMBus Controller (rev 10) $ lspci -s 1f.4 -vvv 00:1f.4 SMBus: Intel Corporation Cannon Lake PCH SMBus Controller (rev 10) DeviceName: Onboard - Other Subsystem: Fujitsu Technology Solutions Cannon Lake PCH SMBus Controller Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953613/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1953613] [NEW] GPIO character device API not enabled in kernel
Public bug reported: The current versions of gpiod, libgpiod-dev and libgpiod2 (1.6.2-1) use version 1 of the GPIO character device API. However, they cannot work because the interface is disabled in the default kernel (tested with 5.13.19). After rebuilding the kernel with the option CONFIG_GPIO_CDEV_V1=y, the gpiod tools work as expected. What I expect to happen: $ gpiodetect gpiochip0 [0-003c] (8 lines) $ gpioinfo gpiochip0 - 8 lines: line 0: unnamed unused output active-high line 1: unnamed unused output active-high line 2: unnamed unused output active-high line 3: unnamed unused output active-high line 4: unnamed unused output active-high line 5: unnamed unused output active-high line 6: unnamed unused input active-high line 7: unnamed unused input active-high $ gpioget gpiochip0 0 1 What actually happens: $ gpiodetect gpiochip0 [0-003c] (8 lines) $ gpioinfo gpioinfo: error creating line iterator: Invalid argument $ gpioget gpiochip0 0 gpioget: error reading GPIO values: Invalid argument $ cat /proc/version_signature Ubuntu 5.13.0-22.22-lowlatency 5.13.19 $ apt-cache policy libgpiod2 libgpiod2: Installed: 1.6.2-1 Candidate: 1.6.2-1 Version table: *** 1.6.2-1 500 500 http://de.archive.ubuntu.com/ubuntu impish/universe amd64 Packages 100 /var/lib/dpkg/status I am testing with the onboard PCA9554A on a Fujitsu D3641-S motherboard. $ lspci | grep -i smb 00:1f.4 SMBus: Intel Corporation Cannon Lake PCH SMBus Controller (rev 10) $ lspci -s 1f.4 -vvv 00:1f.4 SMBus: Intel Corporation Cannon Lake PCH SMBus Controller (rev 10) DeviceName: Onboard - Other Subsystem: Fujitsu Technology Solutions Cannon Lake PCH SMBus Controller Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- https://bugs.launchpad.net/bugs/1953613 Title: GPIO character device API not enabled in kernel Status in linux package in Ubuntu: New Bug description: The current versions of gpiod, libgpiod-dev and libgpiod2 (1.6.2-1) use version 1 of the GPIO character device API. However, they cannot work because the interface is disabled in the default kernel (tested with 5.13.19). After rebuilding the kernel with the option CONFIG_GPIO_CDEV_V1=y, the gpiod tools work as expected. What I expect to happen: $ gpiodetect gpiochip0 [0-003c] (8 lines) $ gpioinfo gpiochip0 - 8 lines: line 0: unnamed unused output active-high line 1: unnamed unused output active-high line 2: unnamed unused output active-high line 3: unnamed unused output active-high line 4: unnamed unused output active-high line 5: unnamed unused output active-high line 6: unnamed unused input active-high line 7: unnamed unused input active-high $ gpioget gpiochip0 0 1 What actually happens: $ gpiodetect gpiochip0 [0-003c] (8 lines) $ gpioinfo gpioinfo: error creating line iterator: Invalid argument $ gpioget gpiochip0 0 gpioget: error reading GPIO values: Invalid argument $ cat /proc/version_signature Ubuntu 5.13.0-22.22-lowlatency 5.13.19 $ apt-cache policy libgpiod2 libgpiod2: Installed: 1.6.2-1 Candidate: 1.6.2-1 Version table: *** 1.6.2-1 500 500 http://de.archive.ubuntu.com/ubuntu impish/universe amd64 Packages 100 /var/lib/dpkg/status I am testing with the onboard PCA9554A on a Fujitsu D3641-S motherboard. $ lspci | grep -i smb 00:1f.4 SMBus: Intel Corporation Cannon Lake PCH SMBus Controller (rev 10) $ lspci -s 1f.4 -vvv 00:1f.4 SMBus: Intel Corporation Cannon Lake PCH SMBus Controller (rev 10) DeviceName: Onboard - Other Subsystem: Fujitsu Technology Solutions Cannon Lake PCH SMBus Controller Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953613/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1948436] Re: Add RevID field to VPD info in EEPROM
This bug was fixed in the package linux-bluefield - 5.4.0-1022.25 --- linux-bluefield (5.4.0-1022.25) focal; urgency=medium * focal/linux-bluefield: 5.4.0-1022.25 -proposed tracker (LP: #1949817) * Add RevID field to VPD info in EEPROM (LP: #1948436) - SAUCE: mlx-bootctl: Add RevID field to VPD info * Check if secure boot is enabled with development keys (LP: #1948434) - SAUCE: mlx-bootctl: Check secure boot development mode status bit [ Ubuntu: 5.4.0-91.102 ] * focal/linux: 5.4.0-91.102 -proposed tracker (LP: #1949840) * Packaging resync (LP: #1786013) - [Packaging] update Ubuntu.md - debian/dkms-versions -- update from kernel-versions (main/2021.11.08) * KVM emulation failure when booting into VM crash kernel with multiple CPUs (LP: #1948862) - KVM: x86: Properly reset MMU context at vCPU RESET/INIT * aufs: kernel bug with apparmor and fuseblk (LP: #1948470) - SAUCE: aufs: bugfix, stop omitting path->mnt * ebpf: bpf_redirect fails with ip6 gre interfaces (LP: #1947164) - net: handle ARPHRD_IP6GRE in dev_is_mac_header_xmit() * require CAP_NET_ADMIN to attach N_HCI ldisc (LP: #1949516) - Bluetooth: hci_ldisc: require CAP_NET_ADMIN to attach N_HCI ldisc * ACL updates on OCFS2 are not revalidated (LP: #1947161) - ocfs2: fix remounting needed after setfacl command * ppc64 BPF JIT mod by 1 will not return 0 (LP: #1948351) - powerpc/bpf: Fix BPF_MOD when imm == 1 * Drop "UBUNTU: SAUCE: cachefiles: Page leaking in cachefiles_read_backing_file while vmscan is active" (LP: #1947709) - Revert "UBUNTU: SAUCE: cachefiles: Page leaking in cachefiles_read_backing_file while vmscan is active" * Reassign I/O Path of ConnectX-5 Port 1 before Port 2 causes NULL dereference (LP: #1943464) - s390/pci: fix leak of PCI device structure - s390/pci: fix use after free of zpci_dev - s390/pci: fix zpci_zdev_put() on reserve * [SRU][F] USB: serial: pl2303: add support for PL2303HXN (LP: #1948377) - USB: serial: pl2303: add support for PL2303HXN - USB: serial: pl2303: fix line-speed handling on newer chips * Focal update: v5.4.151 upstream stable release (LP: #1947888) - tty: Fix out-of-bound vmalloc access in imageblit - cpufreq: schedutil: Use kobject release() method to free sugov_tunables - cpufreq: schedutil: Destroy mutex before kobject_put() frees the memory - usb: cdns3: fix race condition before setting doorbell - fs-verity: fix signed integer overflow with i_size near S64_MAX - 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 - 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 - drm/amd/display: Pass PCI deviceid into DC - ipvs: check that ip_vs_conn_tab_bits is between 8 and 20 - 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 - hwmon: (tmp421) report /PVLD condition as fault - hwmon: (tmp421) fix rounding for negative values - net: ipv4: Fix rtnexthop len when RTA_FLOW is present - e100: fix length calculation in e100_get_regs_len - e100: fix buffer overrun in e100_get_regs - selftests, bpf: test_lwt_ip_encap: Really disable rp_filter - scsi: csiostor: Add module softdep on cxgb4 - net: hns3: do not allow call hns3_nic_net_open repeatedly - 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 - 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: fix reserved space counter leakage - 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 - net: stmmac: don't attach interface until resume finishes - PCI: Fix pci_host_bridge struct device release/free handling -
[Kernel-packages] [Bug 1948434] Re: Check if secure boot is enabled with development keys
This bug was fixed in the package linux-bluefield - 5.4.0-1022.25 --- linux-bluefield (5.4.0-1022.25) focal; urgency=medium * focal/linux-bluefield: 5.4.0-1022.25 -proposed tracker (LP: #1949817) * Add RevID field to VPD info in EEPROM (LP: #1948436) - SAUCE: mlx-bootctl: Add RevID field to VPD info * Check if secure boot is enabled with development keys (LP: #1948434) - SAUCE: mlx-bootctl: Check secure boot development mode status bit [ Ubuntu: 5.4.0-91.102 ] * focal/linux: 5.4.0-91.102 -proposed tracker (LP: #1949840) * Packaging resync (LP: #1786013) - [Packaging] update Ubuntu.md - debian/dkms-versions -- update from kernel-versions (main/2021.11.08) * KVM emulation failure when booting into VM crash kernel with multiple CPUs (LP: #1948862) - KVM: x86: Properly reset MMU context at vCPU RESET/INIT * aufs: kernel bug with apparmor and fuseblk (LP: #1948470) - SAUCE: aufs: bugfix, stop omitting path->mnt * ebpf: bpf_redirect fails with ip6 gre interfaces (LP: #1947164) - net: handle ARPHRD_IP6GRE in dev_is_mac_header_xmit() * require CAP_NET_ADMIN to attach N_HCI ldisc (LP: #1949516) - Bluetooth: hci_ldisc: require CAP_NET_ADMIN to attach N_HCI ldisc * ACL updates on OCFS2 are not revalidated (LP: #1947161) - ocfs2: fix remounting needed after setfacl command * ppc64 BPF JIT mod by 1 will not return 0 (LP: #1948351) - powerpc/bpf: Fix BPF_MOD when imm == 1 * Drop "UBUNTU: SAUCE: cachefiles: Page leaking in cachefiles_read_backing_file while vmscan is active" (LP: #1947709) - Revert "UBUNTU: SAUCE: cachefiles: Page leaking in cachefiles_read_backing_file while vmscan is active" * Reassign I/O Path of ConnectX-5 Port 1 before Port 2 causes NULL dereference (LP: #1943464) - s390/pci: fix leak of PCI device structure - s390/pci: fix use after free of zpci_dev - s390/pci: fix zpci_zdev_put() on reserve * [SRU][F] USB: serial: pl2303: add support for PL2303HXN (LP: #1948377) - USB: serial: pl2303: add support for PL2303HXN - USB: serial: pl2303: fix line-speed handling on newer chips * Focal update: v5.4.151 upstream stable release (LP: #1947888) - tty: Fix out-of-bound vmalloc access in imageblit - cpufreq: schedutil: Use kobject release() method to free sugov_tunables - cpufreq: schedutil: Destroy mutex before kobject_put() frees the memory - usb: cdns3: fix race condition before setting doorbell - fs-verity: fix signed integer overflow with i_size near S64_MAX - 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 - 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 - drm/amd/display: Pass PCI deviceid into DC - ipvs: check that ip_vs_conn_tab_bits is between 8 and 20 - 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 - hwmon: (tmp421) report /PVLD condition as fault - hwmon: (tmp421) fix rounding for negative values - net: ipv4: Fix rtnexthop len when RTA_FLOW is present - e100: fix length calculation in e100_get_regs_len - e100: fix buffer overrun in e100_get_regs - selftests, bpf: test_lwt_ip_encap: Really disable rp_filter - scsi: csiostor: Add module softdep on cxgb4 - net: hns3: do not allow call hns3_nic_net_open repeatedly - 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 - 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: fix reserved space counter leakage - 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 - net: stmmac: don't attach interface until resume finishes - PCI: Fix pci_host_bridge struct device release/free handling -
[Kernel-packages] [Bug 1951767] Re: [SRU][I/J/OEM-5.13/OEM-5.14] Add MAC passthrough support for more Lenovo docks
This bug was fixed in the package linux-oem-5.13 - 5.13.0-1021.25 --- linux-oem-5.13 (5.13.0-1021.25) focal; urgency=medium * focal/linux-oem-5.13: 5.13.0-1021.25 -proposed tracker (LP: #1953028) * [SRU][I/OEM-5.13/OEM-5.14] Fix USB3.1 hotplug after S3 on AMD renoir (LP: #1952817) - drm/amd/display: Look at firmware version to determine using dmub on dcn21 * Fix non-working e1000e device after resume (LP: #1951861) - SAUCE: Revert "e1000e: Additional PHY power saving in S0ix" - SAUCE: Revert "e1000e: Add polling mechanism to indicate CSME DPG exit" - SAUCE: Revert "e1000e: Add handshake with the CSME to support S0ix" * [SRU][I/J/OEM-5.13/OEM-5.14] Add MAC passthrough support for more Lenovo docks (LP: #1951767) - net: usb: r8152: Add MAC passthrough support for more Lenovo Docks * Fix missing external headset after resume problem for Cirrus CS8409 sound driver (LP: #1952385) - SAUCE: ALSA: hda/cs8409: Schedule delayed work for jack detect on resume -- Timo Aaltonen Thu, 02 Dec 2021 19:29:38 +0200 ** Changed in: linux-oem-5.13 (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1951767 Title: [SRU][I/J/OEM-5.13/OEM-5.14] Add MAC passthrough support for more Lenovo docks Status in HWE Next: New Status in linux package in Ubuntu: Fix Committed Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.13 source package in Focal: Fix Released Status in linux-oem-5.14 source package in Focal: Fix Committed Status in linux source package in Impish: Fix Committed Status in linux source package in Jammy: Fix Committed Bug description: [Impact] MAC pass through is not working on new TBT and USB-C docks. [Fix] Enable MAC pass through based on Lenovo USB hub. [Test] Tested on Lenovo TBT4 and TBT3 dock, MAC pass through works well. [Where problems could occur] The Realtek USB ethernet in Lenovo USB hub will mess the MAC address. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1951767/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1951861] Re: Fix non-working e1000e device after resume
This bug was fixed in the package linux-oem-5.13 - 5.13.0-1021.25 --- linux-oem-5.13 (5.13.0-1021.25) focal; urgency=medium * focal/linux-oem-5.13: 5.13.0-1021.25 -proposed tracker (LP: #1953028) * [SRU][I/OEM-5.13/OEM-5.14] Fix USB3.1 hotplug after S3 on AMD renoir (LP: #1952817) - drm/amd/display: Look at firmware version to determine using dmub on dcn21 * Fix non-working e1000e device after resume (LP: #1951861) - SAUCE: Revert "e1000e: Additional PHY power saving in S0ix" - SAUCE: Revert "e1000e: Add polling mechanism to indicate CSME DPG exit" - SAUCE: Revert "e1000e: Add handshake with the CSME to support S0ix" * [SRU][I/J/OEM-5.13/OEM-5.14] Add MAC passthrough support for more Lenovo docks (LP: #1951767) - net: usb: r8152: Add MAC passthrough support for more Lenovo Docks * Fix missing external headset after resume problem for Cirrus CS8409 sound driver (LP: #1952385) - SAUCE: ALSA: hda/cs8409: Schedule delayed work for jack detect on resume -- Timo Aaltonen Thu, 02 Dec 2021 19:29:38 +0200 ** Changed in: linux-oem-5.13 (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1951861 Title: Fix non-working e1000e device after resume Status in HWE Next: New Status in OEM Priority Project: New Status in linux package in Ubuntu: Confirmed 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.13 source package in Focal: Fix Released Status in linux-oem-5.14 source package in Focal: Fix Committed Status in linux source package in Impish: Fix Committed 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] e1000e devices stop working after s2idle resume. [Fix] Revert the offending patch series, which is to bring some minor power saving. [Test] Vendor did extensive tests and didn't find any regression, and the power consumption remains the same. [Where problems could occur] Maybe on some system the series can save some energy, so reverting will cause some power consumption increase. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1951861/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1952385] Re: Fix missing external headset after resume problem for Cirrus CS8409 sound driver
This bug was fixed in the package linux-oem-5.13 - 5.13.0-1021.25 --- linux-oem-5.13 (5.13.0-1021.25) focal; urgency=medium * focal/linux-oem-5.13: 5.13.0-1021.25 -proposed tracker (LP: #1953028) * [SRU][I/OEM-5.13/OEM-5.14] Fix USB3.1 hotplug after S3 on AMD renoir (LP: #1952817) - drm/amd/display: Look at firmware version to determine using dmub on dcn21 * Fix non-working e1000e device after resume (LP: #1951861) - SAUCE: Revert "e1000e: Additional PHY power saving in S0ix" - SAUCE: Revert "e1000e: Add polling mechanism to indicate CSME DPG exit" - SAUCE: Revert "e1000e: Add handshake with the CSME to support S0ix" * [SRU][I/J/OEM-5.13/OEM-5.14] Add MAC passthrough support for more Lenovo docks (LP: #1951767) - net: usb: r8152: Add MAC passthrough support for more Lenovo Docks * Fix missing external headset after resume problem for Cirrus CS8409 sound driver (LP: #1952385) - SAUCE: ALSA: hda/cs8409: Schedule delayed work for jack detect on resume -- Timo Aaltonen Thu, 02 Dec 2021 19:29:38 +0200 ** Changed in: linux-oem-5.13 (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1952385 Title: Fix missing external headset after resume problem for Cirrus CS8409 sound driver Status in HWE Next: New Status in linux package in Ubuntu: Triaged Status in linux-oem-5.13 package in Ubuntu: New 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.13 source package in Focal: Fix Released Status in linux-oem-5.14 source package in Focal: Fix Committed Status in linux source package in Jammy: Triaged Status in linux-oem-5.13 source package in Jammy: New Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: [SRU Justification] [Impact] On some platforms with Cirrus CS8409 audio codec, the external headset will fail to be detected after system resume. [Fix] Cirrus released a fix and send it upstream for approval. It's trying to schedule a harmless delayed work to do jack detection to reflect the real power state after resume. [Test] Plug-in an external headset in front headset port, suspend/resume the system then check whether the headset function works as expected. [Where problem could occur] Low. It only affect the platforms with Cirrus codec CS8409 which used to have problem. == Original Bug Description == [Summary] System can't detect external headset after suspend [Steps to reproduce] 1. install manifest and boot into OS 2. plug-in an external headset in front headset port 3. un-plug external headset 4. suspend system 5. resume system from suspend 6. plug-in an external headset [Expected result] System could detect external headset after suspend [Actual result] System can't detect external headset after suspend [Failure rate] 3/3 [Additional information] CID: 202110-29567 SKU: DLPV-SFF-DVT-C1 Image: canonical-oem-somerville-focal-amd64-20200502-85+fossa-davos-adl+X152 system-manufacturer: Dell Inc. system-product-name: Vostro 3710 bios-version: 0.13.73 CPU: 12th Gen Intel(R) Core(TM) i7-12700 (20x) GPU: :00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:4680] (rev 0c) kernel-version: 5.13.0-1019-oem [Stage] Issue reported and logs collected right after it happened To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1952385/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1952817] Re: [SRU][I/OEM-5.13/OEM-5.14] Fix USB3.1 hotplug after S3 on AMD renoir
This bug was fixed in the package linux-oem-5.13 - 5.13.0-1021.25 --- linux-oem-5.13 (5.13.0-1021.25) focal; urgency=medium * focal/linux-oem-5.13: 5.13.0-1021.25 -proposed tracker (LP: #1953028) * [SRU][I/OEM-5.13/OEM-5.14] Fix USB3.1 hotplug after S3 on AMD renoir (LP: #1952817) - drm/amd/display: Look at firmware version to determine using dmub on dcn21 * Fix non-working e1000e device after resume (LP: #1951861) - SAUCE: Revert "e1000e: Additional PHY power saving in S0ix" - SAUCE: Revert "e1000e: Add polling mechanism to indicate CSME DPG exit" - SAUCE: Revert "e1000e: Add handshake with the CSME to support S0ix" * [SRU][I/J/OEM-5.13/OEM-5.14] Add MAC passthrough support for more Lenovo docks (LP: #1951767) - net: usb: r8152: Add MAC passthrough support for more Lenovo Docks * Fix missing external headset after resume problem for Cirrus CS8409 sound driver (LP: #1952385) - SAUCE: ALSA: hda/cs8409: Schedule delayed work for jack detect on resume -- Timo Aaltonen Thu, 02 Dec 2021 19:29:38 +0200 ** Changed in: linux-oem-5.13 (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1952817 Title: [SRU][I/OEM-5.13/OEM-5.14] Fix USB3.1 hotplug after S3 on AMD renoir 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-oem-5.13 source package in Focal: Fix Released Status in linux-oem-5.14 source package in Focal: Fix Committed Status in linux source package in Impish: In Progress Bug description: [Impact] On new amdgpu renoir firmware, the USB-type-C port is useless when uplug the USB-type-C <-> DP/HDMI/VGA Dongle after the system resumed from S3. [Fix] Restore the old amdgpu fw, this issue is gone. For new fw, AMD make kernel fix be ready, after backport, the issue is not reproduced on new fw. Cherry-picked from stable kernel release to fix it. [Test] After S3 on renoir's platforms, hotplug USB, the USB3.1 devices works good. [Where problems could occur] AMD renoir platform may have issues when suspend. Jammy already got this commit via stable updates v5.15.3 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1952817/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1952403] Re: Realtek 8822CE wireless card fails to work after laptop discharge in sleep
I forgot to add - I use the sleep button from the GUI and it works well.
Thank you for reminding me about it, as I tried another solution, based
on this forum post: https://forum.garudalinux.org/t/rtl8822ce-wifi-
problems-asus-tuf-gaming-a15/1940/7
I created a SystemD service, called `network-restart` with the following
contents:
```
# cat /etc/systemd/system/network-restart.service
# systemctl enable --now network-restart.service
# systemctl start network-restart.service
# systemctl stop network-restart.service
# systemctl disable --now network-restart.service
# systemctl status network-restart.service
# systemctl daemon-reload
[Unit]
Description=Network Suspend/Resume Service
Before=sleep.target
StopWhenUnneeded=yes
[Service]
User=root
Type=oneshot
RemainAfterExit=yes
ExecStartPre=/usr/bin/nmcli networking off
ExecStart=/usr/bin/sleep 1
ExecStart=-/usr/bin/systemctl stop NetworkManager
ExecStart=/usr/bin/sleep 1
ExecStart=/usr/bin/ip link set wlp3s0 down
ExecStart=/usr/bin/sleep 1
ExecStart=/usr/sbin/modprobe -r rtw88_8822ce
ExecStop=/usr/bin/sleep 5
ExecStop=/usr/sbin/modprobe rtw88_8822ce
ExecStop=/usr/bin/sleep 2
ExecStop=/usr/bin/ip link set wlp3s0 up
ExecStop=/usr/bin/sleep 2
ExecStop=/usr/bin/systemctl start NetworkManager
ExecStop=/usr/bin/sleep 2
ExecStop=/usr/bin/nmcli networking on
ExecStop=/usr/bin/sleep 1
ExecStop=/usr/bin/nmcli r wifi off
ExecStop=/usr/bin/sleep 1
ExecStop=/usr/bin/nmcli r wifi on
[Install]
WantedBy=sleep.target
```
I saw no changes, except goind to sleep taking more time. It didn't
succeed in "resurrecting" the wi-fi card after returning from sleep,
stopping at the line `/usr/bin/ip link set wlp3s0 up` with the error
that no such interface exists. Seeing that it didn't help, I removed
this service from the system.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1952403
Title:
Realtek 8822CE wireless card fails to work after laptop discharge in
sleep
Status in linux package in Ubuntu:
Confirmed
Bug description:
I own an Asus TUF A15 FA506IV laptop with Ubuntu 21.10. After putting
it to sleep it discharged. Turning it back on the Wireless cards
doesn't work.
This is what I found in the logs that could help:
Nov 24 15:25:56 Zveri2 krunner[16146]: [11/24/21, 15:25:56:311] info: Store:
POWER_RESUMED
Nov 24 15:25:56 Zveri2 krunner[16146]: [11/24/21, 15:25:56:312] info: Store:
SET_SUSPEND_STATUS true
Nov 24 15:25:56 Zveri2 krunner[16146]: [11/24/21, 15:25:56:313] info:
[DESKTOP-SIDE-EFFECT] Update from desktop for keys ["app"]
Nov 24 15:25:56 Zveri2 kernel: [21587.358139] rtw_8822ce :03:00.0: start
vif 80:30:49:cc:98:0f on port 0
Nov 24 15:25:56 Zveri2 charon: 01[KNL] interface wlp3s0 activated
Nov 24 15:25:56 Zveri2 NetworkManager[1059]: [1637760356.4839]
manager: NetworkManager state is now CONNECTED_LOCAL
Nov 24 15:25:56 Zveri2 krunner[16146]: [11/24/21, 15:25:56:489] info:
NetworkStatus: Network check failed {
Nov 24 15:25:56 Zveri2 krunner[16146]: "error": "Failed to fetch"
Nov 24 15:25:56 Zveri2 krunner[16146]: }
Nov 24 15:25:56 Zveri2 krunner[16146]: [11/24/21, 15:25:56:490] info: Network
status check {
Nov 24 15:25:56 Zveri2 krunner[16146]: "elapsed_time_ms": 999784,
Nov 24 15:25:56 Zveri2 krunner[16146]: "navigator_online": false,
Nov 24 15:25:56 Zveri2 krunner[16146]: "api_test": "offline"
Nov 24 15:25:56 Zveri2 krunner[16146]: }
After this I am getting the following trace:
Nov 24 15:26:05 Zveri2 kernel: [21596.291200] rtw_8822ce :03:00.0: timed
out to flush pci tx ring[0]
Nov 24 15:26:05 Zveri2 kernel: [21596.291287] rtw_8822ce :03:00.0: timed
out to flush pci tx ring[1]
Nov 24 15:26:05 Zveri2 kernel: [21596.291365] rtw_8822ce :03:00.0: timed
out to flush pci tx ring[2]
Nov 24 15:26:05 Zveri2 kernel: [21596.291484] rtw_8822ce :03:00.0: timed
out to flush pci tx ring[3]
Nov 24 15:26:05 Zveri2 kernel: [21596.291570] rtw_8822ce :03:00.0: timed
out to flush pci tx ring[5]
Nov 24 15:26:05 Zveri2 kernel: [21596.291651] rtw_8822ce :03:00.0: timed
out to flush pci tx ring[6]
Nov 24 15:26:06 Zveri2 krunner[16146]: [11/24/21, 15:26:06:125] info:
[NETWORK-CONNECTIVITY] Failed to establish a connection after 10 attempt(s).
Nov 24 15:26:07 Zveri2 kernel: [21598.291806] rtw_8822ce :03:00.0: failed
to poll offset=0x5 mask=0x2 value=0x0
Nov 24 15:26:07 Zveri2 kernel: [21598.292047] [ cut here
]
Nov 24 15:26:07 Zveri2 kernel: [21598.292049] failed to read DBI register,
addr=0x0719
Nov 24 15:26:07 Zveri2 kernel: [21598.292082] WARNING: CPU: 2 PID: 17826 at
drivers/net/wireless/realtek/rtw88/pci.c:1310 rtw_dbi_read8.constprop.0+0x
aa/0xc0 [rtw88_pci]
Nov 24 15:26:07 Zveri2 kernel: [21598.292096] Modules linked in:
nf_conntrack_netlink xt_addrtype br_netfilter vboxnetadp(OE) vboxnetflt(OE)
xfrm_user
xfrm_algo
[Kernel-packages] [Bug 1952403] Re: Realtek 8822CE wireless card fails to work after laptop discharge in sleep
Thank you for your reply.
To clarify what "laptop discharge in sleep" means - the day before I
put the laptop to sleep, with around 20% of battery remaining. On the
second day in the morning the laptop was off, fully discharged. When I
plugged it in and turned it on, there was no wireless conectivity, the
load on the CPU was increased with lots of messages like below in
syslog:
```
Dec 8 13:30:10 Zveri2 kernel: [ 57.005777] rtw_8822ce :03:00.0: failed
to poll offset=0x5 mask=0x2 value=0x0
Dec 8 13:30:10 Zveri2 kernel: [ 57.005789] rtw_8822ce :03:00.0: mac
power on failed
Dec 8 13:30:10 Zveri2 kernel: [ 57.005793] rtw_8822ce :03:00.0: failed
to power on mac
Dec 8 13:30:10 Zveri2 kernel: [ 57.005795] rtw_8822ce :03:00.0: leave
idle state failed
Dec 8 13:30:10 Zveri2 kernel: [ 57.005956] rtw_8822ce :03:00.0: failed
to leave ips state
Dec 8 13:30:10 Zveri2 kernel: [ 57.005962] rtw_8822ce :03:00.0: failed
to leave idle state
Dec 8 13:30:10 Zveri2 kernel: [ 57.006050] rtw_8822ce :03:00.0: timed
out to flush pci tx ring[0]
Dec 8 13:30:10 Zveri2 kernel: [ 57.006122] rtw_8822ce :03:00.0: timed
out to flush pci tx ring[1]
Dec 8 13:30:10 Zveri2 kernel: [ 57.006193] rtw_8822ce :03:00.0: timed
out to flush pci tx ring[2]
Dec 8 13:30:10 Zveri2 kernel: [ 57.006264] rtw_8822ce :03:00.0: timed
out to flush pci tx ring[3]
Dec 8 13:30:10 Zveri2 kernel: [ 57.006335] rtw_8822ce :03:00.0: timed
out to flush pci tx ring[5]
Dec 8 13:30:10 Zveri2 kernel: [ 57.006406] rtw_8822ce :03:00.0: timed
out to flush pci tx ring[6]
```
Now I have to add that with `options rtw88_pci disable_msi=1`, sometimes
the wifi starts on boot. It works for around 20-30 minutes, and after
that I get the following in the logs:
```
Dec 8 12:52:53 Zveri2 krunner[23639]: [12/08/21, 12:52:53:939] info: Store:
SET_SYSTEM_IDLE idle
Dec 8 12:53:18 Zveri2 krunner[23954]: Qt: Session management error:
networkIdsList argument is NULL
Dec 8 12:53:35 Zveri2 wpa_supplicant[1074]: wlp3s0: CTRL-EVENT-BEACON-LOSS
Dec 8 12:53:35 Zveri2 kernel: [ 4589.882099] rtw_8822ce :03:00.0: failed
to send h2c command
Dec 8 12:53:35 Zveri2 kernel: [ 4589.885182] rtw_8822ce :03:00.0: failed
to send h2c command
```
> please check /proc/cmdline to see the setting take effect.
```
BOOT_IMAGE=/vmlinuz-5.13.0-22-generic root=/dev/mapper/vgkubuntu-root ro quiet
splash pcie_aspm.policy=performance amd_iommu=off vt.handoff=7
```
> Please confirm the module parameters by
/sys/module/rtw88_pci/parameters/ if they are set properly
```
root@Zveri2:~# cat /sys/module/rtw88_pci/parameters/disable_aspm
Y
root@Zveri2:~# cat /sys/module/rtw88_pci/parameters/disable_msi
Y
```
--
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/1952403
Title:
Realtek 8822CE wireless card fails to work after laptop discharge in
sleep
Status in linux package in Ubuntu:
Confirmed
Bug description:
I own an Asus TUF A15 FA506IV laptop with Ubuntu 21.10. After putting
it to sleep it discharged. Turning it back on the Wireless cards
doesn't work.
This is what I found in the logs that could help:
Nov 24 15:25:56 Zveri2 krunner[16146]: [11/24/21, 15:25:56:311] info: Store:
POWER_RESUMED
Nov 24 15:25:56 Zveri2 krunner[16146]: [11/24/21, 15:25:56:312] info: Store:
SET_SUSPEND_STATUS true
Nov 24 15:25:56 Zveri2 krunner[16146]: [11/24/21, 15:25:56:313] info:
[DESKTOP-SIDE-EFFECT] Update from desktop for keys ["app"]
Nov 24 15:25:56 Zveri2 kernel: [21587.358139] rtw_8822ce :03:00.0: start
vif 80:30:49:cc:98:0f on port 0
Nov 24 15:25:56 Zveri2 charon: 01[KNL] interface wlp3s0 activated
Nov 24 15:25:56 Zveri2 NetworkManager[1059]: [1637760356.4839]
manager: NetworkManager state is now CONNECTED_LOCAL
Nov 24 15:25:56 Zveri2 krunner[16146]: [11/24/21, 15:25:56:489] info:
NetworkStatus: Network check failed {
Nov 24 15:25:56 Zveri2 krunner[16146]: "error": "Failed to fetch"
Nov 24 15:25:56 Zveri2 krunner[16146]: }
Nov 24 15:25:56 Zveri2 krunner[16146]: [11/24/21, 15:25:56:490] info: Network
status check {
Nov 24 15:25:56 Zveri2 krunner[16146]: "elapsed_time_ms": 999784,
Nov 24 15:25:56 Zveri2 krunner[16146]: "navigator_online": false,
Nov 24 15:25:56 Zveri2 krunner[16146]: "api_test": "offline"
Nov 24 15:25:56 Zveri2 krunner[16146]: }
After this I am getting the following trace:
Nov 24 15:26:05 Zveri2 kernel: [21596.291200] rtw_8822ce :03:00.0: timed
out to flush pci tx ring[0]
Nov 24 15:26:05 Zveri2 kernel: [21596.291287] rtw_8822ce :03:00.0: timed
out to flush pci tx ring[1]
Nov 24 15:26:05 Zveri2 kernel: [21596.291365] rtw_8822ce :03:00.0: timed
out to flush pci tx ring[2]
Nov 24 15:26:05 Zveri2 kernel: [21596.291484] rtw_8822ce :03:00.0: timed
out to flush pci tx ring[3]
Nov 24 15:26:05 Zveri2 kernel:
[Kernel-packages] [Bug 1952011] Re: [SRU] linux-firmware: add sof-firmware for adl platforms from sof-firmware-v1.9.2
enable the -proposed, and sudo apt-get update;sudo apt-get install linux-firmware; the linux-firmware-1.187.23 is installed, check the /lib/firmware/intel/sof and sof-tplg folder, we could see the files and links from v1.9.2. Verification done on focal. -- 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/1952011 Title: [SRU] linux-firmware: add sof-firmware for adl platforms from sof- firmware-v1.9.2 Status in HWE Next: New Status in linux-firmware package in Ubuntu: New Status in linux-firmware source package in Focal: Fix Committed Status in linux-firmware source package in Hirsute: In Progress Status in linux-firmware source package in Impish: In Progress Bug description: Because we plan to remove sof-firmware related files from linux-firmware of jammy and replace them with a debian package firmware-sof-signed, so this SRU is not applied to jammy. I will submit another SRU to firmware-sof-signed package later. [Impact] In the Dell oem project, we have many laptops which has sof dmic or sof soundwire audio design, they need to load firmware and topology files specific to ADL, otherwise the audio driver will fail to initialize and the whole audio can't work. [Fix] Integrate the firmware and topology files from sof-firmware-v1.9.2 [Test] Installed the patched linux-firmware and booting the patched kernel, the audio work well, all output and input devices work normally [Where problems could occur] This SRU introduces new firmware and topology files for adl, it has low possibility to introduce regression. If it could, it could possibilily affect the other machines which also need to load firmware and topology files, it could make the audio can't work on those machines, but this possibility is very low, we have tested the SRU on many laptops, no regression found. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1952011/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1953596] 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/1953596 Title: The computer hangs and I have to restart it. Frequently crashes. Status in linux package in Ubuntu: Confirmed Bug description: For no apparent reason my computer hangs frequently and I have to shut it down and restart it. I thought it was Firefox, but even without using the browser it still happens. I have recently updated the ubuntu version and I don't know if it is due to this. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: ubuntu-release-upgrader-core 1:21.10.8 ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 Uname: Linux 5.13.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Wed Dec 8 10:10:24 2021 InstallationDate: Installed on 2020-08-12 (482 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: Upgraded to impish on 2021-11-11 (26 days ago) VarLogDistupgradeTermlog: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953596/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
