[Kernel-packages] [Bug 1993318] Re: ZFS + Encryption installations of Ubuntu Desktop do not come up correctly on first boot, systemd unmounts many of the zfs volumes
** No longer affects: zsys (Ubuntu) ** No longer affects: systemd (Ubuntu) ** No longer affects: snapd (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1993318 Title: ZFS + Encryption installations of Ubuntu Desktop do not come up correctly on first boot, systemd unmounts many of the zfs volumes Status in Ubuntu Manual Tests: New Status in Release Notes for Ubuntu: Fix Released Status in ubiquity package in Ubuntu: Fix Released Status in zfs-linux package in Ubuntu: Confirmed Status in ubiquity source package in Jammy: Fix Released Bug description: This is *probably* the wrong package, but it's the best I can figure for this, so here goes. Hardware: Kubuntu Focus XE, 32 GB RAM, 1 TB SSD, 11th Gen Intel Core i5, UEFI, no secure boot. Testing done in GNOME Boxes, BIOS, 4 GB RAM, 50 GB disk space . OS is Ubuntu Desktop, Kinetic Final ISO. [Testcase] tl;dr encrypted-zfs, firstboot, `systemctl daemon-reload` must not unmount half of mountpoints, ie. /var/lib. Steps to reproduce: 1. Boot the Ubuntu desktop ISO. 2. Select "Install Ubuntu" and proceed with the installation process. 3. When you get to the "Installation type" screen, select "Advanced Options", and enable ZFS + Encryption. 4. Proceed with the rest of the installation as normal. 5. Reboot into the newly installed system. 6. Log in. 7. Run "sudo apt update" in a terminal. Expected result: The package database should be updated normally. Actual result: You are presented with the following errors at the end of the apt output: Reading package lists... Error! E: flAbsPath on /var/lib/dpkg/status failed - realpath (2: No such file or directory) E: Could not open file - open (2: No such file or directory) E: Problem opening E: The package lists or status file could not be parsed or opened. Notes: Switching to a TTY will print a crash error message related to the same missing /var/lib/dpkg/status file. Running "sudo touch /var/lib/dpkg/status" will allow "sudo apt update" to function and fix the crashed process in the TTY. [End Testcase] Once you log in, you'll notice that Firefox is missing (bug #1993279), and you will likely be presented with a ton of error messages and other scary junk. At least one of those error messages was related to update-manager in my experience, and another one was from "check-new- release-gtk". ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: zsys (not installed) ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7 Uname: Linux 5.19.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Oct 18 09:55:27 2022 InstallationDate: Installed on 2022-10-18 (0 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221018) ProcEnviron: TERM=xterm-256color PATH=(custom, no username) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: zsys UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-manual-tests/+bug/1993318/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1966841] Re: alsa/sdw: Fix the audio issue on a Dell machine without internal mic
** No longer affects: firmware-sof (Ubuntu Focal) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1966841 Title: alsa/sdw: Fix the audio issue on a Dell machine without internal mic Status in HWE Next: New Status in firmware-sof package in Ubuntu: Fix Released Status in linux package in Ubuntu: In Progress Status in linux-firmware package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Fix Committed Status in linux source package in Focal: Invalid Status in linux-firmware source package in Focal: Fix Released Status in linux-oem-5.14 source package in Focal: Fix Released Status in firmware-sof source package in Jammy: In Progress Status in linux source package in Jammy: In Progress Status in linux-firmware source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Committed Bug description: SRU template for linux-firmware [Impact] we have a Dell ADL laptop which has sdw audio, but there is no camera and no internal digital mic in this machine, the current asoc driver can't work on this machine, the speaker and headset couldn't work. [Fix] Backport a tplg file which is specific to this mahcine [Test] Install the patched linux-firmware and boot the latest oem-5.14 kernel on the machine, check dmesg, it loads the correct tplg, and test speaker and headset, all work well. [Where problems could occur] This SRU is adding a new tplg file, it has no chance to introduce a regression. SRU template for linux [Impact] we have a Dell ADL laptop which has sdw audio, but there is no camera and no internal digital mic in this machine, the current soc driver can't work on this machine, it will load a wrong tplg without this patch, and the speaker and headset couldn't work. [Fix] Backport one patch from upstream. [Test] Boot the patched kernel on the machine, check dmesg, it loads the correct tplg, and test speaker and headset, all work well. [Where problems could occur] If it could introduce regression, it will be on the sdw codec matching for adl machines, then it will make the driver load wrong tplg and make output device and input device not work anymore. But this possibility is very low, we already tested the patch on some dell adl machines, no regression found. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1966841/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1966841] Re: alsa/sdw: Fix the audio issue on a Dell machine without internal mic
** No longer affects: linux-oem-5.14 (Ubuntu Jammy) ** No longer affects: linux-oem-5.14 (Ubuntu) ** No longer affects: linux-oem-5.17 (Ubuntu Focal) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1966841 Title: alsa/sdw: Fix the audio issue on a Dell machine without internal mic Status in HWE Next: New Status in firmware-sof package in Ubuntu: In Progress Status in linux package in Ubuntu: In Progress Status in linux-firmware package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Fix Committed Status in firmware-sof source package in Focal: Invalid Status in linux source package in Focal: Invalid Status in linux-firmware source package in Focal: Fix Committed Status in linux-oem-5.14 source package in Focal: Fix Committed Status in firmware-sof source package in Jammy: In Progress Status in linux source package in Jammy: In Progress Status in linux-firmware source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Committed Bug description: SRU template for linux-firmware [Impact] we have a Dell ADL laptop which has sdw audio, but there is no camera and no internal digital mic in this machine, the current asoc driver can't work on this machine, the speaker and headset couldn't work. [Fix] Backport a tplg file which is specific to this mahcine [Test] Install the patched linux-firmware and boot the latest oem-5.14 kernel on the machine, check dmesg, it loads the correct tplg, and test speaker and headset, all work well. [Where problems could occur] This SRU is adding a new tplg file, it has no chance to introduce a regression. SRU template for linux [Impact] we have a Dell ADL laptop which has sdw audio, but there is no camera and no internal digital mic in this machine, the current soc driver can't work on this machine, it will load a wrong tplg without this patch, and the speaker and headset couldn't work. [Fix] Backport one patch from upstream. [Test] Boot the patched kernel on the machine, check dmesg, it loads the correct tplg, and test speaker and headset, all work well. [Where problems could occur] If it could introduce regression, it will be on the sdw codec matching for adl machines, then it will make the driver load wrong tplg and make output device and input device not work anymore. But this possibility is very low, we already tested the patch on some dell adl machines, no regression found. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1966841/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1915071] Re: [MIR] kdump-tools
kdump-tools (1:1.6.8.2) unstable; urgency=medium * debian/control: Add Vcs-* tags. * Support compressing the core file at dump time (Closes: #856960). Thanks to Benjamin Drung! * kdump-config: Allow running in an initrd, thanks to Benjamin Drung. -- dann frazier Mon, 01 Feb 2021 13:35:59 -0700 ** Changed in: kdump-tools (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to kdump-tools in Ubuntu. Matching subscriptions: Maintainer https://bugs.launchpad.net/bugs/1915071 Title: [MIR] kdump-tools Status in kdump-tools package in Ubuntu: Fix Released Bug description: kdump-tools was split out of makedumpfile into its own source package in Debian. Since this is source that was already in main, I'd like to request that kdump-tools also be included in main. I'm submitting this "lightweight" MIR per https://wiki.ubuntu.com/MainInclusionProcess: "If a new source package contains only code which is already in main (e.g., the result of a source package split or rename, or source packages with a version in the name), it may not need a full review. Submitting a bug with an explanation is sufficient." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kdump-tools/+bug/1915071/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1877533] Re: [20.10 FEAT] Increase the crashkernel setting if the root volume is luks2-encrypted
** Changed in: kdump-tools (Ubuntu) Status: Fix Committed => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1877533 Title: [20.10 FEAT] Increase the crashkernel setting if the root volume is luks2-encrypted Status in Ubuntu on IBM z Systems: In Progress Status in kdump-tools package in Ubuntu: In Progress Status in makedumpfile package in Ubuntu: Invalid Status in kdump-tools source package in Focal: Invalid Status in makedumpfile source package in Focal: In Progress Status in kdump-tools source package in Groovy: Invalid Status in makedumpfile source package in Groovy: Won't Fix Bug description: Description: In case the volume containing the root filesystem is encrypted using LUKS2 the memory used while unlocking the volume may exceed the size allocated to the kdump kernel. This will lead to a failure while processing kdump and the dump file will not be stored. Unfortunately, this condition may not be detected by a client before a problem occurs. The request is to have the kdump package installation script check for LUKS2 encryption (more precisely for Argon2i PBKDF, which is the root cause of the high memory usage). If the condition is met, the installation procedure should increase the crashkernel parameter to a higher value (>=512M)or issue a warning, if the system memory is insufficient to reserve enough crashkernel memory. Business Case: Pervasive Encryption and Secure Execution require encryption of the filesystems in order to keep customer data secure at all times. With the increasing usage of these technologies, the number of kdump will rise too, typically at inconvenient times, when the kdump is triggered due to a real customer issue. With the suggested change, the number of customer complaints and effort to handle them will be reduced. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1877533/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1939855] Re: [SRU] Ice driver causes the kernel to crash with Ubuntu 20.04.2 with ethtool specific register commands
** No longer affects: focal (Ubuntu) ** No longer affects: focal (Ubuntu Focal) ** Project changed: dellserver => ubuntu-translations ** No longer affects: ubuntu-translations ** Changed in: linux (Ubuntu) Status: Invalid => Fix Released ** Changed in: linux (Ubuntu) Importance: Undecided => High -- 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/1939855 Title: [SRU] Ice driver causes the kernel to crash with Ubuntu 20.04.2 with ethtool specific register commands Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Released Bug description: [Impact] When we run the command, ethtool -d with Intel cards (ice driver), the kernel crashes because of the ice driver. The same works fine with HWE kernel (5.11). Here, we do not see any crash. [FIXES] ice: Fix bad register reads The "ethtool -d" handler reads registers in the ice_regs_dump_list array and returns read values back to the userspace. commitID: 1fba4a8a92706c89716449b1aab1b6879f438d34 https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net- next.git/commit/drivers/net/ethernet/intel/ice?id=1fba4a8a92706c89716449b1aab1b6879f438d34 [TESTING] Install Focal on a system with an E810 network device. Ensure the network device has an IP address and has connectivity Run ethtool -d Expected result: Prints a register dump for the specified network device [REGRESSION RISK] The regression risk is low [OTHER INFO] I have added the fix, built the kernel and tested the fix. https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/focal/+ref/e810_ethtool_fix_next To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1939855/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1957094] Re: on-demand mode doesn't work with nvidia-390
** Changed in: ubuntu-drivers-common (Ubuntu Jammy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/1957094 Title: on-demand mode doesn't work with nvidia-390 Status in OEM Priority Project: New Status in nvidia-settings package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in nvidia-settings source package in Focal: Fix Released Status in ubuntu-drivers-common source package in Focal: Fix Released Status in nvidia-settings source package in Impish: Fix Released Status in ubuntu-drivers-common source package in Impish: Fix Released Status in nvidia-settings source package in Jammy: Fix Released Status in ubuntu-drivers-common source package in Jammy: Fix Released Bug description: [Impact] * In any Ubuntu series, if user using a old GPU (which supported by nvidia-390 only) then issuing glxinfo will get "Error: couldn't find RGB GLX visual or fbconfig". Which mean the Xorg doesn't load dri driver correctly. [Test Plan] * install nvidia-390 on nvidia-390 supported system. * prime-select on-demand * reboot * glxinfo * after applying this patch, it will fall back to "ON" mode after reboot. * install nvidia-450 on nvidia-450 supported system. * prime-select on-demand * reboot the system * prime-select query (and check that on-demand mode is still in use). [Where problems could occur] * Since nvidia-390 doesn't support on-demand mode (RTD3 either). If a user stays in on-demand mode with 390 without problem, the after upgrading u-d-c and reboot. The mode will fall back to "ON" mode. * From my point of view, it's fine because nvidia-390 doesn't support RTD3. Thus, the nvidia will always stay in "Active" stage no matter which mode it is. * While there is no way to inform the user about this change, changing to the only supported default will avoid breaking GLX. --- The regression from https://bugs.launchpad.net/ubuntu/+source/ubuntu- drivers-common/+bug/1942789. It impacts Jammy and Impish so far. [Steps to reproduce] 1. Find a GPU supports nvidia-390 2. ubuntu-drivers install nvidia:390 3. prime-select on-demand 4. glxinfo [Expected result] Shows intel or nvidia drives monitor [Actual result] Error: couldn't find RGB GLX visual or fbconfig Since we are all agree "on-demand" mode as default mode. Pre-talk with Alberto, on-demand doesn't support with nvidia-390 (no matter RTD3). We could consider to make it as performance mode and leave a note on nvidia-settings. I'll prepare some test packages. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1957094/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1951580] Re: backport-iwlwifi-dkms fails to build with kernel 5.15 jammy
** No longer affects: linux (Ubuntu) ** No longer affects: linux (Ubuntu Jammy) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1951580 Title: backport-iwlwifi-dkms fails to build with kernel 5.15 jammy Status in backport-iwlwifi-dkms package in Ubuntu: Fix Released Status in backport-iwlwifi-dkms source package in Jammy: Fix Released Bug description: [Impact] backport-iwlwifi-dkms fails to build on the latest jammy kernel 5.15: CC [M] /tmp/backport-iwlwifi-dkms/drivers/net/wireless/intel/iwlwifi/mei/main.o In file included from /tmp/backport-iwlwifi-dkms/backport-include/asm-generic/bug.h:3, from ./arch/x86/include/asm/bug.h:84, from ./include/linux/bug.h:5, from /tmp/backport-iwlwifi-dkms/backport-include/linux/bug.h:3, from /tmp/backport-iwlwifi-dkms/backport-include/linux/kernel.h:4, from ./include/linux/skbuff.h:13, from /tmp/backport-iwlwifi-dkms/backport-include/linux/skbuff.h:3, from ./include/linux/if_ether.h:19, from /tmp/backport-iwlwifi-dkms/backport-include/linux/if_ether.h:3, from ./include/linux/etherdevice.h:20, from /tmp/backport-iwlwifi-dkms/backport-include/linux/etherdevice.h:3, from /tmp/backport-iwlwifi-dkms/drivers/net/wireless/intel/iwlwifi/mei/main.c:6: /tmp/backport-iwlwifi-dkms/drivers/net/wireless/intel/iwlwifi/mei/main.c: In function ‘iwl_mei_free_shared_mem’: /tmp/backport-iwlwifi-dkms/drivers/net/wireless/intel/iwlwifi/mei/main.c:243:17: error: implicit declaration of function ‘mei_cldev_dma_unmap’ [-Werror=implicit-function-declaration] 243 | WARN_ON(mei_cldev_dma_unmap(cldev)); | ^~~ [Test case] sudo apt install backport-iwlwifi-dkms [Fix] The driver assumes that kernels > 5.13 provide mei_cldev_dma_map/unmap() when CONFIG_WLAN_VENDOR_INTEL_MEI is defined. However these functions and the config option are not available at all in recent kernels. So instead of relying on the specific kernel version simply rely on the availability of CONFIG_WLAN_VENDOR_INTEL_MEI to determine if the kernel has the required functions defined, or if the driver needs to provide a custom implementation of these functions. [Regression potential] We may see build errors in newer kernel if CONFIG_WLAN_VENDOR_INTEL_MEI is merged upstream and these functions are actually provided by recent kernels. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/backport-iwlwifi-dkms/+bug/1951580/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1960839] Re: Missing firmware /lib/firmware/intel/ice/ddp/ice.pkg for ice driver
** Changed in: linux-firmware (Ubuntu)
Status: Invalid => Fix Released
** Changed in: linux-firmware (Ubuntu)
Importance: Undecided => Medium
--
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/1960839
Title:
Missing firmware /lib/firmware/intel/ice/ddp/ice.pkg for ice driver
Status in linux-firmware package in Ubuntu:
Fix Released
Status in linux-firmware source package in Bionic:
Fix Committed
Bug description:
[Impact]
* Missing firmware for Intel ICE driver on Bionic,
which is supported by the HWE kernel from Focal.
[Fix]
* commit 9ae61e7d8658 ("ice: Add package file for Intel E800 series driver")
brings the Bionic package in line with Focal (ice-1.3.4.0.pkg,LICENSE.ice)
[Test Case]
* Without firmware:
ice :98:00.0: firmware 5.4.5 api 1.7.6 nvm 2.40 0x8000706a 0.0.0
build 0x391f7640
ice :98:00.0: Direct firmware load for intel/ice/ddp/ice.pkg failed
with error -2
ice :98:00.0: The DDP package file was not found or could not be
read. Entering Safe Mode
ice :98:00.0: Package download failed. Advanced features disabled -
Device now in Safe Mode
* With firmware:
ice :98:00.0: firmware 5.4.5 api 1.7.6 nvm 2.40 0x8000706a 0.0.0
build 0x391f7640
ice :98:00.0: The DDP package was successfully loaded: ICE OS Default
Package version 1.3.4.0
ice :98:00.0: DCB is enabled in the hardware, max number of TCs
supported on this port are 8
ice :98:00.0: FW LLDP is disabled, DCBx/LLDP in SW mode.
[Where problems could occur]
* Systems with devices managed by the ice driver on Bionic HWE kernel
from Focal.
* The firmware enables advanced features, increasing driver exposure
and device activity.
* This has been available on Focal, which helps with some chance of issues
being hit and
reported previously (e.g. bug 1939855, searched for 'kernel ice driver' on
bugs.lp.net).
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1960839/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1915117] Re: [Regression] Audio card [8086:9d71] not detected after upgrade from linux 5.4 to 5.8
** Tags removed: verification-needed-hirsute -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-topology-conf in Ubuntu. https://bugs.launchpad.net/bugs/1915117 Title: [Regression] Audio card [8086:9d71] not detected after upgrade from linux 5.4 to 5.8 Status in alsa-topology-conf package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in alsa-topology-conf source package in Focal: New Status in linux source package in Focal: Confirmed Status in alsa-topology-conf source package in Hirsute: Won't Fix Status in linux source package in Hirsute: Fix Released Status in alsa-topology-conf source package in Impish: Fix Released Status in linux source package in Impish: Fix Released Bug description: [SRU Justification] [Impact] Skylake, Kabylake, Kabylake-refresh, Amberlake and some other platforms where audio is of SPT (PCH) type, HDA (with DSP capabilities) plus DMIC configuration is supported on these with skylake driver since kernel 5.8. However, no sound card can be detected w/o the topology binary file in /lib/firmware and corresponding ucm file. [Fix] The kernel config CONFIG_SND_SOC_INTEL_SKYLAKE_HDAUDIO_CODEC needa to be enabled for the snd_soc_skl driver to support HDA+DMIC configuration. And the topology binary file and UCM files need to be located in the correct path based on Intel's suggestion. https://gist.github.com/crojewsk/4e6382bfb0dbfaaf60513174211f29cb. [Test] On the Skylake/Kabylake platforms with either the PCI device 8086:9d70 and 8086:9d71, boot up the machine and check the existence of the sound card by either 'aplay -l' or 'pactl list' command. [Where problems could occur] Should be low risk, it only affects limited Intel Platforms with particular PCI device IDs + HDA plus DMIC configuration. == Original Bug Description == Ubuntu version: 20.10 (updated from 20.04) Kernel: 5.8.0-41-generic #46-Ubuntu Manufacturer: Acer Product Name: Swift SF314-54 BIOS Revision: 1.11 Audio card: Realtek High Definition Audio Multimedia audio controller [0401]: Intel Corporation Sunrise Point-LP HD Audio [8086:9d71] (rev 21) Summary === After upgrading from linux kernel 5.4 to 5.8, there is no more sound card available. However, if I select kernel 5.4 in GRUB, the sound card is available. Steps to reproduce == 1. Install 20.04 or 20.10 with a kenel 5.4 2. Check that sound output works as excepted (Settings > Sound > Output > Test) 3. Check that `alsa-info` command returns information 4. Upgrade kernel to 5.8 Expected results Sound output still works. Actual results == 2. Sound card is available, and sound can be output to the internal speakers. 4. No more sound card detected (Sound Settings display "Dummy Output" in the list of output devices). ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-41-generic 5.8.0-41.46 ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18 Uname: Linux 5.8.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Feb 9 14:42:00 2021 InstallationDate: Installed on 2019-01-20 (751 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Acer Swift SF314-54 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-41-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash mem_sleep_default=deep vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-41-generic N/A linux-backports-modules-5.8.0-41-generic N/A linux-firmware1.190.3 SourcePackage: linux UpgradeStatus: Upgraded to groovy on 2021-02-03 (5 days ago) dmi.bios.date: 11/21/2018 dmi.bios.release: 1.11 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.11 dmi.board.name: Strongbow_KL dmi.board.vendor: KBL dmi.board.version: V1.11 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.11 dmi.ec.firmware.release: 1.6 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.11:bd11/21/2018:br1.11:efr1.6:svnAcer:pnSwiftSF314-54:pvrV1.11:rvnKBL:rnStrongbow_KL:rvrV1.11:cvnAcer:ct10:cvrV1.11: dmi.product.family: Swift 3 dmi.product.name: Swift SF314-54 dmi.product.sku: dmi.product.version: V1.11 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-topology-conf/+bug/1915117/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchp
[Kernel-packages] [Bug 1875015] Re: Displaylink is extremely slow
** Bug watch removed: gitlab.gnome.org/GNOME/mutter/-/issues #2005 https://gitlab.gnome.org/GNOME/mutter/-/issues/2005 -- 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/1875015 Title: Displaylink is extremely slow Status in Nouveau Xorg driver: Unknown Status in OEM Priority Project: New Status in xf86-video-amd: Unknown Status in X.Org X server: Unknown Status in nvidia-graphics-drivers-470 package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Fix Released Status in xserver-xorg-video-amdgpu package in Ubuntu: In Progress Status in xserver-xorg-video-nouveau package in Ubuntu: In Progress Status in xorg-server source package in Focal: Fix Released Status in xorg-server source package in Hirsute: Won't Fix Status in xorg-server source package in Impish: Fix Released Bug description: Using ubuntu 20.04 on displaylink docking with external monitor is totally slow, unusable. The GUI responds very slow, if you click, the command of the click goes on after about 3 seconds... if you type, all the letters are with the same lag, so it is totally unusable. Was using displaylink without any problem on 19.10 until yesterday, when I upgraded to 20.04. It is terrific. If i plug out the usb for the displaylink docking station, than the speed is back, and the system is ok, if I connect it to the docking station again, everything extremely slow again. Please investigate this asap, as it is unusable on displaylink docking stations. To manage notifications about this bug go to: https://bugs.launchpad.net/nouveau/+bug/1875015/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1915117] Re: [Regression] Audio card [8086:9d71] not detected after upgrade from linux 5.4 to 5.8
** No longer affects: alsa-ucm-conf (Ubuntu Focal) ** No longer affects: alsa-ucm-conf (Ubuntu Hirsute) ** No longer affects: alsa-ucm-conf (Ubuntu Impish) ** Changed in: alsa-topology-conf (Ubuntu) Importance: Undecided => Medium ** Changed in: alsa-topology-conf (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: alsa-topology-conf (Ubuntu Hirsute) Importance: Undecided => Medium ** Changed in: alsa-topology-conf (Ubuntu Impish) Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-topology-conf in Ubuntu. https://bugs.launchpad.net/bugs/1915117 Title: [Regression] Audio card [8086:9d71] not detected after upgrade from linux 5.4 to 5.8 Status in alsa-topology-conf package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in alsa-topology-conf source package in Focal: New Status in linux source package in Focal: Confirmed Status in alsa-topology-conf source package in Hirsute: New Status in linux source package in Hirsute: Fix Released Status in alsa-topology-conf source package in Impish: Fix Released Status in linux source package in Impish: Fix Released Bug description: [SRU Justification] [Impact] Skylake, Kabylake, Kabylake-refresh, Amberlake and some other platforms where audio is of SPT (PCH) type, HDA (with DSP capabilities) plus DMIC configuration is supported on these with skylake driver since kernel 5.8. However, no sound card can be detected w/o the topology binary file in /lib/firmware and corresponding ucm file. [Fix] The kernel config CONFIG_SND_SOC_INTEL_SKYLAKE_HDAUDIO_CODEC needa to be enabled for the snd_soc_skl driver to support HDA+DMIC configuration. And the topology binary file and UCM files need to be located in the correct path based on Intel's suggestion. https://gist.github.com/crojewsk/4e6382bfb0dbfaaf60513174211f29cb. [Test] On the Skylake/Kabylake platforms with either the PCI device 8086:9d70 and 8086:9d71, boot up the machine and check the existence of the sound card by either 'aplay -l' or 'pactl list' command. [Where problems could occur] Should be low risk, it only affects limited Intel Platforms with particular PCI device IDs + HDA plus DMIC configuration. == Original Bug Description == Ubuntu version: 20.10 (updated from 20.04) Kernel: 5.8.0-41-generic #46-Ubuntu Manufacturer: Acer Product Name: Swift SF314-54 BIOS Revision: 1.11 Audio card: Realtek High Definition Audio Multimedia audio controller [0401]: Intel Corporation Sunrise Point-LP HD Audio [8086:9d71] (rev 21) Summary === After upgrading from linux kernel 5.4 to 5.8, there is no more sound card available. However, if I select kernel 5.4 in GRUB, the sound card is available. Steps to reproduce == 1. Install 20.04 or 20.10 with a kenel 5.4 2. Check that sound output works as excepted (Settings > Sound > Output > Test) 3. Check that `alsa-info` command returns information 4. Upgrade kernel to 5.8 Expected results Sound output still works. Actual results == 2. Sound card is available, and sound can be output to the internal speakers. 4. No more sound card detected (Sound Settings display "Dummy Output" in the list of output devices). ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-41-generic 5.8.0-41.46 ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18 Uname: Linux 5.8.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Feb 9 14:42:00 2021 InstallationDate: Installed on 2019-01-20 (751 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Acer Swift SF314-54 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-41-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash mem_sleep_default=deep vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-41-generic N/A linux-backports-modules-5.8.0-41-generic N/A linux-firmware1.190.3 SourcePackage: linux UpgradeStatus: Upgraded to groovy on 2021-02-03 (5 days ago) dmi.bios.date: 11/21/2018 dmi.bios.release: 1.11 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.11 dmi.board.name: Strongbow_KL dmi.board.vendor: KBL dmi.board.version: V1.11 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.11 dmi.ec.firmware.release: 1.6 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.11:bd11/21/2018:br1.11:efr1.6:svnAcer:pnSwiftSF314-54:pvrV1.11:rvnKBL:rnStrongbow_KL:rvrV1.11:cvnAcer:ct10:cvrV1.11: dmi.product.family: Swift 3 dmi.produ
[Kernel-packages] [Bug 1875015] Re: Ubuntu 20.04 and Displaylink is extremely slow
** Bug watch removed: github.com/DisplayLink/evdi/issues #181 https://github.com/DisplayLink/evdi/issues/181 -- 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/1875015 Title: Ubuntu 20.04 and Displaylink is extremely slow Status in Nouveau Xorg driver: Unknown Status in OEM Priority Project: New Status in xf86-video-amd: Unknown Status in X.Org X server: Unknown Status in nvidia-graphics-drivers-470 package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Fix Released Status in xserver-xorg-video-amdgpu package in Ubuntu: In Progress Status in xserver-xorg-video-nouveau package in Ubuntu: In Progress Status in xorg-server source package in Focal: In Progress Status in xorg-server source package in Hirsute: In Progress Status in xorg-server source package in Impish: Fix Released Bug description: Using ubuntu 20.04 on displaylink docking with external monitor is totally slow, unusable. The GUI responds very slow, if you click, the command of the click goes on after about 3 seconds... if you type, all the letters are with the same lag, so it is totally unusable. Was using displaylink without any problem on 19.10 until yesterday, when I upgraded to 20.04. It is terrific. If i plug out the usb for the displaylink docking station, than the speed is back, and the system is ok, if I connect it to the docking station again, everything extremely slow again. Please investigate this asap, as it is unusable on displaylink docking stations. To manage notifications about this bug go to: https://bugs.launchpad.net/nouveau/+bug/1875015/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1955042] Re: SBI SRST extension is missing
** Changed in: linux-riscv (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-riscv in Ubuntu. https://bugs.launchpad.net/bugs/1955042 Title: SBI SRST extension is missing Status in linux-riscv package in Ubuntu: New Bug description: SBI SRST extension is needed for handling sifive unmatched reboot and with the reset now merged into openSBI package, enabling SRST extension finally gives us the possibility to reset the board. The patch to enable SRST extension can be found here: https://lore.kernel.org/all/20210609121322.3058-2-anup.pa...@wdc.com/ or use the attached patch. I tested it on top of 5.13.0-1006.6+22.04.1 on the unmatched board and it allows to successfully reboots the board. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/1955042/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1953249] Re: UVD firmware for AMD Southern Islands (GCN 1) GPUs is missing
** Changed in: linux-firmware (Ubuntu) Status: Confirmed => 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/1953249 Title: UVD firmware for AMD Southern Islands (GCN 1) GPUs is missing Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Focal: Fix Committed Bug description: [ Impact ] AMD GPU not functional on Focal with HWE kernel. [ Test Case ] See original description below. [ Fix ] Cherry-pick relevant commit from upstream linux-firmware. [ Where Problems Could Occur ] Broken graphics with AMD GPUs. [ Original Description ] Release: up-to-date Focal LTS (20.04.3) Package-version: linux-firmware 1.187.20 Hardware model: [AMD/ATI] Chelsea LP [Radeon HD 7730M] With the latest kernel upgrade (5.4 --> 5.11, if I recall correctly), my laptop's discrete graphics stopped working. Looking at the logs, I found these messages: -- snippet -- kernel: [1.492908] [drm] amdgpu: dpm initialized kernel: [1.492932] [drm] AMDGPU Display Connectors kernel: [1.492951] amdgpu :01:00.0: Direct firmware load for amdgpu/verde_uvd.bin failed with error -2 kernel: [1.492954] amdgpu :01:00.0: amdgpu: amdgpu_uvd: Can't load firmware "amdgpu/verde_uvd.bin" kernel: [1.492957] [drm:amdgpu_device_ip_init [amdgpu]] *ERROR* sw_init of IP block failed -2 kernel: [1.493196] amdgpu :01:00.0: amdgpu: amdgpu_device_ip_init failed kernel: [1.493198] amdgpu :01:00.0: amdgpu: Fatal error during GPU init kernel: [1.493200] amdgpu :01:00.0: amdgpu: amdgpu: finishing device. -- snippet -- In fact, file '/lib/firmware/amdgpu/verde_uvd.bin' was missing. Running '$ dpkg -L linux-firmware | sort' gives this: -- snippet -- /lib/firmware/amdgpu/vegam_uvd.bin /lib/firmware/amdgpu/vegam_vce.bin /lib/firmware/amdgpu/verde_ce.bin /lib/firmware/amdgpu/verde_k_smc.bin /lib/firmware/amdgpu/verde_mc.bin /lib/firmware/amdgpu/verde_me.bin /lib/firmware/amdgpu/verde_pfp.bin /lib/firmware/amdgpu/verde_rlc.bin /lib/firmware/amdgpu/verde_smc.bin /lib/firmware/amdgpu/yellow_carp_asd.bin /lib/firmware/amdgpu/yellow_carp_ce.bin -- snippet -- Copying the file from upstream (https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux- firmware.git/tree/amdgpu/verde_uvd.bin) didn't work on my system, probably because I use UEFI and the module wasn't signed (error below): -- snippet -- kernel: [ 502.174932] amdgpu :01:00.0: amdgpu: amdgpu_uvd: Can't validate firmware "amdgpu/verde_uvd.bin" kernel: [ 502.174992] [drm:amdgpu_device_ip_init [amdgpu]] *ERROR* sw_init of IP block failed -22 kernel: [ 502.175285] amdgpu :01:00.0: amdgpu: amdgpu_device_ip_init failed kernel: [ 502.175289] amdgpu :01:00.0: amdgpu: Fatal error during GPU init kernel: [ 502.175293] amdgpu :01:00.0: amdgpu: amdgpu: finishing device. -- snippet -- I can confirm that reverting kernel driver to 'radeonsi' makes the device usable again, but at the expense of Vulkan APIs (not supported by this driver). Could you, please, fix this? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1953249/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1954300] Re: mt7921e: Failed to start WM firmware
** No longer affects: linux-oem-5.13 (Ubuntu Impish)
** No longer affects: linux-oem-5.13 (Ubuntu Jammy)
** No longer affects: linux-oem-5.13 (Ubuntu)
** No longer affects: linux-oem-5.14 (Ubuntu Impish)
** No longer affects: linux-oem-5.14 (Ubuntu Jammy)
** No longer affects: linux-oem-5.14 (Ubuntu)
** No longer affects: linux (Ubuntu Focal)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1954300
Title:
mt7921e: Failed to start WM firmware
Status in HWE Next:
New
Status in OEM Priority Project:
New
Status in linux package in Ubuntu:
In Progress
Status in linux-firmware package in Ubuntu:
Fix Released
Status in linux-firmware source package in Focal:
Fix Committed
Status in linux-oem-5.13 source package in Focal:
Fix Released
Status in linux-oem-5.14 source package in Focal:
Fix Released
Status in linux source package in Impish:
Fix Committed
Status in linux-firmware source package in Impish:
Fix Committed
Status in linux source package in Jammy:
In Progress
Status in linux-firmware source package in Jammy:
Fix Released
Bug description:
[SRU Justification]
[Impact]
MT7921 might fail at device probe at boot:
mt7921e :03:00.0: WM Firmware Version: 01, Build Time:
20211014150922
IPv6: ADDRCONF(NETDEV_CHANGE): enp2s0: link becomes ready
mt7921e :03:00.0: Message 8002 (seq 9) timeout
mt7921e :03:00.0: Failed to start WM firmware
mt7921e: probe of :03:00.0 failed with error -110
[Fix]
Kernel fixes:
* 995d948cf2e4 ("Bluetooth: btusb: Return error code when getting patch status
failed")
* 00c0ee9850b7 ("Bluetooth: btusb: Handle download_firmware failure cases")
And firmware:
* 948cad200e94 ("linux-firmware: update frimware for mediatek bluetooth chip
(MT7921)")
[Test Case]
Run checkbox reboot stress tests to try trigger this issue:
$ checkbox-cli run com.canonical.certification::stress/reboot
[Where problems could occur]
This imports fixes requiring both kernel driver and proprietary firmware
updates, the firmware part might cause instability or so.
== original bug report ==
Oct 25 22:40:10 u kernel: [ 6.194102] mt7921e :03:00.0: WM Firmware
Version: 01, Build Time: 20211014150922
Oct 25 22:40:11 u kernel: [ 7.948458] rfkill: input handler disabled
Oct 25 22:40:12 u kernel: [ 9.012741] r8169 :02:00.0 enp2s0: Link is Up -
1Gbps/Full - flow control rx/tx
Oct 25 22:40:12 u kernel: [ 9.012766] IPv6: ADDRCONF(NETDEV_CHANGE): enp2s0:
link becomes ready
Oct 25 22:40:13 u kernel: [ 9.174471] usb 1-2.4: device descriptor read/64,
error -110
Oct 25 22:40:13 u kernel: [ 9.250459] mt7921e :03:00.0: Message 8002
(seq 9) timeout
Oct 25 22:40:13 u kernel: [ 9.250470] mt7921e :03:00.0: Failed to start
WM firmware
Oct 25 22:40:13 u kernel: [ 9.250596] mt7921e: probe of :03:00.0 failed
with error -110
This takes following fixes to resolve completely:
* kernel patch:
*
https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-next.git/commit/?id=995d948cf2e45834275f07afc1c9881a9902e73c
*
https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-next.git/commit/?id=00c0ee9850b7b0cb7c40b8daba806ae2245e59d4
* firmware:
*
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=948cad200e94d82d339207f8ac7b10f932bd627a
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1954300/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1918110] Re: overlay_map.dtb is in wrong location
** No longer affects: linux-raspi (Ubuntu) ** No longer affects: linux-raspi (Ubuntu Focal) ** No longer affects: linux-raspi (Ubuntu Groovy) ** No longer affects: linux-raspi (Ubuntu Hirsute) ** Changed in: flash-kernel (Ubuntu Groovy) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/1918110 Title: overlay_map.dtb is in wrong location Status in flash-kernel package in Ubuntu: Fix Released Status in flash-kernel source package in Focal: Confirmed Status in flash-kernel source package in Groovy: Won't Fix Status in flash-kernel source package in Hirsute: Fix Released Bug description: overlay_map.dtb is supposed to be located in /boot/firmware/overlays and *not* in /boot/firmware. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/1918110/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1919177] Re: Azure: issues with accelerated networking on Hirsute
** No longer affects: linux-azure (Ubuntu)
** No longer affects: linux-azure (Ubuntu Hirsute)
** No longer affects: cloud-init (Ubuntu Hirsute)
** No longer affects: cloud-init (Ubuntu)
** Project changed: cloud-init => ubuntu-translations
** No longer affects: ubuntu-translations
--
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/1919177
Title:
Azure: issues with accelerated networking on Hirsute
Status in systemd package in Ubuntu:
Fix Released
Status in systemd source package in Hirsute:
New
Bug description:
[General]
On Azure, when provisioning a Hirsute VM with Accelerated Networking
enabled, sometimes part of the cloud-init configuration is not
applied.
Especially, in those cases, the public SSH key is not setup properly.
[how to reproduce]
Start a VM with AN enabled:
```
az vm create --name "$VM_NAME --resource-group "$GROUP" --location "UK South"
--image
'Canonical:0001-com-ubuntu-server-hirsute-daily:21_04-daily-gen2:latest' --size
Standard_F8s_v2 --admin-username ubuntu --ssh-key-value "$SSH_KEY"
--accelerated-networking
```
After a moment, try to SSH: if you succeed, delete and recreate a new
VM.
[troubleshooting]
To be able to connect into the VM, run:
az vm run-command invoke -g "$GROUP" -n "$VM_NAME" --command-id
RunShellScript --scripts "sudo -u ubuntu ssh-import-id $LP_USERNAME"
```
In "/run/cloud-init/instance-data.json", I can see:
```
"publicKeys": [
{
"keyData": "",
"path": "/home/ubuntu/.ssh/authorized_keys"
}
],
```
as expected.
[workaround]
As mentioned, Azure allows the user to run command into the VM without
SSH connection. To do so, one can use the Azure CLI:
az vm run-command invoke -g "$GROUP" -n "$VM_NAME" --command-id
RunShellScript --scripts "sudo -u ubuntu ssh-import-id $LP_USERNAME"
This example uses "ssh-import-id" but it's also possible to just echo
a given public key into /home/ubuntu/.ssh/authorized_keys
NOTE: this will only solves the SSH issue, I do not know if this bug
affects other things. If so the user would have to apply those things
manually.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1919177/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1925211] Re: Hot-unplug of disks leaves broken block devices around in Hirsute on s390x
** No longer affects: systemd (Ubuntu) ** No longer affects: systemd (Ubuntu Hirsute) ** No longer affects: udev (Ubuntu) ** No longer affects: udev (Ubuntu Hirsute) -- 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/1925211 Title: Hot-unplug of disks leaves broken block devices around in Hirsute on s390x Status in Ubuntu on IBM z Systems: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Hirsute: Fix Released Bug description: SRU Justification [Impact] Hot removal of disks under kvm on s390 does not result in the kernel removing the block device, which can lead to hung tasks and other issues. [Test Plan] See steps to reproduce the bug in the original description below. To test, execute these steps and confirm that the block device gets removed as expected. [Where problems could occur] The fix is a revert of the changes which introduced this regression. The original commit was a removal of supposedly unused code, but it seems a mistake was made in the logic around unregistering of disks. Reverting the changes could have potential to introduce bugs related to other virt devices, especially if it interacts badly with subsequent driver changes. However, the patch reverted cleanly, and reverting restores the code to the state which has been working well in previous kernels and seems like the lowest risk option until a proper fix is available upstream. --- Repro: #1 Get a guest $ uvt-kvm create --disk 5 --password=ubuntu h release=hirsute arch=s390x label=daily $ uvt-kvm wait h release=hirsute arch=s390x label=daily #2 Attach and Detach disk $ sudo qemu-img create -f qcow2 /var/lib/libvirt/images/test.qcow2 10M $ virsh attach-disk h /var/lib/libvirt/images/test.qcow2 vdc $ virsh detach-disk h vdc From libvirts POV it is gone at this point $ virsh domblklist h Target Source -- vda /var/lib/uvtool/libvirt/images/hirsute-2nd-zfs.qcow vdb /var/lib/uvtool/libvirt/images/hirsute-2nd-zfs-ds.qcow But the guest thinks still it is present $ uvt-kvm ssh --insecure hirsute-2nd-zfs lsblk ... vdc252:32 0 20M 0 disk This even remains a while after (not a race). Any access to it in the guest will hang (as you'd expect of a non-existing blockdev) 4 017581739 20 0 12140 4800 - S+ pts/0 0:00 | \_ sudo mkfs.ext4 /dev/vdc 4 017591758 20 0 6924 1044 - D+ pts/0 0:00 | \_ mkfs.ext4 /dev/vdc The result above was originally found with hirsute-guest@hirsute-host on s390x I do NOT see the same with groovy-guest@hirsute-host on s390x I DO see the same with hirsute-guest@groovy-host on s390x => Guest version dependent not Host/Hipervisor dependent I DO see the same with ZFS disks AND LVM disks being added&removed => not type dependent I do NOT see the same on x86. => Arch dependent ?? ... the evidence slowly points towards an issue in the guest, damn we are so close to release - but non-fully detaching disks are critical in my POV :-/ Filing this as-is for awareness, but certainly this will need more debugging. Unsure where this is going to eventually I'll now file it for kernel/udev/systemd. If there are any known issues/components that are related let me know please! --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu65 Architecture: s390x ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: N/A CasperMD5CheckResult: unknown DistroRelease: Ubuntu 21.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Lspci-vt: -[:00]- Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Error: command ['lsusb', '-t'] failed with exit code 1: /sys/bus/usb/devices: No such file or directory Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: Package: udev PackageArchitecture: s390x PciMultimedia: ProcFB: ProcKernelCmdLine: root=LABEL=cloudimg-rootfs ProcVersionSignature: User Name 5.11.0-14.15-generic 5.11.12 RelatedPackageVersions: linux-restricted-modules-5.11.0-14-generic N/A linux-backports-modules-5.11.0-14-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: hirsute uec-images Uname: Linux 5.11.0-14-generic s390x UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video _MarkFo
[Kernel-packages] [Bug 1929371] Re: [SRU] there is always a "Rear Microphone - Built-in Audio" option on the input device list even if the microphone is unplugged
** Tags removed: verification-needed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to alsa-ucm-conf in Ubuntu.
https://bugs.launchpad.net/bugs/1929371
Title:
[SRU] there is always a "Rear Microphone - Built-in Audio" option on
the input device list even if the microphone is unplugged
Status in OEM Priority Project:
Fix Released
Status in alsa-ucm-conf package in Ubuntu:
Fix Released
Status in pulseaudio package in Ubuntu:
Fix Released
Status in alsa-ucm-conf source package in Focal:
Fix Released
Status in pulseaudio source package in Focal:
Fix Released
Status in alsa-ucm-conf source package in Hirsute:
Fix Released
Status in pulseaudio source package in Hirsute:
Fix Released
Bug description:
[Impact]
In Lenovo P520, which using a codec for front panel, the other codec for rear
panel and both are on a same card.
In this case, the rear Mic will present on input devices of "Sound
Settings" even if attaching nothing to rear mic jack.
[Fix]
For alsa-ucm-conf part, the Mic 2 should use "Rear Mic Jack" as JackControl
because of
```
control.18 {
iface CARD
name 'Rear Mic Jack'
value true
comment {
access read
type BOOLEAN
count 1
}
}
```
After applying "Rear Mic Jack", the rear Mic will not always there anymore
but it's not there as well if hot-plugging audio device on rear mic. Thus, it
needs to change pulseaudio to handle if all devices are off cases.
For pulseaudio, if there is no any audio devices attached, then
attaching an input device on rear mic jack. The port will not be
selected automatically because the profiles is off. It needs patch
pulseaudio to check off profiles (for dual codec case).
[Test]
After applying these patches, the rear mic jack works good in all cases (boot
without mic and then attach mic, boot with mic and then hotplug it) and other
functions (line-in / line-out) work pretty well.
[Where problems could occur]
This change only apply the bonus on below cases:
```
if ((has_input_port && found_available_input_port && !has_output_port) ||
(has_output_port && found_available_output_port && !has_input_port) ||
(has_input_port && found_available_input_port && has_output_port &&
found_available_output_port))
```
and these cases have been tested.
If there are some complex codec design then it might cause problem but so far
we didn't see that.
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1929371/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1875015] Re: Ubuntu 20.04 and Displaylink is extremely slow
** Bug watch removed: github.com/DisplayLink/evdi/issues #181 https://github.com/DisplayLink/evdi/issues/181 ** Bug watch removed: github.com/DisplayLink/evdi/issues #61 https://github.com/DisplayLink/evdi/issues/61 -- 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/1875015 Title: Ubuntu 20.04 and Displaylink is extremely slow Status in Nouveau Xorg driver: Unknown Status in OEM Priority Project: New Status in xf86-video-amd: Unknown Status in X.Org X server: Unknown Status in nvidia-graphics-drivers-470 package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Fix Released Status in xserver-xorg-video-amdgpu package in Ubuntu: In Progress Status in xserver-xorg-video-nouveau package in Ubuntu: In Progress Status in xorg-server source package in Focal: In Progress Status in xorg-server source package in Hirsute: In Progress Status in xorg-server source package in Impish: Fix Released Bug description: Using ubuntu 20.04 on displaylink docking with external monitor is totally slow, unusable. The GUI responds very slow, if you click, the command of the click goes on after about 3 seconds... if you type, all the letters are with the same lag, so it is totally unusable. Was using displaylink without any problem on 19.10 until yesterday, when I upgraded to 20.04. It is terrific. If i plug out the usb for the displaylink docking station, than the speed is back, and the system is ok, if I connect it to the docking station again, everything extremely slow again. Please investigate this asap, as it is unusable on displaylink docking stations. To manage notifications about this bug go to: https://bugs.launchpad.net/nouveau/+bug/1875015/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1875015] Re: Ubuntu 20.04 and Displaylink is extremely slow
** Bug watch removed: gitlab.freedesktop.org/xorg/xserver/-/issues #1183 https://gitlab.freedesktop.org/xorg/xserver/-/issues/1183 -- 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/1875015 Title: Ubuntu 20.04 and Displaylink is extremely slow Status in Nouveau Xorg driver: Unknown Status in OEM Priority Project: New Status in xf86-video-amd: Unknown Status in X.Org X server: Unknown Status in nvidia-graphics-drivers-470 package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Fix Released Status in xserver-xorg-video-amdgpu package in Ubuntu: In Progress Status in xserver-xorg-video-nouveau package in Ubuntu: In Progress Status in xorg-server source package in Focal: In Progress Status in xorg-server source package in Hirsute: In Progress Status in xorg-server source package in Impish: Fix Released Bug description: Using ubuntu 20.04 on displaylink docking with external monitor is totally slow, unusable. The GUI responds very slow, if you click, the command of the click goes on after about 3 seconds... if you type, all the letters are with the same lag, so it is totally unusable. Was using displaylink without any problem on 19.10 until yesterday, when I upgraded to 20.04. It is terrific. If i plug out the usb for the displaylink docking station, than the speed is back, and the system is ok, if I connect it to the docking station again, everything extremely slow again. Please investigate this asap, as it is unusable on displaylink docking stations. To manage notifications about this bug go to: https://bugs.launchpad.net/nouveau/+bug/1875015/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1875015] Re: Ubuntu 20.04 and Displaylink is extremely slow
** Bug watch added: gitlab.freedesktop.org/xorg/driver/xf86-video-amdgpu/-/issues #37 https://gitlab.freedesktop.org/xorg/driver/xf86-video-amdgpu/-/issues/37 ** Also affects: xf86-video-amd via https://gitlab.freedesktop.org/xorg/driver/xf86-video-amdgpu/-/issues/37 Importance: Unknown Status: Unknown ** Tags removed: fixed-upstream ** Tags added: patch-accepted-upstream -- 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/1875015 Title: Ubuntu 20.04 and Displaylink is extremely slow Status in Nouveau Xorg driver: Unknown Status in OEM Priority Project: New Status in xf86-video-amd: Unknown Status in X.Org X server: Unknown Status in nvidia-graphics-drivers-470 package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Fix Released Status in xserver-xorg-video-amdgpu package in Ubuntu: In Progress Status in xserver-xorg-video-nouveau package in Ubuntu: In Progress Status in xorg-server source package in Focal: In Progress Status in xorg-server source package in Hirsute: In Progress Status in xorg-server source package in Impish: Fix Released Bug description: Using ubuntu 20.04 on displaylink docking with external monitor is totally slow, unusable. The GUI responds very slow, if you click, the command of the click goes on after about 3 seconds... if you type, all the letters are with the same lag, so it is totally unusable. Was using displaylink without any problem on 19.10 until yesterday, when I upgraded to 20.04. It is terrific. If i plug out the usb for the displaylink docking station, than the speed is back, and the system is ok, if I connect it to the docking station again, everything extremely slow again. Please investigate this asap, as it is unusable on displaylink docking stations. To manage notifications about this bug go to: https://bugs.launchpad.net/nouveau/+bug/1875015/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1946686] Re: Fix zfs_get_data access to files with wrong generation causing panics
** Changed in: zfs-linux (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1946686 Title: Fix zfs_get_data access to files with wrong generation causing panics Status in zfs-linux package in Ubuntu: Fix Released Status in zfs-linux source package in Focal: Fix Committed Status in zfs-linux source package in Hirsute: Fix Committed Status in zfs-linux source package in Impish: Fix Released Bug description: == SRU Focal/Hirsute == [Impact] ZFS: Fix a panic while acquiring a lock. If TX_WRITE is create on a file, and the file is later deleted and a new directory is created on the same object id, it is possible that when zil_commit happens, zfs_get_data will be called on the new directory. This may result in panic as it tries to do range lock. Upstream ZFS bug #10593, #11682, upstream fix: commit 296a4a369bc1078a694f88570972330985b3b1b8 Author: Chunwei Chen Date: Fri Mar 19 22:53:31 2021 -0700 Fix zfs_get_data access to files with wrong generation This patch fixes this issue by record the generation number during zfs_log_write, so zfs_get_data can check if the object is valid. The fix is already in Ubuntu ZFS 2.0.6 in Impish. The fix is a relatively simple backport with only minor backporting effort required in moving some of the module specific upstream changes into the pre- renamed module specific os specific parts of the ZFS module. [Test Plan] This is difficult to reproduce, see https://github.com/openzfs/zfs/issues/10593 The fix has been tested with the complete ubuntu autotest ZFS regression tests that exercise ZFS core functionality (smoke tests), file system POSIX compliance (fs tests), extra XFS tests and every mount option with stress-ng file I/O stress tests. [Where problems could occur] This fix could regress the ZIL (ZFS intent log) commit writes since it modifies this code to now checks for generation numbers. Testing with ZFS autotests with intent logs have not found any regressions, but there is a risk that the ZIL functionality is affected. This could lead to corruption. -- As mentioned at https://answers.launchpad.net/ubuntu/+source/zfs- linux/+question/696659, the following pull request fixes a panic acquiring a lock: https://github.com/openzfs/zfs/pull/11682 This fix does not appear to be a part of the latest Ubuntu 20.04 release: zfsutils-linux: Installed: 0.8.3-1ubuntu12.12 Candidate: 0.8.3-1ubuntu12.12 Version table: *** 0.8.3-1ubuntu12.12 500 500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 0.8.3-1ubuntu12.9 500 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 0.8.3-1ubuntu12 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages Of note is this issue where the bug is reported against the Ubuntu 0.8.3 packages: https://github.com/openzfs/zfs/issues/10642 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1946686/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786013] Re: Packaging resync
** Changed in: linux-azure-edge (Ubuntu) Status: Confirmed => Fix Released ** Changed in: linux-azure (Ubuntu Precise) Status: Invalid => Won't Fix ** Changed in: linux-azure-edge (Ubuntu Cosmic) Status: Confirmed => Won't Fix ** Changed in: linux-azure-edge (Ubuntu Precise) Status: Invalid => Won't Fix ** Changed in: linux-azure-edge (Ubuntu Trusty) Status: Invalid => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packing resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1915117] Re: [Regression] Audio card [8086:9d71] not detected after upgrade from linux 5.4 to 5.8
** Bug watch removed: Debian Bug tracker #991591 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991591 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-topology-conf in Ubuntu. https://bugs.launchpad.net/bugs/1915117 Title: [Regression] Audio card [8086:9d71] not detected after upgrade from linux 5.4 to 5.8 Status in alsa-topology-conf package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in alsa-topology-conf source package in Focal: New Status in alsa-ucm-conf source package in Focal: Confirmed Status in linux source package in Focal: Confirmed Status in alsa-topology-conf source package in Hirsute: New Status in alsa-ucm-conf source package in Hirsute: Won't Fix Status in linux source package in Hirsute: Fix Released Status in alsa-topology-conf source package in Impish: Fix Released Status in alsa-ucm-conf source package in Impish: Won't Fix Status in linux source package in Impish: Fix Released Bug description: [SRU Justification] [Impact] Skylake, Kabylake, Kabylake-refresh, Amberlake and some other platforms where audio is of SPT (PCH) type, HDA (with DSP capabilities) plus DMIC configuration is supported on these with skylake driver since kernel 5.8. However, no sound card can be detected w/o the topology binary file in /lib/firmware and corresponding ucm file. [Fix] The kernel config CONFIG_SND_SOC_INTEL_SKYLAKE_HDAUDIO_CODEC needa to be enabled for the snd_soc_skl driver to support HDA+DMIC configuration. And the topology binary file and UCM files need to be located in the correct path based on Intel's suggestion. https://gist.github.com/crojewsk/4e6382bfb0dbfaaf60513174211f29cb. [Test] On the Skylake/Kabylake platforms with either the PCI device 8086:9d70 and 8086:9d71, boot up the machine and check the existence of the sound card by either 'aplay -l' or 'pactl list' command. [Where problems could occur] Should be low risk, it only affects limited Intel Platforms with particular PCI device IDs + HDA plus DMIC configuration. == Original Bug Description == Ubuntu version: 20.10 (updated from 20.04) Kernel: 5.8.0-41-generic #46-Ubuntu Manufacturer: Acer Product Name: Swift SF314-54 BIOS Revision: 1.11 Audio card: Realtek High Definition Audio Multimedia audio controller [0401]: Intel Corporation Sunrise Point-LP HD Audio [8086:9d71] (rev 21) Summary === After upgrading from linux kernel 5.4 to 5.8, there is no more sound card available. However, if I select kernel 5.4 in GRUB, the sound card is available. Steps to reproduce == 1. Install 20.04 or 20.10 with a kenel 5.4 2. Check that sound output works as excepted (Settings > Sound > Output > Test) 3. Check that `alsa-info` command returns information 4. Upgrade kernel to 5.8 Expected results Sound output still works. Actual results == 2. Sound card is available, and sound can be output to the internal speakers. 4. No more sound card detected (Sound Settings display "Dummy Output" in the list of output devices). ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-41-generic 5.8.0-41.46 ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18 Uname: Linux 5.8.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Feb 9 14:42:00 2021 InstallationDate: Installed on 2019-01-20 (751 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Acer Swift SF314-54 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-41-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash mem_sleep_default=deep vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-41-generic N/A linux-backports-modules-5.8.0-41-generic N/A linux-firmware1.190.3 SourcePackage: linux UpgradeStatus: Upgraded to groovy on 2021-02-03 (5 days ago) dmi.bios.date: 11/21/2018 dmi.bios.release: 1.11 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.11 dmi.board.name: Strongbow_KL dmi.board.vendor: KBL dmi.board.version: V1.11 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.11 dmi.ec.firmware.release: 1.6 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.11:bd11/21/2018:br1.11:efr1.6:svnAcer:pnSwiftSF314-54:pvrV1.11:rvnKBL:rnStrongbow_KL:rvrV1.11:cvnAcer:ct10:cvrV1.11: dmi.product.family: Swift 3 dmi.product.name: Swift SF314-54 dmi.product.sku: dmi.product.version: V1.11 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source
[Kernel-packages] [Bug 1945764] Re: crda: Fail to build against OpenSSL 3.0
** Changed in: crda (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to crda in Ubuntu. https://bugs.launchpad.net/bugs/1945764 Title: crda: Fail to build against OpenSSL 3.0 Status in crda package in Ubuntu: New Bug description: Hello, As part of a rebuild against OpenSSL3, this package failed to build on one or several architectures. You can find the details of the rebuild at https://people.canonical.com/~schopin/rebuilds/openssl-3.0.0-impish.html or for the amd64 failed build, directly at https://launchpadlibrarian.net/559464520/buildlog_ubuntu-impish- amd64.crda_4.14+git20191112.9856751-1.0~ssl3ppa1.1_BUILDING.txt.gz We're planning to transition to OpenSSL 3.0 for the 22.04 release, and consider this issue as blocking for this transition. For your tests, you can build against libssl-dev as found in the PPA schopin/openssl-3.0.0 I haven't found any mention of the issue upstream. However, a quick glance at the logs tells me the errors seem due to the use of deprecated APIs combined with -Werror. Thus, a quick fix might be to simply add -Wno-error=deprecated-declarations to the CFLAGS ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/crda/+bug/1945764/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1915117] Re: [Regression] Audio card [8086:9d71] not detected after upgrade from linux 5.4 to 5.8
** No longer affects: linux-firmware (Ubuntu Impish) ** No longer affects: linux-firmware (Ubuntu) ** No longer affects: linux-firmware (Ubuntu Focal) ** No longer affects: linux-firmware (Ubuntu Hirsute) -- 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/1915117 Title: [Regression] Audio card [8086:9d71] not detected after upgrade from linux 5.4 to 5.8 Status in alsa-topology-conf package in Ubuntu: New Status in linux package in Ubuntu: Fix Released Status in alsa-topology-conf source package in Focal: New Status in alsa-ucm-conf source package in Focal: Confirmed Status in linux source package in Focal: Confirmed Status in alsa-topology-conf source package in Hirsute: New Status in alsa-ucm-conf source package in Hirsute: Won't Fix Status in linux source package in Hirsute: Fix Released Status in alsa-topology-conf source package in Impish: New Status in alsa-ucm-conf source package in Impish: Won't Fix Status in linux source package in Impish: Fix Released Bug description: [SRU Justification] [Impact] Skylake, Kabylake, Kabylake-refresh, Amberlake and some other platforms where audio is of SPT (PCH) type, HDA (with DSP capabilities) plus DMIC configuration is supported on these with skylake driver since kernel 5.8. However, no sound card can be detected w/o the topology binary file in /lib/firmware and corresponding ucm file. [Fix] The kernel config CONFIG_SND_SOC_INTEL_SKYLAKE_HDAUDIO_CODEC needa to be enabled for the snd_soc_skl driver to support HDA+DMIC configuration. And the topology binary file and UCM files need to be located in the correct path based on Intel's suggestion. https://gist.github.com/crojewsk/4e6382bfb0dbfaaf60513174211f29cb. [Test] On the Skylake/Kabylake platforms with either the PCI device 8086:9d70 and 8086:9d71, boot up the machine and check the existence of the sound card by either 'aplay -l' or 'pactl list' command. [Where problems could occur] Should be low risk, it only affects limited Intel Platforms with particular PCI device IDs + HDA plus DMIC configuration. == Original Bug Description == Ubuntu version: 20.10 (updated from 20.04) Kernel: 5.8.0-41-generic #46-Ubuntu Manufacturer: Acer Product Name: Swift SF314-54 BIOS Revision: 1.11 Audio card: Realtek High Definition Audio Multimedia audio controller [0401]: Intel Corporation Sunrise Point-LP HD Audio [8086:9d71] (rev 21) Summary === After upgrading from linux kernel 5.4 to 5.8, there is no more sound card available. However, if I select kernel 5.4 in GRUB, the sound card is available. Steps to reproduce == 1. Install 20.04 or 20.10 with a kenel 5.4 2. Check that sound output works as excepted (Settings > Sound > Output > Test) 3. Check that `alsa-info` command returns information 4. Upgrade kernel to 5.8 Expected results Sound output still works. Actual results == 2. Sound card is available, and sound can be output to the internal speakers. 4. No more sound card detected (Sound Settings display "Dummy Output" in the list of output devices). ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-41-generic 5.8.0-41.46 ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18 Uname: Linux 5.8.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Feb 9 14:42:00 2021 InstallationDate: Installed on 2019-01-20 (751 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Acer Swift SF314-54 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-41-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash mem_sleep_default=deep vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-41-generic N/A linux-backports-modules-5.8.0-41-generic N/A linux-firmware1.190.3 SourcePackage: linux UpgradeStatus: Upgraded to groovy on 2021-02-03 (5 days ago) dmi.bios.date: 11/21/2018 dmi.bios.release: 1.11 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.11 dmi.board.name: Strongbow_KL dmi.board.vendor: KBL dmi.board.version: V1.11 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.11 dmi.ec.firmware.release: 1.6 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.11:bd11/21/2018:br1.11:efr1.6:svnAcer:pnSwiftSF314-54:pvrV1.11:rvnKBL:rnStrongbow_KL:rvrV1.11:cvnAcer:ct10:cvrV1.11: dmi.product.family: Swift 3 dmi.product.name: Swift SF314-54 dmi.product.sku: dmi.product.version: V1.11 dmi.sys.vendor: Acer To manage notificat
[Kernel-packages] [Bug 1946808] Re: zfs fails reverting to a previous snapshot on reboot when selected on grub
** Tags added: verification-needed-impish -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1946808 Title: zfs fails reverting to a previous snapshot on reboot when selected on grub Status in zfs-linux package in Ubuntu: Fix Released Status in zfs-linux source package in Impish: Fix Committed Bug description: [Impact] * zfs fails reverting to a previous snapshot on reboot when selected on grub * A miss-merge dropped initramfs hook changes, which result in failing to generate and use a new zfs uid. * Thus revert code to how it was before in https://launchpad.net/ubuntu/+source/zfs-linux/2.0.2-1ubuntu3 [Test Plan] * Create snapshot with $ zsysctl save test-sru --system * Reboot and attempt to boot into test-sru snapshot [Where problems could occur] * The change is to initramfs hook only, thus initrd generation and boot paths are affected. Only latest initrd is rebuilt, rather than old ones, meaning booting initrds of older kernel abis will not be resolved. [Other Info] * Original bug report After creating a snapshot with: zsysctl save 211012-linux13-19 -s the reboot fails as shown on the screenshot, the other screenshot shows the result of the snapshot. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: zsys 0.5.8 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: XFCE Date: Tue Oct 12 19:11:43 2021 InstallationDate: Installed on 2021-10-12 (0 days ago) InstallationMedia: Xubuntu 21.10 "Impish Indri" - Release amd64 (20211012) Mounts: Error: [Errno 40] Too many levels of symbolic links: '/proc/mounts' ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_zgtuq6@/vmlinuz-5.13.0-19-generic root=ZFS=rpool/ROOT/ubuntu_zgtuq6 ro quiet splash RelatedPackageVersions: zfs-initramfs 2.0.6-1ubuntu2 zfsutils-linux 2.0.6-1ubuntu2 SourcePackage: zsys SystemdFailedUnits: UpgradeStatus: No upgrade log present (probably fresh install) ZFSImportedPools: NAMESIZE ALLOC FREE CKPOINT EXPANDSZ FRAGCAP DEDUPHEALTH ALTROOT bpool 768M 79.2M 689M- - 0%10% 1.00xONLINE - rpool14G 3.33G 10.7G- - 1%23% 1.00xONLINE - ZFSListcache-bpool: bpool/boot off on on off on off on off - none- - - - - - - - bpool/BOOT noneoff on on off on off on off - none- - - - - - - - bpool/BOOT/ubuntu_zgtuq6 /boot on on on off on off on off - none- - - - - - - - ZSYSJournal: -- Journal begins at Tue 2021-10-12 18:10:37 AST, ends at Tue 2021-10-12 19:11:52 AST. -- -- No entries -- modified.conffile..etc.apt.apt.conf.d.90_zsys_system_autosnapshot: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1946808/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1938886] Re: rrr:no dh_strip or strip loose setuid bit
** No longer affects: virtualbox (Ubuntu) ** No longer affects: linux (Ubuntu) ** No longer affects: debugedit (Ubuntu) ** No longer affects: dash (Ubuntu) ** No longer affects: bash (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1938886 Title: rrr:no dh_strip or strip loose setuid bit Status in binutils package in Ubuntu: New Status in debhelper package in Ubuntu: Fix Released Bug description: Over at https://launchpadlibrarian.net/550715513/buildlog_ubuntu- hirsute-amd64.virtualbox_6.1.22-dfsg-2~ubuntu1.21.04.2_BUILDING.txt.gz I have rebuilt an earlier version of virtualbox, that sets Rules- Requires-Root: no and added extra ls statements to find where/when/why setuid bits are getting lost after fixperms. make[1]: Leaving directory '/<>' debian/rules override_dh_strip make[1]: Entering directory '/<>' ls -latr debian/virtualbox/usr/lib/virtualbox/VBoxSDL -rwsr-sr-x 1 buildd buildd 406808 Jul 29 14:34 debian/virtualbox/usr/lib/virtualbox/VBoxSDL ... dh_strip --dbgsym-migration='virtualbox-dbg' debugedit: debian/virtualbox/usr/lib/virtualbox/VBoxSDL.so: Unknown DWARF DW_FORM_0x1f20 a7cf3c43c8b18c3261d2d4737a475bf730ad1554 ls -latr debian/virtualbox/usr/lib/virtualbox/VBoxSDL -rwxr-xr-x 1 buildd buildd 166208 Jul 29 14:35 debian/virtualbox/usr/lib/virtualbox/VBoxSDL It seems to me that either dh_strip or something it calls (strip, debugedit) looses the setuid permission in hirsute and up. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1938886/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1942784] Re: makedumpfile falls back to cp on focal with 5.11 kernel
** No longer affects: makedumpfile (Ubuntu Hirsute)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to makedumpfile in Ubuntu.
https://bugs.launchpad.net/bugs/1942784
Title:
makedumpfile falls back to cp on focal with 5.11 kernel
Status in makedumpfile package in Ubuntu:
Fix Released
Status in makedumpfile source package in Focal:
Fix Committed
Bug description:
[IMPACT]
When running Focal with the hwe 5.11 kernel makedumpfile is not working as it
should.
Instead of compressing the dump makedumpfile falls back to cp.
This can create problems on systems with very large RAM and result into
exhausting all storage on the host.
[FIX]
This can be resolved with upstream commit f1197543d1c4 ([PATCH] Retrieve
MAX_PHYSMEM_BITS from vmcoreinfo).
The reason for falling back to cp is that without this patch makedumpfile
calculates wrongly the memory layout.
This happens after the kernel commit 1d50e5d0c505 ("crash_core, vmcoreinfo:
Append 'MAX_PHYSMEM_BITS'to vmcoreinfo").
With this commit applied, reading MAX_PHYSMEM_BITS from vmcoreinfo instead of
inferring lead to correctly detecting the memory layout and creating the dump
file properly.
[TEST CASE]
For testing a machine running focal with the 5.11 kernel is required.
Then trigger a crash.
On the console we can see that makedumpfile fails and `falls back to cp`.
In /var/crash we can see that no dmesg file is created and instead of the
dump file
the uncompressed vmcoreinfo is created.
[WHERE PROBLEMS COULD OCCUR]
Any regression potential would involve the crash dump not being
created after a crash in case kdump is configured.
[OTHER]
Only Focal with 5.11 kernel is affected.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1942784/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1929371] Re: [SRU] there is always a "Rear Microphone - Built-in Audio" option on the input device list even if the microphone is unplugged
** Changed in: oem-priority
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to alsa-ucm-conf in Ubuntu.
https://bugs.launchpad.net/bugs/1929371
Title:
[SRU] there is always a "Rear Microphone - Built-in Audio" option on
the input device list even if the microphone is unplugged
Status in OEM Priority Project:
Fix Released
Status in alsa-ucm-conf package in Ubuntu:
Fix Released
Status in pulseaudio package in Ubuntu:
Fix Released
Status in alsa-ucm-conf source package in Focal:
Fix Released
Status in pulseaudio source package in Focal:
Fix Released
Status in alsa-ucm-conf source package in Hirsute:
Fix Released
Status in pulseaudio source package in Hirsute:
Fix Released
Bug description:
[Impact]
In Lenovo P520, which using a codec for front panel, the other codec for rear
panel and both are on a same card.
In this case, the rear Mic will present on input devices of "Sound
Settings" even if attaching nothing to rear mic jack.
[Fix]
For alsa-ucm-conf part, the Mic 2 should use "Rear Mic Jack" as JackControl
because of
```
control.18 {
iface CARD
name 'Rear Mic Jack'
value true
comment {
access read
type BOOLEAN
count 1
}
}
```
After applying "Rear Mic Jack", the rear Mic will not always there anymore
but it's not there as well if hot-plugging audio device on rear mic. Thus, it
needs to change pulseaudio to handle if all devices are off cases.
For pulseaudio, if there is no any audio devices attached, then
attaching an input device on rear mic jack. The port will not be
selected automatically because the profiles is off. It needs patch
pulseaudio to check off profiles (for dual codec case).
[Test]
After applying these patches, the rear mic jack works good in all cases (boot
without mic and then attach mic, boot with mic and then hotplug it) and other
functions (line-in / line-out) work pretty well.
[Where problems could occur]
This change only apply the bonus on below cases:
```
if ((has_input_port && found_available_input_port && !has_output_port) ||
(has_output_port && found_available_output_port && !has_input_port) ||
(has_input_port && found_available_input_port && has_output_port &&
found_available_output_port))
```
and these cases have been tested.
If there are some complex codec design then it might cause problem but so far
we didn't see that.
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1929371/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1893002] Re: alsa-ucm-conf: the rear mic on Lenovo p520 can't be detected when hot plugging
*** This bug is a duplicate of bug 1929371 *** https://bugs.launchpad.net/bugs/1929371 ** This bug has been marked a duplicate of bug 1929371 [SRU] there is always a "Rear Microphone - Built-in Audio" option on the input device list even if the microphone is unplugged -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/1893002 Title: alsa-ucm-conf: the rear mic on Lenovo p520 can't be detected when hot plugging Status in alsa-ucm-conf package in Ubuntu: Fix Released Status in alsa-ucm-conf source package in Focal: Fix Released Status in alsa-ucm-conf source package in Groovy: Won't Fix Bug description: This bug is for tracking purpose. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/1893002/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1939177] Re: Ubuntu 20.04.2 LTS kernel 5.11.0-25 zfs send | receive broken
** Changed in: zfs-linux (Ubuntu) Status: Confirmed => Fix Released ** Changed in: zfs-linux (Ubuntu Focal) Importance: Undecided => High -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1939177 Title: Ubuntu 20.04.2 LTS kernel 5.11.0-25 zfs send | receive broken Status in zfs-linux package in Ubuntu: Fix Released Status in zfs-linux source package in Focal: Fix Released Bug description: == SRU Justification Focal == [Impact] https://github.com/openzfs/zfs/issues/12462 Ubuntu 20.04.2 LTS Kernel: 5.11.0-25-generic #27~20.04.1-Ubuntu zfs-0.8.3-1ubuntu12.12 zfs-kmod-2.0.2-1ubuntu5 Trying to run zfs send | receive and getting an error: # zfs send 'rpool/home'@'autosnap_2020-08-01_00:59:01_monthly' | zfs receive -s -F 'nas/rpool_backup/home' cannot receive: failed to read from stream cannot receive new filesystem stream: dataset does not exist This used to work before the recent Ubuntu kernel update from 5.8 to 5.11 Kernel 5.8 came with zfs-kmod-0.8.4-1ubuntu11.2 Ubuntu updates that broke it: Upgrade: linux-headers-generic-hwe-20.04:amd64 (5.8.0.63.71~20.04.45, 5.11.0.25.27~20.04.10), linux- image-generic-hwe-20.04:amd64 (5.8.0.63.71~20.04.45, 5.11.0.25.27~20.04.10), linux-generic-hwe-20.04 :amd64 (5.8.0.63.71~20.04.45, 5.11.0.25.27~20.04.10) Sending the zfs send part to a file works, but then sending the file to zfs receive also fails. The dump file size seems reasonable but the contents may not be correct. [Test Plan] 1. create test pool and backup pool sudo zpool create pool /dev/vdb1 sudo zpool create backup /dev/vdc1 2. populate pool with some files and create some snapshots sudo zfs snapshot pool@now1 create some more files etc, make another snapshot sudo zfs snapshot pool@now2 3. perform send/recv using -s option: sudo zfs send pool@now1 | sudo zfs receive -vFs backup sudo zfs send -i pool@now1 pool@now2 | sudo zfs receive -vFs backup Without the fix, the -s option on the receive fails. With the fix it works fine. Test with focal 5.4 and 5.11 kernel to exercise 0.8.x and 2.x kernel ZFS drivers. [Where problems could occur] The main fix nullifies the deprecated action_handle option so that it's not checked, this allows 0.8.x userspace it to be forwardly compatible with 2.x kernel ZFS and also since it is deprecated in 0.8.x it makes not difference to the 0.8.x kernel ZFS driver. Thus the risk with patch action_handle is very small. Included in the fix is a send/recv upstream bug fix 4910-Fix-EIO-after-resuming-receive-of-new-dataset-over-a.patch that makes send/recv more resilient by making zfs receive to always unmount and remount the destination, regardless of whether the stream is a new stream or a resumed stream. The change is upstream for ~10 months and has minimal impact on current recv functionality. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1939177/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1941708] Re: BlueZ 5.62 release
** Changed in: bluez (Ubuntu) Importance: Undecided => Wishlist ** Tags added: upgrade-software-version -- 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/1941708 Title: BlueZ 5.62 release Status in bluez package in Ubuntu: In Progress Bug description: BlueZ 5.62 release is out: https://mirrors.edge.kernel.org/pub/linux/bluetooth/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1941708/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1915117] Re: [Regression] Audio card [8086:9d71] not detected after upgrade from linux 5.4 to 5.8
** Tags added: regression-release ** Changed in: linux (Ubuntu Focal) Importance: Undecided => High ** Changed in: linux (Ubuntu Hirsute) Importance: Undecided => High ** Changed in: linux (Ubuntu Impish) Importance: Undecided => High -- 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/1915117 Title: [Regression] Audio card [8086:9d71] not detected after upgrade from linux 5.4 to 5.8 Status in alsa-topology-conf package in Ubuntu: New Status in linux package in Ubuntu: Fix Released Status in linux-firmware package in Ubuntu: Confirmed Status in alsa-topology-conf source package in Focal: New Status in alsa-ucm-conf source package in Focal: Confirmed Status in linux source package in Focal: Confirmed Status in linux-firmware source package in Focal: Confirmed Status in alsa-topology-conf source package in Hirsute: New Status in alsa-ucm-conf source package in Hirsute: Won't Fix Status in linux source package in Hirsute: Fix Released Status in linux-firmware source package in Hirsute: Confirmed Status in alsa-topology-conf source package in Impish: New Status in alsa-ucm-conf source package in Impish: Won't Fix Status in linux source package in Impish: Fix Released Status in linux-firmware source package in Impish: Confirmed Bug description: [SRU Justification] [Impact] Skylake, Kabylake, Kabylake-refresh, Amberlake and some other platforms where audio is of SPT (PCH) type, HDA (with DSP capabilities) plus DMIC configuration is supported on these with skylake driver since kernel 5.8. However, no sound card can be detected w/o the topology binary file in /lib/firmware and corresponding ucm file. [Fix] The kernel config CONFIG_SND_SOC_INTEL_SKYLAKE_HDAUDIO_CODEC needa to be enabled for the snd_soc_skl driver to support HDA+DMIC configuration. And the topology binary file and UCM files need to be located in the correct path based on Intel's suggestion. https://gist.github.com/crojewsk/4e6382bfb0dbfaaf60513174211f29cb. [Test] On the Skylake/Kabylake platforms with either the PCI device 8086:9d70 and 8086:9d71, boot up the machine and check the existence of the sound card by either 'aplay -l' or 'pactl list' command. [Where problems could occur] Should be low risk, it only affects limited Intel Platforms with particular PCI device IDs + HDA plus DMIC configuration. == Original Bug Description == Ubuntu version: 20.10 (updated from 20.04) Kernel: 5.8.0-41-generic #46-Ubuntu Manufacturer: Acer Product Name: Swift SF314-54 BIOS Revision: 1.11 Audio card: Realtek High Definition Audio Multimedia audio controller [0401]: Intel Corporation Sunrise Point-LP HD Audio [8086:9d71] (rev 21) Summary === After upgrading from linux kernel 5.4 to 5.8, there is no more sound card available. However, if I select kernel 5.4 in GRUB, the sound card is available. Steps to reproduce == 1. Install 20.04 or 20.10 with a kenel 5.4 2. Check that sound output works as excepted (Settings > Sound > Output > Test) 3. Check that `alsa-info` command returns information 4. Upgrade kernel to 5.8 Expected results Sound output still works. Actual results == 2. Sound card is available, and sound can be output to the internal speakers. 4. No more sound card detected (Sound Settings display "Dummy Output" in the list of output devices). ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-41-generic 5.8.0-41.46 ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18 Uname: Linux 5.8.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Feb 9 14:42:00 2021 InstallationDate: Installed on 2019-01-20 (751 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Acer Swift SF314-54 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-41-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash mem_sleep_default=deep vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-41-generic N/A linux-backports-modules-5.8.0-41-generic N/A linux-firmware1.190.3 SourcePackage: linux UpgradeStatus: Upgraded to groovy on 2021-02-03 (5 days ago) dmi.bios.date: 11/21/2018 dmi.bios.release: 1.11 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.11 dmi.board.name: Strongbow_KL dmi.board.vendor: KBL dmi.board.version: V1.11 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.11 dmi.ec.firmware.release: 1.6 dmi.modalias: dmi:bvnInsydeCorp.:bvr
[Kernel-packages] [Bug 1885942] Re: Focal update: v5.4.50 upstream stable release
** Changed in: linux (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1885942 Title: Focal update: v5.4.50 upstream stable release Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Released Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.4.50 upstream stable release from git://git.kernel.org/ block/bio-integrity: don't free 'buf' if bio_integrity_add_page() failed enetc: Fix tx rings bitmap iteration range, irq handling geneve: allow changing DF behavior after creation ibmveth: Fix max MTU limit mld: fix memory leak in ipv6_mc_destroy_dev() mvpp2: ethtool rxtx stats fix net: bridge: enfore alignment for ethernet address net: core: reduce recursion limit value net: Do not clear the sock TX queue in sk_set_socket() net: fix memleak in register_netdevice() net: Fix the arp error in some cases net: increment xmit_recursion level in dev_direct_xmit() net: usb: ax88179_178a: fix packet alignment padding openvswitch: take into account de-fragmentation/gso_size in execute_check_pkt_len rocker: fix incorrect error handling in dma_rings_init rxrpc: Fix notification call on completion of discarded calls sctp: Don't advertise IPv4 addresses if ipv6only is set on the socket tcp: don't ignore ECN CWR on pure ACK tcp: grow window for OOO packets only for SACK flows tg3: driver sleeps indefinitely when EEH errors exceed eeh_max_freezes ip6_gre: fix use-after-free in ip6gre_tunnel_lookup() net: phy: Check harder for errors in get_phy_id() ip_tunnel: fix use-after-free in ip_tunnel_lookup() sch_cake: don't try to reallocate or unshare skb unconditionally sch_cake: don't call diffserv parsing code when it is not needed sch_cake: fix a few style nits tcp_cubic: fix spurious HYSTART_DELAY exit upon drop in min RTT Revert "i2c: tegra: Fix suspending in active runtime PM state" btrfs: fix a block group ref counter leak after failure to remove block group net: sched: export __netdev_watchdog_up() fix a braino in "sparc32: fix register window handling in genregs32_[gs]et()" ALSA: usb-audio: Fix potential use-after-free of streams binder: fix null deref of proc->context USB: ohci-sm501: Add missed iounmap() in remove usb: dwc2: Postponed gadget registration to the udc class driver usb: add USB_QUIRK_DELAY_INIT for Logitech C922 USB: ehci: reopen solution for Synopsys HC bug usb: host: xhci-mtk: avoid runtime suspend when removing hcd xhci: Poll for U0 after disabling USB2 LPM usb: host: ehci-exynos: Fix error check in exynos_ehci_probe() usb: typec: tcpci_rt1711h: avoid screaming irq causing boot hangs ALSA: usb-audio: Add implicit feedback quirk for SSL2+. ALSA: usb-audio: add quirk for Denon DCD-1500RE ALSA: usb-audio: add quirk for Samsung USBC Headset (AKG) ALSA: usb-audio: Fix OOB access of mixer element list usb: cdns3: trace: using correct dir value usb: cdns3: ep0: fix the test mode set incorrectly usb: cdns3: ep0: add spinlock for cdns3_check_new_setup scsi: qla2xxx: Keep initiator ports after RSCN scsi: zfcp: Fix panic on ERP timeout for previously dismissed ERP action cifs: Fix cached_fid refcnt leak in open_shroot cifs/smb3: Fix data inconsistent when punch hole cifs/smb3: Fix data inconsistent when zero file range xhci: Fix incorrect EP_STATE_MASK xhci: Fix enumeration issue when setting max packet size for FS devices. xhci: Return if xHCI doesn't support LPM cdc-acm: Add DISABLE_ECHO quirk for Microchip/SMSC chip loop: replace kill_bdev with invalidate_bdev IB/mad: Fix use after free when destroying MAD agent IB/hfi1: Fix module use count flaw due to leftover module put calls bus: ti-sysc: Flush posted write on enable and disable bus: ti-sysc: Ignore clockactivity unless specified as a quirk ARM: OMAP2+: Fix legacy mode dss_reset xfrm: Fix double ESP trailer insertion in IPsec crypto offload. ASoC: q6asm: handle EOS correctly efi/tpm: Verify event log header before parsing efi/esrt: Fix reference count leak in esre_create_sysfs_entry. ASoc: q6afe: add support to get port direction ASoC: qcom: common: set correct directions for dailinks regualtor: pfuze100: correct sw1a/sw2 on pfuze3000 RDMA/siw: Fix pointer-to-int-cast warning in siw_rx_pbl() ASoC: fsl_ssi: Fix bclk calculation for mono channel samples/bpf: xdp_redirect_cp
[Kernel-packages] [Bug 1895132] Re: s390x broken with unknown syscall number on kernels < 5.8
** Changed in: linux (Ubuntu)
Status: Invalid => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1895132
Title:
s390x broken with unknown syscall number on kernels < 5.8
Status in Ubuntu on IBM z Systems:
Fix Released
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Bionic:
Fix Released
Status in linux source package in Focal:
Fix Released
Bug description:
SRU Justification
Note: I marked this as affecting bionic as well, as discovered in bug
1916485.
Impact: On kernels prior to 5.8 when a task is in traced state (due to
audit, ptrace, or seccomp) s390x and a syscall is issued that the
kernel doesn't know about s390x will not return ENOSYS in r2 but
instead will return the syscall number. This breaks userspace all over
the place. The following program compiled on s390x will output 500
instead of -ENOSYS:
root@test:~# cat test.c
#define _GNU_SOURCE
#include
#include
#include
#include
#include
#include
#include
#include
#include
#include
#include
#include
#include
static inline int dummy_inline_asm(void)
{
register long r1 asm("r1") = 500;
register long r2 asm("r2") = -1;
register long r3 asm("r3") = -1;
register long r4 asm("r4") = -1;
register long r5 asm("r5") = -1;
register long __res_r2 asm("r2");
asm volatile(
"svc 0\n\t"
: "=d"(__res_r2)
: "d"(r1), "0"(r2), "d"(r3), "d"(r4), "d"(r5)
: "memory");
return (int) __res_r2;
}
static inline int dummy_syscall(void)
{
return syscall(500, -1, -1, -1, -1);
}
int main(int argc, char *argv[])
{
printf("Uhm: %d\n", dummy_inline_asm());
printf("Uhm: %d\n", dummy_syscall());
exit(EXIT_SUCCESS);
}
This breaks LXD on s390x currently completely as well as strace.
Fix: Backport
commit cd29fa798001075a554b978df3a64e6656c25794
Author: Sven Schnelle
Date: Fri Mar 6 13:18:31 2020 +0100
s390/ptrace: return -ENOSYS when invalid syscall is supplied
The current code returns the syscall number which an invalid
syscall number is supplied and tracing is enabled. This makes
the strace testsuite fail.
Signed-off-by: Sven Schnelle
Signed-off-by: Vasily Gorbik
which got released with 5.8. The commit missed to Cc stable and
although I've asked Sven to include it in stable I'm not sure when or
if it will show up there.
Regression Potential: Limited to s390x.
Test Case: The reproducer given above needs to output -ENOSYS instead
of 500.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1895132/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1930188] Re: Acer Aspire 5 sound driver issues
** Also affects: alsa-ucm-conf (Ubuntu) Importance: Undecided Status: New ** No longer affects: linux (Ubuntu Focal) ** No longer affects: linux (Ubuntu Hirsute) ** No longer affects: linux (Ubuntu Impish) ** No longer affects: pulseaudio (Ubuntu Focal) ** No longer affects: pulseaudio (Ubuntu Hirsute) ** Also affects: pulseaudio (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: alsa-ucm-conf (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: pulseaudio (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: alsa-ucm-conf (Ubuntu Hirsute) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Focal) Status: New => Fix Released ** Changed in: linux (Ubuntu Hirsute) Status: New => Fix Released ** Changed in: pulseaudio (Ubuntu Focal) Status: New => In Progress ** Changed in: pulseaudio (Ubuntu Hirsute) Status: New => In Progress ** Changed in: pulseaudio (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: pulseaudio (Ubuntu Hirsute) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Focal) Assignee: (unassigned) => Hui Wang (hui.wang) ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Hirsute) Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/1930188 Title: Acer Aspire 5 sound driver issues Status in alsa-ucm-conf package in Ubuntu: New Status in linux package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: Fix Released Status in alsa-ucm-conf source package in Focal: New Status in linux source package in Focal: Fix Released Status in pulseaudio source package in Focal: In Progress Status in alsa-ucm-conf source package in Hirsute: New Status in linux source package in Hirsute: Fix Released Status in pulseaudio source package in Hirsute: In Progress Bug description: SRU Justification for alsa-ucm-conf: [Impact] On the machines with the sof audio driver, users could adjust the input volume from UI, but this only adjusts the "Capture Volume", the "Mic Boost" can't be changed, if "Mic Boost" is 0, even we adjust the "Capture Volume" to max, the recorded volume is still very low. [Fix] Backport a upstream patch, the patch adds the "Mic Boost" into the ucm [Test] plug a headset, make sure the headset-mic is the active input device, adjust the input volume to %20, open a terminal and run alsamixer, check the "Capture Volume" and "Mic Boost" value, then adjust the input volume to 80%, check those values and we could see both values are changed. [Where problems could occur] This patch could make the parse of input volume control fail, then the input volume can't be changed anymore when users adjust the volume from UI. But this possibility is very low, I tested this patch on many lenovo and dell machines with sof audio driver, all worked well. SRU Justification for pulseaudio: [Impact] On the machines with the sof audio driver, after booting up, the active output device is speaker by default, we adjust the output volume to 100%, then we plug a headphone, and adjust the output volume from 100% to 20%, now in theory, the speaker's volume is 100%, the headphone's volume is 20%. We plugout the headphone, the active output device becomes speaker and we expect the volume changes to 100%, but the output volume for speaker is 20%. [Fix] Backport a upstream patch, this patch is already in the pulseaudio-15.0, so impish already has this fix. Only hirsute and focal need to backport this patch. [Test] adjust speaker's volume to 80%, then plug headphone and adjust headphone's volume to 20%, unplug the headphone, the speaker's volume becomes to 80%, plug the headphone, the headphone's volume becomes to 20%. [Where problems could occur] The patch writes the output volume to hardware immediately when switching output device on the machines with sof audio driver, this could introduce pop noise when changing the output device, but this possibility is very low, I tested the patch on many lenovo and dell machines with sof audio driver, all worked as expected and have no pop noise when switching output device. The patch was merged to ubuntu 5.13.0 and 5.11.0 generic kernels with stable update already, but it is not merged to ubuntu 5.4.0 kernel yet, so I
[Kernel-packages] [Bug 1845677] Re: volume control doesn't work (it's just on/off) on Lenovo ThinkPad X1 Carbon 7th gen
** Changed in: linux (Ubuntu Bionic) Status: Invalid => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1845677 Title: volume control doesn't work (it's just on/off) on Lenovo ThinkPad X1 Carbon 7th gen Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: Won't Fix Status in linux-oem-osp1 source package in Bionic: Fix Committed Status in linux source package in Eoan: Won't Fix Status in linux source package in Focal: In Progress Bug description: [Impact] There are 2 physical speakers on the X1 7th, and one is Bass speaker and connect to a DAC which doesn't have volume control on it. [Fix] adjust that speaker to connect to a DAC which has volume control capability. [Test Case] adjust the output volume from UI and play sound from speaker. [Regression Risk] Low, these change is specific to 2 lenovo machines. On my Lenovo ThinkPad X1 Carbon 7th generation using the built-in speakers, the volume is either off or on, there's no gradation in volume when I move the slider up or down. If I enable Over-Amplification than there's gradation in volume when I turn the volume up past 100%, but not for 0-100%. This problem does not occur with a headset plugged into the 3.5mm jack. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-12-generic 5.3.0-12.13 ProcVersionSignature: Ubuntu 5.3.0-12.13-generic 5.3.0 Uname: Linux 5.3.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jik3746 F pulseaudio /dev/snd/pcmC0D0p: jik3746 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Sep 27 11:07:44 2019 InstallationDate: Installed on 2019-09-12 (14 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: LENOVO 20QD001VUS ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-12-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-12-generic N/A linux-backports-modules-5.3.0-12-generic N/A linux-firmware1.182 SourcePackage: linux UpgradeStatus: Upgraded to eoan on 2019-09-20 (7 days ago) dmi.bios.date: 07/04/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N2HET30W (1.13 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QD001VUS 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.modalias: dmi:bvnLENOVO:bvrN2HET30W(1.13):bd07/04/2019:svnLENOVO:pn20QD001VUS:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QD001VUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 7th dmi.product.name: 20QD001VUS dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th dmi.product.version: ThinkPad X1 Carbon 7th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1845677/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1890231] Re: alsa: should not load sof driver if the internal mic connects to the codec
** No longer affects: linux-oem-5.6 (Ubuntu)
** Changed in: hwe-next
Status: New => 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/1890231
Title:
alsa: should not load sof driver if the internal mic connects to the
codec
Status in HWE Next:
Fix Released
Status in linux-oem-5.6 source package in Focal:
Fix Released
Bug description:
This issue was introduced by #1872916 ("Support Intel Soundwire
in 5.6-OEM Kernel 20.04"), so focal and groovy kernels don't need
this fix.
[Impact]
We found the sof driver instead of hda driver is enabled on a dell
machine without soundwire and dmic. This will make gnome show dummy
output and users have no audio device to use.
[Fix]
When we integrated fix for #1872916, we backported 2 patches, these
2 patches enable the sof driver unconditionally for Dell comet lake
machines. There is an upstream patch to fix it, let the sof driver
enable conditionally on comet lake machines.
[Test Case]
Boot the kernel with this patch on that dell machine, check the
gnome-control-center, all audio devices exist, playback and recording
work well.
[Regression Risk]
On Dell Comet Lake machines with DMIC, the sof driver should be
enabled. Without this patch, the sof driver will be enabled unconditionally,
but with this patch, the sof driver will be enabled conditionally, so it is
possible to introduce a regression that on Dell Comet Lake machines, the sof
driver is not enabled even the machine has DMIC.
I have tested this patch on a Dell Comet Lake dmic machines, it worked
well.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1890231/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1909814] Re: Medion Notebook Keyboard not working
** No longer affects: linux-oem-5.10 (Ubuntu) ** No longer affects: linux-oem-5.10 (Ubuntu Focal) ** No longer affects: linux-oem-5.10 (Ubuntu Hirsute) ** No longer affects: linux-oem-5.10 (Ubuntu 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/1909814 Title: Medion Notebook Keyboard not working Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: In Progress Status in linux source package in Hirsute: In Progress Status in linux source package in Impish: In Progress Bug description: [Impact] The keyboard of some medion laptops can't work under Linux. [Fix] Backport a upstream patch, after applying the patch, the keyboard will skip the irq override from the acpi resource layer, and the keyboard could work normally. [Test] Booting the patched kernel, use the keyboard to do the input. [Where problems could occur] The patch will skip the irq override based on the DMI info, so if a medion laptop which has the same DMI info and the irq 1 needs to be overriden, this patch will introduce regression on the machine, but this possibility is very low. If this happens, we will consider to add more DMI match info in the table. Hello, Brand new laptop (Medion), keyboard is only working with the grub menu. Mouse is now working since 20.10 have been installed. Only the luminosity key are working on the keyboard. External usb keyboard works fine. I tried to install with usb keyboard disconnected but doesn't change anything. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-25-generic 5.8.0-25.26 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: did4364 F pulseaudio /dev/snd/pcmC0D0p: did4364 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jan 1 16:24:12 2021 InstallationDate: Installed on 2021-01-01 (0 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: MEDION S15450 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-25-generic root=UUID=da76ef9f-aca8-4bb0-94a9-03b7cc82a59a ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-25-generic N/A linux-backports-modules-5.8.0-25-generic N/A linux-firmware1.190.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/24/2020 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 209 dmi.board.asset.tag: Default string dmi.board.name: M15T dmi.board.vendor: MEDION dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: MEDION dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr209:bd11/24/2020:br5.19:svnMEDION:pnS15450:pvrDefaultstring:rvnMEDION:rnM15T:rvrDefaultstring:cvnMEDION:ct10:cvrDefaultstring: dmi.product.family: Akoya dmi.product.name: S15450 dmi.product.sku: ML-230008 30030452 dmi.product.version: Default string dmi.sys.vendor: MEDION To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1909814/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1845677] Re: volume control doesn't work (it's just on/off) on Lenovo ThinkPad X1 Carbon 7th gen
** No longer affects: linux-oem-osp1 (Ubuntu) ** No longer affects: linux-oem-osp1 (Ubuntu Eoan) ** No longer affects: linux-oem-osp1 (Ubuntu Focal) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-osp1 in Ubuntu. https://bugs.launchpad.net/bugs/1845677 Title: volume control doesn't work (it's just on/off) on Lenovo ThinkPad X1 Carbon 7th gen Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: Invalid Status in linux-oem-osp1 source package in Bionic: Fix Committed Status in linux source package in Eoan: Won't Fix Status in linux source package in Focal: In Progress Bug description: [Impact] There are 2 physical speakers on the X1 7th, and one is Bass speaker and connect to a DAC which doesn't have volume control on it. [Fix] adjust that speaker to connect to a DAC which has volume control capability. [Test Case] adjust the output volume from UI and play sound from speaker. [Regression Risk] Low, these change is specific to 2 lenovo machines. On my Lenovo ThinkPad X1 Carbon 7th generation using the built-in speakers, the volume is either off or on, there's no gradation in volume when I move the slider up or down. If I enable Over-Amplification than there's gradation in volume when I turn the volume up past 100%, but not for 0-100%. This problem does not occur with a headset plugged into the 3.5mm jack. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-12-generic 5.3.0-12.13 ProcVersionSignature: Ubuntu 5.3.0-12.13-generic 5.3.0 Uname: Linux 5.3.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jik3746 F pulseaudio /dev/snd/pcmC0D0p: jik3746 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Sep 27 11:07:44 2019 InstallationDate: Installed on 2019-09-12 (14 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: LENOVO 20QD001VUS ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-12-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-12-generic N/A linux-backports-modules-5.3.0-12-generic N/A linux-firmware1.182 SourcePackage: linux UpgradeStatus: Upgraded to eoan on 2019-09-20 (7 days ago) dmi.bios.date: 07/04/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N2HET30W (1.13 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QD001VUS 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.modalias: dmi:bvnLENOVO:bvrN2HET30W(1.13):bd07/04/2019:svnLENOVO:pn20QD001VUS:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QD001VUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 7th dmi.product.name: 20QD001VUS dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th dmi.product.version: ThinkPad X1 Carbon 7th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1845677/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1940488] Re: dell300x: rsi wifi and bluetooth crash after suspend and resume
** Tags added: suspend-resume ** No longer affects: linux-dell300x (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-dell300x in Ubuntu. https://bugs.launchpad.net/bugs/1940488 Title: dell300x: rsi wifi and bluetooth crash after suspend and resume Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: Fix Committed Status in linux-dell300x source package in Bionic: Fix Released Bug description: I tested the upstream stable kernel 4.19.191, also could reproduce this issue, and reported this testing result to stable mail list. [Impact] On the Dell300x machine, after system suspend and resume, the wifi and bluetooth can't work anymore. [Fix] Revert a patch which was applied to bionic kernel from stable update. [Test] Booting up with the patched kernel, run $sudo rtcwake -m freeze -s 10, then check dmesg to make sure there is crashing log, and run 'nmcli d wifi' and 'bluetoothctl, power on, scan on', all worked well. [Where problems could occur] After applying this SRU, the rsi wifi and bluetooth could have come change, like wifi and bluetooth can't work well after resume, but this possibility is very low, I already run '$sudo rtcwake -m freeze -s 10' for 50 times, the wifi and bluetooth still worked well. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1940488/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1895603] Re: alsa/hdmi: the hdmi audio stops working from Ubuntu-4.4.0-155.182
** Changed in: linux (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1895603 Title: alsa/hdmi: the hdmi audio stops working from Ubuntu-4.4.0-155.182 Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Bug description: [Impact] We had a Dell machine, this machine was enabled with ubuntu 4.4 kernel before, but recently the hdmi audio on this machine stopped working with the latest ubuntu 4.4. kernel. The system can't detect its plugging and can't output sound to it anymore. [Fix] This is because we backported a patch from stable updates, and that patch is for v5.2 kernel, if we backported it to 4.4 kernel, we need to do some change, and also we need to backport one more patch from stabe kernel. [Test Case] Connect a monitor to the machine and boot up, after booting up, we could see the hdmi audio is found, and play sound to the hdmi audio, we could hear the sound from monitor. [Regression Risk] It is possible to make the hdmi audio fail to work after applying this patchset, like the hdmi audio can't be detected after plugging a hdmi monitor. But this possibility is very low, we tested the patchset on many dell and lenovo machines, all worked well. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1895603/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1901971] Re: alsa/hda: mic can't be detect if booting with headset plugged on a HP machine
** No longer affects: linux-oem-5.6 (Ubuntu) ** Changed in: hwe-next Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1901971 Title: alsa/hda: mic can't be detect if booting with headset plugged on a HP machine Status in HWE Next: Fix Released Status in linux-oem-5.6 source package in Focal: Fix Released Bug description: Since this patch is cced to stable kernel, I only send this patch to oem-5.6 kernel, other ubuntu kernels will merge this patch with stable update. [Impact] On a HP machine, if we plug a headset before booting, after booting to the desktop, the mic can't be detected. [Fix] Realtek engineer submit a patch to usptream, I backport this patch to ubuntu oem kernel. [Test] Plug a headset, then power on the machine, after entering the gnome, check the mic, it is detected, and use mic to record, it could record the sound. [Regression Potential] I could make the sound on that HP machine not work, but this possibility is very low and this regression possibility is limited to this HP machine since this patch use pin definition to apply the quirk. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1901971/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1940504] Re: Support Alder Lake P graphics
** No longer affects: linux-oem-5.14 (Ubuntu)
** Changed in: linux-firmware (Ubuntu)
Status: Invalid => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.14 in Ubuntu.
https://bugs.launchpad.net/bugs/1940504
Title:
Support Alder Lake P graphics
Status in libdrm package in Ubuntu:
Fix Released
Status in linux-firmware package in Ubuntu:
Fix Released
Status in mesa package in Ubuntu:
Fix Released
Status in libdrm source package in Focal:
Fix Committed
Status in linux-firmware source package in Focal:
In Progress
Status in linux-oem-5.14 source package in Focal:
New
Status in mesa source package in Focal:
Fix Committed
Bug description:
[SRU Justification:linux-firmware]
[Impact]
It shows the firmware is missing, and runtime power management has been
disabled:
i915 :00:02.0: [drm] Failed to load DMC firmware
i915/adlp_dmc_ver2_10.bin. Disabling runtime power management.
[Fix]
Upstream commit 3d32f216 ("i915: Add ADL-P DMC Support").
[Test Case]
Verified on Intel ADL-M/ADL-P RVPs.
[Where problems could occur]
It's a new firmware for new GPU, not possible to introduce
regressions.
[Other Info]
Impish has this already. And while ADL-P/M support begins since v5.14,
only focal (for oem-5.14) is being nominated.
=
[SRU Justification:mesa,libdrm]
NOTE: this is for focal only, hirsute/impish do not and will not have
kernel support for this.
[Impact]
ADL-P machines need to use the native driver.
[Fix]
Backport support from upstream.
libdrm: a single patch from 2.4.107
mesa: three commits to add pci-id's and a workaround
kernel: needs drm sync from 5.14 (bug 1940085) plus additional backports
[Test case]
Boot a machine and check that it's using the native driver and that the usual
workloads are fine.
[Where things could go wrong]
For older gpu's there's little to go wrong, since the commits are for ADL-P
only.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1940504/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1942784] Re: makedumpfile not properly working on focal with 5.11 kernel
** Changed in: makedumpfile (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1942784 Title: makedumpfile not properly working on focal with 5.11 kernel Status in makedumpfile package in Ubuntu: Fix Released Status in makedumpfile source package in Focal: In Progress Status in makedumpfile source package in Hirsute: In Progress Bug description: [IMPACT] When running Focal with the hwe 5.11 kernel makedumpfile is not working as it should. Instead of compressing the dump makedumpfile falls back to cp. This can create problems on systems with very large RAM and result into exhausting all storage on the host. This can be resolved with upstream commit 54aec3878b3f([PATCH] make use of 'uts_namespace.name' offset in VMCOREINFO). In addition the dmesg. is not created. This can be resolved with the following two commits : - commit c617ec633392([PATCH 1/2] printk: add support for lockless ringbuffer) - commit 44b073b7ec46([PATCH 2/2] printk: use committed/finalized state values) [TEST CASE] For testing a machine running focal with the 5.11 kernel is required. Then trigger a crash. On the console we can see that makedumpfile fails and `falls back to cp`. In /var/crash we can see that no dmesg file is created and instead of the dump file the uncompressed vmcoreinfo is created. [WHERE PROBLEMS COULD OCCUR] The 3 commits pulled into focal make makedumpfile compatible with the 5.11 kernel. Any regression potential would involve the crash dump not being created after a crash in case kdump is configured. [OTHER] Only Focal with 5.11 kernel is affected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1942784/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1943160] Re: [SRU] It will take about 90+ seconds to open the 'Nvidia settings' app when 'Power Saving mode' running.
** Changed in: nvidia-settings (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-settings in Ubuntu.
https://bugs.launchpad.net/bugs/1943160
Title:
[SRU] It will take about 90+ seconds to open the 'Nvidia settings' app
when 'Power Saving mode' running.
Status in OEM Priority Project:
In Progress
Status in nvidia-settings package in Ubuntu:
In Progress
Bug description:
[Impact]
On some I+N configs, It will take about 90+ seconds to open the 'Nvidia
settings' window when 'Power Saving mode' running.
[Fix]
do not read config file if Nvidia driver did not loaded:
change nvidia-settings/src/nvidia-settings.c
if (!op->no_load) {
ret = nv_read_config_file(op, op->config, op->ctrl_display,
p, &conf, &systems);
to
if (!op->no_load && systems.n != 0) {
ret = nv_read_config_file(op, op->config, op->ctrl_display,
p, &conf, &systems);
[Test]
1. Install Ubuntu image.
2. Boot and login the system.
3. Open 'Nvidia Settings' app
4. Select the prime is 'Power saving' mode
5. Reboot system and login
6. Open 'Nvidia Settings' app
7. Verify the result
[Where problems will occur]
the "systems.n" gets from
NvCtrlConnectToSystem(op->ctrl_display, &systems);
If there is a possibility that systems.n is zero and we still need to read
nvidia config file, then it will be a problem. I tried and cannot find a
situation like that.
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1943160/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1845048] Re: Improve sysctl handling on kdump-tools
** No longer affects: makedumpfile (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. Matching subscriptions: Maintainer https://bugs.launchpad.net/bugs/1845048 Title: Improve sysctl handling on kdump-tools Status in kdump-tools package in Ubuntu: Fix Released Status in makedumpfile source package in Xenial: Opinion Status in makedumpfile source package in Bionic: In Progress Status in makedumpfile source package in Eoan: Won't Fix Status in makedumpfile source package in Focal: In Progress Status in makedumpfile source package in Groovy: Fix Released Status in kdump-tools package in Debian: New Bug description: [impact] Documentation, and past behavior, for kdump-tools was that the KDUMP_SYSCTL variable in the /etc/default/kdump-tools file would be applied to the system kernel params at kdump 'load'. However this is no longer true, and those params are no longer applied to the system's kernel param settings. [test case] install linux-crashdump (and kdump-tools). Edit the /etc/default/kdump-tools file to set the KDUMP_SYSCTL param to something other than default, e.g.: KDUMP_SYSCTL="kernel.panic_on_oops=1 kernel.panic_on_warn=1" reboot, or unload/reload kdump, to pick up the changes to the file. Check if the panic_on_warn param is set: $ cat /proc/sys/kernel/panic_on_warn 0 the problem does not seem to be with sysctl, as manually calling it does work: $ KDUMP_SYSCTL="kernel.panic_on_oops=1 kernel.panic_on_warn=1" $ cat /proc/sys/kernel/panic_on_warn 0 $ sudo sysctl -w $KDUMP_SYSCTL kernel.panic_on_oops = 1 kernel.panic_on_warn = 1 $ cat /proc/sys/kernel/panic_on_warn 1 [regression potential] TBD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kdump-tools/+bug/1845048/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1932163] Re: evdi/1.7.0+dfsg-1ubuntu1~20.04.3 ADT test failure with linux-hwe-5.11/5.11.0-20.21~20.04.1
** No longer affects: linux-hwe-5.11 (Ubuntu) ** No longer affects: linux-hwe-5.11 (Ubuntu Focal) ** No longer affects: linux-hwe-5.11 (Ubuntu Hirsute) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1932163 Title: evdi/1.7.0+dfsg-1ubuntu1~20.04.3 ADT test failure with linux- hwe-5.11/5.11.0-20.21~20.04.1 Status in evdi package in Ubuntu: Fix Released Status in evdi source package in Focal: Confirmed Status in evdi source package in Hirsute: Confirmed Bug description: [Impact] focal users running latest hwe kernel, version 5.11, won't be able to use evdi-dkms. [Test case] Built evdi dkms and loaded the evdi module on 5.4, 5.8 and 5.11 kernels. [Potential regression] DisplayLink devices will stop working. -- This is a scripted bug report about ADT failures while running evdi tests for linux-hwe-5.11/5.11.0-20.21~20.04.1 on focal. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/e/evdi/20210611_210228_7f0da@/log.gz arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/arm64/e/evdi/20210612_122245_bd52e@/log.gz ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/ppc64el/e/evdi/20210611_210028_038f3@/log.gz s390x: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/s390x/e/evdi/20210611_205902_3dc65@/log.gz [Other] NB! dkms ftbfs fixes must be built in security, such that after SRU process in -proposed & -updates it can be copied into -security pocket too. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evdi/+bug/1932163/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1931677] Re: [SRU][F/G][linux-firmware] add realtek 8852a wifi fimware
Ubuntu Hirsute doesn't have the patch rtw89: 8852a: update fw to v0.13.8.0 so that should be backported there to avoid losing functionality on upgrade from Groovy to Hirsute. https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux- firmware.git/commit/?id=2f4f0f826eed328675e8a84b1d80e41a25e94ec4 ** Also affects: linux-firmware (Ubuntu Hirsute) Importance: Undecided Status: New ** Changed in: linux-firmware (Ubuntu Hirsute) Status: New => Triaged -- 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/1931677 Title: [SRU][F/G][linux-firmware] add realtek 8852a wifi fimware Status in HWE Next: 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 Groovy: Fix Committed Status in linux-firmware source package in Hirsute: Triaged Bug description: [Impact] Realtek 8852A wifi can not work without proper firmware. [Fix] Add realtek 8852a wifi firmware for driver. Kernel driver will be in another SRU. [Test] Verified on hardware with wifi ap, connect with 2.4G/5G, all good. [Where problems could occur] It should be low risk for adding fw for specfic hardware chip. Hirsute already got it, only SRU fw for F/G. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1931677/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1931677] Re: [SRU][F/G][linux-firmware] add realtek 8852a wifi fimware
** Changed in: linux-firmware (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1931677 Title: [SRU][F/G][linux-firmware] add realtek 8852a wifi fimware Status in HWE Next: 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 Groovy: Fix Committed Status in linux-firmware source package in Hirsute: New Bug description: [Impact] Realtek 8852A wifi can not work without proper firmware. [Fix] Add realtek 8852a wifi firmware for driver. Kernel driver will be in another SRU. [Test] Verified on hardware with wifi ap, connect with 2.4G/5G, all good. [Where problems could occur] It should be low risk for adding fw for specfic hardware chip. Hirsute already got it, only SRU fw for F/G. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1931677/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1929147] Re: fix system hang with 5.10 kernel + RX540 on RKL platform
** Changed in: linux-firmware (Ubuntu) Importance: Undecided => High ** Changed in: linux-firmware (Ubuntu Focal) Importance: Undecided => High ** Changed in: linux-firmware (Ubuntu Hirsute) Importance: Undecided => High -- 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/1929147 Title: fix system hang with 5.10 kernel + RX540 on RKL platform Status in HWE Next: 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 Hirsute: Fix Committed Bug description: [Impact] On RKL platform with AMD RX540, system would hang during boot-up. [Fix] AMD introduce a brand new firmware, polaris 12 MC firmware. This fix the issue and the system wouldn't hang during boot-up with AMD RX540. [Test] Verified on RKL platform and AMD RX540 System would boot-up and login to desktop successfully. [Where problems could occur] This's a brand new firmware to support Polaris-series, it may introduce new issues. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1929147/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926236] Re: Fix The sound has noise while audio volume is maximum
linux-firmware (1.198) impish; urgency=medium * Rebase against git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git f8462923ed8fc874f770b8c6dfad49d39b381f14 - qcom: update a650 firmware files - qcom: sm8250: update remoteproc firmware - brcm: Add nvram for the Predia Basic tablet - brcm: Add nvram for the Chuwi Hi8 (CWI509) tablet - rtl_bt: Add rtl8723bs_config-OBDA0623.bin symlink - amdgpu: add arcturus firmware - nfp: update Agilio SmartNIC flower firmware to rev AOTC-2.14.A.6 - WHENCE: link to similar config file for rtl8821a support - QCA: Update Bluetooth firmware for QCA6174 - amdgpu: update navi10 SMC firmware - amdgpu: update navi14 smc firmware - linux-firmware: Update firmware file for Intel Bluetooth AX201 - brcm: Link CM4's WiFi firmware with DMI machine name. - Mellanox: Add new mlxsw_spectrum firmware xx.2008.2438 - cxgb4: Update firmware to revision 1.25.4.0 - rtl_nic: add new firmware for RTL8153 and RTL8156 series - amdgpu: update raven firmware from 21.10 - amdgpu: update raven2 firmware from 21.10 - amdgpu: update navi10 firmware from 21.10 - amdgpu: update renoir firmware from 21.10 - amdgpu: update vega10 firmware from 21.10 - amdgpu: update navi12 firmware from 21.10 - amdgpu: update vega12 firmware from 21.10 - amdgpu: update green sardine firmware from 21.10 - amdgpu: update navi14 firmware from 21.10 - amdgpu: update picasso firmware from 21.10 - amdgpu: update vega20 firmware from 21.10 - amdgpu: update sienna cichlid firmware from 21.10 - amdgpu: update navy flounder firmware from 21.10 - amdgpu: update arcturus firmware from 21.10 - brcm: add missing symlink for Pi Zero W NVRAM file - rtw88: 8822c: Update normal firmware to v9.9.9 - mrvl: prestera: Add Marvell Prestera Switchdev firmware 3.0 version - qcom: update venus firmware files for v5.4 - linux-firmware: Update firmware file for Intel Bluetooth 8265 - linux-firmware: Intel BT 7265: Fix Security Issues - linux-firmware: Update firmware file for Intel Bluetooth AX201 - linux-firmware: Update firmware file for Intel Bluetooth AX200 - linux-firmware: Update firmware file for Intel Bluetooth 9260 - linux-firmware: Update firmware file for Intel Bluetooth 9560 - linux-firmware: Update firmware file for Intel Bluetooth AX210 - rtw89: 8852a: update fw to v0.13.8.0 - qcom: Add venus firmware files for VPU-2.0 - rtl_bt: Update RTL8852A BT USB firmware to 0xD9A8_7893 - rtw89: 8852a: update fw to v0.13.8.0 - brcm: Add a link to enable khadas VIM2's WiFi - qcom: add gpu firmwares for sc7280 - firmware: nvidia: Add VIC firmware for Tegra194 - amdgpu: add new polaris 12 MC firmware (LP: #1929147) - i915: Add ADL-P DMC Support - linux-firmware: update firmware for mhdp8546 - nvidia: Update Tegra210 XUSB firmware to v50.26 - nvidia: Update Tegra186 XUSB firmware to v55.18 - nvidia: Update Tegra194 XUSB firmware to v60.09 - iwlwifi: add new FWs from core60-51 release - iwlwifi: update 9000-family firmwares to core60-51 - iwlwifi: update 8000 family firmwares - rtw88: 8822c: Update normal firmware to v9.9.10 - nvidia: fix symlinks for tu104/tu106 acr unload firmware -- Seth Forshee Tue, 25 May 2021 08:35:16 -0500 ** Changed in: linux-firmware (Ubuntu) Status: New => Fix Released ** Changed in: linux-firmware (Ubuntu) Importance: Undecided => Medium ** Changed in: linux-firmware (Ubuntu Focal) Importance: Undecided => Medium -- 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/1926236 Title: Fix The sound has noise while audio volume is maximum 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: [Impact] The sound has noise while turning the audio volume to maximum [Fix] For VEGA & Polaris, need two patches(landed on mainline kernel) to fix and a modprobe 1.(50ceb1fe7a) drm/amd/pm: bug fix for pcie dpm, has landed on oem kernel. 2.(9d03730ecb) drm/amd/pm: workaround for audio noise issue, has landed on oem kernel 3. #modprobe amdgpu ppfeaturemask=0xfff7bffb. For Navi_1x, need smc firmware to fix. 1. (4fe6e53b96 linux-firmware) amdgpu: update navi10 SMC firmware 1. (8ab7abaf63 linux-firmware) amdgpu: update navi14 SMC firmware [Test] Verified on RKL platform A. with wx3200(Polaris series) and the following configuration 1. With these two patch, 1.1. (50ceb1fe7a) drm/amd/pm: bug fix for pcie dpm, has landed on oem kernel. 1.2. (9d03730ecb) drm/amd/pm: workaround fo
[Kernel-packages] [Bug 1890641] Re: Possible missing firmware /lib/firmware/rtl_nic/rtl8125a-3.fw for module r8169
** Changed in: linux-firmware (Ubuntu)
Status: Invalid => Fix Released
** Changed in: linux-firmware (Ubuntu)
Importance: Undecided => High
--
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/1890641
Title:
Possible missing firmware /lib/firmware/rtl_nic/rtl8125a-3.fw for
module r8169
Status in linux-firmware package in Ubuntu:
Fix Released
Status in linux-firmware source package in Bionic:
Fix Released
Bug description:
[SRU Justification]
[Impact]
Missing firmware for Realtek RTL8153 Based USB Ethernet Adapters,
which is supported by linux-generic-hwe-18.04 kernel (currently v5.4).
[Fix]
Two upstream commit necessary:
* commit b27d12383e7a ("rtl_nic: add firmware files for RTL8153")
* commit 6f89735800fe ("rtl_nic: update firmware for RTL8153A")
[Test Case]
Without firmware, drive probe would fail with:
$ dmesg | grep firmware | grep rtl8153
r8152 2-4.1:1.0: firmware: failed to load rtl_nic/rtl8153a-2.fw (-2)
r8152 2-4.1:1.0: Direct firmware load for rtl_nic/rtl8153a-2.fw failed with
error -2
r8152 2-4.1:1.0: unable to load firmware patch rtl_nic/rtl8153a-2.fw (-2)
With firmware, it should succeed:
$ dmesg | grep rtl8152
r8152 2-1:1.0: load rtl8153a-3 v2 02/07/20 successfully
r8152 2-1:1.0 eth0: v1.11.11
r8152 2-1:1.0 enp0s20f0u1: renamed from eth0
[Where problems could occur]
While this introduces new firmware blobs and enabled devices supported
by new kernels, it should have little effect on existing systems, but
with new devices up and running, it may still affect power consumptions,
ability to enter deep suspend, etc.
[Other Info]
RTL8153 firmware has been available on Eoan and newer, so only Bionic is
nominated.
== original bug report ==
Possible missing firmware /lib/firmware/rtl_nic/rtl8125a-3.fw for
module r8169
after running sudo apt upgrade in ubuntu 18.04
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubuntu-release-upgrader-core 1:18.04.38
ProcVersionSignature: Ubuntu 5.4.0-42.46~18.04.1-generic 5.4.44
Uname: Linux 5.4.0-42-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.16
Architecture: amd64
CrashDB: ubuntu
CurrentDesktop: ubuntu:GNOME
Date: Thu Aug 6 22:38:31 2020
InstallationDate: Installed on 2019-06-16 (417 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64
(20190210)
PackageArchitecture: all
SourcePackage: ubuntu-release-upgrader
Symptom: release-upgrade
UpgradeStatus: No upgrade log present (probably fresh install)
VarLogDistupgradeAptlog:
Log time: 2020-03-08 22:54:00.439353
Starting pkgProblemResolver with broken count: 0
Starting 2 pkgProblemResolver with broken count: 0
Done
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1890641/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-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] Re: Support MIPI camera through Intel IPU6
** Changed in: linux-firmware (Ubuntu) Status: Invalid => Won't Fix ** Changed in: linux-firmware (Ubuntu Hirsute) Status: Invalid => 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-firmware package in Ubuntu: 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-firmware source package in Hirsute: Won't Fix 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 intel-ipu6-isys0: All sensor registration completed. intel-ipu6-isys intel-ipu6-isys0: stream on ov01a1s 20-0036 This one equips an OV01A1S sensor, and HM11B1 is also supported. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /d
[Kernel-packages] [Bug 1921345] Re: Support MIPI camera through Intel IPU6
** No longer affects: linux-oem-5.10 (Ubuntu) ** No longer affects: linux-oem-5.10 (Ubuntu Hirsute) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1921345 Title: Support MIPI camera through Intel IPU6 Status in HWE Next: New Status in linux-firmware package in Ubuntu: Invalid 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-firmware source package in Hirsute: 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 intel-ipu6-isys0: All sensor registration completed. intel-ipu6-isys intel-ipu6-isys0: stream on ov01a1s 20-0036 This one equips an OV01A1S sensor, and HM11B1 is also supported. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: u 1721 F pulseaudio CasperMD
[Kernel-packages] [Bug 1929255] Re: update-initrd-links creates incorrect symlinks
** Tags removed: regression-update -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-base in Ubuntu. https://bugs.launchpad.net/bugs/1929255 Title: update-initrd-links creates incorrect symlinks Status in linux-base package in Ubuntu: Fix Released Status in linux-base source package in Bionic: Confirmed Status in linux-base source package in Focal: New Status in linux-base source package in Groovy: New Status in linux-base source package in Hirsute: New Status in linux-base source package in Impish: Fix Released Bug description: [Impact] ## Problem description Executing the `/etc/kernel/postinst.d/xx-update-initrd-links` script incorrectly detects symbolic links targets and then creates malformed (hence broken) ones instead: /initrd.img -> initrd.imgboot/vmlinuz-5.3.0-53-generic /initrd.img.old -> initrd.imgboot/vmlinuz-5.3.0-53-generic while it should actually be: /initrd.img -> boot/initrd.img-5.3.0-53-generic /initrd.img.old -> boot/initrd.img-5.3.0-53-generic The problem appeared with the release of the version 4.5ubuntu1.5 of the linux-base package, which made this script executable. [Test Plan] * Install new linux-base and initramfs-tools * create /etc/kernel-img.conf with do_symlinks = yes do_bootloader = no do_initrd = yes link_in_boot = yes * Install one kernel flavour, check that symlinks in /boot have sane targets * Install another kernel, check that symlinks in /boot/ have sane targets * create a selfbuilt kernel and install it by calling installkernel (you can download kernel debs from kernel-ppa, and unpack them to pretend one has self built it). and check that symlinks in /boot have sane targets. * Purge all kernel, and remove symlinks in /boot * Update /etc/kernel-img.conf to do_symlinks = yes do_bootloader = no do_initrd = yes link_in_boot = no * Install one kernel flavour, check that symlinks in / have sane targets * Install another kernel, check that symlinks in / have sane targets * create a selfbuilt kernel and install it by calling installkernel (you can download kernel debs from kernel-ppa, and unpack them to pretend one has self built it) * remove all kernels, purge initramfs-tools, clean up symlinks in / and /boot * repeat all of the above, without having initramfs-tools installed. I.e. install kernels _without_ recommneds. [Where problems could occur] * The rewritten postinst.d script now simply mostly calls linux- update-links like the normal linux-image postinst script does. One has to make sure that .deb installations of kernels happens correctly and that installkernel way of installing kernels happens correctly. Under different kernel-img.conf settings. The previous incarnations of fixing this and related issues did not account for the above cases and codepaths. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-base/+bug/1929255/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1929371] Re: [SRU] there is always a "Rear Microphone - Built-in Audio" option on the input device list even if the microphone is unplugged
** Changed in: alsa-ucm-conf (Ubuntu) Importance: Undecided => Low ** Changed in: pulseaudio (Ubuntu) Importance: Undecided => Low ** Also affects: pulseaudio (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: alsa-ucm-conf (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: pulseaudio (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: alsa-ucm-conf (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: pulseaudio (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: alsa-ucm-conf (Ubuntu Groovy) Importance: Undecided Status: New ** Changed in: alsa-ucm-conf (Ubuntu Focal) Importance: Undecided => Low ** Changed in: alsa-ucm-conf (Ubuntu Groovy) Importance: Undecided => Low ** Changed in: alsa-ucm-conf (Ubuntu Hirsute) Importance: Undecided => Low ** Changed in: pulseaudio (Ubuntu Focal) Importance: Undecided => Low ** Changed in: pulseaudio (Ubuntu Groovy) Importance: Undecided => Low ** Changed in: pulseaudio (Ubuntu Hirsute) Importance: Undecided => Low ** Changed in: alsa-ucm-conf (Ubuntu Hirsute) Status: New => Fix Released ** Changed in: alsa-ucm-conf (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/1929371 Title: [SRU] there is always a "Rear Microphone - Built-in Audio" option on the input device list even if the microphone is unplugged Status in OEM Priority Project: In Progress Status in alsa-ucm-conf package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: Incomplete Status in alsa-ucm-conf source package in Focal: New Status in pulseaudio source package in Focal: New Status in alsa-ucm-conf source package in Groovy: New Status in pulseaudio source package in Groovy: New Status in alsa-ucm-conf source package in Hirsute: Fix Released Status in pulseaudio source package in Hirsute: New Bug description: [Impact] [Fix] [Test] [Where problems could occur] To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1929371/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1862559] Re: ubuntu 19.10: unresponsive/freezes on ThunderX2 if system is idle for ~22min
** No longer affects: linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1862559 Title: ubuntu 19.10: unresponsive/freezes on ThunderX2 if system is idle for ~22min Status in gdm3 package in Ubuntu: Won't Fix Bug description: UBUNTU 19.10 installed on ThunderX2 saber ARM64 machine. If the system left idle for ~22min it becomes unresponsive. The system will not take any inputs like from UART, ping ..etc. The system will completely freeze and we need to hard reset the system. It could be possible the system goes to hibernate state and could not able to come out of the state. Dmesg log when system halts/no response on Saber boards (TX2) Ubuntu 19.10 ubuntu ttyAMA0 ubuntu login: ubuntu Password: Last login: Wed Jan 29 20:08:22 PST 2020 on ttyAMA0 Welcome to Ubuntu 19.10 (GNU/Linux 5.3.0-26-generic aarch64) * Documentation: https://help.ubuntu.com * Management: https://landscape.canonical.com * Support:https://ubuntu.com/advantage ubuntu@ubuntu:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 19.10 Release: 19.10 Codename: eoan [ +0.732512] audit: type=1400 audit(1580358920.412:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="lsb_release" pid=3087 comm="apparmor_parser" [ +0.64] audit: type=1400 audit(1580358920.412:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/ippusbxd" pid=3091 comm="apparmor_parser" [ +0.000168] audit: type=1400 audit(1580358920.412:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="nvidia_modprobe" pid=3086 comm="apparmor_parser" [ +0.05] audit: type=1400 audit(1580358920.412:5): apparmor="STATUS" operation="profile_load" profile="unconfined" name="nvidia_modprobe//kmod" pid=3086 comm="apparmor_parser" [ +0.000546] audit: type=1400 audit(1580358920.412:6): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/bin/man" pid=3085 comm="apparmor_parser" [ +0.06] audit: type=1400 audit(1580358920.412:7): apparmor="STATUS" operation="profile_load" profile="unconfined" name="man_filter" pid=3085 comm="apparmor_parser" [ +0.05] audit: type=1400 audit(1580358920.412:8): apparmor="STATUS" operation="profile_load" profile="unconfined" name="man_groff" pid=3085 comm="apparmor_parser" [ +0.000854] audit: type=1400 audit(1580358920.412:9): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/tcpdump" pid=3089 comm="apparmor_parser" [ +0.002667] audit: type=1400 audit(1580358920.416:10): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/sbin/dhclient" pid=3093 comm="apparmor_parser" [ +0.04] audit: type=1400 audit(1580358920.416:11): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=3093 comm="apparmor_parser" [ +1.382579] igb :92:00.1 enp146s0f1: igb: enp146s0f1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX [ +0.000299] IPv6: ADDRCONF(NETDEV_CHANGE): enp146s0f1: link becomes ready [ +3.131173] mpt3sas_cm0: port enable: SUCCESS [Jan29 20:36] random: crng init done [ +0.04] random: 7 urandom warning(s) missed due to ratelimiting *[Jan29 20:37] rfkill: input handler disabled* *[Jan29 20:57] PM: suspend entry (deep)* To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1862559/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1879214] Re: Package makedumpfile 1:1.6.7-1ubuntu2(arm64) failed to makedumpfile:calculate_plat_config: PAGE SIZE 0x1000 and VA Bits 47 not supported
** Changed in: makedumpfile (Ubuntu Bionic) Importance: Undecided => High -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1879214 Title: Package makedumpfile 1:1.6.7-1ubuntu2(arm64) failed to makedumpfile:calculate_plat_config: PAGE SIZE 0x1000 and VA Bits 47 not supported Status in makedumpfile package in Ubuntu: Fix Released Status in makedumpfile source package in Bionic: Fix Committed Status in makedumpfile source package in Focal: Fix Committed Status in makedumpfile source package in Groovy: Fix Committed Status in makedumpfile source package in Hirsute: Fix Released Status in makedumpfile package in Debian: Fix Released Bug description: [Impact] On arm64 and kernels 5.4+ makedumpfile fails. Upstream patches solve this bug : [PATCH 1/3] Use vmcoreinfo note in /proc/kcore for --mem-usage option https://github.com/makedumpfile/makedumpfile/commit/d8b701796f0491f2ac4b06c7a5b795c29399efab [PATCH 2/3] arm64: Make use of NUMBER(VA_BITS) in vmcoreinfo https://github.com/makedumpfile/makedumpfile/commit/67d0e1d68f28c567a704fd6b9b8fd696ad3df183 [PATCH 3/3] arm64: support flipped VA and 52-bit kernel VA https://github.com/makedumpfile/makedumpfile/commit/a0216b678a95f099a16172cc4a67ad5aa6a89583 [Test Case] OS: Ubuntu 20.04 LTS kernel: 5.4.0-21-generic arch:arm64 Description: When testing kdump on Ubuntu 20.04 LTS (arm64), makedumpfile fails. The test steps are as follows: # echo 1> / proc / sys / kernel / sysrq # echo c> / proc / sysrq-trigger The error logs are as follows: [ 26.599161] kdump-tools[653]: Starting kdump-tools: [ 26.612761] kdump-tools[659]: Starting kdump-tools: [ 26.628565] kdump-tools[659]: * running makedumpfile -c -d 31 /proc/vmcore /var/crash/2020050 [ 26.648621] kdump-tools[676]: * running makedumpfile -c -d 31 /proc/vmcore /var/crash/2020050 [ 26.668445] kdump-tools[676]: calculate_plat_config: PAGE SIZE 0x1000 and VA Bits 47 not supported [ 26.678199] kdump-tools[676]: get_machdep_info_arm64 [ 26.692518] kdump-tools[659]: get_machdep_info_arm64 [ 26.852221] hns3 :7d:00.0: get link status cmd failed -16 [ 94.351303] kdump-tools[659]: * kdump-tools: makedumpfile failed, * kdump-tools: saved vmcore in /var/crash/202005061048 [ 94.435510] kdump-tools[659]: * running makedumpfile --dump-dmesg /proc/vmcore /var/crash/202005061048/dmesg.202005061048 [ 94.457103] kdump-tools[688]: calculate_plat_config: PAGE SIZE 0x1000 and VA Bits 47 not supported [ 94.476228] kdump-tools[688]: get_machdep_info_arm64: Can't determine platform config values [ 94.485912] kdump-tools[688]: makedumpfile Failed. [ 94.500760] kdump-tools[659]: * kdump-tools: makedumpfile --dump-dmesg failed. dmesg content will be unavailable [ 94.520225] kdump-tools[659]: * kdump-tools: failed to save dmesg content in /var/crash/202005061048 [ 94.544205] kdump-tools[691]: Wed, 06 May 2020 10:49:42 -0400 [ 94.564597] kdump-tools[692]: Rebooting. [ 94.678709] reboot: Restarting systemlpc uart init Done [Regression Potential] Patch 1 : [PATCH 1/3] Use vmcoreinfo note in /proc/kcore for --mem-usage option removes get_elf_loads function this function was only used with --mem-usage option , since kernel commit kernel commit 23c85094fe18 (kernel versions >4.19) the information needed is in vmcoreinfo Any regression potential would affect the --mem-usage only Patch 2 : [PATCH 2/3] arm64: Make use of NUMBER(VA_BITS) in vmcoreinfo arm64 only make use of NUMBER(VA_BITS) in vmcoreinfo as the current way of guessing VA_BITS does not work on Linux 5.4 and later. Before this commit VA_BITS would be calculated in get_versiondep_info_arm64, however this way of calculation breaks after 5.4. This commit gets the VA_BITS from vmcoreinfo and as a safeguard it uses the old way of deriving VA_BITS only if reading from vmcoreinfo doesn't work. From the kernel side VA_BITS is in vmcoreinfo since kernel 4.12, F and later use later kernel so not great regression potentional and if any it would only affect arm64. Patch 3 : [PATCH 3/3] arm64: support flipped VA and 52-bit kernel VA arm64 only Linux 5.4 and later kernels for arm64 changed the kernel VA space arrangement and introduced 52-bit kernel VAs by merging branch commit b333b0ba2346. Support 5.9+ kernels with vmcoreinfo entries and 5.4+ kernels with best guessing. This patch makes adjustemnt to properly calculate vabits_actual, max_physmem_bits, page_offset Any regression potential would affect only arm64 and the calculation of the above variables. [Other] For H only the 3 commits are needed and they cherry-pick. For G and F the 3rd commit does not apply and an extra commit is needed : commit da0d25ffa585c9a1adb94562c815daa393b1ee5e [PATCH] arm64: Add suppor
[Kernel-packages] [Bug 1924970] Re: Add soundwire sdca codec support
** Changed in: alsa-ucm-conf (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: alsa-ucm-conf (Ubuntu Hirsute) Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/1924970 Title: Add soundwire sdca codec support Status in OEM Priority Project: New Status in alsa-ucm-conf package in Ubuntu: In Progress Status in alsa-ucm-conf source package in Focal: Fix Committed Status in alsa-ucm-conf source package in Hirsute: Fix Committed Bug description: [Impact] * The output device in sound settings will non-functional. Sound input device will be empty. An upstream commit add supports for SDW sdca codec support. [Test Plan] * Open settings and select Sound column. Testing speaker won't have any sound output. * Try to update files mentioned here https://github.com/alsa-project/alsa-ucm-conf/pull/71/commits/a7f348bb37d2b3254801702299ab2c76833a3c16 https://github.com/alsa-project/alsa-ucm-conf/pull/71/commits/651c2c851bf17a1d76e0a046eb33eccbcf98845f * alsactl init * Open settings and select Sound column and test output device again. Sound devices work properly. [Where problems could occur] * This change adds new hardware support. * The change only adds new hardware support, it will not affect other codec device. [Other Info] * The change has been verified on Dell machine with sdca codec. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1924970/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1924970] Re: Add soundwire sdca codec support
** Changed in: alsa-ucm-conf (Ubuntu) Status: Incomplete => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/1924970 Title: Add soundwire sdca codec support Status in OEM Priority Project: New Status in alsa-ucm-conf package in Ubuntu: In Progress Bug description: [Impact] * The output device in sound settings will non-functional. Sound input device will be empty. An upstream commit add supports for SDW sdca codec support. [Test Plan] * Open settings and select Sound column. Testing speaker won't have any sound output. * Try to update files mentioned here https://github.com/alsa-project/alsa-ucm-conf/pull/71/commits/a7f348bb37d2b3254801702299ab2c76833a3c16 https://github.com/alsa-project/alsa-ucm-conf/pull/71/commits/651c2c851bf17a1d76e0a046eb33eccbcf98845f * alsactl init * Open settings and select Sound column and test output device again. Sound devices work properly. [Where problems could occur] * This change adds new hardware support. * The change only adds new hardware support, it will not affect other codec device. [Other Info] * The change has been verified on Dell machine with sdca codec. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1924970/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1922792] Re: Bluez should notify users when they need to reboot to apply changes on Raspberry Pi
** Also affects: bluez (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=986836 Importance: Unknown Status: Unknown -- 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/1922792 Title: Bluez should notify users when they need to reboot to apply changes on Raspberry Pi Status in bluez package in Ubuntu: In Progress Status in bluez package in Debian: Unknown Bug description: In the case of upgrading or installing bluez for the first time on certain raspberry pi devices, a reboot may be required to apply the changes. We should add a check for this scenario in the postinst script. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1922792/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1921452] Re: [SRU] alsa-lib: conf: USB - add "Cmedia Audio" to USB-Audio.pcm.iec958_device
** Changed in: alsa-lib (Ubuntu Focal) Importance: Undecided => Low ** Changed in: alsa-lib (Ubuntu Groovy) Importance: Undecided => Low ** Changed in: alsa-lib (Ubuntu Hirsute) Importance: Undecided => Low -- 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/1921452 Title: [SRU] alsa-lib: conf: USB - add "Cmedia Audio" to USB- Audio.pcm.iec958_device Status in OEM Priority Project: In Progress Status in alsa-lib package in Ubuntu: In Progress Status in alsa-lib source package in Focal: In Progress Status in alsa-lib source package in Groovy: In Progress Status in alsa-lib source package in Hirsute: In Progress Bug description: [Impact] On Cmedia Audio, unusable SPDIF can be selected as output from PulseAudio. [Fix] Disable IEC958 (SPDIF) through ALSA UCM. [Test] With the UCM applied, `pactl` and audio panel in gnome-control-center no longer have SPDIF option. [Where problems will occur] This fix limits to the Cmedia Audio only, other devices are unaffected. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1921452/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1903048] Re: [SRU] Bluetooth won't activate on the pi 400
** Changed in: bluez (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: bluez (Ubuntu Groovy) Importance: Undecided => Medium -- 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/1903048 Title: [SRU] Bluetooth won't activate on the pi 400 Status in bluez package in Ubuntu: Fix Released Status in bluez source package in Focal: In Progress Status in bluez source package in Groovy: Fix Released Status in bluez source package in Hirsute: Fix Released Bug description: [Impact] Without these patches, Bluetooth is inoperable on the recently released Raspberry Pi 400. [Test Case] * Boot the Ubuntu Desktop for Pi image on a Pi 400. * Start the Settings application and switch to the Bluetooth tab * Verify that Bluetooth is not enabled and attempting to activate it fails * Enable the -proposed repository for the release (groovy) * sudo apt update * sudo apt install bluez * sudo reboot * Start the Settings application and switch to the Bluetooth tab * Verify that Bluetooth is active and that Bluetooth devices (e.g. mice, mobile phones, headphones, etc.) can connect and operate correctly [Regression Potential] Extremely low (on groovy in particular, this has the same version of bluez as hirsute). The only significant risk is to non-Pi platforms or dongles which also use the Broadcom 43xx (or Cypress 305) chips for Bluetooth which might be inadvertently affected by these patches. [Original Description] The new Pi 400 has a slightly different Wifi/BT chip to the Pi4. Whilst wifi works happily, Bluetooth fails to operate. This doesn't appear to be an issue with either the firmware (the latest versions from upstream Raspbian have been tried), or the kernel (a known-good raspi kernel has been tested under Ubuntu), but with Bluez itself. Specifically, tracing the initialization with btmon on Raspbian and Ubuntu, the stack consistently fails when attempting to "Set Default PHY" on the latter. Curiously, under Ubuntu the adapter also appears to lack a MAC address. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1903048/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1905627] Re: Bluetooth stops working on Raspberry Pi 4 with bluez 5.55-0ubuntu1.1
** Changed in: bluez (Ubuntu Groovy) Importance: Undecided => Medium -- 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/1905627 Title: Bluetooth stops working on Raspberry Pi 4 with bluez 5.55-0ubuntu1.1 Status in bluez package in Ubuntu: New Status in bluez source package in Groovy: New Status in bluez source package in Hirsute: New Bug description: Bluetooth stops working after updating to bluez version 5.55-0ubuntu1.1. /usr/bin/btuart returns "bcm43xx_init Initialization timed out". Bluetooth is working again if bluez is reverted to version 5.55-0ubuntu1. I don't have any unusual setup like miniuart-bt. Release: 20.10 bluez: Installed: 5.55-0ubuntu1.1 Candidate: 5.55-0ubuntu1.1 Version table: *** 5.55-0ubuntu1.1 500 500 http://ports.ubuntu.com/ubuntu-ports groovy-updates/main arm64 Packages 100 /var/lib/dpkg/status 5.55-0ubuntu1 500 500 http://ports.ubuntu.com/ubuntu-ports groovy/main arm64 Packages ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: bluez 5.55-0ubuntu1.1 ProcVersionSignature: Ubuntu 5.8.0-1007.10-raspi 5.8.14 Uname: Linux 5.8.0-1007-raspi aarch64 ApportVersion: 2.20.11-0ubuntu50.2 Architecture: arm64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Nov 25 16:09:03 2020 ImageMediaBuild: 20200423.1 InterestingModules: bnep bluetooth Lspci-vt: -[:00]---00.0-[01]00.0 VIA Technologies, Inc. VL805 USB 3.0 Host Controller Lsusb: Bus 002 Device 002: ID 1058:25ee Western Digital Technologies, Inc. My Book 25EE Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub 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/4p, 5000M |__ Port 2: Dev 2, If 0, Class=Mass Storage, Driver=usb-storage, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 480M |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 snd_bcm2835.enable_headphones=1 video=HDMI-A-1:1920x1080M@60 smsc95xx.macaddr=DC:A6:32:B9:18:CC vc_mem.mem_base=0x3eb0 vc_mem.mem_size=0x3ff0 dwc_otg.lpm_enable=0 console=tty1 root=PARTUUID=5f9d0997-1b4e-423b-ad5e-8bce1a7e1ae4 rootfstype=ext4 elevator=deadline rootwait fixrtc SourcePackage: bluez UpgradeStatus: Upgraded to groovy on 2020-10-23 (33 days ago) acpidump: hciconfig: rfkill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1905627/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1908677] Re: Dell Latitude 9510 capture volume is too low
** Also affects: alsa-ucm-conf (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: alsa-ucm-conf (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: alsa-ucm-conf (Ubuntu Focal) Status: New => In Progress ** Changed in: alsa-ucm-conf (Ubuntu Groovy) Status: New => In Progress ** Changed in: alsa-ucm-conf (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: alsa-ucm-conf (Ubuntu Groovy) Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/1908677 Title: Dell Latitude 9510 capture volume is too low Status in OEM Priority Project: New Status in alsa-ucm-conf package in Ubuntu: Fix Released Status in alsa-ucm-conf source package in Focal: In Progress Status in alsa-ucm-conf source package in Groovy: In Progress Bug description: [Impact] * The internal mic default volume is too low A upstream commit correct the init configuration [Test Case] * Using gnome-sound-recoder to record audio without tweak capture volume The volume is very low * Try to update the init.conf mentioned by https://github.com/alsa-project/alsa-ucm-conf/commit/263bd26b1216c933db3d216197a78678d0f8610e $ alsactl init $ amixer cget name='rt715 ADC 07 Capture Volume' numid=14,iface=MIXER,name='rt715 ADC 07 Capture Volume' ; type=INTEGER,access=rw---R--,values=2,min=0,max=63,step=0 : values=58,58 | dBscale-min=-17.25dB,step=0.75dB,mute=0 * Using gnome-sound-recorder to record again The volume is significantly improved [Where problems could occur] * The change only apply to the hardware with rt715 codec. * The change adjust the volume only, but not change other control, the worst case is the change doesn't take effect. [Other Info] * The change has been verified on Latitude 9510. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1908677/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1915051] Re: dkms-autopkgtest: Also select binary packages that depends on dkms for testing
** Tags removed: verification-needed ** Also affects: dkms (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982315 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/1915051 Title: dkms-autopkgtest: Also select binary packages that depends on dkms for testing Status in dkms package in Ubuntu: Fix Released Status in dkms source package in Focal: Fix Released Status in dkms source package in Groovy: Fix Released Status in dkms source package in Hirsute: Fix Released Status in dkms package in Debian: Unknown Bug description: [Impact] The current version of dkms-autopkgtest in 20.04 and later only selects binary packages with names ending with "-dkms" for its automatic DKMS test. With that packages suchs bcml-kernel-source and nvidia drivers are not being tested automatically by autopkgtest. [Test Case] Run autopkgtest in Focal for bcmwl-kernel-source (6.30.223.271+bdcom- 0ubuntu5) and the 5.8 kernel and even with this version of the driver failing to build with the 5.8 kernel, the test succeeds. The expected behavior, is that that dkms-autopkgtest should fail in this case. [Where problems could occur] The main issue that we can have here is selecting additional packages for the DKMS test that are not DKMS packages. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1915051/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1893837] Re: [RFE] Enable makedumpfile invocation from initramfs
** Package changed: makedumpfile (Ubuntu) => kdump-tools (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1893837 Title: [RFE] Enable makedumpfile invocation from initramfs Status in kdump-tools package in Ubuntu: Confirmed Bug description: [Request] To be able to call makedumpfile at the from the initramfs, instead of doing so after rootfs is active/mounted. [Justification] Systems with too much memory will demand higher amounts of memory for the crashkernel parameter, as well as having less systemd units up and running before makedumpfile kicks in. The idea is to use as little memory as possible in the kernel dump generation. [Workaround] Tailoring the postinst.d/kdump-tools hooks can have makedumpfile be called earler. Although feasible, that's too much of a "hack", and this could ideally be embedded in kdump-tools as an option. [Regressions] TBE. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kdump-tools/+bug/1893837/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1687791] Re: Install of kdump-tools fails
*** This bug is a duplicate of bug 1661629 *** https://bugs.launchpad.net/bugs/1661629 ** Also affects: initramfs-tools (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: makedumpfile (Ubuntu Bionic) Importance: Undecided Status: New ** This bug has been marked a duplicate of bug 1661629 upgrade of kernel fails with mkinitramfs: failed to determine device for / -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1687791 Title: Install of kdump-tools fails Status in initramfs-tools package in Ubuntu: New Status in makedumpfile package in Ubuntu: Confirmed Status in initramfs-tools source package in Bionic: New Status in makedumpfile source package in Bionic: New Bug description: When installing Ubuntu xenial via netimage, installation fails because of an error, when configuring the kdump-tools. /var/log/syslog says: ... May 2 22:15:17 in-target: Setting up grub2 (2.02~beta2-36ubuntu3.9) ...^M May 2 22:15:17 in-target: Setting up lxc-common (2.0.7-0ubuntu1~16.04.2) ...^M May 2 22:15:17 in-target: Running in chroot, ignoring request.^M May 2 22:15:17 in-target: invoke-rc.d: policy-rc.d denied execution of reload.^M May 2 22:15:17 in-target: Setting up grub-gfxpayload-lists (0.7) ...^M May 2 22:15:17 in-target: Processing triggers for libc-bin (2.23-0ubuntu7) ...^M May 2 22:15:17 in-target: Processing triggers for systemd (229-4ubuntu17) ...^M May 2 22:15:17 in-target: Processing triggers for ureadahead (0.100.0-19) ...^M May 2 22:15:17 in-target: Processing triggers for dbus (1.10.6-1ubuntu3.3) ...^M May 2 22:15:17 in-target: Errors were encountered while processing:^M May 2 22:15:17 in-target: kdump-tools^M May 2 22:15:17 in-target: linux-crashdump^M May 2 22:15:18 in-target: E: Sub-process /usr/bin/dpkg returned an error code (1) May 2 22:15:18 in-target: Setting up kdump-tools (1:1.5.9-5ubuntu0.4) ... May 2 22:15:18 in-target: dpkg: error processing package kdump-tools (--configure): May 2 22:15:18 in-target: subprocess installed post-installation script returned error exit status 1 May 2 22:15:18 in-target: dpkg: dependency problems prevent configuration of linux-crashdump: May 2 22:15:18 in-target: linux-crashdump depends on kdump-tools; however: May 2 22:15:18 in-target: Package kdump-tools is not configured yet. May 2 22:15:18 in-target: May 2 22:15:18 in-target: dpkg: error processing package linux-crashdump (--configure): May 2 22:15:18 in-target: dependency problems - leaving unconfigured May 2 22:15:18 in-target: Errors were encountered while processing: May 2 22:15:18 in-target: kdump-tools May 2 22:15:18 in-target: linux-crashdump May 2 22:15:18 main-menu[616]: WARNING **: Configuring 'pkgsel' failed with error code 100 May 2 22:15:18 main-menu[616]: WARNING **: Menu item 'pkgsel' failed. After this the 'Select and install software' dialog pops up and says, that 'Installation step failed'. If one presses '', one gets bombed back into the 'Ubuntu installer main menu'. Now you get into a loop, when choosing the 'Select and install software' item from the menu. Installer image is 'Linux foo 4.4.0-62-generic #83-Ubuntu SMP Wed Jan 18 14:10:15 UTC 2017 x86_64 GNU/Linux'. The only workaround found so far is: cp -p /target/var/lib/dpkg/info/kdump-tools.postinst \ /target/var/lib/dpkg/info/kdump-tools.postinst.suck printf '#!/bin/sh\nexit 0\n' \ >/target/var/lib/dpkg/info/kdump-tools.postinst To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1687791/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1845048] Re: Improve sysctl handling on kdump-tools
** Package changed: makedumpfile (Debian) => kdump-tools (Debian) ** Also affects: kdump-tools (Ubuntu) Importance: Undecided Status: New ** No longer affects: kdump-tools (Ubuntu Xenial) ** No longer affects: kdump-tools (Ubuntu Bionic) ** No longer affects: kdump-tools (Ubuntu Eoan) ** No longer affects: kdump-tools (Ubuntu Focal) ** No longer affects: kdump-tools (Ubuntu Groovy) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1845048 Title: Improve sysctl handling on kdump-tools Status in kdump-tools package in Ubuntu: New Status in makedumpfile package in Ubuntu: In Progress Status in makedumpfile source package in Xenial: Opinion Status in makedumpfile source package in Bionic: In Progress Status in makedumpfile source package in Eoan: Won't Fix Status in makedumpfile source package in Focal: In Progress Status in makedumpfile source package in Groovy: In Progress Status in kdump-tools package in Debian: New Bug description: [impact] Documentation, and past behavior, for kdump-tools was that the KDUMP_SYSCTL variable in the /etc/default/kdump-tools file would be applied to the system kernel params at kdump 'load'. However this is no longer true, and those params are no longer applied to the system's kernel param settings. [test case] install linux-crashdump (and kdump-tools). Edit the /etc/default/kdump-tools file to set the KDUMP_SYSCTL param to something other than default, e.g.: KDUMP_SYSCTL="kernel.panic_on_oops=1 kernel.panic_on_warn=1" reboot, or unload/reload kdump, to pick up the changes to the file. Check if the panic_on_warn param is set: $ cat /proc/sys/kernel/panic_on_warn 0 the problem does not seem to be with sysctl, as manually calling it does work: $ KDUMP_SYSCTL="kernel.panic_on_oops=1 kernel.panic_on_warn=1" $ cat /proc/sys/kernel/panic_on_warn 0 $ sudo sysctl -w $KDUMP_SYSCTL kernel.panic_on_oops = 1 kernel.panic_on_warn = 1 $ cat /proc/sys/kernel/panic_on_warn 1 [regression potential] TBD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kdump-tools/+bug/1845048/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1879214] Re: Package makedumpfile 1:1.6.7-1ubuntu2(arm64) failed to makedumpfile:calculate_plat_config: PAGE SIZE 0x1000 and VA Bits 47 not supported
** Changed in: makedumpfile (Ubuntu Focal) Importance: Undecided => High ** Changed in: makedumpfile (Ubuntu Groovy) Importance: Undecided => High ** Changed in: makedumpfile (Ubuntu Hirsute) Importance: Undecided => High -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1879214 Title: Package makedumpfile 1:1.6.7-1ubuntu2(arm64) failed to makedumpfile:calculate_plat_config: PAGE SIZE 0x1000 and VA Bits 47 not supported Status in makedumpfile package in Ubuntu: Confirmed Status in makedumpfile source package in Focal: Confirmed Status in makedumpfile source package in Groovy: Confirmed Status in makedumpfile source package in Hirsute: Confirmed Bug description: [Impact] On arm64 and kernels 5.4+ makedumpfile fails. Upstream patches solve this bug : [PATCH 1/3] Use vmcoreinfo note in /proc/kcore for --mem-usage option https://github.com/makedumpfile/makedumpfile/commit/d8b701796f0491f2ac4b06c7a5b795c29399efab [PATCH 2/3] arm64: Make use of NUMBER(VA_BITS) in vmcoreinfo https://github.com/makedumpfile/makedumpfile/commit/67d0e1d68f28c567a704fd6b9b8fd696ad3df183 [PATCH 3/3] arm64: support flipped VA and 52-bit kernel VA https://github.com/makedumpfile/makedumpfile/commit/a0216b678a95f099a16172cc4a67ad5aa6a89583 [Test Case] OS: Ubuntu 20.04 LTS kernel: 5.4.0-21-generic arch:arm64 Description: When testing kdump on Ubuntu 20.04 LTS (arm64), makedumpfile fails. The test steps are as follows: # echo 1> / proc / sys / kernel / sysrq # echo c> / proc / sysrq-trigger The error logs are as follows: [ 26.599161] kdump-tools[653]: Starting kdump-tools: [ 26.612761] kdump-tools[659]: Starting kdump-tools: [ 26.628565] kdump-tools[659]: * running makedumpfile -c -d 31 /proc/vmcore /var/crash/2020050 [ 26.648621] kdump-tools[676]: * running makedumpfile -c -d 31 /proc/vmcore /var/crash/2020050 [ 26.668445] kdump-tools[676]: calculate_plat_config: PAGE SIZE 0x1000 and VA Bits 47 not supported [ 26.678199] kdump-tools[676]: get_machdep_info_arm64 [ 26.692518] kdump-tools[659]: get_machdep_info_arm64 [ 26.852221] hns3 :7d:00.0: get link status cmd failed -16 [ 94.351303] kdump-tools[659]: * kdump-tools: makedumpfile failed, * kdump-tools: saved vmcore in /var/crash/202005061048 [ 94.435510] kdump-tools[659]: * running makedumpfile --dump-dmesg /proc/vmcore /var/crash/202005061048/dmesg.202005061048 [ 94.457103] kdump-tools[688]: calculate_plat_config: PAGE SIZE 0x1000 and VA Bits 47 not supported [ 94.476228] kdump-tools[688]: get_machdep_info_arm64: Can't determine platform config values [ 94.485912] kdump-tools[688]: makedumpfile Failed. [ 94.500760] kdump-tools[659]: * kdump-tools: makedumpfile --dump-dmesg failed. dmesg content will be unavailable [ 94.520225] kdump-tools[659]: * kdump-tools: failed to save dmesg content in /var/crash/202005061048 [ 94.544205] kdump-tools[691]: Wed, 06 May 2020 10:49:42 -0400 [ 94.564597] kdump-tools[692]: Rebooting. [ 94.678709] reboot: Restarting systemlpc uart init Done [Regression Potential] Patch 1 : [PATCH 1/3] Use vmcoreinfo note in /proc/kcore for --mem-usage option removes get_elf_loads function this function was only used with --mem-usage option , since kernel commit kernel commit 23c85094fe18 (kernel versions >4.19) the information needed is in vmcoreinfo Any regression potential would affect the --mem-usage only Patch 2 : [PATCH 2/3] arm64: Make use of NUMBER(VA_BITS) in vmcoreinfo arm64 only make use of NUMBER(VA_BITS) in vmcoreinfo as the current way of guessing VA_BITS does not work on Linux 5.4 and later. Before this commit VA_BITS would be calculated in get_versiondep_info_arm64, however this way of calculation breaks after 5.4. This commit gets the VA_BITS from vmcoreinfo and as a safeguard it uses the old way of deriving VA_BITS only if reading from vmcoreinfo doesn't work. From the kernel side VA_BITS is in vmcoreinfo since kernel 4.12, F and later use later kernel so not great regression potentional and if any it would only affect arm64. Patch 3 : [PATCH 3/3] arm64: support flipped VA and 52-bit kernel VA arm64 only Linux 5.4 and later kernels for arm64 changed the kernel VA space arrangement and introduced 52-bit kernel VAs by merging branch commit b333b0ba2346. Support 5.9+ kernels with vmcoreinfo entries and 5.4+ kernels with best guessing. This patch makes adjustemnt to properly calculate vabits_actual, max_physmem_bits, page_offset Any regression potential would affect only arm64 and the calculation of the above variables. [Other] For H only the 3 commits are needed and they cherry-pick. For G and F the 3rd commit does not apply and an extra commit is needed : commit da0d25ffa585c9a1adb94562c815daa393b1ee5e [PATC
[Kernel-packages] [Bug 1877533] Re: [20.10 FEAT] Increase the crashkernel setting if the root volume is luks2-encrypted
** No longer affects: linux (Ubuntu) ** No longer affects: linux (Ubuntu Focal) ** No longer affects: linux (Ubuntu Groovy) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1877533 Title: [20.10 FEAT] Increase the crashkernel setting if the root volume is luks2-encrypted Status in Ubuntu on IBM z Systems: In Progress Status in kdump-tools package in Ubuntu: New Status in makedumpfile package in Ubuntu: Invalid Status in kdump-tools source package in Focal: Invalid Status in makedumpfile source package in Focal: In Progress Status in kdump-tools source package in Groovy: Invalid Status in makedumpfile source package in Groovy: In Progress Bug description: Description: In case the volume containing the root filesystem is encrypted using LUKS2 the memory used while unlocking the volume may exceed the size allocated to the kdump kernel. This will lead to a failure while processing kdump and the dump file will not be stored. Unfortunately, this condition may not be detected by a client before a problem occurs. The request is to have the kdump package installation script check for LUKS2 encryption (more precisely for Argon2i PBKDF, which is the root cause of the high memory usage). If the condition is met, the installation procedure should increase the crashkernel parameter to a higher value (>=512M)or issue a warning, if the system memory is insufficient to reserve enough crashkernel memory. Business Case: Pervasive Encryption and Secure Execution require encryption of the filesystems in order to keep customer data secure at all times. With the increasing usage of these technologies, the number of kdump will rise too, typically at inconvenient times, when the kdump is triggered due to a real customer issue. With the suggested change, the number of customer complaints and effort to handle them will be reduced. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1877533/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1916570] Re: BlueZ 5.56 release
** Tags added: upgrade-software-version -- 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/1916570 Title: BlueZ 5.56 release Status in bluez package in Ubuntu: In Progress Bug description: BlueZ 5.56 is now available: https://mirrors.edge.kernel.org/pub/linux/bluetooth/ ver 5.56: Fix issue with setting AVDTP disconnect timer. Fix issue with AVDTP not sending GetCapabilities. Fix issue with AVDTP connecting using streaming mode. Fix issue with handling A2DP and remote SEP disappearing. Fix issue with handling session of A2DP channels. Fix issue with GATT and handling device removal. Fix issue with GATT not accepting multiple requests. Fix issue with HID report value callback registration. Add support for new advertising management command. Add support for battery D-Bus interface. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1916570/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1870189] Re: initramfs does not get loaded
** No longer affects: grub2 (Ubuntu Focal)
** No longer affects: grub2 (Ubuntu)
** No longer affects: linux-azure (Ubuntu Focal)
** No longer affects: linux-azure (Ubuntu)
--
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/1870189
Title:
initramfs does not get loaded
Status in cloud-images:
Confirmed
Status in livecd-rootfs package in Ubuntu:
Triaged
Status in livecd-rootfs source package in Focal:
Confirmed
Bug description:
[Impact]
Generic cloud images will boot without initramfs, fail, and then fall back,
resulting in a double boot performance hit
[Test Case]
Load up cloud images from
http://cloud-images.ubuntu.com/releases/focal/release/.
For example, using http://cloud-
images.ubuntu.com/releases/focal/release/ubuntu-20.04-server-cloudimg-
amd64.img :
qemu-system-x86_64-cpu host -machine type=q35,accel=kvm -m 2048
-nographic -snapshot -netdev
id=net00,type=user,hostfwd=tcp::-:22 -device virtio-net-
pci,netdev=net00 -drive if=virtio,format=qcow2,file=ubuntu-20.04
-server-cloudimg-amd64.img -drive if=virtio,format=raw,file=seed.img
Note: seed.img is created using cloud-localds and a cloud-init file
containing ssh keys.
Observe the double boot.
On a fixed system, there should only be one boot, and
/boot/grub/grubenv should show initrdless_boot_fallback_triggered=0.
[Regression Potential]
Cloud images (both generic and cloud-specific) images perform a double boot.
To mitigate the regression potential, testing will occur for all cloud-specific
kernels as well as all generic cloud images.
[Original Description]
A Gen-1 Ubuntu 19.10 VM on Azure was created and upgraded to Ubuntu 20.04 by
“do-release-upgrade –d”.
Then the latest Ubuntu v5.6 kernel was installed from
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.6/. As soon as a
reboot was performed, a panic with the v5.6 kernel occured because the
rootfs can not be found.
It turns out by default, initramfs does not get loaded:
/boot/grub/grub.cfg:
menuentry 'Ubuntu' --class ubuntu --class gnu-linux --class gnu --class os
$menuentry_id_option 'gnulinux-simple-3d2737e8-
b95a-42bf-bac1-bb6fb4cda87f' {
…
if [ "${initrdfail}" = 1 ]; then
linux /boot/vmlinuz-5.6.0-050600-generic
root=PARTUUID=bc3d472f-401e-4774-affa-df1acba65a73 ro console=tty1
console=ttyS0 earlyprintk=ttyS0 ignore_loglevel sysrq_always_enabled
unknown_nmi_panic
initrd/boot/initrd.img-5.6.0-050600-generic
else
linux /boot/vmlinuz-5.6.0-050600-generic
root=PARTUUID=bc3d472f-401e-4774-affa-df1acba65a73 ro console=tty1
console=ttyS0 earlyprintk=ttyS0 ignore_loglevel sysrq_always_enabled
unknown_nmi_panic panic=-1
#Dexuan: here the initrd line is missing!
fi
initrdfail
}
As we can see, Ubuntu only uses the initrd.img if initrdfail=1.
Normally, initrdfail = 0, so when we boot the v5.6 kernel for the
first time, we must hit the “fail to mount rootfs” panic and the
kernel will automatically reboot….
Also, the “initrdfail” here marks initrdfail=1, so when the kernel
boots for the 2nd time, the kernel should successfully boot up. Next,
when the kernel boots for the 3rd time, it panics again since the
userspace program resets initrdfail to 0, and next time when the
kernel boots, it can boot up successfully -- this
“panic/success/panic/success” pattern repeats forever…
The linux-azure kernels are not affected since they have the vmbus driver and
storage drivers built-in (i.e. “=y”):
/boot/config-5.3.0-1013-azure:CONFIG_HYPERV_STORAGE=y
/boot/config-5.3.0-1013-azure:CONFIG_HYPERV=y
/boot/config-5.4.0-1006-azure:CONFIG_HYPERV_STORAGE=y
/boot/config-5.4.0-1006-azure:CONFIG_HYPERV=y
/boot/config-5.6.0-050600-generic:CONFIG_HYPERV_STORAGE=m
/boot/config-5.6.0-050600-generic:CONFIG_HYPERV=m
The v5.6 kernel uses =m rather than =y, so is affected here.
It looks the setting may be intentional, but we should not assume a
customer kernel must have the necessary vmbus/storage drivers built-
in.
This issue only happens to the Ubuntu Marketplace image (19.10 and maybe
19.04 as well?) on Azure.
We installed a Ubuntu 20.04 VM from the .iso file from
http://cdimage.ubuntu.com/daily-live/pending/ and don’t see the strange grub
issue.
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1870189/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1869860] Re: Ubuntu mainline kernel v5.6 not supported by bcmwl-kernel-source
*** This bug is a duplicate of bug 1872908 *** https://bugs.launchpad.net/bugs/1872908 ** This bug has been marked a duplicate of bug 1872908 bcmwl kernel module does not build with kernel version 5.6 or 5.8 -- 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/1869860 Title: Ubuntu mainline kernel v5.6 not supported by bcmwl-kernel-source Status in bcmwl package in Ubuntu: Confirmed Bug description: I am using Ubuntu 18.04 with kernel 4.15.0-91-generic and packet bcmwl-kernel-source version 6.30.223.271+bdcom-0ubuntu5~18.04.1 from bionic-updates. Wifi BCM43228 802.11a/b/g/n [14e4:4359] is fine working. But working stops after installing ubuntu mainline kernel v5.6 (image, modules, headers-all, headers-amd64). While installing kernel there were error messages regarding dkms and no dkms-modul was built. bcmwl-kernel-source should support kernel v5.6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1869860/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1872908] Re: bcmwl kernel module does not build with kernel version 5.6 or 5.8
** Tags removed: verification-needed
--
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/1872908
Title:
bcmwl kernel module does not build with kernel version 5.6 or 5.8
Status in bcmwl package in Ubuntu:
Fix Released
Status in bcmwl source package in Focal:
Fix Released
Bug description:
After kernel update to 5.6.0-1007-oem wifi stopped working.
Turned out dkms is unable to build the bcmwl module.
The make log shows:
ubuntu@ubuntu-inspiron-5482:~$ cat
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/make.log
DKMS make.log for bcmwl-6.30.223.271+bdcom for kernel 5.6.0-1007-oem (x86_64)
ons 15 apr 2020 09:19:05 CEST
make: Entering directory '/usr/src/linux-headers-5.6.0-1007-oem'
CFG80211 API is prefered for this kernel version
Using CFG80211 API
AR /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/built-in.a
CC [M] /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.o
CC [M] /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.o
CC [M] /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_iw.o
CC [M]
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.o
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c: In
function ‘osl_reg_map’:
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c:949:10:
error: implicit declaration of function ‘ioremap_nocache’; did you mean
‘ioremap_cache’? [-Werror=implicit-function-declaration]
949 | return (ioremap_nocache((unsigned long)pa, (unsigned long)size));
| ^~~
| ioremap_cache
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c:949:10:
warning: returning ‘int’ from a function with return type ‘void *’ makes
pointer from integer without a cast [-Wint-conversion]
949 | return (ioremap_nocache((unsigned long)pa, (unsigned long)size));
| ~^~~~
In file included from
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:40:
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:
In function ‘wl_set_auth_type’:
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.h:52:5:
warning: this statement may fall through [-Wimplicit-fallthrough=]
52 | if (wl_dbg_level & WL_DBG_DBG) { \
| ^
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:816:3:
note: in expansion of macro ‘WL_DBG’
816 | WL_DBG(("network eap\n"));
| ^~
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:817:2:
note: here
817 | default:
| ^~~
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c: In
function ‘wl_attach’:
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:593:20:
error: implicit declaration of function ‘ioremap_nocache’; did you mean
‘ioremap_cache’? [-Werror=implicit-function-declaration]
593 | if ((wl->regsva = ioremap_nocache(dev->base_addr, PCI_BAR0_WINSZ))
== NULL) {
|^~~
|ioremap_cache
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:593:18:
warning: assignment to ‘void *’ from ‘int’ makes pointer from integer without a
cast [-Wint-conversion]
593 | if ((wl->regsva = ioremap_nocache(dev->base_addr, PCI_BAR0_WINSZ))
== NULL) {
| ^
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c: In
function ‘wl_pci_probe’:
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:780:2:
warning: this ‘if’ clause does not guard... [-Wmisleading-indentation]
780 | if ((val & 0xff00) != 0)
| ^~
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:782:3:
note: ...this statement, but the latter is misleadingly indented as if it were
guarded by the ‘if’
782 | bar1_size = pci_resource_len(pdev, 2);
| ^
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:783:15:
warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
783 | bar1_addr = (uchar *)ioremap_nocache(pci_resource_start(pdev, 2),
| ^
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c: In
function ‘wl_reg_proc_entry’:
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:3376:58:
error: passing argument 4 of ‘proc_create_data’ from incompatible pointer type
[-Werror=incompatible-pointer-types]
3376 | if ((wl->proc_entry = proc_create_data(tmp, 0644, NULL, &wl_fops,
wl)) == NULL) {
| ^~~~
| |
|
[Kernel-packages] [Bug 1894329] Re: ZFS revert from grub menu not working.
** No longer affects: coreutils (Ubuntu Groovy)
** No longer affects: coreutils (Ubuntu Focal)
** No longer affects: coreutils (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1894329
Title:
ZFS revert from grub menu not working.
Status in zfs-linux package in Ubuntu:
Fix Released
Status in zfs-linux source package in Focal:
Fix Released
Status in zfs-linux source package in Groovy:
Fix Released
Bug description:
[Impact]
* Users can’t revert to previous snapshots when enabling the hw enablement
stack kernel on focal or using any more recent version.
* The option is available on grub and will let you with a broken system,
partially cloned.
[Test Case]
* Boot on a system, using ZFS and ZSys.
* In grub, select "History" entry
* Select one of the "Revert" option: the system should boot after being
reverted with an older version.
[Where problems could occur]
* The code is in the initramfs, where the generated id suffix for all our
ZFS datasets was empty due to new coreutils/kernels.
* We replace dd with another way (more robust and simple) for generating
this ID.
-
@coreutils maintainers, any idea why dd is being flagged as having an
executable stack?
When I try to revert to a previous state from the grub menu, the boot
fails. The system drops me to a repair modus.
zfs-mount-generator fails with the message:
couldn't ensure boot: Mounted clone bootFS dataset created by initramfs
doesn't have a valid _suffix (at least .*_): \"rpool/ROOT/ubuntu_\"".
After a reboot I have an extra clone called "rpool/ROOT/ubuntu_", indeed
without a suffix.
After a little investigation I found the problem in
/usr/share/initramfs-tools/scripts/zfs at the end in function
uid()
{
dd if=/dev/urandom of=/dev/stdout bs=1 count=100 2>/dev/null | tr -dc
'a-z0-9' | cut -c-6
}, the dd command fails during boot with the message "process 'dd' started
with executable stack.
After this an empty uid is returned which explains the dataset without a
proper suffix.
Replacing the function with:
uid()
{
grep -a -m10 -E "\*" /dev/urandom 2>/dev/null | tr -dc 'a-z0-9' | cut -c-6
}
fixes the problem.
Ubuntu version is:
Description:Ubuntu Groovy Gorilla (development branch)
Release:20.10
zfs-initramfs version is:
0.8.4-1ubuntu11
With regards,
Usarin Heininga
ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: zfs-initramfs 0.8.4-1ubuntu11
ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4
Uname: Linux 5.8.0-18-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu45
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: KDE
Date: Fri Sep 4 20:23:44 2020
InstallationDate: Installed on 2020-09-02 (2 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200831)
ProcEnviron:
LANGUAGE=
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=nl_NL.UTF-8
SHELL=/bin/bash
SourcePackage: zfs-linux
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1894329/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1913950] Re: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu1~1.3: bcmwl kernel module failed to build
*** This bug is a duplicate of bug 1827100 *** https://bugs.launchpad.net/bugs/1827100 ** This bug has been marked a duplicate of bug 1827100 bcmwl 6.30.223.271+bdcom-0ubuntu4 ADT test failure with linux 5.1.0-1.1 -- 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/1913950 Title: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu1~1.3: bcmwl kernel module failed to build Status in bcmwl package in Ubuntu: New Bug description: guanhe@guanhe-Lenovo-G510:~/Downloads$ lsb_release -rd Description: Ubuntu 20.04.1 LTS Release: 20.04 dpkg -i bcmwl-kernel-source_6.30.223.271+bdcom-0ubuntu1~1.3_amd64.deb cat /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/make.log DKMS make.log for bcmwl-6.30.223.271+bdcom for kernel 5.8.0-41-generic (x86_64) 2021年 01月 31日 星期日 23:09:12 CST make: Entering directory '/usr/src/linux-headers-5.8.0-41-generic' CFG80211 API is prefered for this kernel version Using CFG80211 API AR /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/built-in.a CC [M] /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.o CC [M] /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.o CC [M] /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_iw.o CC [M] /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.o /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c: In function ‘wl_dev_ioctl’: /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:462:9: error: implicit declaration of function ‘get_ds’; did you mean ‘get_fs’? [-Werror=implicit-function-declaration] 462 | set_fs(get_ds()); | ^~ | get_fs /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:462:9: error: incompatible type for argument 1 of ‘set_fs’ 462 | set_fs(get_ds()); ProblemType: Package DistroRelease: Ubuntu 20.04 Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu1~1.3 ProcVersionSignature: Ubuntu 5.8.0-41.46~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 CasperMD5CheckResult: skip DKMSKernelVersion: 5.8.0-41-generic Date: Sun Jan 31 23:09:15 2021 DuplicateSignature: dkms:bcmwl-kernel-source:6.30.223.271+bdcom-0ubuntu1~1.3:/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:462:9: error: implicit declaration of function ‘get_ds’; did you mean ‘get_fs’? [-Werror=implicit-function-declaration] InstallationDate: Installed on 2020-12-14 (48 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageVersion: 6.30.223.271+bdcom-0ubuntu1~1.3 Python3Details: /usr/local/bin/python3.9, Python 3.9.1, unpackaged PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.2 SourcePackage: bcmwl Title: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu1~1.3: bcmwl 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/bcmwl/+bug/1913950/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1872908] Re: bcmwl kernel module does not build with kernel version 5.6 or 5.8
** Summary changed:
- bcmwl kernel module does not build with 5.6.0 kernel or later
+ bcmwl kernel module does not build with kernel version 5.6 or 5.8
--
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/1872908
Title:
bcmwl kernel module does not build with kernel version 5.6 or 5.8
Status in bcmwl package in Ubuntu:
Fix Released
Status in bcmwl source package in Focal:
Fix Committed
Bug description:
After kernel update to 5.6.0-1007-oem wifi stopped working.
Turned out dkms is unable to build the bcmwl module.
The make log shows:
ubuntu@ubuntu-inspiron-5482:~$ cat
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/make.log
DKMS make.log for bcmwl-6.30.223.271+bdcom for kernel 5.6.0-1007-oem (x86_64)
ons 15 apr 2020 09:19:05 CEST
make: Entering directory '/usr/src/linux-headers-5.6.0-1007-oem'
CFG80211 API is prefered for this kernel version
Using CFG80211 API
AR /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/built-in.a
CC [M] /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.o
CC [M] /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.o
CC [M] /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_iw.o
CC [M]
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.o
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c: In
function ‘osl_reg_map’:
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c:949:10:
error: implicit declaration of function ‘ioremap_nocache’; did you mean
‘ioremap_cache’? [-Werror=implicit-function-declaration]
949 | return (ioremap_nocache((unsigned long)pa, (unsigned long)size));
| ^~~
| ioremap_cache
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c:949:10:
warning: returning ‘int’ from a function with return type ‘void *’ makes
pointer from integer without a cast [-Wint-conversion]
949 | return (ioremap_nocache((unsigned long)pa, (unsigned long)size));
| ~^~~~
In file included from
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:40:
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:
In function ‘wl_set_auth_type’:
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.h:52:5:
warning: this statement may fall through [-Wimplicit-fallthrough=]
52 | if (wl_dbg_level & WL_DBG_DBG) { \
| ^
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:816:3:
note: in expansion of macro ‘WL_DBG’
816 | WL_DBG(("network eap\n"));
| ^~
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:817:2:
note: here
817 | default:
| ^~~
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c: In
function ‘wl_attach’:
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:593:20:
error: implicit declaration of function ‘ioremap_nocache’; did you mean
‘ioremap_cache’? [-Werror=implicit-function-declaration]
593 | if ((wl->regsva = ioremap_nocache(dev->base_addr, PCI_BAR0_WINSZ))
== NULL) {
|^~~
|ioremap_cache
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:593:18:
warning: assignment to ‘void *’ from ‘int’ makes pointer from integer without a
cast [-Wint-conversion]
593 | if ((wl->regsva = ioremap_nocache(dev->base_addr, PCI_BAR0_WINSZ))
== NULL) {
| ^
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c: In
function ‘wl_pci_probe’:
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:780:2:
warning: this ‘if’ clause does not guard... [-Wmisleading-indentation]
780 | if ((val & 0xff00) != 0)
| ^~
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:782:3:
note: ...this statement, but the latter is misleadingly indented as if it were
guarded by the ‘if’
782 | bar1_size = pci_resource_len(pdev, 2);
| ^
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:783:15:
warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
783 | bar1_addr = (uchar *)ioremap_nocache(pci_resource_start(pdev, 2),
| ^
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c: In
function ‘wl_reg_proc_entry’:
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:3376:58:
error: passing argument 4 of ‘proc_create_data’ from incompatible pointer type
[-Werror=incompatible-pointer-types]
3376 | if ((wl->proc_entry = proc_create_data(tmp, 0644, NULL, &wl_fops,
wl)) == NULL) {
|
[Kernel-packages] [Bug 1871306] Re: [SRU]No sound from internal card chtmax98090 - missing UCM2 files in alsa-ucm-conf 1.2.2, available in alsa-ucm-conf 1.2.3
alsa-ucm-conf (1.2.4-1) unstable; urgency=medium * New upstream release. * Update Standards-Version to 4.5.1, with no changes needed. -- Jordi Mallach Mon, 07 Dec 2020 22:13:23 +0100 ** Changed in: alsa-ucm-conf (Ubuntu) Status: In Progress => Fix Released ** Summary changed: - [SRU]No sound from internal card chtmax98090 - missing UCM2 files in alsa-ucm-conf 1.2.2, available in alsa-ucm-conf 1.2.3 + [SRU] No sound from internal card chtmax98090 (missing UCM2 files in alsa-ucm-conf) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/1871306 Title: [SRU] No sound from internal card chtmax98090 (missing UCM2 files in alsa-ucm-conf) Status in OEM Priority Project: New Status in alsa-ucm-conf package in Ubuntu: Fix Released Status in alsa-ucm-conf source package in Focal: In Progress Status in alsa-ucm-conf source package in Groovy: In Progress Bug description: [Impact] There is no ucm for ASUS C300 in the 20.04 and 20.10, as a result, the audio doesn't work on this machine after installing the 20.04 or 20.10. [Fix] The ucm files for this machine are in the alsa-ucm-conf 1.2.3, cherry-pick them to ubuntu 20.04 and 20.10 [Test Case] After booting up, use speaker to play some sound, it works well, plug a headset, play sound to headphone, it basically works but has some crankling noise, it is a kernel issue for this noise. [Regression Risk] This SRU adds new ucm files, If the machine uses the audio driver of chtmax98090, it will apply this new added ucm files, there will be speaker/headphone in the UI. So the possible regression is with this SRU, users could see the audio devices in the UI but the audio doesn't work (without this SRU, users couldn't see the audio devices in the UI at all and the audio doesn't work). This possibility is low since we tested it on the ASUS C300. Asus C300 (repurposed chromembook - bios flashed by Mr.Chromebox script) - Kubuntu Focal minimal fresh installation. The sound card is detected: I see it in the Plasma Widget, in pavucontrol, in alsamixer and it's not muted. I tried and add in /usr/share/alsa/ucm/chtmax98090/ the old style use case config files: no success. I tried and unmute speakers left and right in alsamixer: no success. I rapidly tested Ubuntu Mate Focal fresh install: I had exactly the same issue. I'm running on the same rig Debian Bullseye, kernel 5.4: sound card output and input are both working perfectly - I noticed that in Kubuntu alsamixer Kubuntu when I open it I have an entry HDA IntelPCH (the HDMI card), while in Debian I find Pulseaudio. I attach the alsa-info.sh output. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.17 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu24 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: KDE Date: Tue Apr 7 08:55:46 2020 InstallationDate: Installed on 2020-04-04 (2 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: gabriel3937 F pulseaudio /dev/snd/controlC0: gabriel3937 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-04 (3 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:07dc Intel Corp. Bus 001 Device 003: ID 13d3:5657 IMC Networks USB2.0 UVC HD Webcam Bus 001 Device 002: ID 062a:4101 MosArt Semiconductor Corp. Wireless Keyboard/Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: GOOGLE Quawks Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic root=UUID=225cba91-c164-4882-95d4-4f9854a80fe9 ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 RelatedPackageVersions: linux-restricted-modules-5.4.0-21-generic N/A linux-backports-modules-5.4.0-21-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/17/2020 dmi.bios.vendor: coreboot dmi.bios.version: MrChromebox-4.11.2 dmi.board.name: Quawks dmi.board.vendor: GOOGLE dmi.board.ve
[Kernel-packages] [Bug 1897982] Re: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5 (amd64 binary) in ubuntu groovy leaves MacBook Air offline
*** This bug is a duplicate of bug 1872908 *** https://bugs.launchpad.net/bugs/1872908 ** This bug has been marked a duplicate of bug 1872908 bcmwl kernel module does not build with 5.6.0 kernel or later -- 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/1897982 Title: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5 (amd64 binary) in ubuntu groovy leaves MacBook Air offline Status in bcmwl package in Ubuntu: New Bug description: bcmwl-kernel-source_6.30.223.271+bdcom-0ubuntu5_amd64.deb leaves MacBook Air with no network. How to reproduce: 1. Install Ubuntu 20.10 with update-manager -d on MacBook Air 2. Reboot 3. Wifi Network is offline because the package bcmwl-kernel- source_6.30.223.271+bdcom-0ubuntu5_amd64.deb failed in post-configure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1897982/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1902409] Re: bcmwl-kernel-source not supported on kernel package linux-headers-5.8.0-7625-generic
*** This bug is a duplicate of bug 1872908 *** https://bugs.launchpad.net/bugs/1872908 ** This bug has been marked a duplicate of bug 1872908 bcmwl kernel module does not build with 5.6.0 kernel or later -- 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/1902409 Title: bcmwl-kernel-source not supported on kernel package linux- headers-5.8.0-7625-generic Status in bcmwl package in Ubuntu: Confirmed Bug description: I'm currently at 20.04 LTS with 5.8 kernel, the driver doesn't work and my wifi is dissappear. I've tried to reinstall the driver but it doesn't work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1902409/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1910890] Re: package bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu1~1.3 failed to install/upgrade: installed bcmwl-kernel-source package post-installation script subprocess ret
*** This bug is a duplicate of bug 1872908 *** https://bugs.launchpad.net/bugs/1872908 ** This bug has been marked a duplicate of bug 1872908 bcmwl kernel module does not build with 5.6.0 kernel or later -- 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/1910890 Title: package bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu1~1.3 failed to install/upgrade: installed bcmwl-kernel-source package post- installation script subprocess returned error exit status 10 Status in bcmwl package in Ubuntu: Confirmed Bug description: ther eis no wireless, trying to fix it ProblemType: Package DistroRelease: Ubuntu 20.04 Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu1~1.3 ProcVersionSignature: Ubuntu 5.8.0-36.40~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-36-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.14 AptOrdering: NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Sat Jan 9 23:10:07 2021 ErrorMessage: installed bcmwl-kernel-source package post-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2021-01-10 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.2 SourcePackage: bcmwl Title: package bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu1~1.3 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/1910890/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1910995] Re: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5: bcmwl kernel module failed to build
*** This bug is a duplicate of bug 1872908 *** https://bugs.launchpad.net/bugs/1872908 ** This bug has been marked a duplicate of bug 1872908 bcmwl kernel module does not build with 5.6.0 kernel or later -- 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/1910995 Title: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5: bcmwl kernel module failed to build Status in bcmwl package in Ubuntu: Confirmed Bug description: after update the packages and reboot my computer, the wifi do not work any more. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5 ProcVersionSignature: Ubuntu 5.8.0-36.40~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-36-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip DKMSKernelVersion: 5.8.0-34-generic Date: Thu Jan 7 06:11:05 2021 DuplicateSignature: dkms:bcmwl-kernel-source:6.30.223.271+bdcom-0ubuntu5:/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c:949:10: error: implicit declaration of function ‘ioremap_nocache’; did you mean ‘ioremap_cache’? [-Werror=implicit-function-declaration] InstallationDate: Installed on 2020-09-18 (114 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageVersion: 6.30.223.271+bdcom-0ubuntu5 Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.2 SourcePackage: bcmwl Title: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5: bcmwl 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/bcmwl/+bug/1910995/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1910572] Re: Ugprading to 5.8.0-34-generic kernel broke wifi (BCM4352 802.11ac Wireless Network Adapter [14e4:43b1] (rev 03))
*** This bug is a duplicate of bug 1872908 ***
https://bugs.launchpad.net/bugs/1872908
** This bug has been marked a duplicate of bug 1872908
bcmwl kernel module does not build with 5.6.0 kernel or later
--
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/1910572
Title:
Ugprading to 5.8.0-34-generic kernel broke wifi (BCM4352 802.11ac
Wireless Network Adapter [14e4:43b1] (rev 03))
Status in bcmwl package in Ubuntu:
New
Bug description:
DKMS make.log for bcmwl-6.30.223.271+bdcom for kernel 5.8.0-34-generic
(x86_64)
joi 7 ianuarie 2021, 19:24:12 +0200
make: Entering directory '/usr/src/linux-headers-5.8.0-34-generic'
CFG80211 API is prefered for this kernel version
Using CFG80211 API
AR /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/built-in.a
CC [M] /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.o
CC [M] /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.o
CC [M] /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_iw.o
CC [M]
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.o
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c: In
function ‘osl_reg_map’:
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c:949:10:
error: implicit declaration of function ‘iore>
949 | return (ioremap_nocache((unsigned long)pa, (unsigned long)size));
| ^~~
| ioremap_cache
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c:949:10:
warning: returning ‘int’ from a function with>
949 | return (ioremap_nocache((unsigned long)pa, (unsigned long)size));
| ~^~~~
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c: In
function ‘wl_attach’:
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:593:20:
error: implicit declaration of function ‘iorem>
593 | if ((wl->regsva = ioremap_nocache(dev->base_addr, PCI_BAR0_WINSZ))
== NULL) {
|^~~
|ioremap_cache
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:593:18:
warning: assignment to ‘void *’ from ‘int’ mak>
593 | if ((wl->regsva = ioremap_nocache(dev->base_addr, PCI_BAR0_WINSZ))
== NULL) {
| ^
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c: In
function ‘wl_pci_probe’:
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:780:2:
warning: this ‘if’ clause does not guard... [-W>
780 | if ((val & 0xff00) != 0)
| ^~
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:782:3:
note: ...this statement, but the latter is misl>
782 | bar1_size = pci_resource_len(pdev, 2);
| ^
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:783:15:
warning: cast to pointer from integer of diffe>
783 | bar1_addr = (uchar *)ioremap_nocache(pci_resource_start(pdev, 2),
| ^
In file included from
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:40:
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:
In function ‘wl_set_auth_type’:
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.h:52:5:
warning: this statement may fall throu>
52 | if (wl_dbg_level & WL_DBG_DBG) { \
| ^
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:816:3:
note: in expansion of macro ‘WL_DBG’
816 | WL_DBG(("network eap\n"));
| ^~
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:817:2:
note: here
817 | default:
| ^~~
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c: In
function ‘wl_reg_proc_entry’:
817 | default:
| ^~~
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c: In
function ‘wl_reg_proc_entry’:
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:3376:58:
error: passing argument 4 of ‘proc_create_dat>
3376 | if ((wl->proc_entry = proc_create_data(tmp, 0644, NULL, &wl_fops,
wl)) == NULL) {
| ^~~~
| |
| const struct
file_operations *
In file included from
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:38:
./include/linux/proc_fs.h:102:31: note: expected ‘const struct proc_ops *’
but argument is of type ‘const struct file_ope>
102 | extern struct proc_dir_entry *proc_create_data(const char *, umode_t,
|
[Kernel-packages] [Bug 1911240] Re: package bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu4 failed to install/upgrade: installed bcmwl-kernel-source package post-installation script subprocess returne
*** This bug is a duplicate of bug 1872908 *** https://bugs.launchpad.net/bugs/1872908 linux-libc-dev 5.8.0-36.40 [origin: unknown] ** This bug has been marked a duplicate of bug 1872908 bcmwl kernel module does not build with 5.6.0 kernel or later -- 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/1911240 Title: package bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu4 failed to install/upgrade: installed bcmwl-kernel-source package post- installation script subprocess returned error exit status 10 Status in bcmwl package in Ubuntu: Confirmed Bug description: dpkg: error processing package bcmwl-kernel-source (--configure): installed bcmwl-kernel-source package post-installation script subprocess returned error exit status 10 ProblemType: Package DistroRelease: Ubuntu 20.04 Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu4 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Jan 12 13:53:08 2021 ErrorMessage: installed bcmwl-kernel-source package post-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2021-01-12 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: bcmwl Title: package bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu4 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/1911240/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1910618] Re: bcmwl 6.30.223.271+bdcom build fails with kernel 5.8.0-34/36 Ubuntu 20.04.1 LTS
*** This bug is a duplicate of bug 1872908 ***
https://bugs.launchpad.net/bugs/1872908
** This bug has been marked a duplicate of bug 1872908
bcmwl kernel module does not build with 5.6.0 kernel or later
--
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/1910618
Title:
bcmwl 6.30.223.271+bdcom build fails with kernel 5.8.0-34/36 Ubuntu
20.04.1 LTS
Status in bcmwl package in Ubuntu:
Confirmed
Bug description:
Ubuntu 20.04.1 LTS
bcmwl-kernel-source_6.30.223.271
I believe the important part of the
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/make.log is below.
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c: In
function ‘wl_reg_proc_entry’:
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:3376:58:
error: passing argument 4 of ‘proc_create_data’ from incompatible pointe
r type [-Werror=incompatible-pointer-types]
3376 | if ((wl->proc_entry = proc_create_data(tmp, 0644, NULL, &wl_fops,
wl)) == NULL) {
| ^~~~
| |
| const struct
file_operations *
In file included from
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:38:
./include/linux/proc_fs.h:102:31: note: expected ‘const struct proc_ops *’
but argument is of type ‘const struct file_operations *’
102 | extern struct proc_dir_entry *proc_create_data(const char *, umode_t,
| ^~~~
It looks like
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c uses the
file_operations structure.
lines 3359-3381 from wl_linux.c
#if LINUX_VERSION_CODE >= KERNEL_VERSION(3, 10, 0)
static const struct file_operations wl_fops = {
.owner = THIS_MODULE,
.read = wl_proc_read,
.write = wl_proc_write,
};
#endif
static int
wl_reg_proc_entry(wl_info_t *wl)
{
char tmp[32];
sprintf(tmp, "%s%d", HYBRID_PROC, wl->pub->unit);
#if LINUX_VERSION_CODE < KERNEL_VERSION(3, 10, 0)
if ((wl->proc_entry = create_proc_entry(tmp, 0644, NULL)) == NULL) {
WL_ERROR(("%s: create_proc_entry %s failed\n", __FUNCTION__,
tmp));
#else
if ((wl->proc_entry = proc_create_data(tmp, 0644, NULL, &wl_fops, wl))
== NULL) {
WL_ERROR(("%s: proc_create_data %s failed\n", __FUNCTION__,
tmp));
#endif
ASSERT(0);
return -1;
}
However, it looks like proc_fs.h uses a different structure (proc_ops).
/usr/src/linux-headers-5.8.0-34-generic/include/linux/proc_fs.h
/usr/src/linux-hwe-5.8-headers-5.8.0-34/include/linux/proc_fs.h
kernel 5.8.0-34
proc_fs.h
lines 29-43
struct proc_ops {
unsigned int proc_flags;
int (*proc_open)(struct inode *, struct file *);
ssize_t (*proc_read)(struct file *, char __user *, size_t, loff_t *);
ssize_t (*proc_write)(struct file *, const char __user *, size_t,
loff_t *);
loff_t (*proc_lseek)(struct file *, loff_t, int);
int (*proc_release)(struct inode *, struct file *);
__poll_t (*proc_poll)(struct file *, struct poll_table_struct *);
long(*proc_ioctl)(struct file *, unsigned int, unsigned long);
#ifdef CONFIG_COMPAT
long(*proc_compat_ioctl)(struct file *, unsigned int, unsigned
long);
#endif
int (*proc_mmap)(struct file *, struct vm_area_struct *);
unsigned long (*proc_get_unmapped_area)(struct file *, unsigned long,
unsigned long, unsigned long, unsigned long);
} __randomize_layout;
and lines 102-107
extern struct proc_dir_entry *proc_create_data(const char *, umode_t,
struct proc_dir_entry *,
const struct proc_ops *,
void *);
struct proc_dir_entry *proc_create(const char *name, umode_t mode,
struct proc_dir_entry *parent, const struct proc_ops *proc_ops);
Looking back at the linux 5.4.0-59 headers, proc_fs.h appears to use the
file_operations structure.
/usr/src/linux-headers-5.4.0-59-generic/include/linux/proc_fs.h
/usr/src/linux-headers-5.4.0-59/include/linux/proc_fs.h
kernel 5.4.0-59
proc_fs.h
lines 44-49
extern struct proc_dir_entry *proc_create_data(const char *, umode_t,
struct proc_dir_entry *,
const struct file_operations *,
void *);
struct proc_dir_entry *proc_create(const char *name, umode_t mode,
struct proc_dir_entry *parent, const struct file_operations
*proc_fops);
If this is where the problem lie
[Kernel-packages] [Bug 1910875] Re: Broadcom wireless driver failed to install with code 10 on focal 20.04
*** This bug is a duplicate of bug 1872908 ***
https://bugs.launchpad.net/bugs/1872908
** This bug has been marked a duplicate of bug 1872908
bcmwl kernel module does not build with 5.6.0 kernel or later
--
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/1910875
Title:
Broadcom wireless driver failed to install with code 10 on focal
20.04
Status in bcmwl package in Ubuntu:
Confirmed
Bug description:
First, I suspect this may be the same bug as Bug #1905211 "package
bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5 failed focal fossa in
kernel v5.9" because I got the same error "installed bcmwl-kernel-
source package post-installation script subprocess returned error exit
status 10". However, I wanted to make a separate report because I am
still on kernel v5.8. Please merge these threads if it seems like
they're the same bug.
Anyway, my problem is this:
The last time I installed a tranche of system updates, I got a "System
software problem detected" dialog and submitted the crash report. The
next time I booted up my computer, the Broadcom wifi device was not
recognized. The wifi had worked fine up until that point.
I tried to manually uninstall and reinstall the driver using dpkg with
the bcmwl-kernel-source (6.30.223.271+bdcom-0ubuntu5) package
downloaded from packages.ubuntu.com (the machine in question does not
have a wired ethernet connection). dpkg produced the following
output:
Preparing to unpack bcmwl-kernel-source_6.30.223.271+bdcom-0ubuntu5_amd64.deb
...
Unpacking bcmwl-kernel-source (6.30.223.271+bdcom-0ubuntu5) over
(6.30.223.271+bdcom-0ubuntu5) ...
Setting up bcmwl-kernel-source (6.30.223.271+bdcom-0ubuntu5) ...
Loading new bcmwl-6.30.223.271+bdcom DKMS files...
Building for 5.8.0-36-generic
Building for architecture x86_64
Building initial module for 5.8.0-36-generic
ERROR: Cannot create report: [Errno 17] File exists:
'/var/crash/bcmwl-kernel-source.0.crash'
Error! Bad return status for module build on kernel: 5.8.0-36-generic (x86_64)
Consult /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/make.log for more
information.
dpkg: error processing package bcmwl-kernel-source (--install):
installed bcmwl-kernel-source package post-installation script subprocess
returned error exit status 10
Errors were encountered while processing:
bcmwl-kernel-source
The make log from my manually installation attempt read:
DKMS make.log for bcmwl-6.30.223.271+bdcom for kernel 5.8.0-36-generic
(x86_64)
Sat 09 Jan 2021 01:14:26 PM PST
make: Entering directory '/usr/src/linux-headers-5.8.0-36-generic'
CFG80211 API is prefered for this kernel version
Using CFG80211 API
AR /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/built-in.a
CC [M] /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.o
CC [M] /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.o
CC [M] /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_iw.o
CC [M]
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.o
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c: In
function ‘osl_reg_map’:
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c:949:10:
error: implicit declaration of function ‘ioremap_nocache’; did you mean
‘ioremap_cache’? [-Werror=implicit-function-declaration]
949 | return (ioremap_nocache((unsigned long)pa, (unsigned long)size));
| ^~~
| ioremap_cache
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c:949:10:
warning: returning ‘int’ from a function with return type ‘void *’ makes
pointer from integer without a cast [-Wint-conversion]
949 | return (ioremap_nocache((unsigned long)pa, (unsigned long)size));
| ~^~~~
In file included from
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:40:
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:
In function ‘wl_set_auth_type’:
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.h:52:5:
warning: this statement may fall through [-Wimplicit-fallthrough=]
52 | if (wl_dbg_level & WL_DBG_DBG) { \
| ^
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:816:3:
note: in expansion of macro ‘WL_DBG’
816 | WL_DBG(("network eap\n"));
| ^~
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:817:2:
note: here
817 | default:
| ^~~
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c: In
function ‘wl_attach’:
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:593:20:
error: implicit declaration of function ‘ior
[Kernel-packages] [Bug 1906745] Re: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5: bcmwl kernel module failed to build
*** This bug is a duplicate of bug 1872908 *** https://bugs.launchpad.net/bugs/1872908 ** This bug has been marked a duplicate of bug 1872908 bcmwl kernel module does not build with 5.6.0 kernel or later -- 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/1906745 Title: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5: bcmwl kernel module failed to build Status in bcmwl package in Ubuntu: Confirmed Bug description: apt-get upgrade caused crash of wireless bcmwl afterwards my wifi fails to work before updates had x86_64 5.4.0-57-generic DISTRIB_ID=Ubuntu DISTRIB_RELEASE=20.04 DISTRIB_CODENAME=focal DISTRIB_DESCRIPTION="Ubuntu 20.04.1 LTS" apt-get upgrade The following NEW packages will be installed: linux-headers-5.8.0-32-generic linux-hwe-5.8-headers-5.8.0-32 linux-image-5.8.0-32-generic linux-modules-5.8.0-32-generic linux-modules-extra-5.8.0-32-generic The following packages will be upgraded: linux-generic-hwe-20.04 linux-headers-generic-hwe-20.04 linux-image-generic-hwe-20.04 wireless-regdb Setting up linux-modules-5.8.0-32-generic (5.8.0-32.34~20.04.1) ... Setting up linux-hwe-5.8-headers-5.8.0-32 (5.8.0-32.34~20.04.1) ... Setting up linux-headers-5.8.0-32-generic (5.8.0-32.34~20.04.1) ... /etc/kernel/header_postinst.d/dkms: * dkms: running auto installation service for kernel 5.8.0-32-generic Kernel preparation unnecessary for this kernel. Skipping... applying patch 0002-Makefile.patch...patching file Makefile Hunk #1 succeeded at 113 with fuzz 1. Hunk #2 succeeded at 132 with fuzz 2 (offset 1 line). applying patch 0003-Make-up-for-missing-init_MUTEX.patch...patching file src/wl/sys/wl_linux.c Hunk #1 succeeded at 111 with fuzz 2 (offset 12 lines). applying patch 0010-change-the-network-interface-name-from-eth-to-wlan.patch...patching file src/wl/sys/wl_linux.c Hunk #1 succeeded at 221 (offset -14 lines). applying patch 0013-gcc.patch...patching file Makefile applying patch 0019-broadcom-sta-6.30.223.248-3.18-null-pointer-fix.patch...patching file src/wl/sys/wl_linux.c Hunk #1 succeeded at 2169 (offset 12 lines). applying patch 0020-add-support-for-linux-4.3.patch...patching file src/shared/linux_osl.c applying patch 0021-add-support-for-Linux-4.7.patch...patching file src/wl/sys/wl_cfg80211_hybrid.c applying patch 0022-add-support-for-Linux-4.8.patch...patching file src/wl/sys/wl_cfg80211_hybrid.c Hunk #1 succeeded at 2391 (offset 3 lines). Hunk #2 succeeded at 2501 (offset 3 lines). Hunk #3 succeeded at 2933 (offset 9 lines). applying patch 0023-add-support-for-Linux-4.11.patch...patching file src/include/linuxver.h patching file src/wl/sys/wl_linux.c Hunk #1 succeeded at 2919 (offset 4 lines). applying patch 0024-add-support-for-Linux-4.12.patch...patching file src/wl/sys/wl_cfg80211_hybrid.c Hunk #1 succeeded at 55 (offset 5 lines). Hunk #2 succeeded at 472 (offset 5 lines). Hunk #3 succeeded at 2371 (offset 5 lines). Hunk #4 succeeded at 2388 (offset 5 lines). applying patch 0025-add-support-for-Linux-4.14.patch...patching file src/shared/linux_osl.c Hunk #1 succeeded at 1080 (offset 4 lines). applying patch 0026-add-support-for-Linux-4.15.patch...patching file src/wl/sys/wl_linux.c Hunk #2 succeeded at 2306 (offset 4 lines). Hunk #3 succeeded at 2368 (offset 4 lines). applying patch 0027-add-support-for-linux-5.1.patch...patching file src/include/linuxver.h Hunk #1 succeeded at 595 (offset 4 lines). Building module: cleaning build area... make -j8 KERNELRELEASE=5.8.0-32-generic -C /lib/modules/5.8.0-32-generic/build M=/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build...(bad exit status: 2) Error! Bad return status for module build on kernel: 5.8.0-32-generic (x86_64) Consult /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/make.log for more information. ...done. Setting up linux-image-5.8.0-32-generic (5.8.0-32.34~20.04.1) ... I: /boot/vmlinuz.old is now a symlink to vmlinuz-5.4.0-57-generic I: /boot/initrd.img.old is now a symlink to initrd.img-5.4.0-57-generic I: /boot/vmlinuz is now a symlink to vmlinuz-5.8.0-32-generic I: /boot/initrd.img is now a symlink to initrd.img-5.8.0-32-generic Setting up linux-headers-generic-hwe-20.04 (5.8.0.32.34~20.04.19) ... Setting up linux-modules-extra-5.8.0-32-generic (5.8.0-32.34~20.04.1) ... Setting up linux-image-generic-hwe-20.04 (5.8.0.32.34~20.04.19) ... Setting up linux-generic-hwe-20.04 (5.8.0.32.34~20.04.19) ... Processing triggers for man-db (2.9.1-1) ... Processing triggers for linux-image-5.8.0-32-generic (5.8.0-32.34~20.04.1) ... /etc/kernel/postinst.d/dkms: * dkms: running auto installation service for kernel 5.8.0-32-generic Kernel preparation unnecessary for this kernel. Skipping... applying patch 0002-Makefile.patch...patchin
[Kernel-packages] [Bug 1907557] Re: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5: bcmwl kernel module failed to build
*** This bug is a duplicate of bug 1872908 *** https://bugs.launchpad.net/bugs/1872908 ** This bug is no longer a duplicate of bug 1907445 bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5: bcmwl kernel module failed to build ** This bug has been marked a duplicate of bug 1872908 bcmwl kernel module does not build with 5.6.0 kernel -- 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/1907557 Title: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5: bcmwl kernel module failed to build Status in bcmwl package in Ubuntu: Confirmed Bug description: ? ProblemType: Package DistroRelease: Ubuntu 20.04 Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-57.63-generic 5.4.78 Uname: Linux 5.4.0-57-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia wl ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip DKMSKernelVersion: 5.8.0-32-generic Date: Thu Dec 10 10:16:44 2020 DuplicateSignature: dkms:bcmwl-kernel-source:6.30.223.271+bdcom-0ubuntu5:/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c:949:10: error: implicit declaration of function ‘ioremap_nocache’; did you mean ‘ioremap_cache’? [-Werror=implicit-function-declaration] InstallationDate: Installed on 2020-11-05 (34 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageVersion: 6.30.223.271+bdcom-0ubuntu5 Python3Details: /usr/bin/python3.8, Python 3.8.5, 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.2ubuntu0.2 SourcePackage: bcmwl Title: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5: bcmwl 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/bcmwl/+bug/1907557/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1907445] Re: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5: bcmwl kernel module failed to build
*** This bug is a duplicate of bug 1872908 *** https://bugs.launchpad.net/bugs/1872908 ** This bug has been marked a duplicate of bug 1872908 bcmwl kernel module does not build with 5.6.0 kernel -- 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/1907445 Title: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5: bcmwl kernel module failed to build Status in bcmwl package in Ubuntu: Confirmed Bug description: Wifi disappear on Macbook Pro 15" ProblemType: Package DistroRelease: Ubuntu 20.04 Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5 ProcVersionSignature: Ubuntu 5.8.0-32.34~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip DKMSKernelVersion: 5.8.0-32-generic Date: Tue Dec 8 18:14:41 2020 DuplicateSignature: dkms:bcmwl-kernel-source:6.30.223.271+bdcom-0ubuntu5:/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:593:20: error: implicit declaration of function ‘ioremap_nocache’; did you mean ‘ioremap_cache’? [-Werror=implicit-function-declaration] InstallationDate: Installed on 2020-05-07 (215 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageVersion: 6.30.223.271+bdcom-0ubuntu5 Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.3 SourcePackage: bcmwl Title: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5: bcmwl 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/bcmwl/+bug/1907445/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1872908] Re: bcmwl kernel module does not build with 5.6.0 kernel or later
** Summary changed:
- bcmwl kernel module does not build with 5.6.0 kernel
+ bcmwl kernel module does not build with 5.6.0 kernel or later
--
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/1872908
Title:
bcmwl kernel module does not build with 5.6.0 kernel or later
Status in bcmwl package in Ubuntu:
Fix Released
Status in bcmwl source package in Focal:
Triaged
Bug description:
After kernel update to 5.6.0-1007-oem wifi stopped working.
Turned out dkms is unable to build the bcmwl module.
The make log shows:
ubuntu@ubuntu-inspiron-5482:~$ cat
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/make.log
DKMS make.log for bcmwl-6.30.223.271+bdcom for kernel 5.6.0-1007-oem (x86_64)
ons 15 apr 2020 09:19:05 CEST
make: Entering directory '/usr/src/linux-headers-5.6.0-1007-oem'
CFG80211 API is prefered for this kernel version
Using CFG80211 API
AR /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/built-in.a
CC [M] /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.o
CC [M] /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.o
CC [M] /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_iw.o
CC [M]
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.o
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c: In
function ‘osl_reg_map’:
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c:949:10:
error: implicit declaration of function ‘ioremap_nocache’; did you mean
‘ioremap_cache’? [-Werror=implicit-function-declaration]
949 | return (ioremap_nocache((unsigned long)pa, (unsigned long)size));
| ^~~
| ioremap_cache
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c:949:10:
warning: returning ‘int’ from a function with return type ‘void *’ makes
pointer from integer without a cast [-Wint-conversion]
949 | return (ioremap_nocache((unsigned long)pa, (unsigned long)size));
| ~^~~~
In file included from
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:40:
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:
In function ‘wl_set_auth_type’:
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.h:52:5:
warning: this statement may fall through [-Wimplicit-fallthrough=]
52 | if (wl_dbg_level & WL_DBG_DBG) { \
| ^
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:816:3:
note: in expansion of macro ‘WL_DBG’
816 | WL_DBG(("network eap\n"));
| ^~
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:817:2:
note: here
817 | default:
| ^~~
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c: In
function ‘wl_attach’:
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:593:20:
error: implicit declaration of function ‘ioremap_nocache’; did you mean
‘ioremap_cache’? [-Werror=implicit-function-declaration]
593 | if ((wl->regsva = ioremap_nocache(dev->base_addr, PCI_BAR0_WINSZ))
== NULL) {
|^~~
|ioremap_cache
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:593:18:
warning: assignment to ‘void *’ from ‘int’ makes pointer from integer without a
cast [-Wint-conversion]
593 | if ((wl->regsva = ioremap_nocache(dev->base_addr, PCI_BAR0_WINSZ))
== NULL) {
| ^
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c: In
function ‘wl_pci_probe’:
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:780:2:
warning: this ‘if’ clause does not guard... [-Wmisleading-indentation]
780 | if ((val & 0xff00) != 0)
| ^~
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:782:3:
note: ...this statement, but the latter is misleadingly indented as if it were
guarded by the ‘if’
782 | bar1_size = pci_resource_len(pdev, 2);
| ^
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:783:15:
warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
783 | bar1_addr = (uchar *)ioremap_nocache(pci_resource_start(pdev, 2),
| ^
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c: In
function ‘wl_reg_proc_entry’:
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:3376:58:
error: passing argument 4 of ‘proc_create_data’ from incompatible pointer type
[-Werror=incompatible-pointer-types]
3376 | if ((wl->proc_entry = proc_create_data(tmp, 0644, NULL, &wl_fops,
wl)) == NULL) {
|
[Kernel-packages] [Bug 1910555] Re: Driver build error on kernel 5.8, but works on 5.4
*** This bug is a duplicate of bug 1872908 *** https://bugs.launchpad.net/bugs/1872908 ** This bug has been marked a duplicate of bug 1872908 bcmwl kernel module does not build with 5.6.0 kernel -- 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/1910555 Title: Driver build error on kernel 5.8, but works on 5.4 Status in bcmwl package in Ubuntu: Confirmed Bug description: Recently kernel was updated on Focal from 5.4 to 5.8. From that moment on WiFi doesn't work anymore. After a try rebuild (reconfigure) the result is: --- # dpkg-reconfigure bcmwl-kernel-source Removing all DKMS Modules Done. Loading new bcmwl-6.30.223.271+bdcom DKMS files... Building for 5.4.0-59-generic 5.8.0-34-generic Building for architecture x86_64 Building initial module for 5.4.0-59-generic Done. wl.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/5.4.0-59-generic/updates/dkms/ depmod DKMS: install completed. Building initial module for 5.8.0-34-generic ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/bcmwl-kernel-source.0.crash' Error! Bad return status for module build on kernel: 5.8.0-34-generic (x86_64) Consult /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/make.log for more information. --- As could be seen, the build for 5.4 completes successfully (and works on same kernel), but for 5.8 fails. Seems something is going wrong with missing function declaration - function "ioremap_nocache", as could be seen in attached make.log. I'm guessing, driver code may need be updated according to the new kernel headers. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78 Uname: Linux 5.4.0-59-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Thu Jan 7 17:13:05 2021 InstallationDate: Installed on 2020-06-22 (198 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: bcmwl UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1910555/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1911840] Re: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5: bcmwl kernel module failed to build
*** This bug is a duplicate of bug 1872908 *** https://bugs.launchpad.net/bugs/1872908 ** This bug is no longer a duplicate of bug 1907445 bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5: bcmwl kernel module failed to build ** This bug has been marked a duplicate of bug 1872908 bcmwl kernel module does not build with 5.6.0 kernel -- 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/1911840 Title: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5: bcmwl kernel module failed to build Status in bcmwl package in Ubuntu: New Bug description: Failed during update to Ubuntu 20.04 - wifi no longer works ProblemType: Package DistroRelease: Ubuntu 20.04 Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5 ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 CasperMD5CheckResult: skip DKMSKernelVersion: 5.8.0-38-generic Date: Thu Jan 14 21:48:02 2021 DuplicateSignature: dkms:bcmwl-kernel-source:6.30.223.271+bdcom-0ubuntu5:/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:593:20: error: implicit declaration of function ‘ioremap_nocache’; did you mean ‘ioremap_cache’? [-Werror=implicit-function-declaration] InstallationDate: Installed on 2021-01-14 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageVersion: 6.30.223.271+bdcom-0ubuntu5 Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.2 SourcePackage: bcmwl Title: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5: bcmwl 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/bcmwl/+bug/1911840/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1910515] Re: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5: bcmwl kernel module failed to build
*** This bug is a duplicate of bug 1872908 *** https://bugs.launchpad.net/bugs/1872908 ** This bug is no longer a duplicate of bug 1907445 bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5: bcmwl kernel module failed to build ** This bug has been marked a duplicate of bug 1872908 bcmwl kernel module does not build with 5.6.0 kernel -- 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/1910515 Title: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5: bcmwl kernel module failed to build Status in bcmwl package in Ubuntu: New Bug description: wifi stopped working after update from software and updates ProblemType: Package DistroRelease: Ubuntu 20.04 Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5 ProcVersionSignature: Ubuntu 5.8.0-34.37~20.04.2-generic 5.8.18 Uname: Linux 5.8.0-34-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip DKMSKernelVersion: 5.8.0-34-generic Date: Thu Jan 7 14:08:16 2021 DuplicateSignature: dkms:bcmwl-kernel-source:6.30.223.271+bdcom-0ubuntu5:/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c:949:10: error: implicit declaration of function ‘ioremap_nocache’; did you mean ‘ioremap_cache’? [-Werror=implicit-function-declaration] InstallationDate: Installed on 2020-12-07 (30 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageVersion: 6.30.223.271+bdcom-0ubuntu5 Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.2 SourcePackage: bcmwl Title: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5: bcmwl 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/bcmwl/+bug/1910515/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1910467] Re: bcmwl-kernel-source 6.30.223.271 stopped working with latest kernel 5.8.0-34
*** This bug is a duplicate of bug 1872908 ***
https://bugs.launchpad.net/bugs/1872908
** This bug is no longer a duplicate of bug 1907445
bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5: bcmwl kernel module failed
to build
** This bug has been marked a duplicate of bug 1872908
bcmwl kernel module does not build with 5.6.0 kernel
--
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/1910467
Title:
bcmwl-kernel-source 6.30.223.271 stopped working with latest kernel
5.8.0-34
Status in bcmwl package in Ubuntu:
New
Bug description:
Hello,
This is my first time reporting a bug so please bear with me in case
something is missing :)
After upgrading my Linux Kernel to version 5.8.0-34-generic my WiFi
simply stopped working. So then I tried to understand what happened
with the module and saw some errors related to the bcmwl-kernel-source
(6.30.223.271), tried to remove the bcmwl-kernel-source package and
install it again but that still didn't work. Below I leave a log from
the crash:
- - - - - Log Starts Here - - - - -
ProblemType: Package
DKMSBuildLog:
DKMS make.log for bcmwl-6.30.223.271+bdcom for kernel 5.8.0-34-generic
(x86_64)
qua 06 jan 2021 23:43:32 WET
make: Entering directory '/usr/src/linux-headers-5.8.0-34-generic'
CFG80211 API is prefered for this kernel version
Using CFG80211 API
AR /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/built-in.a
CC [M] /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.o
CC [M] /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.o
CC [M] /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_iw.o
CC [M]
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.o
In file included from
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:40:
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:
In function ‘wl_set_auth_type’:
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.h:52:5:
warning: this statement may fall through [-Wimplicit-fallthrough=]
52 | if (wl_dbg_level & WL_DBG_DBG) { \
| ^
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:816:3:
note: in expansion of macro ‘WL_DBG’
816 | WL_DBG(("network eap\n"));
| ^~
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:817:2:
note: here
817 | default:
| ^~~
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c: In
function ‘osl_reg_map’:
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c:949:10:
error: implicit declaration of function ‘ioremap_nocache’; did you mean
‘ioremap_cache’? [-Werror=implicit-function-declaration]
949 | return (ioremap_nocache((unsigned long)pa, (unsigned long)size));
| ^~~
| ioremap_cache
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c:949:10:
warning: returning ‘int’ from a function with return type ‘void *’ makes
pointer from integer without a cast [-Wint-conversion]
949 | return (ioremap_nocache((unsigned long)pa, (unsigned long)size));
| ~^~~~
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c: In
function ‘wl_attach’:
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:593:20:
error: implicit declaration of function ‘ioremap_nocache’; did you mean
‘ioremap_cache’? [-Werror=implicit-function-declaration]
593 | if ((wl->regsva = ioremap_nocache(dev->base_addr, PCI_BAR0_WINSZ))
== NULL) {
|^~~
|ioremap_cache
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:593:18:
warning: assignment to ‘void *’ from ‘int’ makes pointer from integer without a
cast [-Wint-conversion]
593 | if ((wl->regsva = ioremap_nocache(dev->base_addr, PCI_BAR0_WINSZ))
== NULL) {
| ^
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c: In
function ‘wl_pci_probe’:
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:780:2:
warning: this ‘if’ clause does not guard... [-Wmisleading-indentation]
780 | if ((val & 0xff00) != 0)
| ^~
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:782:3:
note: ...this statement, but the latter is misleadingly indented as if it were
guarded by the ‘if’
782 | bar1_size = pci_resource_len(pdev, 2);
| ^
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:783:15:
warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
783 | bar1_addr = (uc
[Kernel-packages] [Bug 1910697] Re: incapability with broadcom wifi driver - failed at dkms build
*** This bug is a duplicate of bug 1872908 ***
https://bugs.launchpad.net/bugs/1872908
** This bug is no longer a duplicate of bug 1910555
Driver build error on kernel 5.8, but works on 5.4
** This bug has been marked a duplicate of bug 1872908
bcmwl kernel module does not build with 5.6.0 kernel
--
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/1910697
Title:
incapability with broadcom wifi driver - failed at dkms build
Status in bcmwl package in Ubuntu:
New
Status in linux-signed-hwe-5.8 package in Ubuntu:
New
Bug description:
Linux-5.8-#34
incapability with broadcom wifi driver - failed at dkms build
Logs:
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build# cat make.log
DKMS make.log for bcmwl-6.30.223.271+bdcom for kernel 5.8.0-34-generic
(x86_64)
Friday 08 January 2021 02:46:07 PM IST
make: Entering directory '/usr/src/linux-headers-5.8.0-34-generic'
CFG80211 API is prefered for this kernel version
Using CFG80211 API
AR /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/built-in.a
CC [M] /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.o
CC [M] /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.o
CC [M] /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_iw.o
CC [M]
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.o
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c: In
function ‘osl_reg_map’:
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c:949:10:
error: implicit declaration of function ‘ioremap_nocache’; did you mean
‘ioremap_cache’? [-Werror=implicit-function-declaration]
949 | return (ioremap_nocache((unsigned long)pa, (unsigned long)size));
| ^~~
| ioremap_cache
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c:949:10:
warning: returning ‘int’ from a function with return type ‘void *’ makes
pointer from integer without a cast [-Wint-conversion]
949 | return (ioremap_nocache((unsigned long)pa, (unsigned long)size));
| ~^~~~
cc1: some warnings being treated as errors
make[1]: *** [scripts/Makefile.build:288:
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.o] Error 1
make[1]: *** Waiting for unfinished jobs
In file included from
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:40:
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:
In function ‘wl_set_auth_type’:
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.h:52:5:
warning: this statement may fall through [-Wimplicit-fallthrough=]
52 | if (wl_dbg_level & WL_DBG_DBG) { \
| ^
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:816:3:
note: in expansion of macro ‘WL_DBG’
816 | WL_DBG(("network eap\n"));
| ^~
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:817:2:
note: here
817 | default:
| ^~~
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c: In
function ‘wl_attach’:
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:593:20:
error: implicit declaration of function ‘ioremap_nocache’; did you mean
‘ioremap_cache’? [-Werror=implicit-function-declaration]
593 | if ((wl->regsva = ioremap_nocache(dev->base_addr, PCI_BAR0_WINSZ))
== NULL) {
|^~~
|ioremap_cache
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:593:18:
warning: assignment to ‘void *’ from ‘int’ makes pointer from integer without a
cast [-Wint-conversion]
593 | if ((wl->regsva = ioremap_nocache(dev->base_addr, PCI_BAR0_WINSZ))
== NULL) {
| ^
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c: In
function ‘wl_pci_probe’:
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:780:2:
warning: this ‘if’ clause does not guard... [-Wmisleading-indentation]
780 | if ((val & 0xff00) != 0)
| ^~
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:782:3:
note: ...this statement, but the latter is misleadingly indented as if it were
guarded by the ‘if’
782 | bar1_size = pci_resource_len(pdev, 2);
| ^
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:783:15:
warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
783 | bar1_addr = (uchar *)ioremap_nocache(pci_resource_start(pdev, 2),
| ^
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c: In
function ‘wl_reg_proc_entry’:
/var/lib/dkms/bcmwl/6.30.223.271+bdcom
