[Kernel-packages] [Bug 1949497] Re: [amdgpu] AMD R5 M430 dGPU freezes ([drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout)
Sorry I just noticed you are not using an Ubuntu kernel so we can't track this bug here... unless you find the same issue occurs with the Ubuntu 5.13 kernel. ** Changed in: linux (Ubuntu) Status: Incomplete => New ** Changed in: linux (Ubuntu) Status: New => 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/1949497 Title: [amdgpu] AMD R5 M430 dGPU freezes ([drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout) Status in linux package in Ubuntu: Invalid Bug description: When i try to run anything with my dGPU (Radeon R5 M430), application freezes. But when i set "power_dpm_state" to "battery", or amdgpu.dpm=0 in boot options, it runs fine. i get errors like this: [ 56.647827] [drm] PCIE gen 3 link speeds already enabled [ 56.649064] amdgpu :01:00.0: amdgpu: PCIE GART of 256M enabled (table at 0x00F4). [ 83.707076] [drm] PCIE gen 3 link speeds already enabled [ 83.708350] amdgpu :01:00.0: amdgpu: PCIE GART of 256M enabled (table at 0x00F4). [ 94.813212] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, signaled seq=47, emitted seq=49 [ 94.814219] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process glmark2 pid 4471 thread glmark2:cs0 pid 4473 [ 94.815125] amdgpu :01:00.0: amdgpu: GPU recovery disabled. [ 95.069353] Asynchronous wait on fence :00:02.0:gnome-shell[1648]:3c6 timed out (hint:intel_atomic_commit_ready [i915]) [ 95.069353] Asynchronous wait on fence dma_fence_chain:unbound:1 timed out (hint:submit_notify [i915]) ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: xorg 1:7.7+22ubuntu2 Uname: Linux 5.15.0-051500-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 BootLog: Error: [Errno 13] Erişim engellendi: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Nov 2 19:26:01 2021 DistUpgraded: Fresh install DistroCodename: impish DistroVariant: ubuntu DkmsStatus: v4l2loopback, 0.12.5, 5.13.0-20-generic, x86_64: installed v4l2loopback, 0.12.5, 5.15.0-051500-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Since before I upgraded GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company HD Graphics 620 [103c:81ee] Subsystem: Hewlett-Packard Company Sun XT [Radeon HD 8670A/8670M/8690M / R5 M330 / M430 / Radeon 520 Mobile] [103c:81ee] InstallationDate: Installed on 2021-10-29 (4 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: HP HP Notebook ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=tr_TR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-051500-generic root=UUID=51509311-ce8a-48fb-9ece-8e018d63fe03 ro quiet splash radeon.si_support=0 amdgpu.si_support=1 vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/26/2020 dmi.bios.release: 15.49 dmi.bios.vendor: Insyde dmi.bios.version: F.49 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 81EE dmi.board.vendor: HP dmi.board.version: 62.29 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 62.29 dmi.modalias: dmi:bvnInsyde:bvrF.49:bd06/26/2020:br15.49:efr62.29:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn81EE:rvr62.29:cvnHP:ct10:cvrChassisVersion:skuX9Z24EA#AB8: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Notebook dmi.product.sku: X9Z24EA#AB8 dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1949497/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 397269] Re: HDMI audio cuts out intermittently while normal audio plays fine
This bug has been closed for 12 years. Please open a new one if you have any ongoing issues. -- 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/397269 Title: HDMI audio cuts out intermittently while normal audio plays fine Status in linux package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: Invalid Bug description: Binary package hint: pulseaudio I have my audio set up to play through my laptop speakers and over HDMI to my television. In Jaunty this works fine while in Karmic the HDMI audio will intermittently cut out for a split second a few times a minute. During this time however the audio over the laptop speakers plays just fine. It just seems as if a frame of the HDMI audio gets dropped randomly. The video over the HDMI is perfectly fine, FYI. ProblemType: Bug Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: michael4942 f mixer_applet2 michael7360 F npviewer.bin /dev/snd/pcmC0D0p: michael7360 F...m npviewer.bin /dev/snd/timer: michael7360 F npviewer.bin Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xf6ffc000 irq 21' Mixer name : 'SigmaTel STAC9228' Components : 'HDA:83847616,10280209,00100402' Controls : 28 Simple ctrls : 18 Date: Wed Jul 8 21:20:16 2009 DistroRelease: Ubuntu 9.10 NonfreeKernelModules: nvidia wl Package: pulseaudio 1:0.9.15-4ubuntu1 ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.30-10.12-generic SourcePackage: pulseaudio Uname: Linux 2.6.30-10-generic x86_64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/397269/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926985] Re: linux-version sort: argv and stdin behaviors differ
** Merge proposal unlinked: https://code.launchpad.net/~dannf/+git/maas-preseeds/+merge/411293 -- 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/1926985 Title: linux-version sort: argv and stdin behaviors differ Status in linux-base package in Ubuntu: Fix Released Status in linux-base source package in Bionic: Fix Released Status in linux-base source package in Focal: Fix Released Status in linux-base source package in Groovy: Won't Fix Status in linux-base source package in Hirsute: Fix Released Status in linux-base source package in Impish: Fix Released Status in linux-base package in Debian: New Bug description: [Impact] `linux-version sort` provides 2 ways to sort kernel version strings: users can provide these strings either via the command line or via stdin. Currently these methods give different answers for certain version strings (see Test Case). The stdin behavior is decidedly incorrect, and this is the mode flash-kernel uses. As a real world example, a user with an arm64 u-boot system might end up booting 5.8.0-50-generic instead of the expected 5.8.0-50-generic-64k if both are installed. There maybe additional issues caused by this; for example, I found this with our automation that tests kernels on various arm64 platforms in version increasing order. Only after consulting logs did we realize that 64k kernels were not ever getting booted because the tooling (which uses argv mode) disagreed with the kernel installer (flash-kernel using stdin mode) about which kernel should be the default. It's possible this internal discrepancy can cause other issues due to tools disagreeing about which kernel is the latest, but the flash- kernel example is the only one I'm aware of at this point. [Test Case] Using argv: $ linux-version sort 5.8.0-50-generic 5.8.0-50-generic-64k 5.8.0-50-generic 5.8.0-50-generic-64k Using stdin (incorrect): $ cat versions.txt 5.8.0-50-generic 5.8.0-50-generic-64k $ cat versions.txt | linux-version sort 5.8.0-50-generic-64k 5.8.0-50-generic [Where Problems Could Occur] An obvious place where problems could occur is if someone is relying on rebooting into the kernel that is incorrectly being sorted greatest. For those using only Ubuntu kernel packages, the only case I'm aware of is arm64 generic vs. generic-64k case used in the examples above. The generic-64k flavor is available in >= 20.10, as well as 20.04-hwe. ARM server users - those most likely to want the generic-64k flavor - are very unlikely to be using flash-kernel. The standard for ARM servers is UEFI firmware, which use GRUB and are unaffected by this change. We found this on an HP m400 platform which is the only Ubuntu certified u-boot-based arm64 server. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-base/+bug/1926985/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926985] Re: linux-version sort: argv and stdin behaviors differ
** Merge proposal linked: https://code.launchpad.net/~dannf/+git/maas-preseeds/+merge/411293 -- 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/1926985 Title: linux-version sort: argv and stdin behaviors differ Status in linux-base package in Ubuntu: Fix Released Status in linux-base source package in Bionic: Fix Released Status in linux-base source package in Focal: Fix Released Status in linux-base source package in Groovy: Won't Fix Status in linux-base source package in Hirsute: Fix Released Status in linux-base source package in Impish: Fix Released Status in linux-base package in Debian: New Bug description: [Impact] `linux-version sort` provides 2 ways to sort kernel version strings: users can provide these strings either via the command line or via stdin. Currently these methods give different answers for certain version strings (see Test Case). The stdin behavior is decidedly incorrect, and this is the mode flash-kernel uses. As a real world example, a user with an arm64 u-boot system might end up booting 5.8.0-50-generic instead of the expected 5.8.0-50-generic-64k if both are installed. There maybe additional issues caused by this; for example, I found this with our automation that tests kernels on various arm64 platforms in version increasing order. Only after consulting logs did we realize that 64k kernels were not ever getting booted because the tooling (which uses argv mode) disagreed with the kernel installer (flash-kernel using stdin mode) about which kernel should be the default. It's possible this internal discrepancy can cause other issues due to tools disagreeing about which kernel is the latest, but the flash- kernel example is the only one I'm aware of at this point. [Test Case] Using argv: $ linux-version sort 5.8.0-50-generic 5.8.0-50-generic-64k 5.8.0-50-generic 5.8.0-50-generic-64k Using stdin (incorrect): $ cat versions.txt 5.8.0-50-generic 5.8.0-50-generic-64k $ cat versions.txt | linux-version sort 5.8.0-50-generic-64k 5.8.0-50-generic [Where Problems Could Occur] An obvious place where problems could occur is if someone is relying on rebooting into the kernel that is incorrectly being sorted greatest. For those using only Ubuntu kernel packages, the only case I'm aware of is arm64 generic vs. generic-64k case used in the examples above. The generic-64k flavor is available in >= 20.10, as well as 20.04-hwe. ARM server users - those most likely to want the generic-64k flavor - are very unlikely to be using flash-kernel. The standard for ARM servers is UEFI firmware, which use GRUB and are unaffected by this change. We found this on an HP m400 platform which is the only Ubuntu certified u-boot-based arm64 server. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-base/+bug/1926985/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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
well let's be clear here: none of the workarounds suggested in this thread are fixes, nor are they meant to be, they are workarounds only, to allow some functionality until the actual fix arrives. the actual fix will be a new kernel package release that has the underlying stack corruption bug fixed. that said, it would be great to get an update here from the bug assignee Andrea, or someone on the ubuntu kernel team. we fully realise the bug is in the upstream linux kernel, and has to be fixed there, but an update on how that fix is progressing, or even a pointer to the upstream kernel bug report would be really great 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 Bug description: I installed the Ubuntu 21.10 beta and as soon as I boot I get the kernel panic that I am attaching. I also installed Ubuntu 21.04 and upgraded, as soon as I boot with the 5.13 kernel I get the same problem, disabling the trackpad and trackpoint in the bios the problem disappears. Everything works with the 5.11 kernel. I remain available for further details and sorry for my lack of experience. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-16-generic 5.13.0-16.16 ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pietro 1810 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Sep 30 10:26:10 2021 InstallationDate: Installed on 2021-09-29 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: LENOVO 20TA0033IX ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-16-generic root=UUID=b5ea9465-4cd9-408b-8e30-458acf90181b ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.13.0-16-generic N/A linux-backports-modules-5.13.0-16-generic N/A linux-firmware 1.201 SourcePackage: linux UpgradeStatus: Upgraded to impish on 2021-09-29 (0 days ago) dmi.bios.date: 09/02/2021 dmi.bios.release: 1.43 dmi.bios.vendor: LENOVO dmi.bios.version: R1EET43W(1.43 ) dmi.board.asset.tag: Not Available dmi.board.name: 20TA0033IX dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.43 dmi.modalias: dmi:bvnLENOVO:bvrR1EET43W(1.43):bd09/02/2021:br1.43:efr1.43:svnLENOVO:pn20TA0033IX:pvrThinkPadE14Gen2:skuLENOVO_MT_20TA_BU_Think_FM_ThinkPadE14Gen2:rvnLENOVO:rn20TA0033IX:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad E14 Gen 2 dmi.product.name: 20TA0033IX dmi.product.sku: LENOVO_MT_20TA_BU_Think_FM_ThinkPad E14 Gen 2 dmi.product.version: ThinkPad E14 Gen 2 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945590/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1945590] Re: Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled
Touchpad is not fully functionalwith @Mark Harfouche's method. You cannot scroll with two fingers or two finger tap to right click. Not a fix! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1945590 Title: Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled Status in linux package in Ubuntu: Confirmed Status in linux source package in Impish: Confirmed Bug description: I installed the Ubuntu 21.10 beta and as soon as I boot I get the kernel panic that I am attaching. I also installed Ubuntu 21.04 and upgraded, as soon as I boot with the 5.13 kernel I get the same problem, disabling the trackpad and trackpoint in the bios the problem disappears. Everything works with the 5.11 kernel. I remain available for further details and sorry for my lack of experience. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-16-generic 5.13.0-16.16 ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pietro 1810 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Sep 30 10:26:10 2021 InstallationDate: Installed on 2021-09-29 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: LENOVO 20TA0033IX ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-16-generic root=UUID=b5ea9465-4cd9-408b-8e30-458acf90181b ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.13.0-16-generic N/A linux-backports-modules-5.13.0-16-generic N/A linux-firmware 1.201 SourcePackage: linux UpgradeStatus: Upgraded to impish on 2021-09-29 (0 days ago) dmi.bios.date: 09/02/2021 dmi.bios.release: 1.43 dmi.bios.vendor: LENOVO dmi.bios.version: R1EET43W(1.43 ) dmi.board.asset.tag: Not Available dmi.board.name: 20TA0033IX dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.43 dmi.modalias: dmi:bvnLENOVO:bvrR1EET43W(1.43):bd09/02/2021:br1.43:efr1.43:svnLENOVO:pn20TA0033IX:pvrThinkPadE14Gen2:skuLENOVO_MT_20TA_BU_Think_FM_ThinkPadE14Gen2:rvnLENOVO:rn20TA0033IX:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad E14 Gen 2 dmi.product.name: 20TA0033IX dmi.product.sku: LENOVO_MT_20TA_BU_Think_FM_ThinkPad E14 Gen 2 dmi.product.version: ThinkPad E14 Gen 2 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945590/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1948025] Autopkgtest regression report (nvidia-graphics-drivers-470-server/470.82.01-0ubuntu0.21.04.1)
All autopkgtests for the newly accepted nvidia-graphics-drivers-470-server (470.82.01-0ubuntu0.21.04.1) for hirsute have finished running. The following regressions have been reported in tests triggered by the package: pyopencl/2021.1.2-1build1 (armhf) 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#nvidia-graphics-drivers-470-server [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 nvidia-graphics-drivers-460-server in Ubuntu. https://bugs.launchpad.net/bugs/1948025 Title: Update the NVIDIA drivers October 2021 Status in fabric-manager-450 package in Ubuntu: Fix Released Status in fabric-manager-460 package in Ubuntu: Fix Released Status in libnvidia-nscq-450 package in Ubuntu: Fix Released Status in libnvidia-nscq-460 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-418-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-450-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-460-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-470 package in Ubuntu: In Progress Status in nvidia-graphics-drivers-470-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-495 package in Ubuntu: In Progress Status in nvidia-graphics-drivers-418-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-470 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-495 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-470 source package in Focal: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-495 source package in Focal: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-470 source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-495 source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Impish: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Impish: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Impish: Fix Committed Status in nvidia-graphics-drivers-470 source package in Impish: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Impish: Fix Committed Bug description: Update the NVIDIA series and introduce the new 495 series in Bionic, Focal, Hirsute, and Impish. [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our users have access to these improvements. See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. nVidia maintainers team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned system level tests are attached to this bug. [Discussion] [Changelog] == 470 == * New upstream release (LP: #1948025): - Fixed a bug that can cause a kernel crash in SLI Mosaic configurations. - Added support for the EGL_NV_robustness_video_memory_purge. == 495 == * Initial release (LP: #1948025). == 460-server == * New upstream release (LP: #1948025). == 450-server == * New upstream release (LP: #1948025). * debian/templates/dkms_nvidia.conf.in:
[Kernel-packages] [Bug 1949532] Re: ubuntu_ltp_controllers tests failing on Impish
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1942113 Here is a discussion about recent regressions in systemd tests where its stated that the cgroups are set up in "unified" (v2) mode in 248.3-1ubuntu5 systemd package. 248.3-1ubuntu7 became the release package on 2021-09-27 which was around the start of the cycle that we started seeing this issues (did we see this before then?), which means that it could very likely have been this upgrade that caused it. Even if earlier packages were in updates I am pretty sure that the machine needs to be restarted for the systemd changes to take affect, which I am pretty sure our test machines don't restart after updating during deployment. So it would make sense that we are seeing the errors correlating with the new systemd package hitting release. I also re-ran tests on previous kernels which didnt have these issues and they are now reporting all the errors, which also points to this being a problem with the systemd package upgrade. In the meantime, it seems that these tests are broken and we should just hint the whole ubuntu_ltp_controllers test suite. -- 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/1949532 Title: ubuntu_ltp_controllers tests failing on Impish Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Bug description: Almost half of the ubuntu_ltp_controllers tests are failing due to the general pattern 'cgroup_name already mounted or mount point busy' causing the tests to fail. e.g. mount: /dev/cgroup: ltp_cgroup already mounted or mount point busy. cgroup_fj_function2_memory 1 TBROK: mount -t cgroup -o memory ltp_cgroup /dev/cgroup failed From investigation it seems there could be an issue with the transition to cgroup-v2. There have been rumors on the ltp mailing list that one of these days the tests could break due to the transition. Switching to cgroup-v2, likely due to a systemd update, could cause these tests to break due to different mount and cgroup hierarchy semantics. I could only reproduce a subset of the new failures we are seeing, but after setting systemd.unified_cgroup_hierarchy=0 on the kernel command line which sets cgroup back to v1, a lot of the failures I could produce went away. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1949532/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1784152] Re: i2c_hid_get_input floods system logs
As Paul D. just described I am also seeing this on my Razer Blade Pro 17 2021. I'm assuming this and the 15 inch probably use the same touchpad/driver. I've seen this on Kubuntu 21.10 and with kernel 5.13. Will try with some newer kernels too but 5.15 completely broke suspend, so will need to troubleshoot that first before I can tell if it fixes the touchpad issue after suspend. Installing xserver-xorg-input-synaptics also made no difference. ELAN0406:00 04F3:30A6 Touchpad -- 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/1784152 Title: i2c_hid_get_input floods system logs Status in linux package in Ubuntu: Fix Released Bug description: Ubuntu 4.15.0-29.31-generic 4.15.18 After upgrading to kernel version 4.15.0-29 from 4.15.0-23, the system logs are flooded whenever I move the cursor with my touchpad. It looks like this: i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535) i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535) i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535) i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535) etc... This problem did not occur on the previous kernel version so there must have been a change to the "drivers/hid/i2c-hid/i2c-hid.c" file. This seems to be fixed in a recent commit here: https://github.com/torvalds/linux/commit/ef6eaf27274c0351f7059163918f3795da13199c I am currently running the older kernel version but would still like to be up to date without this flooding happening. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784152/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1932329] Re: Benchmark if we can compress kernel modules
This bug was fixed in the package initramfs-tools - 0.140ubuntu8 --- initramfs-tools (0.140ubuntu8) jammy; urgency=medium * Cherry-pick merge request !26 to support xz compressed firmware. Uncompressed firmware is preffered, with a fallback to use compressed firmware files. LP: #1942260 * Cherry-pick merge request !51 to decompress compressed kernel modules for boot speed performance. LP: #1932329 * Cherry-pick partially merge request !50 to fix ftbfs with new shellcheck. * Fix shellcheck issues in ubuntu patches. -- Dimitri John Ledkov Tue, 19 Oct 2021 11:49:38 +0100 ** Changed in: initramfs-tools (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1932329 Title: Benchmark if we can compress kernel modules Status in initramfs-tools package in Ubuntu: Fix Released Status in linux package in Ubuntu: In Progress Bug description: Symbol: MODULE_COMPRESS_ZSTD [=n] Type : bool = Impacts to measure and observe = == Disk space == * Inspect linux-modules-* and linux-modules-extra* deb package Installed-Size and Download-Size changes, i.e. $ apt show linux-modules-5.8.0-53-generic linux-modules- extra-5.8.0-53-generic | grep -e Package: -e Size: Package: linux-modules-5.8.0-53-generic Installed-Size: 81.5 MB Download-Size: 15.5 MB Package: linux-modules-extra-5.8.0-53-generic Installed-Size: 215 MB Download-Size: 41.5 MB In theory, there should not be a significant change in the Download- size. It is desired that there is a significant reduction in Installed-Size. Modules take up about 300MB and normally one has upto three kernel version installed, resulting in about of 1GB of disk space that one constantly pays for. == Boot Speed == In theory, boot speed may either improve or regress. It depends if disk IO is slower than decompression speed, meaning loading compressed modules is faster. Also one has to observe the changes in the initrd size. zstd(zstd) compression may result in slight growth, which shouldn't impact boot speed too much. = Outcomes = If installed size savings can be achieved without regressing bootspeed we should enable CONFIG_MODULE_COMPRESS_ZSTD=y by default. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1932329/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1942260] Re: compress firmware in /lib/firmware
This bug was fixed in the package initramfs-tools - 0.140ubuntu8 --- initramfs-tools (0.140ubuntu8) jammy; urgency=medium * Cherry-pick merge request !26 to support xz compressed firmware. Uncompressed firmware is preffered, with a fallback to use compressed firmware files. LP: #1942260 * Cherry-pick merge request !51 to decompress compressed kernel modules for boot speed performance. LP: #1932329 * Cherry-pick partially merge request !50 to fix ftbfs with new shellcheck. * Fix shellcheck issues in ubuntu patches. -- Dimitri John Ledkov Tue, 19 Oct 2021 11:49:38 +0100 ** Changed in: initramfs-tools (Ubuntu) Status: New => Fix Released -- 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/1942260 Title: compress firmware in /lib/firmware Status in initramfs-tools package in Ubuntu: Fix Released Status in linux-firmware package in Ubuntu: New Status in linux-firmware-raspi2 package in Ubuntu: New Bug description: Some facts: - The linux kernel has supported loading xz compressed firmware since 5.3 - The size of /lib/firmware in impish is ~650Mb (and growing) - The compressed size of firmware could be ~230Mb It would be nice to install compressed firmware to save space. Here are the plans from the Fedora project: https://fedoraproject.org/wiki/Changes/CompressKernelFirmware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1942260/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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-oem-5.14/5.14.0.1006.6)
All autopkgtests for the newly accepted linux-meta-oem-5.14 (5.14.0.1006.6) for focal have finished running. The following regressions have been reported in tests triggered by the package: virtualbox-hwe/6.1.26-dfsg-3~ubuntu1.20.04.2 (amd64) virtualbox/6.1.26-dfsg-3~ubuntu1.20.04.2 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#linux-meta-oem-5.14 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Confirmed Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Invalid Status in linux-azure-edge source package in Precise: Invalid Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Invalid Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Confirmed Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packing resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926985] Re: linux-version sort: argv and stdin behaviors differ
This bug was fixed in the package linux-base - 4.5ubuntu5.4 --- linux-base (4.5ubuntu5.4) hirsute; urgency=medium * linux-version: Fix sorting of versions provided via stdin to match the output when provided via argv (LP: #1926985). -- dann frazier Wed, 07 Jul 2021 14:13:01 -0600 ** Changed in: linux-base (Ubuntu Hirsute) Status: Fix Committed => Fix Released -- 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/1926985 Title: linux-version sort: argv and stdin behaviors differ Status in linux-base package in Ubuntu: Fix Released Status in linux-base source package in Bionic: Fix Released Status in linux-base source package in Focal: Fix Released Status in linux-base source package in Groovy: Won't Fix Status in linux-base source package in Hirsute: Fix Released Status in linux-base source package in Impish: Fix Released Status in linux-base package in Debian: New Bug description: [Impact] `linux-version sort` provides 2 ways to sort kernel version strings: users can provide these strings either via the command line or via stdin. Currently these methods give different answers for certain version strings (see Test Case). The stdin behavior is decidedly incorrect, and this is the mode flash-kernel uses. As a real world example, a user with an arm64 u-boot system might end up booting 5.8.0-50-generic instead of the expected 5.8.0-50-generic-64k if both are installed. There maybe additional issues caused by this; for example, I found this with our automation that tests kernels on various arm64 platforms in version increasing order. Only after consulting logs did we realize that 64k kernels were not ever getting booted because the tooling (which uses argv mode) disagreed with the kernel installer (flash-kernel using stdin mode) about which kernel should be the default. It's possible this internal discrepancy can cause other issues due to tools disagreeing about which kernel is the latest, but the flash- kernel example is the only one I'm aware of at this point. [Test Case] Using argv: $ linux-version sort 5.8.0-50-generic 5.8.0-50-generic-64k 5.8.0-50-generic 5.8.0-50-generic-64k Using stdin (incorrect): $ cat versions.txt 5.8.0-50-generic 5.8.0-50-generic-64k $ cat versions.txt | linux-version sort 5.8.0-50-generic-64k 5.8.0-50-generic [Where Problems Could Occur] An obvious place where problems could occur is if someone is relying on rebooting into the kernel that is incorrectly being sorted greatest. For those using only Ubuntu kernel packages, the only case I'm aware of is arm64 generic vs. generic-64k case used in the examples above. The generic-64k flavor is available in >= 20.10, as well as 20.04-hwe. ARM server users - those most likely to want the generic-64k flavor - are very unlikely to be using flash-kernel. The standard for ARM servers is UEFI firmware, which use GRUB and are unaffected by this change. We found this on an HP m400 platform which is the only Ubuntu certified u-boot-based arm64 server. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-base/+bug/1926985/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926985] Re: linux-version sort: argv and stdin behaviors differ
This bug was fixed in the package linux-base - 4.5ubuntu1.7 --- linux-base (4.5ubuntu1.7) bionic; urgency=medium * linux-version: Fix sorting of versions provided via stdin to match the output when provided via argv (LP: #1926985). -- dann frazier Wed, 07 Jul 2021 14:34:55 -0600 -- 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/1926985 Title: linux-version sort: argv and stdin behaviors differ Status in linux-base package in Ubuntu: Fix Released Status in linux-base source package in Bionic: Fix Released Status in linux-base source package in Focal: Fix Released Status in linux-base source package in Groovy: Won't Fix Status in linux-base source package in Hirsute: Fix Released Status in linux-base source package in Impish: Fix Released Status in linux-base package in Debian: New Bug description: [Impact] `linux-version sort` provides 2 ways to sort kernel version strings: users can provide these strings either via the command line or via stdin. Currently these methods give different answers for certain version strings (see Test Case). The stdin behavior is decidedly incorrect, and this is the mode flash-kernel uses. As a real world example, a user with an arm64 u-boot system might end up booting 5.8.0-50-generic instead of the expected 5.8.0-50-generic-64k if both are installed. There maybe additional issues caused by this; for example, I found this with our automation that tests kernels on various arm64 platforms in version increasing order. Only after consulting logs did we realize that 64k kernels were not ever getting booted because the tooling (which uses argv mode) disagreed with the kernel installer (flash-kernel using stdin mode) about which kernel should be the default. It's possible this internal discrepancy can cause other issues due to tools disagreeing about which kernel is the latest, but the flash- kernel example is the only one I'm aware of at this point. [Test Case] Using argv: $ linux-version sort 5.8.0-50-generic 5.8.0-50-generic-64k 5.8.0-50-generic 5.8.0-50-generic-64k Using stdin (incorrect): $ cat versions.txt 5.8.0-50-generic 5.8.0-50-generic-64k $ cat versions.txt | linux-version sort 5.8.0-50-generic-64k 5.8.0-50-generic [Where Problems Could Occur] An obvious place where problems could occur is if someone is relying on rebooting into the kernel that is incorrectly being sorted greatest. For those using only Ubuntu kernel packages, the only case I'm aware of is arm64 generic vs. generic-64k case used in the examples above. The generic-64k flavor is available in >= 20.10, as well as 20.04-hwe. ARM server users - those most likely to want the generic-64k flavor - are very unlikely to be using flash-kernel. The standard for ARM servers is UEFI firmware, which use GRUB and are unaffected by this change. We found this on an HP m400 platform which is the only Ubuntu certified u-boot-based arm64 server. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-base/+bug/1926985/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926985] Update Released
The verification of the Stable Release Update for linux-base has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-base in Ubuntu. https://bugs.launchpad.net/bugs/1926985 Title: linux-version sort: argv and stdin behaviors differ Status in linux-base package in Ubuntu: Fix Released Status in linux-base source package in Bionic: Fix Released Status in linux-base source package in Focal: Fix Released Status in linux-base source package in Groovy: Won't Fix Status in linux-base source package in Hirsute: Fix Released Status in linux-base source package in Impish: Fix Released Status in linux-base package in Debian: New Bug description: [Impact] `linux-version sort` provides 2 ways to sort kernel version strings: users can provide these strings either via the command line or via stdin. Currently these methods give different answers for certain version strings (see Test Case). The stdin behavior is decidedly incorrect, and this is the mode flash-kernel uses. As a real world example, a user with an arm64 u-boot system might end up booting 5.8.0-50-generic instead of the expected 5.8.0-50-generic-64k if both are installed. There maybe additional issues caused by this; for example, I found this with our automation that tests kernels on various arm64 platforms in version increasing order. Only after consulting logs did we realize that 64k kernels were not ever getting booted because the tooling (which uses argv mode) disagreed with the kernel installer (flash-kernel using stdin mode) about which kernel should be the default. It's possible this internal discrepancy can cause other issues due to tools disagreeing about which kernel is the latest, but the flash- kernel example is the only one I'm aware of at this point. [Test Case] Using argv: $ linux-version sort 5.8.0-50-generic 5.8.0-50-generic-64k 5.8.0-50-generic 5.8.0-50-generic-64k Using stdin (incorrect): $ cat versions.txt 5.8.0-50-generic 5.8.0-50-generic-64k $ cat versions.txt | linux-version sort 5.8.0-50-generic-64k 5.8.0-50-generic [Where Problems Could Occur] An obvious place where problems could occur is if someone is relying on rebooting into the kernel that is incorrectly being sorted greatest. For those using only Ubuntu kernel packages, the only case I'm aware of is arm64 generic vs. generic-64k case used in the examples above. The generic-64k flavor is available in >= 20.10, as well as 20.04-hwe. ARM server users - those most likely to want the generic-64k flavor - are very unlikely to be using flash-kernel. The standard for ARM servers is UEFI firmware, which use GRUB and are unaffected by this change. We found this on an HP m400 platform which is the only Ubuntu certified u-boot-based arm64 server. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-base/+bug/1926985/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926985] Re: linux-version sort: argv and stdin behaviors differ
This bug was fixed in the package linux-base - 4.5ubuntu3.7 --- linux-base (4.5ubuntu3.7) focal; urgency=medium * linux-version: Fix sorting of versions provided via stdin to match the output when provided via argv (LP: #1926985). -- dann frazier Wed, 07 Jul 2021 14:20:10 -0600 ** Changed in: linux-base (Ubuntu Focal) Status: Fix Committed => Fix Released ** Changed in: linux-base (Ubuntu Bionic) Status: Fix Committed => Fix Released -- 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/1926985 Title: linux-version sort: argv and stdin behaviors differ Status in linux-base package in Ubuntu: Fix Released Status in linux-base source package in Bionic: Fix Released Status in linux-base source package in Focal: Fix Released Status in linux-base source package in Groovy: Won't Fix Status in linux-base source package in Hirsute: Fix Released Status in linux-base source package in Impish: Fix Released Status in linux-base package in Debian: New Bug description: [Impact] `linux-version sort` provides 2 ways to sort kernel version strings: users can provide these strings either via the command line or via stdin. Currently these methods give different answers for certain version strings (see Test Case). The stdin behavior is decidedly incorrect, and this is the mode flash-kernel uses. As a real world example, a user with an arm64 u-boot system might end up booting 5.8.0-50-generic instead of the expected 5.8.0-50-generic-64k if both are installed. There maybe additional issues caused by this; for example, I found this with our automation that tests kernels on various arm64 platforms in version increasing order. Only after consulting logs did we realize that 64k kernels were not ever getting booted because the tooling (which uses argv mode) disagreed with the kernel installer (flash-kernel using stdin mode) about which kernel should be the default. It's possible this internal discrepancy can cause other issues due to tools disagreeing about which kernel is the latest, but the flash- kernel example is the only one I'm aware of at this point. [Test Case] Using argv: $ linux-version sort 5.8.0-50-generic 5.8.0-50-generic-64k 5.8.0-50-generic 5.8.0-50-generic-64k Using stdin (incorrect): $ cat versions.txt 5.8.0-50-generic 5.8.0-50-generic-64k $ cat versions.txt | linux-version sort 5.8.0-50-generic-64k 5.8.0-50-generic [Where Problems Could Occur] An obvious place where problems could occur is if someone is relying on rebooting into the kernel that is incorrectly being sorted greatest. For those using only Ubuntu kernel packages, the only case I'm aware of is arm64 generic vs. generic-64k case used in the examples above. The generic-64k flavor is available in >= 20.10, as well as 20.04-hwe. ARM server users - those most likely to want the generic-64k flavor - are very unlikely to be using flash-kernel. The standard for ARM servers is UEFI firmware, which use GRUB and are unaffected by this change. We found this on an HP m400 platform which is the only Ubuntu certified u-boot-based arm64 server. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-base/+bug/1926985/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926985] Re: linux-version sort: argv and stdin behaviors differ
** Changed in: linux-base (Ubuntu Groovy) Status: Fix Committed => Won't Fix -- 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/1926985 Title: linux-version sort: argv and stdin behaviors differ Status in linux-base package in Ubuntu: Fix Released Status in linux-base source package in Bionic: Fix Released Status in linux-base source package in Focal: Fix Released Status in linux-base source package in Groovy: Won't Fix Status in linux-base source package in Hirsute: Fix Released Status in linux-base source package in Impish: Fix Released Status in linux-base package in Debian: New Bug description: [Impact] `linux-version sort` provides 2 ways to sort kernel version strings: users can provide these strings either via the command line or via stdin. Currently these methods give different answers for certain version strings (see Test Case). The stdin behavior is decidedly incorrect, and this is the mode flash-kernel uses. As a real world example, a user with an arm64 u-boot system might end up booting 5.8.0-50-generic instead of the expected 5.8.0-50-generic-64k if both are installed. There maybe additional issues caused by this; for example, I found this with our automation that tests kernels on various arm64 platforms in version increasing order. Only after consulting logs did we realize that 64k kernels were not ever getting booted because the tooling (which uses argv mode) disagreed with the kernel installer (flash-kernel using stdin mode) about which kernel should be the default. It's possible this internal discrepancy can cause other issues due to tools disagreeing about which kernel is the latest, but the flash- kernel example is the only one I'm aware of at this point. [Test Case] Using argv: $ linux-version sort 5.8.0-50-generic 5.8.0-50-generic-64k 5.8.0-50-generic 5.8.0-50-generic-64k Using stdin (incorrect): $ cat versions.txt 5.8.0-50-generic 5.8.0-50-generic-64k $ cat versions.txt | linux-version sort 5.8.0-50-generic-64k 5.8.0-50-generic [Where Problems Could Occur] An obvious place where problems could occur is if someone is relying on rebooting into the kernel that is incorrectly being sorted greatest. For those using only Ubuntu kernel packages, the only case I'm aware of is arm64 generic vs. generic-64k case used in the examples above. The generic-64k flavor is available in >= 20.10, as well as 20.04-hwe. ARM server users - those most likely to want the generic-64k flavor - are very unlikely to be using flash-kernel. The standard for ARM servers is UEFI firmware, which use GRUB and are unaffected by this change. We found this on an HP m400 platform which is the only Ubuntu certified u-boot-based arm64 server. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-base/+bug/1926985/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1853977] Re: nvidia-340 dpkg: error: version '-' has bad syntax: revision number is empty
Users are still finding this issue. In #ubuntu, 3 November 2021: https://justpaste.it/97emx Thanks ** Also affects: nvidia-graphics-drivers-340 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1853977 Title: nvidia-340 dpkg: error: version '-' has bad syntax: revision number is empty Status in linux package in Ubuntu: Confirmed Status in nvidia-graphics-drivers package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-340 package in Ubuntu: New Bug description: Hello, When installing `nvidia-340` there is an error is the postinst script: philippe@pv-desktop:~$ sudo apt install --reinstall nvidia-340 Reading package lists... Done Building dependency tree Reading state information... Done 0 to upgrade, 0 to newly install, 1 reinstalled, 0 to remove and 7 not to upgrade. Need to get 0 B/51.9 MB of archives. After this operation, 0 B of additional disk space will be used. (Reading database ... 309892 files and directories currently installed.) Preparing to unpack .../nvidia-340_340.107-0ubuntu0.18.04.4_amd64.deb ... Stopping nvidia-persistenced nvidia-persistenced: no process found Done. (snip) Setting up nvidia-340 (340.107-0ubuntu0.18.04.4) ... dpkg: error: version '-' has bad syntax: revision number is empty dpkg: error: version '-' has bad syntax: revision number is empty update-initramfs: deferring update (trigger activated) INFO:Enable nvidia-340 DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/put_your_quirks_here DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/lenovo_thinkpad DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/dell_latitude Loading new nvidia-340-340.107 DKMS files... Building for 4.15.0-70-generic Building for architecture x86_64 Building initial module for 4.15.0-70-generic Done. The comment at https://askubuntu.com/questions/969352/uninstalling- and-then-reinstalling-nvidia-384-kills-colord tells us that /var/lib/dpkg/info/nvidia-340.postinst has a typo: replace $KERNELS with $CURRENT_KERNEL then `dpkg-reconfigure nvidia-340` works as expected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853977/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1949640] [NEW] Hirsute update: upstream stable patchset 2021-11-03
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2021-11-03 Ported from the following upstream stable releases: v5.10.70, v5.14.9 from git://git.kernel.org/ ocfs2: drop acl cache for directories too mm: fix uninitialized use in overcommit_policy_handler usb: gadget: r8a66597: fix a loop in set_feature() usb: dwc2: gadget: Fix ISOC flow for BDMA and Slave usb: dwc2: gadget: Fix ISOC transfer complete handling for DDMA usb: musb: tusb6010: uninitialized data in tusb_fifo_write_unaligned() cifs: fix incorrect check for null pointer in header_assemble xen/x86: fix PV trap handling on secondary processors usb-storage: Add quirk for ScanLogic SL11R-IDE older than 2.6c USB: serial: cp210x: add ID for GW Instek GDM-834x Digital Multimeter USB: cdc-acm: fix minor-number release Revert "USB: bcma: Add a check for devm_gpiod_get" binder: make sure fd closes complete staging: greybus: uart: fix tty use after free Re-enable UAS for LaCie Rugged USB3-FW with fk quirk usb: dwc3: core: balance phy init and exit USB: serial: mos7840: remove duplicated 0xac24 device ID USB: serial: option: add Telit LN920 compositions USB: serial: option: remove duplicate USB device ID USB: serial: option: add device id for Foxconn T99W265 mcb: fix error handling in mcb_alloc_bus() erofs: fix up erofs_lookup tracepoint btrfs: prevent __btrfs_dump_space_info() to underflow its free space serial: 8250: 8250_omap: Fix RX_LVL register offset serial: mvebu-uart: fix driver's tx_empty callback scsi: sd_zbc: Ensure buffer size is aligned to SECTOR_SIZE drm/amd/pm: Update intermediate power state for SI net: hso: fix muxed tty registration comedi: Fix memory leak in compat_insnlist() afs: Fix incorrect triggering of sillyrename on 3rd-party invalidation afs: Fix updating of i_blocks on file/dir extension platform/x86/intel: punit_ipc: Drop wrong use of ACPI_PTR() enetc: Fix illegal access when reading affinity_hint enetc: Fix uninitialized struct dim_sample field usage bnxt_en: Fix TX timeout when TX ring size is set to the smallest net: hns3: fix change RSS 'hfunc' ineffective issue net: hns3: check queue id range before using net/smc: add missing error check in smc_clc_prfx_set() net/smc: fix 'workqueue leaked lock' in smc_conn_abort_work net: dsa: don't allocate the slave_mii_bus using devres net: dsa: realtek: register the MDIO bus under devres kselftest/arm64: signal: Add SVE to the set of features we can check for kselftest/arm64: signal: Skip tests if required features are missing s390/qeth: fix NULL deref in qeth_clear_working_pool_list() gpio: uniphier: Fix void functions to remove return value qed: rdma - don't wait for resources under hw error recovery flow net/mlx4_en: Don't allow aRFS for encapsulated packets atlantic: Fix issue in the pm resume flow. scsi: iscsi: Adjust iface sysfs attr detection scsi: target: Fix the pgr/alua_support_store functions tty: synclink_gt, drop unneeded forward declarations tty: synclink_gt: rename a conflicting function name fpga: machxo2-spi: Return an error on failure fpga: machxo2-spi: Fix missing error code in machxo2_write_complete() nvme-tcp: fix incorrect h2cdata pdu offset accounting treewide: Change list_sort to use const pointers nvme: keep ctrl->namespaces ordered thermal/core: Potential buffer overflow in thermal_build_list_of_policies() cifs: fix a sign extension bug scsi: qla2xxx: Restore initiator in dual mode scsi: lpfc: Use correct scnprintf() limit irqchip/goldfish-pic: Select GENERIC_IRQ_CHIP to fix build irqchip/gic-v3-its: Fix potential VPE leak on error md: fix a lock order reversal in md_alloc x86/asm: Add a missing __iomem annotation in enqcmds() x86/asm: Fix SETZ size enqcmds() build failure io_uring: put provided buffer meta data under memcg accounting blktrace: Fix uaf in blk_trace access after removing by sysfs net: phylink: Update SFP selected interface on advertising changes net: macb: fix use after free on rmmod net: stmmac: allow CSR clock of 300MHz blk-mq: avoid to iterate over stale request m68k: Double cast io functions to unsigned long ipv6: delay fib6_sernum increase in fib6_add cpufreq: intel_pstate: Override parameters if HWP forced by BIOS bpf: Add oversize check before call kvcalloc() xen/balloon: use a kernel thread instead a workqueue nvme-multipath: fix ANA state updates when a namespace is not present nvme-rdma: destroy cm id before destroy qp to avoid use after free sparc32: page align size in arch_dma_alloc amd/display: downgrade validation failure log level block:
[Kernel-packages] [Bug 1948025] Please test proposed package
Hello Alberto, or anyone else affected, Accepted nvidia-graphics-drivers-470-server into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/nvidia-graphics- drivers-470-server/470.82.01-0ubuntu0.18.04.1 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- bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-bionic. 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 nvidia-graphics-drivers-460-server in Ubuntu. https://bugs.launchpad.net/bugs/1948025 Title: Update the NVIDIA drivers October 2021 Status in fabric-manager-450 package in Ubuntu: Fix Released Status in fabric-manager-460 package in Ubuntu: Fix Released Status in libnvidia-nscq-450 package in Ubuntu: Fix Released Status in libnvidia-nscq-460 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-418-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-450-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-460-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-470 package in Ubuntu: In Progress Status in nvidia-graphics-drivers-470-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-495 package in Ubuntu: In Progress Status in nvidia-graphics-drivers-418-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-470 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-495 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-470 source package in Focal: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-495 source package in Focal: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-470 source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-495 source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Impish: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Impish: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Impish: Fix Committed Status in nvidia-graphics-drivers-470 source package in Impish: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Impish: Fix Committed Bug description: Update the NVIDIA series and introduce the new 495 series in Bionic, Focal, Hirsute, and Impish. [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our users have access to these improvements. See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. nVidia maintainers team members will not
[Kernel-packages] [Bug 1948025] Please test proposed package
Hello Alberto, or anyone else affected, Accepted nvidia-graphics-drivers-470-server into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/nvidia-graphics- drivers-470-server/470.82.01-0ubuntu0.20.04.1 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- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. 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: nvidia-graphics-drivers-470-server (Ubuntu Bionic) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460-server in Ubuntu. https://bugs.launchpad.net/bugs/1948025 Title: Update the NVIDIA drivers October 2021 Status in fabric-manager-450 package in Ubuntu: Fix Released Status in fabric-manager-460 package in Ubuntu: Fix Released Status in libnvidia-nscq-450 package in Ubuntu: Fix Released Status in libnvidia-nscq-460 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-418-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-450-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-460-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-470 package in Ubuntu: In Progress Status in nvidia-graphics-drivers-470-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-495 package in Ubuntu: In Progress Status in nvidia-graphics-drivers-418-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-470 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-495 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-470 source package in Focal: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-495 source package in Focal: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-470 source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-495 source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Impish: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Impish: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Impish: Fix Committed Status in nvidia-graphics-drivers-470 source package in Impish: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Impish: Fix Committed Bug description: Update the NVIDIA series and introduce the new 495 series in Bionic, Focal, Hirsute, and Impish. [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our users have access to these improvements. See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the artifacts
[Kernel-packages] [Bug 1948025] Please test proposed package
Hello Alberto, or anyone else affected, Accepted nvidia-graphics-drivers-470-server into hirsute-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/nvidia-graphics- drivers-470-server/470.82.01-0ubuntu0.21.04.1 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: nvidia-graphics-drivers-470-server (Ubuntu Focal) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460-server in Ubuntu. https://bugs.launchpad.net/bugs/1948025 Title: Update the NVIDIA drivers October 2021 Status in fabric-manager-450 package in Ubuntu: Fix Released Status in fabric-manager-460 package in Ubuntu: Fix Released Status in libnvidia-nscq-450 package in Ubuntu: Fix Released Status in libnvidia-nscq-460 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-418-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-450-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-460-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-470 package in Ubuntu: In Progress Status in nvidia-graphics-drivers-470-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-495 package in Ubuntu: In Progress Status in nvidia-graphics-drivers-418-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-470 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-495 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-470 source package in Focal: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-495 source package in Focal: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-470 source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-495 source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Impish: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Impish: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Impish: Fix Committed Status in nvidia-graphics-drivers-470 source package in Impish: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Impish: Fix Committed Bug description: Update the NVIDIA series and introduce the new 495 series in Bionic, Focal, Hirsute, and Impish. [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our users have access to these improvements. See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the
[Kernel-packages] [Bug 1948025] Re: Update the NVIDIA drivers October 2021
Hello Alberto, or anyone else affected, Accepted nvidia-graphics-drivers-470-server into impish-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/nvidia-graphics- drivers-470-server/470.82.01-0ubuntu0.21.10.1 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. ** Changed in: nvidia-graphics-drivers-470-server (Ubuntu Impish) Status: New => Fix Committed ** Changed in: nvidia-graphics-drivers-470-server (Ubuntu Hirsute) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460-server in Ubuntu. https://bugs.launchpad.net/bugs/1948025 Title: Update the NVIDIA drivers October 2021 Status in fabric-manager-450 package in Ubuntu: Fix Released Status in fabric-manager-460 package in Ubuntu: Fix Released Status in libnvidia-nscq-450 package in Ubuntu: Fix Released Status in libnvidia-nscq-460 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-418-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-450-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-460-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-470 package in Ubuntu: In Progress Status in nvidia-graphics-drivers-470-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-495 package in Ubuntu: In Progress Status in nvidia-graphics-drivers-418-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-470 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-495 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-470 source package in Focal: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-495 source package in Focal: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-470 source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-495 source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Impish: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Impish: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Impish: Fix Committed Status in nvidia-graphics-drivers-470 source package in Impish: Fix Committed Status in nvidia-graphics-drivers-470-server source package in Impish: Fix Committed Bug description: Update the NVIDIA series and introduce the new 495 series in Bionic, Focal, Hirsute, and Impish. [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our users have access to these improvements. See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware:
[Kernel-packages] [Bug 1949636] [NEW] Impish update: upstream stable patchset 2021-11-03
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2021-11-03 Ported from the following upstream stable releases: v5.10.70, v5.14.9 from git://git.kernel.org/ ocfs2: drop acl cache for directories too mm: fix uninitialized use in overcommit_policy_handler usb: gadget: r8a66597: fix a loop in set_feature() usb: dwc2: gadget: Fix ISOC flow for BDMA and Slave usb: dwc2: gadget: Fix ISOC transfer complete handling for DDMA usb: musb: tusb6010: uninitialized data in tusb_fifo_write_unaligned() cifs: fix incorrect check for null pointer in header_assemble xen/x86: fix PV trap handling on secondary processors usb-storage: Add quirk for ScanLogic SL11R-IDE older than 2.6c USB: serial: cp210x: add ID for GW Instek GDM-834x Digital Multimeter USB: cdc-acm: fix minor-number release Revert "USB: bcma: Add a check for devm_gpiod_get" binder: make sure fd closes complete staging: greybus: uart: fix tty use after free Re-enable UAS for LaCie Rugged USB3-FW with fk quirk usb: dwc3: core: balance phy init and exit usb: core: hcd: Add support for deferring roothub registration USB: serial: mos7840: remove duplicated 0xac24 device ID USB: serial: option: add Telit LN920 compositions USB: serial: option: remove duplicate USB device ID USB: serial: option: add device id for Foxconn T99W265 mcb: fix error handling in mcb_alloc_bus() erofs: fix up erofs_lookup tracepoint btrfs: prevent __btrfs_dump_space_info() to underflow its free space xhci: Set HCD flag to defer primary roothub registration serial: 8250: 8250_omap: Fix RX_LVL register offset serial: mvebu-uart: fix driver's tx_empty callback scsi: sd_zbc: Ensure buffer size is aligned to SECTOR_SIZE drm/amd/pm: Update intermediate power state for SI net: hso: fix muxed tty registration comedi: Fix memory leak in compat_insnlist() afs: Fix incorrect triggering of sillyrename on 3rd-party invalidation afs: Fix updating of i_blocks on file/dir extension platform/x86/intel: punit_ipc: Drop wrong use of ACPI_PTR() enetc: Fix illegal access when reading affinity_hint enetc: Fix uninitialized struct dim_sample field usage bnxt_en: Fix TX timeout when TX ring size is set to the smallest net: hns3: fix change RSS 'hfunc' ineffective issue net: hns3: check queue id range before using net/smc: add missing error check in smc_clc_prfx_set() net/smc: fix 'workqueue leaked lock' in smc_conn_abort_work net: dsa: don't allocate the slave_mii_bus using devres net: dsa: realtek: register the MDIO bus under devres kselftest/arm64: signal: Add SVE to the set of features we can check for kselftest/arm64: signal: Skip tests if required features are missing s390/qeth: fix NULL deref in qeth_clear_working_pool_list() gpio: uniphier: Fix void functions to remove return value qed: rdma - don't wait for resources under hw error recovery flow net/mlx4_en: Don't allow aRFS for encapsulated packets atlantic: Fix issue in the pm resume flow. scsi: iscsi: Adjust iface sysfs attr detection scsi: target: Fix the pgr/alua_support_store functions tty: synclink_gt: rename a conflicting function name fpga: machxo2-spi: Return an error on failure fpga: machxo2-spi: Fix missing error code in machxo2_write_complete() nvme-tcp: fix incorrect h2cdata pdu offset accounting nvme: keep ctrl->namespaces ordered thermal/core: Potential buffer overflow in thermal_build_list_of_policies() cifs: fix a sign extension bug scsi: qla2xxx: Restore initiator in dual mode scsi: lpfc: Use correct scnprintf() limit irqchip/goldfish-pic: Select GENERIC_IRQ_CHIP to fix build irqchip/gic-v3-its: Fix potential VPE leak on error md: fix a lock order reversal in md_alloc x86/asm: Fix SETZ size enqcmds() build failure io_uring: put provided buffer meta data under memcg accounting blktrace: Fix uaf in blk_trace access after removing by sysfs net: phylink: Update SFP selected interface on advertising changes net: macb: fix use after free on rmmod net: stmmac: allow CSR clock of 300MHz blk-mq: avoid to iterate over stale request m68k: Double cast io functions to unsigned long ipv6: delay fib6_sernum increase in fib6_add cpufreq: intel_pstate: Override parameters if HWP forced by BIOS bpf: Add oversize check before call kvcalloc() xen/balloon: use a kernel thread instead a workqueue nvme-multipath: fix ANA state updates when a namespace is not present nvme-rdma: destroy cm id before destroy qp to avoid use after free sparc32: page align size in arch_dma_alloc amd/display: downgrade validation failure log level block: check if a profile is actually
[Kernel-packages] [Bug 1945289] Re: Failed to properly resume from S3 (suspend-to-ram) on kernel version 5.13.0-16 (installed while updating to impish), amdgpu driver.
Same problem here : AMD Radeon R7 Graphics (CARRIZO, DRM 3.41.0, 5.13.0-21-generic, LLVM 12.0.1) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/1945289 Title: Failed to properly resume from S3 (suspend-to-ram) on kernel version 5.13.0-16 (installed while updating to impish), amdgpu driver. Status in linux-meta package in Ubuntu: Confirmed Bug description: On 5.11.0 everything is OK. The GPU is AMD Carrizo APU. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1945289/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926985] Re: linux-version sort: argv and stdin behaviors differ
** Tags added: verification-done verification-done-bionic verification- done-focal verification-done-hirsute -- 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/1926985 Title: linux-version sort: argv and stdin behaviors differ Status in linux-base package in Ubuntu: Fix Released Status in linux-base source package in Bionic: Fix Committed Status in linux-base source package in Focal: Fix Committed Status in linux-base source package in Groovy: Fix Committed Status in linux-base source package in Hirsute: Fix Committed Status in linux-base source package in Impish: Fix Released Status in linux-base package in Debian: New Bug description: [Impact] `linux-version sort` provides 2 ways to sort kernel version strings: users can provide these strings either via the command line or via stdin. Currently these methods give different answers for certain version strings (see Test Case). The stdin behavior is decidedly incorrect, and this is the mode flash-kernel uses. As a real world example, a user with an arm64 u-boot system might end up booting 5.8.0-50-generic instead of the expected 5.8.0-50-generic-64k if both are installed. There maybe additional issues caused by this; for example, I found this with our automation that tests kernels on various arm64 platforms in version increasing order. Only after consulting logs did we realize that 64k kernels were not ever getting booted because the tooling (which uses argv mode) disagreed with the kernel installer (flash-kernel using stdin mode) about which kernel should be the default. It's possible this internal discrepancy can cause other issues due to tools disagreeing about which kernel is the latest, but the flash- kernel example is the only one I'm aware of at this point. [Test Case] Using argv: $ linux-version sort 5.8.0-50-generic 5.8.0-50-generic-64k 5.8.0-50-generic 5.8.0-50-generic-64k Using stdin (incorrect): $ cat versions.txt 5.8.0-50-generic 5.8.0-50-generic-64k $ cat versions.txt | linux-version sort 5.8.0-50-generic-64k 5.8.0-50-generic [Where Problems Could Occur] An obvious place where problems could occur is if someone is relying on rebooting into the kernel that is incorrectly being sorted greatest. For those using only Ubuntu kernel packages, the only case I'm aware of is arm64 generic vs. generic-64k case used in the examples above. The generic-64k flavor is available in >= 20.10, as well as 20.04-hwe. ARM server users - those most likely to want the generic-64k flavor - are very unlikely to be using flash-kernel. The standard for ARM servers is UEFI firmware, which use GRUB and are unaffected by this change. We found this on an HP m400 platform which is the only Ubuntu certified u-boot-based arm64 server. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-base/+bug/1926985/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1948807] Re: Boot time from snap in 20/stable increses boot time on 3.5 seconds
** Also affects: linux-raspi (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux-raspi (Ubuntu Focal) Status: New => Confirmed ** Changed in: linux-raspi (Ubuntu Focal) Assignee: (unassigned) => Juerg Haefliger (juergh) ** Changed in: linux-raspi (Ubuntu Focal) Importance: Undecided => High ** Summary changed: - Boot time from snap in 20/stable increses boot time on 3.5 seconds + Boot time from snap in 20/stable increases boot time on 3.5 seconds -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/1948807 Title: Boot time from snap in 20/stable increases boot time on 3.5 seconds Status in linux-raspi package in Ubuntu: New Status in linux-raspi source package in Focal: Confirmed Bug description: I am seeing what looks as a regression in pi-kernel snap for UC20: there are around 3.5 additional seconds spent in boot time. In the image from cdimage (2021-06-30), I see: [1.856540] random: crng init done [1.871798] loop: module loaded (see https://paste.ubuntu.com/p/CkfWXY5Vgf/) while if I build an image from latest snaps in the 20/stable channel, I get: [1.855481] random: crng init done [5.349491] loop: module loaded (see https://paste.ubuntu.com/p/CNt42gdDcZ/) The pi-kernel snap revision is 353. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1948807/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1906370] Re: [21.04 FEAT] Deactivate CONFIG_QETH_OSN kernel config option
Hi Stefan, you can ignore this - was an accident and is already cleaned up in LP (but the clean-up probably didn't synched to BZ yet). -- 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/1906370 Title: [21.04 FEAT] Deactivate CONFIG_QETH_OSN kernel config option Status in Ubuntu on IBM z Systems: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: OSN devices' final shipment was as part of the IBM z13 release. The primary exploiter was the IBM Communication Controller, which was pulled out of marketing in March 2015 and should be out of service now. Therefore, we pull the support from all Linux distros going forward. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1906370/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1949609] 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 1949609 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/1949609 Title: [mlx5][ct-offload] Traffic disruption and errors logged when system is gateway chassis for OVN logical router Status in linux package in Ubuntu: Incomplete Bug description: System running 5.13.0 kernel, OFED 5.4.3, OVS 2.16 and OVN 21.09. ConnectX-5 with firmware=16.31.2006 Hardware offload enabled. Ports bonded (VF LAG enabled). Security Groups enabled (i.e. CT offload). When the system is the active gateway chassis for a logical OVN router, i.e. it is currently responsible for north/south traffic for instances that may be on other hosts, I see disturbances in the traffic and see messages like this in the log. Nov 3 13:35:01 pc1-rb3-n4 kernel: [ 250.761959] mlx5_core :81:00.0: mlx5dr_actions_build_ste_arr:721:(pid 6628): Failed to handle checksum recalculation err -22 Nov 3 13:35:01 pc1-rb3-n4 kernel: [ 250.774656] mlx5_core :81:00.0: dr_rule_create_rule:1287:(pid 6628): Failed creating rule Nov 3 13:35:01 pc1-rb3-n4 kernel: [ 250.774659] mlx5_core :81:00.0: mlx5_cmd_dr_create_fte:561:(pid 6628): Failed to create dr rule err(-22) Nov 3 13:35:01 pc1-rb3-n4 kernel: [ 250.784057] mlx5_core :81:00.0 enp129s0f0: Failed to add post action rule Nov 3 13:35:01 pc1-rb3-n4 kernel: [ 250.819968] mlx5_core :81:00.0 enp129s0f0: Failed to offload ct flow, err -22 Nov 3 13:35:01 pc1-rb3-n4 kernel: [ 250.829390] mlx5_core :81:00.1: mlx5dr_actions_build_ste_arr:721:(pid 6628): Failed to handle checksum recalculation err -22 Nov 3 13:35:01 pc1-rb3-n4 kernel: [ 250.842403] mlx5_core :81:00.1: dr_rule_create_rule:1287:(pid 6628): Failed creating rule Nov 3 15:28:35 pc1-rb3-n4 kernel: [ 7065.597150] mlx5_core :81:00.0: mlx5_cmd_check:810:(pid 6654): DEALLOC_PACKET_REFORMAT_CONTEXT(0x93e) op_mod(0x0) failed, status bad resource state(0x9), syndrome (0x179e84) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1949609/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1949609] Re: [mlx5][ct-offload] Traffic disruption and errors logged when system is gateway chassis for OVN logical router
** Attachment added: "dpctl-dump-flows.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1949609/+attachment/5537899/+files/dpctl-dump-flows.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/1949609 Title: [mlx5][ct-offload] Traffic disruption and errors logged when system is gateway chassis for OVN logical router Status in linux package in Ubuntu: Incomplete Bug description: System running 5.13.0 kernel, OFED 5.4.3, OVS 2.16 and OVN 21.09. ConnectX-5 with firmware=16.31.2006 Hardware offload enabled. Ports bonded (VF LAG enabled). Security Groups enabled (i.e. CT offload). When the system is the active gateway chassis for a logical OVN router, i.e. it is currently responsible for north/south traffic for instances that may be on other hosts, I see disturbances in the traffic and see messages like this in the log. Nov 3 13:35:01 pc1-rb3-n4 kernel: [ 250.761959] mlx5_core :81:00.0: mlx5dr_actions_build_ste_arr:721:(pid 6628): Failed to handle checksum recalculation err -22 Nov 3 13:35:01 pc1-rb3-n4 kernel: [ 250.774656] mlx5_core :81:00.0: dr_rule_create_rule:1287:(pid 6628): Failed creating rule Nov 3 13:35:01 pc1-rb3-n4 kernel: [ 250.774659] mlx5_core :81:00.0: mlx5_cmd_dr_create_fte:561:(pid 6628): Failed to create dr rule err(-22) Nov 3 13:35:01 pc1-rb3-n4 kernel: [ 250.784057] mlx5_core :81:00.0 enp129s0f0: Failed to add post action rule Nov 3 13:35:01 pc1-rb3-n4 kernel: [ 250.819968] mlx5_core :81:00.0 enp129s0f0: Failed to offload ct flow, err -22 Nov 3 13:35:01 pc1-rb3-n4 kernel: [ 250.829390] mlx5_core :81:00.1: mlx5dr_actions_build_ste_arr:721:(pid 6628): Failed to handle checksum recalculation err -22 Nov 3 13:35:01 pc1-rb3-n4 kernel: [ 250.842403] mlx5_core :81:00.1: dr_rule_create_rule:1287:(pid 6628): Failed creating rule Nov 3 15:28:35 pc1-rb3-n4 kernel: [ 7065.597150] mlx5_core :81:00.0: mlx5_cmd_check:810:(pid 6654): DEALLOC_PACKET_REFORMAT_CONTEXT(0x93e) op_mod(0x0) failed, status bad resource state(0x9), syndrome (0x179e84) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1949609/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1949609] Re: [mlx5][ct-offload] Traffic disruption and errors logged when system is gateway chassis for OVN logical router
** Attachment added: "version.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1949609/+attachment/5537897/+files/version.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1949609 Title: [mlx5][ct-offload] Traffic disruption and errors logged when system is gateway chassis for OVN logical router Status in linux package in Ubuntu: Incomplete Bug description: System running 5.13.0 kernel, OFED 5.4.3, OVS 2.16 and OVN 21.09. ConnectX-5 with firmware=16.31.2006 Hardware offload enabled. Ports bonded (VF LAG enabled). Security Groups enabled (i.e. CT offload). When the system is the active gateway chassis for a logical OVN router, i.e. it is currently responsible for north/south traffic for instances that may be on other hosts, I see disturbances in the traffic and see messages like this in the log. Nov 3 13:35:01 pc1-rb3-n4 kernel: [ 250.761959] mlx5_core :81:00.0: mlx5dr_actions_build_ste_arr:721:(pid 6628): Failed to handle checksum recalculation err -22 Nov 3 13:35:01 pc1-rb3-n4 kernel: [ 250.774656] mlx5_core :81:00.0: dr_rule_create_rule:1287:(pid 6628): Failed creating rule Nov 3 13:35:01 pc1-rb3-n4 kernel: [ 250.774659] mlx5_core :81:00.0: mlx5_cmd_dr_create_fte:561:(pid 6628): Failed to create dr rule err(-22) Nov 3 13:35:01 pc1-rb3-n4 kernel: [ 250.784057] mlx5_core :81:00.0 enp129s0f0: Failed to add post action rule Nov 3 13:35:01 pc1-rb3-n4 kernel: [ 250.819968] mlx5_core :81:00.0 enp129s0f0: Failed to offload ct flow, err -22 Nov 3 13:35:01 pc1-rb3-n4 kernel: [ 250.829390] mlx5_core :81:00.1: mlx5dr_actions_build_ste_arr:721:(pid 6628): Failed to handle checksum recalculation err -22 Nov 3 13:35:01 pc1-rb3-n4 kernel: [ 250.842403] mlx5_core :81:00.1: dr_rule_create_rule:1287:(pid 6628): Failed creating rule Nov 3 15:28:35 pc1-rb3-n4 kernel: [ 7065.597150] mlx5_core :81:00.0: mlx5_cmd_check:810:(pid 6654): DEALLOC_PACKET_REFORMAT_CONTEXT(0x93e) op_mod(0x0) failed, status bad resource state(0x9), syndrome (0x179e84) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1949609/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1949609] Re: [mlx5][ct-offload] Traffic disruption and errors logged when system is gateway chassis for OVN logical router
** Attachment added: "lspci-vnvn.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1949609/+attachment/5537898/+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/1949609 Title: [mlx5][ct-offload] Traffic disruption and errors logged when system is gateway chassis for OVN logical router Status in linux package in Ubuntu: Incomplete Bug description: System running 5.13.0 kernel, OFED 5.4.3, OVS 2.16 and OVN 21.09. ConnectX-5 with firmware=16.31.2006 Hardware offload enabled. Ports bonded (VF LAG enabled). Security Groups enabled (i.e. CT offload). When the system is the active gateway chassis for a logical OVN router, i.e. it is currently responsible for north/south traffic for instances that may be on other hosts, I see disturbances in the traffic and see messages like this in the log. Nov 3 13:35:01 pc1-rb3-n4 kernel: [ 250.761959] mlx5_core :81:00.0: mlx5dr_actions_build_ste_arr:721:(pid 6628): Failed to handle checksum recalculation err -22 Nov 3 13:35:01 pc1-rb3-n4 kernel: [ 250.774656] mlx5_core :81:00.0: dr_rule_create_rule:1287:(pid 6628): Failed creating rule Nov 3 13:35:01 pc1-rb3-n4 kernel: [ 250.774659] mlx5_core :81:00.0: mlx5_cmd_dr_create_fte:561:(pid 6628): Failed to create dr rule err(-22) Nov 3 13:35:01 pc1-rb3-n4 kernel: [ 250.784057] mlx5_core :81:00.0 enp129s0f0: Failed to add post action rule Nov 3 13:35:01 pc1-rb3-n4 kernel: [ 250.819968] mlx5_core :81:00.0 enp129s0f0: Failed to offload ct flow, err -22 Nov 3 13:35:01 pc1-rb3-n4 kernel: [ 250.829390] mlx5_core :81:00.1: mlx5dr_actions_build_ste_arr:721:(pid 6628): Failed to handle checksum recalculation err -22 Nov 3 13:35:01 pc1-rb3-n4 kernel: [ 250.842403] mlx5_core :81:00.1: dr_rule_create_rule:1287:(pid 6628): Failed creating rule Nov 3 15:28:35 pc1-rb3-n4 kernel: [ 7065.597150] mlx5_core :81:00.0: mlx5_cmd_check:810:(pid 6654): DEALLOC_PACKET_REFORMAT_CONTEXT(0x93e) op_mod(0x0) failed, status bad resource state(0x9), syndrome (0x179e84) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1949609/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1949609] Re: [mlx5][ct-offload] Traffic disruption and errors logged when system is gateway chassis for OVN logical router
** Attachment added: "br-int-flows.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1949609/+attachment/5537900/+files/br-int-flows.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/1949609 Title: [mlx5][ct-offload] Traffic disruption and errors logged when system is gateway chassis for OVN logical router Status in linux package in Ubuntu: Incomplete Bug description: System running 5.13.0 kernel, OFED 5.4.3, OVS 2.16 and OVN 21.09. ConnectX-5 with firmware=16.31.2006 Hardware offload enabled. Ports bonded (VF LAG enabled). Security Groups enabled (i.e. CT offload). When the system is the active gateway chassis for a logical OVN router, i.e. it is currently responsible for north/south traffic for instances that may be on other hosts, I see disturbances in the traffic and see messages like this in the log. Nov 3 13:35:01 pc1-rb3-n4 kernel: [ 250.761959] mlx5_core :81:00.0: mlx5dr_actions_build_ste_arr:721:(pid 6628): Failed to handle checksum recalculation err -22 Nov 3 13:35:01 pc1-rb3-n4 kernel: [ 250.774656] mlx5_core :81:00.0: dr_rule_create_rule:1287:(pid 6628): Failed creating rule Nov 3 13:35:01 pc1-rb3-n4 kernel: [ 250.774659] mlx5_core :81:00.0: mlx5_cmd_dr_create_fte:561:(pid 6628): Failed to create dr rule err(-22) Nov 3 13:35:01 pc1-rb3-n4 kernel: [ 250.784057] mlx5_core :81:00.0 enp129s0f0: Failed to add post action rule Nov 3 13:35:01 pc1-rb3-n4 kernel: [ 250.819968] mlx5_core :81:00.0 enp129s0f0: Failed to offload ct flow, err -22 Nov 3 13:35:01 pc1-rb3-n4 kernel: [ 250.829390] mlx5_core :81:00.1: mlx5dr_actions_build_ste_arr:721:(pid 6628): Failed to handle checksum recalculation err -22 Nov 3 13:35:01 pc1-rb3-n4 kernel: [ 250.842403] mlx5_core :81:00.1: dr_rule_create_rule:1287:(pid 6628): Failed creating rule Nov 3 15:28:35 pc1-rb3-n4 kernel: [ 7065.597150] mlx5_core :81:00.0: mlx5_cmd_check:810:(pid 6654): DEALLOC_PACKET_REFORMAT_CONTEXT(0x93e) op_mod(0x0) failed, status bad resource state(0x9), syndrome (0x179e84) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1949609/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1949609] [NEW] [mlx5][ct-offload] Traffic disruption and errors logged when system is gateway chassis for OVN logical router
Public bug reported: System running 5.13.0 kernel, OFED 5.4.3, OVS 2.16 and OVN 21.09. ConnectX-5 with firmware=16.31.2006 Hardware offload enabled. Ports bonded (VF LAG enabled). Security Groups enabled (i.e. CT offload). When the system is the active gateway chassis for a logical OVN router, i.e. it is currently responsible for north/south traffic for instances that may be on other hosts, I see disturbances in the traffic and see messages like this in the log. Nov 3 13:35:01 pc1-rb3-n4 kernel: [ 250.761959] mlx5_core :81:00.0: mlx5dr_actions_build_ste_arr:721:(pid 6628): Failed to handle checksum recalculation err -22 Nov 3 13:35:01 pc1-rb3-n4 kernel: [ 250.774656] mlx5_core :81:00.0: dr_rule_create_rule:1287:(pid 6628): Failed creating rule Nov 3 13:35:01 pc1-rb3-n4 kernel: [ 250.774659] mlx5_core :81:00.0: mlx5_cmd_dr_create_fte:561:(pid 6628): Failed to create dr rule err(-22) Nov 3 13:35:01 pc1-rb3-n4 kernel: [ 250.784057] mlx5_core :81:00.0 enp129s0f0: Failed to add post action rule Nov 3 13:35:01 pc1-rb3-n4 kernel: [ 250.819968] mlx5_core :81:00.0 enp129s0f0: Failed to offload ct flow, err -22 Nov 3 13:35:01 pc1-rb3-n4 kernel: [ 250.829390] mlx5_core :81:00.1: mlx5dr_actions_build_ste_arr:721:(pid 6628): Failed to handle checksum recalculation err -22 Nov 3 13:35:01 pc1-rb3-n4 kernel: [ 250.842403] mlx5_core :81:00.1: dr_rule_create_rule:1287:(pid 6628): Failed creating rule Nov 3 15:28:35 pc1-rb3-n4 kernel: [ 7065.597150] mlx5_core :81:00.0: mlx5_cmd_check:810:(pid 6654): DEALLOC_PACKET_REFORMAT_CONTEXT(0x93e) op_mod(0x0) failed, status bad resource state(0x9), syndrome (0x179e84) ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1949609 Title: [mlx5][ct-offload] Traffic disruption and errors logged when system is gateway chassis for OVN logical router Status in linux package in Ubuntu: Incomplete Bug description: System running 5.13.0 kernel, OFED 5.4.3, OVS 2.16 and OVN 21.09. ConnectX-5 with firmware=16.31.2006 Hardware offload enabled. Ports bonded (VF LAG enabled). Security Groups enabled (i.e. CT offload). When the system is the active gateway chassis for a logical OVN router, i.e. it is currently responsible for north/south traffic for instances that may be on other hosts, I see disturbances in the traffic and see messages like this in the log. Nov 3 13:35:01 pc1-rb3-n4 kernel: [ 250.761959] mlx5_core :81:00.0: mlx5dr_actions_build_ste_arr:721:(pid 6628): Failed to handle checksum recalculation err -22 Nov 3 13:35:01 pc1-rb3-n4 kernel: [ 250.774656] mlx5_core :81:00.0: dr_rule_create_rule:1287:(pid 6628): Failed creating rule Nov 3 13:35:01 pc1-rb3-n4 kernel: [ 250.774659] mlx5_core :81:00.0: mlx5_cmd_dr_create_fte:561:(pid 6628): Failed to create dr rule err(-22) Nov 3 13:35:01 pc1-rb3-n4 kernel: [ 250.784057] mlx5_core :81:00.0 enp129s0f0: Failed to add post action rule Nov 3 13:35:01 pc1-rb3-n4 kernel: [ 250.819968] mlx5_core :81:00.0 enp129s0f0: Failed to offload ct flow, err -22 Nov 3 13:35:01 pc1-rb3-n4 kernel: [ 250.829390] mlx5_core :81:00.1: mlx5dr_actions_build_ste_arr:721:(pid 6628): Failed to handle checksum recalculation err -22 Nov 3 13:35:01 pc1-rb3-n4 kernel: [ 250.842403] mlx5_core :81:00.1: dr_rule_create_rule:1287:(pid 6628): Failed creating rule Nov 3 15:28:35 pc1-rb3-n4 kernel: [ 7065.597150] mlx5_core :81:00.0: mlx5_cmd_check:810:(pid 6654): DEALLOC_PACKET_REFORMAT_CONTEXT(0x93e) op_mod(0x0) failed, status bad resource state(0x9), syndrome (0x179e84) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1949609/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1906370] Comment bridged from LTC Bugzilla
--- Comment From stefan.ra...@de.ibm.com 2021-11-03 11:52 EDT--- Hi - did you add your comment to the wrong bugzilla..?! I can't quite make the connection here! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1906370 Title: [21.04 FEAT] Deactivate CONFIG_QETH_OSN kernel config option Status in Ubuntu on IBM z Systems: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: OSN devices' final shipment was as part of the IBM z13 release. The primary exploiter was the IBM Communication Controller, which was pulled out of marketing in March 2015 and should be out of service now. Therefore, we pull the support from all Linux distros going forward. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1906370/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1943464] Re: Reassign I/O Path of ConnectX-5 Port 1 before Port 2 causes NULL dereference
** Changed in: linux (Ubuntu Focal) Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1943464 Title: Reassign I/O Path of ConnectX-5 Port 1 before Port 2 causes NULL dereference Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: In Progress Status in linux source package in Hirsute: Fix Committed Status in linux source package in Impish: Fix Committed Status in linux source package in Jammy: Fix Released Bug description: SRU Justification: [Impact] * After reassigning a PCHID of a ConnectX-5 based RoCE Adapter from one physical LPAR to another, running Ubuntu 20.04 with kernel 5.4 (latest), a lifetime issue occurs. * Subsequent testing on newer kernels now shows that a NULL pointer dereference in the zPCI code happens (causing a hard crash) that was previously hidden by leaking the struct pci_dev. * For a more detailed root cause analysis, see the below original bug description. [Fix] The following three commits fix this issue in focal: * upstream (since v5.12-rc4): 0b13525c20febcfecccf6fc1db5969727401317d 0b13525c20fe "s390/pci: fix leak of PCI device structure" backport: https://launchpadlibrarian.net/566161494/0001-s390-pci-fix-leak-of-PCI-device-structure.patch * upstream (since v5.14-rc7): 2a671f77ee49f3e78997b77fdee139467ff6a598 2a671f77ee49 "s390/pci: fix use after free of zpci_dev" backport: https://launchpadlibrarian.net/566161496/0002-s390-pci-fix-use-after-free-of-zpci_dev.patch * upstream (since v5.15-rc5): a46044a92add6a400f4dada7b943b30221f7cc80 a46044a92add "s390/pci: fix zpci_zdev_put() on reserve" backport: https://launchpadlibrarian.net/566161497/0003-s390-pci-fix-zpci_zdev_put-on-reserve.patch * Commit 0b13525c20fe fixes a lifetime issue of the struct pci_dev that was not released on removal, commit 2a671f77ee49 fixes the 'NULL pointer dereference' (causing the hard crash) itself. and commit a46044a92add fixes the handling of multiple events for a single reserve state transition of the device. Without this, the NULL dereference can still be triggered as Reassign I/O Path causes a redudant second removal event. * Since none of the three upstream commits does apply cleanly to focal master-next by just cherry-picking them (mainly due to changes in the context), the above backports are needed. [Test Case] * Two z15 or LinuxONE III LPARs, one with a Connect-X5 based RoCE adapter attached. * LPARs need to run Ubuntu 20.04 with kernel 5.4 to hit the lifetime issue (that hides the also potential existing 'NULL pointer dereference') - with Hirsute and kernel 5.11 the 'NULL pointer dereference' crash occurs. * Now change the PCHID (physical channel identifier) to a different one from the 2nd LPAR (at the HMC?). * Verify if the reassignment worked properly (by checking the PCHID) and monitor the kernel ring buffer dmesg (diagnostic messages) for "Krnl PSW" crash (caused by NULL pointer) (for more error details, please see below original bug description). * Due hardware availability reasons (the ConnectX-5 cards are only used in special cases), the testing needs to be done by IBM. [Regression Potential / What can go wrong] * What can go wrong with: 2a671f77ee49 "s390/pci: fix use after free of zpci_dev" * The reference count to the struct zpci_dev got increased while it is used by the PCI core. This could cause a leak if not properly released. * Hot-plug of there Connect-X5 devices could be broken on s390x entirely, in case the new pointer handing is erroneous. * This may even have an impact on "cold plug", too. * Fortunately the modifications are quite minimal and thereby traceable, * and affect /arch/s390/pci/pci.c and arch/s390/pci/pci_bus.h only, hence are specific to the s390x platform only and there again to "plugging" of zPCI devices. * What can go wrong with: 0b13525c20fe "s390/pci: fix leak of PCI device structure" * The function zpci_remove_device got expanded with an additional set_error argument, and the internal flow got significantly changed. In case handled in a wrong way, this may harm the entire remove/release logic. * The calls of zpci_remove_device need to be adjusted (as part of the new arg), failures here will most likely be identified at compile time. * The initialization of the pci_dev struct got improved, * and the flow in __zpci_event_availability carefully changed to reflect the device slot/bus remove characteristics. However, issues here may lead again to general zpci hotplug removal issues. * Fortunately all modifications are limited to
[Kernel-packages] [Bug 1943464] Re: Reassign I/O Path of ConnectX-5 Port 1 before Port 2 causes NULL dereference
SRU request submitted to the Ubuntu kernel team mailing list for focal: https://lists.ubuntu.com/archives/kernel-team/2021-November/thread.html#125405 Changing status to 'In Progress' for and focal. As mentioned in the SRU Justification, IBM is working on upstream stable, that will eventually cover hirsute and 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/1943464 Title: Reassign I/O Path of ConnectX-5 Port 1 before Port 2 causes NULL dereference Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: In Progress Status in linux source package in Hirsute: Fix Committed Status in linux source package in Impish: Fix Committed Status in linux source package in Jammy: Fix Released Bug description: SRU Justification: [Impact] * After reassigning a PCHID of a ConnectX-5 based RoCE Adapter from one physical LPAR to another, running Ubuntu 20.04 with kernel 5.4 (latest), a lifetime issue occurs. * Subsequent testing on newer kernels now shows that a NULL pointer dereference in the zPCI code happens (causing a hard crash) that was previously hidden by leaking the struct pci_dev. * For a more detailed root cause analysis, see the below original bug description. [Fix] The following three commits fix this issue in focal: * upstream (since v5.12-rc4): 0b13525c20febcfecccf6fc1db5969727401317d 0b13525c20fe "s390/pci: fix leak of PCI device structure" backport: https://launchpadlibrarian.net/566161494/0001-s390-pci-fix-leak-of-PCI-device-structure.patch * upstream (since v5.14-rc7): 2a671f77ee49f3e78997b77fdee139467ff6a598 2a671f77ee49 "s390/pci: fix use after free of zpci_dev" backport: https://launchpadlibrarian.net/566161496/0002-s390-pci-fix-use-after-free-of-zpci_dev.patch * upstream (since v5.15-rc5): a46044a92add6a400f4dada7b943b30221f7cc80 a46044a92add "s390/pci: fix zpci_zdev_put() on reserve" backport: https://launchpadlibrarian.net/566161497/0003-s390-pci-fix-zpci_zdev_put-on-reserve.patch * Commit 0b13525c20fe fixes a lifetime issue of the struct pci_dev that was not released on removal, commit 2a671f77ee49 fixes the 'NULL pointer dereference' (causing the hard crash) itself. and commit a46044a92add fixes the handling of multiple events for a single reserve state transition of the device. Without this, the NULL dereference can still be triggered as Reassign I/O Path causes a redudant second removal event. * Since none of the three upstream commits does apply cleanly to focal master-next by just cherry-picking them (mainly due to changes in the context), the above backports are needed. [Test Case] * Two z15 or LinuxONE III LPARs, one with a Connect-X5 based RoCE adapter attached. * LPARs need to run Ubuntu 20.04 with kernel 5.4 to hit the lifetime issue (that hides the also potential existing 'NULL pointer dereference') - with Hirsute and kernel 5.11 the 'NULL pointer dereference' crash occurs. * Now change the PCHID (physical channel identifier) to a different one from the 2nd LPAR (at the HMC?). * Verify if the reassignment worked properly (by checking the PCHID) and monitor the kernel ring buffer dmesg (diagnostic messages) for "Krnl PSW" crash (caused by NULL pointer) (for more error details, please see below original bug description). * Due hardware availability reasons (the ConnectX-5 cards are only used in special cases), the testing needs to be done by IBM. [Regression Potential / What can go wrong] * What can go wrong with: 2a671f77ee49 "s390/pci: fix use after free of zpci_dev" * The reference count to the struct zpci_dev got increased while it is used by the PCI core. This could cause a leak if not properly released. * Hot-plug of there Connect-X5 devices could be broken on s390x entirely, in case the new pointer handing is erroneous. * This may even have an impact on "cold plug", too. * Fortunately the modifications are quite minimal and thereby traceable, * and affect /arch/s390/pci/pci.c and arch/s390/pci/pci_bus.h only, hence are specific to the s390x platform only and there again to "plugging" of zPCI devices. * What can go wrong with: 0b13525c20fe "s390/pci: fix leak of PCI device structure" * The function zpci_remove_device got expanded with an additional set_error argument, and the internal flow got significantly changed. In case handled in a wrong way, this may harm the entire remove/release logic. * The calls of zpci_remove_device need to be adjusted (as part of the new arg), failures here will most likely be identified at compile time. * The initialization of the pci_dev struct got improved, * and the flow in __zpci_event_availability
[Kernel-packages] [Bug 1949497] Re: [amdgpu] AMD R5 M430 dGPU freezes ([drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout)
"MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0" and "Ubuntu on Xorg" did not change anything. It gave the same error. with "MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0": [ 58.240910] [drm] PCIE gen 3 link speeds already enabled [ 58.242162] amdgpu :01:00.0: amdgpu: PCIE GART of 256M enabled (table at 0x00F4). [ 78.052145] [drm] PCIE gen 3 link speeds already enabled [ 78.053444] amdgpu :01:00.0: amdgpu: PCIE GART of 256M enabled (table at 0x00F4). [ 89.004997] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, signaled seq=45, emitted seq=47 [ 89.005811] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process glmark2 pid 3161 thread glmark2:cs0 pid 3162 [ 89.006531] amdgpu :01:00.0: amdgpu: GPU recovery disabled. [ 89.261947] Asynchronous wait on fence dma_fence_chain:unbound:1 timed out (hint:submit_notify [i915]) [ 89.262349] Asynchronous wait on fence dma_fence_chain:unbound:1 timed out (hint:submit_notify [i915]) with "Ubuntu on Xorg": [ 38.254745] [drm] PCIE gen 3 link speeds already enabled [ 38.255880] amdgpu :01:00.0: amdgpu: PCIE GART of 256M enabled (table at 0x00F4). [ 68.697606] [drm] PCIE gen 3 link speeds already enabled [ 68.698896] amdgpu :01:00.0: amdgpu: PCIE GART of 256M enabled (table at 0x00F4). [ 80.279529] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, signaled seq=49, emitted seq=51 [ 80.280382] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process glmark2 pid 3198 thread glmark2:cs0 pid 3199 [ 80.281144] amdgpu :01:00.0: amdgpu: GPU recovery disabled. [ 81.047412] Asynchronous wait on fence :00:02.0:gnome-shell[1686]:666 timed out (hint:intel_atomic_commit_ready [i915]) [ 81.047412] Asynchronous wait on fence dma_fence_chain:unbound:1 timed out (hint:submit_notify [i915]) [ 81.047915] Asynchronous wait on fence dma_fence_chain:unbound:1 timed out (hint:submit_notify [i915]) -- 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/1949497 Title: [amdgpu] AMD R5 M430 dGPU freezes ([drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout) Status in linux package in Ubuntu: Incomplete Bug description: When i try to run anything with my dGPU (Radeon R5 M430), application freezes. But when i set "power_dpm_state" to "battery", or amdgpu.dpm=0 in boot options, it runs fine. i get errors like this: [ 56.647827] [drm] PCIE gen 3 link speeds already enabled [ 56.649064] amdgpu :01:00.0: amdgpu: PCIE GART of 256M enabled (table at 0x00F4). [ 83.707076] [drm] PCIE gen 3 link speeds already enabled [ 83.708350] amdgpu :01:00.0: amdgpu: PCIE GART of 256M enabled (table at 0x00F4). [ 94.813212] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, signaled seq=47, emitted seq=49 [ 94.814219] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process glmark2 pid 4471 thread glmark2:cs0 pid 4473 [ 94.815125] amdgpu :01:00.0: amdgpu: GPU recovery disabled. [ 95.069353] Asynchronous wait on fence :00:02.0:gnome-shell[1648]:3c6 timed out (hint:intel_atomic_commit_ready [i915]) [ 95.069353] Asynchronous wait on fence dma_fence_chain:unbound:1 timed out (hint:submit_notify [i915]) ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: xorg 1:7.7+22ubuntu2 Uname: Linux 5.15.0-051500-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 BootLog: Error: [Errno 13] Erişim engellendi: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Nov 2 19:26:01 2021 DistUpgraded: Fresh install DistroCodename: impish DistroVariant: ubuntu DkmsStatus: v4l2loopback, 0.12.5, 5.13.0-20-generic, x86_64: installed v4l2loopback, 0.12.5, 5.15.0-051500-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Since before I upgraded GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company HD Graphics 620 [103c:81ee] Subsystem: Hewlett-Packard Company Sun XT [Radeon HD 8670A/8670M/8690M / R5 M330 / M430 / Radeon 520 Mobile] [103c:81ee] InstallationDate: Installed on 2021-10-29 (4 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: HP HP Notebook ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=tr_TR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-051500-generic root=UUID=51509311-ce8a-48fb-9ece-8e018d63fe03 ro quiet splash radeon.si_support=0 amdgpu.si_support=1 vt.handoff=7 SourcePackage:
[Kernel-packages] [Bug 397269] Re: HDMI audio cuts out intermittently while normal audio plays fine
For the record I have the same problem on a Huawei Matebook Pro using Ubuntu 20.04 - fully upgraded. But the computer uses an HDMI adapter. Could that be the problem? Again for the record, on another computer with Ubuntu 21.04 (Waylabd), everything works fine. -- 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/397269 Title: HDMI audio cuts out intermittently while normal audio plays fine Status in linux package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: Invalid Bug description: Binary package hint: pulseaudio I have my audio set up to play through my laptop speakers and over HDMI to my television. In Jaunty this works fine while in Karmic the HDMI audio will intermittently cut out for a split second a few times a minute. During this time however the audio over the laptop speakers plays just fine. It just seems as if a frame of the HDMI audio gets dropped randomly. The video over the HDMI is perfectly fine, FYI. ProblemType: Bug Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: michael4942 f mixer_applet2 michael7360 F npviewer.bin /dev/snd/pcmC0D0p: michael7360 F...m npviewer.bin /dev/snd/timer: michael7360 F npviewer.bin Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xf6ffc000 irq 21' Mixer name : 'SigmaTel STAC9228' Components : 'HDA:83847616,10280209,00100402' Controls : 28 Simple ctrls : 18 Date: Wed Jul 8 21:20:16 2009 DistroRelease: Ubuntu 9.10 NonfreeKernelModules: nvidia wl Package: pulseaudio 1:0.9.15-4ubuntu1 ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.30-10.12-generic SourcePackage: pulseaudio Uname: Linux 2.6.30-10-generic x86_64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/397269/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1674273] Re: Resolver ignores ndots option
This still occurs in Focal.
nslookup "respects the dots" as it calls the systemd resolver, and as per man
resolved.conf(5)
Domains=
A space-separated list of domains. These domains are used as search
suffixes when resolving single-label host names (domain names which contain no
dot)
to get this behavior on ping you need ping to switch to the systemd resolver
("resolve" in nsswitch) which is achieved with apt install libnss-resolve
--
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/1674273
Title:
Resolver ignores ndots option
Status in glibc package in Ubuntu:
Confirmed
Status in linux package in Ubuntu:
Invalid
Status in glibc source package in Xenial:
Confirmed
Status in linux source package in Xenial:
Invalid
Bug description:
This is a re-report of
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/401202 since that
one was apparently closed as no-fix simply because it was too old.
This still occurs in xenial.
Original description:
Regardless of ndots option in /etc/resolv.conf, when NXDOMAIN is returned
from the DNS server then resolver always try another attempt with the original
name extended by what is in search option.
For example, if you're looking for very.long.url.nowhere and there is a line
"search ubuntu.com" in resolv.conf you will get addres of server
very.long.url.nowhere.ubuntu.com if such exists. It is incorrect, it should
occurs only for urls having less that ndots option dots in its name.
My system is a standard Ubuntu Xenial desktop amd64 using network
manager and the default configured Wired Connection 1 (i.e. DHCP).
To reproduce:
- sudo install /dev/fd/0 /etc/NetworkManager/dnsmasq.d/domain
<<<'log-queries=extra'
- sudo killall dnsmasq
- ping some.long.non-existent.name
- Watch /var/log/syslog
In my case:
Mar 20 23:19:22 eragon dnsmasq[27367]: 46 127.0.0.1/40646 query[A]
some.long.non-existent.name from 127.0.0.1
Mar 20 23:19:22 eragon dnsmasq[27367]: 46 127.0.0.1/40646 forwarded
some.long.non-existent.name to 192.168.5.1
Mar 20 23:19:22 eragon dnsmasq[27367]: 46 127.0.0.1/40646 reply
some.long.non-existent.name is NXDOMAIN
Mar 20 23:19:22 eragon dnsmasq[27367]: 47 127.0.0.1/52417 query[A]
some.long.non-existent.name.sebunger.dnsalias.org from 127.0.0.1
Mar 20 23:19:22 eragon dnsmasq[27367]: 47 127.0.0.1/52417 forwarded
some.long.non-existent.name.sebunger.dnsalias.org to 192.168.5.1
Mar 20 23:19:23 eragon dnsmasq[27367]: 47 127.0.0.1/52417 reply
some.long.non-existent.name.sebunger.dnsalias.org is
Mar 20 23:19:23 eragon dnsmasq[27367]: 47 127.0.0.1/52417 reply
sebunger.dnsalias.org is 203.173.156.30
My /etc/resolv.conf (which is a sym-link to ../run/resolvconf/resolv.conf
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
nameserver 127.0.1.1
search sebunger.dnsalias.org
options ndots:1
(I added the options ndots with no effect)
---
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-id',
'/dev/snd/by-path', '/dev/snd/pcmC1D0c', '/dev/snd/controlC1',
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1c',
'/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p',
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
DistroRelease: Ubuntu 16.04
EcryptfsInUse: Yes
IwConfig:
enp2s0no wireless extensions.
lono wireless extensions.
MachineType: Gigabyte Technology Co., Ltd. GA-MA770-UD3
NonfreeKernelModules: nvidia_uvm nvidia
Package: linux (not installed)
ProcFB:
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-66-generic
root=/dev/mapper/vg0-root ro rootdelay=120 quiet splash
ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-4.4.0-66-generic N/A
linux-backports-modules-4.4.0-66-generic N/A
linux-firmware1.157.8
RfKill:
Tags: xenial xenial
Uname: Linux 4.4.0-66-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm audio cdrom dialout dip floppy kvm lpadmin plugdev sambashare
ssh sudo users video
_MarkForUpload: True
dmi.bios.date: 06/12/2009
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: FB
dmi.board.name: GA-MA770-UD3
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias:
[Kernel-packages] [Bug 1943464] Re: Reassign I/O Path of ConnectX-5 Port 1 before Port 2 causes NULL dereference
** Description changed: + SRU Justification: + + [Impact] + + * After reassigning a PCHID of a ConnectX-5 based RoCE Adapter + from one physical LPAR to another, + running Ubuntu 20.04 with kernel 5.4 (latest), + a lifetime issue occurs. + + * Subsequent testing on newer kernels now shows that a + NULL pointer dereference in the zPCI code happens (causing a hard crash) + that was previously hidden by leaking the struct pci_dev. + + * For a more detailed root cause analysis, see the below original bug description. + + [Fix] + + The following three commits fix this issue in focal: + + * upstream (since v5.12-rc4): + 0b13525c20febcfecccf6fc1db5969727401317d 0b13525c20fe "s390/pci: fix leak of PCI device structure" + backport: https://launchpadlibrarian.net/566161494/0001-s390-pci-fix-leak-of-PCI-device-structure.patch + + * upstream (since v5.14-rc7): + 2a671f77ee49f3e78997b77fdee139467ff6a598 2a671f77ee49 "s390/pci: fix use after free of zpci_dev" + backport: https://launchpadlibrarian.net/566161496/0002-s390-pci-fix-use-after-free-of-zpci_dev.patch + + * upstream (since v5.15-rc5): + a46044a92add6a400f4dada7b943b30221f7cc80 a46044a92add "s390/pci: fix zpci_zdev_put() on reserve" + backport: https://launchpadlibrarian.net/566161497/0003-s390-pci-fix-zpci_zdev_put-on-reserve.patch + + * Commit 0b13525c20fe fixes a lifetime issue of the struct pci_dev that was not released on removal, + commit 2a671f77ee49 fixes the 'NULL pointer dereference' (causing the hard crash) itself. + and commit a46044a92add fixes the handling of multiple events for a single reserve state transition of the device. + Without this, the NULL dereference can still be triggered as Reassign I/O Path causes a redudant second removal event. + + * Since none of the three upstream commits does apply cleanly to focal master-next by just cherry-picking them + (mainly due to changes in the context), the above backports are needed. + + [Test Case] + + * Two z15 or LinuxONE III LPARs, one with a Connect-X5 based RoCE + adapter attached. + + * LPARs need to run Ubuntu 20.04 with kernel 5.4 to hit the lifetime issue + (that hides the also potential existing 'NULL pointer dereference') - + with Hirsute and kernel 5.11 the 'NULL pointer dereference' crash occurs. + + * Now change the PCHID (physical channel identifier) + to a different one from the 2nd LPAR (at the HMC?). + + * Verify if the reassignment worked properly (by checking the PCHID) and + monitor the kernel ring buffer dmesg (diagnostic messages) for + "Krnl PSW" crash (caused by NULL pointer) + (for more error details, please see below original bug description). + + * Due hardware availability reasons (the ConnectX-5 cards are only used in special cases), + the testing needs to be done by IBM. + + [Regression Potential / What can go wrong] + + * What can go wrong with: 2a671f77ee49 "s390/pci: fix use after free of + zpci_dev" + + * The reference count to the struct zpci_dev got increased + while it is used by the PCI core. + This could cause a leak if not properly released. + + * Hot-plug of there Connect-X5 devices could be broken on s390x entirely, + in case the new pointer handing is erroneous. + + * This may even have an impact on "cold plug", too. + + * Fortunately the modifications are quite minimal and thereby traceable, + + * and affect /arch/s390/pci/pci.c and arch/s390/pci/pci_bus.h only, + hence are specific to the s390x platform only + and there again to "plugging" of zPCI devices. + + * What can go wrong with: 0b13525c20fe "s390/pci: fix leak of PCI device + structure" + + * The function zpci_remove_device got expanded with an additional set_error argument, + and the internal flow got significantly changed. + In case handled in a wrong way, this may harm the entire remove/release logic. + + * The calls of zpci_remove_device need to be adjusted (as part of the new arg), + failures here will most likely be identified at compile time. + + * The initialization of the pci_dev struct got improved, + + * and the flow in __zpci_event_availability carefully changed + to reflect the device slot/bus remove characteristics. + However, issues here may lead again to general zpci hotplug removal issues. + + * Fortunately all modifications are limited to s390x only (/arch/s390/* + and /drivers/pci/hotplug/s390*) obviously affect zpci devices only + (and no ccw devices). + + [Other] + + * jammy, the current release in development, has all three commits + included. + + * impish and hirsute already incl. "s390/pci: fix leak of PCI device structure" + and "s390/pci: fix use after free of zpci_dev"; + "s390/pci: fix zpci_zdev_put() on reserve" is tagged for upstream stable v5.14.x / v5.10.x + (see https://lore.kernel.org/stable/31dcc776244843aa76deebd49f4ba3fbe4819990.ca...@linux.ibm.com/) + and since we pick up v5.14.x / v5.10.x for the Ubuntu hirsute and impish
[Kernel-packages] [Bug 1948767] Re: Fail to detect audio output from external monitor
This bug is awaiting verification that the linux-oem-5.13/5.13.0-1019.23
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-focal' to 'verification-done-focal'. If the
problem still exists, change the tag 'verification-needed-focal' to
'verification-failed-focal'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: verification-needed-focal
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.14 in Ubuntu.
https://bugs.launchpad.net/bugs/1948767
Title:
Fail to detect audio output from external monitor
Status in HWE Next:
New
Status in linux package in Ubuntu:
Incomplete
Status in linux-oem-5.13 package in Ubuntu:
New
Status in linux-oem-5.14 package in Ubuntu:
New
Status in linux source package in Focal:
Incomplete
Status in linux-oem-5.13 source package in Focal:
Fix Committed
Status in linux-oem-5.14 source package in Focal:
Fix Committed
Status in linux source package in Hirsute:
In Progress
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:
In Progress
Status in linux-oem-5.13 source package in Impish:
Invalid
Status in linux-oem-5.14 source package in Impish:
Invalid
Bug description:
[SRU Justification]
[Impact]
Few recent AMD systems shows "snd_hda_intel :00:1f.3: azx_get_response
timeout" and fail to detect the HDMI/DP audio output device when connects to
external monitor. It will work magically when re-loading the driver.
[Fix]
Backport the upstream fix c0f1886de7e1 ("Allow repeatedly probing on codec
configuration errors) from 5.15.0 rc. It adds the capability for retrying the
probe upon codec probe errors on the certain AMD platforms.
[Test]
1. Connect the external monitor to particular affected AMD systems with HDMI
or DisplayPort.
2. Go to Audio Settings to check if the HDMI/DP audio output device exist or
not.
[Where problems could occur]
Should be low risk, it adds the chance for retrying codec probe and won't
affect machines which used to work.
== Original Bug Description ==
Can not detect DP audio output
[Steps to reproduce]
1) install dell-bto-focal-fossa-grimer-rkl-X72-20210929-8.iso and boot into OS
2) switch to on-demand mode
3) connect an external monitor via DP Port
4) check sound setting --> Output Device
5) switch to performance mode
6) check sound setting --> Output Device
[Expected result]
System can detect DP audio output when external monitor connected
[Actual result]
Can not detect DP audio output
This issue can be reproduce in on-demand and performance mode.
[Failure rate]
1/1
[Additional information]
CID: 202101-28624
SKU: PRH-DVT-C6
Image: canonical-oem-somerville-focal-amd64-20200502-85+fossa-grimer-rkl+X72
system-manufacturer: Dell Inc.
system-product-name: OptiPlex 5490 AIO
bios-version: 1.4.1
CPU: 11th Gen Intel(R) Core(TM) i7-11700 @ 2.50GHz (16x)
GPU: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device
[8086:4c8a] (rev 04)
01:00.0 3D controller [0302]: NVIDIA Corporation Device [10de:1f99] (rev a1)
kernel-version: 5.14.0-2006-oem
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: gdm1081 F pulseaudio
u 1592 F pulseaudio
CasperMD5CheckResult: skip
DistributionChannelDescriptor:
# This is the distribution channel descriptor for the OEM CDs
# For more information see
http://wiki.ubuntu.com/DistributionChannelDescriptor
canonical-oem-somerville-focal-amd64-20200502-85+fossa-proposed-release+X88
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2021-10-27 (1 days ago)
InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary
20200502-05:58
MachineType: Dell Inc. OptiPlex 5490 AIO
NonfreeKernelModules: nvidia_modeset nvidia
Package: linux (not installed)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1020-oem
root=UUID=d0e48268-091a-436d-8b79-2420e385c5c8 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.10.0-1020.21-oem 5.10.25
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-5.10.0-1020-oem N/A
linux-backports-modules-5.10.0-1020-oem
[Kernel-packages] [Bug 1949050] Re: Fix Screen freeze after resume from suspend with iGPU [1002:6987]
This bug is awaiting verification that the linux-oem-5.13/5.13.0-1019.23 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1949050 Title: Fix Screen freeze after resume from suspend with iGPU [1002:6987] Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux-oem-5.13 package in Ubuntu: New Status in linux-oem-5.14 package in Ubuntu: New Status in linux source package in Focal: Incomplete Status in linux-oem-5.13 source package in Focal: Fix Committed Status in linux-oem-5.14 source package in Focal: Fix Committed Status in linux source package in Hirsute: In Progress Status in linux-oem-5.13 source package in Hirsute: New Status in linux-oem-5.14 source package in Hirsute: New Status in linux source package in Impish: In Progress Status in linux-oem-5.13 source package in Impish: New Status in linux-oem-5.14 source package in Impish: New Bug description: [Impact] Screen freeze after resume from suspend [Fix] Perform proper cleanups on UVD/VCE suspend: powergate enablement, clockgating enablement and dpm disablement. This can fix some hangs observed on suspending when UVD/VCE still using(e.g. issue "pm-suspend" when video is still playing). [Test] 1. Plug AMD RX640/Radeon 540 into the system 2. Connect with DP monitor to iGPU 3. Power on 4. Suspend the system 5. Resume from suspend 6. Do something for a while (terminal, nautilus, gnome-control-center, etc). 7. System could resume normally [Regression Potential] Low To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1949050/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1943464] Re: Reassign I/O Path of ConnectX-5 Port 1 before Port 2 causes NULL dereference
** Also affects: linux (Ubuntu Jammy) Importance: Low Assignee: Skipper Bug Screeners (skipper-screen-team) Status: Fix Released ** Changed in: linux (Ubuntu Impish) Status: Fix Released => In Progress ** Changed in: linux (Ubuntu Focal) Status: Incomplete => 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/1943464 Title: Reassign I/O Path of ConnectX-5 Port 1 before Port 2 causes NULL dereference Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: In Progress Status in linux source package in Hirsute: In Progress Status in linux source package in Impish: In Progress Status in linux source package in Jammy: Fix Released Bug description: After reassign RoCE ConnectX-5 Card Pchid to another LPAR dmesg show under Ubuntu the following Error message Ubuntu 20.04.01 with updates oot@t35lp02:~# uname -a Linux t35lp02.lnxne.boe 5.4.0-80-generic #90-Ubuntu SMP Fri Jul 9 17:41:33 UTC 2021 s390x s390x s390x GNU/Linux root@t35lp02:~# DMESG Output 761.778422] mlx5_core 0018:00:00.1: poll_health:715:(pid 0): Fatal error 1 detected [ 761.778432] mlx5_core 0018:00:00.1: print_health_info:381:(pid 0): assert_var[0] 0x [ 761.778435] mlx5_core 0018:00:00.1: print_health_info:381:(pid 0): assert_var[1] 0x [ 761.778437] mlx5_core 0018:00:00.1: print_health_info:381:(pid 0): assert_var[2] 0x [ 761.778439] mlx5_core 0018:00:00.1: print_health_info:381:(pid 0): assert_var[3] 0x [ 761.778442] mlx5_core 0018:00:00.1: print_health_info:381:(pid 0): assert_var[4] 0x [ 761.778444] mlx5_core 0018:00:00.1: print_health_info:384:(pid 0): assert_exit_ptr 0x [ 761.778447] mlx5_core 0018:00:00.1: print_health_info:386:(pid 0): assert_callra 0x [ 761.778451] mlx5_core 0018:00:00.1: print_health_info:389:(pid 0): fw_ver 65535.65535.65535 [ 761.778454] mlx5_core 0018:00:00.1: print_health_info:390:(pid 0): hw_id 0x [ 761.778456] mlx5_core 0018:00:00.1: print_health_info:391:(pid 0): irisc_index 255 [ 761.778460] mlx5_core 0018:00:00.1: print_health_info:392:(pid 0): synd 0xff: unrecognized error [ 761.778462] mlx5_core 0018:00:00.1: print_health_info:394:(pid 0): ext_synd 0x [ 761.778465] mlx5_core 0018:00:00.1: print_health_info:396:(pid 0): raw fw_ver 0x [ 761.778467] mlx5_core 0018:00:00.1: mlx5_trigger_health_work:696:(pid 0): new health works are not permitted at this stage [ 763.179016] mlx5_core 0018:00:00.1: E-Switch: cleanup [ 768.348431] mlx5_core 0018:00:00.1: mlx5_reclaim_startup_pages:562:(pid 123): FW did not return all pages. giving up... [ 768.348433] [ cut here ] [ 768.348434] FW pages counter is 43318 after reclaiming all pages [ 768.348562] WARNING: CPU: 0 PID: 123 at drivers/net/ethernet/mellanox/mlx5/core/pagealloc.c:567 mlx5_reclaim_startup_pages+0x12c/0x1c0 [mlx5_core] [ 768.348563] Modules linked in: s390_trng chsc_sch eadm_sch vfio_ccw vfio_mdev mdev vfio_iommu_type1 vfio sch_fq_codel drm drm_panel_orientation_quirks i2c_core ip_tables x_tables btrfs zstd_compress zlib_deflate raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 linear dm_service_time mlx5_ib ib_uverbs ib_core pkey qeth_l2 zcrypt crc32_vx_s390 ghash_s390 prng aes_s390 des_s390 libdes sha3_512_s390 sha3_256_s390 sha512_s390 mlx5_core sha256_s390 sha1_s390 sha_common tls mlxfw ptp pps_core zfcp scsi_transport_fc dasd_eckd_mod dasd_mod qeth qdio ccwgroup scsi_dh_emc scsi_dh_rdac scsi_dh_alua dm_multipath [ 768.348586] CPU: 0 PID: 123 Comm: kmcheck Tainted: GW 5.4.0-80-generic #90-Ubuntu [ 768.348586] Hardware name: IBM 8561 T01 703 (LPAR) [ 768.348587] Krnl PSW : 0704c0018000 03ff808d33ac (mlx5_reclaim_startup_pages+0x12c/0x1c0 [mlx5_core]) [ 768.348607]R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:0 AS:3 CC:0 PM:0 RI:0 EA:3 [ 768.348608] Krnl GPRS: 0004 0006 0034 0007 [ 768.348608]0007 fcb4fa00 007b 03e00458fafc [ 768.348609]b7d406f0 4d849c00 b7d00120 0001b6c0 [ 768.348610]f4cb1100 03e00458fe70 03ff808d33a8 03e00458fa50 [ 768.348615] Krnl Code: 03ff808d339c: c0241043larl %r2,03ff80955422 03ff808d33a2: c0e570c7brasl %r14,03ff808c1530 #03ff808d33a8: a7f40001brc 15,03ff808d33aa >03ff808d33ac: e330a5f04012lt %r3,263664(%r10)
[Kernel-packages] [Bug 1912946] Re: [ThinkPad E14 Gen2] Closing the lid does not trigger system suspend - fn keys not working
Can confirm that both issues are present on my Lenovo Ideapad Yoga Slim 7 14ARE05 (AMD) on 21.10. -- 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/1912946 Title: [ThinkPad E14 Gen2] Closing the lid does not trigger system suspend - fn keys not working Status in linux package in Ubuntu: Confirmed Bug description: According to the system settings (see the attached screenshot), the laptop should go to sleep (suspend to RAM) when I close the lid. However, closing the lid has no visible effect. 'systemctl suspend' works OK, choosing 'Leave' -> 'Sleep' in the menu works too. After suspend and resume, closing the lid starts working as expected and is triggering suspend to RAM. So this might be related to BIOS, ACPI or something similar. I am filing this bug against 'linux' package because, perhaps, a quirk could be added in the kernel as a workaround. IIRC, the kernel had a number of quirks to work around BIOS/ACPI problems. A similar issue exists with Fn keys on this machine: they do not work after a boot but start working after I have suspended and resumed the system (checked with Fn+F5/F6 - brightness down/up). Others encountered that too (see [1], [2] below). I suspect it is caused by the same bug in BIOS or ACPI. ThinkPad E14 Gen2 with AMD Ryzen 5 4500U Machine type model: 20T60030RT UEFI BIOS ver: R1AET33W (1.09), the latest version at the moment Embedded controller FW ver. R1AHT33W (1.09) SecureBoot: off OS: Ubuntu 20.10 amd64 Kernel 5.8.0-40-generic. I have also tried the builds of the newer mainline kernels: * 5.9.0-050900-generic from https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.9/amd64/ * 5.10.0-051000-generic from https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.10/amd64/ The issues with lid closing and Fn keys show up there too. [1] https://askubuntu.com/questions/1289640/fn-key-doesnt-work-in-ubuntu-20-04-on-lenovo-thinkpad-e14 [2] https://forums.lenovo.com/t5/Other-Linux-Discussions/Linux-Fn-keys-not-working-Thinkpad-E14-AMD-Gen-2/m-p/5027791 ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-40-generic 5.8.0-40.45 ProcVersionSignature: Ubuntu 5.8.0-40.45-generic 5.8.18 Uname: Linux 5.8.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: alina 1059 F pulseaudio alina 1062 F pipewire-media- /dev/snd/controlC0: alina 1062 F pipewire-media- /dev/snd/seq:alina 1058 F pipewire CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Sun Jan 24 17:09:34 2021 InstallationDate: Installed on 2021-01-18 (6 days ago) InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: LENOVO 20T60030RT ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-40-generic root=UUID=1b0f22fc-c314-411c-87c4-ef7e71326576 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-40-generic N/A linux-backports-modules-5.8.0-40-generic N/A linux-firmware1.190.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/26/2020 dmi.bios.release: 1.9 dmi.bios.vendor: LENOVO dmi.bios.version: R1AET33W (1.09 ) dmi.board.asset.tag: Not Available dmi.board.name: 20T60030RT dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.9 dmi.modalias: dmi:bvnLENOVO:bvrR1AET33W(1.09):bd10/26/2020:br1.9:efr1.9:svnLENOVO:pn20T60030RT:pvrThinkPadE14Gen2:rvnLENOVO:rn20T60030RT:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad E14 Gen 2 dmi.product.name: 20T60030RT dmi.product.sku: LENOVO_MT_20T6_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/1912946/+subscriptions -- Mailing list: https://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 1949304] Re: package bcmwl-kernel-source 6.20.155.1+bdcom-0ubuntu0.0.1 failed to install/upgrade: installed bcmwl-kernel-source package post-installation script subprocess r
I did try that and rebooted still 'no WiFi adapters found'. And when I go into additional drivers 'no drivers available'. I am running a Dell Optiplex 9020 using a WiFi dongle that reportedly works with Window$, Mac and Linux. On 11/3/21 5:14 AM, Jeremy wrote: > You should be able to install the driver from the driver manager or by > using this command in terminal with an ethernet connection > > sudo apt update && sudo apt install bcmwl-kernel-source > -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1949304 Title: package bcmwl-kernel-source 6.20.155.1+bdcom-0ubuntu0.0.1 failed to install/upgrade: installed bcmwl-kernel-source package post- installation script subprocess returned error exit status 10 Status in bcmwl package in Ubuntu: New Bug description: Tried to install on 20.04.3 Ubuntu Gnome andwill not load.Trying to get WiFi on Dell Optiplex 9020 ProblemType: Package DistroRelease: Ubuntu 20.04 Package: bcmwl-kernel-source 6.20.155.1+bdcom-0ubuntu0.0.1 ProcVersionSignature: Ubuntu 5.11.0-38.42~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 AptOrdering: linux-headers-3.5.0-30:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Sun Oct 31 12:38:49 2021 ErrorMessage: installed bcmwl-kernel-source package post-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2021-10-30 (1 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: bcmwl Title: package bcmwl-kernel-source 6.20.155.1+bdcom-0ubuntu0.0.1 failed to install/upgrade: installed bcmwl-kernel-source package post-installation script subprocess returned error exit status 10 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1949304/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1942319] Re: When booting with UEFI, mokvar table and %:.platform keyring must be available
Booted impish lxd vm; enabled proposed and upgraded to the new kvm abi: # uname -a Linux leading-fly 5.13.0-1005-kvm #5-Ubuntu SMP Tue Oct 26 23:55:45 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux # ls /sys/firmware/efi/mok-variables/ MokListRT MokListXRT SbatLevelRT # keyctl list %:.blacklist | head 80 keys in keyring: 252860331: ---lswrv 0 0 blacklist: bin:82db3bceb4f60843ce9d97c3d187cd9b5941cd3de8100e586f2bda5637575f67 676962175: ---lswrv 0 0 blacklist: bin:7827af99362cfaf0717dade4b1bfe0438ad171c15addc248b75bf8caa44bb2c5 1059112409: ---lswrv 0 0 blacklist: bin:8d8ea289cfe70a1c07ab7365cb28ee51edd33cf2506de888fbadd60ebf80481c 990976823: ---lswrv 0 0 blacklist: bin:fddd6e3d29ea84c7743dad4a1bdbc700b5fec1b391f932409086acc71dd6dbd8 772477785: ---lswrv 0 0 blacklist: bin:b97a0889059c035ff1d54b6db53b11b978d9f955247c028b2837d7a04cd9 234365151: ---lswrv 0 0 blacklist: bin:d626157e1d6a718bc124ab8da27cbb65072ca03a7b6b257dbdcbbd60f65ef3d1 812179032: ---lswrv 0 0 blacklist: bin:c409bdac4775add8db92aa22b5b718fb8c94a1462c1fe9a416b95d8a3388c2fc 1025256417: ---lswrv 0 0 blacklist: bin:939aeef4f5fa51e23340c3f2e49048ce8872526afdf752c3a7f3a3f2bc9f6049 442082266: ---lswrv 0 0 blacklist: bin:075eea060589548ba060b2feed10da3c20c7fe9b17cd026b94e8a683b8115238 # keyctl list %:.blacklist | grep asym 73781777: ---lswrv 0 0 asymmetric: Canonical Ltd. Secure Boot Signing: 61482aa2830d0ab2ad5af10b7250da9033ddcef0 # keyctl list %:.platform 3 keys in keyring: 848858004: ---lswrv 0 0 asymmetric: Microsoft Windows Production PCA 2011: a92902398e16c49778cd90f99e4f9ae17c55af53 221029845: ---lswrv 0 0 asymmetric: Canonical Ltd. Master Certificate Authority: ad91990bc22ab1f517048c23b6655a268e345a63 730971307: ---lswrv 0 0 asymmetric: Microsoft Corporation UEFI CA 2011: 13adbf4309bd82709c8cd54f316ed522988a1bd4 mok-variables, blacklist, and platform keyrings are now there. ** Tags removed: verification-needed-impish ** Tags added: verification-done-impish -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1942319 Title: When booting with UEFI, mokvar table and %:.platform keyring must be available Status in linux-kvm package in Ubuntu: Fix Committed Status in linux-kvm source package in Impish: Fix Committed Bug description: [Impact] * When booting with UEFI, mokvar table and %:.platform keyring must be available. These are required for builtin revocation certificates to be present, shim builtin certificates to be present and thus support to signed & verified kexec present. It also allows revocation of signed lrm and livepatch drivers which are trusted by this kernel. * The kvm annotations are very minimal, v3 format, and the parent kernel's annotations are not enforced. [Test Plan] * Check that /sys/firmware/efi/mok-variables/ is available * Check that %:.blacklist keyring is populated $ sudo keyctl list %:.blacklist * Check that %:.platform keyring is populated $ sudo keyctl list %:.platform [Where problems could occur] * Given how small the kvm config is, it is not clear if all of lockdown features are correctly enabled. Specifically measuring and appraising things with integrity framework. It is possible further config changes will be required to make kvm flavour as hardened as generic one. [Other Info] * This issue was discovered whilst working on https://bugs.launchpad.net/bugs/1928679 and https://bugs.launchpad.net/bugs/1932029 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-kvm/+bug/1942319/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1947829] Re: Cannot identified WLAN card MT7921 in Ubunut OS with Install OS complete first OOBE Boot OS
The changes made to linux-firmware 1.201.1 on impish has destablized use of a Gigabyte GC-WB867D-I REV Bluetooth 4.0/Wireless AC/B/G/N Band Dual Frequency 2.4Ghz/5.8Ghz Expansion Card. Under the new linux-firmware 1.201.1, no wifi is available under Gnome in about 80-90% of the boots. Under the prior linux-firmware 1.201 release, the wifi always appears under Gnome. Below are the differences in syslog for the broken linux- firmware 1.201.1 release... Nov 3 04:27:07 home kernel: [ 13.045691] iwlwifi :4d:00.0: enabling device ( -> 0002) Nov 3 04:27:07 home kernel: [ 13.055795] iwlwifi :4d:00.0: loaded firmware version 36.ca7b901d.0 8265-36.ucode op_mode iwlmvm Nov 3 04:27:07 home kernel: [ 13.112172] iwlwifi :4d:00.0: Detected Intel(R) Dual Band Wireless AC 8265, REV=0x230 versus the stable linux-firmware 1.201 release... Nov 3 04:36:53 home kernel: [ 14.482126] iwlwifi :4d:00.0: enabling device ( -> 0002) Nov 3 04:36:53 home kernel: [ 14.492179] iwlwifi :4d:00.0: loaded firmware version 36.ca7b901d.0 8265-36.ucode op_mode iwlmvm Nov 3 04:36:53 home kernel: [ 14.548114] iwlwifi :4d:00.0: Detected Intel(R) Dual Band Wireless AC 8265, REV=0x230 Nov 3 04:36:53 home kernel: [ 14.606163] iwlwifi :4d:00.0: base HW address: 00:28:f8:f9:16:e0 Nov 3 04:36:53 home kernel: [ 14.722166] iwlwifi :4d:00.0 wlp77s0: renamed from wlan0 -- 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/1947829 Title: Cannot identified WLAN card MT7921 in Ubunut OS with Install OS complete first OOBE Boot OS Status in HWE Next: New Status in OEM Priority Project: New Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Focal: Fix Released Status in linux-firmware source package in Impish: Fix Released Bug description: [SRU Justification] [Impact] Sometimes MT7921 may not be probed due to an endless mcu reset: [ 5.789548] mt7921 mcu reset 0 [ 5.790625] mt7921 rx type 0x7 [ 5.790625] mt7921 eid 0x1 ext_eid 0x0 [ 5.790626] mt76_rx_event eid 0x1 ext_eid 0x0 [Fix] WiFi and Bluetooth firmware updates from mainline: * e5a80ef8 linux-firmware: update frimware for mediatek bluetooth chip (MT7921) * d34196f5 linux-firmware: update firmware for MT7921 WiFi device [Test Case] This should fix the mcu reset and wireless/bluetooh devices should be probed successfully. [Where problems could occur] While there is explicit FW API for kernel version compatibility checking, this might introduce some hidden glitches that we don't know yet. [Other Info] MT7921 is supported since Impish 5.13 kernel, and Impish already has the latest Bluetooth firmware, so only the WiFi one is proposed. For oem-5.13 and oem-5.14 in Focal, both firmware updates for Bluetooth and WiFi are required. == original bug report == [Reproduce Steps] 1.Add the wireless card MT7921 to SUT,Install the Ubuntu OS. 2.During OOBE, Open the settings, there is no wireless settings in the panel,and the wifi cannot be used,issue occurred. [Results] Expected Result:The wireless settings should be exists and wifi can be used Actual Result:The wireless settings not exists and wifi can not be used To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1947829/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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
The kernel 5.13.0-20 don't work on my Thinkpad E14 Gen 2 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1945590 Title: Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled Status in linux package in Ubuntu: Confirmed Status in linux source package in Impish: Confirmed Bug description: I installed the Ubuntu 21.10 beta and as soon as I boot I get the kernel panic that I am attaching. I also installed Ubuntu 21.04 and upgraded, as soon as I boot with the 5.13 kernel I get the same problem, disabling the trackpad and trackpoint in the bios the problem disappears. Everything works with the 5.11 kernel. I remain available for further details and sorry for my lack of experience. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-16-generic 5.13.0-16.16 ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pietro 1810 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Sep 30 10:26:10 2021 InstallationDate: Installed on 2021-09-29 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: LENOVO 20TA0033IX ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-16-generic root=UUID=b5ea9465-4cd9-408b-8e30-458acf90181b ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.13.0-16-generic N/A linux-backports-modules-5.13.0-16-generic N/A linux-firmware 1.201 SourcePackage: linux UpgradeStatus: Upgraded to impish on 2021-09-29 (0 days ago) dmi.bios.date: 09/02/2021 dmi.bios.release: 1.43 dmi.bios.vendor: LENOVO dmi.bios.version: R1EET43W(1.43 ) dmi.board.asset.tag: Not Available dmi.board.name: 20TA0033IX dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.43 dmi.modalias: dmi:bvnLENOVO:bvrR1EET43W(1.43):bd09/02/2021:br1.43:efr1.43:svnLENOVO:pn20TA0033IX:pvrThinkPadE14Gen2:skuLENOVO_MT_20TA_BU_Think_FM_ThinkPadE14Gen2:rvnLENOVO:rn20TA0033IX:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad E14 Gen 2 dmi.product.name: 20TA0033IX dmi.product.sku: LENOVO_MT_20TA_BU_Think_FM_ThinkPad E14 Gen 2 dmi.product.version: ThinkPad E14 Gen 2 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945590/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1949304] Re: package bcmwl-kernel-source 6.20.155.1+bdcom-0ubuntu0.0.1 failed to install/upgrade: installed bcmwl-kernel-source package post-installation script subprocess retur
You should be able to install the driver from the driver manager or by using this command in terminal with an ethernet connection sudo apt update && sudo apt install bcmwl-kernel-source -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1949304 Title: package bcmwl-kernel-source 6.20.155.1+bdcom-0ubuntu0.0.1 failed to install/upgrade: installed bcmwl-kernel-source package post- installation script subprocess returned error exit status 10 Status in bcmwl package in Ubuntu: New Bug description: Tried to install on 20.04.3 Ubuntu Gnome andwill not load.Trying to get WiFi on Dell Optiplex 9020 ProblemType: Package DistroRelease: Ubuntu 20.04 Package: bcmwl-kernel-source 6.20.155.1+bdcom-0ubuntu0.0.1 ProcVersionSignature: Ubuntu 5.11.0-38.42~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 AptOrdering: linux-headers-3.5.0-30:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Sun Oct 31 12:38:49 2021 ErrorMessage: installed bcmwl-kernel-source package post-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2021-10-30 (1 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: bcmwl Title: package bcmwl-kernel-source 6.20.155.1+bdcom-0ubuntu0.0.1 failed to install/upgrade: installed bcmwl-kernel-source package post-installation script subprocess returned error exit status 10 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1949304/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1912052]
The model should be detected automatically. The parameter is just for
override useful for tests.
If you can, could you test this code change?
diff --git a/sound/pci/hda/patch_realtek.c b/sound/pci/hda/patch_realtek.c
index 6322fac9e694..4f46cfc5393b 100644
--- a/sound/pci/hda/patch_realtek.c
+++ b/sound/pci/hda/patch_realtek.c
@@ -8485,6 +8485,7 @@ static const struct snd_pci_quirk alc269_fixup_tbl[] = {
SND_PCI_QUIRK(0x1025, 0x1308, "Acer Aspire Z24-890",,
ALC286_FIXUP_ACER_AIO_HEADSET_MIC),
SND_PCI_QUIRK(0x1025, 0x132a, "Acer TravelMate B114-21",
ALC233_FIXUP_ACER_HEADSET_MIC),
SND_PCI_QUIRK(0x1025, 0x1330, "Acer TravelMate X514-51T",
ALC255_FIXUP_ACER_HEADSET_MIC),
+ SND_PCI_QUIRK(0x1025, 0x141f, "Acer Acer Spin SP513-54N",
ALC255_FIXUP_ACER_MIC_NO_PRESENCE),
SND_PCI_QUIRK(0x1025, 0x142b, "Acer Swift SF314-42",
ALC255_FIXUP_ACER_MIC_NO_PRESENCE),
SND_PCI_QUIRK(0x1025, 0x1430, "Acer TravelMate B311R-31",
ALC256_FIXUP_ACER_MIC_NO_PRESENCE),
SND_PCI_QUIRK(0x1025, 0x1466, "Acer Aspire A515-56",
ALC255_FIXUP_ACER_HEADPHONE_AND_MIC),
--
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/1912052
Title:
[Acer Spin 5 - SP513-54N] External headset microphone not working on
Ubuntu 21.04 (not even wired, cable headset)
Status in Linux:
Confirmed
Status in linux package in Ubuntu:
Confirmed
Bug description:
Recently, external microphone has stopped working while using classic
wired audio combo jack headset.
Basics:
1) Headset's microphone works fine both in MS Windows on the same machine and
on older Xubuntu on another machine.
2) Internal laptop mic works normally.
3) Yes, I have mic unmuted in settings.
I've followed whole step1 from this troubleshoot guide:
https://help.ubuntu.com/community/SoundTroubleshootingProcedure
Did not help.
There are more information with screenshots here:
https://askubuntu.com/questions/1305942/external-headset-microphone-
not-working-on-ubuntu-20-10-not-even-wired-cable-h:
ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: pulseaudio 1:13.99.2-1ubuntu2.1
ProcVersionSignature: Ubuntu 5.8.0-38.43-generic 5.8.18
Uname: Linux 5.8.0-38-generic x86_64
ApportVersion: 2.20.11-0ubuntu50.3
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: crysman2301 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sat Jan 16 13:31:13 2021
InstallationDate: Installed on 2020-06-19 (210 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
SourcePackage: pulseaudio
UpgradeStatus: Upgraded to groovy on 2020-12-08 (38 days ago)
dmi.bios.date: 07/17/2020
dmi.bios.release: 1.5
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V1.05
dmi.board.name: Caboom_IL
dmi.board.vendor: IL
dmi.board.version: V1.05
dmi.chassis.type: 31
dmi.chassis.vendor: Acer
dmi.chassis.version: V1.05
dmi.ec.firmware.release: 1.2
dmi.modalias:
dmi:bvnInsydeCorp.:bvrV1.05:bd07/17/2020:br1.5:efr1.2:svnAcer:pnSpinSP513-54N:pvrV1.05:rvnIL:rnCaboom_IL:rvrV1.05:cvnAcer:ct31:cvrV1.05:
dmi.product.family: Spin 5
dmi.product.name: Spin SP513-54N
dmi.product.sku:
dmi.product.version: V1.05
dmi.sys.vendor: Acer
To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1912052/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1912052]
@Jaroslav: OK, I've just tested that. 5) only alc255-acer: ❱ cat /proc/cmdline initrd=\EFI\Pop_OS-a99686bf-c48a-464b-af3a-25f67847049a\initrd.img root=UUID=a99686bf-c48a-464b-af3a-25f67847049a ro quiet splash pci=nocrs snd_hda_intel.model=alc255-acer - internal mic works - external does not :( I've noticed some RED messages in dmesg, though - the latest seem to be relevant: [0.089089] x86/cpu: SGX disabled by BIOS. [0.670858] pci :00:07.0: DPC: RP PIO log size 0 is invalid [0.672459] pci :00:07.1: DPC: RP PIO log size 0 is invalid [0.674048] pci :00:07.2: DPC: RP PIO log size 0 is invalid [0.675635] pci :00:07.3: DPC: RP PIO log size 0 is invalid [ 30.127898] snd_hda_codec_realtek ehdaudio0D0: didn't find PCM for DAI Digital Codec DAI [ 30.127909] snd_hda_codec_realtek ehdaudio0D0: ASoC: error at snd_soc_dai_startup on Digital Codec DAI: -22 [ 30.127915] Digital Playback and Capture: soc_pcm_open() failed (-22) [ 30.127919] HDA Digital: ASoC: dpcm_be_dai_startup() failed at Digital Playback and Capture (-22) [ 30.127922] HDA Digital: dpcm_fe_dai_startup() failed (-22) [ 30.128026] snd_hda_codec_realtek ehdaudio0D0: didn't find PCM for DAI Digital Codec DAI [ 30.128030] snd_hda_codec_realtek ehdaudio0D0: ASoC: error at snd_soc_dai_startup on Digital Codec DAI: -22 [ 30.128034] Digital Playback and Capture: soc_pcm_open() failed (-22) [ 30.128036] HDA Digital: ASoC: dpcm_be_dai_startup() failed at Digital Playback and Capture (-22) [ 30.128039] HDA Digital: dpcm_fe_dai_startup() failed (-22) -- 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/1912052 Title: [Acer Spin 5 - SP513-54N] External headset microphone not working on Ubuntu 21.04 (not even wired, cable headset) Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Recently, external microphone has stopped working while using classic wired audio combo jack headset. Basics: 1) Headset's microphone works fine both in MS Windows on the same machine and on older Xubuntu on another machine. 2) Internal laptop mic works normally. 3) Yes, I have mic unmuted in settings. I've followed whole step1 from this troubleshoot guide: https://help.ubuntu.com/community/SoundTroubleshootingProcedure Did not help. There are more information with screenshots here: https://askubuntu.com/questions/1305942/external-headset-microphone- not-working-on-ubuntu-20-10-not-even-wired-cable-h: ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.2-1ubuntu2.1 ProcVersionSignature: Ubuntu 5.8.0-38.43-generic 5.8.18 Uname: Linux 5.8.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: crysman2301 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jan 16 13:31:13 2021 InstallationDate: Installed on 2020-06-19 (210 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: pulseaudio UpgradeStatus: Upgraded to groovy on 2020-12-08 (38 days ago) dmi.bios.date: 07/17/2020 dmi.bios.release: 1.5 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.05 dmi.board.name: Caboom_IL dmi.board.vendor: IL dmi.board.version: V1.05 dmi.chassis.type: 31 dmi.chassis.vendor: Acer dmi.chassis.version: V1.05 dmi.ec.firmware.release: 1.2 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.05:bd07/17/2020:br1.5:efr1.2:svnAcer:pnSpinSP513-54N:pvrV1.05:rvnIL:rnCaboom_IL:rvrV1.05:cvnAcer:ct31:cvrV1.05: dmi.product.family: Spin 5 dmi.product.name: Spin SP513-54N dmi.product.sku: dmi.product.version: V1.05 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1912052/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1912052]
@jaroslav you RULEZZ! This has, indeed, solved reported problem, now both microphones work! Thanks a lot! SOLUTION SUMMARY: 1) use kernel 5.11+ 2) use `snd_sof_intel_hda_common.hda_model=alc255-acer` kernel boot parameter -- 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/1912052 Title: [Acer Spin 5 - SP513-54N] External headset microphone not working on Ubuntu 21.04 (not even wired, cable headset) Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Recently, external microphone has stopped working while using classic wired audio combo jack headset. Basics: 1) Headset's microphone works fine both in MS Windows on the same machine and on older Xubuntu on another machine. 2) Internal laptop mic works normally. 3) Yes, I have mic unmuted in settings. I've followed whole step1 from this troubleshoot guide: https://help.ubuntu.com/community/SoundTroubleshootingProcedure Did not help. There are more information with screenshots here: https://askubuntu.com/questions/1305942/external-headset-microphone- not-working-on-ubuntu-20-10-not-even-wired-cable-h: ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.2-1ubuntu2.1 ProcVersionSignature: Ubuntu 5.8.0-38.43-generic 5.8.18 Uname: Linux 5.8.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: crysman2301 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jan 16 13:31:13 2021 InstallationDate: Installed on 2020-06-19 (210 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: pulseaudio UpgradeStatus: Upgraded to groovy on 2020-12-08 (38 days ago) dmi.bios.date: 07/17/2020 dmi.bios.release: 1.5 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.05 dmi.board.name: Caboom_IL dmi.board.vendor: IL dmi.board.version: V1.05 dmi.chassis.type: 31 dmi.chassis.vendor: Acer dmi.chassis.version: V1.05 dmi.ec.firmware.release: 1.2 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.05:bd07/17/2020:br1.5:efr1.2:svnAcer:pnSpinSP513-54N:pvrV1.05:rvnIL:rnCaboom_IL:rvrV1.05:cvnAcer:ct31:cvrV1.05: dmi.product.family: Spin 5 dmi.product.name: Spin SP513-54N dmi.product.sku: dmi.product.version: V1.05 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1912052/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1912052]
@jaroslav fresh report here: http://alsa-project.org/db/?f=4fa645dcfb6f79261c362d5510af0ad4e6183548 (while booted with `❱ cat /proc/cmdline initrd=\EFI\Pop_OS-a99686bf-c48a-464b-af3a-25f67847049a\initrd.img root=UUID=a99686bf-c48a-464b-af3a-25f67847049a ro quiet splash pci=nocrs snd_hda_intel.model=alc255-acer ` please, could you navigate me to "the instructions", I've been looking around and have not found what you mean, I will try my best to follow them once I know exactly what to follow, thanks a lot! -- 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/1912052 Title: [Acer Spin 5 - SP513-54N] External headset microphone not working on Ubuntu 21.04 (not even wired, cable headset) Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Recently, external microphone has stopped working while using classic wired audio combo jack headset. Basics: 1) Headset's microphone works fine both in MS Windows on the same machine and on older Xubuntu on another machine. 2) Internal laptop mic works normally. 3) Yes, I have mic unmuted in settings. I've followed whole step1 from this troubleshoot guide: https://help.ubuntu.com/community/SoundTroubleshootingProcedure Did not help. There are more information with screenshots here: https://askubuntu.com/questions/1305942/external-headset-microphone- not-working-on-ubuntu-20-10-not-even-wired-cable-h: ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.2-1ubuntu2.1 ProcVersionSignature: Ubuntu 5.8.0-38.43-generic 5.8.18 Uname: Linux 5.8.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: crysman2301 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jan 16 13:31:13 2021 InstallationDate: Installed on 2020-06-19 (210 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: pulseaudio UpgradeStatus: Upgraded to groovy on 2020-12-08 (38 days ago) dmi.bios.date: 07/17/2020 dmi.bios.release: 1.5 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.05 dmi.board.name: Caboom_IL dmi.board.vendor: IL dmi.board.version: V1.05 dmi.chassis.type: 31 dmi.chassis.vendor: Acer dmi.chassis.version: V1.05 dmi.ec.firmware.release: 1.2 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.05:bd07/17/2020:br1.5:efr1.2:svnAcer:pnSpinSP513-54N:pvrV1.05:rvnIL:rnCaboom_IL:rvrV1.05:cvnAcer:ct31:cvrV1.05: dmi.product.family: Spin 5 dmi.product.name: Spin SP513-54N dmi.product.sku: dmi.product.version: V1.05 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1912052/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1912052]
And you didn't follow my instructions - read them carefully. There is another module and parameters for the SOF driver to set the HDA model. -- 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/1912052 Title: [Acer Spin 5 - SP513-54N] External headset microphone not working on Ubuntu 21.04 (not even wired, cable headset) Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Recently, external microphone has stopped working while using classic wired audio combo jack headset. Basics: 1) Headset's microphone works fine both in MS Windows on the same machine and on older Xubuntu on another machine. 2) Internal laptop mic works normally. 3) Yes, I have mic unmuted in settings. I've followed whole step1 from this troubleshoot guide: https://help.ubuntu.com/community/SoundTroubleshootingProcedure Did not help. There are more information with screenshots here: https://askubuntu.com/questions/1305942/external-headset-microphone- not-working-on-ubuntu-20-10-not-even-wired-cable-h: ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.2-1ubuntu2.1 ProcVersionSignature: Ubuntu 5.8.0-38.43-generic 5.8.18 Uname: Linux 5.8.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: crysman2301 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jan 16 13:31:13 2021 InstallationDate: Installed on 2020-06-19 (210 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: pulseaudio UpgradeStatus: Upgraded to groovy on 2020-12-08 (38 days ago) dmi.bios.date: 07/17/2020 dmi.bios.release: 1.5 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.05 dmi.board.name: Caboom_IL dmi.board.vendor: IL dmi.board.version: V1.05 dmi.chassis.type: 31 dmi.chassis.vendor: Acer dmi.chassis.version: V1.05 dmi.ec.firmware.release: 1.2 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.05:bd07/17/2020:br1.5:efr1.2:svnAcer:pnSpinSP513-54N:pvrV1.05:rvnIL:rnCaboom_IL:rvrV1.05:cvnAcer:ct31:cvrV1.05: dmi.product.family: Spin 5 dmi.product.name: Spin SP513-54N dmi.product.sku: dmi.product.version: V1.05 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1912052/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1912052]
Please, attach new alsa-info.sh output. -- 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/1912052 Title: [Acer Spin 5 - SP513-54N] External headset microphone not working on Ubuntu 21.04 (not even wired, cable headset) Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Recently, external microphone has stopped working while using classic wired audio combo jack headset. Basics: 1) Headset's microphone works fine both in MS Windows on the same machine and on older Xubuntu on another machine. 2) Internal laptop mic works normally. 3) Yes, I have mic unmuted in settings. I've followed whole step1 from this troubleshoot guide: https://help.ubuntu.com/community/SoundTroubleshootingProcedure Did not help. There are more information with screenshots here: https://askubuntu.com/questions/1305942/external-headset-microphone- not-working-on-ubuntu-20-10-not-even-wired-cable-h: ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.2-1ubuntu2.1 ProcVersionSignature: Ubuntu 5.8.0-38.43-generic 5.8.18 Uname: Linux 5.8.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: crysman2301 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jan 16 13:31:13 2021 InstallationDate: Installed on 2020-06-19 (210 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: pulseaudio UpgradeStatus: Upgraded to groovy on 2020-12-08 (38 days ago) dmi.bios.date: 07/17/2020 dmi.bios.release: 1.5 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.05 dmi.board.name: Caboom_IL dmi.board.vendor: IL dmi.board.version: V1.05 dmi.chassis.type: 31 dmi.chassis.vendor: Acer dmi.chassis.version: V1.05 dmi.ec.firmware.release: 1.2 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.05:bd07/17/2020:br1.5:efr1.2:svnAcer:pnSpinSP513-54N:pvrV1.05:rvnIL:rnCaboom_IL:rvrV1.05:cvnAcer:ct31:cvrV1.05: dmi.product.family: Spin 5 dmi.product.name: Spin SP513-54N dmi.product.sku: dmi.product.version: V1.05 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1912052/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1912052]
snd_sof_intel_hda_common.hda_model=alc255-acer not snd_hda_intel.model=alc255-acer -- 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/1912052 Title: [Acer Spin 5 - SP513-54N] External headset microphone not working on Ubuntu 21.04 (not even wired, cable headset) Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Recently, external microphone has stopped working while using classic wired audio combo jack headset. Basics: 1) Headset's microphone works fine both in MS Windows on the same machine and on older Xubuntu on another machine. 2) Internal laptop mic works normally. 3) Yes, I have mic unmuted in settings. I've followed whole step1 from this troubleshoot guide: https://help.ubuntu.com/community/SoundTroubleshootingProcedure Did not help. There are more information with screenshots here: https://askubuntu.com/questions/1305942/external-headset-microphone- not-working-on-ubuntu-20-10-not-even-wired-cable-h: ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.2-1ubuntu2.1 ProcVersionSignature: Ubuntu 5.8.0-38.43-generic 5.8.18 Uname: Linux 5.8.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: crysman2301 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jan 16 13:31:13 2021 InstallationDate: Installed on 2020-06-19 (210 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: pulseaudio UpgradeStatus: Upgraded to groovy on 2020-12-08 (38 days ago) dmi.bios.date: 07/17/2020 dmi.bios.release: 1.5 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.05 dmi.board.name: Caboom_IL dmi.board.vendor: IL dmi.board.version: V1.05 dmi.chassis.type: 31 dmi.chassis.vendor: Acer dmi.chassis.version: V1.05 dmi.ec.firmware.release: 1.2 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.05:bd07/17/2020:br1.5:efr1.2:svnAcer:pnSpinSP513-54N:pvrV1.05:rvnIL:rnCaboom_IL:rvrV1.05:cvnAcer:ct31:cvrV1.05: dmi.product.family: Spin 5 dmi.product.name: Spin SP513-54N dmi.product.sku: dmi.product.version: V1.05 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1912052/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1912052]
Try 'snd_sof_intel_hda_common.hda_model=alc255-acer' kernel parameter and don't modify snd_intel_dspcfg configuration. -- 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/1912052 Title: [Acer Spin 5 - SP513-54N] External headset microphone not working on Ubuntu 21.04 (not even wired, cable headset) Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Recently, external microphone has stopped working while using classic wired audio combo jack headset. Basics: 1) Headset's microphone works fine both in MS Windows on the same machine and on older Xubuntu on another machine. 2) Internal laptop mic works normally. 3) Yes, I have mic unmuted in settings. I've followed whole step1 from this troubleshoot guide: https://help.ubuntu.com/community/SoundTroubleshootingProcedure Did not help. There are more information with screenshots here: https://askubuntu.com/questions/1305942/external-headset-microphone- not-working-on-ubuntu-20-10-not-even-wired-cable-h: ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.2-1ubuntu2.1 ProcVersionSignature: Ubuntu 5.8.0-38.43-generic 5.8.18 Uname: Linux 5.8.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: crysman2301 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jan 16 13:31:13 2021 InstallationDate: Installed on 2020-06-19 (210 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: pulseaudio UpgradeStatus: Upgraded to groovy on 2020-12-08 (38 days ago) dmi.bios.date: 07/17/2020 dmi.bios.release: 1.5 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.05 dmi.board.name: Caboom_IL dmi.board.vendor: IL dmi.board.version: V1.05 dmi.chassis.type: 31 dmi.chassis.vendor: Acer dmi.chassis.version: V1.05 dmi.ec.firmware.release: 1.2 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.05:bd07/17/2020:br1.5:efr1.2:svnAcer:pnSpinSP513-54N:pvrV1.05:rvnIL:rnCaboom_IL:rvrV1.05:cvnAcer:ct31:cvrV1.05: dmi.product.family: Spin 5 dmi.product.name: Spin SP513-54N dmi.product.sku: dmi.product.version: V1.05 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1912052/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1912052]
I've made a new test, currently on POPOS 21.04, kernel 5.13: ❱ uname -rv 5.13.0-7614-generic #14~1631647151~21.04~930e87c-Ubuntu SMP Fri Sep 17 00:24:58 UTC 1) default boot options: - internal mic works, external not 2) changed to intel_dspcfg.dsp_driver + headset-mic: ❱ cat /proc/cmdline initrd=\EFI\Pop_OS-a99686bf-c48a-464b-af3a-25f67847049a\initrd.img root=UUID=a99686bf-c48a-464b-af3a-25f67847049a ro snd_intel_dspcfg.dsp_driver=1 snd_hda_intel.model=headset-mic - neither mic works 3) changed to intel_dspcfg.dsp_driver + alc255-acer = ❱ cat /proc/cmdline initrd=\EFI\Pop_OS-a99686bf-c48a-464b-af3a-25f67847049a\initrd.img root=UUID=a99686bf-c48a-464b-af3a-25f67847049a ro quiet splash snd_intel_dspcfg.dsp_driver=1 snd_hda_intel.model=alc255-acer - external mic is now working (!), when jack is plugged-in, it corerctly asks what device have I connected (headset or headphones?) - internal mic is not working, though :( 4) it (does not) works with pci=nocrs, too: ❱ cat /proc/cmdline initrd=\EFI\Pop_OS-a99686bf-c48a-464b-af3a-25f67847049a\initrd.img root=UUID=a99686bf-c48a-464b-af3a-25f67847049a ro quiet splash pci=nocrs snd_intel_dspcfg.dsp_driver=1 snd_hda_intel.model=alc255-acer So, this solution is not very practical, because when I do not have headset available at the moment, I cannot use internal microphone :( -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1912052 Title: [Acer Spin 5 - SP513-54N] External headset microphone not working on Ubuntu 21.04 (not even wired, cable headset) Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Recently, external microphone has stopped working while using classic wired audio combo jack headset. Basics: 1) Headset's microphone works fine both in MS Windows on the same machine and on older Xubuntu on another machine. 2) Internal laptop mic works normally. 3) Yes, I have mic unmuted in settings. I've followed whole step1 from this troubleshoot guide: https://help.ubuntu.com/community/SoundTroubleshootingProcedure Did not help. There are more information with screenshots here: https://askubuntu.com/questions/1305942/external-headset-microphone- not-working-on-ubuntu-20-10-not-even-wired-cable-h: ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.2-1ubuntu2.1 ProcVersionSignature: Ubuntu 5.8.0-38.43-generic 5.8.18 Uname: Linux 5.8.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: crysman2301 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jan 16 13:31:13 2021 InstallationDate: Installed on 2020-06-19 (210 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: pulseaudio UpgradeStatus: Upgraded to groovy on 2020-12-08 (38 days ago) dmi.bios.date: 07/17/2020 dmi.bios.release: 1.5 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.05 dmi.board.name: Caboom_IL dmi.board.vendor: IL dmi.board.version: V1.05 dmi.chassis.type: 31 dmi.chassis.vendor: Acer dmi.chassis.version: V1.05 dmi.ec.firmware.release: 1.2 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.05:bd07/17/2020:br1.5:efr1.2:svnAcer:pnSpinSP513-54N:pvrV1.05:rvnIL:rnCaboom_IL:rvrV1.05:cvnAcer:ct31:cvrV1.05: dmi.product.family: Spin 5 dmi.product.name: Spin SP513-54N dmi.product.sku: dmi.product.version: V1.05 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1912052/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
