[Kernel-packages] [Bug 1965968] Re: post jammy update, black/flickering screen on boot
both of those exhibit the bug. -- 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/1965968 Title: post jammy update, black/flickering screen on boot Status in linux package in Ubuntu: Confirmed Bug description: After initial jammy upgrade things were working fine, but after a recent update the machine boots to a blank screen. There are occasional purplish flickers that seem to correspond with keypresses, but even blindly typing the encrypted disk password doesn't appear to advance the boot process to gdm. Plugging in an external monitor does fix the issue and allow boot to proceed, but obviously doesn't help if not near an external monitor. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: plymouth 0.9.5+git20211018-1ubuntu3 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Tue Mar 22 09:22:26 2022 DefaultPlymouth: /usr/share/plymouth/themes/bgrt/bgrt.plymouth InstallationDate: Installed on 2019-08-17 (948 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) MachineType: Dell Inc. XPS 15 9575 ProcCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-23-generic root=UUID=83cade14-7628-437d-8517-36ad82f00d20 ro quiet splash vt.handoff=7 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-23-generic root=UUID=83cade14-7628-437d-8517-36ad82f00d20 ro quiet splash vt.handoff=7 SourcePackage: plymouth TextPlymouth: /usr/share/plymouth/themes/ubuntu-gnome-text/ubuntu-gnome-text.plymouth UpgradeStatus: Upgraded to jammy on 2022-03-18 (3 days ago) dmi.bios.date: 03/25/2021 dmi.bios.release: 1.15 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.1 dmi.board.name: 0N338G dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.1:bd03/25/2021:br1.15:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0N338G:rvrA00:cvnDellInc.:ct31:cvr:sku080D: dmi.product.family: XPS dmi.product.name: XPS 15 9575 dmi.product.sku: 080D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1965968/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1937295] Re: [SRU]PCI: vmd: Do not disable MSI-X remapping if interrupt remapping is enabled by IOMMU
Hi Jeff, Now it fail to install Ubuntu server 22.04 with the latest ISO image, but it can pass after update subiquity to the latest. If the latest subiquitythe can be merged into ISO image? -- 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/1937295 Title: [SRU]PCI: vmd: Do not disable MSI-X remapping if interrupt remapping is enabled by IOMMU Status in subiquity: Invalid Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Invalid Status in linux source package in Focal: In Progress Status in linux source package in Impish: Fix Released Status in linux source package in Jammy: Fix Released Bug description: [Impact] A hardware partner discovered they were unable to install Ubuntu on some servers using VROC setups. They point to this issue involving DMAR that is blocking discovery of the VROC RAID devices: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=2565e5b69c44b4e42469afea3cc5a97e74d1ed45 `git bisect` points to this offending commit ee81ee84f873 ("PCI: vmd: Disable MSI-X remapping when possible"), which disables VMD MSI remapping. The IOMMU hardware blocks the compatibility format interrupt request because Interrupt Remapping Enable Status (IRES) and Extended Interrupt Mode Enable (EIME) are enabled. Please refer to section "5.1.4 Interrupt-Remapping Hardware Operation" in Intel VT-d spec. To fix the issue, VMD driver still enables the interrupt remapping irrespective of VMD_FEAT_CAN_BYPASS_MSI_REMAP if the IOMMU subsystem enables the interrupt remapping. [Fix] 2565e5b69c44 PCI: vmd: Do not disable MSI-X remapping if interrupt remapping is enabled by IOMMU [Test Plan] 1. Boot into VRoC controller in uEFI Setup and create a raid10 disk. 2. Install affected Ubuntu release on the RAID10. 3. The system hangs at "Partitions formatting 33%". [Where problems could occur] The fix itself is a very small change to drivers/pci/controller/vmd.c and problems should not occur. The root cause was discovered by the hardware partner's engineers, who tested and submitted it upstream where it was accepted and landed in 5.16. That said, I doubt this will fix 18.04.6 as it would require a respin to get the patched kernel onto the ISO. 20.04 should pick it up in ISO in 20.04.5, so there could still be the initial issue since those ISOs would be lacking the patched kernel. [Other Info] As noted, this would need to not only land in the kernel but land in the kernel in the ISO to resolve the issue in the installation process. I'll bring this back as far as Focal with the expectation that while 20.04.4 is too late, it will be present using the GA kernel in 20.04.5 later on. * Original Bug Summary: A hardware partner has been testing 18.04 subiquity images on their servers with VROC enabled and configured in a RAID 10 setup. In their own words: Steps to reproduce: 1. Boot into VRoC controller in uEFI Setup and create a raid10 disk. 2. Install Ubuntu 18.04.5 on the RAID10. 3. The system hangs at "Partitions formatting 33%". After looking at the launchpad (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1896578/), the fix was included in the updated kernel. [Quotes from the launchpad] The released kernels are: Hirsute: 5.11.0-22-generic Groovy: 5.8.0-59-generic Focal: 5.4.0-77-generic Bionic: 4.15.0-147-generic I've asked them to also confirm this on 20.04.2, and check that 20.04.3 dailies fix the issue. It is at least a very reasonable hypothesis that this will also break on all current ISO installs as none of them are respun once released to include updated SRUs in the installation media. This currently affects 20.04.2 but that will be resolved shortly when 20.04.3 releases as the GA and HWE kernels in that image should have the SRU that fixes this issue. However, 18.04 has no further releases, and even the 18.04.5 daily-live and daily images on cdimages.ubuntu.com are not built after 18.04.5 was released. To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1937295/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1965968] Re: post jammy update, black/flickering screen on boot
Heh, two separate bugs on screen at the same time... Next please try these kernels: https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.14.20/ https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.14.21/ And please keep i915.enable_psr=0 -- 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/1965968 Title: post jammy update, black/flickering screen on boot Status in linux package in Ubuntu: Confirmed Bug description: After initial jammy upgrade things were working fine, but after a recent update the machine boots to a blank screen. There are occasional purplish flickers that seem to correspond with keypresses, but even blindly typing the encrypted disk password doesn't appear to advance the boot process to gdm. Plugging in an external monitor does fix the issue and allow boot to proceed, but obviously doesn't help if not near an external monitor. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: plymouth 0.9.5+git20211018-1ubuntu3 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Tue Mar 22 09:22:26 2022 DefaultPlymouth: /usr/share/plymouth/themes/bgrt/bgrt.plymouth InstallationDate: Installed on 2019-08-17 (948 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) MachineType: Dell Inc. XPS 15 9575 ProcCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-23-generic root=UUID=83cade14-7628-437d-8517-36ad82f00d20 ro quiet splash vt.handoff=7 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-23-generic root=UUID=83cade14-7628-437d-8517-36ad82f00d20 ro quiet splash vt.handoff=7 SourcePackage: plymouth TextPlymouth: /usr/share/plymouth/themes/ubuntu-gnome-text/ubuntu-gnome-text.plymouth UpgradeStatus: Upgraded to jammy on 2022-03-18 (3 days ago) dmi.bios.date: 03/25/2021 dmi.bios.release: 1.15 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.1 dmi.board.name: 0N338G dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.1:bd03/25/2021:br1.15:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0N338G:rvrA00:cvnDellInc.:ct31:cvr:sku080D: dmi.product.family: XPS dmi.product.name: XPS 15 9575 dmi.product.sku: 080D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1965968/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1965968] Re: post jammy update, black/flickering screen on boot
i915.enable_psr=0 did not fix the black screen issue, but did appear to remove the flickering purple streaks, fwiw. -- 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/1965968 Title: post jammy update, black/flickering screen on boot Status in linux package in Ubuntu: Confirmed Bug description: After initial jammy upgrade things were working fine, but after a recent update the machine boots to a blank screen. There are occasional purplish flickers that seem to correspond with keypresses, but even blindly typing the encrypted disk password doesn't appear to advance the boot process to gdm. Plugging in an external monitor does fix the issue and allow boot to proceed, but obviously doesn't help if not near an external monitor. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: plymouth 0.9.5+git20211018-1ubuntu3 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Tue Mar 22 09:22:26 2022 DefaultPlymouth: /usr/share/plymouth/themes/bgrt/bgrt.plymouth InstallationDate: Installed on 2019-08-17 (948 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) MachineType: Dell Inc. XPS 15 9575 ProcCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-23-generic root=UUID=83cade14-7628-437d-8517-36ad82f00d20 ro quiet splash vt.handoff=7 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-23-generic root=UUID=83cade14-7628-437d-8517-36ad82f00d20 ro quiet splash vt.handoff=7 SourcePackage: plymouth TextPlymouth: /usr/share/plymouth/themes/ubuntu-gnome-text/ubuntu-gnome-text.plymouth UpgradeStatus: Upgraded to jammy on 2022-03-18 (3 days ago) dmi.bios.date: 03/25/2021 dmi.bios.release: 1.15 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.1 dmi.board.name: 0N338G dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.1:bd03/25/2021:br1.15:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0N338G:rvrA00:cvnDellInc.:ct31:cvr:sku080D: dmi.product.family: XPS dmi.product.name: XPS 15 9575 dmi.product.sku: 080D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1965968/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1961608] Re: [amdgpu] Screen freeze after wake from sleep
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-hwe-5.13 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1961608 Title: [amdgpu] Screen freeze after wake from sleep Status in linux-hwe-5.13 package in Ubuntu: Confirmed Bug description: Any time the computer sleeps, and I wake it the screen backlight turns on but nothing appears. This has been occurring since upgrading to Kernel 5.11-44. I used 5.11-40 without issues, and when I did a fresh install, I used 5.11-27 without issues. I have tried multiple 5.13 releases and none of them handle sleep and wakeup successfully. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Feb 21 11:13:07 2022 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Wani [Radeon R5/R6/R7 Graphics] [1002:9874] (rev c9) (prog-if 00 [VGA controller]) Subsystem: Dell Wani [Radeon R5/R6/R7 Graphics] [1028:0769] Subsystem: Dell Topaz XT [Radeon R7 M260/M265 / M340/M360 / M440/M445 / 530/535 / 620/625 Mobile] [1028:0769] InstallationDate: Installed on 2022-01-02 (49 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: Dell Inc. Inspiron 5565 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-30-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/17/2017 dmi.bios.release: 5.3 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.1 dmi.board.name: 0021CT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.1.1 dmi.modalias: dmi:bvnDellInc.:bvr1.1.1:bd07/17/2017:br5.3:svnDellInc.:pnInspiron5565:pvr1.1.1:rvnDellInc.:rn0021CT:rvrA00:cvnDellInc.:ct10:cvr1.1.1:sku0769: dmi.product.family: Inspiron dmi.product.name: Inspiron 5565 dmi.product.sku: 0769 dmi.product.version: 1.1.1 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.13/+bug/1961608/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1964711] Re: [amdgpu] Locked Ubuntu is frozen and cannot be unlocked
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-hwe-5.13 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1964711 Title: [amdgpu] Locked Ubuntu is frozen and cannot be unlocked Status in linux-hwe-5.13 package in Ubuntu: Confirmed Bug description: After locking Ubuntu and leaving it unattended for a while, the operating system cannot be unlocked anymore. No means of user input (e.g. typing on the keyboard, moving the mouse) produce the lock screen and I have to shut down my computer by pressing down the power button. The attached monitor does not receive a signal from the computer during these attempts. This started to happen several weeks ago and worked without a problem before then. Due to the nature of this issue, I can neither report any errors occurring nor can I observe any other out of the ordinary things from happening. Thus, I don’t know which package is causing the issue. Also, this issue happens every time I leave the computer unattended for a longer time and lock it. However, locking it and triggering an input immediately after does produce the lock screen, so the lock screen seems to work in principle. Description: Ubuntu 20.04.4 LTS Release: 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.13/+bug/1964711/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1966021] Re: Impish update: upstream stable patchset 2022-03-22
** Description changed: + SRU Justification - 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: - 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 2022-03-22 -upstream stable patchset 2022-03-22 -from git://git.kernel.org/ + Ported from the following upstream stable releases: + v5.10.99, v5.15.22 + v5.10.100, v5.15.23 + + from git://git.kernel.org/ + + selinux: fix double free of cond_list on error paths + audit: improve audit queue handling when "audit=1" on cmdline + ASoC: ops: Reject out of bounds values in snd_soc_put_volsw() + ASoC: ops: Reject out of bounds values in snd_soc_put_volsw_sx() + ASoC: ops: Reject out of bounds values in snd_soc_put_xr_sx() + ALSA: usb-audio: Correct quirk for VF0770 + ALSA: hda: Fix UAF of leds class devs at unbinding + ALSA: hda: realtek: Fix race at concurrent COEF updates + ALSA: hda/realtek: Add quirk for ASUS GU603 + ALSA: hda/realtek: Add missing fixup-model entry for Gigabyte X570 ALC1220 quirks + ALSA: hda/realtek: Fix silent output on Gigabyte X570S Aorus Master (newer chipset) + ALSA: hda/realtek: Fix silent output on Gigabyte X570 Aorus Xtreme after reboot from Windows + btrfs: fix deadlock between quota disable and qgroup rescan worker + drm/nouveau: fix off by one in BIOS boundary checking + drm/amd/display: Force link_rate as LINK_RATE_RBR2 for 2018 15" Apple Retina panels + nvme-fabrics: fix state check in nvmf_ctlr_matches_baseopts() + mm/debug_vm_pgtable: remove pte entry from the page table + mm/pgtable: define pte_index so that preprocessor could recognize it + mm/kmemleak: avoid scanning potential huge holes + block: bio-integrity: Advance seed correctly for larger interval sizes + dma-buf: heaps: Fix potential spectre v1 gadget + IB/hfi1: Fix AIP early init panic + memcg: charge fs_context and legacy_fs_context + RDMA/cma: Use correct address when leaving multicast group + RDMA/ucma: Protect mc during concurrent multicast leaves + IB/rdmavt: Validate remote_addr during loopback atomic tests + RDMA/siw: Fix broken RDMA Read Fence/Resume logic. + RDMA/mlx4: Don't continue event handler after memory allocation failure + iommu/vt-d: Fix potential memory leak in intel_setup_irq_remapping() + iommu/amd: Fix loop timeout issue in iommu_ga_log_enable() + spi: bcm-qspi: check for valid cs before applying chip select + spi: mediatek: Avoid NULL pointer crash in interrupt + spi: meson-spicc: add IRQ check in meson_spicc_probe + spi: uniphier: fix reference count leak in uniphier_spi_probe() + net: ieee802154: hwsim: Ensure proper channel selection at probe time + net: ieee802154: mcr20a: Fix lifs/sifs periods + net: ieee802154: ca8210: Stop leaking skb's + net: ieee802154: Return meaningful error codes from the netlink helpers + net: macsec: Fix offload support for NETDEV_UNREGISTER event + net: macsec: Verify that send_sci is on when setting Tx sci explicitly + net: stmmac: dump gmac4 DMA registers correctly + net: stmmac: ensure PTP time register reads are consistent + drm/i915/overlay: Prevent divide by zero bugs in scaling + ASoC: fsl: Add missing error handling in pcm030_fabric_probe + ASoC: xilinx: xlnx_formatter_pcm: Make buffer bytes multiple of period bytes + ASoC: cpcap: Check for NULL pointer after calling of_get_child_by_name + ASoC: max9759: fix underflow in speaker_gain_control_put() + pinctrl: intel: Fix a glitch when updating IRQ flags on a preconfigured line + pinctrl: intel: fix unexpected interrupt + pinctrl: bcm2835: Fix a few error paths + scsi: bnx2fc: Make bnx2fc_recv_frame() mp safe + nfsd: nfsd4_setclientid_confirm mistakenly expires confirmed client. + gve: fix the wrong AdminQ buffer queue index check + bpf: Use VM_MAP instead of VM_ALLOC for ringbuf + selftests/exec: Remove pipe from TEST_GEN_FILES + selftests: futex: Use variable MAKE instead of make + tools/resolve_btfids: Do not print any commands when building silently + rtc: cmos: Evaluate century appropriate + Revert "fbcon: Disable accelerated scrolling" + UBUNTU: updateconfigs for FRAMEBUFFER_CONSOLE_LEGACY_ACCELERATION + fbcon: Add option to enable lega
[Kernel-packages] [Bug 1966021] [NEW] Impish update: upstream stable patchset 2022-03-22
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 2022-03-22 from git://git.kernel.org/ ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Impish) Importance: Medium Assignee: Kamal Mostafa (kamalmostafa) Status: In Progress ** Tags: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Impish) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Impish) Status: New => In Progress ** Changed in: linux (Ubuntu Impish) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Impish) Assignee: (unassigned) => Kamal Mostafa (kamalmostafa) ** Changed in: linux (Ubuntu) Status: Confirmed => 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/1966021 Title: Impish update: upstream stable patchset 2022-03-22 Status in linux package in Ubuntu: Invalid Status in linux source package in Impish: In Progress 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 2022-03-22 from git://git.kernel.org/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1966021/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1958571] Re: Linux 5.13.0.25-generic Network not working
[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/1958571 Title: Linux 5.13.0.25-generic Network not working Status in linux package in Ubuntu: Expired Bug description: This problem occurs only with this version of kernel. It works fine with 5.13.0.24 version. (on my system the "ubuntu-bag" table of options, no “network issues” is provided. The option “others” on the bottom of the table yield nothing). Appreciate if you can advise how to fix it. Thanks Levi ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: ubuntu-release-upgrader-core 1:21.10.8 ProcVersionSignature: Ubuntu 5.13.0-24.24-generic 5.13.19 Uname: Linux 5.13.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: X-Cinnamon Date: Thu Jan 20 10:58:34 2022 PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) VarLogDistupgradeAptlog: Log time: 2022-01-20 10:41:58.568301 Starting pkgProblemResolver with broken count: 0 Starting 2 pkgProblemResolver with broken count: 0 Done None --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: meir-user 4770 F pulseaudio /dev/snd/controlC0: meir-user 4770 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: X-Cinnamon DistroRelease: Ubuntu 21.10 MachineType: Dell Inc. Inspiron 3180 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-24-generic root=UUID=66ca53b2-7b9e-4a22-9952-a4447fe3778e ro quiet splash crashkernel=512M-:192M vt.handoff=7 ProcVersionSignature: Ubuntu 5.13.0-24.24-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-24-generic N/A linux-backports-modules-5.13.0-24-generic N/A linux-firmware 1.201.3 Tags: impish Uname: Linux 5.13.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A WifiSyslog: _MarkForUpload: True dmi.bios.date: 03/09/2018 dmi.bios.release: 5.3 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.0 dmi.board.name: 0918N8 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.3.0 dmi.modalias: dmi:bvnDellInc.:bvr1.3.0:bd03/09/2018:br5.3:svnDellInc.:pnInspiron3180:pvr1.3.0:rvnDellInc.:rn0918N8:rvrA00:cvnDellInc.:ct10:cvr1.3.0:sku087E: dmi.product.family: Inspiron dmi.product.name: Inspiron 3180 dmi.product.sku: 087E dmi.product.version: 1.3.0 dmi.sys.vendor: Dell Inc. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: admin-meir 59599 F pulseaudio /dev/snd/controlC0: admin-meir 59599 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: X-Cinnamon DistroRelease: Ubuntu 21.10 MachineType: Dell Inc. Inspiron 3180 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-24-generic root=UUID=66ca53b2-7b9e-4a22-9952-a4447fe3778e ro quiet splash crashkernel=512M-:192M vt.handoff=7 ProcVersionSignature: Ubuntu 5.13.0-24.24-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-24-generic N/A linux-backports-modules-5.13.0-24-generic N/A linux-firmware 1.201.3 Tags: impish Uname: Linux 5.13.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/09/2018 dmi.bios.release: 5.3 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.0 dmi.board.name: 0918N8 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.3.0 dmi.modalias: dmi:bvnDellInc.:bvr1.3.0:bd03/09/2018:br5.3:svnDellInc.:pnInspiron3180:pvr1.3.0:rvnDellInc.:rn0918N8:rvrA00:cvnDellInc.:ct10:cvr1.3.0:sku087E: dmi.product.family: Inspiron dmi.product.name: Inspiron 3180 dmi.product.sku
[Kernel-packages] [Bug 1966010] Re: Fix audio on Zbook Studio G9
** Tags added: oem-priority originate-from-1950559 stella -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1966010 Title: Fix audio on Zbook Studio G9 Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.14 source package in Focal: Confirmed Status in linux source package in Jammy: Confirmed Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: [Impact] Cirrus Logic AMP still doesn't work on Zbook Studio G9. Moreoever, The audio mute LEDs stop working after the said SRU. [Fix] Correcly interpret the debounce time from ACPI to gpiolib, and apply the correct quirk for the audio mute LEDs. [Where problems could occur] It's possible that some hardwares rely on the "wrong" debounce time to work, however the fix is to increase the debounce time, so it's more forgiving than decreasing. The LED fix is only applied to one system, so it's specifi and won't cause too much trouble. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1966010/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1966010] [NEW] Fix audio on Zbook Studio G9
Public bug reported: [Impact] Cirrus Logic AMP still doesn't work on Zbook Studio G9. Moreoever, The audio mute LEDs stop working after the said SRU. [Fix] Correcly interpret the debounce time from ACPI to gpiolib, and apply the correct quirk for the audio mute LEDs. [Where problems could occur] It's possible that some hardwares rely on the "wrong" debounce time to work, however the fix is to increase the debounce time, so it's more forgiving than decreasing. The LED fix is only applied to one system, so it's specifi and won't cause too much trouble. ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Medium Status: Confirmed ** Affects: linux-oem-5.14 (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Focal) Importance: Undecided Status: Won't Fix ** Affects: linux-oem-5.14 (Ubuntu Focal) Importance: Medium Status: Confirmed ** Affects: linux (Ubuntu Jammy) Importance: Medium Status: Confirmed ** Affects: linux-oem-5.14 (Ubuntu Jammy) Importance: Undecided Status: Invalid ** Tags: oem-priority originate-from-1950559 stella ** Also affects: linux-oem-5.14 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-oem-5.14 (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-oem-5.14 (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux-oem-5.14 (Ubuntu Focal) Status: New => Confirmed ** Changed in: linux-oem-5.14 (Ubuntu Jammy) Status: New => Invalid ** Changed in: linux (Ubuntu Focal) Status: New => Won't Fix ** Changed in: linux (Ubuntu Jammy) Status: New => Confirmed ** Changed in: linux (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: linux-oem-5.14 (Ubuntu Focal) 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/1966010 Title: Fix audio on Zbook Studio G9 Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.14 source package in Focal: Confirmed Status in linux source package in Jammy: Confirmed Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: [Impact] Cirrus Logic AMP still doesn't work on Zbook Studio G9. Moreoever, The audio mute LEDs stop working after the said SRU. [Fix] Correcly interpret the debounce time from ACPI to gpiolib, and apply the correct quirk for the audio mute LEDs. [Where problems could occur] It's possible that some hardwares rely on the "wrong" debounce time to work, however the fix is to increase the debounce time, so it's more forgiving than decreasing. The LED fix is only applied to one system, so it's specifi and won't cause too much trouble. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1966010/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1876632] Re: [nvidia] Corrupted/missing shell textures when switching users or resuming from suspend
I wonder if Nvidia is now working on this... "Fixed a regression that could cause OpenGL applications to hang or render incorrectly after suspend/resume cycles or VT-switches" [https://www.nvidia.com/download/driverResults.aspx/187162/en-us] -- 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/1876632 Title: [nvidia] Corrupted/missing shell textures when switching users or resuming from suspend Status in GNOME Shell: Unknown Status in Mutter: Unknown Status in gnome-shell package in Ubuntu: Triaged Status in mutter package in Ubuntu: Triaged Status in nvidia-graphics-drivers-440 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-460 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-470 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-510 package in Ubuntu: Confirmed Bug description: I recently installed ubuntu 20.04 on my computer, and I am running into an issue when I do the following: * Login with a user on desktop * Select switch user, and login as second user * Switch user again, and return to original user At this point, text and icons in the menubar / sidebar are corrupted. Text and icons in normal windows appear correctly. I have attached a screenshot of what this looks like. Screenshots: https://imgur.com/a/3ZFDLMc ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..09.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:09:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 3 18:12:45 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP104 [GeForce GTX 1070] [10de:1b81] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP104 [GeForce GTX 1070] [1043:85a0] InstallationDate: Installed on 2020-05-03 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Gigabyte Technology Co., Ltd. AX370-Gaming ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-28-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/19/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F3 dmi.board.asset.tag: Default string dmi.board.name: AX370-Gaming-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: se1 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF3:bd06/19/2017:svnGigabyteTechnologyCo.,Ltd.:pnAX370-Gaming:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAX370-Gaming-CF:rvrse1:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: AX370-Gaming dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1876632/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1965968] 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/1965968 Title: post jammy update, black/flickering screen on boot Status in linux package in Ubuntu: Confirmed Bug description: After initial jammy upgrade things were working fine, but after a recent update the machine boots to a blank screen. There are occasional purplish flickers that seem to correspond with keypresses, but even blindly typing the encrypted disk password doesn't appear to advance the boot process to gdm. Plugging in an external monitor does fix the issue and allow boot to proceed, but obviously doesn't help if not near an external monitor. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: plymouth 0.9.5+git20211018-1ubuntu3 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Tue Mar 22 09:22:26 2022 DefaultPlymouth: /usr/share/plymouth/themes/bgrt/bgrt.plymouth InstallationDate: Installed on 2019-08-17 (948 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) MachineType: Dell Inc. XPS 15 9575 ProcCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-23-generic root=UUID=83cade14-7628-437d-8517-36ad82f00d20 ro quiet splash vt.handoff=7 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-23-generic root=UUID=83cade14-7628-437d-8517-36ad82f00d20 ro quiet splash vt.handoff=7 SourcePackage: plymouth TextPlymouth: /usr/share/plymouth/themes/ubuntu-gnome-text/ubuntu-gnome-text.plymouth UpgradeStatus: Upgraded to jammy on 2022-03-18 (3 days ago) dmi.bios.date: 03/25/2021 dmi.bios.release: 1.15 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.1 dmi.board.name: 0N338G dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.1:bd03/25/2021:br1.15:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0N338G:rvrA00:cvnDellInc.:ct31:cvr:sku080D: dmi.product.family: XPS dmi.product.name: XPS 15 9575 dmi.product.sku: 080D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1965968/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1965968] Re: post jammy update, black/flickering screen on boot
Please try adding kernel parameter: i915.enable_psr=0 Although if kernel 5.13 works then I suspect it may be a relation of bug 1965882. As I dig deeper into that one it seems like a general kernel bug that's not specific to nouveau at all. ** Package changed: plymouth (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1965968 Title: post jammy update, black/flickering screen on boot Status in linux package in Ubuntu: New Bug description: After initial jammy upgrade things were working fine, but after a recent update the machine boots to a blank screen. There are occasional purplish flickers that seem to correspond with keypresses, but even blindly typing the encrypted disk password doesn't appear to advance the boot process to gdm. Plugging in an external monitor does fix the issue and allow boot to proceed, but obviously doesn't help if not near an external monitor. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: plymouth 0.9.5+git20211018-1ubuntu3 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Tue Mar 22 09:22:26 2022 DefaultPlymouth: /usr/share/plymouth/themes/bgrt/bgrt.plymouth InstallationDate: Installed on 2019-08-17 (948 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) MachineType: Dell Inc. XPS 15 9575 ProcCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-23-generic root=UUID=83cade14-7628-437d-8517-36ad82f00d20 ro quiet splash vt.handoff=7 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-23-generic root=UUID=83cade14-7628-437d-8517-36ad82f00d20 ro quiet splash vt.handoff=7 SourcePackage: plymouth TextPlymouth: /usr/share/plymouth/themes/ubuntu-gnome-text/ubuntu-gnome-text.plymouth UpgradeStatus: Upgraded to jammy on 2022-03-18 (3 days ago) dmi.bios.date: 03/25/2021 dmi.bios.release: 1.15 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.1 dmi.board.name: 0N338G dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.1:bd03/25/2021:br1.15:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0N338G:rvrA00:cvnDellInc.:ct31:cvr:sku080D: dmi.product.family: XPS dmi.product.name: XPS 15 9575 dmi.product.sku: 080D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1965968/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1965968] [NEW] post jammy update, black/flickering screen on boot
You have been subscribed to a public bug: After initial jammy upgrade things were working fine, but after a recent update the machine boots to a blank screen. There are occasional purplish flickers that seem to correspond with keypresses, but even blindly typing the encrypted disk password doesn't appear to advance the boot process to gdm. Plugging in an external monitor does fix the issue and allow boot to proceed, but obviously doesn't help if not near an external monitor. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: plymouth 0.9.5+git20211018-1ubuntu3 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Tue Mar 22 09:22:26 2022 DefaultPlymouth: /usr/share/plymouth/themes/bgrt/bgrt.plymouth InstallationDate: Installed on 2019-08-17 (948 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) MachineType: Dell Inc. XPS 15 9575 ProcCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-23-generic root=UUID=83cade14-7628-437d-8517-36ad82f00d20 ro quiet splash vt.handoff=7 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-23-generic root=UUID=83cade14-7628-437d-8517-36ad82f00d20 ro quiet splash vt.handoff=7 SourcePackage: plymouth TextPlymouth: /usr/share/plymouth/themes/ubuntu-gnome-text/ubuntu-gnome-text.plymouth UpgradeStatus: Upgraded to jammy on 2022-03-18 (3 days ago) dmi.bios.date: 03/25/2021 dmi.bios.release: 1.15 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.1 dmi.board.name: 0N338G dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.1:bd03/25/2021:br1.15:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0N338G:rvrA00:cvnDellInc.:ct31:cvr:sku080D: dmi.product.family: XPS dmi.product.name: XPS 15 9575 dmi.product.sku: 080D dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 amdgpu apport-bug i915 jammy wayland-session -- post jammy update, black/flickering screen on boot https://bugs.launchpad.net/bugs/1965968 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1902464] Re: The rear panel of Lenovo P620 doesn't support more than one audio device at the same time
alsa-ucm-conf debdiff for Focal ** Patch added: "alsa-ucm-conf_1.2.2-1ubuntu0.13.debdiff" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1902464/+attachment/5572018/+files/alsa-ucm-conf_1.2.2-1ubuntu0.13.debdiff -- 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/1902464 Title: The rear panel of Lenovo P620 doesn't support more than one audio device at the same time Status in HWE Next: New Status in OEM Priority Project: Confirmed Status in alsa-ucm-conf package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: Fix Released Status in alsa-ucm-conf source package in Focal: Confirmed Status in pulseaudio source package in Focal: Fix Released Bug description: After backporting following patches from PA and alsa-ucm-conf and then it works. https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/290 https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/354 https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/355 https://github.com/alsa-project/alsa-ucm-conf/tree/master/ucm2/USB- Audio [landed by aa74f4c12eefcc98582572d2fc48982cf7478b51] Here is the test PPA: https://launchpad.net/~os369510/+archive/ubuntu/oem-package-test Since the upstream not yet accepted those patches, the regression potential may quite high. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1902464/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1965953] Re: Bluetooth is not working at all
Thanks for the bug report. The file 'rfkill.txt' above is showing Bluetooth is still disabled in software so this sounds like a kernel module bug. It's likely specific to the 'IMC Networks' Bluetooth dongle. ** Summary changed: - Bluetooth is not working at all + Can't turn on Bluetooth (IMC Networks USB dongle) ** Package changed: bluez (Ubuntu) => linux-hwe-5.13 (Ubuntu) -- 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/1965953 Title: Can't turn on Bluetooth (IMC Networks USB dongle) Status in linux-hwe-5.13 package in Ubuntu: New Bug description: Hello. I have installed Ubuntu on a new laptop. Since then I have faced with some problems. One and the most important one is that the Bluetooth is not working at all. When I click to the menu at the top right, I cannot see Bluetooth. When I switched the bluetooth to on on Settings Panel, nothing happens. I also tried to install blueman-applet. But when I click to Turn Bluetooth On button, that plugin disappers and nothing changes. I just followed instructions gathering the information of system. If you need anything else please let me know. Thanks! I always wondered about Ubuntu developers and now I am with you. I just wanna say that everything you have ever done is amazing. Thanks, thanks and thanks again. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 5.13.0-35.40~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-35-generic x86_64 NonfreeKernelModules: wl nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Mar 22 17:11:22 2022 InstallationDate: Installed on 2022-02-02 (48 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) InterestingModules: bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 322e:202c Sonix Technology Co., Ltd. USB2.0 HD UVC WebCam Bus 001 Device 003: ID 13d3:3563 IMC Networks Wireless_Device Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. ASUS TUF Gaming F15 FX506LH_FX506LH ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-35-generic root=UUID=e6194b62-c908-480f-9104-49349523525b ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/26/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: FX506LH.310 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: FX506LH 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.ec.firmware.release: 3.5 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrFX506LH.310:bd11/26/2021:br5.17:efr3.5:svnASUSTeKCOMPUTERINC.:pnASUSTUFGamingF15FX506LH_FX506LH:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnFX506LH:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: ASUS TUF Gaming F15 dmi.product.name: ASUS TUF Gaming F15 FX506LH_FX506LH dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. hciconfig: hci0:Type: Primary Bus: USB BD Address: 00:00:00:00:00:00 ACL MTU: 0:0 SCO MTU: 0:0 DOWN RX bytes:0 acl:0 sco:0 events:0 errors:0 TX bytes:3 acl:0 sco:0 commands:1 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.13/+bug/1965953/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1964386] 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/1964386 Title: [nouveau][Dell XPS 17 9700] Black screen when laptop lid is reopened Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 21.10 When I lock my laptop and close it, then open it back, the screen remains black and I have to hard reset it. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: xorg 1:7.7+22ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-35.40-generic 5.13.19 Uname: Linux 5.13.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Mar 9 18:50:51 2022 DistUpgraded: 2021-11-02 13:32:25,002 DEBUG icon theme changed, re-reading DistroCodename: impish DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Within the last week or two GraphicsCard: Intel Corporation CometLake-H GT2 [UHD Graphics] [8086:9bc4] (rev 05) (prog-if 00 [VGA controller]) Subsystem: Dell CometLake-H GT2 [UHD Graphics] [1028:098f] Subsystem: Dell TU117M [GeForce GTX 1650 Ti Mobile] [1028:098f] InstallationDate: Installed on 2021-04-12 (330 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Dell Inc. XPS 17 9700 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-35-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to impish on 2021-11-02 (127 days ago) dmi.bios.date: 11/18/2021 dmi.bios.release: 1.11 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.11.1 dmi.board.name: 0PV91W dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.11.1:bd11/18/2021:br1.11:svnDellInc.:pnXPS179700:pvr:rvnDellInc.:rn0PV91W:rvrA00:cvnDellInc.:ct10:cvr:sku098F: dmi.product.family: XPS dmi.product.name: XPS 17 9700 dmi.product.sku: 098F dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1964386/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1964386] Re: [nouveau][Dell XPS 17 9700] Black screen when laptop lid is reopened
** Summary changed: - [Dell XPS 17 9700] Black screen when laptop lid is reopened + [nouveau][Dell XPS 17 9700] Black screen when laptop lid is reopened ** Package changed: xorg-server (Ubuntu) => linux (Ubuntu) ** 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/1964386 Title: [nouveau][Dell XPS 17 9700] Black screen when laptop lid is reopened Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 21.10 When I lock my laptop and close it, then open it back, the screen remains black and I have to hard reset it. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: xorg 1:7.7+22ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-35.40-generic 5.13.19 Uname: Linux 5.13.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Mar 9 18:50:51 2022 DistUpgraded: 2021-11-02 13:32:25,002 DEBUG icon theme changed, re-reading DistroCodename: impish DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Within the last week or two GraphicsCard: Intel Corporation CometLake-H GT2 [UHD Graphics] [8086:9bc4] (rev 05) (prog-if 00 [VGA controller]) Subsystem: Dell CometLake-H GT2 [UHD Graphics] [1028:098f] Subsystem: Dell TU117M [GeForce GTX 1650 Ti Mobile] [1028:098f] InstallationDate: Installed on 2021-04-12 (330 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Dell Inc. XPS 17 9700 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-35-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to impish on 2021-11-02 (127 days ago) dmi.bios.date: 11/18/2021 dmi.bios.release: 1.11 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.11.1 dmi.board.name: 0PV91W dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.11.1:bd11/18/2021:br1.11:svnDellInc.:pnXPS179700:pvr:rvnDellInc.:rn0PV91W:rvrA00:cvnDellInc.:ct10:cvr:sku098F: dmi.product.family: XPS dmi.product.name: XPS 17 9700 dmi.product.sku: 098F dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1964386/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1964386] [NEW] [nouveau][Dell XPS 17 9700] Black screen when laptop lid is reopened
You have been subscribed to a public bug: Ubuntu 21.10 When I lock my laptop and close it, then open it back, the screen remains black and I have to hard reset it. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: xorg 1:7.7+22ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-35.40-generic 5.13.19 Uname: Linux 5.13.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Mar 9 18:50:51 2022 DistUpgraded: 2021-11-02 13:32:25,002 DEBUG icon theme changed, re-reading DistroCodename: impish DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Within the last week or two GraphicsCard: Intel Corporation CometLake-H GT2 [UHD Graphics] [8086:9bc4] (rev 05) (prog-if 00 [VGA controller]) Subsystem: Dell CometLake-H GT2 [UHD Graphics] [1028:098f] Subsystem: Dell TU117M [GeForce GTX 1650 Ti Mobile] [1028:098f] InstallationDate: Installed on 2021-04-12 (330 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Dell Inc. XPS 17 9700 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-35-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to impish on 2021-11-02 (127 days ago) dmi.bios.date: 11/18/2021 dmi.bios.release: 1.11 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.11.1 dmi.board.name: 0PV91W dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.11.1:bd11/18/2021:br1.11:svnDellInc.:pnXPS179700:pvr:rvnDellInc.:rn0PV91W:rvrA00:cvnDellInc.:ct10:cvr:sku098F: dmi.product.family: XPS dmi.product.name: XPS 17 9700 dmi.product.sku: 098F dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1 ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug freeze impish nouveau ubuntu wayland-session -- [nouveau][Dell XPS 17 9700] Black screen when laptop lid is reopened https://bugs.launchpad.net/bugs/1964386 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1902464] Re: The rear panel of Lenovo P620 doesn't support more than one audio device at the same time
** Changed in: pulseaudio (Ubuntu) Assignee: Hui Wang (hui.wang) => Kai-Heng Feng (kaihengfeng) -- 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/1902464 Title: The rear panel of Lenovo P620 doesn't support more than one audio device at the same time Status in HWE Next: New Status in OEM Priority Project: Confirmed Status in alsa-ucm-conf package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: Fix Released Status in alsa-ucm-conf source package in Focal: Confirmed Status in pulseaudio source package in Focal: Fix Released Bug description: After backporting following patches from PA and alsa-ucm-conf and then it works. https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/290 https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/354 https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/355 https://github.com/alsa-project/alsa-ucm-conf/tree/master/ucm2/USB- Audio [landed by aa74f4c12eefcc98582572d2fc48982cf7478b51] Here is the test PPA: https://launchpad.net/~os369510/+archive/ubuntu/oem-package-test Since the upstream not yet accepted those patches, the regression potential may quite high. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1902464/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1965467] Re: Need to reset MT7921 BT when the firmware hang or command no response
This bug is awaiting verification that the linux-oem-5.14/5.14.0-1030.33 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1965467 Title: Need to reset MT7921 BT when the firmware hang or command no response Status in HWE Next: New Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.14 source package in Focal: Fix Committed Bug description: [Impact] Encounter BT command timeout issue when doing reboot test, and BT becomes unusable. Mar 15 22:04:44 u-Inspiron-15-3525 kernel: [ 463.633675] usb 3-4: reset high-speed USB device number 3 using xhci_hcd Mar 15 22:04:45 u-Inspiron-15-3525 kernel: [ 465.027012] Bluetooth: hci0: command 0x2005 tx timeout Mar 15 22:04:47 u-Inspiron-15-3525 kernel: [ 467.043176] Bluetooth: hci0: command 0x2041 tx timeout [Fix] Backport below 2 commit from v5.15-rc1 fix this issue e947802657cb Bluetooth: btusb: Support Bluetooth Reset for Mediatek Chip(MT7921) 0b10c8c84c0c Bluetooth: btusb: Record debug log for Mediatek Chip. [Test] Verified on the problem machine, and confirmed it works [Where problems could occur] It adds a new function to cmd_timeout callback, so it won't affect old behaviors. This only affects the chip which has command timeout issue, and could reset the chip when encounter the issue. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1965467/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1956519] Re: amd_sfh: Null pointer dereference on early device init causes early panic and fails to boot
** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1956519 Title: amd_sfh: Null pointer dereference on early device init causes early panic and fails to boot Status in linux package in Ubuntu: Fix Released Status in linux source package in Impish: Fix Released Bug description: BugLink: https://bugs.launchpad.net/bugs/1956519 [Impact] A regression was introduced into 5.13.0-23-generic for devices using AMD Ryzen chipsets that incorporate AMD Sensor Fusion Hub (SFH) HID devices, which are mostly Ryzen based laptops, but desktops do have the SOC embedded as well. On early boot, when the driver initialises the device, it hits a null pointer dereference with the following stack trace: BUG: kernel NULL pointer dereference, address: 000c #PF: supervisor write access in kernel mode #PF: error_code(0x0002) - not-present page PGD 0 P4D 0 Oops: 0002 [#1] SMP NOPTI CPU: 0 PID: 175 Comm: systemd-udevd Not tainted 5.13.0-23-generic #23-Ubuntu RIP: 0010:amd_sfh_hid_client_init+0x47/0x350 [amd_sfh] Call Trace: ? __pci_set_master+0x5f/0xe0 amd_mp2_pci_probe+0xad/0x160 [amd_sfh] local_pci_probe+0x48/0x80 pci_device_probe+0x105/0x1c0 really_probe+0x24b/0x4c0 driver_probe_device+0xf0/0x160 device_driver_attach+0xab/0xb0 __driver_attach+0xb2/0x140 ? device_driver_attach+0xb0/0xb0 bus_for_each_dev+0x7e/0xc0 driver_attach+0x1e/0x20 bus_add_driver+0x135/0x1f0 driver_register+0x95/0xf0 ? 0xc03d2000 __pci_register_driver+0x57/0x60 amd_mp2_pci_driver_init+0x23/0x1000 [amd_sfh] do_one_initcall+0x48/0x1d0 ? kmem_cache_alloc_trace+0xfb/0x240 do_init_module+0x62/0x290 load_module+0xa8f/0xb10 __do_sys_finit_module+0xc2/0x120 __x64_sys_finit_module+0x18/0x20 do_syscall_64+0x61/0xb0 ? ksys_mmap_pgoff+0x135/0x260 ? exit_to_user_mode_prepare+0x37/0xb0 ? syscall_exit_to_user_mode+0x27/0x50 ? __x64_sys_mmap+0x33/0x40 ? do_syscall_64+0x6e/0xb0 ? do_syscall_64+0x6e/0xb0 ? do_syscall_64+0x6e/0xb0 ? syscall_exit_to_user_mode+0x27/0x50 ? do_syscall_64+0x6e/0xb0 ? exc_page_fault+0x8f/0x170 ? asm_exc_page_fault+0x8/0x30 entry_SYSCALL_64_after_hwframe+0x44/0xae This causes a panic and the system is unable to continue booting, and the user must select an older kernel to boot. [Fix] The issue was introduced in 5.13.0-23-generic by the commit: commit d46ef750ed58cbeeba2d9a55c99231c30a172764 commit-impish 56559d7910e704470ad72da58469b5588e8cbf85 Author: Evgeny Novikov Date: Tue Jun 1 19:38:01 2021 +0300 Subject:HID: amd_sfh: Fix potential NULL pointer dereference Link: https://github.com/torvalds/linux/commit/d46ef750ed58cbeeba2d9a55c99231c30a172764 The issue is pretty straightforward, amd_sfh_client.c attempts to dereference cl_data, but it is NULL: $ eu-addr2line -ifae ./usr/lib/debug/lib/modules/5.13.0-23-generic/kernel/drivers/hid/amd-sfh-hid/amd_sfh.ko amd_sfh_hid_client_init+0x47 0x0767 amd_sfh_hid_client_init /build/linux-k2e9CH/linux-5.13.0/drivers/hid/amd-sfh-hid/amd_sfh_client.c:147:27 134 int amd_sfh_hid_client_init(struct amd_mp2_dev *privdata) 135 { ... 146 147 cl_data->num_hid_devices = amd_mp2_get_sensor_num(privdata, &cl_data->sensor_idx[0]); 148 ... The patch moves the call to amd_sfh_hid_client_init() before privdata->cl_data is actually allocated by devm_kzalloc, hence cl_data being NULL. + rc = amd_sfh_hid_client_init(privdata); + if (rc) + return rc; + privdata->cl_data = devm_kzalloc(&pdev->dev, sizeof(struct amdtp_cl_data), GFP_KERNEL); if (!privdata->cl_data) return -ENOMEM; ... - return amd_sfh_hid_client_init(privdata); + return 0; The issue was fixed upstream in 5.15-rc4 by the commit: commit 88a04049c08cd62e698bc1b1af2d09574b9e0aee Author: Basavaraj Natikar Date: Thu Sep 23 17:59:27 2021 +0530 Subject: HID: amd_sfh: Fix potential NULL pointer dereference Link: https://github.com/torvalds/linux/commit/88a04049c08cd62e698bc1b1af2d09574b9e0aee The fix places the call to amd_sfh_hid_client_init() after privdata->cl_data is allocated, and it changes the order of amd_sfh_hid_client_init() to happen before devm_add_action_or_reset() fixing the actual null pointer dereference which caused these commits to exist. This patch also landed in 5.14.10 -stable, but it seems it was omitted from being backported to impish, likely due to it sharing the exact same subject line as the regression commit, so it was likely dropped as a duplicate? [Testcase] You need an AMD Ryzen based system that has a AMD Sensor Fusion Hub HID device built in to test this. Simply booting the system is e
[Kernel-packages] [Bug 1958410] Re: bytcr_rt5640 sound not working with kernel >= 5.13
Also affects 22.04 on 5.15.0-23-generic ** Also affects: linux-meta-hwe-5.15 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1958410 Title: bytcr_rt5640 sound not working with kernel >= 5.13 Status in linux-meta-hwe-5.13 package in Ubuntu: Confirmed Status in linux-meta-hwe-5.15 package in Ubuntu: New Bug description: Using the built in speakers on a Linx 1010b. The 5.11 kernel works fine, but 5.13 and 5.14 fail. The card, when working is seen in alsa-info as bytcrrt5640,bytcr- rt5640, whereas in the later (hwe-20.04-edge, oem-20.04d) kernels where it fails, it is seen as "rt5640,sof-bytcht rt5640" When failing, speaker-test, spd-say, and most other sound sources seem to get 'sunk', and the level meter on the pulse mixer shows activity. FWIW "espeak-ng hello" blocks on the broken setup. I confess I'm not actually using the linux-meta-hwe-5.13 as it is unavailable in LinuxMint. I am using linux-generic-hwe-20.04-edge, which AFAICT pulls in the same kernels. apt policy pointed me to report here. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe-5.13/+bug/1958410/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1965976] [NEW] nvidia-dkms-390 390.144-0ubuntu0.20.04.1: nvidia kernel module failed to build
Public bug reported: Since the last automatic update of 2022 (a couple of weeks ago) my system only boots in low-graphics mode. It seems not to recognize the NVIDIA graphics card nor the 2nd monitor. How can I reinstall Ubuntu 20.04 or the graphics driver? ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-dkms-390 390.144-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.14.0-1024.26-oem 5.14.21 Uname: Linux 5.14.0-1024-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip DKMSKernelVersion: 5.14.0-1027-oem Date: Tue Mar 22 12:58:54 2022 DuplicateSignature: dkms:nvidia-dkms-390:390.144-0ubuntu0.20.04.1:/var/lib/dkms/nvidia/390.144/build/nvidia/os-interface.c:583:18: error: ‘struct task_struct’ has no member named ‘state’; did you mean ‘__state’? InstallationDate: Installed on 2018-11-28 (1210 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageVersion: 390.144-0ubuntu0.20.04.1 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: nvidia-graphics-drivers-390 Title: nvidia-dkms-390 390.144-0ubuntu0.20.04.1: nvidia kernel module failed to build UpgradeStatus: Upgraded to focal on 2021-06-29 (265 days ago) ** Affects: nvidia-graphics-drivers-390 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal need-duplicate-check -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1965976 Title: nvidia-dkms-390 390.144-0ubuntu0.20.04.1: nvidia kernel module failed to build Status in nvidia-graphics-drivers-390 package in Ubuntu: New Bug description: Since the last automatic update of 2022 (a couple of weeks ago) my system only boots in low-graphics mode. It seems not to recognize the NVIDIA graphics card nor the 2nd monitor. How can I reinstall Ubuntu 20.04 or the graphics driver? ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-dkms-390 390.144-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.14.0-1024.26-oem 5.14.21 Uname: Linux 5.14.0-1024-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip DKMSKernelVersion: 5.14.0-1027-oem Date: Tue Mar 22 12:58:54 2022 DuplicateSignature: dkms:nvidia-dkms-390:390.144-0ubuntu0.20.04.1:/var/lib/dkms/nvidia/390.144/build/nvidia/os-interface.c:583:18: error: ‘struct task_struct’ has no member named ‘state’; did you mean ‘__state’? InstallationDate: Installed on 2018-11-28 (1210 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageVersion: 390.144-0ubuntu0.20.04.1 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: nvidia-graphics-drivers-390 Title: nvidia-dkms-390 390.144-0ubuntu0.20.04.1: nvidia kernel module failed to build UpgradeStatus: Upgraded to focal on 2021-06-29 (265 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1965976/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1955882] Re: MT7921[14c3:7961] ASPM is disabled and it affects power consumption
This bug was fixed in the package linux-oem-5.14 - 5.14.0-1029.32 --- linux-oem-5.14 (5.14.0-1029.32) focal; urgency=medium * focal/linux-oem-5.14: 5.14.0-1029.32 -proposed tracker (LP: #1964962) * CVE-2022-0742 - ipv6: fix skb drops in igmp6_event_query() and igmp6_event_report() -- Timo Aaltonen Fri, 18 Mar 2022 15:06:46 +0200 ** Changed in: linux-oem-5.14 (Ubuntu Focal) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-0742 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1955882 Title: MT7921[14c3:7961] ASPM is disabled and it affects power consumption Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: [Impact] MT7921 is disabled by default, and it affects the power consumption. [Fix] MTK pointed out we need this commit which is included in v5.16-rc1 bf3747ae2e25 mt76: mt7921: enable aspm by default After ASPM is enabled, we found the card disappears after reboot sometimes, so MTK provides another commit for it https://patchwork.kernel.org/project/linux-mediatek/patch/70e27cbc652cbdb78277b9c691a3a5ba02653afb.1641540175.git.obj...@gmail.com/ [Test] Verified on Dell machines with MT7921 wifi card. [Where problems could occur] Enable device ASPM is always risky, we've done our best to test these patches, and no regression could be found. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1955882/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1963615] Re: Add proper runtime PM support to Realtek PCIe cardreader
This bug was fixed in the package linux-oem-5.14 - 5.14.0-1029.32 --- linux-oem-5.14 (5.14.0-1029.32) focal; urgency=medium * focal/linux-oem-5.14: 5.14.0-1029.32 -proposed tracker (LP: #1964962) * CVE-2022-0742 - ipv6: fix skb drops in igmp6_event_query() and igmp6_event_report() -- Timo Aaltonen Fri, 18 Mar 2022 15:06:46 +0200 ** Changed in: linux-oem-5.14 (Ubuntu Focal) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-0742 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1963615 Title: Add proper runtime PM support to Realtek PCIe cardreader Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: [Impact] New generations of Realtek PCIe card reader cannot detect card insertion when the device is in PCI D3. [Fix] Rework the runtime PM flow and add chip specific support. [Test] With the series applied, the device can detect card insertion when it's in PCI D3. [Where problems could occur] System wide power management with less usage like hibernation, kexec reboot, etc. are not tested extensively. So these cases may be affected. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1963615/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1964748] Re: Cirrus audio support [1028:0BB5] & [1028:0BB6]
This bug was fixed in the package linux-oem-5.14 - 5.14.0-1029.32 --- linux-oem-5.14 (5.14.0-1029.32) focal; urgency=medium * focal/linux-oem-5.14: 5.14.0-1029.32 -proposed tracker (LP: #1964962) * CVE-2022-0742 - ipv6: fix skb drops in igmp6_event_query() and igmp6_event_report() -- Timo Aaltonen Fri, 18 Mar 2022 15:06:46 +0200 ** Changed in: linux-oem-5.14 (Ubuntu Focal) Status: In Progress => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-0742 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1964748 Title: Cirrus audio support [1028:0BB5] & [1028:0BB6] Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Jammy: In Progress Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: [Impact] These 2 IDs([1028:0BB5],[1028:0BB6]) are required to be added into cs8409 quirk to get it work [Fix] Cherry picked below commit from v5.17-rc1 2a1355f0bf41 ALSA: hda/cs8409: Add new Warlock SKUs to patch_cs8409 [Test] Verified on Dell machines which contains this Cirrus audio. [Where problems could occur] Adding 2 IDs into quirk is trivial, and should not introduce any regression. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1964748/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1963555] Re: xhci: Fix command ring abort, write all 64 bits to CRCR register.
I have also experienced this upstream bug which causes the USB hubs to drop all attached devices. This means that external drive devices all disappear almost as quickly as they appear. Basically it's a show stopper since I can't use my USB attached data drives at all any more. -- 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/1963555 Title: xhci: Fix command ring abort, write all 64 bits to CRCR register. Status in linux package in Ubuntu: Confirmed Bug description: Upstream mainline kernel includes patch v5.15-rc5-4-gff0e50d3564f. This patch was included in the Ubuntu kernel as Ubuntu-5.13.0-22.22-387-g0fc979747dec, available in Ubuntu kernels 5.13.0-23 and up. The patch is incomplete, which causes an issue with some xHC controllers. An additional patch was made to the upstream mainline kernel, which fixes the issue that was introduced: v5.16-rc3-1-g09f736aa9547. This patch does not yet have a corresponding commit in the Ubuntu kernel repository for Ubuntu 21.10; and Ubuntu 22.04 will use the 5.15 kernel, which does also not include the second patch. Discussion of the first patch (already in Ubuntu kernel) can be found on the kernel.org mailing list: https://lore.kernel.org/r/20211008092547.3996295-5-mathias.ny...@linux.intel.com Discussion of the second patch (not yet in Ubuntu kernel): https://lore.kernel.org/all/20211126122340.1193239-2-mathias.ny...@linux.intel.com/ Request to include upstream patch v5.16-rc3-1-g09f736aa9547 into the kernels for Ubuntu 21.10 (5.13 kernels) and Ubuntu 22.04 LTS (5.15 kernels). ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-22-generic 5.13.0-22.22 ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 Uname: Linux 5.13.0-22-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: amedee 4158 F pulseaudio /dev/snd/controlC3: amedee 4158 F pulseaudio /dev/snd/controlC0: amedee 4158 F pulseaudio /dev/snd/controlC1: amedee 4158 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Mar 3 22:23:43 2022 HibernationDevice: RESUME=UUID=edec0bf3-448f-4e5c-a21a-ef9624572973 InstallationDate: Installed on 2022-01-30 (32 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) IwConfig: lono wireless extensions. eno1 no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. Z370 AORUS Gaming K3 ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-22-generic root=/dev/mapper/hostname-root ro quiet splash vt.handoff=7 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: linux-restricted-modules-5.13.0-22-generic N/A linux-backports-modules-5.13.0-22-generic N/A linux-firmware 1.201.4 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/28/2019 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F15a dmi.board.asset.tag: Default string dmi.board.name: Z370 AORUS Gaming K3-CF 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:bvnAmericanMegatrendsInc.:bvrF15a:bd11/28/2019:br5.12:svnGigabyteTechnologyCo.,Ltd.:pnZ370AORUSGamingK3:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ370AORUSGamingK3-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: Default string dmi.product.name: Z370 AORUS Gaming K3 dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1963555/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1964114] Re: network interface is removed after latest update (pi4)
I installed a fresh Focal image to an SSD and eth0 comes up just fine with kernel 1053. Sorry but I can't reproduce your issue. I'll close the ticket. Please open a new one should you run into this issue again. ** Changed in: linux-raspi (Ubuntu) Status: New => 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/1964114 Title: network interface is removed after latest update (pi4) Status in linux-raspi package in Ubuntu: Invalid Bug description: Hello, I have a image disk of ubuntu 20.04 with the previous package version -> working well When I restore this image at start there is an upgrade and when I reboot eth0 is gone (configured with netplan) I can easily reproduce Restore image, start, just wait for upgrade, reboot thanks --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.4.0-1052-raspi. ApportVersion: 2.20.11-0ubuntu27.21 Architecture: arm64 ArecordDevices: List of CAPTURE Hardware Devices AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/pcmC1D0p', '/dev/snd/controlC0', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Card hw:0 'b1'/'bcm2835 HDMI 1' Mixer name : 'Broadcom Mixer' Components : '' Controls : 2 Simple ctrls : 1 Card0.Amixer.values: Simple mixer control 'HDMI',0 Capabilities: pvolume pvolume-joined pswitch pswitch-joined Playback channels: Mono Limits: Playback -10239 - 400 Mono: Playback 0 [96%] [0.00dB] [on] Card1.Amixer.info: Card hw:1 'Headphones'/'bcm2835 Headphones' Mixer name : 'Broadcom Mixer' Components : '' Controls : 2 Simple ctrls : 1 Card1.Amixer.values: Simple mixer control 'Headphone',0 Capabilities: pvolume pvolume-joined pswitch pswitch-joined Playback channels: Mono Limits: Playback -10239 - 400 Mono: Playback -2000 [77%] [-20.00dB] [on] CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 ImageMediaBuild: 20210819.1 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci-vt: -[:00]---00.0-[01]00.0 VIA Technologies, Inc. VL805 USB 3.0 Host Controller Package: linux-raspi 5.4.0.1052.86 PackageArchitecture: arm64 PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 vc4drmfb ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=1 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 video=HDMI-A-1:1920x1080M@60,margin_left=48,margin_right=48,margin_top=48,margin_bottom=48 smsc95xx.macaddr=E4:5F:01:41:AC:4F vc_mem.mem_base=0x3eb0 vc_mem.mem_size=0x3ff0 usb-storage.quirks=152d:0578:u net.ifnames=0 dwc_otg.lpm_enable=0 console=ttyS0,115200 console=tty1 root=LABEL=writable rootfstype=ext4 elevator=deadline rootwait fixrtc ProcVersionSignature: Ubuntu 5.4.0-1052.58-raspi 5.4.162 RelatedPackageVersions: linux-restricted-modules-5.4.0-1052-raspi N/A linux-backports-modules-5.4.0-1052-raspi N/A linux-firmware1.187.26 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' StagingDrivers: bcm2835_codec bcm2835_isp vc_sm_cma bcm2835_mmal_vchiq bcm2835_v4l2 snd_bcm2835 Tags: third-party-packages arm64-image raspi-image focal staging Uname: Linux 5.4.0-1052-raspi aarch64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True acpidump: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1964114/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1965953] Re: Bluetooth is not working at all
** Package changed: ubuntu => bluez (Ubuntu) -- 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/1965953 Title: Bluetooth is not working at all Status in bluez package in Ubuntu: New Bug description: Hello. I have installed Ubuntu on a new laptop. Since then I have faced with some problems. One and the most important one is that the Bluetooth is not working at all. When I click to the menu at the top right, I cannot see Bluetooth. When I switched the bluetooth to on on Settings Panel, nothing happens. I also tried to install blueman-applet. But when I click to Turn Bluetooth On button, that plugin disappers and nothing changes. I just followed instructions gathering the information of system. If you need anything else please let me know. Thanks! I always wondered about Ubuntu developers and now I am with you. I just wanna say that everything you have ever done is amazing. Thanks, thanks and thanks again. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 5.13.0-35.40~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-35-generic x86_64 NonfreeKernelModules: wl nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Mar 22 17:11:22 2022 InstallationDate: Installed on 2022-02-02 (48 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) InterestingModules: bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 322e:202c Sonix Technology Co., Ltd. USB2.0 HD UVC WebCam Bus 001 Device 003: ID 13d3:3563 IMC Networks Wireless_Device Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. ASUS TUF Gaming F15 FX506LH_FX506LH ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-35-generic root=UUID=e6194b62-c908-480f-9104-49349523525b ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/26/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: FX506LH.310 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: FX506LH 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.ec.firmware.release: 3.5 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrFX506LH.310:bd11/26/2021:br5.17:efr3.5:svnASUSTeKCOMPUTERINC.:pnASUSTUFGamingF15FX506LH_FX506LH:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnFX506LH:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: ASUS TUF Gaming F15 dmi.product.name: ASUS TUF Gaming F15 FX506LH_FX506LH dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. hciconfig: hci0:Type: Primary Bus: USB BD Address: 00:00:00:00:00:00 ACL MTU: 0:0 SCO MTU: 0:0 DOWN RX bytes:0 acl:0 sco:0 events:0 errors:0 TX bytes:3 acl:0 sco:0 commands:1 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1965953/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1965953] [NEW] Bluetooth is not working at all
You have been subscribed to a public bug: Hello. I have installed Ubuntu on a new laptop. Since then I have faced with some problems. One and the most important one is that the Bluetooth is not working at all. When I click to the menu at the top right, I cannot see Bluetooth. When I switched the bluetooth to on on Settings Panel, nothing happens. I also tried to install blueman-applet. But when I click to Turn Bluetooth On button, that plugin disappers and nothing changes. I just followed instructions gathering the information of system. If you need anything else please let me know. Thanks! I always wondered about Ubuntu developers and now I am with you. I just wanna say that everything you have ever done is amazing. Thanks, thanks and thanks again. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 5.13.0-35.40~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-35-generic x86_64 NonfreeKernelModules: wl nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Mar 22 17:11:22 2022 InstallationDate: Installed on 2022-02-02 (48 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) InterestingModules: bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 322e:202c Sonix Technology Co., Ltd. USB2.0 HD UVC WebCam Bus 001 Device 003: ID 13d3:3563 IMC Networks Wireless_Device Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. ASUS TUF Gaming F15 FX506LH_FX506LH ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-35-generic root=UUID=e6194b62-c908-480f-9104-49349523525b ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/26/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: FX506LH.310 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: FX506LH 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.ec.firmware.release: 3.5 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrFX506LH.310:bd11/26/2021:br5.17:efr3.5:svnASUSTeKCOMPUTERINC.:pnASUSTUFGamingF15FX506LH_FX506LH:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnFX506LH:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: ASUS TUF Gaming F15 dmi.product.name: ASUS TUF Gaming F15 FX506LH_FX506LH dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. hciconfig: hci0: Type: Primary Bus: USB BD Address: 00:00:00:00:00:00 ACL MTU: 0:0 SCO MTU: 0:0 DOWN RX bytes:0 acl:0 sco:0 events:0 errors:0 TX bytes:3 acl:0 sco:0 commands:1 errors:0 ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- Bluetooth is not working at all https://bugs.launchpad.net/bugs/1965953 You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1902464] Re: The rear panel of Lenovo P620 doesn't support more than one audio device at the same time
We only need to update UCM to solve this issue for Lenovo P620. ** Also affects: pulseaudio (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: alsa-ucm-conf (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: alsa-ucm-conf (Ubuntu Focal) Status: New => Confirmed ** Changed in: pulseaudio (Ubuntu Focal) Status: New => Fix Released ** Changed in: pulseaudio (Ubuntu) Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/1902464 Title: The rear panel of Lenovo P620 doesn't support more than one audio device at the same time Status in HWE Next: New Status in OEM Priority Project: Confirmed Status in alsa-ucm-conf package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: Fix Released Status in alsa-ucm-conf source package in Focal: Confirmed Status in pulseaudio source package in Focal: Fix Released Bug description: After backporting following patches from PA and alsa-ucm-conf and then it works. https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/290 https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/354 https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/355 https://github.com/alsa-project/alsa-ucm-conf/tree/master/ucm2/USB- Audio [landed by aa74f4c12eefcc98582572d2fc48982cf7478b51] Here is the test PPA: https://launchpad.net/~os369510/+archive/ubuntu/oem-package-test Since the upstream not yet accepted those patches, the regression potential may quite high. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1902464/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1960083] Re: dirname applet missing from initramfs
Hello This version is goodjammy-desktop-amd64.iso 2022-03-21 08:38 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1960083 Title: dirname applet missing from initramfs Status in busybox package in Ubuntu: Fix Released Status in zfs-linux package in Ubuntu: Fix Released Bug description: The initramfs is currently being built without the dirname applet. This is causing issues with zfs encrypted devices, as cryptsetup is attempting to use dirname to determine the location of the system key. This results in the following error: /init: line 971: dirname: not found followed by a prompt that is missing the zpool name. For example "Please unlock disk keystore-" rather than "Please unlock disk keystore-rpool". After entering the password, the user is dropped to an initramfs shell. It appears that this was caused by a change in cryptsetup to suddenly need dirname to function properly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/busybox/+bug/1960083/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1948825] Re: kernel NULL pointer dereference in iwlmvm when debugfs=off
This seems to be fixed upstream by https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=5a6248c0a22352f09ea041665d3bd3e18f6f872c which is marked `Cc: stable `. I'd expect this commit to eventually percolate to Ubuntu kernels, right? If so, should this bug be kept open until then? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1948825 Title: kernel NULL pointer dereference in iwlmvm when debugfs=off Status in linux-hwe-5.11 package in Ubuntu: New Status in linux-hwe-5.13 package in Ubuntu: New Bug description: When booting 5.13.0-30-generic, dmesg shows: ieee80211 phy0: Selected rate control algorithm 'iwl-mvm-rs' BUG: kernel NULL pointer dereference, address: 0017 #PF: supervisor read access in kernel mode #PF: error_code(0x) - not-present page PGD 0 P4D 0 Oops: [#1] SMP PTI CPU: 1 PID: 921 Comm: modprobe Tainted: P U O 5.13.0-30-generic #33~20.04.1-Ubuntu Hardware name: System76Lemur/Lemur, BIOS 1.05.25RSA2-1 04/17/2018 RIP: 0010:iwl_mvm_dbgfs_register+0x660/0x6d0 [iwlmvm] Code: 29 c1 be 80 01 00 00 48 c7 c7 35 f8 29 c1 e8 27 b9 20 cd 48 8b 83 60 18 00 00 48 c7 c2 39 f8 29 c1 be 64 00 00 00 48 8d 7d 8c <48> 8b 48 18 e8 f7 07 36 cd 48 8b 43 28 48 8d 55 8c 48 c7 c7 44 f8 RSP: 0018:9e37c072bb08 EFLAGS: 00010206 RAX: RBX: 8b3fcb5e1f48 RCX: 8b3fcb5e1f48 RDX: c129f839 RSI: 0064 RDI: 9e37c072bb0c RBP: 9e37c072bb80 R08: 8f26c920 R09: c1298ae0 R10: 0100 R11: 0021 R12: R13: 000fffe0 R14: 8b3fcb5e1f48 R15: 8b3fcb5e1f40 FS: 7f9084e19540() GS:8b470ec8() knlGS: CS: 0010 DS: ES: CR0: 80050033 CR2: 0017 CR3: 0001048c8006 CR4: 003706e0 Call Trace: ? iwl_mvm_mac_setup_register+0x95e/0xb90 [iwlmvm] ? iwl_mvm_stop_device+0x65/0x80 [iwlmvm] iwl_op_mode_mvm_start+0x96f/0xa40 [iwlmvm] _iwl_op_mode_start.isra.0+0x47/0x80 [iwlwifi] iwl_opmode_register+0x73/0xe0 [iwlwifi] ? 0xc0a0c000 iwl_mvm_init+0x3a/0x1000 [iwlmvm] ? 0xc0a0c000 do_one_initcall+0x48/0x1d0 ? __cond_resched+0x19/0x30 ? kmem_cache_alloc_trace+0x37c/0x440 do_init_module+0x62/0x260 load_module+0x125d/0x1440 __do_sys_finit_module+0xc2/0x120 ? __do_sys_finit_module+0xc2/0x120 __x64_sys_finit_module+0x1a/0x20 do_syscall_64+0x61/0xb0 entry_SYSCALL_64_after_hwframe+0x44/0xae RIP: 0033:0x7f9084f5e89d Code: 00 c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d c3 f5 0c 00 f7 d8 64 89 01 48 RSP: 002b:7ffcb48505e8 EFLAGS: 0246 ORIG_RAX: 0139 RAX: ffda RBX: 55aa54753d20 RCX: 7f9084f5e89d RDX: RSI: 55aa52f0d358 RDI: 0002 RBP: 0004 R08: R09: R10: 0002 R11: 0246 R12: 55aa52f0d358 R13: R14: 55aa54753e50 R15: 55aa54753d20 Modules linked in: snd_soc_acpi snd_soc_core snd_compress ac97_bus snd_pcm_dmaengine snd_hda_intel snd_intel_dspcfg snd_intel_sdw_acpi zfs(PO+) snd_hda_codec snd_hda_core snd_hwdep snd_pcm snd_seq_midi zunicode(PO) snd_seq_midi_event zzstd(O) snd_rawmidi zlua(O) intel_rapl_m> usbhid hid_generic hid i915 i2c_algo_bit drm_kms_helper aesni_intel syscopyarea sysfillrect sysimgblt fb_sys_fops crypto_simd cec cryptd rc_core drm nvme psmouse nvme_core xhci_pci xhci_pci_renesas wmi video mac_hid CR2: 0017 ---[ end trace cae0adb6dc5e38f3 ]--- iwlwifi :02:00.0 wlp2s0: renamed from wlan0 RIP: 0010:iwl_mvm_dbgfs_register+0x660/0x6d0 [iwlmvm] Code: 29 c1 be 80 01 00 00 48 c7 c7 35 f8 29 c1 e8 27 b9 20 cd 48 8b 83 60 18 00 00 48 c7 c2 39 f8 29 c1 be 64 00 00 00 48 8d 7d 8c <48> 8b 48 18 e8 f7 07 36 cd 48 8b 43 28 48 8d 55 8c 48 c7 c7 44 f8 RSP: 0018:9e37c072bb08 EFLAGS: 00010206 RAX: RBX: 8b3fcb5e1f48 RCX: 8b3fcb5e1f48 RDX: c129f839 RSI: 0064 RDI: 9e37c072bb0c RBP: 9e37c072bb80 R08: 8f26c920 R09: c1298ae0 R10: 0100 R11: 0021 R12: R13: 000fffe0 R14: 8b3fcb5e1f48 R15: 8b3fcb5e1f40 FS: 7f9084e19540() GS:8b470ec8() knlGS: CS: 0010 DS: ES: CR0: 80050033 CR2: 0017 CR3: 0001048c8006 CR4: 003706e0 When booting 5.11.0-38-generic: ieee80211 phy0: Selected rate control algorithm 'iwl-mvm-rs' thermal thermal_zone3: failed to read out thermal zone (-61) BUG: kernel NULL pointer dereferen
[Kernel-packages] [Bug 1962831] Re: [UBUNTU 20.04] KVM: Enable storage key checking for intercepted instruction
** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1962831 Title: [UBUNTU 20.04] KVM: Enable storage key checking for intercepted instruction Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Committed Bug description: SRU Justification: == [Impact] * KVM uses lazy storage key enablement as Linux does no longer make use of the storage keys. When the guest enters keyed mode, then KVM will save/restore the key during paging, provide change/reference tracking for guest and host and for all interpreted instructions will do key protection. * If an instruction is intercepted and passed along to userspace (like QEMU) no storage key protection is checked, though. * But this is in violation of the architecture and it can result in misbehaving guests that rely on key protection for all instructions. * This item will improve the MEMOP ioctl to also add key checking. In case of a key protection the right fault is injected in the guest. [Fix] * The following changes since commit dbdbd581976f9dfcc9e21a777273b55bdb9bf138: UBUNTU: Ubuntu-5.4.0-102.115 (2022-02-23 15:32:05 +0100) are available in the Git repository at: https://git.launchpad.net/~fheimes/+git/lp1962831/ 16c0809cf1012e68279a8936a482c1d63cc4d14c for you to fetch changes up to 16c0809cf1012e68279a8936a482c1d63cc4d14c: KVM: s390: Add missing vm MEM_OP size check (2022-03-03 22:45:50 +0100) * Patches are upstream accepted (but some are as of today still in linux-next). * Notes on why the backports are needed are included in the provenance of the corresponding commit. [Test Case] * An IBM z13 or LinuxONE system is needed running Ubuntu Server 20.04 with QEMU/KVM setup. * These modification here are covered by the following three tests: * [kvm-unit-tests,v2] s390x: Test effect of storage keys on some instructions https://patchwork.kernel.org/project/kvm/patch/20220301095059.3026178-1-s...@linux.ibm.com/ * [PATCH v2 0/5] memop selftest for storage key checking https://lore.kernel.org/kvm/20220225155311.3540514-1-s...@linux.ibm.com/ * c7ef9ebbed20 "KVM: s390: selftests: Test TEST PROTECTION emulation" * The tests and the verification will be done by the IBM Z team. * On top a test build is available (see below). [Where problems could occur] * Issues with vm ioctl may occur due to the introduction of _vm_ioctl. * Tests may fail or may report wrong states due to the new TEST_FAIL macro in tests/utilities or due to new variants of GUEST_ASSERT in selftests. * Problems on gaccess might be caused due to the refactoring of gpa, length calculation, access address range check and the new access_guest_page helper function. * In uaccess issues may occur due to the introduction of the bit field for OAC specifier, that causes lot's but relatively straight forward changes or due to the new storage key checking functions copy_from/to_user_key functions. * Compile issues may happen if the changes in uaccess.h bout z10 features are erroneous. * Instructions that are emulated by KVM might be impacted due to the expanded storage key checking, that now covers intercepted instructions, too. This is the most significant modification in terms of size and complexity and therefore carries the highest risk. * MEM_OP IOCTL could be harmed due to the additional, but optional, storage key extension and checking, or the new size check and I/O emulation can be impacted due to the new vm IOCTL for key checked guest memory access. * Some tests were added to mitigate this, like the selftests TEST PROTECTION. * The renaming of the existing vcpu memop functions shouldn't be very harmful, since issues will already occur test build. * The rest are API documentation updates and clarifications. * Except two include/header changes and changes in tools/testing all other modifications are s390x specific [Other] * It was ensured that these changes are in jammy based on LP#1933179. __ Description: KVM uses lazy storage key enablement as Linux does no longer make use of the storage keys. When the guest enters keyed mode, then KVM will save/restore the key during paging, provide change/reference tracking for guest and host and for all interpreted instructions will do key protection. If an instruction is intercepted and passed along to userspace (like QEMU) no storage key protection is checked, though. This is in violation of the architecture and it can result in misbehaving guests that rely on key protection for all instructions. This item will add the missing key checking
[Kernel-packages] [Bug 1965002] Re: AWS: Hibernate resume crashes when platform changes
** Changed in: linux-aws (Ubuntu Focal) Status: In Progress => Fix Committed ** Changed in: linux-aws (Ubuntu Impish) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1965002 Title: AWS: Hibernate resume crashes when platform changes Status in linux-aws package in Ubuntu: Fix Committed Status in linux-aws source package in Focal: Fix Committed Status in linux-aws source package in Impish: Fix Committed Status in linux-aws source package in Jammy: Fix Committed Bug description: SRU Justification [Impact] At present, if a virt instance is hibernated and restarted in a different environment, the instance will crash. We have seen situations where customers have to enable support cases to recover an instance. The proposed patch is supposed to enable the kernel to detect the change and reboot the instance instead of crashing. In the ACPI specification; there is a 'hardware signature' field in the ACPI tables, and the OS can reboot cleanly if/when that signature changes, instead of attempting the resume and crashing. [Fix] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=74d9 https://lore.kernel.org/lkml/9099d8903e9b2b16daec712acc9aa533fe84d102.ca...@infradead.org/T/#u [Test Case] Hibernate an AWS instance, resume on a different platform. Positive test results from Amazon engineers. [Where things could go wrong] Resume currently crashes when a hibernated instance is migrated to a new machine. It can't get much worse, unless the initial hibernate fails. [Other Info] SF: #00330794 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1965002/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1965936] [NEW] package nvidia-dkms-510 510.47.03-0ubuntu0.20.04.1 failed to install/upgrade: installed nvidia-dkms-510 package post-installation script subprocess returned error
Public bug reported: I'm trying to install the nvidia drivers but an error keeps popping out ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-dkms-510 510.47.03-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.13.0-37.42~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-37-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Mar 22 14:14:12 2022 ErrorMessage: installed nvidia-dkms-510 package post-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2022-03-16 (6 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: nvidia-graphics-drivers-510 Title: package nvidia-dkms-510 510.47.03-0ubuntu0.20.04.1 failed to install/upgrade: installed nvidia-dkms-510 package post-installation script subprocess returned error exit status 10 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-510 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-510 in Ubuntu. https://bugs.launchpad.net/bugs/1965936 Title: package nvidia-dkms-510 510.47.03-0ubuntu0.20.04.1 failed to install/upgrade: installed nvidia-dkms-510 package post-installation script subprocess returned error exit status 10 Status in nvidia-graphics-drivers-510 package in Ubuntu: New Bug description: I'm trying to install the nvidia drivers but an error keeps popping out ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-dkms-510 510.47.03-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.13.0-37.42~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-37-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Mar 22 14:14:12 2022 ErrorMessage: installed nvidia-dkms-510 package post-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2022-03-16 (6 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: nvidia-graphics-drivers-510 Title: package nvidia-dkms-510 510.47.03-0ubuntu0.20.04.1 failed to install/upgrade: installed nvidia-dkms-510 package post-installation script subprocess returned error exit status 10 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-510/+bug/1965936/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1965927] Re: [Ubuntu 22.04] mpt3sas: Request to include latest bug fix patches
I don't see above bug fixes changes in the below jammy repository and hence raised this launchpad to consider these bug fixes, https://git.launchpad.net/~ubuntu- kernel/ubuntu/+source/linux/+git/jammy/log/drivers/scsi/mpt3sas?h=master- next ** Changed in: linux (Ubuntu) Status: Incomplete => Opinion -- 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/1965927 Title: [Ubuntu 22.04] mpt3sas: Request to include latest bug fix patches Status in linux package in Ubuntu: Opinion Bug description: Request to include below mpt3sas driver bug fix patches in Ubuntu 22.04 kernel. These patches got accepted by the upstream and please find the corresponding commit IDs as below, 5db207d66d mpt3sas: Fix incorrect 4gb boundary check ca23ac823c mpt3sas: Remove scsi_dma_map errors messages 9211faa39a scsi: mpt3sas: Update persistent trigger pages from sysfs interface Below is the summary of each of the above bug fix commits, 1. mpt3sas: Fix incorrect 4gb boundary check: Without this patch, driver was checking whether any of it's pool crosses the 4gb boundary or not using the pool's virtual address instead of using it's dma address. So some time driver may false positively assume that the pool as crossed the 4gb boundary region (as it observes that pool's virtual address is crossing the 4gb boundary) even though it is really not. 2. mpt3sas: Remove scsi_dma_map errors messages: When driver set the DMA mask to 32bit then we observe that the SWIOTLB bounce buffers are getting exhausted quickly. For most of the IOs driver observe that scsi_dma_map() API returned with failure status and hence driver was printing below error message. Since this error message is getting printed per IO and if user issues heavy IOs then we observe that kernel overwhelmed with this error message. Also we will observe the kernel panic when the serial console is enabled. So to limit this issue, we removed this error message though this patch. "scsi_dma_map failed: request for 1310720 bytes!" 3. mpt3sas: Update persistent trigger pages from sysfs interface: When user set's any diag buffer trigger conditions then driver has to save these trigger conditions in the controller Firmware's NVRAM region. So that when system reboots then driver can get these trigger conditions from Firmware's NVRAM region and set these trigger conditions automatically. so that user no need to set these conditions again. Without this patch driver was not not saving these user provided trigger conditions in the Firmware's NVRAM region. Please let me if I have missed to add any data. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1965927/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1960018] Re: Boot Failure - linux-image-5.13.0-28-generic | regression
Same error with kernel 5.13.0-37 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1960018 Title: Boot Failure - linux-image-5.13.0-28-generic | regression Status in linux-hwe-5.13 package in Ubuntu: Confirmed Bug description: Ubuntu 20.04.3 Installed since May 2020, now fails to boot into graphics mode after upgrade to kernel version linux-image-5.13.0-27-generic - Have tried linux-image-5.13.0-28-generic with same result, I have reverted back to 5.11.0.40 which works correctly. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: christian 1890 F pulseaudio /dev/snd/controlC0: christian 1890 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-06 (639 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 81MT Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-40-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-40.44~20.04.2-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-40-generic N/A linux-backports-modules-5.11.0-40-generic N/A linux-firmware 1.187.25 Tags: focal Uname: Linux 5.11.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/09/2019 dmi.bios.release: 2.23 dmi.bios.vendor: LENOVO dmi.bios.version: 8ZCN23WW(V2.02) dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: No DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo V145-15AST dmi.ec.firmware.release: 2.23 dmi.modalias: dmi:bvnLENOVO:bvr8ZCN23WW(V2.02):bd05/09/2019:br2.23:efr2.23:svnLENOVO:pn81MT:pvrLenovoV145-15AST:skuLENOVO_MT_81MT_BU_idea_FM_V145-15AST:rvnLENOVO:rnLNVNB161216:rvrNoDPK:cvnLENOVO:ct10:cvrLenovoV145-15AST: dmi.product.family: V145-15AST dmi.product.name: 81MT dmi.product.sku: LENOVO_MT_81MT_BU_idea_FM_V145-15AST dmi.product.version: Lenovo V145-15AST dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.13/+bug/1960018/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1965927] 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 1965927 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/1965927 Title: [Ubuntu 22.04] mpt3sas: Request to include latest bug fix patches Status in linux package in Ubuntu: Incomplete Bug description: Request to include below mpt3sas driver bug fix patches in Ubuntu 22.04 kernel. These patches got accepted by the upstream and please find the corresponding commit IDs as below, 5db207d66d mpt3sas: Fix incorrect 4gb boundary check ca23ac823c mpt3sas: Remove scsi_dma_map errors messages 9211faa39a scsi: mpt3sas: Update persistent trigger pages from sysfs interface Below is the summary of each of the above bug fix commits, 1. mpt3sas: Fix incorrect 4gb boundary check: Without this patch, driver was checking whether any of it's pool crosses the 4gb boundary or not using the pool's virtual address instead of using it's dma address. So some time driver may false positively assume that the pool as crossed the 4gb boundary region (as it observes that pool's virtual address is crossing the 4gb boundary) even though it is really not. 2. mpt3sas: Remove scsi_dma_map errors messages: When driver set the DMA mask to 32bit then we observe that the SWIOTLB bounce buffers are getting exhausted quickly. For most of the IOs driver observe that scsi_dma_map() API returned with failure status and hence driver was printing below error message. Since this error message is getting printed per IO and if user issues heavy IOs then we observe that kernel overwhelmed with this error message. Also we will observe the kernel panic when the serial console is enabled. So to limit this issue, we removed this error message though this patch. "scsi_dma_map failed: request for 1310720 bytes!" 3. mpt3sas: Update persistent trigger pages from sysfs interface: When user set's any diag buffer trigger conditions then driver has to save these trigger conditions in the controller Firmware's NVRAM region. So that when system reboots then driver can get these trigger conditions from Firmware's NVRAM region and set these trigger conditions automatically. so that user no need to set these conditions again. Without this patch driver was not not saving these user provided trigger conditions in the Firmware's NVRAM region. Please let me if I have missed to add any data. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1965927/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1965927] [NEW] [Ubuntu 22.04] mpt3sas: Request to include latest bug fix patches
Public bug reported: Request to include below mpt3sas driver bug fix patches in Ubuntu 22.04 kernel. These patches got accepted by the upstream and please find the corresponding commit IDs as below, 5db207d66d mpt3sas: Fix incorrect 4gb boundary check ca23ac823c mpt3sas: Remove scsi_dma_map errors messages 9211faa39a scsi: mpt3sas: Update persistent trigger pages from sysfs interface Below is the summary of each of the above bug fix commits, 1. mpt3sas: Fix incorrect 4gb boundary check: Without this patch, driver was checking whether any of it's pool crosses the 4gb boundary or not using the pool's virtual address instead of using it's dma address. So some time driver may false positively assume that the pool as crossed the 4gb boundary region (as it observes that pool's virtual address is crossing the 4gb boundary) even though it is really not. 2. mpt3sas: Remove scsi_dma_map errors messages: When driver set the DMA mask to 32bit then we observe that the SWIOTLB bounce buffers are getting exhausted quickly. For most of the IOs driver observe that scsi_dma_map() API returned with failure status and hence driver was printing below error message. Since this error message is getting printed per IO and if user issues heavy IOs then we observe that kernel overwhelmed with this error message. Also we will observe the kernel panic when the serial console is enabled. So to limit this issue, we removed this error message though this patch. "scsi_dma_map failed: request for 1310720 bytes!" 3. mpt3sas: Update persistent trigger pages from sysfs interface: When user set's any diag buffer trigger conditions then driver has to save these trigger conditions in the controller Firmware's NVRAM region. So that when system reboots then driver can get these trigger conditions from Firmware's NVRAM region and set these trigger conditions automatically. so that user no need to set these conditions again. Without this patch driver was not not saving these user provided trigger conditions in the Firmware's NVRAM region. Please let me if I have missed to add any data. ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1965927 Title: [Ubuntu 22.04] mpt3sas: Request to include latest bug fix patches Status in linux package in Ubuntu: Incomplete Bug description: Request to include below mpt3sas driver bug fix patches in Ubuntu 22.04 kernel. These patches got accepted by the upstream and please find the corresponding commit IDs as below, 5db207d66d mpt3sas: Fix incorrect 4gb boundary check ca23ac823c mpt3sas: Remove scsi_dma_map errors messages 9211faa39a scsi: mpt3sas: Update persistent trigger pages from sysfs interface Below is the summary of each of the above bug fix commits, 1. mpt3sas: Fix incorrect 4gb boundary check: Without this patch, driver was checking whether any of it's pool crosses the 4gb boundary or not using the pool's virtual address instead of using it's dma address. So some time driver may false positively assume that the pool as crossed the 4gb boundary region (as it observes that pool's virtual address is crossing the 4gb boundary) even though it is really not. 2. mpt3sas: Remove scsi_dma_map errors messages: When driver set the DMA mask to 32bit then we observe that the SWIOTLB bounce buffers are getting exhausted quickly. For most of the IOs driver observe that scsi_dma_map() API returned with failure status and hence driver was printing below error message. Since this error message is getting printed per IO and if user issues heavy IOs then we observe that kernel overwhelmed with this error message. Also we will observe the kernel panic when the serial console is enabled. So to limit this issue, we removed this error message though this patch. "scsi_dma_map failed: request for 1310720 bytes!" 3. mpt3sas: Update persistent trigger pages from sysfs interface: When user set's any diag buffer trigger conditions then driver has to save these trigger conditions in the controller Firmware's NVRAM region. So that when system reboots then driver can get these trigger conditions from Firmware's NVRAM region and set these trigger conditions automatically. so that user no need to set these conditions again. Without this patch driver was not not saving these user provided trigger conditions in the Firmware's NVRAM region. Please let me if I have missed to add any data. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1965927/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1965467] Re: Need to reset MT7921 BT when the firmware hang or command no response
** Changed in: linux-oem-5.14 (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-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1965467 Title: Need to reset MT7921 BT when the firmware hang or command no response Status in HWE Next: New Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.14 source package in Focal: Fix Committed Bug description: [Impact] Encounter BT command timeout issue when doing reboot test, and BT becomes unusable. Mar 15 22:04:44 u-Inspiron-15-3525 kernel: [ 463.633675] usb 3-4: reset high-speed USB device number 3 using xhci_hcd Mar 15 22:04:45 u-Inspiron-15-3525 kernel: [ 465.027012] Bluetooth: hci0: command 0x2005 tx timeout Mar 15 22:04:47 u-Inspiron-15-3525 kernel: [ 467.043176] Bluetooth: hci0: command 0x2041 tx timeout [Fix] Backport below 2 commit from v5.15-rc1 fix this issue e947802657cb Bluetooth: btusb: Support Bluetooth Reset for Mediatek Chip(MT7921) 0b10c8c84c0c Bluetooth: btusb: Record debug log for Mediatek Chip. [Test] Verified on the problem machine, and confirmed it works [Where problems could occur] It adds a new function to cmd_timeout callback, so it won't affect old behaviors. This only affects the chip which has command timeout issue, and could reset the chip when encounter the issue. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1965467/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1965882] Re: [nouveau] External monitor plugged into (secondary) Nvidia GPU is all white (plus a little flicker)
** Summary changed: - [nouveau] External monitor plugged into Nvidia GPU is all white (plus a little flicker) + [nouveau] External monitor plugged into (secondary) Nvidia GPU is all white (plus a little flicker) ** Description changed: - External monitor plugged into Nvidia GPU is all white (plus a little - flicker) for gnome-shell/mutter when using nouveau. + External monitor plugged into (secondary) Nvidia GPU is all white (plus + a little flicker) for gnome-shell/mutter when using nouveau. The primary + GPU (i915) still works fine. This seems to be a kernel regression... FAIL: 5.17.0-051700drmtip20220322-generic FAIL: 5.17.0-051700-generic FAIL: 5.15.0-23-generic FAIL: 5.14.21-051421-generic PASS: 5.14.20-051420-generic PASS: 5.14.18-051418-generic PASS: 5.14.15-051415-generic PASS: 5.14.10-051410-generic PASS: 5.14.0-051400-generic PASS: 5.13.19-051319-generic PASS: 5.10.107-0510107-generic ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-23-generic 5.15.0-23.23 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/by-id', '/dev/snd/controlC1', '/dev/snd/pcmC1D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass Date: Tue Mar 22 16:35:58 2022 InstallationDate: Installed on 2021-11-05 (136 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211103) MachineType: Intel(R) Client Systems NUC9i7QNX ProcFB: 0 i915drmfb 1 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic root=UUID=70e2069c-a553-4c6d-abfc-c65e52cb3b43 ro quiet splash nvidia-drm.modeset=1 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-23-generic N/A linux-backports-modules-5.15.0-23-generic N/A linux-firmware 20220314.gitcd01f857-0ubuntu2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/25/2019 dmi.bios.release: 5.13 dmi.bios.vendor: Intel Corp. dmi.bios.version: QXCFL579.0034.2019.1125.1436 dmi.board.name: NUC9i7QNB dmi.board.vendor: Intel Corporation dmi.board.version: K49245-402 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.ec.firmware.release: 24.33 dmi.modalias: dmi:bvnIntelCorp.:bvrQXCFL579.0034.2019.1125.1436:bd11/25/2019:br5.13:efr24.33:svnIntel(R)ClientSystems:pnNUC9i7QNX:pvrK49244-403:rvnIntelCorporation:rnNUC9i7QNB:rvrK49245-402:cvnIntelCorporation:ct35:cvr2.0:skuBXNUC9i7QNX: dmi.product.family: QN dmi.product.name: NUC9i7QNX dmi.product.sku: BXNUC9i7QNX dmi.product.version: K49244-403 dmi.sys.vendor: Intel(R) Client Systems -- 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/1965882 Title: [nouveau] External monitor plugged into (secondary) Nvidia GPU is all white (plus a little flicker) Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Bug description: External monitor plugged into (secondary) Nvidia GPU is all white (plus a little flicker) for gnome-shell/mutter when using nouveau. The primary GPU (i915) still works fine. This seems to be a kernel regression... FAIL: 5.17.0-051700drmtip20220322-generic FAIL: 5.17.0-051700-generic FAIL: 5.15.0-23-generic FAIL: 5.14.21-051421-generic PASS: 5.14.20-051420-generic PASS: 5.14.18-051418-generic PASS: 5.14.15-051415-generic PASS: 5.14.10-051410-generic PASS: 5.14.0-051400-generic PASS: 5.13.19-051319-generic PASS: 5.10.107-0510107-generic ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-23-generic 5.15.0-23.23 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/by-id', '/dev/snd/controlC1', '/dev/snd/pcmC1D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass Date: Tue Mar 22 16:35:58 2022 InstallationDate: Installed on 2021-11-05 (136 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211103) MachineType: Intel(R) Client Systems NUC9i7QNX ProcFB: 0 i915drmfb 1 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic root=UUID=70e2069c-a553-4c6d-abfc-c65e52cb3b43 ro quiet splash nvidia-drm.modeset=1 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-23-generic N/A linux-backports-modules-5.15.0-23-generic N/A linux-firmware 20220314.gitcd01f857-0ubuntu2 SourcePackage: linux UpgradeStatus
[Kernel-packages] [Bug 1849084] Re: Freeze on system-resume caused by kwin and amdgpu driver
After 23 months without this Standby/Resume bug, it has now reappeared - See #30 above System; Lenovo V155-15API (V155 Series) Processor; AMD Ryzen 5 3500U Graphics adapter; AMD Radeon RX Vega 8 Memory; 12288 MB (Windows partition) Dual booting Windows 10 & Ubuntu 20.04.4 LTS (Ubuntu being main OS on separate partition) Bug present under both Ubuntu & Windows In Windows I once again ran the AMD Driver Auto-detect tool & let it install the drivers it detected as needed or needing updating. This fixed the problem in April 2020 but it has had no effect in 2022. In the Windows partition Lenovo want to install a BIOS upgrade, but I'm concerned about possible effect on the dual boot. -- 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/1849084 Title: Freeze on system-resume caused by kwin and amdgpu driver Status in kwin package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in plasma-desktop package in Ubuntu: Confirmed Status in xserver-xorg-video-amdgpu package in Ubuntu: Confirmed Bug description: This is a well investigated bug by me. Problem: a black screen freeze occurs by suspend-resume process Ubuntu version: Kubuntu 19.10 default plasma, or the backported 5.17 Kernel version: default 5.3.10 or the mainline 5.4.0rc3 xserver-xorg-video-amdgpu: 19.* or the newest from git, the 18.0.1-1 works well This freeze can be reproduced only if opengl 2.0 or 3.1 compositor is enabled in Plasma settings. Xrender is OK however I don't like screen tearing. On Ubuntu 19.10 Gnome desktop (X based) this doesn't occur even if the Gnome's compositor is enabled. (I don't know what is the default one there but I haven't disabled it) I think this is a Kwin / amdgpu driver related bug because of the differentiation. These can be fixed even in Kwin/opengl compositor not just in the amdgpu driver or in kernel. One possible solution: disable opengl compositor by suspend and re- enable it after login. Use fe.: Xrender before login / before the system restored from suspend. For Ubuntu's maintainers: Couldn't be this problem solved by a downstream solution? Maybe a proper script could be enough by resume and by suspend. There are a lot of bugs like this reported in freedesktop bugreport and the developers haven't got enough time for fix them fast enough. Syslog: Oct 21 10:57:26 pc kernel: [ 9475.308852] Code: 85 78 ff ff ff e9 9f f8 ff ff 8b b0 98 04 00 00 48 c7 c7 ef 5f a5 c0 e8 49 2d 9d ff 44 0f b6 45 a3 49 8b 4d 08 e9 bf fa ff ff <0f> 0b e9 ca fb ff ff 0f 0b e8 7d 36 84 c1 66 66 2e 0f 1f 84 00 00 Oct 21 10:57:26 pc kernel: [ 9475.308853] RSP: 0018:b7b54274b7b0 EFLAGS: 00010002 Oct 21 10:57:26 pc kernel: [ 9475.308855] RAX: 0202 RBX: 0202 RCX: 046a Oct 21 10:57:26 pc kernel: [ 9475.308856] RDX: 0001 RSI: 0202 RDI: 0002 Oct 21 10:57:26 pc kernel: [ 9475.308857] RBP: b7b54274b870 R08: R09: 94da76b2d170 Oct 21 10:57:26 pc kernel: [ 9475.308858] R10: b7b54274b708 R11: b7b54274b70c R12: 94da76b2d000 Oct 21 10:57:26 pc kernel: [ 9475.308859] R13: 94d970f2c300 R14: 94da758d25d0 R15: 94da270d1400 Oct 21 10:57:26 pc kernel: [ 9475.308861] FS: 7f2a1b9bea80() GS:94da87c4() knlGS: Oct 21 10:57:26 pc kernel: [ 9475.308863] CS: 0010 DS: ES: CR0: 80050033 Oct 21 10:57:26 pc kernel: [ 9475.308864] CR2: 7fb083e9b4a5 CR3: 00012c11 CR4: 003406e0 Oct 21 10:57:26 pc kernel: [ 9475.308865] Call Trace: Oct 21 10:57:26 pc kernel: [ 9475.308977] amdgpu_dm_atomic_commit_tail+0x96f/0x1030 [amdgpu] Oct 21 10:57:26 pc kernel: [ 9475.308991] commit_tail+0x50/0xc0 [drm_kms_helper] Oct 21 10:57:26 pc kernel: [ 9475.309000] ? commit_tail+0x50/0xc0 [drm_kms_helper] Oct 21 10:57:26 pc kernel: [ 9475.309009] drm_atomic_helper_commit+0x118/0x120 [drm_kms_helper] Oct 21 10:57:26 pc kernel: [ 9475.309115] amdgpu_dm_atomic_commit+0x95/0xa0 [amdgpu] Oct 21 10:57:26 pc kernel: [ 9475.309135] drm_atomic_commit+0x4a/0x50 [drm] Oct 21 10:57:26 pc kernel: [ 9475.309144] drm_atomic_helper_set_config+0x89/0xa0 [drm_kms_helper] Oct 21 10:57:26 pc kernel: [ 9475.309159] drm_mode_setcrtc+0x1cd/0x7a0 [drm] Oct 21 10:57:26 pc kernel: [ 9475.309234] ? amdgpu_cs_wait_ioctl+0xd6/0x150 [amdgpu] Oct 21 10:57:26 pc kernel: [ 9475.309249] ? drm_mode_getcrtc+0x190/0x190 [drm] Oct 21 10:57:26 pc kernel: [ 9475.309262] drm_ioctl_kernel+0xae/0xf0 [drm] Oct 21 10:57:26 pc kernel: [ 9475.309276] drm_ioctl+0x234/0x3d0 [drm] Oct 21 10:57:26 pc kernel: [ 9475.309290] ? drm_mode_getcrtc+0x190/0x190 [drm] Oct 21 10:57:26 pc kernel: [ 9475.309370] amdgpu_drm_ioctl+0x4e/0x80 [amdgpu] Oct 21 10:57:26 pc kernel: [ 9475.30
[Kernel-packages] [Bug 1965882] Re: [nouveau] External monitor plugged into Nvidia GPU is all white (plus a little flicker)
** Bug watch added: gitlab.freedesktop.org/drm/nouveau/-/issues #166 https://gitlab.freedesktop.org/drm/nouveau/-/issues/166 ** Also affects: linux via https://gitlab.freedesktop.org/drm/nouveau/-/issues/166 Importance: Unknown Status: Unknown -- 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/1965882 Title: [nouveau] External monitor plugged into Nvidia GPU is all white (plus a little flicker) Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Bug description: External monitor plugged into Nvidia GPU is all white (plus a little flicker) for gnome-shell/mutter when using nouveau. This seems to be a kernel regression... FAIL: 5.17.0-051700drmtip20220322-generic FAIL: 5.17.0-051700-generic FAIL: 5.15.0-23-generic FAIL: 5.14.21-051421-generic PASS: 5.14.20-051420-generic PASS: 5.14.18-051418-generic PASS: 5.14.15-051415-generic PASS: 5.14.10-051410-generic PASS: 5.14.0-051400-generic PASS: 5.13.19-051319-generic PASS: 5.10.107-0510107-generic ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-23-generic 5.15.0-23.23 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/by-id', '/dev/snd/controlC1', '/dev/snd/pcmC1D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass Date: Tue Mar 22 16:35:58 2022 InstallationDate: Installed on 2021-11-05 (136 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211103) MachineType: Intel(R) Client Systems NUC9i7QNX ProcFB: 0 i915drmfb 1 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic root=UUID=70e2069c-a553-4c6d-abfc-c65e52cb3b43 ro quiet splash nvidia-drm.modeset=1 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-23-generic N/A linux-backports-modules-5.15.0-23-generic N/A linux-firmware 20220314.gitcd01f857-0ubuntu2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/25/2019 dmi.bios.release: 5.13 dmi.bios.vendor: Intel Corp. dmi.bios.version: QXCFL579.0034.2019.1125.1436 dmi.board.name: NUC9i7QNB dmi.board.vendor: Intel Corporation dmi.board.version: K49245-402 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.ec.firmware.release: 24.33 dmi.modalias: dmi:bvnIntelCorp.:bvrQXCFL579.0034.2019.1125.1436:bd11/25/2019:br5.13:efr24.33:svnIntel(R)ClientSystems:pnNUC9i7QNX:pvrK49244-403:rvnIntelCorporation:rnNUC9i7QNB:rvrK49245-402:cvnIntelCorporation:ct35:cvr2.0:skuBXNUC9i7QNX: dmi.product.family: QN dmi.product.name: NUC9i7QNX dmi.product.sku: BXNUC9i7QNX dmi.product.version: K49244-403 dmi.sys.vendor: Intel(R) Client Systems To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1965882/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1896311] Re: Missing module ptp_kvm.ko in linux-modules-*-kvm
Been hit with this too using locked down environments, (ie. ntp not allowed) and sycning to host's kernel using ptp_kvm had been highly succesful for all other Debian & RedHat based systems except Ubuntu ;( -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1896311 Title: Missing module ptp_kvm.ko in linux-modules-*-kvm Status in linux-kvm package in Ubuntu: New Bug description: The kernel module ptp_kvm.po is for syncing the time between VM and host in a KVM environment. BUT: this module is missing in the -kvm kernel or module flavored packages. It *IS* inside these packages: /lib/modules/5.4.0-1009-aws/kernel/drivers/ptp/ptp_kvm.ko linux-modules-extra-5.4.0-1009-aws /lib/modules/5.4.0-1009-gcp/kernel/drivers/ptp/ptp_kvm.ko linux-modules-extra-5.4.0-1009-gcp /lib/modules/5.4.0-1009-oracle/kernel/drivers/ptp/ptp_kvm.ko linux-modules-extra-5.4.0-1009-oracle /lib/modules/5.4.0-1010-azure/kernel/drivers/ptp/ptp_kvm.ko linux-modules-extra-5.4.0-1010-azure /lib/modules/5.4.0-26-generic/kernel/drivers/ptp/ptp_kvm.ko linux-modules-extra-5.4.0-26-generic /lib/modules/5.4.0-26-lowlatency/kernel/drivers/ptp/ptp_kvm.ko linux-modules-5.4.0-26-lowlatency /lib/modules/5.6.0-1007-oem/kernel/drivers/ptp/ptp_kvm.ko linux-modules-5.6.0-1007-oem For me it looks that the module should also in the linux-modules-*-kvm package which would make a lot sense. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-kvm/+bug/1896311/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1965882] Re: [nouveau] External monitor plugged into Nvidia GPU is all white (plus a little flicker)
** Description changed: External monitor plugged into Nvidia GPU is all white (plus a little flicker) for gnome-shell/mutter when using nouveau. This seems to be a kernel regression... FAIL: 5.17.0-051700-generic FAIL: 5.15.0-23-generic FAIL: 5.14.21-051421-generic + PASS: 5.14.18-051418-generic PASS: 5.14.15-051415-generic PASS: 5.14.10-051410-generic PASS: 5.14.0-051400-generic PASS: 5.13.19-051319-generic PASS: 5.10.107-0510107-generic ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-23-generic 5.15.0-23.23 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/by-id', '/dev/snd/controlC1', '/dev/snd/pcmC1D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass Date: Tue Mar 22 16:35:58 2022 InstallationDate: Installed on 2021-11-05 (136 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211103) MachineType: Intel(R) Client Systems NUC9i7QNX ProcFB: 0 i915drmfb 1 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic root=UUID=70e2069c-a553-4c6d-abfc-c65e52cb3b43 ro quiet splash nvidia-drm.modeset=1 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-23-generic N/A linux-backports-modules-5.15.0-23-generic N/A linux-firmware 20220314.gitcd01f857-0ubuntu2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/25/2019 dmi.bios.release: 5.13 dmi.bios.vendor: Intel Corp. dmi.bios.version: QXCFL579.0034.2019.1125.1436 dmi.board.name: NUC9i7QNB dmi.board.vendor: Intel Corporation dmi.board.version: K49245-402 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.ec.firmware.release: 24.33 dmi.modalias: dmi:bvnIntelCorp.:bvrQXCFL579.0034.2019.1125.1436:bd11/25/2019:br5.13:efr24.33:svnIntel(R)ClientSystems:pnNUC9i7QNX:pvrK49244-403:rvnIntelCorporation:rnNUC9i7QNB:rvrK49245-402:cvnIntelCorporation:ct35:cvr2.0:skuBXNUC9i7QNX: dmi.product.family: QN dmi.product.name: NUC9i7QNX dmi.product.sku: BXNUC9i7QNX dmi.product.version: K49244-403 dmi.sys.vendor: Intel(R) Client Systems ** Description changed: External monitor plugged into Nvidia GPU is all white (plus a little flicker) for gnome-shell/mutter when using nouveau. This seems to be a kernel regression... FAIL: 5.17.0-051700-generic FAIL: 5.15.0-23-generic FAIL: 5.14.21-051421-generic + PASS: 5.14.20-051420-generic PASS: 5.14.18-051418-generic PASS: 5.14.15-051415-generic PASS: 5.14.10-051410-generic PASS: 5.14.0-051400-generic PASS: 5.13.19-051319-generic PASS: 5.10.107-0510107-generic ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-23-generic 5.15.0-23.23 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/by-id', '/dev/snd/controlC1', '/dev/snd/pcmC1D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass Date: Tue Mar 22 16:35:58 2022 InstallationDate: Installed on 2021-11-05 (136 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211103) MachineType: Intel(R) Client Systems NUC9i7QNX ProcFB: 0 i915drmfb 1 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic root=UUID=70e2069c-a553-4c6d-abfc-c65e52cb3b43 ro quiet splash nvidia-drm.modeset=1 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-23-generic N/A linux-backports-modules-5.15.0-23-generic N/A linux-firmware 20220314.gitcd01f857-0ubuntu2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/25/2019 dmi.bios.release: 5.13 dmi.bios.vendor: Intel Corp. dmi.bios.version: QXCFL579.0034.2019.1125.1436 dmi.board.name: NUC9i7QNB dmi.board.vendor: Intel Corporation dmi.board.version: K49245-402 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.ec.firmware.release: 24.33 dmi.modalias: dmi:bvnIntelCorp.:bvrQXCFL579.0034.2019.1125.1436:bd11/25/2019:br5.13:efr24.33:svnIntel(R)ClientSystems:pnNUC9i7QNX:pvrK49244-403:rvnIntelCorporation:rnNUC9i7QNB:rvrK49245-402:cvnIntelCorporation:ct35:cvr2.0:skuBXNUC9i7QNX: dmi.product.family: QN dmi.product.name: NUC9i7QNX dmi.product.sku: BXNUC9i7QNX dmi.product.version: K49244-403 dmi.sys.vendor: Intel(R) Client Systems ** Description changed: External monitor plugged into Nvidia GPU is all white (plus a little fl
[Kernel-packages] [Bug 1965882] Re: [nouveau] External monitor plugged into Nvidia GPU is all white (plus a little flicker)
** Description changed: External monitor plugged into Nvidia GPU is all white (plus a little flicker) for gnome-shell/mutter when using nouveau. This seems to be a kernel regression... FAIL: 5.17.0-051700-generic FAIL: 5.15.0-23-generic FAIL: 5.14.21-051421-generic + PASS: 5.14.10-051410-generic PASS: 5.14.0-051400-generic PASS: 5.13.19-051319-generic PASS: 5.10.107-0510107-generic I'll update the above list in future. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-23-generic 5.15.0-23.23 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/by-id', '/dev/snd/controlC1', '/dev/snd/pcmC1D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass Date: Tue Mar 22 16:35:58 2022 InstallationDate: Installed on 2021-11-05 (136 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211103) MachineType: Intel(R) Client Systems NUC9i7QNX ProcFB: 0 i915drmfb 1 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic root=UUID=70e2069c-a553-4c6d-abfc-c65e52cb3b43 ro quiet splash nvidia-drm.modeset=1 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-23-generic N/A linux-backports-modules-5.15.0-23-generic N/A linux-firmware 20220314.gitcd01f857-0ubuntu2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/25/2019 dmi.bios.release: 5.13 dmi.bios.vendor: Intel Corp. dmi.bios.version: QXCFL579.0034.2019.1125.1436 dmi.board.name: NUC9i7QNB dmi.board.vendor: Intel Corporation dmi.board.version: K49245-402 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.ec.firmware.release: 24.33 dmi.modalias: dmi:bvnIntelCorp.:bvrQXCFL579.0034.2019.1125.1436:bd11/25/2019:br5.13:efr24.33:svnIntel(R)ClientSystems:pnNUC9i7QNX:pvrK49244-403:rvnIntelCorporation:rnNUC9i7QNB:rvrK49245-402:cvnIntelCorporation:ct35:cvr2.0:skuBXNUC9i7QNX: dmi.product.family: QN dmi.product.name: NUC9i7QNX dmi.product.sku: BXNUC9i7QNX dmi.product.version: K49244-403 dmi.sys.vendor: Intel(R) Client Systems ** Description changed: External monitor plugged into Nvidia GPU is all white (plus a little flicker) for gnome-shell/mutter when using nouveau. This seems to be a kernel regression... FAIL: 5.17.0-051700-generic FAIL: 5.15.0-23-generic FAIL: 5.14.21-051421-generic + PASS: 5.14.15-051415-generic PASS: 5.14.10-051410-generic PASS: 5.14.0-051400-generic PASS: 5.13.19-051319-generic PASS: 5.10.107-0510107-generic - - I'll update the above list in future. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-23-generic 5.15.0-23.23 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/by-id', '/dev/snd/controlC1', '/dev/snd/pcmC1D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass Date: Tue Mar 22 16:35:58 2022 InstallationDate: Installed on 2021-11-05 (136 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211103) MachineType: Intel(R) Client Systems NUC9i7QNX ProcFB: 0 i915drmfb 1 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic root=UUID=70e2069c-a553-4c6d-abfc-c65e52cb3b43 ro quiet splash nvidia-drm.modeset=1 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-23-generic N/A linux-backports-modules-5.15.0-23-generic N/A linux-firmware 20220314.gitcd01f857-0ubuntu2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/25/2019 dmi.bios.release: 5.13 dmi.bios.vendor: Intel Corp. dmi.bios.version: QXCFL579.0034.2019.1125.1436 dmi.board.name: NUC9i7QNB dmi.board.vendor: Intel Corporation dmi.board.version: K49245-402 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.ec.firmware.release: 24.33 dmi.modalias: dmi:bvnIntelCorp.:bvrQXCFL579.0034.2019.1125.1436:bd11/25/2019:br5.13:efr24.33:svnIntel(R)ClientSystems:pnNUC9i7QNX:pvrK49244-403:rvnIntelCorporation:rnNUC9i7QNB:rvrK49245-402:cvnIntelCorporation:ct35:cvr2.0:skuBXNUC9i7QNX: dmi.product.family: QN dmi.product.name: NUC9i7QNX dmi.product.sku: BXNUC9i7QNX dmi.product.version: K49244-403 dmi.sys.vendor: Intel(R) Client Systems -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.l
[Kernel-packages] [Bug 1965882] Re: [nouveau] External monitor plugged into Nvidia GPU is all white (plus a little flicker)
** Description changed: External monitor plugged into Nvidia GPU is all white (plus a little flicker) for gnome-shell/mutter when using nouveau. This seems to be a kernel regression... FAIL: 5.17.0-051700-generic FAIL: 5.15.0-23-generic FAIL: 5.14.21-051421-generic + PASS: 5.14.0-051400-generic PASS: 5.13.19-051319-generic PASS: 5.10.107-0510107-generic I'll update the above list in future. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-23-generic 5.15.0-23.23 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/by-id', '/dev/snd/controlC1', '/dev/snd/pcmC1D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass Date: Tue Mar 22 16:35:58 2022 InstallationDate: Installed on 2021-11-05 (136 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211103) MachineType: Intel(R) Client Systems NUC9i7QNX ProcFB: 0 i915drmfb 1 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic root=UUID=70e2069c-a553-4c6d-abfc-c65e52cb3b43 ro quiet splash nvidia-drm.modeset=1 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-23-generic N/A linux-backports-modules-5.15.0-23-generic N/A linux-firmware 20220314.gitcd01f857-0ubuntu2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/25/2019 dmi.bios.release: 5.13 dmi.bios.vendor: Intel Corp. dmi.bios.version: QXCFL579.0034.2019.1125.1436 dmi.board.name: NUC9i7QNB dmi.board.vendor: Intel Corporation dmi.board.version: K49245-402 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.ec.firmware.release: 24.33 dmi.modalias: dmi:bvnIntelCorp.:bvrQXCFL579.0034.2019.1125.1436:bd11/25/2019:br5.13:efr24.33:svnIntel(R)ClientSystems:pnNUC9i7QNX:pvrK49244-403:rvnIntelCorporation:rnNUC9i7QNB:rvrK49245-402:cvnIntelCorporation:ct35:cvr2.0:skuBXNUC9i7QNX: dmi.product.family: QN dmi.product.name: NUC9i7QNX dmi.product.sku: BXNUC9i7QNX dmi.product.version: K49244-403 dmi.sys.vendor: Intel(R) Client Systems -- 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/1965882 Title: [nouveau] External monitor plugged into Nvidia GPU is all white (plus a little flicker) Status in linux package in Ubuntu: Confirmed Bug description: External monitor plugged into Nvidia GPU is all white (plus a little flicker) for gnome-shell/mutter when using nouveau. This seems to be a kernel regression... FAIL: 5.17.0-051700-generic FAIL: 5.15.0-23-generic FAIL: 5.14.21-051421-generic PASS: 5.14.0-051400-generic PASS: 5.13.19-051319-generic PASS: 5.10.107-0510107-generic I'll update the above list in future. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-23-generic 5.15.0-23.23 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/by-id', '/dev/snd/controlC1', '/dev/snd/pcmC1D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass Date: Tue Mar 22 16:35:58 2022 InstallationDate: Installed on 2021-11-05 (136 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211103) MachineType: Intel(R) Client Systems NUC9i7QNX ProcFB: 0 i915drmfb 1 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic root=UUID=70e2069c-a553-4c6d-abfc-c65e52cb3b43 ro quiet splash nvidia-drm.modeset=1 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-23-generic N/A linux-backports-modules-5.15.0-23-generic N/A linux-firmware 20220314.gitcd01f857-0ubuntu2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/25/2019 dmi.bios.release: 5.13 dmi.bios.vendor: Intel Corp. dmi.bios.version: QXCFL579.0034.2019.1125.1436 dmi.board.name: NUC9i7QNB dmi.board.vendor: Intel Corporation dmi.board.version: K49245-402 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.ec.firmware.release: 24.33 dmi.modalias: dmi:bvnIntelCorp.:bvrQXCFL579.0034.2019.1125.1436:bd11/25/2019:br5.13:efr24.33:svnIntel(R)ClientSystems:pnNUC9i7QNX:pvrK49244-403:rvnIntelCorporation:rnNUC9i7QNB:rvrK49245-402:cvnIntelCorporation:ct35:cvr2.0:skuBXNUC9i7QNX: dmi.product.family: QN dmi.product.name: NUC9i7QNX dmi.product.sku: BXNUC9i7QNX dmi.produ
[Kernel-packages] [Bug 1965882] 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/1965882 Title: [nouveau] External monitor plugged into Nvidia GPU is all white (plus a little flicker) Status in linux package in Ubuntu: Confirmed Bug description: External monitor plugged into Nvidia GPU is all white (plus a little flicker) for gnome-shell/mutter when using nouveau. This seems to be a kernel regression... FAIL: 5.17.0-051700-generic FAIL: 5.15.0-23-generic FAIL: 5.14.21-051421-generic PASS: 5.14.0-051400-generic PASS: 5.13.19-051319-generic PASS: 5.10.107-0510107-generic I'll update the above list in future. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-23-generic 5.15.0-23.23 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/by-id', '/dev/snd/controlC1', '/dev/snd/pcmC1D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass Date: Tue Mar 22 16:35:58 2022 InstallationDate: Installed on 2021-11-05 (136 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211103) MachineType: Intel(R) Client Systems NUC9i7QNX ProcFB: 0 i915drmfb 1 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic root=UUID=70e2069c-a553-4c6d-abfc-c65e52cb3b43 ro quiet splash nvidia-drm.modeset=1 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-23-generic N/A linux-backports-modules-5.15.0-23-generic N/A linux-firmware 20220314.gitcd01f857-0ubuntu2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/25/2019 dmi.bios.release: 5.13 dmi.bios.vendor: Intel Corp. dmi.bios.version: QXCFL579.0034.2019.1125.1436 dmi.board.name: NUC9i7QNB dmi.board.vendor: Intel Corporation dmi.board.version: K49245-402 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.ec.firmware.release: 24.33 dmi.modalias: dmi:bvnIntelCorp.:bvrQXCFL579.0034.2019.1125.1436:bd11/25/2019:br5.13:efr24.33:svnIntel(R)ClientSystems:pnNUC9i7QNX:pvrK49244-403:rvnIntelCorporation:rnNUC9i7QNB:rvrK49245-402:cvnIntelCorporation:ct35:cvr2.0:skuBXNUC9i7QNX: dmi.product.family: QN dmi.product.name: NUC9i7QNX dmi.product.sku: BXNUC9i7QNX dmi.product.version: K49244-403 dmi.sys.vendor: Intel(R) Client Systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1965882/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1965884] [NEW] nvidia-kernel-source-460 460.73.01-0ubuntu0.20.04.1: nvidia kernel module failed to build
Public bug reported: I got an error message from Ubuntu. I don't know if it is related, but before getting the error message, I tried to launch Firefox, but instead of a browser window, there appeared a black rectangle with transparent inside. The rectangle seemed to contain an invisible Firefox window, because clicking on the top right corner (where the "x" button would be) made it disappear. I tried to launch it several times, and the same behavior persisted. At the last launch, the browser opened normally again. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-kernel-source-460 460.73.01-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.13.0-35.40~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip DKMSKernelVersion: 5.13.0-37-generic Date: Tue Mar 22 10:14:55 2022 Dependencies: DuplicateSignature: dkms:nvidia-kernel-source-460:460.73.01-0ubuntu0.20.04.1:/var/lib/dkms/nvidia/460.73.01/build/nvidia-drm/nvidia-drm-crtc.c:311:23: error: initialization of ‘int (*)(struct drm_plane *, struct drm_atomic_state *)’ from incompatible pointer type ‘int (*)(struct drm_plane *, struct drm_plane_state *)’ [-Werror=incompatible-pointer-types] InstallationDate: Installed on 2021-03-23 (363 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageVersion: 460.73.01-0ubuntu0.20.04.1 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.5 SourcePackage: nvidia-graphics-drivers-460 Title: nvidia-kernel-source-460 460.73.01-0ubuntu0.20.04.1: nvidia kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-460 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal need-duplicate-check -- 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/1965884 Title: nvidia-kernel-source-460 460.73.01-0ubuntu0.20.04.1: nvidia kernel module failed to build Status in nvidia-graphics-drivers-460 package in Ubuntu: New Bug description: I got an error message from Ubuntu. I don't know if it is related, but before getting the error message, I tried to launch Firefox, but instead of a browser window, there appeared a black rectangle with transparent inside. The rectangle seemed to contain an invisible Firefox window, because clicking on the top right corner (where the "x" button would be) made it disappear. I tried to launch it several times, and the same behavior persisted. At the last launch, the browser opened normally again. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-kernel-source-460 460.73.01-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.13.0-35.40~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip DKMSKernelVersion: 5.13.0-37-generic Date: Tue Mar 22 10:14:55 2022 Dependencies: DuplicateSignature: dkms:nvidia-kernel-source-460:460.73.01-0ubuntu0.20.04.1:/var/lib/dkms/nvidia/460.73.01/build/nvidia-drm/nvidia-drm-crtc.c:311:23: error: initialization of ‘int (*)(struct drm_plane *, struct drm_atomic_state *)’ from incompatible pointer type ‘int (*)(struct drm_plane *, struct drm_plane_state *)’ [-Werror=incompatible-pointer-types] InstallationDate: Installed on 2021-03-23 (363 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageVersion: 460.73.01-0ubuntu0.20.04.1 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.5 SourcePackage: nvidia-graphics-drivers-460 Title: nvidia-kernel-source-460 460.73.01-0ubuntu0.20.04.1: nvidia kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-460/+bug/1965884/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1965882] Re: [nouveau] External monitor plugged into Nvidia GPU is all white (plus a little flicker)
** Description changed: External monitor plugged into Nvidia GPU is all white (plus a little flicker) for gnome-shell/mutter when using nouveau. This seems to be a kernel regression... FAIL: 5.17.0-051700-generic FAIL: 5.15.0-23-generic + FAIL: 5.14.21-051421-generic PASS: 5.13.19-051319-generic PASS: 5.10.107-0510107-generic I'll update the above list in future. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-23-generic 5.15.0-23.23 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/by-id', '/dev/snd/controlC1', '/dev/snd/pcmC1D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass Date: Tue Mar 22 16:35:58 2022 InstallationDate: Installed on 2021-11-05 (136 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211103) MachineType: Intel(R) Client Systems NUC9i7QNX ProcFB: 0 i915drmfb 1 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic root=UUID=70e2069c-a553-4c6d-abfc-c65e52cb3b43 ro quiet splash nvidia-drm.modeset=1 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-23-generic N/A linux-backports-modules-5.15.0-23-generic N/A linux-firmware 20220314.gitcd01f857-0ubuntu2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/25/2019 dmi.bios.release: 5.13 dmi.bios.vendor: Intel Corp. dmi.bios.version: QXCFL579.0034.2019.1125.1436 dmi.board.name: NUC9i7QNB dmi.board.vendor: Intel Corporation dmi.board.version: K49245-402 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.ec.firmware.release: 24.33 dmi.modalias: dmi:bvnIntelCorp.:bvrQXCFL579.0034.2019.1125.1436:bd11/25/2019:br5.13:efr24.33:svnIntel(R)ClientSystems:pnNUC9i7QNX:pvrK49244-403:rvnIntelCorporation:rnNUC9i7QNB:rvrK49245-402:cvnIntelCorporation:ct35:cvr2.0:skuBXNUC9i7QNX: dmi.product.family: QN dmi.product.name: NUC9i7QNX dmi.product.sku: BXNUC9i7QNX dmi.product.version: K49244-403 dmi.sys.vendor: Intel(R) Client Systems -- 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/1965882 Title: [nouveau] External monitor plugged into Nvidia GPU is all white (plus a little flicker) Status in linux package in Ubuntu: Confirmed Bug description: External monitor plugged into Nvidia GPU is all white (plus a little flicker) for gnome-shell/mutter when using nouveau. This seems to be a kernel regression... FAIL: 5.17.0-051700-generic FAIL: 5.15.0-23-generic FAIL: 5.14.21-051421-generic PASS: 5.13.19-051319-generic PASS: 5.10.107-0510107-generic I'll update the above list in future. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-23-generic 5.15.0-23.23 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/by-id', '/dev/snd/controlC1', '/dev/snd/pcmC1D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass Date: Tue Mar 22 16:35:58 2022 InstallationDate: Installed on 2021-11-05 (136 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211103) MachineType: Intel(R) Client Systems NUC9i7QNX ProcFB: 0 i915drmfb 1 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic root=UUID=70e2069c-a553-4c6d-abfc-c65e52cb3b43 ro quiet splash nvidia-drm.modeset=1 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-23-generic N/A linux-backports-modules-5.15.0-23-generic N/A linux-firmware 20220314.gitcd01f857-0ubuntu2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/25/2019 dmi.bios.release: 5.13 dmi.bios.vendor: Intel Corp. dmi.bios.version: QXCFL579.0034.2019.1125.1436 dmi.board.name: NUC9i7QNB dmi.board.vendor: Intel Corporation dmi.board.version: K49245-402 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.ec.firmware.release: 24.33 dmi.modalias: dmi:bvnIntelCorp.:bvrQXCFL579.0034.2019.1125.1436:bd11/25/2019:br5.13:efr24.33:svnIntel(R)ClientSystems:pnNUC9i7QNX:pvrK49244-403:rvnIntelCorporation:rnNUC9i7QNB:rvrK49245-402:cvnIntelCorporation:ct35:cvr2.0:skuBXNUC9i7QNX: dmi.product.family: QN dmi.product.name: NUC9i7QNX dmi.product.sku: BXNUC9i7QNX dmi.product.version: K49244-403 dmi.sys.vendor: Intel(R) Client Sys
[Kernel-packages] [Bug 1965882] Re: [nouveau] External monitor plugged into Nvidia GPU is all white (plus a little flicker)
** Description changed: External monitor plugged into Nvidia GPU is all white (plus a little flicker) for gnome-shell/mutter when using nouveau. This seems to be a kernel regression... FAIL: 5.17.0-051700-generic FAIL: 5.15.0-23-generic + PASS: 5.13.19-051319-generic PASS: 5.10.107-0510107-generic I'll update the above list in future. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-23-generic 5.15.0-23.23 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/by-id', '/dev/snd/controlC1', '/dev/snd/pcmC1D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass Date: Tue Mar 22 16:35:58 2022 InstallationDate: Installed on 2021-11-05 (136 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211103) MachineType: Intel(R) Client Systems NUC9i7QNX ProcFB: 0 i915drmfb 1 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic root=UUID=70e2069c-a553-4c6d-abfc-c65e52cb3b43 ro quiet splash nvidia-drm.modeset=1 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-23-generic N/A linux-backports-modules-5.15.0-23-generic N/A linux-firmware 20220314.gitcd01f857-0ubuntu2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/25/2019 dmi.bios.release: 5.13 dmi.bios.vendor: Intel Corp. dmi.bios.version: QXCFL579.0034.2019.1125.1436 dmi.board.name: NUC9i7QNB dmi.board.vendor: Intel Corporation dmi.board.version: K49245-402 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.ec.firmware.release: 24.33 dmi.modalias: dmi:bvnIntelCorp.:bvrQXCFL579.0034.2019.1125.1436:bd11/25/2019:br5.13:efr24.33:svnIntel(R)ClientSystems:pnNUC9i7QNX:pvrK49244-403:rvnIntelCorporation:rnNUC9i7QNB:rvrK49245-402:cvnIntelCorporation:ct35:cvr2.0:skuBXNUC9i7QNX: dmi.product.family: QN dmi.product.name: NUC9i7QNX dmi.product.sku: BXNUC9i7QNX dmi.product.version: K49244-403 dmi.sys.vendor: Intel(R) Client Systems -- 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/1965882 Title: [nouveau] External monitor plugged into Nvidia GPU is all white (plus a little flicker) Status in linux package in Ubuntu: New Bug description: External monitor plugged into Nvidia GPU is all white (plus a little flicker) for gnome-shell/mutter when using nouveau. This seems to be a kernel regression... FAIL: 5.17.0-051700-generic FAIL: 5.15.0-23-generic FAIL: 5.14.21-051421-generic PASS: 5.13.19-051319-generic PASS: 5.10.107-0510107-generic I'll update the above list in future. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-23-generic 5.15.0-23.23 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/by-id', '/dev/snd/controlC1', '/dev/snd/pcmC1D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass Date: Tue Mar 22 16:35:58 2022 InstallationDate: Installed on 2021-11-05 (136 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211103) MachineType: Intel(R) Client Systems NUC9i7QNX ProcFB: 0 i915drmfb 1 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic root=UUID=70e2069c-a553-4c6d-abfc-c65e52cb3b43 ro quiet splash nvidia-drm.modeset=1 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-23-generic N/A linux-backports-modules-5.15.0-23-generic N/A linux-firmware 20220314.gitcd01f857-0ubuntu2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/25/2019 dmi.bios.release: 5.13 dmi.bios.vendor: Intel Corp. dmi.bios.version: QXCFL579.0034.2019.1125.1436 dmi.board.name: NUC9i7QNB dmi.board.vendor: Intel Corporation dmi.board.version: K49245-402 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.ec.firmware.release: 24.33 dmi.modalias: dmi:bvnIntelCorp.:bvrQXCFL579.0034.2019.1125.1436:bd11/25/2019:br5.13:efr24.33:svnIntel(R)ClientSystems:pnNUC9i7QNX:pvrK49244-403:rvnIntelCorporation:rnNUC9i7QNB:rvrK49245-402:cvnIntelCorporation:ct35:cvr2.0:skuBXNUC9i7QNX: dmi.product.family: QN dmi.product.name: NUC9i7QNX dmi.product.sku: BXNUC9i7QNX dmi.product.version: K49244-403 dmi.sys.vendor: Intel(R) Client Systems To manage notifications about t
[Kernel-packages] [Bug 1965882] [NEW] [nouveau] External monitor plugged into Nvidia GPU is all white (plus a little flicker)
Public bug reported: External monitor plugged into Nvidia GPU is all white (plus a little flicker) for gnome-shell/mutter when using nouveau. This seems to be a kernel regression... FAIL: 5.17.0-051700-generic FAIL: 5.15.0-23-generic PASS: 5.13.19-051319-generic PASS: 5.10.107-0510107-generic I'll update the above list in future. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-23-generic 5.15.0-23.23 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/by-id', '/dev/snd/controlC1', '/dev/snd/pcmC1D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass Date: Tue Mar 22 16:35:58 2022 InstallationDate: Installed on 2021-11-05 (136 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211103) MachineType: Intel(R) Client Systems NUC9i7QNX ProcFB: 0 i915drmfb 1 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic root=UUID=70e2069c-a553-4c6d-abfc-c65e52cb3b43 ro quiet splash nvidia-drm.modeset=1 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-23-generic N/A linux-backports-modules-5.15.0-23-generic N/A linux-firmware 20220314.gitcd01f857-0ubuntu2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/25/2019 dmi.bios.release: 5.13 dmi.bios.vendor: Intel Corp. dmi.bios.version: QXCFL579.0034.2019.1125.1436 dmi.board.name: NUC9i7QNB dmi.board.vendor: Intel Corporation dmi.board.version: K49245-402 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.ec.firmware.release: 24.33 dmi.modalias: dmi:bvnIntelCorp.:bvrQXCFL579.0034.2019.1125.1436:bd11/25/2019:br5.13:efr24.33:svnIntel(R)ClientSystems:pnNUC9i7QNX:pvrK49244-403:rvnIntelCorporation:rnNUC9i7QNB:rvrK49245-402:cvnIntelCorporation:ct35:cvr2.0:skuBXNUC9i7QNX: dmi.product.family: QN dmi.product.name: NUC9i7QNX dmi.product.sku: BXNUC9i7QNX dmi.product.version: K49244-403 dmi.sys.vendor: Intel(R) Client Systems ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug dualgpus hybrid jammy multimonitor nouveau regression-release ** Description changed: External monitor plugged into Nvidia GPU is all white (plus a little - flicker) when using nouveau. + flicker) for gnome-shell/mutter when using nouveau. This seems to be a kernel regression... FAIL: 5.17.0-051700-generic FAIL: 5.15.0-23-generic PASS: 5.10.107-0510107-generic I'll update the above list in future. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-23-generic 5.15.0-23.23 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/by-id', '/dev/snd/controlC1', '/dev/snd/pcmC1D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass Date: Tue Mar 22 16:35:58 2022 InstallationDate: Installed on 2021-11-05 (136 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211103) MachineType: Intel(R) Client Systems NUC9i7QNX ProcFB: - 0 i915drmfb - 1 nouveaudrmfb + 0 i915drmfb + 1 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic root=UUID=70e2069c-a553-4c6d-abfc-c65e52cb3b43 ro quiet splash nvidia-drm.modeset=1 vt.handoff=7 RelatedPackageVersions: - linux-restricted-modules-5.15.0-23-generic N/A - linux-backports-modules-5.15.0-23-generic N/A - linux-firmware 20220314.gitcd01f857-0ubuntu2 + linux-restricted-modules-5.15.0-23-generic N/A + linux-backports-modules-5.15.0-23-generic N/A + linux-firmware 20220314.gitcd01f857-0ubuntu2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/25/2019 dmi.bios.release: 5.13 dmi.bios.vendor: Intel Corp. dmi.bios.version: QXCFL579.0034.2019.1125.1436 dmi.board.name: NUC9i7QNB dmi.board.vendor: Intel Corporation dmi.board.version: K49245-402 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.ec.firmware.release: 24.33 dmi.modalias: dmi:bvnIntelCorp.:bvrQXCFL579.0034.2019.1125.1436:bd11/25/2019:br5.13:efr24.33:svnIntel(R)ClientSystems:pnNUC9i7QNX:pvrK49244-403:rvnIntelCorporation:rnNUC9i7QNB:rvrK49245-402:cvnIntelCorporation:ct35:cvr2.0:skuBXNUC9i7QNX: dmi.product.family: QN dmi.product.name: NUC9i7QNX dmi.product.sku: BXNUC9i7QNX dmi.product.version: K49244-403 dmi.sys.vendor: Intel(R) Client Systems ** Tags added: multimonitor -- You received this bug notification because you are
[Kernel-packages] [Bug 1960242] Re: [amdgpu] kernel fault on monitor wakeup, only reboot recovers.
** Summary changed: - kernel fault on monitor wakeup, only reboot recovers. + [amdgpu] kernel fault on monitor wakeup, only reboot recovers. ** Tags added: amdgpu -- 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/1960242 Title: [amdgpu] kernel fault on monitor wakeup, only reboot recovers. Status in linux package in Ubuntu: Confirmed Bug description: After a normal day's operations, the monitors switch off after an hour or so. Every morning since Impish, upon waking up and unlocking the system: 2 of the monitors wake, the rest remain in sleep mode. The only recourse is to do a graceful poweroff and cold boot. There is a kernel fault, as follows and in the attached file. It is 100% repeatable. [121665.686476] ceph: mds0 caps renewed [126829.470180] [ cut here ] [126829.470183] WARNING: CPU: 6 PID: 4368 at drivers/gpu/drm/ttm/ttm_bo.c:437 ttm_bo_release+0x2de/0x330 [ttm] [126829.470191] Modules linked in: ceph libceph fscache netfs xt_CHECKSUM ipt_REJECT nf_reject_ipv4 xt_tcpudp xt_conntrack xt_MASQUERADE nf_conntrack_netlink nft_chain_nat nf_nat xfrm_user nf_conntrack xfrm_algo nf_defrag_ipv6 nf_defrag_ipv4 xt_addrtype nft_compat nft_counter br_netfilter nf_tables nfnetlink vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) bridge stp llc overlay lz4 lz4_compress zram snd_hda_codec_realtek snd_hda_codec_generic ledtrig_audio snd_hda_codec_hdmi snd_hda_intel snd_intel_dspcfg intel_rapl_msr snd_intel_sdw_acpi intel_rapl_common snd_hda_codec sch_fq_codel snd_usb_audio snd_hda_core snd_usbmidi_lib snd_hwdep snd_pcm snd_seq_midi edac_mce_amd snd_seq_midi_event snd_rawmidi uvcvideo msr videobuf2_vmalloc parport_pc videobuf2_memops kvm_amd videobuf2_v4l2 videobuf2_common ppdev snd_seq videodev kvm snd_seq_device lp snd_timer rapl parport eeepc_wmi wmi_bmof joydev input_leds mc k10temp ccp snd soundcore mac_hid sunrpc ip_tables x_tables autofs4 btrfs blake2b_generic xor [126829.470220] zstd_compress raid6_pq libcrc32c hid_generic uas usbhid usb_storage hid amdgpu iommu_v2 gpu_sched nouveau radeon mxm_wmi i2c_algo_bit drm_ttm_helper ttm drm_kms_helper syscopyarea sysfillrect crct10dif_pclmul sysimgblt fb_sys_fops crc32_pclmul cec ghash_clmulni_intel rc_core mfd_aaeon aesni_intel asus_wmi crypto_simd sparse_keymap nvme video xhci_pci r8169 gpio_amdpt ahci drm cryptd realtek i2c_piix4 libahci xhci_pci_renesas nvme_core wmi gpio_generic [126829.470239] CPU: 6 PID: 4368 Comm: kwin_x11:cs0 Tainted: G OE 5.13.0-28-generic #31-Ubuntu [126829.470241] Hardware name: System manufacturer System Product Name/PRIME B450-PLUS, BIOS 3211 08/10/2021 [126829.470242] RIP: 0010:ttm_bo_release+0x2de/0x330 [ttm] [126829.470246] Code: e8 17 27 3f f0 e9 ac fd ff ff 49 8b 7e 98 b9 4c 1d 00 00 31 d2 be 01 00 00 00 e8 4d 4a 3f f0 49 8b 46 e8 eb 9d 4c 89 e0 eb 98 <0f> 0b 41 c7 86 84 00 00 00 00 00 00 00 49 8d 76 08 31 d2 4c 89 ef [126829.470247] RSP: 0018:b0df43547d28 EFLAGS: 00010202 [126829.470248] RAX: 0002 RBX: 0002 RCX: [126829.470249] RDX: 0001 RSI: 0246 RDI: 89e51b945ac0 [126829.470250] RBP: b0df43547d50 R08: 89e4529488e8 R09: 0002 [126829.470251] R10: 89e894fe4d38 R11: 89e51c2ffce8 R12: 89e51b9452b0 [126829.470251] R13: 89e8aa050c58 R14: 89e8aa050db8 R15: 89eb3bb8c480 [126829.470252] FS: 7f21ee182640() GS:89ec1e30() knlGS: [126829.470253] CS: 0010 DS: ES: CR0: 80050033 [126829.470254] CR2: 7fbf8805e7e8 CR3: 00045811c000 CR4: 00350ee0 [126829.470255] Call Trace: [126829.470256] [126829.470258] ttm_bo_put+0x30/0x50 [ttm] [126829.470262] amdgpu_bo_unref+0x1e/0x30 [amdgpu] [126829.470365] amdgpu_gem_object_free+0x34/0x50 [amdgpu] [126829.470454] drm_gem_object_free+0x1d/0x30 [drm] [126829.470470] drm_gem_dmabuf_release+0x40/0x60 [drm] [126829.470486] dma_buf_release+0x46/0xa0 [126829.470488] __dentry_kill+0x10e/0x190 [126829.470490] dentry_kill+0x52/0x1c0 [126829.470491] dput+0x12f/0x180 [126829.470492] __fput+0xf0/0x250 [126829.470494] fput+0xe/0x10 [126829.470495] task_work_run+0x6d/0xa0 [126829.470497] exit_to_user_mode_loop+0x150/0x160 [126829.470499] exit_to_user_mode_prepare+0x9f/0xb0 [126829.470500] syscall_exit_to_user_mode+0x27/0x50 [126829.470503] do_syscall_64+0x6e/0xb0 [126829.470504] ? do_syscall_64+0x6e/0xb0 [126829.470506] ? asm_sysvec_apic_timer_interrupt+0xa/0x20 [126829.470507] entry_SYSCALL_64_after_hwframe+0x44/0xae [126829.470509] RIP: 0033:0x7f21fb43e9cb [126829.470510] Code: ff ff ff 85 c0 79 8b 49 c7 c4 ff ff ff ff 5b 5d 4c 89 e0 41 5c c3 66 0f 1f 84 00 00 00 00 00 f3 0f 1e fa b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b
[Kernel-packages] [Bug 1965878] [NEW] touchpad dosen't be detected asus f553m
Public bug reported: model:laptop asus f553m issue: lubuntu 20.04 dosen't reveal touchpad Description:Ubuntu 20.04.4 LTS Release:20.04 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.13.0-37-generic 5.13.0-37.42~20.04.1 ProcVersionSignature: Ubuntu 5.13.0-37.42~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-37-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: LXQt Date: Tue Mar 22 09:14:39 2022 InstallationDate: Installed on 2022-01-10 (71 days ago) InstallationMedia: Lubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) SourcePackage: linux-signed-hwe-5.13 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe-5.13 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "devices" https://bugs.launchpad.net/bugs/1965878/+attachment/5571675/+files/devices -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1965878 Title: touchpad dosen't be detected asus f553m Status in linux-signed-hwe-5.13 package in Ubuntu: New Bug description: model:laptop asus f553m issue: lubuntu 20.04 dosen't reveal touchpad Description:Ubuntu 20.04.4 LTS Release:20.04 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.13.0-37-generic 5.13.0-37.42~20.04.1 ProcVersionSignature: Ubuntu 5.13.0-37.42~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-37-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: LXQt Date: Tue Mar 22 09:14:39 2022 InstallationDate: Installed on 2022-01-10 (71 days ago) InstallationMedia: Lubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) SourcePackage: linux-signed-hwe-5.13 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.13/+bug/1965878/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1962462] Re: xserver-xorg-video-nvidia-390 needs to be updated to recognize latest xorg-video-abi virtual package provided by xserver-xorg-core
New xserver-xorg-video-nvidia-390 version 390.147-0ubuntu1 (in jammy- proposed) fixes this. $ apt policy xserver-xorg-video-nvidia-390 xserver-xorg-video-nvidia-390: Installed: 390.147-0ubuntu1 Candidate: 390.147-0ubuntu1 Version table: *** 390.147-0ubuntu1 500 500 http://ch.archive.ubuntu.com/ubuntu jammy-proposed/restricted amd64 Packages 100 /var/lib/dpkg/status 390.144-0ubuntu3 500 500 http://ch.archive.ubuntu.com/ubuntu jammy/restricted amd64 Packages $ apt show xserver-xorg-video-nvidia-390 Package: xserver-xorg-video-nvidia-390 Version: 390.147-0ubuntu1 Priority: optional Section: restricted/x11 Source: nvidia-graphics-drivers-390 Origin: Ubuntu Maintainer: Ubuntu Core Developers Bugs: https://bugs.launchpad.net/ubuntu/+filebug Installed-Size: 8,129 kB Provides: nvidia-driver-binary, xorg-driver-binary, xorg-driver-video Depends: libnvidia-cfg1-390 (= 390.147-0ubuntu1), xorg-video-abi-25 | xorg-video-abi-24 | xorg-video-abi-23 | xorg-video-abi-20 | xorg-video-abi-19 | xorg-video-abi-18 | xorg-video-abi-15 | xorg-video-abi-14 | xorg-video-abi-13 | xorg-video-abi-12 | xorg-video-abi-11 | xorg-video-abi-10 | xorg-video-abi-8 | xorg-video-abi-6.0, xserver-xorg-core (>= 2:1.19.6-1ubuntu2~), libc6 (>= 2.2.5) ** Changed in: nvidia-graphics-drivers-390 (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1962462 Title: xserver-xorg-video-nvidia-390 needs to be updated to recognize latest xorg-video-abi virtual package provided by xserver-xorg-core Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Bug description: xserver-xorg-video-nvidia-390 depends on xorg-video-abi-24 (or lower): xserver-xorg-video-nvidia-390 : Depends: xorg-video-abi-24 or xorg-video-abi-23 but it is not installable or xorg-video-abi-20 but it is not installable or xorg-video-abi-19 but it is not installable or xorg-video-abi-18 but it is not installable or xorg-video-abi-15 but it is not installable or xorg-video-abi-14 but it is not installable or xorg-video-abi-13 but it is not installable or xorg-video-abi-12 but it is not installable or xorg-video-abi-11 but it is not installable or xorg-video-abi-10 but it is not installable or xorg-video-abi-8 but it is not installable or xorg-video-abi-6.0 but it is not installable But the latest xserver-xorg-core provides xorg-video-abi-25: Package: xserver-xorg-core Version: 2:21.1.3-2ubuntu1 Priority: optional Section: x11 Source: xorg-server Origin: Ubuntu Maintainer: Ubuntu X-SWAT Original-Maintainer: Debian X Strike Force Bugs: https://bugs.launchpad.net/ubuntu/+filebug Installed-Size: 4,059 kB Provides: xorg-input-abi-24, xorg-video-abi-25, xserver-xorg-video-modesetting Until nvidia recompile for X ABI 25.x, a workaround will also be needed to get X to load the driver: [17.671] (II) LoadModule: "nvidia" [17.671] (II) Loading /usr/lib/x86_64-linux-gnu/nvidia/xorg/nvidia_drv.so [17.671] (II) Module nvidia: vendor="NVIDIA Corporation" [17.671]compiled for 4.0.2, module version = 1.0.0 [17.671]Module class: X.Org Video Driver [17.671] WARNING WARNING WARNING WARNING [17.671] This server has a video driver ABI version of 25.2 that this driver does not officially support. Please check http://www.nvidia.com/ for driver updates or downgrade to an X server with a supported driver ABI. [17.671] = [17.671] (EE) NVIDIA: Use the -ignoreABI option to override this check. [17.671] (II) UnloadModule: "nvidia" [17.671] (II) Unloading nvidia [17.671] (EE) Failed to load module "nvidia" (unknown error, 0) The workaround would be to include something like this in the package: xserver-xorg-video-nvidia-390 depends on xorg-video-abi-24 (or lower): xserver-xorg-video-nvidia-390 : Depends: xorg-video-abi-24 or xorg-video-abi-23 but it is not installable or xorg-video-abi-20 but it is not installable or xorg-video-abi-19 but it is not installable or
[Kernel-packages] [Bug 1965611] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1965611/+attachment/5571657/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1965611 Title: Ubuntu 21.10 + RTX3060Ti - second display black after login, works again after toggling the sources Status in linux package in Ubuntu: Confirmed Bug description: Hello I have a very peculiar situation. I have a PC with RTX3060Ti and Ubuntu 21.10 (dual-boot). Once I log-in to Ubuntu, only one of my 2 monitors is working properly, the other turns itself on, but has a black screen and goes to sleep mode after couple of seconds. Both monitors are detected by the Nvidia Settings. Furthermore I can drag apps to/from the blacked-out monitor as if it worked correctly. The weird thing is that if I switch to a different source on the blacked-out monitor and then return to the original source (the one connected to the PC), the monitor is detected and works as it should: 1) Switching the source to a different one - Ubuntu detects that there is only one monitor, all apps that were 'displayed' on a blacked-out monitor go to the other, single monitor 2) Switching back to the original source - Ubuntu detects both monitors and they both work correctly. I'm using Nvidia 510 Drivers. Tried older ones and Xorg drivers but no luck. Changing the outputs on GPU doesn't work either. I'm ready to provide any diagnostic information, just tell me what you need. It's really annoying. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: exsio 1193 F pulseaudio /dev/snd/controlC2: exsio 1193 F pulseaudio /dev/snd/controlC1: exsio 1193 F pulseaudio /dev/snd/controlC0: exsio 1193 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2021-10-20 (152 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: Micro-Star International Co., Ltd. MS-7D01 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-37-generic root=UUID=875adb16-91e6-4630-95cc-0084100568c3 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.13.0-37.42-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-37-generic N/A linux-backports-modules-5.13.0-37-generic N/A linux-firmware 1.201.5 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: impish Uname: Linux 5.13.0-37-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/16/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.30 dmi.board.asset.tag: Default string dmi.board.name: H410M PRO-C (MS-7D01) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.30:bd12/16/2020:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7D01:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnH410MPRO-C(MS-7D01):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuDefaultstring: dmi.product.family: Default string dmi.product.name: MS-7D01 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1965611/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1965611] PaInfo.txt
apport information ** Attachment added: "PaInfo.txt" https://bugs.launchpad.net/bugs/1965611/+attachment/5571656/+files/PaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1965611 Title: Ubuntu 21.10 + RTX3060Ti - second display black after login, works again after toggling the sources Status in linux package in Ubuntu: Confirmed Bug description: Hello I have a very peculiar situation. I have a PC with RTX3060Ti and Ubuntu 21.10 (dual-boot). Once I log-in to Ubuntu, only one of my 2 monitors is working properly, the other turns itself on, but has a black screen and goes to sleep mode after couple of seconds. Both monitors are detected by the Nvidia Settings. Furthermore I can drag apps to/from the blacked-out monitor as if it worked correctly. The weird thing is that if I switch to a different source on the blacked-out monitor and then return to the original source (the one connected to the PC), the monitor is detected and works as it should: 1) Switching the source to a different one - Ubuntu detects that there is only one monitor, all apps that were 'displayed' on a blacked-out monitor go to the other, single monitor 2) Switching back to the original source - Ubuntu detects both monitors and they both work correctly. I'm using Nvidia 510 Drivers. Tried older ones and Xorg drivers but no luck. Changing the outputs on GPU doesn't work either. I'm ready to provide any diagnostic information, just tell me what you need. It's really annoying. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: exsio 1193 F pulseaudio /dev/snd/controlC2: exsio 1193 F pulseaudio /dev/snd/controlC1: exsio 1193 F pulseaudio /dev/snd/controlC0: exsio 1193 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2021-10-20 (152 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: Micro-Star International Co., Ltd. MS-7D01 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-37-generic root=UUID=875adb16-91e6-4630-95cc-0084100568c3 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.13.0-37.42-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-37-generic N/A linux-backports-modules-5.13.0-37-generic N/A linux-firmware 1.201.5 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: impish Uname: Linux 5.13.0-37-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/16/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.30 dmi.board.asset.tag: Default string dmi.board.name: H410M PRO-C (MS-7D01) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.30:bd12/16/2020:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7D01:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnH410MPRO-C(MS-7D01):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuDefaultstring: dmi.product.family: Default string dmi.product.name: MS-7D01 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1965611/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1965611] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1965611/+attachment/5571662/+files/PulseList.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1965611 Title: Ubuntu 21.10 + RTX3060Ti - second display black after login, works again after toggling the sources Status in linux package in Ubuntu: Confirmed Bug description: Hello I have a very peculiar situation. I have a PC with RTX3060Ti and Ubuntu 21.10 (dual-boot). Once I log-in to Ubuntu, only one of my 2 monitors is working properly, the other turns itself on, but has a black screen and goes to sleep mode after couple of seconds. Both monitors are detected by the Nvidia Settings. Furthermore I can drag apps to/from the blacked-out monitor as if it worked correctly. The weird thing is that if I switch to a different source on the blacked-out monitor and then return to the original source (the one connected to the PC), the monitor is detected and works as it should: 1) Switching the source to a different one - Ubuntu detects that there is only one monitor, all apps that were 'displayed' on a blacked-out monitor go to the other, single monitor 2) Switching back to the original source - Ubuntu detects both monitors and they both work correctly. I'm using Nvidia 510 Drivers. Tried older ones and Xorg drivers but no luck. Changing the outputs on GPU doesn't work either. I'm ready to provide any diagnostic information, just tell me what you need. It's really annoying. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: exsio 1193 F pulseaudio /dev/snd/controlC2: exsio 1193 F pulseaudio /dev/snd/controlC1: exsio 1193 F pulseaudio /dev/snd/controlC0: exsio 1193 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2021-10-20 (152 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: Micro-Star International Co., Ltd. MS-7D01 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-37-generic root=UUID=875adb16-91e6-4630-95cc-0084100568c3 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.13.0-37.42-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-37-generic N/A linux-backports-modules-5.13.0-37-generic N/A linux-firmware 1.201.5 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: impish Uname: Linux 5.13.0-37-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/16/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.30 dmi.board.asset.tag: Default string dmi.board.name: H410M PRO-C (MS-7D01) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.30:bd12/16/2020:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7D01:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnH410MPRO-C(MS-7D01):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuDefaultstring: dmi.product.family: Default string dmi.product.name: MS-7D01 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1965611/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1965611] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1965611/+attachment/5571660/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1965611 Title: Ubuntu 21.10 + RTX3060Ti - second display black after login, works again after toggling the sources Status in linux package in Ubuntu: Confirmed Bug description: Hello I have a very peculiar situation. I have a PC with RTX3060Ti and Ubuntu 21.10 (dual-boot). Once I log-in to Ubuntu, only one of my 2 monitors is working properly, the other turns itself on, but has a black screen and goes to sleep mode after couple of seconds. Both monitors are detected by the Nvidia Settings. Furthermore I can drag apps to/from the blacked-out monitor as if it worked correctly. The weird thing is that if I switch to a different source on the blacked-out monitor and then return to the original source (the one connected to the PC), the monitor is detected and works as it should: 1) Switching the source to a different one - Ubuntu detects that there is only one monitor, all apps that were 'displayed' on a blacked-out monitor go to the other, single monitor 2) Switching back to the original source - Ubuntu detects both monitors and they both work correctly. I'm using Nvidia 510 Drivers. Tried older ones and Xorg drivers but no luck. Changing the outputs on GPU doesn't work either. I'm ready to provide any diagnostic information, just tell me what you need. It's really annoying. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: exsio 1193 F pulseaudio /dev/snd/controlC2: exsio 1193 F pulseaudio /dev/snd/controlC1: exsio 1193 F pulseaudio /dev/snd/controlC0: exsio 1193 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2021-10-20 (152 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: Micro-Star International Co., Ltd. MS-7D01 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-37-generic root=UUID=875adb16-91e6-4630-95cc-0084100568c3 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.13.0-37.42-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-37-generic N/A linux-backports-modules-5.13.0-37-generic N/A linux-firmware 1.201.5 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: impish Uname: Linux 5.13.0-37-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/16/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.30 dmi.board.asset.tag: Default string dmi.board.name: H410M PRO-C (MS-7D01) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.30:bd12/16/2020:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7D01:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnH410MPRO-C(MS-7D01):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuDefaultstring: dmi.product.family: Default string dmi.product.name: MS-7D01 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1965611/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1965611] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1965611/+attachment/5571661/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1965611 Title: Ubuntu 21.10 + RTX3060Ti - second display black after login, works again after toggling the sources Status in linux package in Ubuntu: Confirmed Bug description: Hello I have a very peculiar situation. I have a PC with RTX3060Ti and Ubuntu 21.10 (dual-boot). Once I log-in to Ubuntu, only one of my 2 monitors is working properly, the other turns itself on, but has a black screen and goes to sleep mode after couple of seconds. Both monitors are detected by the Nvidia Settings. Furthermore I can drag apps to/from the blacked-out monitor as if it worked correctly. The weird thing is that if I switch to a different source on the blacked-out monitor and then return to the original source (the one connected to the PC), the monitor is detected and works as it should: 1) Switching the source to a different one - Ubuntu detects that there is only one monitor, all apps that were 'displayed' on a blacked-out monitor go to the other, single monitor 2) Switching back to the original source - Ubuntu detects both monitors and they both work correctly. I'm using Nvidia 510 Drivers. Tried older ones and Xorg drivers but no luck. Changing the outputs on GPU doesn't work either. I'm ready to provide any diagnostic information, just tell me what you need. It's really annoying. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: exsio 1193 F pulseaudio /dev/snd/controlC2: exsio 1193 F pulseaudio /dev/snd/controlC1: exsio 1193 F pulseaudio /dev/snd/controlC0: exsio 1193 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2021-10-20 (152 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: Micro-Star International Co., Ltd. MS-7D01 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-37-generic root=UUID=875adb16-91e6-4630-95cc-0084100568c3 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.13.0-37.42-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-37-generic N/A linux-backports-modules-5.13.0-37-generic N/A linux-firmware 1.201.5 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: impish Uname: Linux 5.13.0-37-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/16/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.30 dmi.board.asset.tag: Default string dmi.board.name: H410M PRO-C (MS-7D01) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.30:bd12/16/2020:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7D01:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnH410MPRO-C(MS-7D01):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuDefaultstring: dmi.product.family: Default string dmi.product.name: MS-7D01 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1965611/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1965611] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1965611/+attachment/5571665/+files/acpidump.txt ** 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/1965611 Title: Ubuntu 21.10 + RTX3060Ti - second display black after login, works again after toggling the sources Status in linux package in Ubuntu: Confirmed Bug description: Hello I have a very peculiar situation. I have a PC with RTX3060Ti and Ubuntu 21.10 (dual-boot). Once I log-in to Ubuntu, only one of my 2 monitors is working properly, the other turns itself on, but has a black screen and goes to sleep mode after couple of seconds. Both monitors are detected by the Nvidia Settings. Furthermore I can drag apps to/from the blacked-out monitor as if it worked correctly. The weird thing is that if I switch to a different source on the blacked-out monitor and then return to the original source (the one connected to the PC), the monitor is detected and works as it should: 1) Switching the source to a different one - Ubuntu detects that there is only one monitor, all apps that were 'displayed' on a blacked-out monitor go to the other, single monitor 2) Switching back to the original source - Ubuntu detects both monitors and they both work correctly. I'm using Nvidia 510 Drivers. Tried older ones and Xorg drivers but no luck. Changing the outputs on GPU doesn't work either. I'm ready to provide any diagnostic information, just tell me what you need. It's really annoying. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: exsio 1193 F pulseaudio /dev/snd/controlC2: exsio 1193 F pulseaudio /dev/snd/controlC1: exsio 1193 F pulseaudio /dev/snd/controlC0: exsio 1193 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2021-10-20 (152 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: Micro-Star International Co., Ltd. MS-7D01 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-37-generic root=UUID=875adb16-91e6-4630-95cc-0084100568c3 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.13.0-37.42-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-37-generic N/A linux-backports-modules-5.13.0-37-generic N/A linux-firmware 1.201.5 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: impish Uname: Linux 5.13.0-37-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/16/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.30 dmi.board.asset.tag: Default string dmi.board.name: H410M PRO-C (MS-7D01) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.30:bd12/16/2020:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7D01:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnH410MPRO-C(MS-7D01):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuDefaultstring: dmi.product.family: Default string dmi.product.name: MS-7D01 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1965611/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1965611] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1965611/+attachment/5571664/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1965611 Title: Ubuntu 21.10 + RTX3060Ti - second display black after login, works again after toggling the sources Status in linux package in Ubuntu: Confirmed Bug description: Hello I have a very peculiar situation. I have a PC with RTX3060Ti and Ubuntu 21.10 (dual-boot). Once I log-in to Ubuntu, only one of my 2 monitors is working properly, the other turns itself on, but has a black screen and goes to sleep mode after couple of seconds. Both monitors are detected by the Nvidia Settings. Furthermore I can drag apps to/from the blacked-out monitor as if it worked correctly. The weird thing is that if I switch to a different source on the blacked-out monitor and then return to the original source (the one connected to the PC), the monitor is detected and works as it should: 1) Switching the source to a different one - Ubuntu detects that there is only one monitor, all apps that were 'displayed' on a blacked-out monitor go to the other, single monitor 2) Switching back to the original source - Ubuntu detects both monitors and they both work correctly. I'm using Nvidia 510 Drivers. Tried older ones and Xorg drivers but no luck. Changing the outputs on GPU doesn't work either. I'm ready to provide any diagnostic information, just tell me what you need. It's really annoying. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: exsio 1193 F pulseaudio /dev/snd/controlC2: exsio 1193 F pulseaudio /dev/snd/controlC1: exsio 1193 F pulseaudio /dev/snd/controlC0: exsio 1193 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2021-10-20 (152 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: Micro-Star International Co., Ltd. MS-7D01 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-37-generic root=UUID=875adb16-91e6-4630-95cc-0084100568c3 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.13.0-37.42-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-37-generic N/A linux-backports-modules-5.13.0-37-generic N/A linux-firmware 1.201.5 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: impish Uname: Linux 5.13.0-37-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/16/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.30 dmi.board.asset.tag: Default string dmi.board.name: H410M PRO-C (MS-7D01) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.30:bd12/16/2020:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7D01:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnH410MPRO-C(MS-7D01):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuDefaultstring: dmi.product.family: Default string dmi.product.name: MS-7D01 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1965611/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1965611] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1965611/+attachment/5571659/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1965611 Title: Ubuntu 21.10 + RTX3060Ti - second display black after login, works again after toggling the sources Status in linux package in Ubuntu: Confirmed Bug description: Hello I have a very peculiar situation. I have a PC with RTX3060Ti and Ubuntu 21.10 (dual-boot). Once I log-in to Ubuntu, only one of my 2 monitors is working properly, the other turns itself on, but has a black screen and goes to sleep mode after couple of seconds. Both monitors are detected by the Nvidia Settings. Furthermore I can drag apps to/from the blacked-out monitor as if it worked correctly. The weird thing is that if I switch to a different source on the blacked-out monitor and then return to the original source (the one connected to the PC), the monitor is detected and works as it should: 1) Switching the source to a different one - Ubuntu detects that there is only one monitor, all apps that were 'displayed' on a blacked-out monitor go to the other, single monitor 2) Switching back to the original source - Ubuntu detects both monitors and they both work correctly. I'm using Nvidia 510 Drivers. Tried older ones and Xorg drivers but no luck. Changing the outputs on GPU doesn't work either. I'm ready to provide any diagnostic information, just tell me what you need. It's really annoying. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: exsio 1193 F pulseaudio /dev/snd/controlC2: exsio 1193 F pulseaudio /dev/snd/controlC1: exsio 1193 F pulseaudio /dev/snd/controlC0: exsio 1193 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2021-10-20 (152 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: Micro-Star International Co., Ltd. MS-7D01 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-37-generic root=UUID=875adb16-91e6-4630-95cc-0084100568c3 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.13.0-37.42-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-37-generic N/A linux-backports-modules-5.13.0-37-generic N/A linux-firmware 1.201.5 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: impish Uname: Linux 5.13.0-37-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/16/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.30 dmi.board.asset.tag: Default string dmi.board.name: H410M PRO-C (MS-7D01) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.30:bd12/16/2020:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7D01:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnH410MPRO-C(MS-7D01):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuDefaultstring: dmi.product.family: Default string dmi.product.name: MS-7D01 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1965611/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1965611] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1965611/+attachment/5571663/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1965611 Title: Ubuntu 21.10 + RTX3060Ti - second display black after login, works again after toggling the sources Status in linux package in Ubuntu: Confirmed Bug description: Hello I have a very peculiar situation. I have a PC with RTX3060Ti and Ubuntu 21.10 (dual-boot). Once I log-in to Ubuntu, only one of my 2 monitors is working properly, the other turns itself on, but has a black screen and goes to sleep mode after couple of seconds. Both monitors are detected by the Nvidia Settings. Furthermore I can drag apps to/from the blacked-out monitor as if it worked correctly. The weird thing is that if I switch to a different source on the blacked-out monitor and then return to the original source (the one connected to the PC), the monitor is detected and works as it should: 1) Switching the source to a different one - Ubuntu detects that there is only one monitor, all apps that were 'displayed' on a blacked-out monitor go to the other, single monitor 2) Switching back to the original source - Ubuntu detects both monitors and they both work correctly. I'm using Nvidia 510 Drivers. Tried older ones and Xorg drivers but no luck. Changing the outputs on GPU doesn't work either. I'm ready to provide any diagnostic information, just tell me what you need. It's really annoying. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: exsio 1193 F pulseaudio /dev/snd/controlC2: exsio 1193 F pulseaudio /dev/snd/controlC1: exsio 1193 F pulseaudio /dev/snd/controlC0: exsio 1193 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2021-10-20 (152 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: Micro-Star International Co., Ltd. MS-7D01 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-37-generic root=UUID=875adb16-91e6-4630-95cc-0084100568c3 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.13.0-37.42-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-37-generic N/A linux-backports-modules-5.13.0-37-generic N/A linux-firmware 1.201.5 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: impish Uname: Linux 5.13.0-37-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/16/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.30 dmi.board.asset.tag: Default string dmi.board.name: H410M PRO-C (MS-7D01) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.30:bd12/16/2020:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7D01:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnH410MPRO-C(MS-7D01):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuDefaultstring: dmi.product.family: Default string dmi.product.name: MS-7D01 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1965611/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1965611] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1965611/+attachment/5571658/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1965611 Title: Ubuntu 21.10 + RTX3060Ti - second display black after login, works again after toggling the sources Status in linux package in Ubuntu: Confirmed Bug description: Hello I have a very peculiar situation. I have a PC with RTX3060Ti and Ubuntu 21.10 (dual-boot). Once I log-in to Ubuntu, only one of my 2 monitors is working properly, the other turns itself on, but has a black screen and goes to sleep mode after couple of seconds. Both monitors are detected by the Nvidia Settings. Furthermore I can drag apps to/from the blacked-out monitor as if it worked correctly. The weird thing is that if I switch to a different source on the blacked-out monitor and then return to the original source (the one connected to the PC), the monitor is detected and works as it should: 1) Switching the source to a different one - Ubuntu detects that there is only one monitor, all apps that were 'displayed' on a blacked-out monitor go to the other, single monitor 2) Switching back to the original source - Ubuntu detects both monitors and they both work correctly. I'm using Nvidia 510 Drivers. Tried older ones and Xorg drivers but no luck. Changing the outputs on GPU doesn't work either. I'm ready to provide any diagnostic information, just tell me what you need. It's really annoying. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: exsio 1193 F pulseaudio /dev/snd/controlC2: exsio 1193 F pulseaudio /dev/snd/controlC1: exsio 1193 F pulseaudio /dev/snd/controlC0: exsio 1193 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2021-10-20 (152 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: Micro-Star International Co., Ltd. MS-7D01 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-37-generic root=UUID=875adb16-91e6-4630-95cc-0084100568c3 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.13.0-37.42-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-37-generic N/A linux-backports-modules-5.13.0-37-generic N/A linux-firmware 1.201.5 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: impish Uname: Linux 5.13.0-37-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/16/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.30 dmi.board.asset.tag: Default string dmi.board.name: H410M PRO-C (MS-7D01) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.30:bd12/16/2020:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7D01:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnH410MPRO-C(MS-7D01):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuDefaultstring: dmi.product.family: Default string dmi.product.name: MS-7D01 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1965611/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1965611] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1965611/+attachment/5571652/+files/Lspci-vt.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1965611 Title: Ubuntu 21.10 + RTX3060Ti - second display black after login, works again after toggling the sources Status in linux package in Ubuntu: Confirmed Bug description: Hello I have a very peculiar situation. I have a PC with RTX3060Ti and Ubuntu 21.10 (dual-boot). Once I log-in to Ubuntu, only one of my 2 monitors is working properly, the other turns itself on, but has a black screen and goes to sleep mode after couple of seconds. Both monitors are detected by the Nvidia Settings. Furthermore I can drag apps to/from the blacked-out monitor as if it worked correctly. The weird thing is that if I switch to a different source on the blacked-out monitor and then return to the original source (the one connected to the PC), the monitor is detected and works as it should: 1) Switching the source to a different one - Ubuntu detects that there is only one monitor, all apps that were 'displayed' on a blacked-out monitor go to the other, single monitor 2) Switching back to the original source - Ubuntu detects both monitors and they both work correctly. I'm using Nvidia 510 Drivers. Tried older ones and Xorg drivers but no luck. Changing the outputs on GPU doesn't work either. I'm ready to provide any diagnostic information, just tell me what you need. It's really annoying. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: exsio 1193 F pulseaudio /dev/snd/controlC2: exsio 1193 F pulseaudio /dev/snd/controlC1: exsio 1193 F pulseaudio /dev/snd/controlC0: exsio 1193 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2021-10-20 (152 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: Micro-Star International Co., Ltd. MS-7D01 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-37-generic root=UUID=875adb16-91e6-4630-95cc-0084100568c3 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.13.0-37.42-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-37-generic N/A linux-backports-modules-5.13.0-37-generic N/A linux-firmware 1.201.5 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: impish Uname: Linux 5.13.0-37-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/16/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.30 dmi.board.asset.tag: Default string dmi.board.name: H410M PRO-C (MS-7D01) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.30:bd12/16/2020:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7D01:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnH410MPRO-C(MS-7D01):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuDefaultstring: dmi.product.family: Default string dmi.product.name: MS-7D01 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1965611/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1965611] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1965611/+attachment/5571651/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1965611 Title: Ubuntu 21.10 + RTX3060Ti - second display black after login, works again after toggling the sources Status in linux package in Ubuntu: Confirmed Bug description: Hello I have a very peculiar situation. I have a PC with RTX3060Ti and Ubuntu 21.10 (dual-boot). Once I log-in to Ubuntu, only one of my 2 monitors is working properly, the other turns itself on, but has a black screen and goes to sleep mode after couple of seconds. Both monitors are detected by the Nvidia Settings. Furthermore I can drag apps to/from the blacked-out monitor as if it worked correctly. The weird thing is that if I switch to a different source on the blacked-out monitor and then return to the original source (the one connected to the PC), the monitor is detected and works as it should: 1) Switching the source to a different one - Ubuntu detects that there is only one monitor, all apps that were 'displayed' on a blacked-out monitor go to the other, single monitor 2) Switching back to the original source - Ubuntu detects both monitors and they both work correctly. I'm using Nvidia 510 Drivers. Tried older ones and Xorg drivers but no luck. Changing the outputs on GPU doesn't work either. I'm ready to provide any diagnostic information, just tell me what you need. It's really annoying. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: exsio 1193 F pulseaudio /dev/snd/controlC2: exsio 1193 F pulseaudio /dev/snd/controlC1: exsio 1193 F pulseaudio /dev/snd/controlC0: exsio 1193 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2021-10-20 (152 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: Micro-Star International Co., Ltd. MS-7D01 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-37-generic root=UUID=875adb16-91e6-4630-95cc-0084100568c3 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.13.0-37.42-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-37-generic N/A linux-backports-modules-5.13.0-37-generic N/A linux-firmware 1.201.5 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: impish Uname: Linux 5.13.0-37-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/16/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.30 dmi.board.asset.tag: Default string dmi.board.name: H410M PRO-C (MS-7D01) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.30:bd12/16/2020:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7D01:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnH410MPRO-C(MS-7D01):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuDefaultstring: dmi.product.family: Default string dmi.product.name: MS-7D01 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1965611/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1965611] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1965611/+attachment/5571655/+files/Lsusb-v.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1965611 Title: Ubuntu 21.10 + RTX3060Ti - second display black after login, works again after toggling the sources Status in linux package in Ubuntu: Confirmed Bug description: Hello I have a very peculiar situation. I have a PC with RTX3060Ti and Ubuntu 21.10 (dual-boot). Once I log-in to Ubuntu, only one of my 2 monitors is working properly, the other turns itself on, but has a black screen and goes to sleep mode after couple of seconds. Both monitors are detected by the Nvidia Settings. Furthermore I can drag apps to/from the blacked-out monitor as if it worked correctly. The weird thing is that if I switch to a different source on the blacked-out monitor and then return to the original source (the one connected to the PC), the monitor is detected and works as it should: 1) Switching the source to a different one - Ubuntu detects that there is only one monitor, all apps that were 'displayed' on a blacked-out monitor go to the other, single monitor 2) Switching back to the original source - Ubuntu detects both monitors and they both work correctly. I'm using Nvidia 510 Drivers. Tried older ones and Xorg drivers but no luck. Changing the outputs on GPU doesn't work either. I'm ready to provide any diagnostic information, just tell me what you need. It's really annoying. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: exsio 1193 F pulseaudio /dev/snd/controlC2: exsio 1193 F pulseaudio /dev/snd/controlC1: exsio 1193 F pulseaudio /dev/snd/controlC0: exsio 1193 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2021-10-20 (152 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: Micro-Star International Co., Ltd. MS-7D01 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-37-generic root=UUID=875adb16-91e6-4630-95cc-0084100568c3 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.13.0-37.42-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-37-generic N/A linux-backports-modules-5.13.0-37-generic N/A linux-firmware 1.201.5 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: impish Uname: Linux 5.13.0-37-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/16/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.30 dmi.board.asset.tag: Default string dmi.board.name: H410M PRO-C (MS-7D01) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.30:bd12/16/2020:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7D01:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnH410MPRO-C(MS-7D01):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuDefaultstring: dmi.product.family: Default string dmi.product.name: MS-7D01 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1965611/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1965611] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1965611/+attachment/5571648/+files/CRDA.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1965611 Title: Ubuntu 21.10 + RTX3060Ti - second display black after login, works again after toggling the sources Status in linux package in Ubuntu: Confirmed Bug description: Hello I have a very peculiar situation. I have a PC with RTX3060Ti and Ubuntu 21.10 (dual-boot). Once I log-in to Ubuntu, only one of my 2 monitors is working properly, the other turns itself on, but has a black screen and goes to sleep mode after couple of seconds. Both monitors are detected by the Nvidia Settings. Furthermore I can drag apps to/from the blacked-out monitor as if it worked correctly. The weird thing is that if I switch to a different source on the blacked-out monitor and then return to the original source (the one connected to the PC), the monitor is detected and works as it should: 1) Switching the source to a different one - Ubuntu detects that there is only one monitor, all apps that were 'displayed' on a blacked-out monitor go to the other, single monitor 2) Switching back to the original source - Ubuntu detects both monitors and they both work correctly. I'm using Nvidia 510 Drivers. Tried older ones and Xorg drivers but no luck. Changing the outputs on GPU doesn't work either. I'm ready to provide any diagnostic information, just tell me what you need. It's really annoying. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: exsio 1193 F pulseaudio /dev/snd/controlC2: exsio 1193 F pulseaudio /dev/snd/controlC1: exsio 1193 F pulseaudio /dev/snd/controlC0: exsio 1193 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2021-10-20 (152 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: Micro-Star International Co., Ltd. MS-7D01 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-37-generic root=UUID=875adb16-91e6-4630-95cc-0084100568c3 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.13.0-37.42-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-37-generic N/A linux-backports-modules-5.13.0-37-generic N/A linux-firmware 1.201.5 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: impish Uname: Linux 5.13.0-37-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/16/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.30 dmi.board.asset.tag: Default string dmi.board.name: H410M PRO-C (MS-7D01) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.30:bd12/16/2020:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7D01:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnH410MPRO-C(MS-7D01):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuDefaultstring: dmi.product.family: Default string dmi.product.name: MS-7D01 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1965611/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1965611] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1965611/+attachment/5571653/+files/Lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1965611 Title: Ubuntu 21.10 + RTX3060Ti - second display black after login, works again after toggling the sources Status in linux package in Ubuntu: Confirmed Bug description: Hello I have a very peculiar situation. I have a PC with RTX3060Ti and Ubuntu 21.10 (dual-boot). Once I log-in to Ubuntu, only one of my 2 monitors is working properly, the other turns itself on, but has a black screen and goes to sleep mode after couple of seconds. Both monitors are detected by the Nvidia Settings. Furthermore I can drag apps to/from the blacked-out monitor as if it worked correctly. The weird thing is that if I switch to a different source on the blacked-out monitor and then return to the original source (the one connected to the PC), the monitor is detected and works as it should: 1) Switching the source to a different one - Ubuntu detects that there is only one monitor, all apps that were 'displayed' on a blacked-out monitor go to the other, single monitor 2) Switching back to the original source - Ubuntu detects both monitors and they both work correctly. I'm using Nvidia 510 Drivers. Tried older ones and Xorg drivers but no luck. Changing the outputs on GPU doesn't work either. I'm ready to provide any diagnostic information, just tell me what you need. It's really annoying. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: exsio 1193 F pulseaudio /dev/snd/controlC2: exsio 1193 F pulseaudio /dev/snd/controlC1: exsio 1193 F pulseaudio /dev/snd/controlC0: exsio 1193 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2021-10-20 (152 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: Micro-Star International Co., Ltd. MS-7D01 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-37-generic root=UUID=875adb16-91e6-4630-95cc-0084100568c3 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.13.0-37.42-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-37-generic N/A linux-backports-modules-5.13.0-37-generic N/A linux-firmware 1.201.5 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: impish Uname: Linux 5.13.0-37-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/16/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.30 dmi.board.asset.tag: Default string dmi.board.name: H410M PRO-C (MS-7D01) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.30:bd12/16/2020:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7D01:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnH410MPRO-C(MS-7D01):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuDefaultstring: dmi.product.family: Default string dmi.product.name: MS-7D01 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1965611/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1965611] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1965611/+attachment/5571654/+files/Lsusb-t.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1965611 Title: Ubuntu 21.10 + RTX3060Ti - second display black after login, works again after toggling the sources Status in linux package in Ubuntu: Confirmed Bug description: Hello I have a very peculiar situation. I have a PC with RTX3060Ti and Ubuntu 21.10 (dual-boot). Once I log-in to Ubuntu, only one of my 2 monitors is working properly, the other turns itself on, but has a black screen and goes to sleep mode after couple of seconds. Both monitors are detected by the Nvidia Settings. Furthermore I can drag apps to/from the blacked-out monitor as if it worked correctly. The weird thing is that if I switch to a different source on the blacked-out monitor and then return to the original source (the one connected to the PC), the monitor is detected and works as it should: 1) Switching the source to a different one - Ubuntu detects that there is only one monitor, all apps that were 'displayed' on a blacked-out monitor go to the other, single monitor 2) Switching back to the original source - Ubuntu detects both monitors and they both work correctly. I'm using Nvidia 510 Drivers. Tried older ones and Xorg drivers but no luck. Changing the outputs on GPU doesn't work either. I'm ready to provide any diagnostic information, just tell me what you need. It's really annoying. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: exsio 1193 F pulseaudio /dev/snd/controlC2: exsio 1193 F pulseaudio /dev/snd/controlC1: exsio 1193 F pulseaudio /dev/snd/controlC0: exsio 1193 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2021-10-20 (152 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: Micro-Star International Co., Ltd. MS-7D01 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-37-generic root=UUID=875adb16-91e6-4630-95cc-0084100568c3 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.13.0-37.42-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-37-generic N/A linux-backports-modules-5.13.0-37-generic N/A linux-firmware 1.201.5 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: impish Uname: Linux 5.13.0-37-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/16/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.30 dmi.board.asset.tag: Default string dmi.board.name: H410M PRO-C (MS-7D01) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.30:bd12/16/2020:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7D01:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnH410MPRO-C(MS-7D01):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuDefaultstring: dmi.product.family: Default string dmi.product.name: MS-7D01 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1965611/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1965611] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1965611/+attachment/5571649/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1965611 Title: Ubuntu 21.10 + RTX3060Ti - second display black after login, works again after toggling the sources Status in linux package in Ubuntu: Confirmed Bug description: Hello I have a very peculiar situation. I have a PC with RTX3060Ti and Ubuntu 21.10 (dual-boot). Once I log-in to Ubuntu, only one of my 2 monitors is working properly, the other turns itself on, but has a black screen and goes to sleep mode after couple of seconds. Both monitors are detected by the Nvidia Settings. Furthermore I can drag apps to/from the blacked-out monitor as if it worked correctly. The weird thing is that if I switch to a different source on the blacked-out monitor and then return to the original source (the one connected to the PC), the monitor is detected and works as it should: 1) Switching the source to a different one - Ubuntu detects that there is only one monitor, all apps that were 'displayed' on a blacked-out monitor go to the other, single monitor 2) Switching back to the original source - Ubuntu detects both monitors and they both work correctly. I'm using Nvidia 510 Drivers. Tried older ones and Xorg drivers but no luck. Changing the outputs on GPU doesn't work either. I'm ready to provide any diagnostic information, just tell me what you need. It's really annoying. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: exsio 1193 F pulseaudio /dev/snd/controlC2: exsio 1193 F pulseaudio /dev/snd/controlC1: exsio 1193 F pulseaudio /dev/snd/controlC0: exsio 1193 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2021-10-20 (152 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: Micro-Star International Co., Ltd. MS-7D01 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-37-generic root=UUID=875adb16-91e6-4630-95cc-0084100568c3 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.13.0-37.42-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-37-generic N/A linux-backports-modules-5.13.0-37-generic N/A linux-firmware 1.201.5 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: impish Uname: Linux 5.13.0-37-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/16/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.30 dmi.board.asset.tag: Default string dmi.board.name: H410M PRO-C (MS-7D01) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.30:bd12/16/2020:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7D01:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnH410MPRO-C(MS-7D01):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuDefaultstring: dmi.product.family: Default string dmi.product.name: MS-7D01 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1965611/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1965611] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1965611/+attachment/5571650/+files/IwConfig.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1965611 Title: Ubuntu 21.10 + RTX3060Ti - second display black after login, works again after toggling the sources Status in linux package in Ubuntu: Confirmed Bug description: Hello I have a very peculiar situation. I have a PC with RTX3060Ti and Ubuntu 21.10 (dual-boot). Once I log-in to Ubuntu, only one of my 2 monitors is working properly, the other turns itself on, but has a black screen and goes to sleep mode after couple of seconds. Both monitors are detected by the Nvidia Settings. Furthermore I can drag apps to/from the blacked-out monitor as if it worked correctly. The weird thing is that if I switch to a different source on the blacked-out monitor and then return to the original source (the one connected to the PC), the monitor is detected and works as it should: 1) Switching the source to a different one - Ubuntu detects that there is only one monitor, all apps that were 'displayed' on a blacked-out monitor go to the other, single monitor 2) Switching back to the original source - Ubuntu detects both monitors and they both work correctly. I'm using Nvidia 510 Drivers. Tried older ones and Xorg drivers but no luck. Changing the outputs on GPU doesn't work either. I'm ready to provide any diagnostic information, just tell me what you need. It's really annoying. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: exsio 1193 F pulseaudio /dev/snd/controlC2: exsio 1193 F pulseaudio /dev/snd/controlC1: exsio 1193 F pulseaudio /dev/snd/controlC0: exsio 1193 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2021-10-20 (152 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: Micro-Star International Co., Ltd. MS-7D01 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-37-generic root=UUID=875adb16-91e6-4630-95cc-0084100568c3 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.13.0-37.42-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-37-generic N/A linux-backports-modules-5.13.0-37-generic N/A linux-firmware 1.201.5 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: impish Uname: Linux 5.13.0-37-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/16/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.30 dmi.board.asset.tag: Default string dmi.board.name: H410M PRO-C (MS-7D01) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.30:bd12/16/2020:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7D01:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnH410MPRO-C(MS-7D01):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuDefaultstring: dmi.product.family: Default string dmi.product.name: MS-7D01 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1965611/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1965611] Re: Ubuntu 21.10 + RTX3060Ti - second display black after login, works again after toggling the sources
apport information ** Tags added: apport-collected impish ** Description changed: Hello I have a very peculiar situation. I have a PC with RTX3060Ti and Ubuntu 21.10 (dual-boot). Once I log-in to Ubuntu, only one of my 2 monitors is working properly, the other turns itself on, but has a black screen and goes to sleep mode after couple of seconds. Both monitors are detected by the Nvidia Settings. Furthermore I can drag apps to/from the blacked- out monitor as if it worked correctly. The weird thing is that if I switch to a different source on the blacked-out monitor and then return to the original source (the one connected to the PC), the monitor is detected and works as it should: 1) Switching the source to a different one - Ubuntu detects that there is only one monitor, all apps that were 'displayed' on a blacked-out monitor go to the other, single monitor 2) Switching back to the original source - Ubuntu detects both monitors and they both work correctly. - I'm using Nvidia 510 Drivers. Tried older ones and Xorg drivers but no - luck. Changing the outputs on GPU doesn't work either. I'm ready to - provide any diagnostic information, just tell me what you need. It's - really annoying. + I'm using Nvidia 510 Drivers. Tried older ones and Xorg drivers but no luck. Changing the outputs on GPU doesn't work either. I'm ready to provide any diagnostic information, just tell me what you need. It's really annoying. + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu71 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC3: exsio 1193 F pulseaudio + /dev/snd/controlC2: exsio 1193 F pulseaudio + /dev/snd/controlC1: exsio 1193 F pulseaudio + /dev/snd/controlC0: exsio 1193 F pulseaudio + CasperMD5CheckResult: pass + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 21.10 + InstallationDate: Installed on 2021-10-20 (152 days ago) + InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) + MachineType: Micro-Star International Co., Ltd. MS-7D01 + NonfreeKernelModules: nvidia_modeset nvidia + Package: linux (not installed) + ProcFB: 0 EFI VGA + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-37-generic root=UUID=875adb16-91e6-4630-95cc-0084100568c3 ro quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 5.13.0-37.42-generic 5.13.19 + RelatedPackageVersions: + linux-restricted-modules-5.13.0-37-generic N/A + linux-backports-modules-5.13.0-37-generic N/A + linux-firmware 1.201.5 + RfKill: + 0: hci0: Bluetooth + Soft blocked: no + Hard blocked: no + Tags: impish + Uname: Linux 5.13.0-37-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 12/16/2020 + dmi.bios.release: 5.17 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: 1.30 + dmi.board.asset.tag: Default string + dmi.board.name: H410M PRO-C (MS-7D01) + dmi.board.vendor: Micro-Star International Co., Ltd. + dmi.board.version: 1.0 + dmi.chassis.asset.tag: Default string + dmi.chassis.type: 3 + dmi.chassis.vendor: Micro-Star International Co., Ltd. + dmi.chassis.version: 1.0 + dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.30:bd12/16/2020:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7D01:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnH410MPRO-C(MS-7D01):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuDefaultstring: + dmi.product.family: Default string + dmi.product.name: MS-7D01 + dmi.product.sku: Default string + dmi.product.version: 1.0 + dmi.sys.vendor: Micro-Star International Co., Ltd. ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1965611/+attachment/5571647/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1965611 Title: Ubuntu 21.10 + RTX3060Ti - second display black after login, works again after toggling the sources Status in linux package in Ubuntu: Confirmed Bug description: Hello I have a very peculiar situation. I have a PC with RTX3060Ti and Ubuntu 21.10 (dual-boot). Once I log-in to Ubuntu, only one of my 2 monitors is working properly, the other turns itself on, but has a black screen and goes to sleep mode after couple of seconds. Both monitors are detected by the Nvidia Settings. Furthermore I can drag apps to/from the blacked-out monitor as if it worked correctly. The weird thing is that if I switch to a different source on the blacked-out monitor and then return to the original source (the one connected to the PC), the monitor is detected and works as it should: 1) Switching the source to a different one - Ubuntu detects that there is only one monitor, all apps that were 'displayed' on a blacked-ou
[Kernel-packages] [Bug 1964305] Re: [nvidia] Missing VTs in kernel 5.15.0-22-generic (but 5.15.0-18-generic works). Also makes some systems unbootable if they display prompts
Nvidia-470 also works now with kernel 5.15.0-23-generic ** Changed in: nvidia-graphics-drivers-470 (Ubuntu) Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu. https://bugs.launchpad.net/bugs/1964305 Title: [nvidia] Missing VTs in kernel 5.15.0-22-generic (but 5.15.0-18-generic works). Also makes some systems unbootable if they display prompts Status in linux package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-470 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-510 package in Ubuntu: Fix Released Bug description: Missing VTs in kernel 5.15.0-22-generic (but 5.15.0-18-generic works). Steps to reproduce: 1. Boot Ubuntu. 2. Press Ctrl+Alt+F4. Expected: VT to be displayed Observed: Monitor turns off. Notes: * This failure only happens in 5.15.0-22-generic. Kernel version 5.15.0-18-generic works fine. * I am currently using the nvidia-470 driver in case that's relevant. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-22-generic 5.15.0-22.22 ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19 Uname: Linux 5.15.0-22-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-id', '/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/pcmC1D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass Date: Wed Mar 9 14:33:12 2022 InstallationDate: Installed on 2021-11-05 (123 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211103) MachineType: Intel(R) Client Systems NUC9i7QNX ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-22-generic root=UUID=70e2069c-a553-4c6d-abfc-c65e52cb3b43 ro quiet splash nvidia-drm.modeset=1 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-22-generic N/A linux-backports-modules-5.15.0-22-generic N/A linux-firmware 20220302.gitee0667aa-0ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/25/2019 dmi.bios.release: 5.13 dmi.bios.vendor: Intel Corp. dmi.bios.version: QXCFL579.0034.2019.1125.1436 dmi.board.name: NUC9i7QNB dmi.board.vendor: Intel Corporation dmi.board.version: K49245-402 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.ec.firmware.release: 24.33 dmi.modalias: dmi:bvnIntelCorp.:bvrQXCFL579.0034.2019.1125.1436:bd11/25/2019:br5.13:efr24.33:svnIntel(R)ClientSystems:pnNUC9i7QNX:pvrK49244-403:rvnIntelCorporation:rnNUC9i7QNB:rvrK49245-402:cvnIntelCorporation:ct35:cvr2.0:skuBXNUC9i7QNX: dmi.product.family: QN dmi.product.name: NUC9i7QNX dmi.product.sku: BXNUC9i7QNX dmi.product.version: K49244-403 dmi.sys.vendor: Intel(R) Client Systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1964305/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1964305] Re: [nvidia] Missing VTs in kernel 5.15.0-22-generic (but 5.15.0-18-generic works). Also makes some systems unbootable if they display prompts
Verified fixed in kernel 5.15.0-23-generic + nvidia 510.54-0ubuntu2 However: * I can't tell which package fixed it because 5.15.0-22-generic now refuses to boot. * If you have the monitor turned off during boot then the same problem occurs in 5.15.0-23-generic. ** Changed in: linux (Ubuntu) Status: Confirmed => Fix Released ** Changed in: nvidia-graphics-drivers-470 (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu. https://bugs.launchpad.net/bugs/1964305 Title: [nvidia] Missing VTs in kernel 5.15.0-22-generic (but 5.15.0-18-generic works). Also makes some systems unbootable if they display prompts Status in linux package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-470 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-510 package in Ubuntu: Fix Released Bug description: Missing VTs in kernel 5.15.0-22-generic (but 5.15.0-18-generic works). Steps to reproduce: 1. Boot Ubuntu. 2. Press Ctrl+Alt+F4. Expected: VT to be displayed Observed: Monitor turns off. Notes: * This failure only happens in 5.15.0-22-generic. Kernel version 5.15.0-18-generic works fine. * I am currently using the nvidia-470 driver in case that's relevant. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-22-generic 5.15.0-22.22 ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19 Uname: Linux 5.15.0-22-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-id', '/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/pcmC1D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass Date: Wed Mar 9 14:33:12 2022 InstallationDate: Installed on 2021-11-05 (123 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211103) MachineType: Intel(R) Client Systems NUC9i7QNX ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-22-generic root=UUID=70e2069c-a553-4c6d-abfc-c65e52cb3b43 ro quiet splash nvidia-drm.modeset=1 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-22-generic N/A linux-backports-modules-5.15.0-22-generic N/A linux-firmware 20220302.gitee0667aa-0ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/25/2019 dmi.bios.release: 5.13 dmi.bios.vendor: Intel Corp. dmi.bios.version: QXCFL579.0034.2019.1125.1436 dmi.board.name: NUC9i7QNB dmi.board.vendor: Intel Corporation dmi.board.version: K49245-402 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.ec.firmware.release: 24.33 dmi.modalias: dmi:bvnIntelCorp.:bvrQXCFL579.0034.2019.1125.1436:bd11/25/2019:br5.13:efr24.33:svnIntel(R)ClientSystems:pnNUC9i7QNX:pvrK49244-403:rvnIntelCorporation:rnNUC9i7QNB:rvrK49245-402:cvnIntelCorporation:ct35:cvr2.0:skuBXNUC9i7QNX: dmi.product.family: QN dmi.product.name: NUC9i7QNX dmi.product.sku: BXNUC9i7QNX dmi.product.version: K49244-403 dmi.sys.vendor: Intel(R) Client Systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1964305/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1917471] Re: [Regression] Bus Fatal Error observed when reboot on BCM5720
@Kai-Heng Feng In reply to comment #14 Issue is still observed even after blacklisting tg3 driver by giving "blacklist=tg3 modprobe.blacklist=tg3" in kernel parameter. Please find the serial logs of the efforts. ** Attachment added: "fatal_blacklist" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1917471/+attachment/5571631/+files/fatal_blacklist -- 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/1917471 Title: [Regression] Bus Fatal Error observed when reboot on BCM5720 Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: In Progress Status in linux source package in Impish: Fix Released Status in linux source package in Jammy: Fix Released Bug description: following error messages are observed [ 146.429212] shutdown[1]: Rebooting. [ 146.435151] kvm: exiting hardware virtualization [ 146.575319] megaraid_sas :67:00.0: megasas_disable_intr_fusion is called outbound_intr_mask:0x4009 [ 148.088133] [qede_unload:2236(eno12409)]Link is down [ 148.183618] qede :31:00.1: Ending qede_remove successfully [ 148.518541] [qede_unload:2236(eno12399)]Link is down [ 148.625066] qede :31:00.0: Ending qede_remove successfully [ 148.762067] ACPI: Preparing to enter system sleep state S5 [ 148.794638] {1}[Hardware Error]: Hardware error from APEI Generic Hardware Error Source: 5 [ 148.803731] {1}[Hardware Error]: event severity: recoverable [ 148.810191] {1}[Hardware Error]: Error 0, type: fatal [ 148.816088] {1}[Hardware Error]: section_type: PCIe error [ 148.822391] {1}[Hardware Error]: port_type: 0, PCIe end point [ 148.829026] {1}[Hardware Error]: version: 3.0 [ 148.834266] {1}[Hardware Error]: command: 0x0006, status: 0x0010 [ 148.841140] {1}[Hardware Error]: device_id: :04:00.0 [ 148.847309] {1}[Hardware Error]: slot: 0 [ 148.852077] {1}[Hardware Error]: secondary_bus: 0x00 [ 148.857876] {1}[Hardware Error]: vendor_id: 0x14e4, device_id: 0x165f [ 148.865145] {1}[Hardware Error]: class_code: 02 [ 148.870845] {1}[Hardware Error]: aer_uncor_status: 0x0010, aer_uncor_mask: 0x0001 [ 148.879842] {1}[Hardware Error]: aer_uncor_severity: 0x000ef030 [ 148.886575] {1}[Hardware Error]: TLP Header: 4001 030f 90028090 [ 148.894823] tg3 :04:00.0: AER: aer_status: 0x0010, aer_mask: 0x0001 [ 148.902795] tg3 :04:00.0: AER:[20] UnsupReq (First) [ 148.910234] tg3 :04:00.0: AER: aer_layer=Transaction Layer, aer_agent=Requester ID [ 148.918806] tg3 :04:00.0: AER: aer_uncor_severity: 0x000ef030 [ 148.925558] tg3 :04:00.0: AER: TLP Header: 4001 030f 90028090 [ 148.933984] reboot: Restarting system [ 148.938319] reboot: machine restart I have observed the following. when I test older kernel Kernel version Fatal Error 5.4.0-42.46 No 5.4.0-45.49 No 5.4.0-47.51 No 5.4.0-48.52 No 5.4.0-51.56 No 5.4.0-52.57 No 5.4.0-53.59 No 5.4.0-54.60 No 5.4.0-58.64 No 5.4.0-59.65 yes 5.4.0-60.67 yes later I have bisect kernel between 5.4.0-58.64 and 5.4.0-59.65. looks like due to the following patch we are observing this issue. The driver is not handling D3 state properly PCI/ACPI: Whitelist hotplug ports for D3 if power managed by ACPI https://kernel.ubuntu.com/git/ubuntu/ubuntu- focal.git/commit/?id=b9319dd02269593911403dd5d684368bcef3261d To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1917471/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1965862] 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/1965862 Title: package linux-modules-5.4.0-104-generic 5.4.0-104.118 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting a removal Status in linux package in Ubuntu: Confirmed Bug description: ACPI BIOS Error (bug): AE_AML_BUFFER_LIMIT, Field [TBF3] at bit offset/length 258048/32768 exceeds size of target Buffer (266240 bits) (20190816/dsopcode-198) ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-modules-5.4.0-104-generic 5.4.0-104.118 ProcVersionSignature: Ubuntu 5.4.0-100.113-generic 5.4.166 Uname: Linux 5.4.0-100-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 AptOrdering: linux-modules-5.4.0-104-generic:amd64: Remove NULL: ConfigurePending Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mira 1706 F pulseaudio CasperMD5CheckResult: skip Date: Tue Mar 22 08:22:09 2022 Dependencies: ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting a removal MachineType: LENOVO 20RD0086UE ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-100-generic root=UUID=5162038d-18b6-4c77-a50f-d7f0326bf5af ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: grub-pc 2.04-1ubuntu26.13 SourcePackage: linux Title: package linux-modules-5.4.0-104-generic 5.4.0-104.118 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting a removal UpgradeStatus: Upgraded to focal on 2021-08-03 (230 days ago) dmi.bios.date: 01/28/2022 dmi.bios.vendor: LENOVO dmi.bios.version: R16ET34W (1.20 ) dmi.board.asset.tag: Not Available dmi.board.name: 20RD0086UE dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR16ET34W(1.20):bd01/28/2022:svnLENOVO:pn20RD0086UE:pvrThinkPadE15:rvnLENOVO:rn20RD0086UE:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad E15 dmi.product.name: 20RD0086UE dmi.product.sku: LENOVO_MT_20RD_BU_SMB_FM_ThinkPad E15 dmi.product.version: ThinkPad E15 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1965862/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1960865] Re: System freeze when plugging USB-C monitor into a hybrid Intel/Nvidia laptop: [drm:__nv_drm_gem_nvkms_memory_prime_get_sg_table [nvidia_drm]] *ERROR* [nvidia-drm] [G
Would I be correct in thinking that the Nvidia-510 driver turned this into bug 1964037 and bug 1959888 instead? If so then we could just declare "Won't Fix" for nvidia-470. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu. https://bugs.launchpad.net/bugs/1960865 Title: System freeze when plugging USB-C monitor into a hybrid Intel/Nvidia laptop: [drm:__nv_drm_gem_nvkms_memory_prime_get_sg_table [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x0100] Failed to get memory pages for NvKmsKapiMemory Status in Mutter: Unknown Status in nvidia-graphics-drivers-470 package in Ubuntu: Confirmed Bug description: I recently upgraded my NVidia drivers on my ThinkPad P1 Gen 3. If I start Ubuntu on Wayland session and plug in my USB-C monitor the system reliably completely freeze. The freeze is also reproducible if the screen is plugged in during startup and trying to login into a Wayland session. Only Wayland session experiences a crash. The crash happens ONLY if the USB-C monitor is plugged in. USB-C monitor is also a USB3 hub. Hardware seems to work fine, as Windows shows no issues with the setup. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: xorg 1:7.7+22ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-30.33-generic 5.13.19 Uname: Linux 5.13.0-30-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 470.103.01 Thu Jan 6 12:10:04 UTC 2022 GCC version: gcc version 11.2.0 (Ubuntu 11.2.0-7ubuntu2) ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Feb 14 16:39:34 2022 DistUpgraded: 2021-10-14 18:36:11,564 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: impish DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Within the last few days GraphicsCard: Intel Corporation CometLake-H GT2 [UHD Graphics] [8086:9bc4] (rev 05) (prog-if 00 [VGA controller]) Subsystem: Lenovo CometLake-H GT2 [UHD Graphics] [17aa:22c1] NVIDIA Corporation TU117GLM [Quadro T1000 Mobile] [10de:1fb9] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo TU117GLM [Quadro T1000 Mobile] [17aa:22c1] InstallationDate: Installed on 2020-10-05 (497 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: LENOVO 20THCT01WW ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-30-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to impish on 2021-10-14 (122 days ago) dmi.bios.date: 12/27/2021 dmi.bios.release: 1.21 dmi.bios.vendor: LENOVO dmi.bios.version: N2VET36W (1.21 ) dmi.board.asset.tag: Not Available dmi.board.name: 20THCT01WW dmi.board.vendor: LENOVO dmi.board.version: 0B98417 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.10 dmi.modalias: dmi:bvnLENOVO:bvrN2VET36W(1.21):bd12/27/2021:br1.21:efr1.10:svnLENOVO:pn20THCT01WW:pvrThinkPadP1Gen3:rvnLENOVO:rn20THCT01WW:rvr0B98417WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20TH_BU_Think_FM_ThinkPadP1Gen3: dmi.product.family: ThinkPad P1 Gen 3 dmi.product.name: 20THCT01WW dmi.product.sku: LENOVO_MT_20TH_BU_Think_FM_ThinkPad P1 Gen 3 dmi.product.version: ThinkPad P1 Gen 3 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.6-0ubuntu0.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-x
[Kernel-packages] [Bug 1965862] [NEW] package linux-modules-5.4.0-104-generic 5.4.0-104.118 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before atte
Public bug reported: ACPI BIOS Error (bug): AE_AML_BUFFER_LIMIT, Field [TBF3] at bit offset/length 258048/32768 exceeds size of target Buffer (266240 bits) (20190816/dsopcode-198) ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-modules-5.4.0-104-generic 5.4.0-104.118 ProcVersionSignature: Ubuntu 5.4.0-100.113-generic 5.4.166 Uname: Linux 5.4.0-100-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 AptOrdering: linux-modules-5.4.0-104-generic:amd64: Remove NULL: ConfigurePending Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mira 1706 F pulseaudio CasperMD5CheckResult: skip Date: Tue Mar 22 08:22:09 2022 Dependencies: ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting a removal MachineType: LENOVO 20RD0086UE ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-100-generic root=UUID=5162038d-18b6-4c77-a50f-d7f0326bf5af ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: grub-pc 2.04-1ubuntu26.13 SourcePackage: linux Title: package linux-modules-5.4.0-104-generic 5.4.0-104.118 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting a removal UpgradeStatus: Upgraded to focal on 2021-08-03 (230 days ago) dmi.bios.date: 01/28/2022 dmi.bios.vendor: LENOVO dmi.bios.version: R16ET34W (1.20 ) dmi.board.asset.tag: Not Available dmi.board.name: 20RD0086UE dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR16ET34W(1.20):bd01/28/2022:svnLENOVO:pn20RD0086UE:pvrThinkPadE15:rvnLENOVO:rn20RD0086UE:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad E15 dmi.product.name: 20RD0086UE dmi.product.sku: LENOVO_MT_20RD_BU_SMB_FM_ThinkPad E15 dmi.product.version: ThinkPad E15 dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-package focal need-duplicate-check -- 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/1965862 Title: package linux-modules-5.4.0-104-generic 5.4.0-104.118 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting a removal Status in linux package in Ubuntu: Confirmed Bug description: ACPI BIOS Error (bug): AE_AML_BUFFER_LIMIT, Field [TBF3] at bit offset/length 258048/32768 exceeds size of target Buffer (266240 bits) (20190816/dsopcode-198) ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-modules-5.4.0-104-generic 5.4.0-104.118 ProcVersionSignature: Ubuntu 5.4.0-100.113-generic 5.4.166 Uname: Linux 5.4.0-100-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 AptOrdering: linux-modules-5.4.0-104-generic:amd64: Remove NULL: ConfigurePending Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mira 1706 F pulseaudio CasperMD5CheckResult: skip Date: Tue Mar 22 08:22:09 2022 Dependencies: ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting a removal MachineType: LENOVO 20RD0086UE ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-100-generic root=UUID=5162038d-18b6-4c77-a50f-d7f0326bf5af ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: grub-pc 2.04-1ubuntu26.13 SourcePackage: linux Title: package linux-modules-5.4.0-104-generic 5.4.0-104.118 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting a removal UpgradeStatus: Upgraded to focal on 2021-08-03 (230 days ago) dmi.bios.date: 01/28/2022 dmi.bios.vendor: LENOVO dmi.bios.version: R16ET34W (1.20 ) dmi.board.asset.tag: Not Available dmi.board.name: 20RD0086UE dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR16ET34W(1.20):bd01/28/2022:svnLENOVO:pn20RD0086UE:pvrThinkPadE15:rvnLENOVO:rn20RD0086UE:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.fa