[Kernel-packages] [Bug 1949532] Re: ubuntu_ltp_controllers tests failing on Impish
** Description changed: 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's an issue with the transition to - cgroup-v2, which on the ltp mailing list has been rumored that one of - these days the tests would break. Its likely this was caused by a - systemd update, switching to cgroup-v2 causing these tests to break due - to different mount and cgroup hierarchy semantics. + 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. - After setting systemd.unified_cgroup_hierarchy=0 on the kernel command - line which sets cgroup back to v1, we get the expected failures that we - saw in previous cycles, pointing to this not being a kernel regression. + 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. -- 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 1945590] Re: Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled
@mark-harfouche, that did the trick for me, thanks. So no need to change the bios, the latest impish kernel 5.13.0-20 boots on my E15 Ryzen Thinkpad and the touchpad is functional. -- 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 1935850] Re: Dell XPS 17 (9710) PCI/internal sound card not detected
It appears that if I switch from Wayland to X in Ubuntu 21.10 (Impish Indri), the audio works fine, including wired headphones. Is this a problem with Wayland somehow or just coincidence? -- 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/1935850 Title: Dell XPS 17 (9710) PCI/internal sound card not detected Status in linux package in Ubuntu: Fix Released Status in linux source package in Hirsute: Fix Released Status in linux source package in Impish: Fix Released Bug description: This patch is for soundwire audio, and only ubuntu 5.11-generic and later kernels support soundwire audio driver, so this patch is not sent to groovy and focal kernels. For oem-5.10 and oem-5.13 kernels, since this bug is not from OEM project, it is not urgent to merge this patch to OEM kenrels, after the patch is in the hirsute and impish kernels, the oem kernels will have this patch when syncing with generic kernels. [Impact] On the Dell XPS 17 (9710) machine, the audio card is not detected when booting hirsute or impish kernels. So the audio doesn't work on this machine with ubuntu linux 21.04 or 21.10. [Fix] Backport a upstream patch, this will set the correct codec config for this machine: rt711 for headset, dual rt1308 for spks and rt715 for internal mic. [Test] Booting up with the patched kernel, the audio card is detected, test internal speaker and internal mic, all work well, plug a headset, the headphone and external mic work well too. [Where problems could occur] This change only applis to the Dell machines with the DMI_PRODUCT_SKU equals to "0A5D", if this could introduce the regression, it will make the audio (speaker, internal mic and headset) can't work anymore on the Dell machine with that PRODUCT_SKU, but this possibility is very low, and we tested the patch on the machine, so far no regression is found. No audio/mic from internal speakers/build in microphone running Ubuntu 20.04, 20.10 or 21.04 . Can connect via USB headset and audio will work. Tried suggestions from Dell XPS 17 (9700) but this is the new model and fixes do not work. Currently running 21.04 with proposed. Have tried hirsute-proposed (5.11.0-24-generic) with no luck. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.11.0-24.25-generic 5.11.22 Uname: Linux 5.11.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mblack 1698 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jul 12 11:21:27 2021 InstallationDate: Installed on 2021-07-07 (4 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/15/2021 dmi.bios.release: 1.2 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.0 dmi.board.name: 012MMP dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.0:bd06/15/2021:br1.2:svnDellInc.:pnXPS179710:pvr:rvnDellInc.:rn012MMP:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 17 9710 dmi.product.sku: 0A5D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1935850/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1949329] Autopkgtest regression report (alsa-lib/1.2.4-1.1ubuntu2.1)
All autopkgtests for the newly accepted alsa-lib (1.2.4-1.1ubuntu2.1) for hirsute have finished running. The following regressions have been reported in tests triggered by the package: osmid/0.8.0~repack-2 (amd64) cmake/3.18.4-2ubuntu1 (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#alsa-lib [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 alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1949329 Title: [SRU] alsa-lib: ucm: Regex returns correct value without matching a string Status in HWE Next: New Status in alsa-lib package in Ubuntu: Fix Committed Status in alsa-lib source package in Focal: Fix Committed Status in alsa-lib source package in Hirsute: Fix Committed Status in alsa-lib source package in Impish: Fix Committed Status in alsa-lib source package in Jammy: Fix Committed Bug description: [Impact] In the Dell project, we tried to enable the audio on a machine, the machine has the soundwire audio design, it needs to load the ucm correctly, then users could see the audio devices from gnome. But on this machine, the ucm can't be loaded, through debugging, we found this machine has no headset, the Regex returns a wrong value when matching "Regex " hs:([a-z0-9]+(-sdca)?)". If let Regex returns a correct value, the ucm could be loaded successfully. [Fix] Backport a commit from upstream, this commit is merged to upstream from v1.2.5 [Test] After installed the patched libasound2, reboot, we could see the ucm is loaded succesfully on this machine, and open the gnome-sound-setting, we could see the internal mic and internal speaker, and all of them could work normally. [Where problems will occur] This change affect the Regex parser in the ucm, so if it could introduce regression, it will be on the ucm. It could make the audio not work (fail to load ucm and users can't see any audio devices from gnome) on the machines which need ucm. But this possibility is very low, since this commit is backported from upstream and we already tested this backporting on 2 lenovo machines and 2 Dell machines which all need ucm to work. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1949329/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1949329] Re: [SRU] alsa-lib: ucm: Regex returns correct value without matching a string
Focal: Install the Focal on that Dell machine (sdw audio without headset), enable the focal-proposed ppa in the /etc/apt/sources.list, sudo apt-get update, sudo apt install libasound2, the libaousnd2 1.2.2-2.1ubuntu2.5 is installed, reboot, check the gnome-sound-setting, the speaker and internal digital mic show in the UI, this means the pulseaudio loads the correct UCM for this machine. And test playback and recording, all worked well. Verification done on focal. ** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1949329 Title: [SRU] alsa-lib: ucm: Regex returns correct value without matching a string Status in HWE Next: New Status in alsa-lib package in Ubuntu: Fix Committed Status in alsa-lib source package in Focal: Fix Committed Status in alsa-lib source package in Hirsute: Fix Committed Status in alsa-lib source package in Impish: Fix Committed Status in alsa-lib source package in Jammy: Fix Committed Bug description: [Impact] In the Dell project, we tried to enable the audio on a machine, the machine has the soundwire audio design, it needs to load the ucm correctly, then users could see the audio devices from gnome. But on this machine, the ucm can't be loaded, through debugging, we found this machine has no headset, the Regex returns a wrong value when matching "Regex " hs:([a-z0-9]+(-sdca)?)". If let Regex returns a correct value, the ucm could be loaded successfully. [Fix] Backport a commit from upstream, this commit is merged to upstream from v1.2.5 [Test] After installed the patched libasound2, reboot, we could see the ucm is loaded succesfully on this machine, and open the gnome-sound-setting, we could see the internal mic and internal speaker, and all of them could work normally. [Where problems will occur] This change affect the Regex parser in the ucm, so if it could introduce regression, it will be on the ucm. It could make the audio not work (fail to load ucm and users can't see any audio devices from gnome) on the machines which need ucm. But this possibility is very low, since this commit is backported from upstream and we already tested this backporting on 2 lenovo machines and 2 Dell machines which all need ucm to work. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1949329/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1949329] Re: [SRU] alsa-lib: ucm: Regex returns correct value without matching a string
Hirsute: Install the Hirsute on that Dell machine (sdw audio without headset), enable the hirsute-proposed ppa in the /etc/apt/sources.list, sudo apt- get update, sudo apt install libasound2, the libaousnd2 1.2.4-1.1ubuntu2.1 is installed, reboot, check the gnome-sound-setting, the speaker and internal digital mic show in the UI, this means the pulseaudio loads the correct UCM for this machine. And test playback and recording, all worked well. Verification done on hirsute. ** Tags removed: verification-needed-hirsute ** Tags added: verification-done-hirsute -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1949329 Title: [SRU] alsa-lib: ucm: Regex returns correct value without matching a string Status in HWE Next: New Status in alsa-lib package in Ubuntu: Fix Committed Status in alsa-lib source package in Focal: Fix Committed Status in alsa-lib source package in Hirsute: Fix Committed Status in alsa-lib source package in Impish: Fix Committed Status in alsa-lib source package in Jammy: Fix Committed Bug description: [Impact] In the Dell project, we tried to enable the audio on a machine, the machine has the soundwire audio design, it needs to load the ucm correctly, then users could see the audio devices from gnome. But on this machine, the ucm can't be loaded, through debugging, we found this machine has no headset, the Regex returns a wrong value when matching "Regex " hs:([a-z0-9]+(-sdca)?)". If let Regex returns a correct value, the ucm could be loaded successfully. [Fix] Backport a commit from upstream, this commit is merged to upstream from v1.2.5 [Test] After installed the patched libasound2, reboot, we could see the ucm is loaded succesfully on this machine, and open the gnome-sound-setting, we could see the internal mic and internal speaker, and all of them could work normally. [Where problems will occur] This change affect the Regex parser in the ucm, so if it could introduce regression, it will be on the ucm. It could make the audio not work (fail to load ucm and users can't see any audio devices from gnome) on the machines which need ucm. But this possibility is very low, since this commit is backported from upstream and we already tested this backporting on 2 lenovo machines and 2 Dell machines which all need ucm to work. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1949329/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1949329] Re: [SRU] alsa-lib: ucm: Regex returns correct value without matching a string
Impish: Install the impish on that Dell machine (sdw audio without headset), enable the impish-proposed ppa in the /etc/apt/sources.list, sudo apt- get update, sudo apt install libasound2, reboot, check the gnome-sound- setting, the speaker and internal digital mic show in the UI, this means the pulseaudio loads the correct UCM for this machine. And test playback and recording, all worked well. Verification done on impish. ** 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 alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1949329 Title: [SRU] alsa-lib: ucm: Regex returns correct value without matching a string Status in HWE Next: New Status in alsa-lib package in Ubuntu: Fix Committed Status in alsa-lib source package in Focal: Fix Committed Status in alsa-lib source package in Hirsute: Fix Committed Status in alsa-lib source package in Impish: Fix Committed Status in alsa-lib source package in Jammy: Fix Committed Bug description: [Impact] In the Dell project, we tried to enable the audio on a machine, the machine has the soundwire audio design, it needs to load the ucm correctly, then users could see the audio devices from gnome. But on this machine, the ucm can't be loaded, through debugging, we found this machine has no headset, the Regex returns a wrong value when matching "Regex " hs:([a-z0-9]+(-sdca)?)". If let Regex returns a correct value, the ucm could be loaded successfully. [Fix] Backport a commit from upstream, this commit is merged to upstream from v1.2.5 [Test] After installed the patched libasound2, reboot, we could see the ucm is loaded succesfully on this machine, and open the gnome-sound-setting, we could see the internal mic and internal speaker, and all of them could work normally. [Where problems will occur] This change affect the Regex parser in the ucm, so if it could introduce regression, it will be on the ucm. It could make the audio not work (fail to load ucm and users can't see any audio devices from gnome) on the machines which need ucm. But this possibility is very low, since this commit is backported from upstream and we already tested this backporting on 2 lenovo machines and 2 Dell machines which all need ucm to work. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1949329/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1949497] Re: [amdgpu] AMD R5 M430 dGPU freezes
Thanks for the bug report. Please try each of these separately: -- Edit /etc/environment and add: MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0 then reboot. -- Select 'Ubuntu on Xorg' on the login screen. -- ** Summary changed: - AMD R5 M430 dGPU freezes + [amdgpu] AMD R5 M430 dGPU freezes ** Package changed: xorg (Ubuntu) => linux (Ubuntu) ** Tags added: amdgpu ** Tags added: hybrid i915 ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Summary changed: - [amdgpu] AMD R5 M430 dGPU freezes + [amdgpu] AMD R5 M430 dGPU freezes ([drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout) -- 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: 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:
[Kernel-packages] [Bug 1922406]
GUys, I have a Samsung laptop with the AX210, so also the ty. I've been running Debian on the laptop on stable, but decided to do a complete new fresh install with the latest testing variant instead. Everything works except iwlwifi has this .pvnm file and if.. .. I remove it, wifi stops working and bluetooth starts fine .. I put it back, bluetooth stops working and wifi starts fine Well. That means I cant have both working at the same time. Any suggestions as to where to begin? Can I somehow make either bluetooth accept pvnm or have wifi ignore it? Regards, Niclas -- 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/1922406 Title: Intel AX210 Wi-Fi card does not work since updating to 1.196 Status in Linux: In Progress Status in linux package in Ubuntu: Incomplete Status in linux-firmware package in Ubuntu: Fix Released Bug description: Running 21.04, updated daily. Since updating the linux-firmware package yesterday, the Wireless card does not work with current kernel (5.11.0-13). The error message is as follows: Apr 02 21:15:18 Lenovo-V15-IIL kernel: iwlwifi :01:00.0: Timeout waiting for PNVM load! Apr 02 21:15:18 Lenovo-V15-IIL kernel: iwlwifi :01:00.0: Failed to start RT ucode: -110 Apr 02 21:15:18 Lenovo-V15-IIL kernel: iwlwifi :01:00.0: iwl_trans_send_cmd bad state = 1 It **does** work with 5.11.0-11 (previous version) Distro: Ubuntu 21.04 (Hirsute Hippo) Machine: Type: Laptop System: LENOVO product: 82C5 v: Lenovo V15-IIL Mobo: LENOVO model: LNVNB161216 v: SDK0J40700 WIN UEFI: LENOVO v: DKCN51WW date: 12/23/2020 CPU: Info: Dual Core model: Intel Core i3-1005G1 bits: 64 type: MT MCP L2 cache: 4 MiB To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1922406/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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] Re: Update the NVIDIA drivers October 2021
This bug was fixed in the package fabric-manager-460 -
460.106.00-0ubuntu1
---
fabric-manager-460 (460.106.00-0ubuntu1) jammy; urgency=medium
* New upstream release (LP: #1948025).
* debian/rules{.defs}:
- Switch to new tarball format.
* debian/templates/nvidia-fabricmanager*.install.in:
- Change source paths.
-- Alberto Milone Fri, 22 Oct 2021
15:48:27 +0200
** Changed in: fabric-manager-460 (Ubuntu)
Status: Triaged => Fix Released
--
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-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-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-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
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:
- Drop buildfix_kernel_5.14.patch.
== 418-server ==
* New upstream release (LP: #1948025).
* debian/templates/dkms_nvidia.conf.in:
- Drop buildfix_kernel_5.14.patch.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fabric-manager-450/+bug/1948025/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help :
[Kernel-packages] [Bug 1949497] [NEW] [amdgpu] AMD R5 M430 dGPU freezes
You have been subscribed to a public bug: 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 ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug freeze impish third-party-packages ubuntu wayland-session -- [amdgpu] AMD R5 M430 dGPU freezes https://bugs.launchpad.net/bugs/1949497 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1838644] Re: [Notebook N7x0WU] Booting into desktop results in flickering
*** This bug is a duplicate of bug 1948778 *** https://bugs.launchpad.net/bugs/1948778 Continued in bug 1948778 (assuming we don't need this one anymore) ** Summary changed: - Booting into desktop results in flickering + [Notebook N7x0WU] Booting into desktop results in flickering ** This bug has been marked a duplicate of bug 1948778 [Notebook N7x0WU] Random black flickers in gnome-shell Wayland sessions -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe in Ubuntu. https://bugs.launchpad.net/bugs/1838644 Title: [Notebook N7x0WU] Booting into desktop results in flickering Status in linux-hwe package in Ubuntu: Confirmed Bug description: Ubuntu 18.04.2 with kernel 5.0.0-23-generic all up to date @ 1/8/2019 On a CLEVO Notebook product: N7x0WU American Megatrends v: 7.009 date: 05/14/2018 After HWE kernel updates to 5.0.0-23-generic booting into desktop gives flickering after few seconds. backlights are also not working (Fn keys brightness) I filed the bug from a recoverymode, as a normal boot i cant escape the flickering ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.0.0-23-generic 5.0.0-23.24~18.04.1 ProcVersionSignature: Ubuntu 5.0.0-23.24~18.04.1-generic 5.0.15 Uname: Linux 5.0.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Aug 1 15:51:10 2019 InstallationDate: Installed on 2019-06-05 (57 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: linux-signed-hwe UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1838644/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1945565] Re: [SRU] Revert amdgpu/renoir firmware
Mario Limonciello (superm1) wrote 8 hours ago: Canonical team - I had some more review with internal guys about this. Here's a better solution: https://patchwork.freedesktop.org/patch/462084/ This will drop the dependency on FW version for this variable by parsing the loaded FW. That will go into 5.16. You can backport that to your OEM kernel to remain compatible to all FW. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1945565 Title: [SRU] Revert amdgpu/renoir firmware Status in OEM Priority Project: Fix Committed Status in linux-firmware package in Ubuntu: Won't Fix Status in linux-firmware source package in Focal: Fix Released Bug description: [Impact] The USB-type-C port is useless when uplug the USB-type-C <-> DP/HDMI/VGA Dongle after the system resumed from S3. [Fix] Revert below change, this issue is gone. commit a543b9c1bfd12e60d962acd48108234481a8581f Author: Alex Deucher Date: Thu Jul 1 12:23:11 2021 +0800 amdgpu: update renoir firmware from 21.20 BugLink: https://bugs.launchpad.net/bugs/1934014 From internal git commit: 8b05e03570818d047d7ea0a7388c89c4192fd20b Signed-off-by: Alex Deucher Signed-off-by: Josh Boyer (backported from commit 56ef642160203f8be7e1334feca4a76852c74bc0) [khfeng: Squashed multiple updates into one commit] Signed-off-by: Kai-Heng Feng Signed-off-by: Timo Aaltonen [Test] Verify S3 on renoir's platforms. [Where problems could occur] Renoir based systems can't resume from s2idle. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1945565/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1949262] Re: Power Savings doesn't turn monitor off on NUC8i5INH
** Summary changed: - Power Savings doesn't turn monitor off in Wayland on NUC8i5INH + Power Savings doesn't turn monitor off on NUC8i5INH -- 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/1949262 Title: Power Savings doesn't turn monitor off on NUC8i5INH Status in linux package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Bug description: On previous versions of Ubuntu, after 5 minutes, my monitor would turn off as per settings. Since I reinstalled fresh 21.10, this is not happening. Screen becomes black and stays powered on. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: xorg 1:7.7+22ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Uname: Linux 5.13.0-20-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Oct 30 08:11:02 2021 DistUpgraded: Fresh install DistroCodename: impish DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Lexa [Radeon 540X/550X/630 / RX 640 / E9171 MCM] [1002:6987] (rev c3) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Lexa [Radeon 540X/550X/630 / RX 640 / E9171 MCM] [8086:2079] InstallationDate: Installed on 2021-10-14 (15 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 1M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M |__ Port 3: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 3: Dev 2, If 1, Class=Human Interface Device, Driver=usbhid, 12M MachineType: Intel(R) Client Systems NUC8i5INH ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-20-generic root=UUID=1e81e0c8-99b9-447b-b8a2-2ebe4bf0eb88 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/17/2021 dmi.bios.release: 5.13 dmi.bios.vendor: Intel Corp. dmi.bios.version: INWHL357.0043.2021.0817.1957 dmi.board.name: NUC8i5INB dmi.board.vendor: Intel Corporation dmi.board.version: K29935-402 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrINWHL357.0043.2021.0817.1957:bd08/17/2021:br5.13:svnIntel(R)ClientSystems:pnNUC8i5INH:pvrK47340-403:skuBXNUC8i5INHPA:rvnIntelCorporation:rnNUC8i5INB:rvrK29935-402:cvnIntelCorporation:ct35:cvr2.0: dmi.product.family: IN dmi.product.name: NUC8i5INH dmi.product.sku: BXNUC8i5INHPA dmi.product.version: K47340-403 dmi.sys.vendor: Intel(R) Client Systems 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/1949262/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1946304] Re: amdgpu: Add initial firmware for navi24 Beige Goby
This bug was fixed in the package linux-firmware - 1.187.20
---
linux-firmware (1.187.20) focal; urgency=medium
* amdgpu: Add initial firmware for Beige Goby (LP: #1946304)
* Update firmware for MT7921 WiFi/Bluetooth (LP: #1947829)
- linux-firmware: update firmware for mediatek bluetooth chip (MT7921)
- linux-firmware: update firmware for mediatek bluetooth chip (MT7921)
- linux-firmware: update firmware for mediatek bluetooth chip (MT7921)
- linux-firmware: update firmware for MT7921 WiFi device
-- Timo Aaltonen Wed, 20 Oct 2021 15:29:05 +0300
** Changed in: linux-firmware (Ubuntu Focal)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1946304
Title:
amdgpu: Add initial firmware for navi24 Beige Goby
Status in HWE Next:
New
Status in linux-firmware package in Ubuntu:
Fix Released
Status in linux-firmware source package in Focal:
Fix Released
Bug description:
[SRU Justification]
[Impact]
New AMD Beige Goby/Navi24 GPU takes new firmware blobs.
[Fix]
Upstream commit 62fd279be67c ("amdgpu: Add initial firmware for Beige
Goby").
[Test Case]
Apply firmware patch and boot with kernel >= v5.14, amdgpu should probe
successfully.
[Where problems could occur]
New hardware. Expecting issues for external monitor hotplug, power
consumption, etc.
[Other Info]
This change is already applied in upstream linux-firmware repo, and since
it depends on kernel >= v5.14, only Focal is nominated for oem-5.14 here.
== original bug report ==
- This GPU is needed for AMD R21M-P50-50
- amdgpu upstream driver already landed kernel v5.14.
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/tree/drivers/gpu/drm/amd/amdgpu/amdgpu_drv.c?h=v5.14#n1216
[git.kernel.org]
/* BEIGE_GOBY */
{0x1002, 0x7420, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_BEIGE_GOBY},
{0x1002, 0x7421, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_BEIGE_GOBY},
{0x1002, 0x7422, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_BEIGE_GOBY},
{0x1002, 0x7423, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_BEIGE_GOBY},
{0x1002, 0x743F, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_BEIGE_GOBY},
- linux-firmware is being under reviewed in
https://lore.kernel.org/linux-
firmware/cadnq5_nnubczwd66tcutevyajrw5x2q2+kurtqws4ahzopw...@mail.gmail.com/T/#u
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1946304/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-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
This bug was fixed in the package linux-firmware - 1.187.20 --- linux-firmware (1.187.20) focal; urgency=medium * amdgpu: Add initial firmware for Beige Goby (LP: #1946304) * Update firmware for MT7921 WiFi/Bluetooth (LP: #1947829) - linux-firmware: update firmware for mediatek bluetooth chip (MT7921) - linux-firmware: update firmware for mediatek bluetooth chip (MT7921) - linux-firmware: update firmware for mediatek bluetooth chip (MT7921) - linux-firmware: update firmware for MT7921 WiFi device -- Timo Aaltonen Wed, 20 Oct 2021 15:29:05 +0300 ** Changed in: linux-firmware (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-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 1949245] Re: AMD ACP 6.x DMIC Supports
SRU sent for review: https://lists.ubuntu.com/archives/kernel- team/2021-November/125381.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1949245 Title: AMD ACP 6.x DMIC Supports Status in HWE Next: In Progress Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.14 source package in Focal: New Bug description: [Impact] AMD's Yellow carp platforms will have an updated ACP IP block (ACP 6.x) which will not work with existing ACP drivers. [Fix] Backport the new driver that is now in linux-next (to be in 5.16) [Test] This is requested by AMD. [Where problems could occur] Low risk. This is a stand-alone driver that does not affect others devices and platforms. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1949245/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1949532] 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 1949532 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/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's an issue with the transition to cgroup-v2, which on the ltp mailing list has been rumored that one of these days the tests would break. Its likely this was caused by a systemd update, switching to cgroup-v2 causing these tests to break due to different mount and cgroup hierarchy semantics. After setting systemd.unified_cgroup_hierarchy=0 on the kernel command line which sets cgroup back to v1, we get the expected failures that we saw in previous cycles, pointing to this not being a kernel regression. 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 1949532] Re: ubuntu_ltp_controllers tests failing on Impish
** Tags added: 5.13 hinted linux-kvm sru-20211018 ubuntu-ltp ubuntu-ltp- controllers ** Changed in: linux (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1949532 Title: ubuntu_ltp_controllers tests failing on Impish Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: New 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's an issue with the transition to cgroup-v2, which on the ltp mailing list has been rumored that one of these days the tests would break. Its likely this was caused by a systemd update, switching to cgroup-v2 causing these tests to break due to different mount and cgroup hierarchy semantics. After setting systemd.unified_cgroup_hierarchy=0 on the kernel command line which sets cgroup back to v1, we get the expected failures that we saw in previous cycles, pointing to this not being a kernel regression. 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 1948025] Re: Update the NVIDIA drivers October 2021
This bug was fixed in the package libnvidia-nscq-450 -
450.156.00-0ubuntu1
---
libnvidia-nscq-450 (450.156.00-0ubuntu1) jammy; urgency=medium
* New upstream release (LP: #1948025).
* debian/rules{.defs}:
- Switch to new tarball format.
- Change path to extract soname.
* debian/templates/libnvidia-nscq-BRANCH.install.in:
- Change source paths.
-- Alberto Milone Fri, 22 Oct 2021
18:02:38 +0200
** Changed in: libnvidia-nscq-450 (Ubuntu)
Status: Triaged => Fix Released
--
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:
Triaged
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-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-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-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
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:
- Drop buildfix_kernel_5.14.patch.
== 418-server ==
* New upstream release (LP: #1948025).
* debian/templates/dkms_nvidia.conf.in:
- Drop buildfix_kernel_5.14.patch.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fabric-manager-450/+bug/1948025/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
[Kernel-packages] [Bug 1949532] 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 1949532 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Tags added: impish -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1949532 Title: ubuntu_ltp_controllers tests failing on Impish Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: New 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's an issue with the transition to cgroup-v2, which on the ltp mailing list has been rumored that one of these days the tests would break. Its likely this was caused by a systemd update, switching to cgroup-v2 causing these tests to break due to different mount and cgroup hierarchy semantics. After setting systemd.unified_cgroup_hierarchy=0 on the kernel command line which sets cgroup back to v1, we get the expected failures that we saw in previous cycles, pointing to this not being a kernel regression. 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 1949532] [NEW] ubuntu_ltp_controllers tests failing on Impish
Public bug reported: 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's an issue with the transition to cgroup-v2, which on the ltp mailing list has been rumored that one of these days the tests would break. Its likely this was caused by a systemd update, switching to cgroup-v2 causing these tests to break due to different mount and cgroup hierarchy semantics. After setting systemd.unified_cgroup_hierarchy=0 on the kernel command line which sets cgroup back to v1, we get the expected failures that we saw in previous cycles, pointing to this not being a kernel regression. ** Affects: ubuntu-kernel-tests Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: 5.13 hinted impish linux-kvm sru-20211018 ubuntu-ltp ubuntu-ltp-controllers ** Also affects: ubuntu-kernel-tests 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/1949532 Title: ubuntu_ltp_controllers tests failing on Impish Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: New 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's an issue with the transition to cgroup-v2, which on the ltp mailing list has been rumored that one of these days the tests would break. Its likely this was caused by a systemd update, switching to cgroup-v2 causing these tests to break due to different mount and cgroup hierarchy semantics. After setting systemd.unified_cgroup_hierarchy=0 on the kernel command line which sets cgroup back to v1, we get the expected failures that we saw in previous cycles, pointing to this not being a kernel regression. 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 1945590] Re: Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled
For clarity, I am able to use the touchpad. Honestly, I'm going to be using the laptop remotely so I can't tell you how smooth it is. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/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
For those that need to boot and the other methods aren't working, I was able to boot by adding the following to the grub command line: ``` psmouse.proto=bare ``` as suggested in https://askubuntu.com/questions/1250841/ubuntu-20-04-elantech-touchpad- not-working It should give those working hard at fixing the underlying issues some breathing room. -- 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 1949245] Re: AMD ACP 6.x DMIC Supports
** Changed in: hwe-next Assignee: (unassigned) => Alex Hung (alexhung) ** Changed in: linux-oem-5.14 (Ubuntu) Assignee: Alex Hung (alexhung) => (unassigned) ** Description changed: [Impact] - AMD's Yellow carp platforms will have an updated ACP IP block (ACP 6.x) - which will not work with existing ACP drivers. + AMD's Yellow carp platforms will have an updated ACP IP block (ACP 6.x) + which will not work with existing ACP drivers. [Fix] - Backport the new driver that is now in linux-next (to be in 5.16) + Backport the new driver that is now in linux-next (to be in 5.16) [Test] - This is requested by AMD. + This is requested by AMD. [Where problems could occur] - Low risk. This is a stand-alone driver that does not affect others devices - and platforms. + Low risk. This is a stand-alone driver that does not affect others + devices and platforms. ** Changed in: hwe-next Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1949245 Title: AMD ACP 6.x DMIC Supports Status in HWE Next: In Progress Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.14 source package in Focal: New Bug description: [Impact] AMD's Yellow carp platforms will have an updated ACP IP block (ACP 6.x) which will not work with existing ACP drivers. [Fix] Backport the new driver that is now in linux-next (to be in 5.16) [Test] This is requested by AMD. [Where problems could occur] Low risk. This is a stand-alone driver that does not affect others devices and platforms. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1949245/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1949329] Please test proposed package
Hello Hui, or anyone else affected, Accepted alsa-lib into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/alsa- lib/1.2.2-2.1ubuntu2.5 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- 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. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1949329 Title: [SRU] alsa-lib: ucm: Regex returns correct value without matching a string Status in HWE Next: New Status in alsa-lib package in Ubuntu: Fix Committed Status in alsa-lib source package in Focal: Fix Committed Status in alsa-lib source package in Hirsute: Fix Committed Status in alsa-lib source package in Impish: Fix Committed Status in alsa-lib source package in Jammy: Fix Committed Bug description: [Impact] In the Dell project, we tried to enable the audio on a machine, the machine has the soundwire audio design, it needs to load the ucm correctly, then users could see the audio devices from gnome. But on this machine, the ucm can't be loaded, through debugging, we found this machine has no headset, the Regex returns a wrong value when matching "Regex " hs:([a-z0-9]+(-sdca)?)". If let Regex returns a correct value, the ucm could be loaded successfully. [Fix] Backport a commit from upstream, this commit is merged to upstream from v1.2.5 [Test] After installed the patched libasound2, reboot, we could see the ucm is loaded succesfully on this machine, and open the gnome-sound-setting, we could see the internal mic and internal speaker, and all of them could work normally. [Where problems will occur] This change affect the Regex parser in the ucm, so if it could introduce regression, it will be on the ucm. It could make the audio not work (fail to load ucm and users can't see any audio devices from gnome) on the machines which need ucm. But this possibility is very low, since this commit is backported from upstream and we already tested this backporting on 2 lenovo machines and 2 Dell machines which all need ucm to work. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1949329/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1949329] Please test proposed package
Hello Hui, or anyone else affected, Accepted alsa-lib into hirsute-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/alsa- lib/1.2.4-1.1ubuntu2.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. ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1949329 Title: [SRU] alsa-lib: ucm: Regex returns correct value without matching a string Status in HWE Next: New Status in alsa-lib package in Ubuntu: Fix Committed Status in alsa-lib source package in Focal: Fix Committed Status in alsa-lib source package in Hirsute: Fix Committed Status in alsa-lib source package in Impish: Fix Committed Status in alsa-lib source package in Jammy: Fix Committed Bug description: [Impact] In the Dell project, we tried to enable the audio on a machine, the machine has the soundwire audio design, it needs to load the ucm correctly, then users could see the audio devices from gnome. But on this machine, the ucm can't be loaded, through debugging, we found this machine has no headset, the Regex returns a wrong value when matching "Regex " hs:([a-z0-9]+(-sdca)?)". If let Regex returns a correct value, the ucm could be loaded successfully. [Fix] Backport a commit from upstream, this commit is merged to upstream from v1.2.5 [Test] After installed the patched libasound2, reboot, we could see the ucm is loaded succesfully on this machine, and open the gnome-sound-setting, we could see the internal mic and internal speaker, and all of them could work normally. [Where problems will occur] This change affect the Regex parser in the ucm, so if it could introduce regression, it will be on the ucm. It could make the audio not work (fail to load ucm and users can't see any audio devices from gnome) on the machines which need ucm. But this possibility is very low, since this commit is backported from upstream and we already tested this backporting on 2 lenovo machines and 2 Dell machines which all need ucm to work. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1949329/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1949329] Re: [SRU] alsa-lib: ucm: Regex returns correct value without matching a string
Hello Hui, or anyone else affected, Accepted alsa-lib into impish-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/alsa- lib/1.2.4-1.1ubuntu3.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. ** Tags added: verification-needed verification-needed-impish ** Tags added: verification-needed-hirsute -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1949329 Title: [SRU] alsa-lib: ucm: Regex returns correct value without matching a string Status in HWE Next: New Status in alsa-lib package in Ubuntu: Fix Committed Status in alsa-lib source package in Focal: Fix Committed Status in alsa-lib source package in Hirsute: Fix Committed Status in alsa-lib source package in Impish: Fix Committed Status in alsa-lib source package in Jammy: Fix Committed Bug description: [Impact] In the Dell project, we tried to enable the audio on a machine, the machine has the soundwire audio design, it needs to load the ucm correctly, then users could see the audio devices from gnome. But on this machine, the ucm can't be loaded, through debugging, we found this machine has no headset, the Regex returns a wrong value when matching "Regex " hs:([a-z0-9]+(-sdca)?)". If let Regex returns a correct value, the ucm could be loaded successfully. [Fix] Backport a commit from upstream, this commit is merged to upstream from v1.2.5 [Test] After installed the patched libasound2, reboot, we could see the ucm is loaded succesfully on this machine, and open the gnome-sound-setting, we could see the internal mic and internal speaker, and all of them could work normally. [Where problems will occur] This change affect the Regex parser in the ucm, so if it could introduce regression, it will be on the ucm. It could make the audio not work (fail to load ucm and users can't see any audio devices from gnome) on the machines which need ucm. But this possibility is very low, since this commit is backported from upstream and we already tested this backporting on 2 lenovo machines and 2 Dell machines which all need ucm to work. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1949329/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1949245] Re: AMD ACP 6.x DMIC Supports
** Tags added: amd oem-priority originate-from-1943460 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1949245 Title: AMD ACP 6.x DMIC Supports Status in HWE Next: New Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.14 source package in Focal: New Bug description: [Impact] AMD's Yellow carp platforms will have an updated ACP IP block (ACP 6.x) which will not work with existing ACP drivers. [Fix] Backport the new driver that is now in linux-next (to be in 5.16) [Test] This is requested by AMD. [Where problems could occur] Low risk. This is a stand-alone driver that does not affect others devices and platforms. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1949245/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1784152] Re: i2c_hid_get_input floods system logs
I am seeing this on my system POP!_OS 21.04. kernel 5.13.0 Would love a fix. It's a brand new Razer Blade 15 Advanced 2021. -- 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 1877226] Re: nvidia - external display unavailable after screen goes to sleep
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-graphics-drivers-440 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-440 in Ubuntu. https://bugs.launchpad.net/bugs/1877226 Title: nvidia - external display unavailable after screen goes to sleep Status in gnome-control-center package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-440 package in Ubuntu: Confirmed Bug description: On ubuntu 20.04 (Linux 5.4.0-29-generic #33-Ubuntu SMP Wed Apr 29 14:32:27 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux) with nvidia proprietary driver 440.64 with an nvidia MX250 (Lenovo T590): 1) Attach monitor via HDMI 2) Monitor is properly detected. Gnome-control-center sees the correct monitor and sets it to join displays. No issue 3) activate lock screen (window key + L) 4) wait for screens to go to sleep 5) wake up screens to login again (external monitor flashes briefly) 6) login 7) system no longer uses external display and returns to single display 8) open gnome-control-center -> displays. Single Display is active 9) Attempt to select join displays 10) Error at the top of gnome-control-center: Changes cannot be applied - This could be due to hardware limitations 11) select mirror - click apply 12) a keep settings dialogue will pop-up briefly before the screen goes blank. When the screen comes back on, both screens come back on, with a new keep settings dialogue. 13) select keep settings. gnome-control-center now shows Joing Displays as being active. not/not mirror. Notes: -changing prime-select to nvidia vs adaptive does not change the issue -setting power profile to performance in nvidia-settings does not change the issue gnome-control-center info: Installed: 1:3.36.1-1ubuntu5 Candidate: 1:3.36.1-1ubuntu5 Version table: *** 1:3.36.1-1ubuntu5 500 500 http://de.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status nvidia-driver-440: Installed: 440.82+really.440.64-0ubuntu6 Candidate: 440.82+really.440.64-0ubuntu6 Version table: *** 440.82+really.440.64-0ubuntu6 500 500 http://de.archive.ubuntu.com/ubuntu focal/restricted amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.1-1ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu May 7 06:16:15 2020 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2020-04-24 (12 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1877226/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1877226] Re: nvidia - external display unavailable after screen goes to sleep
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-control-center (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-440 in Ubuntu. https://bugs.launchpad.net/bugs/1877226 Title: nvidia - external display unavailable after screen goes to sleep Status in gnome-control-center package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-440 package in Ubuntu: Confirmed Bug description: On ubuntu 20.04 (Linux 5.4.0-29-generic #33-Ubuntu SMP Wed Apr 29 14:32:27 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux) with nvidia proprietary driver 440.64 with an nvidia MX250 (Lenovo T590): 1) Attach monitor via HDMI 2) Monitor is properly detected. Gnome-control-center sees the correct monitor and sets it to join displays. No issue 3) activate lock screen (window key + L) 4) wait for screens to go to sleep 5) wake up screens to login again (external monitor flashes briefly) 6) login 7) system no longer uses external display and returns to single display 8) open gnome-control-center -> displays. Single Display is active 9) Attempt to select join displays 10) Error at the top of gnome-control-center: Changes cannot be applied - This could be due to hardware limitations 11) select mirror - click apply 12) a keep settings dialogue will pop-up briefly before the screen goes blank. When the screen comes back on, both screens come back on, with a new keep settings dialogue. 13) select keep settings. gnome-control-center now shows Joing Displays as being active. not/not mirror. Notes: -changing prime-select to nvidia vs adaptive does not change the issue -setting power profile to performance in nvidia-settings does not change the issue gnome-control-center info: Installed: 1:3.36.1-1ubuntu5 Candidate: 1:3.36.1-1ubuntu5 Version table: *** 1:3.36.1-1ubuntu5 500 500 http://de.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status nvidia-driver-440: Installed: 440.82+really.440.64-0ubuntu6 Candidate: 440.82+really.440.64-0ubuntu6 Version table: *** 440.82+really.440.64-0ubuntu6 500 500 http://de.archive.ubuntu.com/ubuntu focal/restricted amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.1-1ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu May 7 06:16:15 2020 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2020-04-24 (12 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1877226/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1877226] Re: nvidia - external display unavailable after screen goes to sleep
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: mutter (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-440 in Ubuntu. https://bugs.launchpad.net/bugs/1877226 Title: nvidia - external display unavailable after screen goes to sleep Status in gnome-control-center package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-440 package in Ubuntu: Confirmed Bug description: On ubuntu 20.04 (Linux 5.4.0-29-generic #33-Ubuntu SMP Wed Apr 29 14:32:27 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux) with nvidia proprietary driver 440.64 with an nvidia MX250 (Lenovo T590): 1) Attach monitor via HDMI 2) Monitor is properly detected. Gnome-control-center sees the correct monitor and sets it to join displays. No issue 3) activate lock screen (window key + L) 4) wait for screens to go to sleep 5) wake up screens to login again (external monitor flashes briefly) 6) login 7) system no longer uses external display and returns to single display 8) open gnome-control-center -> displays. Single Display is active 9) Attempt to select join displays 10) Error at the top of gnome-control-center: Changes cannot be applied - This could be due to hardware limitations 11) select mirror - click apply 12) a keep settings dialogue will pop-up briefly before the screen goes blank. When the screen comes back on, both screens come back on, with a new keep settings dialogue. 13) select keep settings. gnome-control-center now shows Joing Displays as being active. not/not mirror. Notes: -changing prime-select to nvidia vs adaptive does not change the issue -setting power profile to performance in nvidia-settings does not change the issue gnome-control-center info: Installed: 1:3.36.1-1ubuntu5 Candidate: 1:3.36.1-1ubuntu5 Version table: *** 1:3.36.1-1ubuntu5 500 500 http://de.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status nvidia-driver-440: Installed: 440.82+really.440.64-0ubuntu6 Candidate: 440.82+really.440.64-0ubuntu6 Version table: *** 440.82+really.440.64-0ubuntu6 500 500 http://de.archive.ubuntu.com/ubuntu focal/restricted amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.1-1ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu May 7 06:16:15 2020 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2020-04-24 (12 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1877226/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1798363] Re: i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/65535)
*** This bug is a duplicate of bug 1813733 *** https://bugs.launchpad.net/bugs/1813733 Finding now that it doesn't just happen after sleep, but also occurs when a restart is initiated. I'm running kernel 5.13.0-7620 POP!_OS 21.04 -- 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/1798363 Title: i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/65535) Status in Linux: Confirmed Status in linux package in Ubuntu: Fix Released Bug description: Oct 17 20:07:57 blurhy-FX503VD kernel: [ 1133.740053] i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/65535) Oct 17 20:07:57 blurhy-FX503VD kernel: [ 1133.740764] i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/65535) Oct 17 20:07:57 blurhy-FX503VD kernel: [ 1133.741478] i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/65535) Oct 17 20:07:57 blurhy-FX503VD kernel: [ 1133.742205] i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/65535) Oct 17 20:07:57 blurhy-FX503VD kernel: [ 1133.742921] i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/65535) Oct 17 20:07:57 blurhy-FX503VD kernel: [ 1133.743624] i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/65535) Oct 17 20:07:57 blurhy-FX503VD kernel: [ 1133.744321] i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/65535) Oct 17 20:07:57 blurhy-FX503VD kernel: [ 1133.745026] i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/65535) Oct 17 20:07:57 blurhy-FX503VD kernel: [ 1133.745714] i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/65535) Oct 17 20:07:57 blurhy-FX503VD kernel: [ 1133.746420] i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/65535) Lots of these things ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-10-generic 4.18.0-10.11 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: blurhy 2908 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Oct 17 20:07:13 2018 InstallationDate: Installed on 2018-10-10 (6 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20180927) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0b05:1869 ASUSTek Computer, Inc. Bus 001 Device 003: ID 13d3:5666 IMC Networks Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. FX503VD ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic root=UUID=ad490863-aaf6-49d0-8508-514c07335e07 ro nouveau.runpm=0 RelatedPackageVersions: linux-restricted-modules-4.18.0-10-generic N/A linux-backports-modules-4.18.0-10-generic N/A linux-firmware 1.175 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/03/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: FX503VD.302 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: FX503VD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrFX503VD.302:bd10/03/2017:svnASUSTeKCOMPUTERINC.:pnFX503VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnFX503VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: FX dmi.product.name: FX503VD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1798363/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1870971] Re: [amdgpu] (X)ubuntu 20.04 boots to black screen on Lenovo Ideapad L340-17API when in battery mode
I noticed this bug on an Lenovo Ideapad S340-14API. The system runs Mint 20.2 with Kernel 5.4.0.89, but I upgraded, because I had the problem with the previous Mint version as well. Plugging in power supply lets the system boot into graphics mode. It also helps to boot into the rescue mode via grub and then just say resume. -- 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/1870971 Title: [amdgpu] (X)ubuntu 20.04 boots to black screen on Lenovo Ideapad L340-17API when in battery mode Status in linux package in Ubuntu: Confirmed Status in vlc package in Ubuntu: Invalid Bug description: Freshly installed Xubuntu 20.04 shows black screen instead of login screen upon boot on Lenovo Ideapad L340-17API. It is not possible to chvt to text terminal when boot is stuck on black screen. Booting with 'nomodeset' kernel option works properly but is not an option (e.g. screen brightness is not adjustable in this case). Another workaround is to ssh to laptop and run systemctl restart display-manager.service. After 5-10 seconds upon executing this command perfectly working login screen appears. Check dmesg. There is apparently related messages from amdgpu driver: ... апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_crtc_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_crtc_irq_state: crtc is NULL at id :3 апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_crtc_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_crtc_irq_state: crtc is NULL at id :3 апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_crtc_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_crtc_irq_state: crtc is NULL at id :3 апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_crtc_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_crtc_irq_state: crtc is NULL at id :3 апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_pflip_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_pflip_irq_state: crtc is NULL at id :3 апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_pflip_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_pflip_irq_state: crtc is NULL at id :3 апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_pflip_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_pflip_irq_state: crtc is NULL at id :3 апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_pflip_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_pflip_irq_state: crtc is NULL at id :3 апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_vupdate_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_vupdate_irq_state: crtc is NULL at id :3 апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_vupdate_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_vupdate_irq_state: crtc is NULL at id :3 апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_vupdate_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_vupdate_irq_state: crtc is NULL at id :3 апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_vupdate_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_vupdate_irq_state: crtc is NULL at id :3 апр 05 20:46:45 kernel: [drm] recover vram bo from shadow start апр 05 20:46:45 kernel: [drm] recover vram bo from shadow done апр 05 20:46:45 kernel: [drm] Skip scheduling IBs! апр 05 20:46:45 kernel: [ cut here ] апр 05 20:46:45 kernel: WARNING: CPU: 3 PID: 793 at include/linux/dma-fence.h:533 drm_sched_resubmit_jobs+0x152/0x160 [gpu_sched] апр 05 20:46:45 kernel: Modules linked in: cmac algif_hash algif_skcipher af_alg bnep zram nls_iso8859_1 snd_hda_codec_realtek snd_hda_codec_generic ledtrig_audio snd_hda_codec_hdmi snd_hda_intel snd_intel_nhlt snd_hda_codec > апр 05 20:46:45 kernel: CPU: 3 PID: 793 Comm: kworker/3:4 Tainted: G OE 5.4.0-21-generic #25-Ubuntu апр 05 20:46:45 kernel: Hardware name: LENOVO 81LY/LNVNB161216, BIOS ARCN32WW 07/11/2019 апр 05 20:46:45 kernel: Workqueue: events drm_sched_job_timedout [gpu_sched] апр 05 20:46:45 kernel: RIP: 0010:drm_sched_resubmit_jobs+0x152/0x160 [gpu_sched] апр 05 20:46:45 kernel: Code: 41 5c 41 5d 41 5e 41 5f 5d c3 49 8b 46 10 31 c9 48 c7 80 80 00 00 00 00 00 00 00 49 8b 7f 70 31 c0 83 e7 01 74 04 0f 0b eb bf <0f> 0b eb c7 0f 0b eb 8b 66 0f 1f 44 00 00 0f 1f 44 00 00 83 7f 4c апр 05 20:46:45 kernel: RSP: 0018:a4dc806d7d28 EFLAGS: 00010246 апр 05 20:46:45 kernel: RAX: RBX: 0001 RCX: апр 05 20:46:45 kernel: RDX: 8cc9a6fc9180 RSI: 8cc9ac4609f8 RDI: апр 05 20:46:45 kernel: RBP: a4dc806d7d60 R08: 047a R09: 0004 апр 05 20:46:45 kernel: R10: R11: 0001 R12: 8cc9ac463c00 апр 05 20:46:45 kernel: R13: 8cc9a63c7980 R14: 8cc9ac460800 R15: 8cc9a6fc9140 апр 05 20:46:45 kernel: FS: () GS:8cc9b88c() knlGS: апр 05 20:46:45 kernel: CS: 0010 DS: ES: CR0: 80050033 апр 05 20:46:45 kernel: CR2: 7f275ff6c000 CR3: 0001af148000 CR4: 003406e0 апр 05 20:46:45 kernel: Call Trace: апр 05 20:46:45 kernel:
[Kernel-packages] [Bug 1948025] Re: Update the NVIDIA drivers October 2021
This bug was fixed in the package fabric-manager-450 -
450.156.00-0ubuntu1
---
fabric-manager-450 (450.156.00-0ubuntu1) jammy; urgency=medium
* New upstream release (LP: #1948025).
* debian/rules{.defs}:
- Switch to new tarball format.
* debian/templates/nvidia-fabricmanager*.install.in:
- Change source paths.
-- Alberto Milone Fri, 22 Oct 2021
15:54:04 +0200
** Changed in: fabric-manager-450 (Ubuntu)
Status: Triaged => Fix Released
--
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:
Triaged
Status in libnvidia-nscq-450 package in Ubuntu:
Triaged
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-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-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-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
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:
- Drop buildfix_kernel_5.14.patch.
== 418-server ==
* New upstream release (LP: #1948025).
* debian/templates/dkms_nvidia.conf.in:
- Drop buildfix_kernel_5.14.patch.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fabric-manager-450/+bug/1948025/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help :
[Kernel-packages] [Bug 1949516] [NEW] require CAP_NET_ADMIN to attach N_HCI ldisc
Public bug reported: [Impact] Any unprivileged user can attach N_HCI ldisc and send packets coming from a virtual controller by using PTYs. This exposes attack surface on systems where bluetooth is not needed or even allow local attacks that would otherwise require physical proximity. [Test case] Try attaching N_HCI ldisc to a tty. ldattach HCI /dev/tty [Potential regression] Users who rely on programs using N_HCI line discipline in order to emulate or proxy a bluetooth controller will require privilege they may not have. ** Affects: linux (Ubuntu) Importance: Low Assignee: Thadeu Lima de Souza Cascardo (cascardo) Status: In Progress ** Affects: linux (Ubuntu Bionic) Importance: Low Assignee: Thadeu Lima de Souza Cascardo (cascardo) Status: In Progress ** Affects: linux (Ubuntu Focal) Importance: Low Assignee: Thadeu Lima de Souza Cascardo (cascardo) Status: In Progress ** Affects: linux (Ubuntu Hirsute) Importance: Low Assignee: Thadeu Lima de Souza Cascardo (cascardo) Status: In Progress ** Affects: linux (Ubuntu Impish) Importance: Low Assignee: Thadeu Lima de Souza Cascardo (cascardo) Status: In Progress ** Affects: linux (Ubuntu Jammy) Importance: Low Assignee: Thadeu Lima de Souza Cascardo (cascardo) Status: In Progress ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Bionic) Status: New => In Progress ** Changed in: linux (Ubuntu Focal) Status: New => In Progress ** Changed in: linux (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux (Ubuntu Impish) Status: New => In Progress ** Changed in: linux (Ubuntu Hirsute) Status: New => In Progress ** Changed in: linux (Ubuntu Jammy) Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo) ** Changed in: linux (Ubuntu Impish) Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo) ** Changed in: linux (Ubuntu Hirsute) Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo) ** Changed in: linux (Ubuntu Focal) Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo) ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo) ** Changed in: linux (Ubuntu Jammy) Importance: Undecided => Low ** Changed in: linux (Ubuntu Impish) Importance: Undecided => Low ** Changed in: linux (Ubuntu Hirsute) Importance: Undecided => Low ** Changed in: linux (Ubuntu Focal) Importance: Undecided => Low ** Changed in: linux (Ubuntu Bionic) Importance: Undecided => Low -- 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/1949516 Title: require CAP_NET_ADMIN to attach N_HCI ldisc Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Status in linux source package in Focal: In Progress Status in linux source package in Hirsute: In Progress Status in linux source package in Impish: In Progress Status in linux source package in Jammy: In Progress Bug description: [Impact] Any unprivileged user can attach N_HCI ldisc and send packets coming from a virtual controller by using PTYs. This exposes attack surface on systems where bluetooth is not needed or even allow local attacks that would otherwise require physical proximity. [Test case] Try attaching N_HCI ldisc to a tty. ldattach HCI /dev/tty [Potential regression] Users who rely on programs using N_HCI line discipline in order to emulate or proxy a bluetooth controller will require privilege they may not have. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1949516/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1949512] [NEW] Bionic update: upstream stable patchset 2021-11-02
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-02 Ported from the following upstream stable releases: v4.14.249, v4.19.209 from git://git.kernel.org/ ocfs2: drop acl cache for directories too usb: gadget: r8a66597: fix a loop in set_feature() 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 staging: greybus: uart: fix tty use after free Re-enable UAS for LaCie Rugged USB3-FW with fk quirk 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() serial: mvebu-uart: fix driver's tx_empty callback net: hso: fix muxed tty registration bnxt_en: Fix TX timeout when TX ring size is set to the smallest net/mlx4_en: Don't allow aRFS for encapsulated packets scsi: iscsi: Adjust iface sysfs attr detection thermal/core: Potential buffer overflow in thermal_build_list_of_policies() irqchip/gic-v3-its: Fix potential VPE leak on error md: fix a lock order reversal in md_alloc blktrace: Fix uaf in blk_trace access after removing by sysfs net: macb: fix use after free on rmmod net: stmmac: allow CSR clock of 300MHz m68k: Double cast io functions to unsigned long xen/balloon: use a kernel thread instead a workqueue compiler.h: Introduce absolute_pointer macro net: i825xx: Use absolute_pointer for memcpy from fixed memory location sparc: avoid stringop-overread errors qnx4: avoid stringop-overread errors parisc: Use absolute_pointer() to define PAGE0 arm64: Mark __stack_chk_guard as __ro_after_init alpha: Declare virt_to_phys and virt_to_bus parameter as pointer to volatile net: 6pack: Fix tx timeout and slot time spi: Fix tegra20 build with CONFIG_PM=n arm64: dts: marvell: armada-37xx: Extend PCIe MEM space PCI: aardvark: Fix checking for PIO Non-posted Request PCI: aardvark: Fix checking for PIO status xen/balloon: fix balloon kthread freezing qnx4: work around gcc false positive warning bug tty: Fix out-of-bound vmalloc access in imageblit cpufreq: schedutil: Use kobject release() method to free sugov_tunables cpufreq: schedutil: Destroy mutex before kobject_put() frees the memory mac80211: fix use-after-free in CCMP/GCMP RX ipvs: check that ip_vs_conn_tab_bits is between 8 and 20 mac80211: Fix ieee80211_amsdu_aggregate frag_tail bug mac80211: limit injected vht mcs/nss in ieee80211_parse_tx_radiotap sctp: break out if skb_header_pointer returns NULL in sctp_rcv_ootb hwmon: (tmp421) fix rounding for negative values e100: fix length calculation in e100_get_regs_len e100: fix buffer overrun in e100_get_regs scsi: csiostor: Add module softdep on cxgb4 af_unix: fix races in sk_peer_pid and sk_peer_cred accesses ipack: ipoctal: fix stack information leak ipack: ipoctal: fix tty registration race ipack: ipoctal: fix tty-registration error handling ipack: ipoctal: fix missing allocation-failure check ipack: ipoctal: fix module reference leak ext4: fix potential infinite loop in ext4_dx_readdir() net: udp: annotate data race around udp_sk(sk)->corkflag EDAC/synopsys: Fix wrong value type assignment for edac_mode ARM: 9077/1: PLT: Move struct plt_entries definition to header ARM: 9078/1: Add warn suppress parameter to arm_gen_branch_link() ARM: 9079/1: ftrace: Add MODULE_PLTS support ARM: 9098/1: ftrace: MODULE_PLT: Fix build problem without DYNAMIC_FTRACE arm64: Extend workaround for erratum 1024718 to all versions of Cortex-A55 hso: fix bailout in error case of probe usb: hso: fix error handling code of hso_create_net_device usb: hso: remove the bailout parameter crypto: ccp - fix resource leaks in ccp_run_aes_gcm_cmd() HID: betop: fix slab-out-of-bounds Write in betop_probe netfilter: ipset: Fix oversized kvmalloc() calls HID: usbhid: free raw_report buffers in usbhid_stop cred: allow get_cred() and put_cred() to be given NULL. gpio: uniphier: Fix void functions to remove return value tty: synclink_gt, drop unneeded forward declarations tty: synclink_gt: rename a conflicting function name drm/amd/display: Pass PCI deviceid into DC hwmon: (tmp421) Replace S_ with octal values hwmon: (tmp421) report /PVLD condition as fault UBUNTU: upstream stable to v4.14.249,
[Kernel-packages] [Bug 1944586] Re: kernel bug found when disconnecting one fiber channel interface on Cisco Chassis with fnic DRV_VERSION "1.6.0.47"
Thank you, Eric! :) -- 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/1944586 Title: kernel bug found when disconnecting one fiber channel interface on Cisco Chassis with fnic DRV_VERSION "1.6.0.47" Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Committed Bug description: [Impact] It has been brought to my attention the following: " We have been experiencing node lockups and degradation when testing fiber channel fail over for multi-path PURESTORAGE drives. Testing usually consists of either failing over the fabric or the local I/O module for the Cisco chassis which houses a number of individual blades. After rebooting a local Chassis I/O module we see commands like multipath -ll hanging. Resetting the blades individual fiber channel interface results in the following messages. " 6051160.241383] rport-9:0-1: blocked FC remote port time out: removing target and saving binding [6051160.252901] BUG: kernel NULL pointer dereference, address: 0040 [6051160.262267] #PF: supervisor read access in kernel mode [6051160.269314] #PF: error_code(0x) - not-present page [6051160.276016] PGD 0 P4D 0 [6051160.279807] Oops: [#1] SMP NOPTI [6051160.284642] CPU: 10 PID: 49346 Comm: kworker/10:2 Tainted: P O 5.4.0-77-generic #86-Ubuntu [6051160.295967] Hardware name: Cisco Systems Inc UCSB-B200-M5/UCSB-B200-M5, BIOS B200M5.4.1.1d.0.0609200543 06/09/2020 [6051160.308199] Workqueue: fc_dl_9 fc_timeout_deleted_rport [scsi_transport_fc] [6051160.316640] RIP: 0010:fnic_terminate_rport_io+0x10f/0x510 [fnic] [6051160.324050] Code: 48 89 c3 48 85 c0 0f 84 7b 02 00 00 48 05 20 01 00 00 48 89 45 b0 0f 84 6b 02 00 00 48 8b 83 58 01 00 00 48 8b 80 b8 01 00 00 <48> 8b 78 40 e8 68 e6 06 00 85 c0 0f 84 4c 02 00 00 48 8b 83 58 01 [6051160.346553] RSP: 0018:bc224f297d90 EFLAGS: 00010082 [6051160.353115] RAX: RBX: 90abdd4c4b00 RCX: 90d8ab2c2bb0 [6051160.361983] RDX: 90d8b5467400 RSI: RDI: 90d8ab3b4b40 [6051160.370812] RBP: bc224f297df8 R08: 90d8c08978c8 R09: 90d8b8850800 [6051160.379518] R10: 90d8a59d64c0 R11: 0001 R12: 90d8ab2c31f8 [6051160.388242] R13: R14: 0246 R15: 90d8ab2c27b8 [6051160.396953] FS: () GS:90d8c088() knlGS: [6051160.406838] CS: 0010 DS: ES: CR0: 80050033 [6051160.414168] CR2: 0040 CR3: 000fc1c0a004 CR4: 007626e0 [6051160.423146] DR0: DR1: DR2: [6051160.431884] DR3: DR6: fffe0ff0 DR7: 0400 [6051160.440615] PKRU: 5554 [6051160.444337] Call Trace: [6051160.447841] fc_terminate_rport_io+0x56/0x70 [scsi_transport_fc] [6051160.455263] fc_timeout_deleted_rport.cold+0x1bc/0x2c7 [scsi_transport_fc] [6051160.463623] process_one_work+0x1eb/0x3b0 [6051160.468784] worker_thread+0x4d/0x400 [6051160.473660] kthread+0x104/0x140 [6051160.478102] ? process_one_work+0x3b0/0x3b0 [6051160.483439] ? kthread_park+0x90/0x90 [6051160.488213] ret_from_fork+0x1f/0x40 [6051160.492901] Modules linked in: dm_service_time zfs(PO) zunicode(PO) zlua(PO) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) ebtable_filter ebtables ip6table_raw ip6table_mangle ip6table_nat iptable_raw iptable_mangle iptable_nat nf_nat vhost_vsock vmw_vsock_virtio_transport_common vsock unix_diag nf_conntrack_netlink nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 vhost_net vhost tap 8021q garp mrp bluetooth ecdh_generic ecc tcp_diag inet_diag sctp nf_tables nfnetlink ip6table_filter ip6_tables iptable_filter bpfilter bridge stp llc nls_iso8859_1 dm_queue_length dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua intel_rapl_msr intel_rapl_common isst_if_common skx_edac nfit x86_pkg_temp_thermal intel_powerclamp ipmi_ssif coretemp kvm_intel kvm rapl input_leds joydev intel_cstate mei_me ioatdma mei dca ipmi_si ipmi_devintf ipmi_msghandler acpi_power_meter acpi_pad mac_hid sch_fq_codel ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor [6051160.492928] async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear fnic mgag200 drm_vram_helper i2c_algo_bit ttm drm_kms_helper crct10dif_pclmul syscopyarea hid_generic crc32_pclmul libfcoe sysfillrect ghash_clmulni_intel sysimgblt aesni_intel fb_sys_fops crypto_simd libfc usbhid cryptd scsi_transport_fc hid drm glue_helper enic ahci lpc_ich libahci wmi [6051160.632623] CR2: 0040 [6051160.637043] ---[ end trace 236e6f4850146477 ]--- [Test Plan] There are two ways to replicate the bug: Reset a single chassis I/O module or fail over a
[Kernel-packages] [Bug 1945180] Re: vrf: fix refcnt leak with vxlan slaves
Thank you, Samuel! :)
--
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/1945180
Title:
vrf: fix refcnt leak with vxlan slaves
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Bionic:
Fix Committed
Status in linux source package in Focal:
Fix Committed
Bug description:
[Impact]
There are cases, where deleting a VRF device can hang waiting for the refcnt
to drop to 0, with the message:
unregister_netdevice: waiting for vrf1 to become free. Usage count = 1
This is fixed upstream with commit b87b04f5019e ("ipv4: Fix device
used for dst_alloc with local routes"), included in linux v5.13. The
original patch, which has introduced the bug, is included in linux
v4.10.
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=b87b04f5019e
[Test Case]
The upstream patch includes a test case, which describe how to
reproduce the bug.
[Regression Potential]
The patch affects ipv4 routing. It is straightforward, it links new
dst to a vrf device instead of the loopback if needed.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945180/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1949357] Re: linux-azure: make mana.ko built-in
** Changed in: linux-azure (Ubuntu Focal) Status: In Progress => Fix Committed ** Changed in: linux-azure (Ubuntu Hirsute) Status: In Progress => Fix Committed ** Changed in: linux-azure (Ubuntu Impish) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1949357 Title: linux-azure: make mana.ko built-in Status in linux-azure package in Ubuntu: In Progress Status in linux-azure source package in Focal: Fix Committed Status in linux-azure source package in Hirsute: Fix Committed Status in linux-azure source package in Impish: Fix Committed Status in linux-azure source package in Jammy: In Progress Bug description: SRU Justification [Impact] The new networking module mana.ko is not included with linux-modules, rather it is packaged in linux-modules-extra. Instance types that have mana.ko as a boot dependency will not work since Azure images are not created using linux-image-extra. [Test Plan] Download linux-modules and check for mana.ko [Where problems could occur] mana.ko could go missing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1949357/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1947027] Re: hirsute/linux-azure: Backport CIFS patches
** Changed in: linux-azure (Ubuntu Hirsute) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1947027 Title: hirsute/linux-azure: Backport CIFS patches Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Hirsute: Fix Committed Bug description: [SRU Justification] [Impact] Microsoft has asked to backport cifs patches up through v5.15-rc3 from git://git.samba.org/sfrench/cifs-2.6.git 5.11-backport [Test Case] Connect to a SAMBA server [Where things might go wrong] Connections may fail, or have poor performance. [Other Info] SF: #00316229 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1947027/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1040557] Re: UEFI boot live-usb bricks SAMSUNG 530U3C, np700z5c laptop
If you create a new TUI layout, don't include the status window, and then change from a layout with the status window to the new one, gdb crashes. http://www.compilatori.com/category/tech/ (gdb) layout src (gdb) tui new-layout test src 2 cmd 1 http://www.acpirateradio.co.uk/category/tech/ (gdb) layout test http://www.logoarts.co.uk/category/tech/ On Windows I get a STATUS_HEAP_CORRUPTION exception (0xc374). http://www.mconstantine.co.uk/property/netherlands/ It happens because tui_apply_current_layout() deletes all windows that are no longer http://www.go-mk-websites.co.uk/property/miyazaki/ needed, but the status (locator) window is never allocated dynamically. http://www.slipstone.co.uk/category/tech/ If you create a new TUI layout, don't include the status window, and then http://fishingnewsletters.co.uk/health/adrasan/ change from a layout with the status window to the new one, gdb crashes. http://embermanchester.uk/category/tech/ (gdb) layout src (gdb) tui new-layout test src 2 cmd 1 http://connstr.net/category/tech/ (gdb) layout test http://joerg.li/category/tech/ On Windows I get a STATUS_HEAP_CORRUPTION exception (0xc374). It happens because tui_apply http://www.jopspeech.com/category/tech/ _current_layout() deletes all windows that are no longer needed, http://the-hunters.org/services/miui-12-5/ but the status (locator) window is never allocated dynamically. http://www.wearelondonmade.com/category/tech/ If you create a new TUI layout, don't include the status window, and then change from a layout with the status window to the new one, gdb crashes. https://waytowhatsnext.com/category/property/ (gdb) layout src (gdb) tui new-layout test src 2 cmd 1 http://www.iu-bloomington.com/category/property/ (gdb) layout test https://komiya-dental.com/category/property/ On Windows I get a STATUS_HEAP_CORRUPTION exception (0xc374). It happens because tui http://www-look-4.com/category/tech/_apply_current_layout() deletes all windows that are no longer needed, but the status (locator) window is never allocated dynamically. https://www.webb-dev.co.uk/category/property/ -- 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/1040557 Title: UEFI boot live-usb bricks SAMSUNG 530U3C,np700z5c laptop Status in Ubuntu CD Images: Fix Released Status in Release Notes for Ubuntu: Fix Released Status in Release Notes for Ubuntu quantal series: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Oneiric: Fix Released Status in linux source package in Precise: Fix Released Status in linux source package in Quantal: Fix Released Bug description: I cannot provide detailed log massages because laptop is bricked right now. If you have courage to try it select UEFI boot from bios and than try to boot laptop using liveusb (made form Precise Pangolin 12.04.1 amd64). Laptop hangs up in black screen. If you force power-off, after it, laptop wont start. I mean it not event start bios, just black screen no sounds nothing. I filing this report, because i already bricked second laptop. At first i thought it was unrelated issue and laptop was fixed by warranty service (replaced motherboard), but after second time i quite sure. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-cdimage/+bug/1040557/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1876011] Re: Kernel Panic when dasd-fba device is selected for install
This patch fixes a segfault seen when attaching to a process on Solaris. The steps leading to the segfault are: http://www.compilatori.com/tech/xiaomi/ - procfs_target::attach calls do_attach, at this point the inferior's process slot in the target stack is empty. - do_attach adds a thread with `add http://www.acpirateradio.co.uk/tech/forest-fires/ _thread (_procfs_target, ptid)` - in add_thread_silent, the passed target (_procfs_target) is passed to find_inferior_ptid http://www.logoarts.co.uk/tech/drone-cameras/ - find_inferior_ptid returns nullptr, as there is no inferior with this ptid that has _procfs_target as its process target http://www.slipstone.co.uk/tech/express-van/ - the nullptr `inf` is passed to find_thread_ptid, which dereferences it, causing a segfault - back in procfs_target::attach, after do_attach, we push the http://embermanchester.uk/technology/telegram/ the_procfs_target on the inferior's target stack, although we never reach this because the segfault happens before. http://connstr.net/tech/mars-surface/ To fix this, I think we need to do the same as is done in inf_ptrace_target::attach: push the target early and unpush it in case the attach fails (and keep it if the attach succeeds). http://joerg.li/tech/cars-comparison/ Implement it by moving target_unpush_up to target.h, so it can be re-used here. Make procfs_target::attach use it. Note that just like is mentioned http://www.jopspeech.com/tech/xiaomi-headset/ in inf_ptrace_target::attach, we should push the target before calling target_pid_to_str, so that calling target_pid_to_str ends up in procfs_target::pid_to_str. http://www.wearelondonmade.com/tech/driving-assistant/ Tested by trying to attach on a process on gcc211 on the gcc compile farm. https://waytowhatsnext.com/health/vaccination-rates/ gdb/ChangeLog: This patch fixes a segfault seen when attaching to a process on Solaris. The steps leading to the segfault are: http://www.iu-bloomington.com/health/amoled-display/ - procfs_target::attach calls do_attach, at this point the inferior's process slot in the target stack is empty. https://komiya-dental.com/health/telegram-account/ - do_attach adds a thread with `add_thread (_procfs_target, ptid)` - in add_thread_silent, the passed target (_procfs_target) is passed to find_inferior_ptid http://www-look-4.com/services/usb-type-a/ - find_inferior_ptid returns nullptr, as there is no inferior with this ptid that has _procfs_target as its process target - the nullptr `inf` is passed to find_thread_ptid, which dereferences it, causing a segfault https://www.webb-dev.co.uk/property/house-sales-in-2020/ - back in procfs_target::attach, after do_attach, we push the the_procfs_target on the inferior's target stack, although we never reach this because the segfault happens before. To fix this, I think we need to do the same as is done in inf_ptrace_target::attach: push the target early and unpush it in case the attach fails (and keep it if the attach succeeds). -- 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/1876011 Title: Kernel Panic when dasd-fba device is selected for install Status in curtin: Fix Released Status in subiquity: Fix Released Status in Ubuntu on IBM z Systems: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: Stating a zVM install (either subiquity or d-i) and selecting dasd-fba devices leads to a kernel panic. Details from the installer shell before the panic: root@ubuntu-server:/# uname -a Linux ubuntu-server 5.4.0-26-generic #30-Ubuntu SMP Mon Apr 20 16:57:22 UTC 2020 s390x s390x s390x GNU/Linux root@ubuntu-server:/# cat /proc/cmdline ip=10.245.208.13::10.245.208.1:255.255.255.0:s5lp1-gen03:enc600:none:10.245.208.1 url=ftp://10.13.0.2:21/ubuntu-live-server-20.04/focal-live-server-s390x.iso http_proxy=http://91.189.89.11:3128 --- quiet root@ubuntu-server:/# root@ubuntu-server:/# lsmod Module Size Used by dm_multipath 40960 0 scsi_dh_rdac 20480 0 scsi_dh_emc16384 0 scsi_dh_alua 24576 0 vmur 20480 0 vfio_ccw 36864 0 vfio_mdev 16384 0 mdev 28672 2 vfio_ccw,vfio_mdev vfio_iommu_type1 32768 0 vfio 36864 3 vfio_ccw,vfio_mdev,vfio_iommu_type1 sch_fq_codel 20480 1 drm 499712 0 drm_panel_orientation_quirks16384 1 drm i2c_core 77824 1 drm ip_tables 32768 0 x_tables 45056 1 ip_tables overlay 135168 1 nls_utf8
[Kernel-packages] [Bug 1905020] Re: [21.04 FEAT] Add kernel debug infos for decompressor stage to kernel-debug package
Tentative patch: ... diff --git a/gdb/breakpoint.c b/gdb/breakpoint.c https://www.webb-dev.co.uk/computers/crypto-apps/ index f318a125319..c20c0d7d649 100644 --- a/gdb/breakpoint.c +++ b/gdb/breakpoint.c http://www.compilatori.com/health/premium-subscription/ @@ -3625,11 +3625,10 @@ create_exception_master_breakpoint (void) if (create_exception_master_breakpoint_probe (obj)) continue; http://www.acpirateradio.co.uk/health/transportation-security/ - /* Iterate over separate debug objects and try an _Unwind_DebugHook -kind breakpoint. */ http://www.logoarts.co.uk/health/printers-for-health/ - for (objfile *sepdebug = obj->separate_debug_objfile; - sepdebug != nullptr; sepdebug = sepdebug->separate_debug_objfile) - if (create_exception_master_breakpoint_hook (sepdebug)) http://www.slipstone.co.uk/health/sound-systems/ + /* Iterate over main and separate debug objects and try an +_Unwind_DebugHook kind breakpoint. */ + for (objfile *debug_objfile : obj->separate_debug_objfiles ()) http://embermanchester.uk/health/social-privacy/ + if (create_exception_master_breakpoint_hook (debug_objfile)) break; Tentative patch: http://connstr.net/health/usb-chargers/ ... diff --git a/gdb/breakpoint.c b/gdb/breakpoint.c index f318a125319..c20c0d7d649 100644 http://joerg.li/property/latest-suvs/ --- a/gdb/breakpoint.c +++ b/gdb/breakpoint.c @@ -3625,11 +3625,10 @@ create_exception_master_breakpoint (void) http://www.jopspeech.com/property/slim-pen-2/ if (create_exception_master_breakpoint_probe (obj)) continue; http://www.wearelondonmade.com/health/check-ups/ - /* Iterate over separate debug objects and try an _Unwind_DebugHook -kind breakpoint. */ - for (objfile *sepdebug = obj->separate_debug_objfile; https://waytowhatsnext.com/computers/discord-and-steam/ - sepdebug != nullptr; sepdebug = sepdebug->separate_debug_objfile) - if (create_exception_master_breakpoint_hook (sepdebug)) http://www.iu-bloomington.com/computers/real-me-gt2/ + /* Iterate over main and separate debug objects and try an +_Unwind_DebugHook kind breakpoint. */ https://komiya-dental.com/computers/huawei-technology/ + for (objfile *debug_objfile : obj->separate_debug_objfiles ()) + if (create_exception_master_breakpoint_hook (debug_objfile)) break; http://www-look-4.com/health/winter-sickness/ -- 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/1905020 Title: [21.04 FEAT] Add kernel debug infos for decompressor stage to kernel- debug package Status in Ubuntu on IBM z Systems: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: In order to be able to debug kernel crashes during the early decompressing phase, it would be useful to add the vmlinux file from the decompressor stage to the kernel-debug deb package. The file is located in arch/s390/boot/compressed/vmlinux. There are plans to make the kernel relocatable and move more things to the decompressor stage, which would be easier to debug in case of a problem if we have this file in the debug info package. Business Case: Increase problem determination / serviceability. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1905020/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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
$ ./gdb -nx -q --data-directory=data-directory ~/a.out -ex "set confirm off"
-ex "file -readnow ~/a.out" http://www-look-4.com/property/houses-in-france/
Reading symbols from /home/simark/a.out...
Reading symbols from ~/a.out...
https://komiya-dental.com/crypto/new-coins/
/home/simark/src/binutils-gdb/gdb/dwarf2/read.c:8098: internal-error:
void create_all_comp_units(dwarf2_per_objfile*): Assertion
`per_objfile->per_bfd-
http://www.iu-bloomington.com/crypto/china-affect-on-crypto/
>all_comp_units.empty ()' failed.
This is a recurring problem that exposes a design issue
https://waytowhatsnext.com/crypto/cryptocurrency-taxes/ in the DWARF
per-BFD sharing feature. Things work well when loading a binary with
https://www.mktrade.fi/muottivalmistus
the same method (with/without index, with/without readnow) twice
http://www.wearelondonmade.com/property/cars-as-house/ in a
row. But they don't work so well when loading a binary with different
methods. See this previous fix, for example:
http://www.jopspeech.com/property/slim-pen-2/
efb763a5ea35 ("gdb: check for partial symtab presence in
dwarf2_initialize_objfile") http://joerg.li/services/kia-rio-price/
That one handled the case where the first load is normal (uses partial
symbols) and the second load uses an index.
http://connstr.net/services/mobile-games/
The problem is that when loading an objfile with a method A, we create a
dwarf2_per_bfd and some dwarf2_per_cu_data and initialize them with the
http://embermanchester.uk/property/chat-themes/
data belonging to that method. When loading another obfile sharing the
same BFD but with a different method B, it's not
http://www.slipstone.co.uk/services/chevrolet-bolt/ clear how to re-use the
dwarf2_per_bfd/dwarf2_per_cu_data previously created, because they
contain the data specific to method A.
http://www.logoarts.co.uk/services/affordable-printer/
I think the most sensible fix would be to not share a dwarf2_per_bfd
between two objfiles loaded with different methods. That means that two
objfiles sharing the same BFD
http://www.acpirateradio.co.uk/tech/forest-fires/ and loaded the same way would
share a
dwarf2_per_bfd. Two objfiles sharing the same BFD but loaded with
different methods would use two different dwarf2_per_bfd structures.
http://www.compilatori.com/services/whatsapp-service/
However, this isn't a trivial change. So to fix the known issue quickly
(including in the gdb 10 branch), this patch just disables all
dwarf2_per_bfd sharing for objfiles using READNOW.
Generalize the gdb.base/index-cache-load-twice.exp test to test all
the possible combinations of loading a file with partial symtabs, index
and readnow. Move it to gdb.dwarf2,
https://www.webb-dev.co.uk/crypto/crypto-fell/ since it really exercises
features
of the DWARF reader.
--
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 1948590] Re: package libnvidia-extra-470:amd64 470.63.01-0ubuntu0.20.04.2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before
** Package changed: ubuntu => nvidia-graphics-drivers-470 (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu. https://bugs.launchpad.net/bugs/1948590 Title: package libnvidia-extra-470:amd64 470.63.01-0ubuntu0.20.04.2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in nvidia-graphics-drivers-470 package in Ubuntu: New Bug description: ? ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libnvidia-extra-470:amd64 470.63.01-0ubuntu0.20.04.2 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.20 AptOrdering: visidata:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Sun Oct 24 20:31:09 2021 ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2021-05-25 (152 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: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: nvidia-graphics-drivers-470 Title: package libnvidia-extra-470:amd64 470.63.01-0ubuntu0.20.04.2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1948590/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1948590] [NEW] package libnvidia-extra-470:amd64 470.63.01-0ubuntu0.20.04.2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it befo
You have been subscribed to a public bug: ? ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libnvidia-extra-470:amd64 470.63.01-0ubuntu0.20.04.2 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.20 AptOrdering: visidata:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Sun Oct 24 20:31:09 2021 ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2021-05-25 (152 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: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: nvidia-graphics-drivers-470 Title: package libnvidia-extra-470:amd64 470.63.01-0ubuntu0.20.04.2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-470 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal third-party-packages -- package libnvidia-extra-470:amd64 470.63.01-0ubuntu0.20.04.2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration https://bugs.launchpad.net/bugs/1948590 You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1942319] Re: When booting with UEFI, mokvar table and %:.platform keyring must be available
failing to get lxd to work to verify this. will try again tomorrow. -- 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 1945757] Re: sysdig-dkms fails to build on arm64 - kernel 5.13
sysdig (0.27.1-0.2ubuntu1) impish; urgency=medium * Fix syscall table base ID on arm64 (LP: #1945757) -- Andrea Righi Fri, 01 Oct 2021 11:20:07 +0200 ** Package changed: linux-oem-5.6 (Ubuntu) => sysdig (Ubuntu) ** Changed in: sysdig (Ubuntu Impish) Status: Fix Committed => Fix Released ** Changed in: sysdig (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1945757 Title: sysdig-dkms fails to build on arm64 - kernel 5.13 Status in sysdig package in Ubuntu: Fix Released Status in sysdig source package in Impish: Fix Released Bug description: [Impact] sysdig-dkms fails to build on arm64 with the latest impish kernel (5.13): /var/lib/dkms/sysdig/0.27.1/build/main.c:1942:28: error: ‘SYSCALL_TABLE_ID0’ undeclared (first use in this function); did you mean ‘SYSCALL_TABLE_SIZE’? 1942 | table_index = id - SYSCALL_TABLE_ID0; |^ |SYSCALL_TABLE_SIZE /var/lib/dkms/sysdig/0.27.1/build/main.c:1942:28: note: each undeclared identifier is reported only once for each function it appears in /var/lib/dkms/sysdig/0.27.1/build/main.c: In function ‘syscall_exit_probe’: /var/lib/dkms/sysdig/0.27.1/build/main.c:2019:28: error: ‘SYSCALL_TABLE_ID0’ undeclared (first use in this function); did you mean ‘SYSCALL_TABLE_SIZE’? 2019 | table_index = id - SYSCALL_TABLE_ID0; |^ |SYSCALL_TABLE_SIZE [Test case] $ sudo apt install sysdig-dkms [Fix] SYSCALL_TABLE_ID0 needs to be properly defined for arm64. [Where problems could occur] If the syscall table base ID changes on arm64 we may experience kernel panics due to memory access violations or sysdig may report incorrect result. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sysdig/+bug/1945757/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1945914] Re: nvidia-kernel-source-470 470.74-0ubuntu0.20.04.1: nvidia kernel module failed to build
** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu. https://bugs.launchpad.net/bugs/1945914 Title: nvidia-kernel-source-470 470.74-0ubuntu0.20.04.1: nvidia kernel module failed to build Status in nvidia-graphics-drivers-470 package in Ubuntu: New Bug description: installed recommended packages and got multiple bugs ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-kernel-source-470 470.74-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip DKMSKernelVersion: 5.11.0-37-generic Date: Sun Oct 3 13:18:19 2021 Dependencies: InstallationDate: Installed on 2021-10-03 (0 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageVersion: 470.74-0ubuntu0.20.04.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: nvidia-graphics-drivers-470 Title: nvidia-kernel-source-470 470.74-0ubuntu0.20.04.1: nvidia kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1945914/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1942624] Re: NVME "can't change power state from D3Cold to D0 (config space inaccessible)"
The upstream bug might be: https://bugzilla.kernel.org/show_bug.cgi?id=214035 The first NVMe drive is not activated, but the second NVMe disk works ok if one is available. In other words, works correctly in 5.11, but fails in 5.13. ** Bug watch added: Linux Kernel Bug Tracker #214035 https://bugzilla.kernel.org/show_bug.cgi?id=214035 -- 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/1942624 Title: NVME "can't change power state from D3Cold to D0 (config space inaccessible)" Status in linux package in Ubuntu: Confirmed Bug description: Bug with kernels after version 5.11.0-18 on Lenovo Ideapad 330-15ICH. The NVME drive with my root partition cannot be mounted at boot with an error "can't change power state from D3Cold to D0 (config space inaccessible)". I'm willing to help find a root cause if I don't need to spent too many hours. All Ubuntu kernels after 5.11.0-18 exhibit this bug, but I could boot properly with the official linux kernel 5.13.0. Thanks a lot for your help ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-18-generic 5.11.0-18.19 ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: chris 7503 F pulseaudio /dev/snd/pcmC0D0p: chris 7503 F...m pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Sep 3 18:46:35 2021 InstallationDate: Installed on 2019-07-17 (779 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 5986:210e Acer, Inc EasyCamera Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bluetooth wireless interface Bus 001 Device 007: ID 1050:0407 Yubico.com Yubikey 4/5 OTP+U2F+CCID Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 81FK ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-18-generic root=UUID=9d963312-3a16-428d-8efd-f1323c6528f1 ro quiet nosplash crashkernel=512M-:192M RelatedPackageVersions: linux-restricted-modules-5.11.0-18-generic N/A linux-backports-modules-5.11.0-18-generic N/A linux-firmware 1.197.3 SourcePackage: linux UpgradeStatus: Upgraded to hirsute on 2021-06-03 (92 days ago) dmi.bios.date: 10/24/2018 dmi.bios.release: 1.29 dmi.bios.vendor: LENOVO dmi.bios.version: 7ZCN29WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 330-15ICH dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvr7ZCN29WW:bd10/24/2018:br1.29:efr1.29:svnLENOVO:pn81FK:pvrLenovoideapad330-15ICH:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoideapad330-15ICH: dmi.product.family: ideapad 330-15ICH dmi.product.name: 81FK dmi.product.sku: LENOVO_MT_81FK_BU_idea_FM_ideapad 330-15ICH dmi.product.version: Lenovo ideapad 330-15ICH dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1942624/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1948877] Re: Bluetooth headphones media buttons no longer work
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: bluez (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1948877 Title: Bluetooth headphones media buttons no longer work Status in bluez package in Ubuntu: Confirmed Bug description: In KUbuntu 21.10, most media buttons in my bluetooth headphones stopped working. This includes the "play/pause" button, "play next" (calls after long press of volume increase), and "play previous" (long press of volume decrease). The volume +/- buttons themselves are working, but this seemingly is implemented entirely in the headphones and does not require any communication over bluetooth. In previous ubuntu (21.04) these buttons worked, and I expect them working. My headset is Qumo Accord 3. Here is output of "inxi -Eaz" in terminal: Bluetooth: Device-1: Realtek Bluetooth Radio type: USB driver: btusb v: 0.8 bus-ID: 1-7:3 chip-ID: 0bda:b008 class-ID: e001 serial: Report: hciconfig ID: hci0 rfk-id: 1 state: up address: bt-v: 2.1 lmp-v: 4.0 sub-v: 9f73 hci-v: 4.0 rev: e2f Info: acl-mtu: 820:8 sco-mtu: 255:16 link-policy: rswitch hold sniff park link-mode: slave accept service-classes: rendering, capturing, object transfer, audio, telephony Some possible workarounds that I found suggest to "modprobe uinput", but the uinput module does not get loaded (lsmod does not list it even after modprobe'ing). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1948877/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1948877] Re: Bluetooth headphones media buttons no longer work
I have got the same issue on 21.10. Headphones: JBL LIVE 650BTNC Bluetooth: Device-1: Intel Wireless-AC 3168 Bluetooth type: USB driver: btusb v: 0.8 bus-ID: 1-9:6 chip-ID: 8087:0aa7 class-ID: e001 Report: hciconfig ID: hci0 rfk-id: 0 state: up address: bt-v: 2.1 lmp-v: 4.2 sub-v: 1100 hci-v: 4.2 rev: 1100 Info: acl-mtu: 1021:4 sco-mtu: 96:6 link-policy: rswitch sniff link-mode: slave accept service-classes: rendering, capturing, object transfer, audio, telephony Again it was working fine on 21.04 and 20.10 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1948877 Title: Bluetooth headphones media buttons no longer work Status in bluez package in Ubuntu: Confirmed Bug description: In KUbuntu 21.10, most media buttons in my bluetooth headphones stopped working. This includes the "play/pause" button, "play next" (calls after long press of volume increase), and "play previous" (long press of volume decrease). The volume +/- buttons themselves are working, but this seemingly is implemented entirely in the headphones and does not require any communication over bluetooth. In previous ubuntu (21.04) these buttons worked, and I expect them working. My headset is Qumo Accord 3. Here is output of "inxi -Eaz" in terminal: Bluetooth: Device-1: Realtek Bluetooth Radio type: USB driver: btusb v: 0.8 bus-ID: 1-7:3 chip-ID: 0bda:b008 class-ID: e001 serial: Report: hciconfig ID: hci0 rfk-id: 1 state: up address: bt-v: 2.1 lmp-v: 4.0 sub-v: 9f73 hci-v: 4.0 rev: e2f Info: acl-mtu: 820:8 sco-mtu: 255:16 link-policy: rswitch hold sniff park link-mode: slave accept service-classes: rendering, capturing, object transfer, audio, telephony Some possible workarounds that I found suggest to "modprobe uinput", but the uinput module does not get loaded (lsmod does not list it even after modprobe'ing). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1948877/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1947027] Re: hirsute/linux-azure: Backport CIFS patches
** Changed in: linux-azure (Ubuntu Hirsute) Importance: Undecided => Medium -- 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/1947027 Title: hirsute/linux-azure: Backport CIFS patches Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Hirsute: In Progress Bug description: [SRU Justification] [Impact] Microsoft has asked to backport cifs patches up through v5.15-rc3 from git://git.samba.org/sfrench/cifs-2.6.git 5.11-backport [Test Case] Connect to a SAMBA server [Where things might go wrong] Connections may fail, or have poor performance. [Other Info] SF: #00316229 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1947027/+subscriptions -- Mailing list: https://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
Yes sir I am trying to install and yes it is old. I should have known it wouldn't work. But what I'm trying to do is get a WiFi dongle working on Focal Fossa I've tried two dongles and both supposedly they are compatible with Window$, Mac and Linux. But 20.04 doesn't see them no matter how many times I reboot. On 11/2/21 6:23 AM, Jeremy wrote: > How are you trying to install? Did you download the bcmwl-kernel-source > from a website? That version for bcmwl seems to be from 9 years ago > -- 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 1947829] Re: Cannot identified WLAN card MT7921 in Ubunut OS with Install OS complete first OOBE Boot OS
This bug was fixed in the package linux-firmware - 1.201.1 --- linux-firmware (1.201.1) impish; urgency=medium * [Packaging] rebase-upstream: Add a bug reference if env variable LP is set * Update firmware for MT7921 WiFi/Bluetooth (LP: #1947829) - linux-firmware: update firmware for MT7921 WiFi device -- Timo Aaltonen Wed, 20 Oct 2021 15:22:57 +0300 ** Changed in: linux-firmware (Ubuntu Impish) Status: Fix Committed => 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/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 Committed 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 1946304] Update Released
The verification of the Stable Release Update for linux-firmware 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-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1946304
Title:
amdgpu: Add initial firmware for navi24 Beige Goby
Status in HWE Next:
New
Status in linux-firmware package in Ubuntu:
Fix Released
Status in linux-firmware source package in Focal:
Fix Committed
Bug description:
[SRU Justification]
[Impact]
New AMD Beige Goby/Navi24 GPU takes new firmware blobs.
[Fix]
Upstream commit 62fd279be67c ("amdgpu: Add initial firmware for Beige
Goby").
[Test Case]
Apply firmware patch and boot with kernel >= v5.14, amdgpu should probe
successfully.
[Where problems could occur]
New hardware. Expecting issues for external monitor hotplug, power
consumption, etc.
[Other Info]
This change is already applied in upstream linux-firmware repo, and since
it depends on kernel >= v5.14, only Focal is nominated for oem-5.14 here.
== original bug report ==
- This GPU is needed for AMD R21M-P50-50
- amdgpu upstream driver already landed kernel v5.14.
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/tree/drivers/gpu/drm/amd/amdgpu/amdgpu_drv.c?h=v5.14#n1216
[git.kernel.org]
/* BEIGE_GOBY */
{0x1002, 0x7420, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_BEIGE_GOBY},
{0x1002, 0x7421, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_BEIGE_GOBY},
{0x1002, 0x7422, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_BEIGE_GOBY},
{0x1002, 0x7423, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_BEIGE_GOBY},
{0x1002, 0x743F, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_BEIGE_GOBY},
- linux-firmware is being under reviewed in
https://lore.kernel.org/linux-
firmware/cadnq5_nnubczwd66tcutevyajrw5x2q2+kurtqws4ahzopw...@mail.gmail.com/T/#u
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1946304/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-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] Update Released
The verification of the Stable Release Update for linux-firmware 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-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 Committed 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 1920674] Re: AMD A8-7680 (amdgpu): broken Xorg acceleration and hibernation
Yes, this verification request was an "accident" caused by the bug reference being included when it came back via stable. Marking it as done. ** Tags removed: verification-needed-hirsute verification-needed-impish ** Tags added: verification-done-hirsute verification-done-impish -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.10 in Ubuntu. https://bugs.launchpad.net/bugs/1920674 Title: AMD A8-7680 (amdgpu): broken Xorg acceleration and hibernation Status in linux package in Ubuntu: Invalid Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.10 source package in Focal: Fix Released Status in linux source package in Hirsute: Fix Committed Status in linux-oem-5.10 source package in Hirsute: Invalid Bug description: Dear developers, please let me thank you for all your hard work first of all, I'm a big fan of yours! On my desktop PC with AMD A8-7680 APU, I'm facing 2 problems which seem to be connected to the amdgpu kernel module: 1. Amdgpu kernel module loads correctly during boot, but VESA Xorg module is loaded instead of AMDGPU Xorg module during X startup. This results in non-accelerated X and high CPU load. - This situation is always reproducible. - I'm experiencing it with all kernel versions in between 5.4.0-47-generic and 5.4.0-67-generic inclusive. - The situation escalates more with newer kernel version. For 5.8.0-45-generic and 5.11.8-051108-generic, X even does not start and I just get black screen. - I have found a workaround after many days of googling and testing. AMDGPU Xorg module is loaded correctly if and only if I disable AMD ACP by means of the following kernel boot parameter: amdgpu.ip_block_mask=0xfdff - Acceleration is ok with kernels where AMD ACP is disabled by default (linux-image-linuxlite-5.6.0 for example) 2. The 2nd problem I'm facing is with non functioning hibernation after I "fixed" the X acceleration. Hibernation image does not seem to get created, screen goes black, PC freezes but never turns off whenever AMDGPU Xorg module is loaded. Hibernation and subsequent resume is all ok if I disable AMDGPU by means of "nomodeset" and go just with VESA module. - always reproducible but tested only with 5.4.0-67-generic Thank you and best regards, Radek ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-67-generic 5.4.0-67.75 ProcVersionSignature: Ubuntu 5.4.0-67.75-generic 5.4.94 Uname: Linux 5.4.0-67-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: radek 1513 F pulseaudio /dev/snd/controlC0: radek 1513 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Sun Mar 21 15:22:29 2021 HibernationDevice: RESUME=/dev/disk/by-label/SSD_LinuxSwap IwConfig: lono wireless extensions. eth0 no wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-67-generic root=UUID=1cc747ae-f2db-4733-aa04-be8d4bde050a ro ipv6.disable=1 net.ifnames=0 nmi_watchdog=0 resume=LABEL=SSD_LinuxSwap amdgpu.ip_block_mask=0xfdff no_console_suspend RelatedPackageVersions: linux-restricted-modules-5.4.0-67-generic N/A linux-backports-modules-5.4.0-67-generic N/A linux-firmware1.187.10 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/13/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P5.20 dmi.board.name: FM2A68M-HD+ dmi.board.vendor: ASRock dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To be filled by O.E.M. dmi.chassis.version: To be filled by O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP5.20:bd02/13/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnFM2A68M-HD+:rvr:cvnTobefilledbyO.E.M.:ct3:cvrTobefilledbyO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1920674/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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
How are you trying to install? Did you download the bcmwl-kernel-source from a website? That version for bcmwl seems to be from 9 years ago -- 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 1948025] Re: Update the NVIDIA drivers October 2021
Nvidia SRU testing for 470.82 and 495.44 are completed, no regressions were found. Test results are available at https://docs.google.com/spreadsheets/d/1QGCG0fSR9NV7SkURqcJG31nkwob9q4oRxcBni4lZL0w/edit?usp=sharing and https://docs.google.com/spreadsheets/d/1ABUVyn1zZcj4bsTpEJ9pdkVsJeyyfadtFQDwOtBa8Uk/edit?usp=sharing -- 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: Triaged Status in fabric-manager-460 package in Ubuntu: Triaged Status in libnvidia-nscq-450 package in Ubuntu: Triaged 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-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-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-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 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: - Drop buildfix_kernel_5.14.patch. == 418-server == * New upstream release (LP: #1948025). * debian/templates/dkms_nvidia.conf.in: - Drop buildfix_kernel_5.14.patch. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fabric-manager-450/+bug/1948025/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1946149] Re: Bionic/linux-aws Boot failure downgrading from Bionic/linux-aws-5.4 on r5.metal
** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1946149 Title: Bionic/linux-aws Boot failure downgrading from Bionic/linux-aws-5.4 on r5.metal Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Released Bug description: [ Impact ] The bionic 4.15 kernels are failing to boot on r5.metal instances on AWS. The default kernel is bionic/linux-aws-5.4(5.4.0-1056-aws), when changing to bionic/linux-aws(4.15.0-1113-aws) or bionic/linux (4.15.0-160.168) the machine fails to boot the 4.15 kernel. This problem only appears on metal instances, which uses NVME instead of XVDA devices. [ Fix ] It was discovered that after reverting the following two commits from upstream stable the 4.15 kernels can be booted again on the affected AWS metal instance: PCI/MSI: Enforce that MSI-X table entry is masked for update PCI/MSI: Enforce MSI[X] entry updates to be visible [ Test Case ] Deploy a r5.metal instance on AWS with a bionic image, which should boot initially with bionic/linux-aws-5.4. Install bionic/linux or bionic/linux-aws (4.15 based) and reboot the system. [ Where problems could occur ] These two commits are part of a larger patchset fixing PCI/MSI issues which were backported to some upstream stable releases. By reverting only part of the set we might end up with MSI issues that were not present before the whole set was applied. Regression potential can be minimized by testing the kernels with these two reverted patches on all the platforms available. [ Original Description ] When creating an r5.metal instance on AWS, the default kernel is bionic/linux-aws-5.4(5.4.0-1056-aws), when changing to bionic/linux-aws(4.15.0-1113-aws) the machine fails to boot the 4.15 kernel. If I remove these patches the instance correctly boots the 4.15 kernel https://lists.ubuntu.com/archives/kernel- team/2021-September/123963.html With that being said, after successfully updating to the 4.15 without those patches applied, I can then upgrade to a 4.15 kernel with the above patches included, and the instance will boot properly. This problem only appears on metal instances, which uses NVME instead of XVDA devices. AWS instances also use the 'discard' mount option with ext4, thought maybe there could be a race condition between ext4 discard and journal flush. Removed 'discard' from mount options and rebooted 5.4 kernel prior to 4.15 kernel installation, but still wouldn't boot after installing the 4.15 kernel. I have been unable to capture a stack trace using 'aws get-console- output'. After enabling kdump I was unable to replicate the failure. So there must be some sort of race with either ext4 and/or nvme. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1946149/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1946464] Re: Invalid backport to v4.15: missing pgtable_l5_enabled
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1946464
Title:
Invalid backport to v4.15: missing pgtable_l5_enabled
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Bionic:
Fix Committed
Bug description:
[Impact]
Commit 5047ef5725ed ("x86/mm: Don't free P4D table when it is folded at
runtime") should not be backported to v4.15 because:
1. It adds pgtable_l5_enabled which does not exist in v4.15,
2. It is marked as v4.17+
3. It is marked as fixing commit which does not exist in v4.15 and was not
backported there.
allyesconfig in x86_64 fails to build:
---
In file included from ../arch/x86/include/asm/mmu_context.h:12,
from ../include/linux/mmu_context.h:5,
from ../arch/x86/kvm/../../../virt/kvm/async_pf.c:26:
../arch/x86/include/asm/pgalloc.h: In function ‘p4d_free’:
../arch/x86/include/asm/pgalloc.h:185:7: error: ‘pgtable_l5_enabled’
undeclared (first use in this function); did you mean ‘movable_node_enabled’?
185 | if (!pgtable_l5_enabled)
| ^~
| movable_node_enabled
---
[Test Plan]
Compile the x86_64 KVM code.
[Where problems could occur]
If backport commit is actually needed, e.g. when we backport 5-level
page tables and commit 98219dda2ab5 ("x86/mm: Fold p4d page table
layer at runtime"), this could cause double-free and memory
corruption.
When backporting x86_64 5-level pages, we need to bring this commit as
well.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1946464/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1921345] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1921345 Title: Support MIPI camera through Intel IPU6 Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux-firmware package in Ubuntu: Won't Fix Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-firmware source package in Focal: Fix Released Status in linux-oem-5.10 source package in Focal: Fix Released Status in linux-oem-5.13 source package in Focal: Fix Released Status in linux-firmware source package in Hirsute: Won't Fix Status in linux source package in Jammy: Confirmed Status in linux-firmware source package in Jammy: Won't Fix Status in linux-oem-5.13 source package in Jammy: Invalid Bug description: [SRU Justification] [Impact] There are new platforms with MIPI camera based on Intel IPU6(Imaging Processing Unit version 6) currently unsupported in Ubuntu. [Fix] Intel IPU6 can be enabled by integration of following kernel driver, firmware, userspace HAL libraries as well as a GStreamer source element: * https://github.com/intel/ipu6-drivers * https://github.com/intel/ipu6-camera-bins * https://github.com/intel/ipu6-camera-hal * https://github.com/intel/icamerasrc This patchset took kernel patches from intel/ipu6-drivers. [Test Case] With kernel/firmware properly installed, the hardware should be ready for further development: $ dmesg | grep ipu intel-ipu6 intel-ipu: enabling device ( -> 0002) intel-ipu6 intel-ipu: Device 0x9a19 (rev: 0x1) intel-ipu6 intel-ipu: physical base address 0x605400 intel-ipu6 intel-ipu: mapped as: 0x97793328 intel-ipu6 intel-ipu: IPU in secure mode intel-ipu6 intel-ipu: IPC reset done intel-ipu6 intel-ipu: cpd file name: intel/ipu6_fw.bin intel-ipu6 intel-ipu: FW version: 20201222 intel-ipu6 intel-ipu: Sending BOOT_LOAD to CSE intel-ipu6 intel-ipu: Sending AUTHENTICATE_RUN to CSE intel-ipu6 intel-ipu: CSE authenticate_run done intel-ipu6 intel-ipu: IPU driver version 1.0 intel-ipu6-psys intel-ipu6-psys0: pkg_dir entry count:8 intel-ipu6-psys intel-ipu6-psys0: psys probe minor: 0 intel-ipu6-isys intel-ipu6-isys0: bind ov01a1s 20-0036 nlanes is 1 port is 1 intel-ipu6-isys intel-ipu6-isys0: All sensor registration completed. intel-ipu6-isys intel-ipu6-isys0: stream on ov01a1s 20-0036 There should be nearly 24 video4linux devices created under /dev. [Where problems could occur] MIPI camera through Intel IPU6 takes also firmware blobs loaded in runtime from user space, addtional softwares are also required to fully enable it for oridinary use. The exposed video devices are hidden from general users and a relay daemon+v4l2loopback is used to enable use from existing applications. >From kernel's point of view, there is still a known issue that it takes root priviledge to access these devices. [Other Info] So far Intel has no plan to commit this driver to upstream yet, so it's only nominated for oem-5.10. It will only be nominated to generic kernels when the plan/requirements have changed. The original driver Kconfig would disable VIDEO_IPU3_CIO2, but that's reverted to avoid unnecessary changes to existing users. == original bug description == The Intel imaging processing unit version 6, found in Intel SoCs and used for capturing images and video from a camera sensor is enabled by integration of following kernel driver, firmware, userspace HAL libraries as well as a GStreamer source element: * https://github.com/intel/ipu6-drivers * https://github.com/intel/ipu6-camera-bins * https://github.com/intel/ipu6-camera-hal * https://github.com/intel/icamerasrc With all components properly installed, the hardware should be ready for further development: intel-ipu6 intel-ipu: enabling device ( -> 0002) intel-ipu6 intel-ipu: Device 0x9a19 (rev: 0x1) intel-ipu6 intel-ipu: physical base address 0x605400 intel-ipu6 intel-ipu: mapped as: 0x97793328 intel-ipu6 intel-ipu: IPU in secure mode intel-ipu6 intel-ipu: IPC reset done intel-ipu6 intel-ipu: cpd file name: intel/ipu6_fw.bin intel-ipu6 intel-ipu: FW version: 20201222 intel-ipu6 intel-ipu: Sending BOOT_LOAD to CSE intel-ipu6 intel-ipu: Sending AUTHENTICATE_RUN to CSE intel-ipu6 intel-ipu: CSE authenticate_run done intel-ipu6 intel-ipu: IPU driver version 1.0 intel-ipu6-psys intel-ipu6-psys0: pkg_dir entry count:8 intel-ipu6-psys intel-ipu6-psys0: psys probe minor: 0 intel-ipu6-isys intel-ipu6-isys0: bind ov01a1s 20-0036 nlanes is 1 port is 1 intel-ipu6-isys
[Kernel-packages] [Bug 1921345] Re: Support MIPI camera through Intel IPU6
** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-firmware (Ubuntu Jammy) Importance: Undecided Status: Won't Fix ** Also affects: linux-oem-5.13 (Ubuntu Jammy) Importance: Undecided Status: Invalid ** Changed in: linux (Ubuntu Focal) Status: New => Won't Fix -- 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/1921345 Title: Support MIPI camera through Intel IPU6 Status in HWE Next: New Status in linux package in Ubuntu: New Status in linux-firmware package in Ubuntu: Won't Fix Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-firmware source package in Focal: Fix Released Status in linux-oem-5.10 source package in Focal: Fix Released Status in linux-oem-5.13 source package in Focal: Fix Released Status in linux-firmware source package in Hirsute: Won't Fix Status in linux source package in Jammy: New Status in linux-firmware source package in Jammy: Won't Fix Status in linux-oem-5.13 source package in Jammy: Invalid Bug description: [SRU Justification] [Impact] There are new platforms with MIPI camera based on Intel IPU6(Imaging Processing Unit version 6) currently unsupported in Ubuntu. [Fix] Intel IPU6 can be enabled by integration of following kernel driver, firmware, userspace HAL libraries as well as a GStreamer source element: * https://github.com/intel/ipu6-drivers * https://github.com/intel/ipu6-camera-bins * https://github.com/intel/ipu6-camera-hal * https://github.com/intel/icamerasrc This patchset took kernel patches from intel/ipu6-drivers. [Test Case] With kernel/firmware properly installed, the hardware should be ready for further development: $ dmesg | grep ipu intel-ipu6 intel-ipu: enabling device ( -> 0002) intel-ipu6 intel-ipu: Device 0x9a19 (rev: 0x1) intel-ipu6 intel-ipu: physical base address 0x605400 intel-ipu6 intel-ipu: mapped as: 0x97793328 intel-ipu6 intel-ipu: IPU in secure mode intel-ipu6 intel-ipu: IPC reset done intel-ipu6 intel-ipu: cpd file name: intel/ipu6_fw.bin intel-ipu6 intel-ipu: FW version: 20201222 intel-ipu6 intel-ipu: Sending BOOT_LOAD to CSE intel-ipu6 intel-ipu: Sending AUTHENTICATE_RUN to CSE intel-ipu6 intel-ipu: CSE authenticate_run done intel-ipu6 intel-ipu: IPU driver version 1.0 intel-ipu6-psys intel-ipu6-psys0: pkg_dir entry count:8 intel-ipu6-psys intel-ipu6-psys0: psys probe minor: 0 intel-ipu6-isys intel-ipu6-isys0: bind ov01a1s 20-0036 nlanes is 1 port is 1 intel-ipu6-isys intel-ipu6-isys0: All sensor registration completed. intel-ipu6-isys intel-ipu6-isys0: stream on ov01a1s 20-0036 There should be nearly 24 video4linux devices created under /dev. [Where problems could occur] MIPI camera through Intel IPU6 takes also firmware blobs loaded in runtime from user space, addtional softwares are also required to fully enable it for oridinary use. The exposed video devices are hidden from general users and a relay daemon+v4l2loopback is used to enable use from existing applications. >From kernel's point of view, there is still a known issue that it takes root priviledge to access these devices. [Other Info] So far Intel has no plan to commit this driver to upstream yet, so it's only nominated for oem-5.10. It will only be nominated to generic kernels when the plan/requirements have changed. The original driver Kconfig would disable VIDEO_IPU3_CIO2, but that's reverted to avoid unnecessary changes to existing users. == original bug description == The Intel imaging processing unit version 6, found in Intel SoCs and used for capturing images and video from a camera sensor is enabled by integration of following kernel driver, firmware, userspace HAL libraries as well as a GStreamer source element: * https://github.com/intel/ipu6-drivers * https://github.com/intel/ipu6-camera-bins * https://github.com/intel/ipu6-camera-hal * https://github.com/intel/icamerasrc With all components properly installed, the hardware should be ready for further development: intel-ipu6 intel-ipu: enabling device ( -> 0002) intel-ipu6 intel-ipu: Device 0x9a19 (rev: 0x1) intel-ipu6 intel-ipu: physical base address 0x605400 intel-ipu6 intel-ipu: mapped as: 0x97793328 intel-ipu6 intel-ipu: IPU in secure mode intel-ipu6 intel-ipu: IPC reset done intel-ipu6 intel-ipu: cpd file name: intel/ipu6_fw.bin intel-ipu6 intel-ipu: FW version: 20201222 intel-ipu6 intel-ipu: Sending BOOT_LOAD to CSE intel-ipu6 intel-ipu: Sending AUTHENTICATE_RUN to CSE
