[Kernel-packages] [Bug 1917977] Re: Synaptiks touchpad not detected in kernel
I tried to run the command but it said command not available ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete ** Changed in: linux (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1917977 Title: Synaptiks touchpad not detected in kernel Status in linux package in Ubuntu: New Bug description: After using "cat /proc/bus/input/devices" no touchpad shows up same with xinput and other commands. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1917977/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1917977] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1917977 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1917977 Title: Synaptiks touchpad not detected in kernel Status in linux package in Ubuntu: Incomplete Bug description: After using "cat /proc/bus/input/devices" no touchpad shows up same with xinput and other commands. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1917977/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1917977] [NEW] Synaptiks touchpad not detected in kernel
Public bug reported: After using "cat /proc/bus/input/devices" no touchpad shows up same with xinput and other commands. ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Summary changed: - Synaptiks touchpad not detected in kernal + Synaptiks touchpad not detected in kernel -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1917977 Title: Synaptiks touchpad not detected in kernel Status in linux package in Ubuntu: Incomplete Bug description: After using "cat /proc/bus/input/devices" no touchpad shows up same with xinput and other commands. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1917977/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1912673] Re: sounds not working on Dell XPS 17 (9700)
I've checked kernel configs for Arch, Redhat and Debian. And I suspect that only thing is missing to make it work is following kernel config option: CONFIG_SND_SOC_INTEL_SOUNDWIRE_SOF_MACH=m -- 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/1912673 Title: sounds not working on Dell XPS 17 (9700) Status in alsa-ucm-conf package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: My investigation process: Dell XPS 17 (9700) comes with Windows 10 preinstalled, where sounds worked. I installed Ubuntu 20.04 LTS fresh, sounds did not work on speakers or 3.5mm headphones, using linux-image-5.4.0-42-generic, I did not try blutooth. I sudo apt upgrade, dist-upgrade to get kernels linux-image-5.8.0-38-generic linux-image-5.8.0-40-generic Sounds did not work. I download linux-image-unsigned-5.10.9-051009-generic. Sounds did not work. I upgrade Dell XPS 9700 firmware from 1.3 to 1.63. Sounds did not work. After googling I found this solution in the comments: https://askubuntu.com/questions/1270442/no-sound-on-xps-17-9700 """ Download and install dkms module: https://launchpad.net/~canonical-hwe-team/+archive/ubuntu/pc-oem- dkms/+packages Alternatively, you can install linux-oem-20.04, it will install the 5.6 kernel with the above driver. Your system may be more stable with 5.4 kernel since it is in wide use. Manually install sof-firmware from Arch Linux: https://archlinux.pkgs.org/rolling/archlinux-extra-x86_64/sof- firmware-1.5.1-1-any.pkg.tar.zst.html You will need to delete the existing "sof" and "sof-tplg" files from the Ubuntu linux-firmware package first. Note if this package gets updated from Canoncial and they don't update these, you will have to delete and then reextract. Files go into the /usr/lib/firmware/intel/sof and /usr/lib/firmware/intel/sof-tplg folders. Manually install the ucm2 files: http://xps17.ddns.net/sof-soundwire.zip These go into /usr/share/alsa/ucm2/sof-soundwire. Delete the contents of the existing sof-soundwire folder (if you have it) and replace them with the ones from the archive. Reboot. You should now have all your audio devices available. If speakers do not play, you may need to run alsamixer (non-root) from a terminal and unmute and set the mixer levels all the way up. """ This solution worked for me on linux-image-5.6.0-1042-oem AFTER manually opening alsa-mixer and changing soundcard to sof. The sound would otherwise just show 'dummy'. My sounds still do not work on 5.8 or 5.10, full name listed above. I did not get to test this temporary fix with 5.4. my full alsa-info: http://alsa-project.org/db/?f=6a638be0cfbe8ed08a010eb26a7702e324dce5ff based on some google research, this seems to be a common problem: https://www.reddit.com/r/Dell/comments/hj8oxw/xps_17_9700_no_audio_on_linux_also_hardware_is/ https://www.reddit.com/r/Dell/comments/hge2yo/no_audio_on_linux_ubuntu_2004_xps_17_9700_realtek/ https://www.reddit.com/r/Dell/comments/j2kdjw/xps_17_9700_on_linux_audio_issue/ etc... ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.10 ProcVersionSignature: Ubuntu 5.6.0-1042.46-oem 5.6.19 Uname: Linux 5.6.0-1042-oem x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: neoh 1786 F pulseaudio /dev/snd/pcmC1D0p: neoh 1786 F...m pulseaudio /dev/snd/controlC0: neoh 1786 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jan 21 12:08:45 2021 InstallationDate: Installed on 2021-01-20 (1 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/30/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.3 dmi.board.name: 0CXCCY dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.3:bd12/30/2020:svnDellInc.:pnXPS179700:pvr:rvnDellInc.:rn0CXCCY:rvrA03:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 17 9700 dmi.product.sku: 098F dmi.sys.vendor: Dell Inc. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Dependencies: DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-01-20 (1 days ago) InstallationMedia: Ubuntu 20.04.1
[Kernel-packages] [Bug 1910108] Re: computer crashes soon after startup
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- 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/1910108 Title: computer crashes soon after startup Status in linux package in Ubuntu: Expired Bug description: Computer crashes about 30 seconds after logging in and connecting with websites.First the screen goes blank, then the hard drive shuts down, and in about 30 seconds it starts up again requiring a new sign-in. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.29 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Mon Jan 4 09:20:14 2021 InstallationDate: Installed on 2020-06-21 (197 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1910108/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1917829] Re: alsa/hda: the hdmi audio dosn't work on TGL machines
** Changed in: linux (Ubuntu Groovy) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Hirsute) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1917829 Title: alsa/hda: the hdmi audio dosn't work on TGL machines Status in HWE Next: New Status in linux package in Ubuntu: Fix Committed Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.10 source package in Focal: Fix Committed Status in linux source package in Groovy: Fix Committed Status in linux source package in Hirsute: Fix Committed Bug description: [Impact] On the TGL machines, we plug a dp mst hub to the thunderbolt port, and plug a hdmi/dp monitor to the dp mst hub, then check the gnome-sound-setting, could not find the hdmi/dp audio device. [Fix] backport a patch from upstream, this patch change to assign the pcm slot dynamically on TGL macines. [Test] On 2 lenovo and dell TGL machines, plug dp mst hub and plug 2 monitors to the hub or to the machine hdmi/dp ports, check the gnome-sound-setting, there are 2 hdmi/dp audio devices. and they all could output sound. [Where problems could occur] After this change, the hdmi audio device number starts from 0, 1, ..., while without this change, the hdmi audio device number is fix mapped, it could be 3 or 5 directly. So if there is some userspace applications depends on the fix mapped hdmi audio device, these applicatons could not work on TGL machines. So far, we don't know if those applications exists or not, but I could confirm the ubuntu audio stack builds on the alsa-lib and pulseaudio, this change will not affect the applications based on the alsa-lib and pulseaudio. And I already tested audio functions under ubuntu on the TGL machines, there is no regression. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1917829/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1917964] Re: Groovy update: upstream stable patchset 2021-03-05
** Changed in: linux (Ubuntu Groovy) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1917964 Title: Groovy update: upstream stable patchset 2021-03-05 Status in linux package in Ubuntu: Invalid Status in linux source package in Groovy: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2021-03-05 Ported from the following upstream stable releases: v5.4.93, v5.10.11 from git://git.kernel.org/ mtd: rawnand: gpmi: fix dst bit offset when extracting raw payload i2c: bpmp-tegra: Ignore unknown I2C_M flags platform/x86: i2c-multi-instantiate: Don't create platform device for INT3515 ACPI nodes platform/x86: ideapad-laptop: Disable touchpad_switch for ELAN0634 ALSA: seq: oss: Fix missing error check in snd_seq_oss_synth_make_info() ALSA: hda/realtek - Limit int mic boost on Acer Aspire E5-575T ALSA: hda/via: Add minimum mute flag dm crypt: fix copy and paste bug in crypt_alloc_req_aead ACPI: scan: Make acpi_bus_get_device() clear return pointer on error btrfs: don't get an EINTR during drop_snapshot for reloc btrfs: do not double free backref nodes on error btrfs: fix lockdep splat in btrfs_recover_relocation btrfs: don't clear ret in btrfs_start_dirty_block_groups btrfs: send: fix invalid clone operations when cloning from the same file and root writeback: Drop I_DIRTY_TIME_EXPIRE fs: fix lazytime expiration handling in __writeback_single_inode() pinctrl: ingenic: Fix JZ4760 support mmc: core: don't initialize block size from ext_csd if not present mmc: sdhci-of-dwcmshc: fix rpmb access mmc: sdhci-xenon: fix 1.8v regulator stabilization mmc: sdhci-brcmstb: Fix mmc timeout errors on S5 suspend dm: avoid filesystem lookup in dm_get_dev_t() dm integrity: fix a crash if "recalculate" used without "internal_hash" dm integrity: conditionally disable "recalculate" feature drm/atomic: put state on error path drm/syncobj: Fix use-after-free drm/amdgpu: remove gpu info firmware of green sardine drm/amd/display: DCN2X Find Secondary Pipe properly in MPO + ODM Case drm/i915/gt: Prevent use of engine->wa_ctx after error ASoC: Intel: haswell: Add missing pm_ops ASoC: rt711: mutex between calibration and power state changes SUNRPC: Handle TCP socket sends with kernel_sendpage() again HID: sony: select CONFIG_CRC32 dm integrity: select CRYPTO_SKCIPHER scsi: ufs: Correct the LUN used in eh_device_reset_handler() callback scsi: qedi: Correct max length of CHAP secret scsi: scsi_debug: Fix memleak in scsi_debug_init() scsi: sd: Suppress spurious errors when WRITE SAME is being disabled riscv: Fix kernel time_init() riscv: Fix sifive serial driver riscv: Enable interrupts during syscalls with M-Mode HID: logitech-dj: add the G602 receiver HID: Ignore battery for Elan touchscreen on ASUS UX550 clk: tegra30: Add hda clock default rates to clock driver ALSA: hda/tegra: fix tegra-hda on tegra30 soc arm64: make atomic helpers __always_inline xen: Fix event channel callback via INTX/GSI x86/xen: Add xen_no_vector_callback option to test PCI INTX delivery dts: phy: fix missing mdio device and probe failure of vsc8541-01 device riscv: defconfig: enable gpio support for HiFive Unleashed drm/amdgpu/psp: fix psp gfx ctrl cmds drm/amd/display: disable dcn10 pipe split by default HID: logitech-hidpp: Add product ID for MX Ergo in Bluetooth mode drm/amd/display: Fix to be able to stop crc calculation drm/nouveau/bios: fix issue shadowing expansion ROMs drm/nouveau/privring: ack interrupts the same way as RM drm/nouveau/i2c/gm200: increase width of aux semaphore owner fields drm/nouveau/mmu: fix vram heap sizing drm/nouveau/kms/nv50-: fix case where notifier buffer is at offset 0 io_uring: flush timeouts that should already have expired libperf tests: If a test fails return non-zero libperf tests: Fail when failing to get a tracepoint id RISC-V: Set current memblock limit RISC-V: Fix maximum allowed phsyical memory for RV32 pinctrl: aspeed: g6: Fix PWMG0 pinctrl setting pinctrl: mediatek: Fix fallback call path scsi: megaraid_sas: Fix MEGASAS_IOC_FIRMWARE regression scsi: ufs: ufshcd-pltfrm depends on HAS_IOMEM crypto: omap-sham - Fix link error without crypto-engine powerpc: Use the common INIT_DATA_SECTION macro in
[Kernel-packages] [Bug 1917609] Re: [Regression] ubuntu_bpf failed to build on Groovy
** Changed in: linux (Ubuntu Groovy) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1917609 Title: [Regression] ubuntu_bpf failed to build on Groovy Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Invalid Status in linux source package in Groovy: Fix Committed Bug description: [Impact] Upstream commit d3bec0138bfbe58606fc1d6f57a4cdc1a20218db (bpf: Zero-fill re-used per-cpu map element) was applied to Groovy as part of an upstream stable update. This patch fixes a bpf issue and at the same time adds new selftests to verify these changes. However, the selftests can't be compiled on 5.8 due to missing helper functions that were added only later. The bpf selftest build fails with errors such as: /usr/bin/ld: /tmp/autopkgtest.IzBxE1/build.8NX/src/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/bpf/map_init.test.o: in function `prog_run_insert_elem': /tmp/autopkgtest.IzBxE1/build.8NX/src/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/bpf/prog_tests/map_init.c:89: undefined reference to `ASSERT_OK' [Fix] The proposed fix it to partially revert this commit by removing the selftests parts. [Testcase] On a groovy/linux repo: $ make -C tools/testing/selftests TARGETS=bpf SKIP_TARGETS= [Where problems could occur] By removing the selftests we could be introducing a regression with the bpf code change which would be likely unoticed during the tests. Original Description Issue found on 5.8.0-1024.26-azure / 5.8.0-1022.23-oracle Test failed to build, I didn't see any meaningful error message, this might need to be double checked. HDRINST usr/include/asm/fcntl.h HDRINST usr/include/asm/termbits.h HDRINST usr/include/asm/errno.h INSTALL ./usr/include make[1]: Leaving directory '/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux' make: Leaving directory '/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests' stderr: make: *** [Makefile:159: all] Error 1 Please find attachment for the complete test log. == Process to reproduce this == 1. git clone git://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/groovy 2. cd groovy/tools/testing/selftests 3. make TARGETS=bpf You will see the build failed if it's affected by this. I think this is affecting the ubuntu_kernel_selftests as well, as the net test would require the bpf test to be built first. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1917609/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1917964] [NEW] Groovy update: upstream stable patchset 2021-03-05
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2021-03-05 Ported from the following upstream stable releases: v5.4.93, v5.10.11 from git://git.kernel.org/ mtd: rawnand: gpmi: fix dst bit offset when extracting raw payload i2c: bpmp-tegra: Ignore unknown I2C_M flags platform/x86: i2c-multi-instantiate: Don't create platform device for INT3515 ACPI nodes platform/x86: ideapad-laptop: Disable touchpad_switch for ELAN0634 ALSA: seq: oss: Fix missing error check in snd_seq_oss_synth_make_info() ALSA: hda/realtek - Limit int mic boost on Acer Aspire E5-575T ALSA: hda/via: Add minimum mute flag dm crypt: fix copy and paste bug in crypt_alloc_req_aead ACPI: scan: Make acpi_bus_get_device() clear return pointer on error btrfs: don't get an EINTR during drop_snapshot for reloc btrfs: do not double free backref nodes on error btrfs: fix lockdep splat in btrfs_recover_relocation btrfs: don't clear ret in btrfs_start_dirty_block_groups btrfs: send: fix invalid clone operations when cloning from the same file and root writeback: Drop I_DIRTY_TIME_EXPIRE fs: fix lazytime expiration handling in __writeback_single_inode() pinctrl: ingenic: Fix JZ4760 support mmc: core: don't initialize block size from ext_csd if not present mmc: sdhci-of-dwcmshc: fix rpmb access mmc: sdhci-xenon: fix 1.8v regulator stabilization mmc: sdhci-brcmstb: Fix mmc timeout errors on S5 suspend dm: avoid filesystem lookup in dm_get_dev_t() dm integrity: fix a crash if "recalculate" used without "internal_hash" dm integrity: conditionally disable "recalculate" feature drm/atomic: put state on error path drm/syncobj: Fix use-after-free drm/amdgpu: remove gpu info firmware of green sardine drm/amd/display: DCN2X Find Secondary Pipe properly in MPO + ODM Case drm/i915/gt: Prevent use of engine->wa_ctx after error ASoC: Intel: haswell: Add missing pm_ops ASoC: rt711: mutex between calibration and power state changes SUNRPC: Handle TCP socket sends with kernel_sendpage() again HID: sony: select CONFIG_CRC32 dm integrity: select CRYPTO_SKCIPHER scsi: ufs: Correct the LUN used in eh_device_reset_handler() callback scsi: qedi: Correct max length of CHAP secret scsi: scsi_debug: Fix memleak in scsi_debug_init() scsi: sd: Suppress spurious errors when WRITE SAME is being disabled riscv: Fix kernel time_init() riscv: Fix sifive serial driver riscv: Enable interrupts during syscalls with M-Mode HID: logitech-dj: add the G602 receiver HID: Ignore battery for Elan touchscreen on ASUS UX550 clk: tegra30: Add hda clock default rates to clock driver ALSA: hda/tegra: fix tegra-hda on tegra30 soc arm64: make atomic helpers __always_inline xen: Fix event channel callback via INTX/GSI x86/xen: Add xen_no_vector_callback option to test PCI INTX delivery dts: phy: fix missing mdio device and probe failure of vsc8541-01 device riscv: defconfig: enable gpio support for HiFive Unleashed drm/amdgpu/psp: fix psp gfx ctrl cmds drm/amd/display: disable dcn10 pipe split by default HID: logitech-hidpp: Add product ID for MX Ergo in Bluetooth mode drm/amd/display: Fix to be able to stop crc calculation drm/nouveau/bios: fix issue shadowing expansion ROMs drm/nouveau/privring: ack interrupts the same way as RM drm/nouveau/i2c/gm200: increase width of aux semaphore owner fields drm/nouveau/mmu: fix vram heap sizing drm/nouveau/kms/nv50-: fix case where notifier buffer is at offset 0 io_uring: flush timeouts that should already have expired libperf tests: If a test fails return non-zero libperf tests: Fail when failing to get a tracepoint id RISC-V: Set current memblock limit RISC-V: Fix maximum allowed phsyical memory for RV32 pinctrl: aspeed: g6: Fix PWMG0 pinctrl setting pinctrl: mediatek: Fix fallback call path scsi: megaraid_sas: Fix MEGASAS_IOC_FIRMWARE regression scsi: ufs: ufshcd-pltfrm depends on HAS_IOMEM crypto: omap-sham - Fix link error without crypto-engine powerpc: Use the common INIT_DATA_SECTION macro in vmlinux.lds.S powerpc: Fix alignment bug within the init sections arm64: entry: remove redundant IRQ flag tracing drm/amdkfd: Fix out-of-bounds read in kdf_create_vcrat_image_cpu() i2c: octeon: check correct size of maximum RECV_LEN packet platform/x86: intel-vbtn: Drop HP Stream x360 Convertible PC 11 from allow-list platform/x86: hp-wmi: Don't log a warning on HPWMI_RET_UNKNOWN_COMMAND errors gpio: sifive: select IRQ_DOMAIN_HIERARCHY rather than depend on it selftests: net: fib_tests: remove duplicate log test can: dev: can_restart: fix use after free bug can: vxcan:
[Kernel-packages] [Bug 1917958] Re: Latest linux-generic package (kernel 4.15.0-136) doesn't work on HyperV Gen2 VM
Unable to run apport-collect 1917958 since the VM will not boot when selecting kernel 4.5.0-136. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1917958 Title: Latest linux-generic package (kernel 4.15.0-136) doesn't work on HyperV Gen2 VM Status in linux package in Ubuntu: Confirmed Bug description: On Ubuntu 18.04 LTS 1&2 (so far tested), either when deploying a new VM (which pulls the latest linux-generic) or rebooting a VM (which updated the linux-generic under the cover which installs 4.15.0-136) will prevent the VM to boot. After reboot, will get stuck on /dev/sdX: clean, x / y files, k / m blocks. Using grub, selecting an older kernel, allow the VM to book without any issues. I manually installed kernel 4.15.0-135, however the issue doesn't repro. Finally I've verified that this repro on both Server 2016 and Server 2019 versions of Windows... Output of /proc/version_signature (both on Server 2016/2019) Ubuntu 4.15.0-29.31-generic 4.15.18 lspci -vnvn reported empty on this VM. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1917958/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1917958] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1917958 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1917958 Title: Latest linux-generic package (kernel 4.15.0-136) doesn't work on HyperV Gen2 VM Status in linux package in Ubuntu: Incomplete Bug description: On Ubuntu 18.04 LTS 1&2 (so far tested), either when deploying a new VM (which pulls the latest linux-generic) or rebooting a VM (which updated the linux-generic under the cover which installs 4.15.0-136) will prevent the VM to boot. After reboot, will get stuck on /dev/sdX: clean, x / y files, k / m blocks. Using grub, selecting an older kernel, allow the VM to book without any issues. I manually installed kernel 4.15.0-135, however the issue doesn't repro. Finally I've verified that this repro on both Server 2016 and Server 2019 versions of Windows... Output of /proc/version_signature (both on Server 2016/2019) Ubuntu 4.15.0-29.31-generic 4.15.18 lspci -vnvn reported empty on this VM. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1917958/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1917958] [NEW] Latest linux-generic package (kernel 4.15.0-136) doesn't work on HyperV Gen2 VM
Public bug reported: On Ubuntu 18.04 LTS 1&2 (so far tested), either when deploying a new VM (which pulls the latest linux-generic) or rebooting a VM (which updated the linux-generic under the cover which installs 4.15.0-136) will prevent the VM to boot. After reboot, will get stuck on /dev/sdX: clean, x / y files, k / m blocks. Using grub, selecting an older kernel, allow the VM to book without any issues. I manually installed kernel 4.15.0-135, however the issue doesn't repro. Finally I've verified that this repro on both Server 2016 and Server 2019 versions of Windows... Output of /proc/version_signature (both on Server 2016/2019) Ubuntu 4.15.0-29.31-generic 4.15.18 lspci -vnvn reported empty on this VM. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Attachment added: "output.png" https://bugs.launchpad.net/bugs/1917958/+attachment/5473666/+files/output.png -- 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/1917958 Title: Latest linux-generic package (kernel 4.15.0-136) doesn't work on HyperV Gen2 VM Status in linux package in Ubuntu: New Bug description: On Ubuntu 18.04 LTS 1&2 (so far tested), either when deploying a new VM (which pulls the latest linux-generic) or rebooting a VM (which updated the linux-generic under the cover which installs 4.15.0-136) will prevent the VM to boot. After reboot, will get stuck on /dev/sdX: clean, x / y files, k / m blocks. Using grub, selecting an older kernel, allow the VM to book without any issues. I manually installed kernel 4.15.0-135, however the issue doesn't repro. Finally I've verified that this repro on both Server 2016 and Server 2019 versions of Windows... Output of /proc/version_signature (both on Server 2016/2019) Ubuntu 4.15.0-29.31-generic 4.15.18 lspci -vnvn reported empty on this VM. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1917958/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1917937] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1917937 Title: Ubuntu and Keyboard are not working fine Status in linux package in Ubuntu: Confirmed Bug description: I am using a Dell keyboard+mouse They are lagging. I've changed batteries, and the batteries are brand new, but the problem still persists. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-44-generic 5.8.0-44.50 ProcVersionSignature: Ubuntu 5.8.0-44.50-generic 5.8.18 Uname: Linux 5.8.0-44-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: lheck 8634 F pulseaudio /dev/snd/controlC1: lheck 8634 F pulseaudio /dev/snd/controlC0: lheck 8634 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Mar 5 16:11:25 2021 MachineType: Dell Inc. XPS 15 9500 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-44-generic root=UUID=1e58da87-741f-42cd-99f1-f9e33ba23d40 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-44-generic N/A linux-backports-modules-5.8.0-44-generic N/A linux-firmware1.190.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/24/2020 dmi.bios.release: 1.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.1 dmi.board.name: 05XYW7 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.1:bd12/24/2020:br1.6:svnDellInc.:pnXPS159500:pvr:rvnDellInc.:rn05XYW7:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9500 dmi.product.sku: 097D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1917937/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1831568] Re: [realtime app] disable idle load balancing on cpus from nohz_full= cpuset
This patch appears to alter the default behavior of a stable kernel in that it essentially disables idle load balancing. Is that a fair assessment ? ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1831568 Title: [realtime app] disable idle load balancing on cpus from nohz_full= cpuset Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: New Bug description: We're running realtime application on Ubuntu 16.04 with linux-image 4.15 and found that from time to time we get jitter caused by idle load balancing. I'm providing here a patch which solved the issue for us. The realtime application is bound to isolated CPUs (one thread per CPU, nohz_full= in kernel cmdline, all IRQs moved to housekeeping CPUs), application doesn't use any linux kernel syscalls except in startup phase so we don't expect any interruptions of the application from the kernel or HW. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1831568/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1902156] Re: [ASUS VivoBook X541UJ] Keyboard and touchpad don't work on kernel 5.8.0.29, but 5.4 or 5.8.16 work
I am having these issues with new batteries and all. Linux mars 5.8.0-44-generic #50-Ubuntu SMP Tue Feb 9 06:29:41 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Laptop is Dell XPS 15 9500 -- 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/1902156 Title: [ASUS VivoBook X541UJ] Keyboard and touchpad don't work on kernel 5.8.0.29, but 5.4 or 5.8.16 work Status in linux package in Ubuntu: Fix Released Bug description: when I updated my system to ubuntu 20.10, the keyboard and mouse no longer worked after a little investigation, I found out the kernel causes this problem, downgrading to linux 5.4 or upgrading to linux kernel 5.8.11 solved this issue, I also found that this problem is present on other ASUS laptop models ( my laptop is ASUS) so you may want to investigate this issue to update your default 20.10 Linux kernel. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: joseph 1979 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2019-06-03 (515 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: ASUSTeK COMPUTER INC. X541UJ Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-26-generic root=UUID=1298f5d0-e6c0-4aa3-9c5a-fbe0ebf0fc02 ro quiet splash pci=noaer mds=full,nosmt vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 RelatedPackageVersions: linux-restricted-modules-5.8.0-26-generic N/A linux-backports-modules-5.8.0-26-generic N/A linux-firmware1.190 Tags: groovy Uname: Linux 5.8.0-26-generic x86_64 UpgradeStatus: Upgraded to groovy on 2020-10-24 (5 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/18/2019 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X541UJ.310 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X541UJ dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX541UJ.310:bd04/18/2019:br5.12:svnASUSTeKCOMPUTERINC.:pnX541UJ:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX541UJ:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: VivoBook dmi.product.name: X541UJ dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1902156/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1831566] Re: [realtime app] not possible to redirect drivers/nvme IRQs from realtime cpuset
These patch sets are quite invasive for a stable kernel. It looks like the default behavior is untouched if cq_cpumask is zero. However, I would like to see some discussion with upstream as to the efficacy of IRQ affinity with this device. Mykyta - can you develop and send a patch for current upstream review ? ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1831566 Title: [realtime app] not possible to redirect drivers/nvme IRQs from realtime cpuset Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: New Bug description: We're running realtime application on Ubuntu 16.04 with linux-image 4.15 and found it impossible to get rid of jitter introduced by Intel NVMe IRQs. I'm providing here a patch which solved the issue for us. The realtime application is bound to isolated CPUs (one thread per CPU, nohz_full= in kernel cmdline, all IRQs moved to housekeeping CPUs), application doesn't use any linux kernel syscalls except in startup phase so we don't expect any interruptions of the application from the kernel or HW. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1831566/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1917937] [NEW] Ubuntu and Keyboard are not working fine
Public bug reported: I am using a Dell keyboard+mouse They are lagging. I've changed batteries, and the batteries are brand new, but the problem still persists. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-44-generic 5.8.0-44.50 ProcVersionSignature: Ubuntu 5.8.0-44.50-generic 5.8.18 Uname: Linux 5.8.0-44-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: lheck 8634 F pulseaudio /dev/snd/controlC1: lheck 8634 F pulseaudio /dev/snd/controlC0: lheck 8634 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Mar 5 16:11:25 2021 MachineType: Dell Inc. XPS 15 9500 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-44-generic root=UUID=1e58da87-741f-42cd-99f1-f9e33ba23d40 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-44-generic N/A linux-backports-modules-5.8.0-44-generic N/A linux-firmware1.190.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/24/2020 dmi.bios.release: 1.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.1 dmi.board.name: 05XYW7 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.1:bd12/24/2020:br1.6:svnDellInc.:pnXPS159500:pvr:rvnDellInc.:rn05XYW7:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9500 dmi.product.sku: 097D dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy -- 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/1917937 Title: Ubuntu and Keyboard are not working fine Status in linux package in Ubuntu: New Bug description: I am using a Dell keyboard+mouse They are lagging. I've changed batteries, and the batteries are brand new, but the problem still persists. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-44-generic 5.8.0-44.50 ProcVersionSignature: Ubuntu 5.8.0-44.50-generic 5.8.18 Uname: Linux 5.8.0-44-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: lheck 8634 F pulseaudio /dev/snd/controlC1: lheck 8634 F pulseaudio /dev/snd/controlC0: lheck 8634 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Mar 5 16:11:25 2021 MachineType: Dell Inc. XPS 15 9500 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-44-generic root=UUID=1e58da87-741f-42cd-99f1-f9e33ba23d40 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-44-generic N/A linux-backports-modules-5.8.0-44-generic N/A linux-firmware1.190.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/24/2020 dmi.bios.release: 1.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.1 dmi.board.name: 05XYW7 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.1:bd12/24/2020:br1.6:svnDellInc.:pnXPS159500:pvr:rvnDellInc.:rn05XYW7:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9500 dmi.product.sku: 097D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1917937/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1871794] Re: [Bluetooth] No audio output/input in HSP/HFP mode
I have the same issue with the headphone's microphone. My Bose 700 connects and has sound output for A2DP, but terrible audio quality (HSP/HFP) when switching on headphone's microphone. Laptop: Acer Predator G9 591 2016 OS: Ubuntu 20.04.01 LTS Kernel: 5.4.0-66-generic Headset: Bose 700 -- 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/1871794 Title: [Bluetooth] No audio output/input in HSP/HFP mode Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: I'm testing with Sony bluetooth headset SBH20, works fine in A2DP profile, but I can't get audio input and output work in HSP/HFP profile. [Reproduce steps] 1. Scan and pair BT headset in Bluetooth setting 2. Switch to HSP/HFP profile in Sound setting 3. Test sound output/input [Machine information] ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1359 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Apr 9 16:26:52 2020 InstallationDate: Installed on 2020-04-09 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) SourcePackage: pulseaudio Symptom: audio Symptom_Card: SBH20 Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1359 F pulseaudio Symptom_Type: No sound at all Title: [SBH20, recording] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/17/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.13 dmi.board.name: 0188D1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.13:bd09/17/2019:svnDellInc.:pnXPS1373902-in-1:pvr:rvnDellInc.:rn0188D1:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 7390 2-in-1 dmi.product.sku: 08B0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1871794/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1917918] Re: Add FUA support for XFS
Patches submitted: https://lists.ubuntu.com/archives/kernel- team/2021-March/117799.html ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Tim Gardner (timg-tpi) ** Changed in: linux (Ubuntu Bionic) Status: Incomplete => In Progress ** Changed in: linux (Ubuntu Bionic) Importance: Undecided => Medium ** Summary changed: - Add FUA support for XFS + SRU: Add FUA support for XFS ** Description changed: + SRU justification: + [Impact] This 4 patch set adds backported support for Forced Unit Access (FUA) on XFS file systems to the 18.04 (Bionic) GA (4.15) kernel. FUA on XFS was added upstream in 4.18. FUA on XFS is important for SQL server work loads. [Test Plan] SQLIOSIM (a package from Microsoft) was used to test performance improvements. Tests were run with an XFS file system mounted on a persistent memory block device (PMEM) partition. Performance metrics were found to exhibit satisfactory improvement gains from the GA kernel. [Where problems could occur] Well, these are patches to file system code. They _could_ cause widespread corruption. However, multiple test passes with sqliosim exhibited no issues. [Other Info] - - See attached sqliosim.cfg.ini configuration file for test run parameters. + + See attached sqliosim.cfg.ini configuration file for test run + parameters. -- 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/1917918 Title: SRU: Add FUA support for XFS Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: In Progress Bug description: SRU justification: [Impact] This 4 patch set adds backported support for Forced Unit Access (FUA) on XFS file systems to the 18.04 (Bionic) GA (4.15) kernel. FUA on XFS was added upstream in 4.18. FUA on XFS is important for SQL server work loads. [Test Plan] SQLIOSIM (a package from Microsoft) was used to test performance improvements. Tests were run with an XFS file system mounted on a persistent memory block device (PMEM) partition. Performance metrics were found to exhibit satisfactory improvement gains from the GA kernel. [Where problems could occur] Well, these are patches to file system code. They _could_ cause widespread corruption. However, multiple test passes with sqliosim exhibited no issues. [Other Info] See attached sqliosim.cfg.ini configuration file for test run parameters. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1917918/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1915935] Please test proposed package
Hello Alberto, or anyone else affected, Accepted nvidia-graphics-drivers-390 into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source /nvidia-graphics-drivers-390/390.141-0ubuntu0.18.04.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-450 in Ubuntu. https://bugs.launchpad.net/bugs/1915935 Title: Switching between NVIDIA drivers fails Status in nvidia-graphics-drivers-418-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-450 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-450-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-460 package in Ubuntu: In Progress Status in nvidia-graphics-drivers-460-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-418-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-450 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-460 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-450 source package in Focal: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-460 source package in Focal: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Groovy: Fix Committed Status in nvidia-graphics-drivers-450 source package in Groovy: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Groovy: Fix Committed Status in nvidia-graphics-drivers-460 source package in Groovy: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Groovy: Fix Committed Bug description: Trying to install nvidia-driver-450-server over nvidia-driver-450 triggers the following error: Unpacking libnvidia-common-450-server (450.102.04-0ubuntu0.20.04.1) ... dpkg: error processing archive /tmp/apt-dpkg-install-e75h80/01-libnvidia-common- 450-server_450.102.04-0ubuntu0.20.04.1_all.deb (--unpack): trying to overwrite '/usr/share/nvidia/nvidia-application-profiles-450.102.04-k ey-documentation', which is also in package libnvidia-common-450 450.102.04-0ubu ntu0.20.04.1 ... Unpacking nvidia-driver-450-server (450.102.04-0ubuntu0.20.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-418-server/+bug/1915935/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1916908] Re: Update the 460 driver, make switching between driver series more robust, and add support for Linux 5.11
Hello Alberto, or anyone else affected, Accepted nvidia-graphics-drivers-390 into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source /nvidia-graphics-drivers-390/390.141-0ubuntu0.18.04.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: nvidia-graphics-drivers-390 (Ubuntu Bionic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu. https://bugs.launchpad.net/bugs/1916908 Title: Update the 460 driver, make switching between driver series more robust, and add support for Linux 5.11 Status in linux package in Ubuntu: In Progress Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-418-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-450 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-450-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-460 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-460-server package in Ubuntu: Fix Released Status in linux source package in Bionic: In Progress Status in nvidia-graphics-drivers-390 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-450 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-460 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Bionic: Fix Committed Status in linux source package in Focal: In Progress Status in nvidia-graphics-drivers-390 source package in Focal: In Progress Status in nvidia-graphics-drivers-418-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-450 source package in Focal: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-460 source package in Focal: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Focal: Fix Committed Status in linux source package in Groovy: In Progress Status in nvidia-graphics-drivers-390 source package in Groovy: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Groovy: Fix Committed Status in nvidia-graphics-drivers-450 source package in Groovy: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Groovy: Fix Committed Status in nvidia-graphics-drivers-460 source package in Groovy: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Groovy: Fix Committed Bug description: Update the 460 driver, make switching between driver series more robust (LP: #1915935), and add support for Linux 5.11 [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our users have access to these improvements. See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. nVidia maintainers team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned system level tests are attached to this bug. [Discussion] [Changelog] == 460 == * New upstream release (LP: #1916908): - Added support
[Kernel-packages] [Bug 1915003] Please test proposed package
Hello Alberto, or anyone else affected, Accepted nvidia-settings into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/nvidia- settings/460.39-0ubuntu0.18.04.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/1915003 Title: SRU: Always update the initramfs when changing power profile Status in NVIDIA Drivers Ubuntu: New Status in OEM Priority Project: Triaged Status in nvidia-prime package in Ubuntu: Fix Released Status in nvidia-settings package in Ubuntu: Fix Released Status in nvidia-prime source package in Bionic: Fix Committed Status in nvidia-settings source package in Bionic: Fix Committed Status in nvidia-prime source package in Focal: Fix Released Status in nvidia-settings source package in Focal: Fix Released Status in nvidia-prime source package in Groovy: Fix Released Status in nvidia-settings source package in Groovy: Fix Released Bug description: Since we introduced support for dynamic power management, on systems with hybrid graphics (LP: #1904583), the need to load drivers with different options has become more evident. We need to make sure that the files in the initramfs are in sync with the current user selection. This is also a chance to update the old nvidia-settings release in the archive. [Impact] * If the modules list is not in sync with the selected power profile, users may experience a black screen or increased power consumption. * Updating the initramfs can take a few seconds, and we need to provide users with some form of visual feedback. [Fix] * The prime-select tool shoud update the initramfs when switching between power profiles, and provide visual feedback. * The nvidia-settings panel should provide a progress dialog, since profile switching would otherwise freeze the UI until update-initramfs completes. [Test Case] Make sure a supported nvidia driver is installed (450, 460), then install nvidia-prime and nvidia-settings from proposed, and check the following: 1) prime-select query (to check your current profile) 2) sudo prime-select on-demand (or "intel", or "nvidia", depending on your current power profile) 3) Check that the operation completes successfully. 4) Reboot your system 5) Launch the nvidia-setting panel. 6) Select a different profile from the PRIME tab, and check that a progress dialog is correctly displayed. 7) Close the nvidia-settings panel, and reboot. [Regression Risk] Medium, while the changes in prime-select are trivial, nvidia-settings needs careful testing. To manage notifications about this bug go to: https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/1915003/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1890641] Re: Possible missing firmware /lib/firmware/rtl_nic/rtl8125a-3.fw for module r8169
Hello akchhay, or anyone else affected,
Accepted linux-firmware into bionic-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/linux-
firmware/1.173.20 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed. Your feedback will aid us getting this
update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
bionic to verification-done-bionic. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-bionic. In either case, without details of your testing we will
not be able to proceed.
Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance for helping!
N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.
** Changed in: linux-firmware (Ubuntu Bionic)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-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:
Invalid
Status in linux-firmware source package in Bionic:
Fix Committed
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 1917918] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1917918 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Changed in: linux (Ubuntu Bionic) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1917918 Title: Add FUA support for XFS Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Bug description: [Impact] This 4 patch set adds backported support for Forced Unit Access (FUA) on XFS file systems to the 18.04 (Bionic) GA (4.15) kernel. FUA on XFS was added upstream in 4.18. FUA on XFS is important for SQL server work loads. [Test Plan] SQLIOSIM (a package from Microsoft) was used to test performance improvements. Tests were run with an XFS file system mounted on a persistent memory block device (PMEM) partition. Performance metrics were found to exhibit satisfactory improvement gains from the GA kernel. [Where problems could occur] Well, these are patches to file system code. They _could_ cause widespread corruption. However, multiple test passes with sqliosim exhibited no issues. [Other Info] See attached sqliosim.cfg.ini configuration file for test run parameters. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1917918/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1917918] Re: Add FUA support for XFS
sqliosim configuration file ** Attachment added: "sqliosim.cfg.ini" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1917918/+attachment/5473384/+files/sqliosim.cfg.ini ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1917918 Title: Add FUA support for XFS Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Bug description: [Impact] This 4 patch set adds backported support for Forced Unit Access (FUA) on XFS file systems to the 18.04 (Bionic) GA (4.15) kernel. FUA on XFS was added upstream in 4.18. FUA on XFS is important for SQL server work loads. [Test Plan] SQLIOSIM (a package from Microsoft) was used to test performance improvements. Tests were run with an XFS file system mounted on a persistent memory block device (PMEM) partition. Performance metrics were found to exhibit satisfactory improvement gains from the GA kernel. [Where problems could occur] Well, these are patches to file system code. They _could_ cause widespread corruption. However, multiple test passes with sqliosim exhibited no issues. [Other Info] See attached sqliosim.cfg.ini configuration file for test run parameters. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1917918/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1917918] [NEW] Add FUA support for XFS
Public bug reported: [Impact] This 4 patch set adds backported support for Forced Unit Access (FUA) on XFS file systems to the 18.04 (Bionic) GA (4.15) kernel. FUA on XFS was added upstream in 4.18. FUA on XFS is important for SQL server work loads. [Test Plan] SQLIOSIM (a package from Microsoft) was used to test performance improvements. Tests were run with an XFS file system mounted on a persistent memory block device (PMEM) partition. Performance metrics were found to exhibit satisfactory improvement gains from the GA kernel. [Where problems could occur] Well, these are patches to file system code. They _could_ cause widespread corruption. However, multiple test passes with sqliosim exhibited no issues. [Other Info] See attached sqliosim.cfg.ini configuration file for test run parameters. ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Affects: linux (Ubuntu Bionic) Importance: Undecided Status: Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1917918 Title: Add FUA support for XFS Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Bug description: [Impact] This 4 patch set adds backported support for Forced Unit Access (FUA) on XFS file systems to the 18.04 (Bionic) GA (4.15) kernel. FUA on XFS was added upstream in 4.18. FUA on XFS is important for SQL server work loads. [Test Plan] SQLIOSIM (a package from Microsoft) was used to test performance improvements. Tests were run with an XFS file system mounted on a persistent memory block device (PMEM) partition. Performance metrics were found to exhibit satisfactory improvement gains from the GA kernel. [Where problems could occur] Well, these are patches to file system code. They _could_ cause widespread corruption. However, multiple test passes with sqliosim exhibited no issues. [Other Info] See attached sqliosim.cfg.ini configuration file for test run parameters. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1917918/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1916731] Re: [SRU][F/H] add AMD GPU green sardine firmware
** Tags added: verification-needed-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/1916731 Title: [SRU][F/H] add AMD GPU green sardine firmware Status in HWE Next: New Status in linux-firmware package in Ubuntu: New Status in linux-firmware source package in Focal: Fix Committed Status in linux-firmware source package in Hirsute: New Bug description: SRU justification: [Impact] AMD new gpu can not work without proper firmware. [Fix] Add new firmwares of AMD GPU green sardine. Firmware files are needed by amdgpu in Ubuntu kernel 5.10+ to support new hardware. [Test] Verified on hardware with 5.10 kernel. no errors after benchmark and stress test. [Where problems could occur] Introducs the new firmware to enable support on new GPU. GFX can be failed if it is wrong. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1916731/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1915935] Re: Switching between NVIDIA drivers fails
ok, I have removed the leftover lines from the git merge, and re- uploaded nvidia-graphics-drivers-390 for bionic. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-450 in Ubuntu. https://bugs.launchpad.net/bugs/1915935 Title: Switching between NVIDIA drivers fails Status in nvidia-graphics-drivers-418-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-450 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-450-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-460 package in Ubuntu: In Progress Status in nvidia-graphics-drivers-460-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-418-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-450 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-460 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-450 source package in Focal: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-460 source package in Focal: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Groovy: Fix Committed Status in nvidia-graphics-drivers-450 source package in Groovy: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Groovy: Fix Committed Status in nvidia-graphics-drivers-460 source package in Groovy: Fix Committed Status in nvidia-graphics-drivers-460-server source package in Groovy: Fix Committed Bug description: Trying to install nvidia-driver-450-server over nvidia-driver-450 triggers the following error: Unpacking libnvidia-common-450-server (450.102.04-0ubuntu0.20.04.1) ... dpkg: error processing archive /tmp/apt-dpkg-install-e75h80/01-libnvidia-common- 450-server_450.102.04-0ubuntu0.20.04.1_all.deb (--unpack): trying to overwrite '/usr/share/nvidia/nvidia-application-profiles-450.102.04-k ey-documentation', which is also in package libnvidia-common-450 450.102.04-0ubu ntu0.20.04.1 ... Unpacking nvidia-driver-450-server (450.102.04-0ubuntu0.20.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-418-server/+bug/1915935/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1917885] [NEW] No longer able to install latest nvidia driver with ubuntu-drivers autoinstall
Public bug reported: Following the latest update of nvidia-drivers-460, my second monitor stopped working. I purged that package and attempted to reinstall with ubuntu-drivers autoinstall. The following error occured: linux-modules-nvidia-460-generic : Depends: nvidia-kernel-common-460 (<= 460.39-1) but 460.56-0ubuntu0.20.04.1 is to be installed I'm not sure why the dependency would say <= instead of >=. I suspect this is part of why my 2nd monitor stopped working and I'm having trouble reinstalling the latest driver. ** Affects: linux-restricted-modules (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules in Ubuntu. https://bugs.launchpad.net/bugs/1917885 Title: No longer able to install latest nvidia driver with ubuntu-drivers autoinstall Status in linux-restricted-modules package in Ubuntu: New Bug description: Following the latest update of nvidia-drivers-460, my second monitor stopped working. I purged that package and attempted to reinstall with ubuntu-drivers autoinstall. The following error occured: linux-modules-nvidia-460-generic : Depends: nvidia-kernel-common-460 (<= 460.39-1) but 460.56-0ubuntu0.20.04.1 is to be installed I'm not sure why the dependency would say <= instead of >=. I suspect this is part of why my 2nd monitor stopped working and I'm having trouble reinstalling the latest driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1917885/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1917203] Re: AMD-Vi: Unable to read/write to IOMMU perf counter
Hi Alex!
A splendidly prompt piece of cherry-picking. Many thanks.
I've checked your test release on my Ryzen 2400G on current Ubuntu 20.10 and it
still gives the diagostic:
AMD-Vi: Unable to read/write to IOMMU perf counter
It's to be expected! The little crew engaged with testing Suravee
Suthikulpanit's patch [1] are finding that the 2400G (that's me) needs
120 msec for power-gating and the 2200G (that's Paul Menzel] needs >200
msecs. Suravee's RFC v3 provides 5 x 20 msecs delay which just isn't
enough for these lesser Ryzen's :-).
If you change Suravee's patch line
for (retry = 5; retry; retry--) {
to
for (retry = 25; retry; retry--) {
all will be well (imho). The maximum delay is indeed outrageous but only
that really necessary to enable IOMMU is actually used. Eventually a
proper solution will be found (in firmware or silicon) but (unlike at
present) the many users of entry-level Ryzen CPU's will not have their
IOMMU crippled during linux boot-up.
Incidentally, if you do rebuild your (very kind) test-release with the
above change (please, please), could you also include the deb package
for linux-tools for the same kernel. Things like the command "perf stat
-a -e amd_iommu/mem_trans_total/ test" (used to test IOMMU performance
in user-space) are tied to the running kernel-version and will then
work.
Best regards and again many thanks
David
[1] https://bugzilla.kernel.org/show_bug.cgi?id=201753
** Bug watch added: Linux Kernel Bug Tracker #201753
https://bugzilla.kernel.org/show_bug.cgi?id=201753
--
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/1917203
Title:
AMD-Vi: Unable to read/write to IOMMU perf counter
Status in linux package in Ubuntu:
In Progress
Bug description:
This boot warning (concealed by grub not taking over the fbcon console
on a solo installation but always present on a multi-boot) has been
bothering Linux users of AMD Ryzen machines for some time.
The problem is currently under discussion at kernel level
.
One solution proposed by Suravee Suthikulpanit
works but inserts a boot-up delay of (at least) 100 msec. A second
option by Alexander Monakov
also works but
inserts no delay and more-or-less just moves one line of code.
I've tried both solutions with kernel rebuilds for both Breezy kernel
5.8.18 and Hirsute kernel 5.10.11 and both work on my AMD Ryzen 2400G.
Could I encourage your kernel experts to evaluate the situation (I
think SuSE folk already are).
My suggestion (as a humble user :-) ) would be to fold Alex's simple
patch into your own list of kernel tweeks and get the correction out
with the upcoming Hirsute release.
Best regards and all respect!
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1917203/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1885862] Re: Add in-tree Realtek 8821CE wireless module support
** Changed in: linux-oem-5.10 (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1885862 Title: Add in-tree Realtek 8821CE wireless module support Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-firmware package in Ubuntu: Invalid Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.6 package in Ubuntu: Invalid Status in linux source package in Focal: In Progress Status in linux-firmware source package in Focal: In Progress Status in linux-oem-5.10 source package in Focal: Fix Committed Status in linux-oem-5.6 source package in Focal: Won't Fix Status in linux source package in Groovy: Won't Fix Status in linux-firmware source package in Groovy: Invalid Status in linux-oem-5.10 source package in Groovy: Invalid Status in linux-oem-5.6 source package in Groovy: Invalid Bug description: 8821ce is being upstreamed in https://lore.kernel.org/linux- wireless/20200603094218.19942-1-yhchu...@realtek.com/ . To backport it to ubuntu kernel so that we may obsolete the usage of rtl8821ce-dkms from https://bugs.launchpad.net/ubuntu/+source/rtl8821ce . To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1885862/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1917842] Re: Fix Lenovo ThinkStation P620 rear audio
** Changed in: linux-oem-5.10 (Ubuntu Focal) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1917842 Title: Fix Lenovo ThinkStation P620 rear audio Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.10 package in Ubuntu: Won't Fix Status in linux source package in Focal: Won't Fix Status in linux-oem-5.10 source package in Focal: Fix Committed Bug description: [Impact] Rear audio on Lenovo ThinkStation P620 stops working on newer kernel. [Fix] Use helper to the correct way to disable USB autosuspend. [Test] With the patch applied, the rear audio on Lenovo ThinkStation P620 works again. [Where problems could occur] In a rather unlikely case, if any USB audio wrongly shared same device ID with P620' USB audios, this patch will disable autosuspend on it. However, it won't bring any functional impact. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1917842/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1917829] Re: alsa/hda: the hdmi audio dosn't work on TGL machines
** Changed in: linux-oem-5.10 (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1917829 Title: alsa/hda: the hdmi audio dosn't work on TGL machines Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.10 source package in Focal: Fix Committed Status in linux source package in Groovy: In Progress Status in linux source package in Hirsute: In Progress Bug description: [Impact] On the TGL machines, we plug a dp mst hub to the thunderbolt port, and plug a hdmi/dp monitor to the dp mst hub, then check the gnome-sound-setting, could not find the hdmi/dp audio device. [Fix] backport a patch from upstream, this patch change to assign the pcm slot dynamically on TGL macines. [Test] On 2 lenovo and dell TGL machines, plug dp mst hub and plug 2 monitors to the hub or to the machine hdmi/dp ports, check the gnome-sound-setting, there are 2 hdmi/dp audio devices. and they all could output sound. [Where problems could occur] After this change, the hdmi audio device number starts from 0, 1, ..., while without this change, the hdmi audio device number is fix mapped, it could be 3 or 5 directly. So if there is some userspace applications depends on the fix mapped hdmi audio device, these applicatons could not work on TGL machines. So far, we don't know if those applications exists or not, but I could confirm the ubuntu audio stack builds on the alsa-lib and pulseaudio, this change will not affect the applications based on the alsa-lib and pulseaudio. And I already tested audio functions under ubuntu on the TGL machines, there is no regression. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1917829/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1912752] Re: linux-uc20-efi: megaraid_sas required in the initrd
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1916165 -- 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/1912752 Title: linux-uc20-efi: megaraid_sas required in the initrd Status in HWE Next: New Status in ubuntu-core-initramfs: Fix Released Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: In Progress Bug description: == Impact == Dell R340 fails to boot with UC20 pc-kernel snap because of unable to find the storage device. == Fix == In this case, storage disks are connected through a controller enabled by kernel module megaraid_sas, hence the module must be presented in the initrd in order to make the system boot. == Risk of Regression == Low. We're only adding an existing module into the initrd. The only downside may be the small increase of the snap size. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1912752/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1916950] Re: [amdgpu] Screen fails to wake up after sleep using 5.4.0-66, but 5.4.0-65 works
@Daniel van Vugt That's a good idea. Thank you. I didn't know what the HWE kernel was. This explains it nicely https://askubuntu.com/questions/248914/what-is-hardware-enablement-hwe -- 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/1916950 Title: [amdgpu] Screen fails to wake up after sleep using 5.4.0-66, but 5.4.0-65 works Status in Linux: Unknown Status in linux package in Ubuntu: Triaged Status in linux-meta-hwe-5.8 package in Ubuntu: Fix Released Bug description: It looks an awful lot like this issue : https://gitlab.freedesktop.org/drm/amd/-/issues/1427. I'm hitting these: [11596.268677] [drm:dce112_get_pix_clk_dividers [amdgpu]] *ERROR* dce112_get_pix_clk_dividers: Invalid parameters!! [11596.269781] [drm:dm_restore_drm_connector_state [amdgpu]] *ERROR* Restoring old state failed with -22 Switching to tty2 wakes it up and allows me to switch back and recover my xorg session. Should this be filed against the kernel, xorg, or amd drivers? I'm not sure.. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86 Uname: Linux 5.4.0-66-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: KDE Date: Thu Feb 25 21:07:28 2021 DistUpgraded: 2020-04-22 17:41:41,681 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.16, 5.4.0-64-generic, x86_64: installed virtualbox, 6.1.16, 5.4.0-65-generic, x86_64: installed virtualbox, 6.1.16, 5.4.0-66-generic, x86_64: installed zfs, 0.8.3, 5.4.0-65-generic, x86_64: installed zfs, 0.8.3, 5.4.0-66-generic, x86_64: installed (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Lexa PRO [Radeon 540/540X/550/550X / RX 540X/550/550X] [1002:699f] (rev c7) (prog-if 00 [VGA controller]) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Lexa PRO [Radeon 540/540X/550/550X / RX 540X/550/550X] [1002:0b04] NVIDIA Corporation GP104 [GeForce GTX 1070] [10de:1b81] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd GP104 [GeForce GTX 1070] [1458:3701] InstallationDate: Installed on 2019-08-15 (560 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) MachineType: Gigabyte Technology Co., Ltd. X570 AORUS PRO ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_fnpezh@/vmlinuz-5.4.0-66-generic root=ZFS=rpool/ROOT/ubuntu_fnpezh ro usbcore.autosuspend=-1 quiet splash amd_iommu=on iommu=pt video=efifb:off,vesafb=off,simplefb=off nouveau.modeset=0 rd.driver.blacklist=nouveau,nvidia,nvidia_uvm,nvidia_drm,nvidia_modeset usbhid.quirks=0x1b1c:0x1b44:0x2408 usbcore.quirks=1b1c:1b44:gn crashkernel=384M vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-04-22 (309 days ago) dmi.bios.date: 02/17/2021 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F33c dmi.board.asset.tag: Default string dmi.board.name: X570 AORUS PRO dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF33c:bd02/17/2021:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSPRO:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSPRO:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: X570 MB dmi.product.name: X570 AORUS PRO dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. modified.conffile..etc.default.apport: [modified] mtime.conffile..etc.default.apport: 2020-03-23T10:46:45.197962 version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati
[Kernel-packages] [Bug 1893663] Re: touchpad not detected
Ok this seem to fix problem Create touchpad.conf to following folders and put i2c_hid as content /etc/modules-load.d/ /usr/lib/modules-load.d/ -- 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/1893663 Title: touchpad not detected Status in linux package in Ubuntu: Expired Bug description: Fujitsu Lifebook U7410 core7 10th generation (Model: 7U14A1) S26391-K502-V100 no information on the touchpad fresh install ubuntu 20.04LTS * touchpad is not detected * sudo lspci -vnvn > lspci-vnvn.log more lspci-vnvn.log 00:00.0 Host bridge [0600]: Intel Corporation Device [8086:9b61] (rev 0c) Subsystem: Fujitsu Client Computing Limited Device [1e26:003f] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 00:02.0 VGA compatible controller [0300]: Intel Corporation UHD Graphics [8086:9b41] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Fujitsu Client Computing Limited UHD Graphics [1e26:004a] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Capabilities: [70] Express (v2) Root Complex Integrated Endpoint, MSI 00 DevCap: MaxPayload 128 bytes, PhantFunc 0 ExtTag- RBE+ FLReset+ DevCtl: CorrErr- NonFatalErr- FatalErr- UnsupReq- RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop- FLReset- MaxPayload 128 bytes, MaxReadReq 128 bytes DevSta: CorrErr- NonFatalErr- FatalErr- UnsupReq- AuxPwr- TransPend- DevCap2: Completion Timeout: Not Supported, TimeoutDis-, NROPrPrP-, LTR- 10BitTagComp-, 10BitTagReq-, OBFF Not Supported, ExtFmt-, EETLPPrefix- EmergencyPowerReduction Not Supported, EmergencyPowerReductionInit- FRS- AtomicOpsCap: 32bit- 64bit- 128bitCAS- DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, OBFF Disabled AtomicOpsCtl: ReqEn- Capabilities: [ac] MSI: Enable+ Count=1/1 Maskable- 64bit- Address: fee00018 Data: Capabilities: [d0] Power Management version 2 Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Capabilities: [100 v1] Process Address Space ID (PASID) PASIDCap: Exec- Priv-, Max PASID Width: 14 PASIDCtl: Enable- Exec- Priv- Capabilities: [200 v1] Address Translation Service (ATS) ATSCap: Invalidate Queue Depth: 00 ATSCtl: Enable-, Smallest Translation Unit: 00 Capabilities: [300 v1] Page Request Interface (PRI) PRICtl: Enable- Reset- PRISta: RF- UPRGI- Stopped+ Page Request Capacity: 8000, Page Request Allocation: Kernel driver in use: i915 cat /proc/version_signature > version.log more version.log Ubuntu 5.4.0-42.46-generic 5.4.44 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-42-generic 5.4.0-42.46 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.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tmadmin2348 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Aug 31 16:22:12 2020 InstallationDate: Installed on 2020-08-31 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: FUJITSU CLIENT COMPUTING LIMITED LIFEBOOK U7410 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=4dadb030-fc54-4457-a7cd-6934b85d602c ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.187.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/23/2020 dmi.bios.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.bios.version: Version 2.12 dmi.board.name: FJNB2D4 dmi.board.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.board.version: A2 dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.chassis.version: LIFEBOOK
[Kernel-packages] [Bug 1916554] Re: Cirrus Audio Codec CS8409/CS42L42 support
Updated ppa with v2 patchset, versioned 5.10.0-2016.17+lp1916554.cirrus.CS8409.CS42L42.7. -- 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/1916554 Title: Cirrus Audio Codec CS8409/CS42L42 support Status in HWE Next: New Status in linux package in Ubuntu: Triaged Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.10 source package in Focal: Triaged Status in linux source package in Hirsute: Triaged Status in linux-oem-5.10 source package in Hirsute: Invalid Bug description: $ sudo dmesg|grep hda [ 19.253994] snd_hda_intel :00:1f.3: enabling device ( -> 0002) [ 19.254515] snd_hda_intel :00:1f.3: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [ 19.317386] snd_hda_codec_generic hdaudioC0D0: autoconfig for Generic: line_outs=1 (0x2c/0x0/0x0/0x0/0x0) type:speaker [ 19.317390] snd_hda_codec_generic hdaudioC0D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [ 19.317392] snd_hda_codec_generic hdaudioC0D0:hp_outs=1 (0x24/0x0/0x0/0x0/0x0) [ 19.317393] snd_hda_codec_generic hdaudioC0D0:mono: mono_out=0x0 [ 19.317395] snd_hda_codec_generic hdaudioC0D0:inputs: [ 19.317397] snd_hda_codec_generic hdaudioC0D0: Internal Mic=0x44 [ 19.317399] snd_hda_codec_generic hdaudioC0D0: Mic=0x34 Vendor driver in progress: https://github.com/CirrusLogic/product-support/tree/cs8409_hda Upstream submission: https://patchwork.kernel.org/project/alsa-devel/list/?series=441331 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.10.0-1013-oem 5.10.0-1013.14 ProcVersionSignature: Ubuntu 5.10.0-1013.14-oem 5.10.6 Uname: Linux 5.10.0-1013-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Feb 22 22:13:32 2021 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-beric-icl+X44 InstallationDate: Installed on 2021-02-04 (18 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-oem-5.10 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: u 1673 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-beric-icl+X44 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-02-04 (18 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0c45:671e Microdia Integrated_Webcam_HD Bus 001 Device 003: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 3501 Package: linux-oem-5.10 (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1013-oem root=UUID=9a169458-bf59-48c8-8aa5-4f58d77f69b1 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.10.0-1013.14-oem 5.10.6 RelatedPackageVersions: linux-restricted-modules-5.10.0-1013-oem N/A linux-backports-modules-5.10.0-1013-oem N/A linux-firmware 1.187.9 Tags: focal Uname: Linux 5.10.0-1013-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/21/2021 dmi.bios.release: 1.2 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.1 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.1:bd01/21/2021:br1.2:svnDellInc.:pnInspiron3501:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 3501 dmi.product.sku: 0A2B dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1916554/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe :
[Kernel-packages] [Bug 1912752] Re: linux-uc20-efi: megaraid_sas required in the initrd
ubuntu-core-initramfs v40 has support for main & server features, which on x86 are enabled by default. The next snap build of pc-kernel in 20/ tracks should contain the required modules. ** Changed in: ubuntu-core-initramfs 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/1912752 Title: linux-uc20-efi: megaraid_sas required in the initrd Status in HWE Next: New Status in ubuntu-core-initramfs: Fix Released Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: In Progress Bug description: == Impact == Dell R340 fails to boot with UC20 pc-kernel snap because of unable to find the storage device. == Fix == In this case, storage disks are connected through a controller enabled by kernel module megaraid_sas, hence the module must be presented in the initrd in order to make the system boot. == Risk of Regression == Low. We're only adding an existing module into the initrd. The only downside may be the small increase of the snap size. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1912752/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1916971] Re: After fresh Ubuntu 20.04 install, downgrading Nvidia driver doesn't update nvidia modules in kernel
Can you please provide the output of: $ sudo ubuntu-drivers list In the live session? There are two ways to get the nvidia kernel driver. One option is to compile it from scratch on the users machine with dkms. THe other option is to install a metapackage linux-modules-nvidia for the appropriate kernel flavour and the appropriate nvidia revsision which provides a prebuild, not linked, and secureboot signed nvidia module. So as to why the dkms one will not work or load on secureboot machines, unless one goes through cryptic MOK key enrollment procedure during boot. The secureboot signed nvidia module works on secureboot machines without any additional steps by the user. But the caveat is that the secureboot signed ones must be kept in correct tandem with the kernel flavour & nvidia revisions. Anything you install from the PPA will not be secureboot signed, and thus need MOK signing. ** Also affects: nvidia-graphics-drivers-460 (Ubuntu) Importance: Undecided Status: New ** Also affects: ubuntu-drivers-common (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu. https://bugs.launchpad.net/bugs/1916971 Title: After fresh Ubuntu 20.04 install, downgrading Nvidia driver doesn't update nvidia modules in kernel Status in nvidia-graphics-drivers-460 package in Ubuntu: New Status in ubiquity package in Ubuntu: New Status in ubuntu-drivers-common package in Ubuntu: New Bug description: SYSTEM: Laptop: ASUS ROG GL552VW OS: Ubuntu 20.04.2 LTS GRAPHICS: Nvidia Geforce GTX 960m AND Intel HD Graphics Linux kernel version: 5.8.0-44-generic SUMMARY: From a fresh working install of Ubuntu 20.04, I downgraded from nvidia-driver-460 by installing nvidia-driver-440 (which actually is a transitional package to nvidia-driver-450 but I didn't know this). After reboot I couldn't reach login-screen and instead got a black screen. Problem was that sudo apt-get install nvidia-driver-440 did not insert nvidia modules v450 in kernel since never versions v460 were found. This was solved by uninstalling linux-modules-nvidia-460 packages and instead installing linux-modules-nvidia-450 packages (see WORKAROUND below for instructions). STEPS TO REPRODUCE: Install Ubuntu 20.04. During installation, allow for the installation of proprietary drivers. Once Ubuntu 20.04 has started, open a terminal and run the following: sudo add-apt-repository ppa:graphics-drivers/ppa sudo apt-get update sudo apt-get install nvidia-driver-440 sudo shutdown reboot now PROBLEM: After reboot, you can't reach login screen. Instead you get stuck during bootup. WORKAROUND: WARNING: BETTER WORKAROUND PROBABLY EXISTS! DON'T JUST COPY-PASTE INSTRUCTIONS. PAY ATTENTION TO WHAT NVIDIA DRVER AND LINUX KERNEL VERSIONS ARE RELEVANT FOR YOU! Run dpkg --list | grep linux-image to see what linux kenrel versions you have installed. Remove the linux-modules-nvidia-460 packages and install the corresponding linux-modules-nvidia-450 packages. In my case I had Linux kernel versions 5.8.0-44-generic and 5.8.0-43-generic installed so I did as follows from recovery mode with network (instead of entering recovery mode, you should be able to press CTRL+ALT+F1 from the blank screen after bootup, login with username and password and then running these commands): sudo apt-get autoremove --purge linux-modules-nvidia-460-5.8.0-44-generic linux-modules-nvidia-460-5.8.0-43-generic sudo apt-get install linux-modules-nvidia-450-5.8.0-44-generic linux-modules-nvidia-450-5.8.0-43-generic sudo shutdown reboot now QUESTION: Why was the linux-modules-nvidia-460 packages installed by the Ubuntu installer to begin with? I ask since I later removed the linux- modules-nvidia-450 packages (OBSERVE: 450, not 460) and used the Additional Drivers GUI to update back to nvidia-driver-460. Now linux- modules-nvidia-460 packages are NOT installed but the following still outputs 460: modinfo nvidia | grep -i version LOG: This is a relevant part of /var/log/apt/term.log for when I installed nvidia-driver-440 nvidia.ko: Running module version sanity check. Error! Module version 450.102.04 for nvidia.ko is not newer than what is already found in kernel 5.8.0-44-generic (460.39). You may override by specifying --force. nvidia-modeset.ko: Running module version sanity check. Error! Module version 450.102.04 for nvidia-modeset.ko is not newer than what is already found in kernel 5.8.0-44-generic (460.39). You may override by specifying --force. nvidia-drm.ko: Running module version sanity check. Error! Module version 450.102.04 for nvidia-drm.ko is not newer than what is already found in kernel 5.8.0-44-generic (460.39). You may override by specifying --force. nvidia-uvm.ko:
[Kernel-packages] [Bug 1917138] Re: Bionic kernel 4.15.0-136 causes dosemu2 (with kvm mode) freezes due to lack of KVM patch
** Changed in: linux (Ubuntu Bionic)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1917138
Title:
Bionic kernel 4.15.0-136 causes dosemu2 (with kvm mode) freezes due to
lack of KVM patch
Status in Dosemu2:
New
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Bionic:
Fix Committed
Bug description:
[Impact]
* Since kernel 4.15.0-136, Bionic kernel included a very complex KVM fix for
a kind of "race" in interrupt window with irqchip-split (reported in [0]). The
fix was proposed in the form of a patch series containing 2 patches [1] - this
was merged in Ubuntu though the stable tree, in the form of the following
commit:
71cc849b7093 ("KVM: x86: Fix split-irqchip vs interrupt injection window
request") [2]
* The problem is that such commit has a companion required commit,
which was not proposed in the stable tree. In fact, there was a
confusion among KVM community and the stable maintainer [3], due to
the lack of such missing commit - because of that, the series was
removed from stable trees 4.14.y and 4.9.y, but the solo commit was
merged alone in Ubuntu kernel.
* Without the companion patch, we might have a KVM infinite "loop" condition
in the core IRQ handling, since the merged commit requires an extra check in
kvm_cpu_has_extint() and a condition "inversion" in kvm_cpu_get_extint(), only
present in the missing companion patch. Users reported that this manifested as
dosemu2 (running in KVM mode) to be stuck in kernel 4.15.0-136 and -137, while
works fine in 4.15.0-135 and the
-137 plus the companion patch.
* So, we hereby backport the companion commit, originally upstream
patch: 72c3bcdcda ("KVM: x86: handle !lapic_in_kernel case in
kvm_cpu_*_extint") [4]
[Test Case]
* The test case proposed was the reported bug: try running dosemu2 (with kvm
mode enabled) and it fails without the companion commit.
* In order to test the correctness of both fixes together, we could
rely in the test proposed in [0] (running a guest with "noapic"), but
it wasn't consistent and the VMM wasn't mentioned, so we might have a
workaround mechanism in qemu, for example, preventing such test to
reproduce the issue.
[Where problems could occur]
* Since this is a KVM core modification, it could affect interrupt handling
in KVM but without the fix, we are already experiencing a bug. Also, both
commits were backported to 5.4.y and 4.19.y, so Focal and subsequent released
are already running with them.
[0]
https://lore.kernel.org/kvm/62918f65ec78f8990278a6a0db0567968fa23e49.ca...@infradead.org/
[1]
https://lore.kernel.org/kvm/20201127112114.3219360-1-pbonz...@redhat.com/
[2] http://git.kernel.org/linus/71cc849b70
[3]
https://lore.kernel.org/stable/d29c4b25-33f6-8d99-7a45-8f4e06f5a...@redhat.com/
[4] http://git.kernel.org/linus/72c3bcdcda
With the latest kernel 4.15.0-136 updates on ubuntu 18.04 and ubuntu
16.04, dosemu2 with kvm freezes boot.
dosemu2 source: https://github.com/dosemu2/dosemu2
dosemu2 package can be obtained from
https://launchpad.net/~dosemu2/+archive/ubuntu/ppa
1. ubuntu version
lsb_release -rd
Description: Ubuntu 18.04.5 LTS
Release: 18.04
2. package version
$ apt-cache policy dosemu2
dosemu2:
Installed: (none)
Candidate: (none)
Version table:
2.0~pre8-2 -1
100 /var/lib/dpkg/status
3. What is expected to happen: The dosemu program runs fine as in previous
kernel version
4. What happened instead: The dosemu freezes on loading
I have also reported this problem to dosemu2 developer, here is my bug report:
https://github.com/dosemu2/dosemu2/issues/1404
To manage notifications about this bug go to:
https://bugs.launchpad.net/dosemu2/+bug/1917138/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1857385] Re: xHCI host controller not responding, assume dead via USB-C docking station
Lenovo X1 Extreme Gen2 Docking Lenovo Thunderbolt 3 Gen2 Was getting similar random disconnects every 2-5 minutes: [125028.443102] pcieport :05:01.0: pciehp: Slot(1): Link Down [125028.443108] pcieport :05:01.0: pciehp: Slot(1): Card not present [125028.443122] pcieport :08:04.0: can't change power state from D3cold to D0 (config space inaccessible) [125028.444133] xhci_hcd :09:00.0: remove, state 1 [125028.444151] usb usb6: USB disconnect, device number 1 [125028.444156] usb 6-2: USB disconnect, device number 2 [125028.444162] usb 6-2.1: USB disconnect, device number 3 [125028.444167] usb 6-2.1.2: USB disconnect, device number 5 [125028.444369] xhci_hcd :09:00.0: xHCI host controller not responding, assume dead .. . Fixed by connecting two power supplies to both laptop and docking (2x135W). -- 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/1857385 Title: xHCI host controller not responding, assume dead via USB-C docking station Status in linux package in Ubuntu: Confirmed Bug description: Hello, I'm using a Lenovo T495s with the Lenovo AJ40 - Ultra Docking Station USB-C (https://support.lenovo.com/us/en/solutions/pd500173O) and, when I undock the laptop from the docking station, the USB Hub disconnects all the local laptop USB ports and they are unusable. If I try to re-attach the laptop to the docking station nothing change, the ports (docking and laptop) are still disconnected, the hdmi/lan/power is working good. Sometimes it happens also when the laptop is docked and I'm working. The issue seems similar of the bug 1766076: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1766076 but here no thunderbolt, it's a ryzen cpu. As written in the bug 1766076, the only way to have the USB in working condition is unbinding/binding the xhci or using the unit/systemd workaround described on post 83 (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1766076/comments/83) with some modification, sometimes is still not working at all. The issue is present on Ubuntu 19.10 (see below the logs), on Ubuntu 18.04 (with kernel 4.x or 5.0 mainline by ubuntu, 5.2 and 5.4 debs installed from kernel.org) and on Fedora 31 too. In Windows everything is working fine. The bios and firmware of the docking station are updated to the last one (1 month ago). The dmesg when I undock the laptop: [ 305.299725] usb 2-1: USB disconnect, device number 2 [ 305.310888] [drm] DM_MST: stopping TM on aconnector: 8e933bad [id: 77] [ 305.311186] [drm] DM_MST: Disabling connector: 0c5e8d66 [id: 81] [master: 8e933bad] [ 305.311957] [drm] DM_MST: Disabling connector: b7fb3125 [id: 86] [master: 8e933bad] [ 305.312136] [drm] DM_MST: Disabling connector: e642e447 [id: 91] [master: 8e933bad] [ 305.362012] r8169 :03:00.0 enp3s0f0: Link is Down [ 305.464627] usb 3-4: USB disconnect, device number 2 [ 305.464642] usb 3-4.2: USB disconnect, device number 3 [ 305.472691] usb 2-4: USB disconnect, device number 4 [ 305.472704] usb 2-4.2: USB disconnect, device number 5 [ 305.472712] usb 2-4.2.4: USB disconnect, device number 7 [ 306.725746] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 306.725892] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) ...hundreds of line - the same [ 310.520323] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 310.520504] xhci_hcd :05:00.3: xHCI host not responding to stop endpoint command. [ 310.520622] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) hundreds of line - the same [ 310.529388] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 310.529626] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 310.530634] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 310.530740] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 310.530843] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 310.531095] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 310.531324] usb 2-4.2.4: 2:1: usb_set_interface failed (-19) [ 310.532315] xhci_hcd :05:00.3: xHCI host controller not responding, assume dead [ 310.532379] xhci_hcd :05:00.3: HC died; cleaning up [ 310.532440] xhci_hcd :05:00.3: Timeout while waiting for configure endpoint command [ 310.670248] usb 2-4.3: USB disconnect, device number 6 [ 310.834039] usb 2-4.5: USB disconnect, device number 8 [ 310.835017] usb 2-2: USB disconnect, device number 10 When I re-attach the latop to the docking: [ 343.111212] r8169 :03:00.0 enp3s0f0: Link is Up - 100Mbps/Full - flow control rx/tx [ 344.272052] [drm] DM_MST: starting TM on aconnector: 8e933bad [id: 77] [ 344.365795] [drm] DM_MST: added connector: e2f1a7b4 [id: 100] [master: 8e933bad] [ 344.365857] [drm] DM_MST: added
[Kernel-packages] [Bug 1917829] Re: alsa/hda: the hdmi audio dosn't work on TGL machines
** No longer affects: linux (Ubuntu Focal) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1917829 Title: alsa/hda: the hdmi audio dosn't work on TGL machines Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.10 source package in Focal: In Progress Status in linux source package in Groovy: In Progress Status in linux source package in Hirsute: In Progress Bug description: [Impact] On the TGL machines, we plug a dp mst hub to the thunderbolt port, and plug a hdmi/dp monitor to the dp mst hub, then check the gnome-sound-setting, could not find the hdmi/dp audio device. [Fix] backport a patch from upstream, this patch change to assign the pcm slot dynamically on TGL macines. [Test] On 2 lenovo and dell TGL machines, plug dp mst hub and plug 2 monitors to the hub or to the machine hdmi/dp ports, check the gnome-sound-setting, there are 2 hdmi/dp audio devices. and they all could output sound. [Where problems could occur] After this change, the hdmi audio device number starts from 0, 1, ..., while without this change, the hdmi audio device number is fix mapped, it could be 3 or 5 directly. So if there is some userspace applications depends on the fix mapped hdmi audio device, these applicatons could not work on TGL machines. So far, we don't know if those applications exists or not, but I could confirm the ubuntu audio stack builds on the alsa-lib and pulseaudio, this change will not affect the applications based on the alsa-lib and pulseaudio. And I already tested audio functions under ubuntu on the TGL machines, there is no regression. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1917829/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1917829] Re: alsa/hda: the hdmi audio dosn't work on TGL machines
** Changed in: linux (Ubuntu Groovy) Importance: High => Medium ** Changed in: linux (Ubuntu Focal) Importance: High => Medium ** Changed in: linux-oem-5.10 (Ubuntu) Status: In Progress => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1917829 Title: alsa/hda: the hdmi audio dosn't work on TGL machines Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.10 source package in Focal: In Progress Status in linux source package in Groovy: In Progress Status in linux source package in Hirsute: In Progress Bug description: [Impact] On the TGL machines, we plug a dp mst hub to the thunderbolt port, and plug a hdmi/dp monitor to the dp mst hub, then check the gnome-sound-setting, could not find the hdmi/dp audio device. [Fix] backport a patch from upstream, this patch change to assign the pcm slot dynamically on TGL macines. [Test] On 2 lenovo and dell TGL machines, plug dp mst hub and plug 2 monitors to the hub or to the machine hdmi/dp ports, check the gnome-sound-setting, there are 2 hdmi/dp audio devices. and they all could output sound. [Where problems could occur] After this change, the hdmi audio device number starts from 0, 1, ..., while without this change, the hdmi audio device number is fix mapped, it could be 3 or 5 directly. So if there is some userspace applications depends on the fix mapped hdmi audio device, these applicatons could not work on TGL machines. So far, we don't know if those applications exists or not, but I could confirm the ubuntu audio stack builds on the alsa-lib and pulseaudio, this change will not affect the applications based on the alsa-lib and pulseaudio. And I already tested audio functions under ubuntu on the TGL machines, there is no regression. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1917829/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1917609] Re: [Regression] ubuntu_bpf failed to build on Groovy
** Changed in: linux (Ubuntu Groovy) Importance: Undecided => Medium -- 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/1917609 Title: [Regression] ubuntu_bpf failed to build on Groovy Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Invalid Status in linux source package in Groovy: In Progress Bug description: [Impact] Upstream commit d3bec0138bfbe58606fc1d6f57a4cdc1a20218db (bpf: Zero-fill re-used per-cpu map element) was applied to Groovy as part of an upstream stable update. This patch fixes a bpf issue and at the same time adds new selftests to verify these changes. However, the selftests can't be compiled on 5.8 due to missing helper functions that were added only later. The bpf selftest build fails with errors such as: /usr/bin/ld: /tmp/autopkgtest.IzBxE1/build.8NX/src/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/bpf/map_init.test.o: in function `prog_run_insert_elem': /tmp/autopkgtest.IzBxE1/build.8NX/src/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/bpf/prog_tests/map_init.c:89: undefined reference to `ASSERT_OK' [Fix] The proposed fix it to partially revert this commit by removing the selftests parts. [Testcase] On a groovy/linux repo: $ make -C tools/testing/selftests TARGETS=bpf SKIP_TARGETS= [Where problems could occur] By removing the selftests we could be introducing a regression with the bpf code change which would be likely unoticed during the tests. Original Description Issue found on 5.8.0-1024.26-azure / 5.8.0-1022.23-oracle Test failed to build, I didn't see any meaningful error message, this might need to be double checked. HDRINST usr/include/asm/fcntl.h HDRINST usr/include/asm/termbits.h HDRINST usr/include/asm/errno.h INSTALL ./usr/include make[1]: Leaving directory '/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux' make: Leaving directory '/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests' stderr: make: *** [Makefile:159: all] Error 1 Please find attachment for the complete test log. == Process to reproduce this == 1. git clone git://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/groovy 2. cd groovy/tools/testing/selftests 3. make TARGETS=bpf You will see the build failed if it's affected by this. I think this is affecting the ubuntu_kernel_selftests as well, as the net test would require the bpf test to be built first. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1917609/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1916467] Re: [Intel Maple Ridge] system cannot enter S3 the first time while connecting to TBT4 storage
Fixed firmware upgrades. ** Changed in: linux (Ubuntu) Status: Incomplete => Invalid ** 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 in Ubuntu. https://bugs.launchpad.net/bugs/1916467 Title: [Intel Maple Ridge] system cannot enter S3 the first time while connecting to TBT4 storage Status in HWE Next: Fix Released Status in linux package in Ubuntu: Invalid Bug description: [Reproduce Steps] 1. install TBT4 card 2. Boot into Ubuntu X68 3. suspend and wake up to confirm S3 function 3. Connect TBT storage 4. suspend 5. system cannot enter S3 [Results] Expected Result: system enters suspend Actual Result: 1st attempt fails, screen will be turned off but power & fan won't. system can only enter s3 afterwards Upstream bug: https://bugzilla.kernel.org/show_bug.cgi?id=211377 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1916467/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1917633] Re: Card stuck in wrong state! card_busy_detect status: 0x700
Which was fixed in 5.10 by:
commit 6246d7c9d15aaff0bc3863f67900c6a6e6be921b
Author: Bean Huo
Date: Wed Dec 2 21:23:20 2020 +0100
mmc: block: Fixup condition for CMD13 polling for RPMB requests
The CMD13 polling is needed for commands with R1B responses. In commit
a0d4c7eb71dd ("mmc: block: Add CMD13 polling for MMC IOCTLS with R1B
response"), the intent was to introduce this for requests targeted to the
RPMB partition. However, the condition to trigger the polling loop became
wrong, leading to unnecessary polling. Let's fix the condition to avoid
this.
Fixes: a0d4c7eb71dd ("mmc: block: Add CMD13 polling for MMC IOCTLS with R1B
response")
Cc: sta...@vger.kernel.org
Reported-by: Zhan Liu
Signed-off-by: Zhan Liu
Signed-off-by: Bean Huo
Link: https://lore.kernel.org/r/20201202202320.22165-1-huob...@gmail.com
Signed-off-by: Ulf Hansson
Which we have in the latest 5.8 raspi kernel. I should always test the
latest kernel. Sigh.
** Changed in: linux-raspi (Ubuntu Groovy)
Status: Confirmed => Invalid
--
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/1917633
Title:
Card stuck in wrong state! card_busy_detect status: 0x700
Status in linux-raspi package in Ubuntu:
New
Status in linux-raspi source package in Groovy:
Invalid
Bug description:
Running sdtool from https://github.com/BertoldVdb/sdtool yields:
$ sudo ./sdtool /dev/mmcblk0 status
[+] Found RCA for /dev/mmcblk0: .
Error 110
[-] Failed to send command: Connection timed out
[ 43.004983] sdhost-bcm2835 3f202000.mmc: Card stuck in wrong state!
card_busy_detect status: 0x700
[ 43.102348] sdhost-bcm2835 3f202000.mmc: sdhost_busy_irq: intmask 0440
[ 53.224992] sdhost-bcm2835 3f202000.mmc: timeout waiting for hardware
interrupt.
[ 53.285006] sdhost-bcm2835 3f202000.mmc: __mmc_blk_ioctl_cmd: cmd error
-110
[ 63.465196] sdhost-bcm2835 3f202000.mmc: timeout waiting for hardware
interrupt.
Tested both arm64 and armhf on 2B (armhf only), 3B, 3B+ and 4B.
Focal 5.4 seems to be OK.
Groovy 5.8 fails on:
- 2B armhf
- 3B+ armhf
- 4B arm64
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1917633/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
