[Kernel-packages] [Bug 1969815] Re: [radeon] Dual screens started blinking from blank to another type of blank for =<1 second each state
I'm suddenly reminded of bug 1971146. Please try adding kernel parameter: intel_iommu=off to /etc/default/grub (in GRUB_CMDLINE_LINUX_DEFAULT) and then run: sudo update-grub and reboot. -- 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/1969815 Title: [radeon] Dual screens started blinking from blank to another type of blank for =<1 second each state Status in linux package in Ubuntu: Confirmed Status in marco package in Ubuntu: New Status in xorg-server package in Ubuntu: New Bug description: I've just updated to 22.04 on 3x boxes: 2x laptops and 1x tower. Laptops went well as they are standard running wifi (note to self: next time upgrade one using a USB docking station+as many externally attached devices as possible should prove in a quite pleasurable end- user experience) For the tower: this is the dual-screen portrait system I have been opening up defects for months now. Same config too. Anyways, after I rebooted the overall booting process happened pretty well until TTY7 tried kicking it and totally failed doing so hence rendered my system totally broken. The behavior of my screens is that they started blinking from blank to another type of blank for =<1 second each state. But during one of those states there seemed to be Wayland as I could just see the mouse cursor fly around when activated. Accessing other TTYs was also impossible as even though pressing CTRL+ALT+F2|F3|etc would indeed display a login prompt that within that same blinking instant that it had altered back to only that blinking cursor symbol(_) at the top-hand-left. That behavior held true for all TTYs. Pressing the power button did showed up the UM symbol alongside standard shutdown routine happened OK. Solution was: unplug one of the two monitor and automagically jammy's login screen popped up. If I replug that 2nd monitor while I am inside a working TTY7 session then the same (original) problem happens in which I cannot use any of the screens and when I re-unplug one of the two screens again I am re- back again at the jammy login having lost the current session that I had. Both of my screens are the same model and both use HDMI. I have attached my ~/.config/monitors.xml --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: dd3464333 F pulseaudio /dev/snd/controlC0: dd3464333 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: MATE DistroRelease: Ubuntu 22.04 HibernationDevice: RESUME=UUID=88228def-1fb1-4fc3-964c-3106218355eb InstallationDate: Installed on 2020-08-29 (613 days ago) InstallationMedia: Ubuntu-MATE 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) IwConfig: lono wireless extensions. enp7s0no wireless extensions. tun0 no wireless extensions. MachineType: System manufacturer System Product Name Package: xorg-server PackageArchitecture: amd64 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-25-generic root=/dev/mapper/vgubuntu--mate-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 RelatedPackageVersions: linux-restricted-modules-5.15.0-25-generic N/A linux-backports-modules-5.15.0-25-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 RfKill: Tags: jammy Uname: Linux 5.15.0-25-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-21 (13 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/02/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5809 dmi.board.asset.tag: Default string dmi.board.name: TUF X470-PLUS GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5809:bd12/02/2020:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFX470-PLUSGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1969815/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1971955] Re: systemd-udevd call unshare process when attaching nvme volume
Mauricio, you are right, there is no function issue. just concern about the annoying snap log entries -- 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/1971955 Title: systemd-udevd call unshare process when attaching nvme volume Status in dellserver: New Status in linux package in Ubuntu: Invalid Status in snapd package in Ubuntu: New Bug description: env: PRETTY_NAME="Ubuntu 22.04 LTS" NAME="Ubuntu" VERSION_ID="22.04" VERSION="22.04 (Jammy Jellyfish)" VERSION_CODENAME=jammy # lsb_release -rd Description:Ubuntu 22.04 LTS Release:22.04 host connect dellemc powerstore with nvme-tcp connection # nvme list-subsys nvme-subsys0 - NQN=nqn.1988-11.com.dell:powerstore:00:d42d581e674f2B16F2E2 \ +- nvme1 tcp traddr=172.16.100.165 trsvcid=4420 live +- nvme2 tcp traddr=172.16.200.164 trsvcid=4420 live +- nvme3 tcp traddr=172.16.200.165 trsvcid=4420 live +- nvme4 tcp traddr=172.16.100.164 trsvcid=4420 live when attaching new volume to host. systemd-udevd trigger unshare process to run snap import command on new volumes and it fail. volume finally map to host. it doesn't affect volume usage. but some udev rule need to check for this strange behavior. May 06 08:16:43 e2e-l4-094051 systemd-udevd[33374]: nvme0n234: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme0n234' failed with exit code 1. May 06 08:16:43 e2e-l4-094051 systemd-udevd[33371]: nvme0n232: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme0n232' failed with exit code 1. May 06 08:16:43 e2e-l4-094051 systemd-udevd[33378]: nvme0n236: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme0n236' failed with exit code 1. May 06 08:16:43 e2e-l4-094051 systemd-udevd[33384]: nvme0n239: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme0n239' failed with exit code 1. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 6 08:14 seq crw-rw 1 root audio 116, 33 May 6 08:14 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-05-04 (2 days ago) InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220421) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 002: ID 8087:8002 Intel Corp. 8 channel internal hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub Bus 001 Device 002: ID 8087:800a Intel Corp. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/2p, 480M |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/8p, 480M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/2p, 480M |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/6p, 480M |__ Port 6: Dev 3, If 0, Class=Hub, Driver=hub/6p, 480M Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-27-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 RelatedPackageVersions: linux-restricted-modules-5.15.0-27-generic N/A linux-backports-modules-5.15.0-27-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: jammy uec-images Uname: Linux 5.15.0-27-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 05/14/2021 dmi.bios.release: 2.13 dmi.bios.version: 2.13.0 dmi.board.name: 072T6D dmi.board.version: A01 dmi.chassis.type: 23 dmi.modalias: dmi:bvn:bvr2.13.0:bd05/14/2021:br2.13:svn:pn:pvr:rvn:rn072T6D:rvrA01:cvn:ct23:cvr:skuSKU=NotProvided;ModelName=: dmi.product.sku: SKU=NotProvided;ModelName= To manage notifications about this bug go to: https://bugs.launchpad.net/dellserver/+bug/1971955/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1930795] Re: Keyboard and mouse no longer work with Kernel 5.4.0-74
I'm guessing something corrupted my install. When I wiped everything and did a fresh install of 22.04 I don't have this problem, so it maybe some upgrade messed up some settings or something. -- 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/1930795 Title: Keyboard and mouse no longer work with Kernel 5.4.0-74 Status in linux package in Ubuntu: Confirmed Bug description: My computer was working this morning, but when I powered it back on this afternoon the keyboard and mouse do not function. I have a desktop pc, 3 monitors, encrypted boot drive. dpkg showed that kernel 5.4.0-74 was installed on my computer this morning. When I boot with kernel 5.4.0-74, my keyboard allows me to enter my decryption password, but my computer boots with one monitor active and the USB keyboard and USB mouse do not respond. (Using a different USB keyboard makes no difference. Unplugging the keyboard and plugging it back in makes no difference.) When I use GRUB to boot with kernel 5.4.0-73, my system works as expected (and all 3 monitors light up). REQUIRED DETAILS: lsb_release -rd Description:Ubuntu 20.04.2 LTS Release:20.04 apt-cache policy linux-generic linux-generic: Installed: 5.4.0.74.77 Candidate: 5.4.0.74.77 Version table: *** 5.4.0.74.77 500 500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu focal-security/main amd64 Packages 100 /var/lib/dpkg/status 5.4.0.26.32 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages Any help would be GREATLY appreciated. Thank you! ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-73-generic 5.4.0-73.82 ProcVersionSignature: Ubuntu 5.4.0-73.82-generic 5.4.106 Uname: Linux 5.4.0-73-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ir 1650 F pulseaudio /dev/snd/controlC0: ir 1650 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: Unity:Unity7:ubuntu Date: Thu Jun 3 21:05:15 2021 HibernationDevice: RESUME=UUID=01f6ff4d-fc7b-4a2b-9b64-5a099cc1a441 InstallationDate: Installed on 2017-04-27 (1499 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) IwConfig: lono wireless extensions. enp0s31f6 no wireless extensions. MachineType: System manufacturer System Product Name ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-73-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-73-generic N/A linux-backports-modules-5.4.0-73-generic N/A linux-firmware1.187.12 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-11-05 (210 days ago) dmi.bios.date: 03/15/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1302 dmi.board.asset.tag: Default string dmi.board.name: PRIME Z270-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1302:bd03/15/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ270-A:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1930795/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1967924] Re: re-apply missing overlayfs SAUCE patch
@mihalicyn Yes, this patch without AUFS enabled doesn't introduce any
problem, but that's because without AUFS the patch is basically a no-op.
Here's the ported patch that was applied to 5.15:
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/focal/commit/?h=hwe-5.15-next=e3e60b65fa4db4722bd4b02a9dae58f7ff5d83d2
It'd be great if you could take a look and see if you spot any obvious
bugs. I'll do more tests later today, trying to better figure out the
real issue here.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1967924
Title:
re-apply missing overlayfs SAUCE patch
Status in linux package in Ubuntu:
Fix Committed
Status in linux source package in Impish:
Fix Committed
Status in linux source package in Jammy:
In Progress
Bug description:
[Impact]
Starting with 5.13 we've incorrectly dropped the following sauce
patch:
UBUNTU: SAUCE: overlayfs: fix incorrect mnt_id of files opened
from map_files
This patch seems to be required to use overlayfs on top of shiftfs and
without this patch we may break containers that rely on shiftfs (using
zfs/ceph as storage pool w/ shiftfs enabled).
[Test case]
No specific test case provided.
[Fix]
The original SAUCE patch relies on AUFS in order to use
vma->vm_prfile, but we're not providing AUFS anymore in jammy,.
The fix consists of re-apply this patch with a little refactoring to
be dependent on CONFIG_AUFS_FS.
[Regression potential]
This patch is touching overlayfs, so we may see potential regressions
in overlayfs.
[Original bug report]
The next patch has not been ported to the the 5.13 branch:
$ git show Ubuntu-azure-5.8-5.8.0-1033.35_20.04.1~656
commit 5f5716d1f7ece06c66d7d8145dd6b3a5886b3e56
Author: Alexander Mikhalitsyn
Date: Mon Apr 26 10:11:00 2021 +0200
UBUNTU: SAUCE: overlayfs: fix incorrect mnt_id of files opened
from map_files
BugLink: https://bugs.launchpad.net/bugs/1857257
...
Fixes: d24b8a5 ("UBUNTU: SAUCE: overlayfs: allow with shiftfs as
underlay")
But it isn't in the 5.13 branch:
$ git log --pretty=oneline origin/azure-5.13-next fs/overlayfs/file.c
1e6145d8708c831d2aa5c26aa15eb98e1a1683b9 ovl: fix use after free in struct
ovl_aio_req
7b5bda27d1fc4d7bde20cf6ed203fe88c458169a ovl: fix IOCB_DIRECT if underlying
fs doesn't support direct IO
1626e7f7ab7eb74e142fec7fe6b7c9614972a56b ovl: fix deadlock in splice write
1443bc4a25ca84d60d39a8ae1dc6215abdd637a4 UBUNTU: SAUCE: overlayfs: allow with
shiftfs as underlay
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967924/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1972134] Re: AMD APU s2idle is broken after the ASIC reset fix
** 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 (Ubuntu Jammy) Status: New => Confirmed ** Changed in: linux (Ubuntu Jammy) Importance: Undecided => High ** 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-oem-5.14 (Ubuntu Focal) Importance: Undecided => High ** Description changed: - [Impact] - AMD reported fix for LP: #1968475 breaks AMD APU s2idle + [Impact] + The AMD based system can not reach s2idle after fix for LP: #1968475. [Fix] - TBD + No need to evict resources for s2idle case. [Test] - TBD + Test on a Cezanne, confirmed the 5.14.0-1035 breaks s2idle, and applying + the fix can make s2idle work again. [Where problems could occur] - TBD + The fix only applies to AMD APU, and the resources sould stay at carved + out region over sleep. -- 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/1972134 Title: AMD APU s2idle is broken after the ASIC reset fix Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.14 package in Ubuntu: New 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] The AMD based system can not reach s2idle after fix for LP: #1968475. [Fix] No need to evict resources for s2idle case. [Test] Test on a Cezanne, confirmed the 5.14.0-1035 breaks s2idle, and applying the fix can make s2idle work again. [Where problems could occur] The fix only applies to AMD APU, and the resources sould stay at carved out region over sleep. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1972134/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1972134] Re: AMD APU s2idle is broken after the ASIC reset fix
** 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/1972134 Title: AMD APU s2idle is broken after the ASIC reset fix Status in linux package in Ubuntu: Confirmed Bug description: [Impact] AMD reported fix for LP: #1968475 breaks AMD APU s2idle [Fix] TBD [Test] TBD [Where problems could occur] TBD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1972134/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1971955] Re: systemd-udevd call unshare process when attaching nvme volume
** Also affects: dellserver Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1971955 Title: systemd-udevd call unshare process when attaching nvme volume Status in dellserver: New Status in linux package in Ubuntu: Invalid Status in snapd package in Ubuntu: New Bug description: env: PRETTY_NAME="Ubuntu 22.04 LTS" NAME="Ubuntu" VERSION_ID="22.04" VERSION="22.04 (Jammy Jellyfish)" VERSION_CODENAME=jammy # lsb_release -rd Description:Ubuntu 22.04 LTS Release:22.04 host connect dellemc powerstore with nvme-tcp connection # nvme list-subsys nvme-subsys0 - NQN=nqn.1988-11.com.dell:powerstore:00:d42d581e674f2B16F2E2 \ +- nvme1 tcp traddr=172.16.100.165 trsvcid=4420 live +- nvme2 tcp traddr=172.16.200.164 trsvcid=4420 live +- nvme3 tcp traddr=172.16.200.165 trsvcid=4420 live +- nvme4 tcp traddr=172.16.100.164 trsvcid=4420 live when attaching new volume to host. systemd-udevd trigger unshare process to run snap import command on new volumes and it fail. volume finally map to host. it doesn't affect volume usage. but some udev rule need to check for this strange behavior. May 06 08:16:43 e2e-l4-094051 systemd-udevd[33374]: nvme0n234: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme0n234' failed with exit code 1. May 06 08:16:43 e2e-l4-094051 systemd-udevd[33371]: nvme0n232: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme0n232' failed with exit code 1. May 06 08:16:43 e2e-l4-094051 systemd-udevd[33378]: nvme0n236: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme0n236' failed with exit code 1. May 06 08:16:43 e2e-l4-094051 systemd-udevd[33384]: nvme0n239: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme0n239' failed with exit code 1. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 6 08:14 seq crw-rw 1 root audio 116, 33 May 6 08:14 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-05-04 (2 days ago) InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220421) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 002: ID 8087:8002 Intel Corp. 8 channel internal hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub Bus 001 Device 002: ID 8087:800a Intel Corp. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/2p, 480M |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/8p, 480M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/2p, 480M |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/6p, 480M |__ Port 6: Dev 3, If 0, Class=Hub, Driver=hub/6p, 480M Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-27-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 RelatedPackageVersions: linux-restricted-modules-5.15.0-27-generic N/A linux-backports-modules-5.15.0-27-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: jammy uec-images Uname: Linux 5.15.0-27-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 05/14/2021 dmi.bios.release: 2.13 dmi.bios.version: 2.13.0 dmi.board.name: 072T6D dmi.board.version: A01 dmi.chassis.type: 23 dmi.modalias: dmi:bvn:bvr2.13.0:bd05/14/2021:br2.13:svn:pn:pvr:rvn:rn072T6D:rvrA01:cvn:ct23:cvr:skuSKU=NotProvided;ModelName=: dmi.product.sku: SKU=NotProvided;ModelName= To manage notifications about this bug go to: https://bugs.launchpad.net/dellserver/+bug/1971955/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1972140] 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/1972140 Title: UBSAN: array-index-out-of-bounds in /build/linux- HMZHpV/linux-5.15.0/drivers/net/wireless/ath/ath5k/base.c:1695:20 Status in linux package in Ubuntu: Confirmed Bug description: [114914.279420] [114914.279431] UBSAN: array-index-out-of-bounds in /build/linux-HMZHpV/linux-5.15.0/drivers/net/wireless/ath/ath5k/base.c:1695:20 [114914.279436] index 4 is out of range for type 'ieee80211_tx_rate [4]' [114914.279440] CPU: 1 PID: 0 Comm: swapper/1 Tainted: P IOE 5.15.0-27-generic #28-Ubuntu [114914.279445] Hardware name: Dell Inc. Precision WorkStation T7500 /0D881F, BIOS A18 10/15/2018 [114914.279448] Call Trace: [114914.279451] [114914.279455] show_stack+0x52/0x58 [114914.279465] dump_stack_lvl+0x4a/0x5f [114914.279475] dump_stack+0x10/0x12 [114914.279478] ubsan_epilogue+0x9/0x45 [114914.279482] __ubsan_handle_out_of_bounds.cold+0x44/0x49 [114914.279487] ? iommu_dma_unmap_page+0x4a/0x50 [114914.279492] ath5k_tx_frame_completed.constprop.0+0x279/0x2c0 [ath5k] [114914.279507] ath5k_tx_processq+0xb1/0x1c0 [ath5k] [114914.279519] ath5k_tasklet_tx+0x7b/0xf0 [ath5k] [114914.279531] tasklet_action_common.constprop.0+0xc0/0xf0 [114914.279539] tasklet_action+0x22/0x30 [114914.279543] __do_softirq+0xd9/0x2e3 [114914.279550] irq_exit_rcu+0x8c/0xb0 [114914.279554] common_interrupt+0x8a/0xa0 [114914.279560] [114914.279562] [114914.279563] asm_common_interrupt+0x1e/0x40 [114914.279568] RIP: 0010:cpuidle_enter_state+0xd9/0x620 [114914.279574] Code: 3d 14 5b be 67 e8 d7 ad 6c ff 49 89 c7 0f 1f 44 00 00 31 ff e8 28 ba 6c ff 80 7d d0 00 0f 85 5d 01 00 00 fb 66 0f 1f 44 00 00 <45> 85 f6 0f 88 69 01 00 00 4d 63 ee 49 83 fd 09 0f 87 e3 03 00 00 [114914.279577] RSP: 0018:adc58009be28 EFLAGS: 0292 [114914.279582] RAX: RBX: cdc57ee79f00 RCX: 0020 [114914.279584] RDX: 02c71492 RSI: 3d66 RDI: 99807a40 [114914.279587] RBP: adc58009be78 R08: R09: 000c3500 [114914.279589] R10: 0005 R11: 071c71c71c71c71c R12: 99ad3580 [114914.279592] R13: 0004 R14: 0004 R15: 688390cd49d1 [114914.279597] ? cpuidle_enter_state+0x246/0x620 [114914.279601] cpuidle_enter+0x2e/0x40 [114914.279605] cpuidle_idle_call+0x13e/0x1e0 [114914.279610] do_idle+0x83/0xf0 [114914.279614] cpu_startup_entry+0x20/0x30 [114914.279617] start_secondary+0x12a/0x180 [114914.279622] secondary_startup_64_no_verify+0xc2/0xcb [114914.279630] [114914.279632] ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-27-generic 5.15.0-27.28 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: js1 17869 F pulseaudio /dev/snd/controlC1: js1 17869 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: LXQt Date: Sun May 8 23:36:44 2022 InstallationDate: Installed on 2020-02-02 (826 days ago) InstallationMedia: Lubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017.1) MachineType: Dell Inc. Precision WorkStation T7500 ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=93fc02c6-baa4-4282-96d7-ea5ad53b0c78 ro ipv6.disable=1 splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-27-generic N/A linux-backports-modules-5.15.0-27-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/15/2018 dmi.bios.release: 0.0 dmi.bios.vendor: Dell Inc. dmi.bios.version: A18 dmi.board.name: 0D881F dmi.board.vendor: Dell Inc. dmi.board.version: A05 dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA18:bd10/15/2018:br0.0:svnDellInc.:pnPrecisionWorkStationT7500:pvr:rvnDellInc.:rn0D881F:rvrA05:cvnDellInc.:ct7:cvr:sku: dmi.product.name: Precision WorkStation T7500 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to:
[Kernel-packages] [Bug 1972140] [NEW] UBSAN: array-index-out-of-bounds in /build/linux-HMZHpV/linux-5.15.0/drivers/net/wireless/ath/ath5k/base.c:1695:20
Public bug reported: [114914.279420] [114914.279431] UBSAN: array-index-out-of-bounds in /build/linux-HMZHpV/linux-5.15.0/drivers/net/wireless/ath/ath5k/base.c:1695:20 [114914.279436] index 4 is out of range for type 'ieee80211_tx_rate [4]' [114914.279440] CPU: 1 PID: 0 Comm: swapper/1 Tainted: P IOE 5.15.0-27-generic #28-Ubuntu [114914.279445] Hardware name: Dell Inc. Precision WorkStation T7500 /0D881F, BIOS A18 10/15/2018 [114914.279448] Call Trace: [114914.279451] [114914.279455] show_stack+0x52/0x58 [114914.279465] dump_stack_lvl+0x4a/0x5f [114914.279475] dump_stack+0x10/0x12 [114914.279478] ubsan_epilogue+0x9/0x45 [114914.279482] __ubsan_handle_out_of_bounds.cold+0x44/0x49 [114914.279487] ? iommu_dma_unmap_page+0x4a/0x50 [114914.279492] ath5k_tx_frame_completed.constprop.0+0x279/0x2c0 [ath5k] [114914.279507] ath5k_tx_processq+0xb1/0x1c0 [ath5k] [114914.279519] ath5k_tasklet_tx+0x7b/0xf0 [ath5k] [114914.279531] tasklet_action_common.constprop.0+0xc0/0xf0 [114914.279539] tasklet_action+0x22/0x30 [114914.279543] __do_softirq+0xd9/0x2e3 [114914.279550] irq_exit_rcu+0x8c/0xb0 [114914.279554] common_interrupt+0x8a/0xa0 [114914.279560] [114914.279562] [114914.279563] asm_common_interrupt+0x1e/0x40 [114914.279568] RIP: 0010:cpuidle_enter_state+0xd9/0x620 [114914.279574] Code: 3d 14 5b be 67 e8 d7 ad 6c ff 49 89 c7 0f 1f 44 00 00 31 ff e8 28 ba 6c ff 80 7d d0 00 0f 85 5d 01 00 00 fb 66 0f 1f 44 00 00 <45> 85 f6 0f 88 69 01 00 00 4d 63 ee 49 83 fd 09 0f 87 e3 03 00 00 [114914.279577] RSP: 0018:adc58009be28 EFLAGS: 0292 [114914.279582] RAX: RBX: cdc57ee79f00 RCX: 0020 [114914.279584] RDX: 02c71492 RSI: 3d66 RDI: 99807a40 [114914.279587] RBP: adc58009be78 R08: R09: 000c3500 [114914.279589] R10: 0005 R11: 071c71c71c71c71c R12: 99ad3580 [114914.279592] R13: 0004 R14: 0004 R15: 688390cd49d1 [114914.279597] ? cpuidle_enter_state+0x246/0x620 [114914.279601] cpuidle_enter+0x2e/0x40 [114914.279605] cpuidle_idle_call+0x13e/0x1e0 [114914.279610] do_idle+0x83/0xf0 [114914.279614] cpu_startup_entry+0x20/0x30 [114914.279617] start_secondary+0x12a/0x180 [114914.279622] secondary_startup_64_no_verify+0xc2/0xcb [114914.279630] [114914.279632] ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-27-generic 5.15.0-27.28 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: js1 17869 F pulseaudio /dev/snd/controlC1: js1 17869 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: LXQt Date: Sun May 8 23:36:44 2022 InstallationDate: Installed on 2020-02-02 (826 days ago) InstallationMedia: Lubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017.1) MachineType: Dell Inc. Precision WorkStation T7500 ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=93fc02c6-baa4-4282-96d7-ea5ad53b0c78 ro ipv6.disable=1 splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-27-generic N/A linux-backports-modules-5.15.0-27-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/15/2018 dmi.bios.release: 0.0 dmi.bios.vendor: Dell Inc. dmi.bios.version: A18 dmi.board.name: 0D881F dmi.board.vendor: Dell Inc. dmi.board.version: A05 dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA18:bd10/15/2018:br0.0:svnDellInc.:pnPrecisionWorkStationT7500:pvr:rvnDellInc.:rn0D881F:rvrA05:cvnDellInc.:ct7:cvr:sku: dmi.product.name: Precision WorkStation T7500 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1972140 Title: UBSAN: array-index-out-of-bounds in /build/linux- HMZHpV/linux-5.15.0/drivers/net/wireless/ath/ath5k/base.c:1695:20 Status in linux package in Ubuntu: New Bug description: [114914.279420] [114914.279431] UBSAN: array-index-out-of-bounds in /build/linux-HMZHpV/linux-5.15.0/drivers/net/wireless/ath/ath5k/base.c:1695:20
[Kernel-packages] [Bug 1968475] Re: Fix broken HDMI audio on AMD PRO VII after S3
My team reproed it on Rembrandt but based on the failure (not getting deepest state due to gfx) it should repro on Cezanne too. -- 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/1968475 Title: Fix broken HDMI audio on AMD PRO VII after S3 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: Fix Committed Status in linux source package in Jammy: Fix Committed Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: [Impact] DP/HDMI audio on AMD PRO VII stops working after S3. [Fix] Ensure HDA function is suspended before ASIC reset so the subsequent resume can be carried out successfully. [Test] With the patch applied, DP/HDMI audio continues to work after S3. [Where problems could occur] The suspend_noirq phase should not trigger any interrupt, so if amdgpu_asic_reset() somehow raised IRQ, it can break the system. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1968475/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1969326] Re: Enable hotspot feature for Realtek 8821CE
Hello @soumadeepsarkar1, Can you help to install oem kernel and re-test on your DUT? $ sudo apt install linux-oem-20.04d ** 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-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1969326 Title: Enable hotspot feature for Realtek 8821CE Status in HWE Next: New Status in OEM Priority Project: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: In Progress Status in linux source package in Focal: Invalid Status in linux-oem-5.14 source package in Focal: Fix Committed Status in linux-oem-5.17 source package in Focal: Invalid Status in linux source package in Jammy: In Progress Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: In Progress Bug description: [Impact] The wifi hotspot doesn't work without the fix. [Fix] Realtek provides us the patches to add this feature which are still in linux-next. https://patchwork.kernel.org/project/linux-wireless/cover/20220407095858.46807-1-pks...@realtek.com/ ece31c93d4d6 rtw88: 8821c: fix debugfs rssi value f5207c122102 rtw88: do PHY calibration while starting AP f1c4dabfe68d rtw88: 8821c: Enable TX report for management frames f2217968ffda rtw88: Add update beacon flow for AP mode 6723c0cde84f rtw88: fix incorrect frequency reported c1edc86472fc rtw88: add ieee80211:sta_rc_update ops Realtek provides us another series of patches for 5.14, and it contains 5 commits, we'd verified this series of patches. [Test] Verified on the Realtek 8821CE card. [Where problems could occur] The patches are introducing new interfaces, I think it only has minimal impact to the origin behaviors. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1969326/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1969326] Re: Enable hotspot feature for Realtek 8821CE
Enable proposed on DUT which uses RTL8821CE [10ec:c828] and install 5.14.0-1035.38. Hotspot works fine. My smart phone can connect it and surf the internet. ** Attachment added: "dmesg.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1969326/+attachment/5587781/+files/dmesg.txt -- 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/1969326 Title: Enable hotspot feature for Realtek 8821CE Status in HWE Next: New Status in OEM Priority Project: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: In Progress Status in linux source package in Focal: Invalid Status in linux-oem-5.14 source package in Focal: Fix Committed Status in linux-oem-5.17 source package in Focal: Invalid Status in linux source package in Jammy: In Progress Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: In Progress Bug description: [Impact] The wifi hotspot doesn't work without the fix. [Fix] Realtek provides us the patches to add this feature which are still in linux-next. https://patchwork.kernel.org/project/linux-wireless/cover/20220407095858.46807-1-pks...@realtek.com/ ece31c93d4d6 rtw88: 8821c: fix debugfs rssi value f5207c122102 rtw88: do PHY calibration while starting AP f1c4dabfe68d rtw88: 8821c: Enable TX report for management frames f2217968ffda rtw88: Add update beacon flow for AP mode 6723c0cde84f rtw88: fix incorrect frequency reported c1edc86472fc rtw88: add ieee80211:sta_rc_update ops Realtek provides us another series of patches for 5.14, and it contains 5 commits, we'd verified this series of patches. [Test] Verified on the Realtek 8821CE card. [Where problems could occur] The patches are introducing new interfaces, I think it only has minimal impact to the origin behaviors. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1969326/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1970392] Re: 22.04 USB devices do not work after sleep on Dell XPS 13 9370
According to the log, that's the Thunderbolt port not working, right? -- 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/1970392 Title: 22.04 USB devices do not work after sleep on Dell XPS 13 9370 Status in linux package in Ubuntu: Confirmed Bug description: I have a Dell XPS 13 9370 that came with Ubuntu preinstalled. I have just completed a fresh install of 22.04 on it. When I suspend the laptop, the USB devices that were plugged in when I suspended do not work. Specifically, I had an Ethernet adapter and a USB-C monitor with a keyboard attached through it. The monitor display works as expected, but neither the keyboard nor the Ethernet adapter work after suspending. Interestingly, I can move the Ethernet adapter to the remaining USB-C port and it works correctly. Moving it back afterwards, it still does not work. Please let me know if there is anything more I can do to help. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-25-generic 5.15.0-25.25 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: aaron-work 35648 F pulseaudio /dev/snd/controlC0: aaron-work 35648 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 26 10:36:09 2022 InstallationDate: Installed on 2022-04-24 (1 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Dell Inc. XPS 13 9370 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-25-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-25-generic N/A linux-backports-modules-5.15.0-25-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/11/2019 dmi.bios.release: 1.12 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.1 dmi.board.name: 0F6P3V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.1:bd12/11/2019:br1.12:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct10:cvr:sku07E6: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.product.sku: 07E6 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970392/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1971576] Re: SATA device hot plug regression on AMD EPYC (Asus) server
** Summary changed: - SATA device hot plug regression on AMD EYPC (Asus) server + SATA device hot plug regression on AMD EPYC (Asus) server -- 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/1971576 Title: SATA device hot plug regression on AMD EPYC (Asus) server Status in linux package in Ubuntu: Confirmed Bug description: SATA disk hot plug can't work on Ubuntu 20.04 ga-kernel of "Linux version 5.4.0-109-generic", but it works on earlier version of " Linux version 5.4.0-42-generic" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971576/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1960213] Re: Kernel Panic on linux-image-5.15.0-18-generic
Does kernel parameter "intel_iommu=off" help?
--
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/1960213
Title:
Kernel Panic on linux-image-5.15.0-18-generic
Status in linux package in Ubuntu:
Confirmed
Bug description:
Hello. Get a Kernel Panic on linux-image-5.15.0-18-generic
The same as https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1957012
On 5.13.0-29-generic boot successfully.
Laptop: Lenovo
Model: 20RA002SRT
Stack trace in attached images.
---
ProblemType: Bug
AlsaVersion: Advanced Linux Sound Architecture Driver Version
k5.13.0-29-generic.
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: PCH [HDA Intel PCH], device 0: CX8070 Analog [CX8070 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: grid 2375 F pulseaudio
Card0.Amixer.info:
Card hw:0 'PCH'/'HDA Intel PCH at 0xb131c000 irq 149'
Mixer name : 'Conexant CX8070'
Components : 'HDA:14f11f86,17aa5079,00100100
HDA:8086280b,80860101,0010'
Controls : 55
Simple ctrls : 14
CasperMD5CheckResult: skip
CurrentDesktop: X-Cinnamon
DistroRelease: Ubuntu 20.04
MachineType: LENOVO 20RA002SRT
Package: linux (not installed)
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-29-generic
root=/dev/mapper/vg_core-sys ro ipv6.disable=1 quiet splash iommu=soft
resume=/dev/vg_core/sys resume_offset=34816 crashkernel=512M-:192M vt.handoff=7
ProcVersionSignature: Ubuntu 5.13.0-29.32~20.04.1-generic 5.13.19
RelatedPackageVersions:
linux-restricted-modules-5.13.0-29-generic N/A
linux-backports-modules-5.13.0-29-generic N/A
linux-firmware 1.187.26
Tags: focal
Uname: Linux 5.13.0-29-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: dialout docker plugdev tty uucp vboxusers wireshark
WifiSyslog:
_MarkForUpload: True
dmi.bios.date: 09/15/2021
dmi.bios.release: 1.19
dmi.bios.vendor: LENOVO
dmi.bios.version: R16ET33W (1.19 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20RA002SRT
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.13
dmi.modalias:
dmi:bvnLENOVO:bvrR16ET33W(1.19):bd09/15/2021:br1.19:efr1.13:svnLENOVO:pn20RA002SRT:pvrThinkPadE14:rvnLENOVO:rn20RA002SRT:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20RA_BU_SMB_FM_ThinkPadE14:
dmi.product.family: ThinkPad E14
dmi.product.name: 20RA002SRT
dmi.product.sku: LENOVO_MT_20RA_BU_SMB_FM_ThinkPad E14
dmi.product.version: ThinkPad E14
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1960213/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1972134] 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 1972134 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/1972134 Title: AMD APU s2idle is broken after the ASIC reset fix Status in linux package in Ubuntu: Incomplete Bug description: [Impact] AMD reported fix for LP: #1968475 breaks AMD APU s2idle [Fix] TBD [Test] TBD [Where problems could occur] TBD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1972134/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1971146] Re: [radeon] Pictures including wallpaper not showing in kernel 5.14.21 and later (but 5.14.20 and earlier works)
Please try using the original Ubuntu kernel again (5.15.0-27), verify the bug occurs, and then try comment #31. We need to verify what the exact fix was. -- 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/1971146 Title: [radeon] Pictures including wallpaper not showing in kernel 5.14.21 and later (but 5.14.20 and earlier works) Status in linux package in Ubuntu: Triaged Bug description: I can't see pictures in emails or on some pictures on websites. Sometimes it just shows the bottom 20mm of pictures. The wallpaper is just a blank white screen. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon May 2 13:12:31 2022 DistUpgraded: 2022-04-24 19:05:38,365 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: virtualbox/6.1.32, 5.15.0-25-generic, x86_64: installed virtualbox/6.1.32, 5.15.0-27-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Venus XT [Radeon HD 8870M / R9 M270X/M370X] [1002:6821] (rev 83) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. Radeon R9 M370X Mac Edition [106b:0149] InstallationDate: Installed on 2021-04-26 (371 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) Lsusb: Bus 002 Device 003: ID 05ac:8406 Apple, Inc. Internal Memory Card Reader Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 05ac:8290 Apple, Inc. Bluetooth Host Controller Bus 001 Device 003: ID 05ac:0274 Apple, Inc. Apple Internal Keyboard / Trackpad Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Apple Inc. MacBookPro11,5 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=2234e6d3-3ebc-44e6-b0a5-bef132fd1f72 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to jammy on 2022-04-24 (7 days ago) dmi.bios.date: 06/11/2020 dmi.bios.release: 0.1 dmi.bios.vendor: Apple Inc. dmi.bios.version: 199.0.0.0.0 dmi.board.name: Mac-06F11F11946D27C5 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro11,5 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-06F11F11946D27C5 dmi.modalias: dmi:bvnAppleInc.:bvr199.0.0.0.0:bd06/11/2020:br0.1:svnAppleInc.:pnMacBookPro11,5:pvr1.0:rvnAppleInc.:rnMac-06F11F11946D27C5:rvrMacBookPro11,5:cvnAppleInc.:ct9:cvrMac-06F11F11946D27C5:sku: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro11,5 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.1-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-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-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971146/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1968475] Re: Fix broken HDMI audio on AMD PRO VII after S3
Thanks, filed LP: #1972134 to track the regression. My fault that I didn't test this SRU on APU. What's the APU that can reproduce the issue? ** Tags removed: verification-failed-focal ** Tags added: verification-done-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/1968475 Title: Fix broken HDMI audio on AMD PRO VII after S3 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: Fix Committed Status in linux source package in Jammy: Fix Committed Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: [Impact] DP/HDMI audio on AMD PRO VII stops working after S3. [Fix] Ensure HDA function is suspended before ASIC reset so the subsequent resume can be carried out successfully. [Test] With the patch applied, DP/HDMI audio continues to work after S3. [Where problems could occur] The suspend_noirq phase should not trigger any interrupt, so if amdgpu_asic_reset() somehow raised IRQ, it can break the system. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1968475/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1972134] [NEW] AMD APU s2idle is broken after the ASIC reset fix
Public bug reported: [Impact] AMD reported fix for LP: #1968475 breaks AMD APU s2idle [Fix] TBD [Test] TBD [Where problems could occur] TBD ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1972134 Title: AMD APU s2idle is broken after the ASIC reset fix Status in linux package in Ubuntu: New Bug description: [Impact] AMD reported fix for LP: #1968475 breaks AMD APU s2idle [Fix] TBD [Test] TBD [Where problems could occur] TBD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1972134/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1950282] Re: Fibocom WWAN FM350-GL-00 (Mediatek M80 5G) support
And, here is dmesg log which is filtered with 'mtk_t7xx' -- 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/1950282 Title: Fibocom WWAN FM350-GL-00 (Mediatek M80 5G) support Status in HWE Next: New Status in OEM Priority Project: New Status in linux package in Ubuntu: Incomplete Bug description: :55:00.0 Wireless controller [0d40]: MEDIATEK Corp. Device [14c3:4d75] (rev 01) Subsystem: Hewlett-Packard Company Device [103c:8914] https://lore.kernel.org/linux-wireless/20211101035635.26999-1-ricardo.marti...@linux.intel.com/ --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip Dependencies: DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-edge-staging+X136 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-07-13 (119 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Intel Corporation Alder Lake Client Platform Package: linux-firmware 1.187.20+staging.31 PackageArchitecture: all ProcFB: 0 i915 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-9007-oem root=UUID=56278c18-b6d3-4b07-b758-32f574db7ae0 ro i915.force_probe=46c0 automatic-oem-config quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.14.0-9007.7+staging.29-oem 5.14.14 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.14.0-9007-oem N/A linux-backports-modules-5.14.0-9007-oem N/A linux-firmware 1.187.20+staging.31 Tags: focal Uname: Linux 5.14.0-9007-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 08/23/2021 dmi.bios.vendor: Intel Corporation dmi.bios.version: ADLPFWI1.R00.2347.A00.2108230957 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: AlderLake-M LP5 RVP dmi.board.vendor: Intel Corporation dmi.board.version: 1 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 0.1 dmi.ec.firmware.release: 1.43 dmi.modalias: dmi:bvnIntelCorporation:bvrADLPFWI1.R00.2347.A00.2108230957:bd08/23/2021:efr1.43:svnIntelCorporation:pnAlderLakeClientPlatform:pvr0.1:rvnIntelCorporation:rnAlderLake-MLP5RVP:rvr1:cvnIntelCorporation:ct9:cvr0.1:sku01010002: dmi.product.family: Alder Lake Client System dmi.product.name: Alder Lake Client Platform dmi.product.sku: 01010002 dmi.product.version: 0.1 dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1950282/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1950282] Re: Fibocom WWAN FM350-GL-00 (Mediatek M80 5G) support
** Attachment added: "dmesg.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950282/+attachment/5587776/+files/dmesg.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1950282 Title: Fibocom WWAN FM350-GL-00 (Mediatek M80 5G) support Status in HWE Next: New Status in OEM Priority Project: New Status in linux package in Ubuntu: Incomplete Bug description: :55:00.0 Wireless controller [0d40]: MEDIATEK Corp. Device [14c3:4d75] (rev 01) Subsystem: Hewlett-Packard Company Device [103c:8914] https://lore.kernel.org/linux-wireless/20211101035635.26999-1-ricardo.marti...@linux.intel.com/ --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip Dependencies: DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-edge-staging+X136 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-07-13 (119 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Intel Corporation Alder Lake Client Platform Package: linux-firmware 1.187.20+staging.31 PackageArchitecture: all ProcFB: 0 i915 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-9007-oem root=UUID=56278c18-b6d3-4b07-b758-32f574db7ae0 ro i915.force_probe=46c0 automatic-oem-config quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.14.0-9007.7+staging.29-oem 5.14.14 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.14.0-9007-oem N/A linux-backports-modules-5.14.0-9007-oem N/A linux-firmware 1.187.20+staging.31 Tags: focal Uname: Linux 5.14.0-9007-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 08/23/2021 dmi.bios.vendor: Intel Corporation dmi.bios.version: ADLPFWI1.R00.2347.A00.2108230957 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: AlderLake-M LP5 RVP dmi.board.vendor: Intel Corporation dmi.board.version: 1 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 0.1 dmi.ec.firmware.release: 1.43 dmi.modalias: dmi:bvnIntelCorporation:bvrADLPFWI1.R00.2347.A00.2108230957:bd08/23/2021:efr1.43:svnIntelCorporation:pnAlderLakeClientPlatform:pvr0.1:rvnIntelCorporation:rnAlderLake-MLP5RVP:rvr1:cvnIntelCorporation:ct9:cvr0.1:sku01010002: dmi.product.family: Alder Lake Client System dmi.product.name: Alder Lake Client Platform dmi.product.sku: 01010002 dmi.product.version: 0.1 dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1950282/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1950282] Re: Fibocom WWAN FM350-GL-00 (Mediatek M80 5G) support
Hello Muralidharan! First of all, thanks for the quick reply. After installing the link's kernel, manually reloading the mtk_t7xx kernel module confirmed that the modem device was found normally. However, there is still no connection through mmcli, so the requested firmware and related dmesg log are attached. Also, it would be appreciated if you could advise on where to get information about the firmware of the device or where to obtain the package file. thank you. ** Attachment added: "mmcli connect fail log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950282/+attachment/5587775/+files/mmcli-fail.log.png -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1950282 Title: Fibocom WWAN FM350-GL-00 (Mediatek M80 5G) support Status in HWE Next: New Status in OEM Priority Project: New Status in linux package in Ubuntu: Incomplete Bug description: :55:00.0 Wireless controller [0d40]: MEDIATEK Corp. Device [14c3:4d75] (rev 01) Subsystem: Hewlett-Packard Company Device [103c:8914] https://lore.kernel.org/linux-wireless/20211101035635.26999-1-ricardo.marti...@linux.intel.com/ --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip Dependencies: DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-edge-staging+X136 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-07-13 (119 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Intel Corporation Alder Lake Client Platform Package: linux-firmware 1.187.20+staging.31 PackageArchitecture: all ProcFB: 0 i915 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-9007-oem root=UUID=56278c18-b6d3-4b07-b758-32f574db7ae0 ro i915.force_probe=46c0 automatic-oem-config quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.14.0-9007.7+staging.29-oem 5.14.14 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.14.0-9007-oem N/A linux-backports-modules-5.14.0-9007-oem N/A linux-firmware 1.187.20+staging.31 Tags: focal Uname: Linux 5.14.0-9007-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 08/23/2021 dmi.bios.vendor: Intel Corporation dmi.bios.version: ADLPFWI1.R00.2347.A00.2108230957 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: AlderLake-M LP5 RVP dmi.board.vendor: Intel Corporation dmi.board.version: 1 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 0.1 dmi.ec.firmware.release: 1.43 dmi.modalias: dmi:bvnIntelCorporation:bvrADLPFWI1.R00.2347.A00.2108230957:bd08/23/2021:efr1.43:svnIntelCorporation:pnAlderLakeClientPlatform:pvr0.1:rvnIntelCorporation:rnAlderLake-MLP5RVP:rvr1:cvnIntelCorporation:ct9:cvr0.1:sku01010002: dmi.product.family: Alder Lake Client System dmi.product.name: Alder Lake Client Platform dmi.product.sku: 01010002 dmi.product.version: 0.1 dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1950282/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1958191] Re: [i915] Screen flickering in Ubuntu 22.04 (until i915.enable_dc=0 intel_idle.max_cstate=2 are added)
I'm not using wayland. I stated that I was on X11. I did sudo update-grub indeed! -- 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/1958191 Title: [i915] Screen flickering in Ubuntu 22.04 (until i915.enable_dc=0 intel_idle.max_cstate=2 are added) Status in linux package in Ubuntu: Triaged Bug description: Ubuntu 22.04 development branch on kernel 5.15.0-17-generic @ 18/1/2022 Booting into desktop gets heavy screen flickering and disforming (unusable) both booting on xorg and wayland on kernel 5.13 it did not occur so heavy (only little glitches once in a while see bug 1948778) adding the kernel paramater intel_idle.max_cstate=4 fixed this i had these same bugs on this machine before: https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1838644 https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1948778 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-17-generic 5.15.0-17.17 ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12 Uname: Linux 5.15.0-17-generic x86_64 ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lotuspsychje 1201 F pipewire-media- lotuspsychje 1207 F pulseaudio /dev/snd/seq:lotuspsychje 1193 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Jan 18 04:22:00 2022 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0025 Intel Corp. Wireless-AC 9260 Bluetooth Adapter Bus 001 Device 003: ID 04f2:b59e Chicony Electronics Co., Ltd Chicony USB2.0 Camera Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Notebook N7x0WU ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-17-generic root=UUID=a41247d1-3bc3-453e-849a-e07fdcca6201 ro quiet splash intel_idle.max_cstate=4 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-17-generic N/A linux-backports-modules-5.15.0-17-generic N/A linux-firmware 1.204 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/07/2019 dmi.bios.release: 7.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 7.13 dmi.board.asset.tag: Tag 12345 dmi.board.name: N7x0WU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.ec.firmware.release: 7.14 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr7.13:bd01/07/2019:br7.13:efr7.14:svnNotebook:pnN7x0WU:pvrNotApplicable:rvnNotebook:rnN7x0WU:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A:skuNotApplicable: dmi.product.family: Not Applicable dmi.product.name: N7x0WU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958191/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1971482] Re: Regression: nfs cannot access/list wildcard file unless its cached
Hi Jonathan. Done! That needs some Ubuntu groups/membership. ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1971482 Title: Regression: nfs cannot access/list wildcard file unless its cached Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: New Status in linux source package in Focal: Confirmed Status in linux source package in Impish: New Status in linux source package in Jammy: New Status in linux source package in Kinetic: Incomplete Bug description: Some of our build machines have recently started failing builds. It was noted that all the machines that fail the build are running the most recent kernel 5.4.0-109-generic #123~18.04.1-Ubuntu. The following command was created to minimally reproduce the issue: $ while true; do sudo /usr/local/scripts/drop_cache.sh; ls -la /shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq*.ipk | tee -a /tmp/ls.log 2>&1; sleep 1;done ls: cannot access '/shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq*.ipk': No such file or directory ls: cannot access '/shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq*.ipk': No such file or directory ls: cannot access '/shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq*.ipk': No such file or directory ls: cannot access '/shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq*.ipk': No such file or directory Note directly trying to list the file works every time, it seems the bug must be related to the use of the wildcard. $ while true; do sudo /usr/local/scripts/drop_cache.sh; ls -la /shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq_1.0.9323-r3_cortexa9hf-neon.ipk | tee -a /tmp/ls.log 2>&1; sleep 1;done -rw-r--r-- 1 jenkins engineer 202526 May 2 13:47 /shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq_1.0.9323-r3_cortexa9hf-neon.ipk -rw-r--r-- 1 jenkins engineer 202526 May 2 13:47 /shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq_1.0.9323-r3_cortexa9hf-neon.ipk -rw-r--r-- 1 jenkins engineer 202526 May 2 13:47 /shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq_1.0.9323-r3_cortexa9hf-neon.ipk The drop_cache was needed to force the error everytime, otherwise it would fail only a few times then succeed a bunch in a row before randomly failing again. $ cat /usr/local/scripts/drop_cache.sh #!/bin/bash # Test script to drop filesystem cache sync # Clear pagecache, dentries, and inodes echo 3 > /proc/sys/vm/drop_caches Downgrading the kernel to 5.4.0-107-generic on one of the machines caused the problem to go away. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.4.0-109-generic 5.4.0-109.123~18.04.1 ProcVersionSignature: Ubuntu 5.4.0-107.121~18.04.1-generic 5.4.174 Uname: Linux 5.4.0-107-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.27 Architecture: amd64 Date: Tue May 3 15:04:34 2022 ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= PATH=(custom, no user) SourcePackage: linux-signed-hwe-5.4 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971482/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1971482] Re: Regression: nfs cannot access/list wildcard file unless its cached
How do I add 18.04 Bionic to the affects list? -- 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/1971482 Title: Regression: nfs cannot access/list wildcard file unless its cached Status in linux package in Ubuntu: Incomplete Status in linux source package in Focal: Confirmed Status in linux source package in Impish: New Status in linux source package in Jammy: New Status in linux source package in Kinetic: Incomplete Bug description: Some of our build machines have recently started failing builds. It was noted that all the machines that fail the build are running the most recent kernel 5.4.0-109-generic #123~18.04.1-Ubuntu. The following command was created to minimally reproduce the issue: $ while true; do sudo /usr/local/scripts/drop_cache.sh; ls -la /shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq*.ipk | tee -a /tmp/ls.log 2>&1; sleep 1;done ls: cannot access '/shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq*.ipk': No such file or directory ls: cannot access '/shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq*.ipk': No such file or directory ls: cannot access '/shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq*.ipk': No such file or directory ls: cannot access '/shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq*.ipk': No such file or directory Note directly trying to list the file works every time, it seems the bug must be related to the use of the wildcard. $ while true; do sudo /usr/local/scripts/drop_cache.sh; ls -la /shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq_1.0.9323-r3_cortexa9hf-neon.ipk | tee -a /tmp/ls.log 2>&1; sleep 1;done -rw-r--r-- 1 jenkins engineer 202526 May 2 13:47 /shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq_1.0.9323-r3_cortexa9hf-neon.ipk -rw-r--r-- 1 jenkins engineer 202526 May 2 13:47 /shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq_1.0.9323-r3_cortexa9hf-neon.ipk -rw-r--r-- 1 jenkins engineer 202526 May 2 13:47 /shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq_1.0.9323-r3_cortexa9hf-neon.ipk The drop_cache was needed to force the error everytime, otherwise it would fail only a few times then succeed a bunch in a row before randomly failing again. $ cat /usr/local/scripts/drop_cache.sh #!/bin/bash # Test script to drop filesystem cache sync # Clear pagecache, dentries, and inodes echo 3 > /proc/sys/vm/drop_caches Downgrading the kernel to 5.4.0-107-generic on one of the machines caused the problem to go away. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.4.0-109-generic 5.4.0-109.123~18.04.1 ProcVersionSignature: Ubuntu 5.4.0-107.121~18.04.1-generic 5.4.174 Uname: Linux 5.4.0-107-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.27 Architecture: amd64 Date: Tue May 3 15:04:34 2022 ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= PATH=(custom, no user) SourcePackage: linux-signed-hwe-5.4 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971482/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1971482] Re: Regression: nfs cannot access/list wildcard file unless its cached
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=e0caaf75d443e02e55e146fd75fe2efc8aed5540
commit e0caaf75d443e02e55e146fd75fe2efc8aed5540
Author: Trond Myklebust
Date: Tue Feb 8 13:38:23 2022 -0500
NFS: LOOKUP_DIRECTORY is also ok with symlinks
Commit ac795161c936 (NFSv4: Handle case where the lookup of a directory
fails) [1], part of Linux since 5.17-rc2, introduced a regression, where
a symbolic link on an NFS mount to a directory on another NFS does not
resolve(?) the first time it is accessed:
Reported-by: Paul Menzel
Fixes: ac795161c936 ("NFSv4: Handle case where the lookup of a directory
fails")
Signed-off-by: Trond Myklebust
Tested-by: Donald Buczek
Signed-off-by: Anna Schumaker
~/git/linux$ git describe --contains e0caaf75d443
v5.17-rc5~13^2~1
** Also affects: linux (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: linux-signed-hwe-5.4 (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: linux-signed-hwe-5.13 (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Impish)
Importance: Undecided
Status: New
** Also affects: linux-signed-hwe-5.4 (Ubuntu Impish)
Importance: Undecided
Status: New
** Also affects: linux-signed-hwe-5.13 (Ubuntu Impish)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Kinetic)
Importance: Undecided
Status: Confirmed
** Also affects: linux-signed-hwe-5.4 (Ubuntu Kinetic)
Importance: Undecided
Status: New
** Also affects: linux-signed-hwe-5.13 (Ubuntu Kinetic)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: linux-signed-hwe-5.4 (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: linux-signed-hwe-5.13 (Ubuntu Focal)
Importance: Undecided
Status: New
** No longer affects: linux-signed-hwe-5.13 (Ubuntu)
** No longer affects: linux-signed-hwe-5.4 (Ubuntu)
** No longer affects: linux-signed-hwe-5.13 (Ubuntu Focal)
** No longer affects: linux-signed-hwe-5.13 (Ubuntu Impish)
** No longer affects: linux-signed-hwe-5.13 (Ubuntu Jammy)
** No longer affects: linux-signed-hwe-5.13 (Ubuntu Kinetic)
** No longer affects: linux-signed-hwe-5.4 (Ubuntu Focal)
** No longer affects: linux-signed-hwe-5.4 (Ubuntu Impish)
** No longer affects: linux-signed-hwe-5.4 (Ubuntu Jammy)
** No longer affects: linux-signed-hwe-5.4 (Ubuntu Kinetic)
** Changed in: linux (Ubuntu Kinetic)
Status: Confirmed => New
** Changed in: linux (Ubuntu Focal)
Status: New => Confirmed
--
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/1971482
Title:
Regression: nfs cannot access/list wildcard file unless its cached
Status in linux package in Ubuntu:
Incomplete
Status in linux source package in Focal:
Confirmed
Status in linux source package in Impish:
New
Status in linux source package in Jammy:
New
Status in linux source package in Kinetic:
Incomplete
Bug description:
Some of our build machines have recently started failing builds. It
was noted that all the machines that fail the build are running the
most recent kernel 5.4.0-109-generic #123~18.04.1-Ubuntu.
The following command was created to minimally reproduce the issue:
$ while true; do sudo /usr/local/scripts/drop_cache.sh; ls -la
/shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq*.ipk
| tee -a /tmp/ls.log 2>&1; sleep 1;done
ls: cannot access
'/shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq*.ipk':
No such file or directory
ls: cannot access
'/shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq*.ipk':
No such file or directory
ls: cannot access
'/shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq*.ipk':
No such file or directory
ls: cannot access
'/shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq*.ipk':
No such file or directory
Note directly trying to list the file works every time, it seems the bug must
be related to the use of the wildcard.
$ while true; do sudo /usr/local/scripts/drop_cache.sh; ls -la
/shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq_1.0.9323-r3_cortexa9hf-neon.ipk
| tee -a /tmp/ls.log 2>&1; sleep 1;done
-rw-r--r-- 1 jenkins engineer 202526 May 2 13:47
/shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq_1.0.9323-r3_cortexa9hf-neon.ipk
-rw-r--r-- 1 jenkins engineer 202526 May 2 13:47
/shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq_1.0.9323-r3_cortexa9hf-neon.ipk
-rw-r--r-- 1 jenkins engineer 202526 May 2 13:47
[Kernel-packages] [Bug 1971482] 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 1971482 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/1971482 Title: Regression: nfs cannot access/list wildcard file unless its cached Status in linux package in Ubuntu: Incomplete Status in linux source package in Focal: Confirmed Status in linux source package in Impish: New Status in linux source package in Jammy: New Status in linux source package in Kinetic: Incomplete Bug description: Some of our build machines have recently started failing builds. It was noted that all the machines that fail the build are running the most recent kernel 5.4.0-109-generic #123~18.04.1-Ubuntu. The following command was created to minimally reproduce the issue: $ while true; do sudo /usr/local/scripts/drop_cache.sh; ls -la /shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq*.ipk | tee -a /tmp/ls.log 2>&1; sleep 1;done ls: cannot access '/shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq*.ipk': No such file or directory ls: cannot access '/shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq*.ipk': No such file or directory ls: cannot access '/shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq*.ipk': No such file or directory ls: cannot access '/shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq*.ipk': No such file or directory Note directly trying to list the file works every time, it seems the bug must be related to the use of the wildcard. $ while true; do sudo /usr/local/scripts/drop_cache.sh; ls -la /shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq_1.0.9323-r3_cortexa9hf-neon.ipk | tee -a /tmp/ls.log 2>&1; sleep 1;done -rw-r--r-- 1 jenkins engineer 202526 May 2 13:47 /shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq_1.0.9323-r3_cortexa9hf-neon.ipk -rw-r--r-- 1 jenkins engineer 202526 May 2 13:47 /shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq_1.0.9323-r3_cortexa9hf-neon.ipk -rw-r--r-- 1 jenkins engineer 202526 May 2 13:47 /shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq_1.0.9323-r3_cortexa9hf-neon.ipk The drop_cache was needed to force the error everytime, otherwise it would fail only a few times then succeed a bunch in a row before randomly failing again. $ cat /usr/local/scripts/drop_cache.sh #!/bin/bash # Test script to drop filesystem cache sync # Clear pagecache, dentries, and inodes echo 3 > /proc/sys/vm/drop_caches Downgrading the kernel to 5.4.0-107-generic on one of the machines caused the problem to go away. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.4.0-109-generic 5.4.0-109.123~18.04.1 ProcVersionSignature: Ubuntu 5.4.0-107.121~18.04.1-generic 5.4.174 Uname: Linux 5.4.0-107-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.27 Architecture: amd64 Date: Tue May 3 15:04:34 2022 ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= PATH=(custom, no user) SourcePackage: linux-signed-hwe-5.4 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971482/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1971482] Re: Regression: nfs cannot access/list wildcard file unless its cached
Assiging to the linux source package, and marking as confirmed per comment #5. Thanks for the detailed report and test steps. ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** 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-signed-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1971482 Title: Regression: nfs cannot access/list wildcard file unless its cached Status in linux package in Ubuntu: Incomplete Status in linux source package in Focal: Confirmed Status in linux source package in Impish: New Status in linux source package in Jammy: New Status in linux source package in Kinetic: Incomplete Bug description: Some of our build machines have recently started failing builds. It was noted that all the machines that fail the build are running the most recent kernel 5.4.0-109-generic #123~18.04.1-Ubuntu. The following command was created to minimally reproduce the issue: $ while true; do sudo /usr/local/scripts/drop_cache.sh; ls -la /shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq*.ipk | tee -a /tmp/ls.log 2>&1; sleep 1;done ls: cannot access '/shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq*.ipk': No such file or directory ls: cannot access '/shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq*.ipk': No such file or directory ls: cannot access '/shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq*.ipk': No such file or directory ls: cannot access '/shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq*.ipk': No such file or directory Note directly trying to list the file works every time, it seems the bug must be related to the use of the wildcard. $ while true; do sudo /usr/local/scripts/drop_cache.sh; ls -la /shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq_1.0.9323-r3_cortexa9hf-neon.ipk | tee -a /tmp/ls.log 2>&1; sleep 1;done -rw-r--r-- 1 jenkins engineer 202526 May 2 13:47 /shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq_1.0.9323-r3_cortexa9hf-neon.ipk -rw-r--r-- 1 jenkins engineer 202526 May 2 13:47 /shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq_1.0.9323-r3_cortexa9hf-neon.ipk -rw-r--r-- 1 jenkins engineer 202526 May 2 13:47 /shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq_1.0.9323-r3_cortexa9hf-neon.ipk The drop_cache was needed to force the error everytime, otherwise it would fail only a few times then succeed a bunch in a row before randomly failing again. $ cat /usr/local/scripts/drop_cache.sh #!/bin/bash # Test script to drop filesystem cache sync # Clear pagecache, dentries, and inodes echo 3 > /proc/sys/vm/drop_caches Downgrading the kernel to 5.4.0-107-generic on one of the machines caused the problem to go away. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.4.0-109-generic 5.4.0-109.123~18.04.1 ProcVersionSignature: Ubuntu 5.4.0-107.121~18.04.1-generic 5.4.174 Uname: Linux 5.4.0-107-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.27 Architecture: amd64 Date: Tue May 3 15:04:34 2022 ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= PATH=(custom, no user) SourcePackage: linux-signed-hwe-5.4 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971482/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1971955] Re: systemd-udevd call unshare process when attaching nvme volume
Reassigning to package snapd per ownership of rules file. $ grep -r 'snap auto-import' /lib/udev/rules.d/ /lib/udev/rules.d/66-snapd-autoimport.rules:3:RUN+="/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/%k" $ dpkg -S /lib/udev/rules.d/66-snapd-autoimport.rules snapd: /lib/udev/rules.d/66-snapd-autoimport.rules ** 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/1971955 Title: systemd-udevd call unshare process when attaching nvme volume Status in linux package in Ubuntu: Invalid Status in snapd package in Ubuntu: New Bug description: env: PRETTY_NAME="Ubuntu 22.04 LTS" NAME="Ubuntu" VERSION_ID="22.04" VERSION="22.04 (Jammy Jellyfish)" VERSION_CODENAME=jammy # lsb_release -rd Description:Ubuntu 22.04 LTS Release:22.04 host connect dellemc powerstore with nvme-tcp connection # nvme list-subsys nvme-subsys0 - NQN=nqn.1988-11.com.dell:powerstore:00:d42d581e674f2B16F2E2 \ +- nvme1 tcp traddr=172.16.100.165 trsvcid=4420 live +- nvme2 tcp traddr=172.16.200.164 trsvcid=4420 live +- nvme3 tcp traddr=172.16.200.165 trsvcid=4420 live +- nvme4 tcp traddr=172.16.100.164 trsvcid=4420 live when attaching new volume to host. systemd-udevd trigger unshare process to run snap import command on new volumes and it fail. volume finally map to host. it doesn't affect volume usage. but some udev rule need to check for this strange behavior. May 06 08:16:43 e2e-l4-094051 systemd-udevd[33374]: nvme0n234: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme0n234' failed with exit code 1. May 06 08:16:43 e2e-l4-094051 systemd-udevd[33371]: nvme0n232: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme0n232' failed with exit code 1. May 06 08:16:43 e2e-l4-094051 systemd-udevd[33378]: nvme0n236: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme0n236' failed with exit code 1. May 06 08:16:43 e2e-l4-094051 systemd-udevd[33384]: nvme0n239: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme0n239' failed with exit code 1. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 6 08:14 seq crw-rw 1 root audio 116, 33 May 6 08:14 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-05-04 (2 days ago) InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220421) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 002: ID 8087:8002 Intel Corp. 8 channel internal hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub Bus 001 Device 002: ID 8087:800a Intel Corp. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/2p, 480M |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/8p, 480M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/2p, 480M |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/6p, 480M |__ Port 6: Dev 3, If 0, Class=Hub, Driver=hub/6p, 480M Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-27-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 RelatedPackageVersions: linux-restricted-modules-5.15.0-27-generic N/A linux-backports-modules-5.15.0-27-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: jammy uec-images Uname: Linux 5.15.0-27-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 05/14/2021 dmi.bios.release: 2.13 dmi.bios.version: 2.13.0 dmi.board.name: 072T6D dmi.board.version: A01 dmi.chassis.type: 23 dmi.modalias: dmi:bvn:bvr2.13.0:bd05/14/2021:br2.13:svn:pn:pvr:rvn:rn072T6D:rvrA01:cvn:ct23:cvr:skuSKU=NotProvided;ModelName=: dmi.product.sku: SKU=NotProvided;ModelName= To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971955/+subscriptions -- Mailing list:
[Kernel-packages] [Bug 1971955] Re: systemd-udevd call unshare process when attaching nvme volume
Hi Vincent, Thanks for the bug report. > when attaching new volume to host. systemd-udevd trigger > unshare process to run snap import command on new volumes and it fail. > volume finally map to host. it doesn't affect volume usage. > but some udev rule need to check for this strange behavior. Please correct me if I'm wrong, but it seems the issue is only a concern about the command failure status logged, and there's no functional issue; is that correct? ** Also affects: snapd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1971955 Title: systemd-udevd call unshare process when attaching nvme volume Status in linux package in Ubuntu: Invalid Status in snapd package in Ubuntu: New Bug description: env: PRETTY_NAME="Ubuntu 22.04 LTS" NAME="Ubuntu" VERSION_ID="22.04" VERSION="22.04 (Jammy Jellyfish)" VERSION_CODENAME=jammy # lsb_release -rd Description:Ubuntu 22.04 LTS Release:22.04 host connect dellemc powerstore with nvme-tcp connection # nvme list-subsys nvme-subsys0 - NQN=nqn.1988-11.com.dell:powerstore:00:d42d581e674f2B16F2E2 \ +- nvme1 tcp traddr=172.16.100.165 trsvcid=4420 live +- nvme2 tcp traddr=172.16.200.164 trsvcid=4420 live +- nvme3 tcp traddr=172.16.200.165 trsvcid=4420 live +- nvme4 tcp traddr=172.16.100.164 trsvcid=4420 live when attaching new volume to host. systemd-udevd trigger unshare process to run snap import command on new volumes and it fail. volume finally map to host. it doesn't affect volume usage. but some udev rule need to check for this strange behavior. May 06 08:16:43 e2e-l4-094051 systemd-udevd[33374]: nvme0n234: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme0n234' failed with exit code 1. May 06 08:16:43 e2e-l4-094051 systemd-udevd[33371]: nvme0n232: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme0n232' failed with exit code 1. May 06 08:16:43 e2e-l4-094051 systemd-udevd[33378]: nvme0n236: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme0n236' failed with exit code 1. May 06 08:16:43 e2e-l4-094051 systemd-udevd[33384]: nvme0n239: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme0n239' failed with exit code 1. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 6 08:14 seq crw-rw 1 root audio 116, 33 May 6 08:14 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-05-04 (2 days ago) InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220421) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 002: ID 8087:8002 Intel Corp. 8 channel internal hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub Bus 001 Device 002: ID 8087:800a Intel Corp. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/2p, 480M |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/8p, 480M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/2p, 480M |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/6p, 480M |__ Port 6: Dev 3, If 0, Class=Hub, Driver=hub/6p, 480M Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-27-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 RelatedPackageVersions: linux-restricted-modules-5.15.0-27-generic N/A linux-backports-modules-5.15.0-27-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: jammy uec-images Uname: Linux 5.15.0-27-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 05/14/2021 dmi.bios.release: 2.13 dmi.bios.version: 2.13.0 dmi.board.name: 072T6D dmi.board.version: A01 dmi.chassis.type: 23 dmi.modalias: dmi:bvn:bvr2.13.0:bd05/14/2021:br2.13:svn:pn:pvr:rvn:rn072T6D:rvrA01:cvn:ct23:cvr:skuSKU=NotProvided;ModelName=: dmi.product.sku: SKU=NotProvided;ModelName= To manage
[Kernel-packages] [Bug 1939347] Re: Ubuntu 20.04 freeze since kernel 5.11
Perhaps you need both intel_idle.max_cstate=1 and i915.enable_dc=0 parameters? According to the above link, some chips might need both. Also, are you able to try a more recent Ubuntu version? -- 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/1939347 Title: Ubuntu 20.04 freeze since kernel 5.11 Status in linux package in Ubuntu: Confirmed Bug description: Since the last kernel update 5.11.0-25-generic, the system freezes in a few seconds or minutes, sometimes even on the login screen. The machine is a recent dell latitude 7490. The graphics card is Intel Corporation UHD Graphics 620 (rev 07). No multiboot. No problem with the previous kernel 5.8.0-63. I had the same problem with fedora a few months ago, which forced me to switch to ubuntu without any problems so far. Thanks for your help. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: plawrence 1996 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-06-21 (414 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 1bcf:2b96 Sunplus Innovation Technology Inc. Integrated_Webcam_HD Bus 001 Device 004: ID 0a5c:5834 Broadcom Corp. 5880 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Latitude 7490 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic root=UUID=01fd281b-07d7-45f2-846b-d5b79ed5d431 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-25-generic N/A linux-backports-modules-5.11.0-25-generic N/A linux-firmware 1.187.15 Tags: focal Uname: Linux 5.11.0-25-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: 02/23/2021 dmi.bios.release: 1.19 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.19.0 dmi.board.name: 0KP0FT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.19.0:bd02/23/2021:br1.19:svnDellInc.:pnLatitude7490:pvr:rvnDellInc.:rn0KP0FT:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 7490 dmi.product.sku: 081C dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1939347/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1971985] Re: Kernel 5.17.5-76051705 not supported
I've found a fix: Run the usual install sudo apt install bcmwl-kernel-source 2. When it stops with the error, edit the file sudo gedit /var/lib/dkms/bcmwl/6.30.223.271+bdcom/source/src/wl/sys/wl_linux.c find PDE_DATA( and replace it with pde_data( . There should be 2 replaces total. Save the file. 3. Continue the installation with sudo apt-get -f install 4. Enjoy =D Not me! https://www.reddit.com/r/pop_os/comments/uk2idd/comment/i7o58c0/?utm_source=share_medium=web2x=3 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1971985 Title: Kernel 5.17.5-76051705 not supported Status in bcmwl package in Ubuntu: Confirmed Bug description: Yesterday, after a system update for kernel 5.17.5-76051705, in Pop 22.04, the wifi did not work more. After to try uninstall e reinstall the bcmwl-kernel-package trough Pop Shop (it closes when the process is running) and terminal, it shows some of the following messages in lines: Building initial module for 5.17.5-76051705-generic ERROR (dkms apport): kernel package linux-headers-5.17.5-76051705-generic is not supported Error! Bad return status for module build on kernel: 5.17.5-76051705-generic (x86_64) I am not sure if here is the right place to communicate this kind of problem or if it is a bug. But I think in soon others will have the same problem. Description: Pop!_OS 22.04 LTS Release: 22.04 bcmwl-kernel-source: Instalado: 6.30.223.271+bdcom-0ubuntu8 Candidato: 6.30.223.271+bdcom-0ubuntu8 Tabela de versão: *** 6.30.223.271+bdcom-0ubuntu8 500 500 http://us.archive.ubuntu.com/ubuntu jammy/restricted amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1971985/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1958191] Re: [i915] Screen flickering in Ubuntu 22.04 (until i915.enable_dc=0 intel_idle.max_cstate=2 are added)
@ Diogo #16 did you also sudo update-grub after the kernel paramater? and doublechecked if you are using your intel card and not your nvidia on wayland? -- 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/1958191 Title: [i915] Screen flickering in Ubuntu 22.04 (until i915.enable_dc=0 intel_idle.max_cstate=2 are added) Status in linux package in Ubuntu: Triaged Bug description: Ubuntu 22.04 development branch on kernel 5.15.0-17-generic @ 18/1/2022 Booting into desktop gets heavy screen flickering and disforming (unusable) both booting on xorg and wayland on kernel 5.13 it did not occur so heavy (only little glitches once in a while see bug 1948778) adding the kernel paramater intel_idle.max_cstate=4 fixed this i had these same bugs on this machine before: https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1838644 https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1948778 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-17-generic 5.15.0-17.17 ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12 Uname: Linux 5.15.0-17-generic x86_64 ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lotuspsychje 1201 F pipewire-media- lotuspsychje 1207 F pulseaudio /dev/snd/seq:lotuspsychje 1193 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Jan 18 04:22:00 2022 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0025 Intel Corp. Wireless-AC 9260 Bluetooth Adapter Bus 001 Device 003: ID 04f2:b59e Chicony Electronics Co., Ltd Chicony USB2.0 Camera Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Notebook N7x0WU ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-17-generic root=UUID=a41247d1-3bc3-453e-849a-e07fdcca6201 ro quiet splash intel_idle.max_cstate=4 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-17-generic N/A linux-backports-modules-5.15.0-17-generic N/A linux-firmware 1.204 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/07/2019 dmi.bios.release: 7.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 7.13 dmi.board.asset.tag: Tag 12345 dmi.board.name: N7x0WU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.ec.firmware.release: 7.14 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr7.13:bd01/07/2019:br7.13:efr7.14:svnNotebook:pnN7x0WU:pvrNotApplicable:rvnNotebook:rnN7x0WU:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A:skuNotApplicable: dmi.product.family: Not Applicable dmi.product.name: N7x0WU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958191/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1958191] Re: [i915] Screen flickering in Ubuntu 22.04 (until i915.enable_dc=0 intel_idle.max_cstate=2 are added)
I'm having the same issue, I'd like to add that I've tested both Xubuntu 22.04 and Ubuntu 22.04 and was able to reproduce the same error. Now I'm running Kubuntu 22.04 with the following spec: OS: Kubuntu 22.04 LTS x86_64 Kernel: 5.15.0-27-generic Shell: bash 5.1.16 Resolution: 1920x1080 @ 120Hz DE: KDE Plasma 5.24.5 KDE Frameworks Version: 5.93.0 WN: Kwin 5.24.5 Qt Version: 5.15.3 Graphics Platform: X11 Host: GL62 6QF REV:1.0 CPU: Intel i5-6300HQ (4) @ 3.200GHz GPU: Mesa Intel® HD Graphics 530 GPU: NVIDIA GeForce GTX 960M Here's another video of the issue: https://streamable.com/b9792p PS: I added GRUB_CMDLINE_LINUX_DEFAULT="quiet splash i915.enable_dc=0 intel_idle.max_cstate=2" to /etc/default/grub and I still have some instances of screen shaking. -- 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/1958191 Title: [i915] Screen flickering in Ubuntu 22.04 (until i915.enable_dc=0 intel_idle.max_cstate=2 are added) Status in linux package in Ubuntu: Triaged Bug description: Ubuntu 22.04 development branch on kernel 5.15.0-17-generic @ 18/1/2022 Booting into desktop gets heavy screen flickering and disforming (unusable) both booting on xorg and wayland on kernel 5.13 it did not occur so heavy (only little glitches once in a while see bug 1948778) adding the kernel paramater intel_idle.max_cstate=4 fixed this i had these same bugs on this machine before: https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1838644 https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1948778 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-17-generic 5.15.0-17.17 ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12 Uname: Linux 5.15.0-17-generic x86_64 ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lotuspsychje 1201 F pipewire-media- lotuspsychje 1207 F pulseaudio /dev/snd/seq:lotuspsychje 1193 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Jan 18 04:22:00 2022 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0025 Intel Corp. Wireless-AC 9260 Bluetooth Adapter Bus 001 Device 003: ID 04f2:b59e Chicony Electronics Co., Ltd Chicony USB2.0 Camera Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Notebook N7x0WU ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-17-generic root=UUID=a41247d1-3bc3-453e-849a-e07fdcca6201 ro quiet splash intel_idle.max_cstate=4 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-17-generic N/A linux-backports-modules-5.15.0-17-generic N/A linux-firmware 1.204 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/07/2019 dmi.bios.release: 7.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 7.13 dmi.board.asset.tag: Tag 12345 dmi.board.name: N7x0WU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.ec.firmware.release: 7.14 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr7.13:bd01/07/2019:br7.13:efr7.14:svnNotebook:pnN7x0WU:pvrNotApplicable:rvnNotebook:rnN7x0WU:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A:skuNotApplicable: dmi.product.family: Not Applicable dmi.product.name: N7x0WU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958191/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1971985] Re: Kernel 5.17.5-76051705 not supported
Same issue on Pop 22.04 on Acer Aspire 5750g WiFi: Broadcom BCM43227 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1971985 Title: Kernel 5.17.5-76051705 not supported Status in bcmwl package in Ubuntu: Confirmed Bug description: Yesterday, after a system update for kernel 5.17.5-76051705, in Pop 22.04, the wifi did not work more. After to try uninstall e reinstall the bcmwl-kernel-package trough Pop Shop (it closes when the process is running) and terminal, it shows some of the following messages in lines: Building initial module for 5.17.5-76051705-generic ERROR (dkms apport): kernel package linux-headers-5.17.5-76051705-generic is not supported Error! Bad return status for module build on kernel: 5.17.5-76051705-generic (x86_64) I am not sure if here is the right place to communicate this kind of problem or if it is a bug. But I think in soon others will have the same problem. Description: Pop!_OS 22.04 LTS Release: 22.04 bcmwl-kernel-source: Instalado: 6.30.223.271+bdcom-0ubuntu8 Candidato: 6.30.223.271+bdcom-0ubuntu8 Tabela de versão: *** 6.30.223.271+bdcom-0ubuntu8 500 500 http://us.archive.ubuntu.com/ubuntu jammy/restricted amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1971985/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1968475] Re: Fix broken HDMI audio on AMD PRO VII after S3
This caused a regression in s2idle on APUs. I think you forgot to pick up e53d9665ab003df0ece8f869fcd3c2bbbecf7190 which was in the original series too. ** Tags removed: verification-done-focal ** Tags added: verification-failed-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/1968475 Title: Fix broken HDMI audio on AMD PRO VII after S3 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: Fix Committed Status in linux source package in Jammy: Fix Committed Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: [Impact] DP/HDMI audio on AMD PRO VII stops working after S3. [Fix] Ensure HDA function is suspended before ASIC reset so the subsequent resume can be carried out successfully. [Test] With the patch applied, DP/HDMI audio continues to work after S3. [Where problems could occur] The suspend_noirq phase should not trigger any interrupt, so if amdgpu_asic_reset() somehow raised IRQ, it can break the system. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1968475/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1946303] Re: No video after wake from S3 due to Nvidia driver crash
I confirm that the workaround suggested above works on x11, GeForce GTX 1050 Mobile, driver NVIDIA 510 systemctl disable nvidia-hibernate.service nvidia-resume.service nvidia- suspend.service -- 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/1946303 Title: No video after wake from S3 due to Nvidia driver crash Status in nvidia-graphics-drivers-470 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-510 package in Ubuntu: Confirmed Bug description: Since upgrading to Ubuntu 21.10, my computer sometimes fails to properly wake from suspend. It does start running again, but there is no video output. I'm attaching text for two crashes from kernel log output. First is: /var/lib/dkms/nvidia/470.63.01/build/nvidia/nv.c:3967 nv_restore_user_channels+0xce/0xe0 [nvidia] Second is: /var/lib/dkms/nvidia/470.63.01/build/nvidia/nv.c:4162 nv_set_system_power_state+0x2c8/0x3d0 [nvidia] Apparently I'm not the only one having this problem with 470 drivers. https://forums.linuxmint.com/viewtopic.php?t=354445 https://forums.developer.nvidia.com/t/fixed-suspend-resume-issues-with-the-driver-version-470/187150 Driver 470 uses the new suspend mechanism via /usr/lib/systemd/system- sleep/nvidia. But I was using that mechanism with driver 460 in Ubuntu 21.04 and sleep was reliable then. Right now I'm going back to driver 460. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: nvidia-driver-470 470.63.01-0ubuntu4 ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Oct 6 23:24:02 2021 SourcePackage: nvidia-graphics-drivers-470 UpgradeStatus: Upgraded to impish on 2021-10-02 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1946303/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1972085] 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/1972085 Title: cannot wake from suspend must force shutdown and reboot Status in linux package in Ubuntu: Confirmed Bug description: I upgraded my laptop from ubuntu 20.04 to 22.04 ever since. My laptop will not wake up from suspend. I tried booting lubuntu 20.04 and xubunt 22.04 and still have the problem. ubuntu 20.04 will not boot from a usb. I want to reset my bios back to default but am scared to brick my laptop as i cannot afford another one. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.10 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sat May 7 23:55:10 2022 InstallationDate: Installed on 2021-11-15 (173 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: Upgraded to jammy on 2022-04-22 (15 days ago) VarLogDistupgradeXorgFixuplog: INFO:root:/usr/bin/do-release-upgrade running INFO:root:No xorg.conf, exiting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1972085/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1972085] Re: cannot wake from suspend must force shutdown and reboot
Thank you for taking the time to report this bug and helping to make Ubuntu better. The suspend function is not performed in the do-release-upgrade step you have filed this bug against (which was also run/completed 15 days ago). Your issue is likely related to the newer 5.15 kernel (20.04.4 using HWE used 5.13 kernel; thus I've changed package bug is filed against. Bug reporting is mostly about finding & fixing problems thus preventing future users from hitting the same bug. I suspect a Support site would be more appropriate, eg. https://answers.launchpad.net/ubuntu. You can also find help with your problem in the support forum of your local Ubuntu community http://loco.ubuntu.com/ or asking at https://askubuntu.com or https://ubuntuforums.org, or for more support options please look at https://discourse.ubuntu.com/t/community-support/709 ** Package changed: ubuntu-release-upgrader (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/1972085 Title: cannot wake from suspend must force shutdown and reboot Status in linux package in Ubuntu: New Bug description: I upgraded my laptop from ubuntu 20.04 to 22.04 ever since. My laptop will not wake up from suspend. I tried booting lubuntu 20.04 and xubunt 22.04 and still have the problem. ubuntu 20.04 will not boot from a usb. I want to reset my bios back to default but am scared to brick my laptop as i cannot afford another one. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.10 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sat May 7 23:55:10 2022 InstallationDate: Installed on 2021-11-15 (173 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: Upgraded to jammy on 2022-04-22 (15 days ago) VarLogDistupgradeXorgFixuplog: INFO:root:/usr/bin/do-release-upgrade running INFO:root:No xorg.conf, exiting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1972085/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1972085] [NEW] cannot wake from suspend must force shutdown and reboot
You have been subscribed to a public bug: I upgraded my laptop from ubuntu 20.04 to 22.04 ever since. My laptop will not wake up from suspend. I tried booting lubuntu 20.04 and xubunt 22.04 and still have the problem. ubuntu 20.04 will not boot from a usb. I want to reset my bios back to default but am scared to brick my laptop as i cannot afford another one. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.10 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sat May 7 23:55:10 2022 InstallationDate: Installed on 2021-11-15 (173 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: Upgraded to jammy on 2022-04-22 (15 days ago) VarLogDistupgradeXorgFixuplog: INFO:root:/usr/bin/do-release-upgrade running INFO:root:No xorg.conf, exiting ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug dist-upgrade jammy wayland-session -- cannot wake from suspend must force shutdown and reboot https://bugs.launchpad.net/bugs/1972085 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 1912673] Re: sounds not working on Dell XPS 17 (9700)
Headphone sounds have stopped working after upgrade from 21.10 to 22.04 LTS. Sound bar is movement is seen in sound settings under output device: Headphones - Comet Lake PCH cAVS - but no sound output from headphones. There is sounds via screen speakers when speakers - Comet Lake PCH cAVS is chosen. -- 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/1912673 Title: sounds not working on Dell XPS 17 (9700) Status in linux package in Ubuntu: Fix Released Status in linux package in Debian: Fix Released Bug description: My investigation process: Dell XPS 17 (9700) comes with Windows 10 preinstalled, where sounds worked. I installed Ubuntu 20.04 LTS fresh, sounds did not work on speakers or 3.5mm headphones, using linux-image-5.4.0-42-generic, I did not try blutooth. I sudo apt upgrade, dist-upgrade to get kernels linux-image-5.8.0-38-generic linux-image-5.8.0-40-generic Sounds did not work. I download linux-image-unsigned-5.10.9-051009-generic. Sounds did not work. I upgrade Dell XPS 9700 firmware from 1.3 to 1.63. Sounds did not work. After googling I found this solution in the comments: https://askubuntu.com/questions/1270442/no-sound-on-xps-17-9700 """ Download and install dkms module: https://launchpad.net/~canonical-hwe-team/+archive/ubuntu/pc-oem- dkms/+packages Alternatively, you can install linux-oem-20.04, it will install the 5.6 kernel with the above driver. Your system may be more stable with 5.4 kernel since it is in wide use. Manually install sof-firmware from Arch Linux: https://archlinux.pkgs.org/rolling/archlinux-extra-x86_64/sof- firmware-1.5.1-1-any.pkg.tar.zst.html You will need to delete the existing "sof" and "sof-tplg" files from the Ubuntu linux-firmware package first. Note if this package gets updated from Canoncial and they don't update these, you will have to delete and then reextract. Files go into the /usr/lib/firmware/intel/sof and /usr/lib/firmware/intel/sof-tplg folders. Manually install the ucm2 files: http://xps17.ddns.net/sof-soundwire.zip These go into /usr/share/alsa/ucm2/sof-soundwire. Delete the contents of the existing sof-soundwire folder (if you have it) and replace them with the ones from the archive. Reboot. You should now have all your audio devices available. If speakers do not play, you may need to run alsamixer (non-root) from a terminal and unmute and set the mixer levels all the way up. """ This solution worked for me on linux-image-5.6.0-1042-oem AFTER manually opening alsa-mixer and changing soundcard to sof. The sound would otherwise just show 'dummy'. My sounds still do not work on 5.8 or 5.10, full name listed above. I did not get to test this temporary fix with 5.4. my full alsa-info: http://alsa-project.org/db/?f=6a638be0cfbe8ed08a010eb26a7702e324dce5ff based on some google research, this seems to be a common problem: https://www.reddit.com/r/Dell/comments/hj8oxw/xps_17_9700_no_audio_on_linux_also_hardware_is/ https://www.reddit.com/r/Dell/comments/hge2yo/no_audio_on_linux_ubuntu_2004_xps_17_9700_realtek/ https://www.reddit.com/r/Dell/comments/j2kdjw/xps_17_9700_on_linux_audio_issue/ etc... ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.10 ProcVersionSignature: Ubuntu 5.6.0-1042.46-oem 5.6.19 Uname: Linux 5.6.0-1042-oem x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: neoh 1786 F pulseaudio /dev/snd/pcmC1D0p: neoh 1786 F...m pulseaudio /dev/snd/controlC0: neoh 1786 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jan 21 12:08:45 2021 InstallationDate: Installed on 2021-01-20 (1 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/30/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.3 dmi.board.name: 0CXCCY dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.3:bd12/30/2020:svnDellInc.:pnXPS179700:pvr:rvnDellInc.:rn0CXCCY:rvrA03:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 17 9700 dmi.product.sku: 098F dmi.sys.vendor: Dell Inc. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Dependencies: DistroRelease:
[Kernel-packages] [Bug 1971985] Re: Kernel 5.17.5-76051705 not supported
Same issue on Pop 22.04 on macbook pro 2012 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1971985 Title: Kernel 5.17.5-76051705 not supported Status in bcmwl package in Ubuntu: Confirmed Bug description: Yesterday, after a system update for kernel 5.17.5-76051705, in Pop 22.04, the wifi did not work more. After to try uninstall e reinstall the bcmwl-kernel-package trough Pop Shop (it closes when the process is running) and terminal, it shows some of the following messages in lines: Building initial module for 5.17.5-76051705-generic ERROR (dkms apport): kernel package linux-headers-5.17.5-76051705-generic is not supported Error! Bad return status for module build on kernel: 5.17.5-76051705-generic (x86_64) I am not sure if here is the right place to communicate this kind of problem or if it is a bug. But I think in soon others will have the same problem. Description: Pop!_OS 22.04 LTS Release: 22.04 bcmwl-kernel-source: Instalado: 6.30.223.271+bdcom-0ubuntu8 Candidato: 6.30.223.271+bdcom-0ubuntu8 Tabela de versão: *** 6.30.223.271+bdcom-0ubuntu8 500 500 http://us.archive.ubuntu.com/ubuntu jammy/restricted amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1971985/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1939347] Re: Ubuntu 20.04 freeze since kernel 5.11
I tried GRUB_CMDLINE_LINUX_DEFAULT="i915.enable_dc=0" it still freezes after one hour use. -- 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/1939347 Title: Ubuntu 20.04 freeze since kernel 5.11 Status in linux package in Ubuntu: Confirmed Bug description: Since the last kernel update 5.11.0-25-generic, the system freezes in a few seconds or minutes, sometimes even on the login screen. The machine is a recent dell latitude 7490. The graphics card is Intel Corporation UHD Graphics 620 (rev 07). No multiboot. No problem with the previous kernel 5.8.0-63. I had the same problem with fedora a few months ago, which forced me to switch to ubuntu without any problems so far. Thanks for your help. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: plawrence 1996 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-06-21 (414 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 1bcf:2b96 Sunplus Innovation Technology Inc. Integrated_Webcam_HD Bus 001 Device 004: ID 0a5c:5834 Broadcom Corp. 5880 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Latitude 7490 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic root=UUID=01fd281b-07d7-45f2-846b-d5b79ed5d431 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-25-generic N/A linux-backports-modules-5.11.0-25-generic N/A linux-firmware 1.187.15 Tags: focal Uname: Linux 5.11.0-25-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: 02/23/2021 dmi.bios.release: 1.19 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.19.0 dmi.board.name: 0KP0FT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.19.0:bd02/23/2021:br1.19:svnDellInc.:pnLatitude7490:pvr:rvnDellInc.:rn0KP0FT:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 7490 dmi.product.sku: 081C dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1939347/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1971437] Re: linux-image-5.15.0-27-generic causes Thinkpad T460p to not resume after suspend
The Lenovo Thinkpad T460p has 3 ways to resume the laptop after suspend : the screen lid button (when we open up the screen), the power button and the Fn key on the keyboard. All of them work with kernels up to 5.14 on Ubuntu, and none of them work with kernels starting from 5.15 and upwards. -- 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/1971437 Title: linux-image-5.15.0-27-generic causes Thinkpad T460p to not resume after suspend Status in linux package in Ubuntu: Confirmed Bug description: After upgrading from Ubuntu 21.10 to Ubuntu 22.04, my Lenovo Thinkpad T460p doesn't wake-up after suspend. The kernel installed was linux- image-5.15.0-27-generic. I downgraded to Linux kernel 5.13.15 and it works fine now. With Ubuntu 21.10, I had linux-image-5.13.15-40-generic kernel and it worked fine, but I've uninstalled it after the upgrade to 22.04. I also tested newer versions like 5.16.x and 5.17.x with the mainline program and they cause the same issue. The issue is that no key nor the power button nor the screen lid wake the laptop with kernel versions superior to Linux 5.13 (5.13.15 I think). It's either a Linux kernel problem, or a compile options mistake. $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 22.04 LTS Release:22.04 Codename: jammy --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jack 1283 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: LXQt DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-04-06 (27 days ago) InstallationMedia: Lubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: LENOVO 20FXS09D00 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=11961357-77ee-4aa4-82c2-359cbb8ef64b ro quiet cryptdevice=UUID=08f4ae12-6133-4c63-b78d-d855746c5f26:luks-08f4ae12-6133-4c63-b78d-d855746c5f26 root=/dev/mapper/luks-08f4ae12-6133-4c63-b78d-d855746c5f26 splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 RelatedPackageVersions: linux-restricted-modules-5.15.0-27-generic N/A linux-backports-modules-5.15.0-27-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 Tags: jammy Uname: Linux 5.15.0-27-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-05-03 (0 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/28/2019 dmi.bios.release: 2.32 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET92W (2.32 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FXS09D00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.5 dmi.modalias: dmi:bvnLENOVO:bvrR07ET92W(2.32):bd07/28/2019:br2.32:efr1.5:svnLENOVO:pn20FXS09D00:pvrThinkPadT460p:rvnLENOVO:rn20FXS09D00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20FX_BU_Think_FM_ThinkPadT460p: dmi.product.family: ThinkPad T460p dmi.product.name: 20FXS09D00 dmi.product.sku: LENOVO_MT_20FX_BU_Think_FM_ThinkPad T460p dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jack 1283 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: LXQt DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-04-06 (27 days ago) InstallationMedia: Lubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: LENOVO 20FXS09D00 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=11961357-77ee-4aa4-82c2-359cbb8ef64b ro quiet cryptdevice=UUID=08f4ae12-6133-4c63-b78d-d855746c5f26:luks-08f4ae12-6133-4c63-b78d-d855746c5f26 root=/dev/mapper/luks-08f4ae12-6133-4c63-b78d-d855746c5f26 splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 RelatedPackageVersions: linux-restricted-modules-5.15.0-27-generic N/A linux-backports-modules-5.15.0-27-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 Tags: jammy Uname: Linux 5.15.0-27-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-05-03 (0 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/28/2019 dmi.bios.release: 2.32 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET92W (2.32 ) dmi.board.asset.tag: Not Available dmi.board.name:
[Kernel-packages] [Bug 1971505] Re: DMAR: ERROR: DMA PTE for vPFN 0x8e8fe already set
This might be a duplicate of bug #1970453, which also occurs on HPE servers starting with Ubuntu 22.04. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1971505 Title: DMAR: ERROR: DMA PTE for vPFN 0x8e8fe already set Status in linux package in Ubuntu: Incomplete Bug description: I got this error after a fresh install of Ubuntu 22.4 The server is a Gen8 Microserver. I moved from Fedora 35 to Ubuntu. Everything was working before the format and reinstall. Unfortunately, I cannot get to a command line in order to gather any other logs as the server is hung in mid boot with this error flooding the screen. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Apr 7 19:28 seq crw-rw 1 root audio 116, 33 Apr 7 19:28 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-05-03 (0 days ago) InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220421) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: HP ProLiant MicroServer Gen8 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-27-generic root=UUID=6df4f807-876c-40e3-ba9d-667c4b1c504d ro ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 RelatedPackageVersions: linux-restricted-modules-5.15.0-27-generic N/A linux-backports-modules-5.15.0-27-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: jammy uec-images Uname: Linux 5.15.0-27-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 07/16/2015 dmi.bios.vendor: HP dmi.bios.version: J06 dmi.chassis.type: 7 dmi.chassis.vendor: HP dmi.ec.firmware.release: 2.30 dmi.modalias: dmi:bvnHP:bvrJ06:bd07/16/2015:efr2.30:svnHP:pnProLiantMicroServerGen8:pvr:cvnHP:ct7:cvr:sku819187-001: dmi.product.family: ProLiant dmi.product.name: ProLiant MicroServer Gen8 dmi.product.sku: 819187-001 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971505/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
