[Kernel-packages] [Bug 2080181] [NEW] suspend fails because lockd refuses to freeze
Public bug reported: Up to 5.15.0-117-generic (package 5.15.0-117.127), I could reliably suspend and restart my computer. Now with package 5.15.0-119.129, I cannot suspend. I get this error: Sep 8 21:26:35 trotzdem kernel: [ 2365.487773] Freezing user space processes ... (elapsed 0.003 seconds) done. Sep 8 21:26:35 trotzdem kernel: [ 2365.491406] OOM killer disabled. Sep 8 21:26:35 trotzdem kernel: [ 2365.491408] Freezing remaining freezable tasks ... Sep 8 21:26:35 trotzdem kernel: [ 2385.497718] Freezing of tasks failed after 20.005 seconds (1 tasks refusing to freeze, wq_busy=0): Sep 8 21:26:35 trotzdem kernel: [ 2385.497884] task:lockd state:I stack:0 pid: 1677 ppid: 2 flags:0x4000 Sep 8 21:26:35 trotzdem kernel: [ 2385.497893] Call Trace: Sep 8 21:26:35 trotzdem kernel: [ 2385.497898] Sep 8 21:26:35 trotzdem kernel: [ 2385.497904] __schedule+0x24e/0x590 Sep 8 21:26:35 trotzdem kernel: [ 2385.497916] schedule+0x69/0x110 Sep 8 21:26:35 trotzdem kernel: [ 2385.497922] schedule_timeout+0x105/0x140 Sep 8 21:26:35 trotzdem kernel: [ 2385.497931] svc_get_next_xprt+0xf1/0x190 [sunrpc] Sep 8 21:26:35 trotzdem kernel: [ 2385.498041] svc_recv+0x1a9/0x330 [sunrpc] Sep 8 21:26:35 trotzdem kernel: [ 2385.498142] lockd+0xa9/0x1c0 [lockd] Sep 8 21:26:35 trotzdem kernel: [ 2385.498162] ? set_grace_period+0xa0/0xa0 [lockd] Sep 8 21:26:35 trotzdem kernel: [ 2385.498179] kthread+0x12a/0x150 Sep 8 21:26:35 trotzdem kernel: [ 2385.498188] ? set_kthread_struct+0x50/0x50 Sep 8 21:26:35 trotzdem kernel: [ 2385.498196] ret_from_fork+0x22/0x30 Sep 8 21:26:35 trotzdem kernel: [ 2385.498206] Sep 8 21:26:35 trotzdem kernel: [ 2385.498450] Sep 8 21:26:35 trotzdem kernel: [ 2385.498452] Restarting kernel threads ... Sep 8 21:26:35 trotzdem kernel: [ 2385.498661] usb 2-1: USB disconnect, device number 5 Sep 8 21:26:35 trotzdem kernel: [ 2385.498756] done. Sep 8 21:26:35 trotzdem kernel: [ 2385.498761] OOM killer enabled. It is consistently lockd which produces this error. As far as I know, lockd is related to NFS. This computer is an NFS client. I believe the issue started in version 5.15.0-118.128. I will re-test to confirm, then update this report. ** Affects: linux-signed-hwe-5.15 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/2080181 Title: suspend fails because lockd refuses to freeze Status in linux-signed-hwe-5.15 package in Ubuntu: New Bug description: Up to 5.15.0-117-generic (package 5.15.0-117.127), I could reliably suspend and restart my computer. Now with package 5.15.0-119.129, I cannot suspend. I get this error: Sep 8 21:26:35 trotzdem kernel: [ 2365.487773] Freezing user space processes ... (elapsed 0.003 seconds) done. Sep 8 21:26:35 trotzdem kernel: [ 2365.491406] OOM killer disabled. Sep 8 21:26:35 trotzdem kernel: [ 2365.491408] Freezing remaining freezable tasks ... Sep 8 21:26:35 trotzdem kernel: [ 2385.497718] Freezing of tasks failed after 20.005 seconds (1 tasks refusing to freeze, wq_busy=0): Sep 8 21:26:35 trotzdem kernel: [ 2385.497884] task:lockd state:I stack:0 pid: 1677 ppid: 2 flags:0x4000 Sep 8 21:26:35 trotzdem kernel: [ 2385.497893] Call Trace: Sep 8 21:26:35 trotzdem kernel: [ 2385.497898] Sep 8 21:26:35 trotzdem kernel: [ 2385.497904] __schedule+0x24e/0x590 Sep 8 21:26:35 trotzdem kernel: [ 2385.497916] schedule+0x69/0x110 Sep 8 21:26:35 trotzdem kernel: [ 2385.497922] schedule_timeout+0x105/0x140 Sep 8 21:26:35 trotzdem kernel: [ 2385.497931] svc_get_next_xprt+0xf1/0x190 [sunrpc] Sep 8 21:26:35 trotzdem kernel: [ 2385.498041] svc_recv+0x1a9/0x330 [sunrpc] Sep 8 21:26:35 trotzdem kernel: [ 2385.498142] lockd+0xa9/0x1c0 [lockd] Sep 8 21:26:35 trotzdem kernel: [ 2385.498162] ? set_grace_period+0xa0/0xa0 [lockd] Sep 8 21:26:35 trotzdem kernel: [ 2385.498179] kthread+0x12a/0x150 Sep 8 21:26:35 trotzdem kernel: [ 2385.498188] ? set_kthread_struct+0x50/0x50 Sep 8 21:26:35 trotzdem kernel: [ 2385.498196] ret_from_fork+0x22/0x30 Sep 8 21:26:35 trotzdem kernel: [ 2385.498206] Sep 8 21:26:35 trotzdem kernel: [ 2385.498450] Sep 8 21:26:35 trotzdem kernel: [ 2385.498452] Restarting kernel threads ... Sep 8 21:26:35 trotzdem kernel: [ 2385.498661] usb 2-1: USB disconnect, device number 5 Sep 8 21:26:35 trotzdem kernel: [ 2385.498756] done. Sep 8 21:26:35 trotzdem kernel: [ 2385.498761] OOM killer enabled. It is consistently lockd which produces this error. As far as I know, lockd is related to NFS. This computer is an NFS client. I believe the issue started in version 5.15.0-118.128. I will re-test to confirm, then update this report. To manage notifications about this bug go to: https://bugs.launchpad.net/u
[Kernel-packages] [Bug 2047683] Re: Kernel build fails on debian/build/tools-perarch/tools/bpf/bpftool/vmlinux
Follow-up from my previous comment. The build appears to fail if I try to run it twice without running "clean" in between. In other words, to successfully build, I ran: fakeroot debian/rules clean fakeroot debian/rules binary-headers binary-generic binary-perarch The drawback is it rebuilds everything (which is about 45 minutes on my machine). -- 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/2047683 Title: Kernel build fails on debian/build/tools- perarch/tools/bpf/bpftool/vmlinux Status in linux package in Ubuntu: Confirmed Bug description: I've been attempting to build both the hwe-edge and lowlatency-hwe- next kernels from source. Both fail on bpftool not being present, though `debian/build/tools-perarch/tools/bpf/bpftool/vmlinux.h` is there. ``` make[1]: Leaving directory '/home/ubuntu/build-linux/linux-hwe-6.5-6.5.0/debian/build/tools-perarch/tools/perf' mv /home/ubuntu/build-linux/linux-hwe-6.5-6.5.0/debian/build/tools-perarch/tools/bpf/bpftool/vmlinux /home/ubuntu/build-linux/linux-hwe-6.5-6.5.0/debian/build/tools-perarch/vmlinux mv: cannot stat '/home/ubuntu/build-linux/linux-hwe-6.5-6.5.0/debian/build/tools-perarch/tools/bpf/bpftool/vmlinux': No such file or directory make: *** [debian/rules.d/2-binary-arch.mk:713: /home/ubuntu/build-linux/linux-hwe-6.5-6.5.0/debian/stamps/stamp-build-perarch] Error 1 ``` I've installed the related version of libbpf1 and libbpf-devel, but still seeing this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2047683/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2047683] Re: Kernel build fails on debian/build/tools-perarch/tools/bpf/bpftool/vmlinux
I experienced a similar issue building 6.5.0-25 on Ubuntu 22.04. I followed the steps in the "Build Your Own Kernel" post: https://wiki.ubuntu.com/Kernel/BuildYourOwnKernel Specifically, the error occurs after I ran the build step with the parameters: fakeroot debian/rules binary-headers binary-generic binary-perarch I tried the LLVM and CC tricks mentioned in the previous post, but it did not 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/2047683 Title: Kernel build fails on debian/build/tools- perarch/tools/bpf/bpftool/vmlinux Status in linux package in Ubuntu: Confirmed Bug description: I've been attempting to build both the hwe-edge and lowlatency-hwe- next kernels from source. Both fail on bpftool not being present, though `debian/build/tools-perarch/tools/bpf/bpftool/vmlinux.h` is there. ``` make[1]: Leaving directory '/home/ubuntu/build-linux/linux-hwe-6.5-6.5.0/debian/build/tools-perarch/tools/perf' mv /home/ubuntu/build-linux/linux-hwe-6.5-6.5.0/debian/build/tools-perarch/tools/bpf/bpftool/vmlinux /home/ubuntu/build-linux/linux-hwe-6.5-6.5.0/debian/build/tools-perarch/vmlinux mv: cannot stat '/home/ubuntu/build-linux/linux-hwe-6.5-6.5.0/debian/build/tools-perarch/tools/bpf/bpftool/vmlinux': No such file or directory make: *** [debian/rules.d/2-binary-arch.mk:713: /home/ubuntu/build-linux/linux-hwe-6.5-6.5.0/debian/stamps/stamp-build-perarch] Error 1 ``` I've installed the related version of libbpf1 and libbpf-devel, but still seeing this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2047683/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2049674] [NEW] package libnvidia-compute-390 (not installed) failed to install/upgrade: trying to overwrite shared '/etc/OpenCL/vendors/nvidia.icd', which is different from othe
Public bug reported: I tried to switch from nouveau to nvdidia-390 (in Additional Drivers) and got the above error message. The proprietary driver will not install. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: libnvidia-compute-390 (not installed) ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3 Uname: Linux 6.5.0-14-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass Date: Wed Jan 17 14:30:02 2024 DuplicateSignature: package:libnvidia-compute-390:(not installed) Unpacking libnvidia-compute-390:amd64 (390.157-0ubuntu0.22.04.2) ... dpkg: error processing archive /tmp/apt-dpkg-install-QgW0Up/63-libnvidia-compute-390_390.157-0ubuntu0.22.04.2_amd64.deb (--unpack): trying to overwrite shared '/etc/OpenCL/vendors/nvidia.icd', which is different from other instances of package libnvidia-compute-390:amd64 ErrorMessage: trying to overwrite shared '/etc/OpenCL/vendors/nvidia.icd', which is different from other instances of package libnvidia-compute-390:amd64 InstallationDate: Installed on 2024-01-16 (1 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.11 SourcePackage: nvidia-graphics-drivers-390 Title: package libnvidia-compute-390 (not installed) failed to install/upgrade: trying to overwrite shared '/etc/OpenCL/vendors/nvidia.icd', which is different from other instances of package libnvidia-compute-390:amd64 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-390 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package jammy need-duplicate-check package-conflict -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/2049674 Title: package libnvidia-compute-390 (not installed) failed to install/upgrade: trying to overwrite shared '/etc/OpenCL/vendors/nvidia.icd', which is different from other instances of package libnvidia-compute-390:amd64 Status in nvidia-graphics-drivers-390 package in Ubuntu: New Bug description: I tried to switch from nouveau to nvdidia-390 (in Additional Drivers) and got the above error message. The proprietary driver will not install. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: libnvidia-compute-390 (not installed) ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3 Uname: Linux 6.5.0-14-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass Date: Wed Jan 17 14:30:02 2024 DuplicateSignature: package:libnvidia-compute-390:(not installed) Unpacking libnvidia-compute-390:amd64 (390.157-0ubuntu0.22.04.2) ... dpkg: error processing archive /tmp/apt-dpkg-install-QgW0Up/63-libnvidia-compute-390_390.157-0ubuntu0.22.04.2_amd64.deb (--unpack): trying to overwrite shared '/etc/OpenCL/vendors/nvidia.icd', which is different from other instances of package libnvidia-compute-390:amd64 ErrorMessage: trying to overwrite shared '/etc/OpenCL/vendors/nvidia.icd', which is different from other instances of package libnvidia-compute-390:amd64 InstallationDate: Installed on 2024-01-16 (1 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.11 SourcePackage: nvidia-graphics-drivers-390 Title: package libnvidia-compute-390 (not installed) failed to install/upgrade: trying to overwrite shared '/etc/OpenCL/vendors/nvidia.icd', which is different from other instances of package libnvidia-compute-390:amd64 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2049674/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2049514] [NEW] sleeping laptop and moving between external monitors triggers screen flickering
Public bug reported: Note: this has been happening for many of the past kernel releases. Wasn't seeing this under Ubuntu-22.04 until around 6 months ago - but it's been triggering ever since (although not all the time) Basically I'll be docked at work on my Dell Latitude laptop, pull out the USB-C connector (which power/ethernet/HDMI runs through) and go home. Then plug into a similar dock at home. End result is the same whether it's work->home or home->work, the laptop un-sleeps, monitor comes back to life - but the screen is flickering, wayland seems to think the monitor is waay bigger than it is (eg fonts are big) and it's unusable. Once in this state, plugging/unplugging cables doesn't help - only a reboot fixes the problem. Then it all works again for several home<->work journey's - until it happens again. No real rhythm to it from what I can see - maybe once every couple of weeks? But definitely related to coming back from sleep-mode Googling around shows the same symptoms related to the kernel error i915 :00:02.0: [drm] *ERROR* CPU pipe A FIFO underrun: transcoder Suggested fixes seems to mention it's related to cstate and a suggested fix is to edit /etc/default/grub with GRUB_CMDLINE_LINUX="i915.enable_psr=0 intel_idle.max_cstate=4" I'm going to give that a go to see if it helps ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-39-generic 6.2.0-39.40~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jan 17 04:03:13 2024 InstallationDate: Installed on 2022-03-13 (673 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe-6.2 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2049514 Title: sleeping laptop and moving between external monitors triggers screen flickering Status in linux-signed-hwe-6.2 package in Ubuntu: New Bug description: Note: this has been happening for many of the past kernel releases. Wasn't seeing this under Ubuntu-22.04 until around 6 months ago - but it's been triggering ever since (although not all the time) Basically I'll be docked at work on my Dell Latitude laptop, pull out the USB-C connector (which power/ethernet/HDMI runs through) and go home. Then plug into a similar dock at home. End result is the same whether it's work->home or home->work, the laptop un-sleeps, monitor comes back to life - but the screen is flickering, wayland seems to think the monitor is waay bigger than it is (eg fonts are big) and it's unusable. Once in this state, plugging/unplugging cables doesn't help - only a reboot fixes the problem. Then it all works again for several home<->work journey's - until it happens again. No real rhythm to it from what I can see - maybe once every couple of weeks? But definitely related to coming back from sleep-mode Googling around shows the same symptoms related to the kernel error i915 :00:02.0: [drm] *ERROR* CPU pipe A FIFO underrun: transcoder Suggested fixes seems to mention it's related to cstate and a suggested fix is to edit /etc/default/grub with GRUB_CMDLINE_LINUX="i915.enable_psr=0 intel_idle.max_cstate=4" I'm going to give that a go to see if it helps ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-39-generic 6.2.0-39.40~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jan 17 04:03:13 2024 InstallationDate: Installed on 2022-03-13 (673 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.2/+bug/2049514/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1921536] Re: "modprobe: ERROR: could not insert 'nvidia': Key was rejected by service" due to binutils mismatch
Same here. > sudo apt install nvidia-driver-535 linux-modules-nvidia-535-generic > sudo apt remove nvidia-dkms-535 After doing this you also have to roll back the kernel to 6.2.0-24 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules in Ubuntu. https://bugs.launchpad.net/bugs/1921536 Title: "modprobe: ERROR: could not insert 'nvidia': Key was rejected by service" due to binutils mismatch Status in linux package in Ubuntu: Confirmed Status in linux-restricted-modules package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-525 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-535 package in Ubuntu: Confirmed Bug description: If a user does not have the same version of binutils installed as the one used to produce the nvidia module signature, the module generated at postinst maybe unloadable: modprobe: ERROR: could not insert 'nvidia': Key was rejected by service I ran into this when I tried to install the hirsute kernel/nvidia driver on a focal system. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1921536/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2024677] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/2024677/+attachment/5681503/+files/acpidump.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2024677 Title: This kernel fails to install properly Status in linux package in Ubuntu: Confirmed Bug description: After updates, this kernel fails to install properly then causes failed package installs afterwards, fixing broken package does no good. I used TIMESHIFT to step back before that update, and placed an IGNORE on this kernel, and everything is fine now. Ubuntu 5.15.0-67.74-generic 5.15.85 00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v3/4th Gen Core Proc$ Subsystem: Dell Xeon E3-1200 v3/4th Gen Core Processor DRAM Controller $ Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Ste$ Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- Kernel modules: ie31200_edac 00:01.0 PCI bridge [0604]: Intel Corporation Xeon E3-1200 v3/4th Gen Core Proce$ Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Ste$ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- TAbort- Reset- FastB2B- --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jason 3481 F pulseaudio /dev/snd/pcmC1D0p: jason 3481 F...m pulseaudio /dev/snd/controlC0: jason 3481 F pulseaudio /dev/snd/controlC2: jason 3481 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: XFCE DistroRelease: Linux Mint 21.1 InstallationDate: Installed on 2022-02-04 (502 days ago) InstallationMedia: Linux Mint 20 "Ulyana" - Release amd64 20200624 MachineType: Dell Inc. Precision M6800 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-67-generic root=UUID=1e080b6a-a43a-43c0-8098-7d61b1482ac7 ro quiet splash zswap.enabled=1 zswap.zpool=z3fold zswap.compressor=lz4 vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-67.74-generic 5.15.85 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: linux-restricted-modules-5.15.0-67-generic N/A linux-backports-modules-5.15.0-67-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.13 Tags: vera Uname: Linux 5.15.0-67-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip fax floppy lpadmin netdev news plugdev sambashare scanner sudo tape video _MarkForUpload: True dmi.bios.date: 10/08/2018 dmi.bios.release: 65.25 dmi.bios.vendor: Dell Inc. dmi.bios.version: A25 dmi.board.name: 0F5HF3 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA25:bd10/08/2018:br65.25:svnDellInc.:pnPrecisionM6800:pvr00:rvnDellInc.:rn0F5HF3:rvrA00:cvnDellInc.:ct9:cvr:sku05CD: dmi.product.name: Precision M6800 dmi.product.sku: 05CD dmi.product.version: 00 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2024677/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2024677] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/2024677/+attachment/5681501/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2024677 Title: This kernel fails to install properly Status in linux package in Ubuntu: Confirmed Bug description: After updates, this kernel fails to install properly then causes failed package installs afterwards, fixing broken package does no good. I used TIMESHIFT to step back before that update, and placed an IGNORE on this kernel, and everything is fine now. Ubuntu 5.15.0-67.74-generic 5.15.85 00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v3/4th Gen Core Proc$ Subsystem: Dell Xeon E3-1200 v3/4th Gen Core Processor DRAM Controller $ Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Ste$ Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- Kernel modules: ie31200_edac 00:01.0 PCI bridge [0604]: Intel Corporation Xeon E3-1200 v3/4th Gen Core Proce$ Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Ste$ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- TAbort- Reset- FastB2B- --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jason 3481 F pulseaudio /dev/snd/pcmC1D0p: jason 3481 F...m pulseaudio /dev/snd/controlC0: jason 3481 F pulseaudio /dev/snd/controlC2: jason 3481 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: XFCE DistroRelease: Linux Mint 21.1 InstallationDate: Installed on 2022-02-04 (502 days ago) InstallationMedia: Linux Mint 20 "Ulyana" - Release amd64 20200624 MachineType: Dell Inc. Precision M6800 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-67-generic root=UUID=1e080b6a-a43a-43c0-8098-7d61b1482ac7 ro quiet splash zswap.enabled=1 zswap.zpool=z3fold zswap.compressor=lz4 vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-67.74-generic 5.15.85 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: linux-restricted-modules-5.15.0-67-generic N/A linux-backports-modules-5.15.0-67-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.13 Tags: vera Uname: Linux 5.15.0-67-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip fax floppy lpadmin netdev news plugdev sambashare scanner sudo tape video _MarkForUpload: True dmi.bios.date: 10/08/2018 dmi.bios.release: 65.25 dmi.bios.vendor: Dell Inc. dmi.bios.version: A25 dmi.board.name: 0F5HF3 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA25:bd10/08/2018:br65.25:svnDellInc.:pnPrecisionM6800:pvr00:rvnDellInc.:rn0F5HF3:rvrA00:cvnDellInc.:ct9:cvr:sku05CD: dmi.product.name: Precision M6800 dmi.product.sku: 05CD dmi.product.version: 00 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2024677/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2024677] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/2024677/+attachment/5681502/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2024677 Title: This kernel fails to install properly Status in linux package in Ubuntu: Confirmed Bug description: After updates, this kernel fails to install properly then causes failed package installs afterwards, fixing broken package does no good. I used TIMESHIFT to step back before that update, and placed an IGNORE on this kernel, and everything is fine now. Ubuntu 5.15.0-67.74-generic 5.15.85 00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v3/4th Gen Core Proc$ Subsystem: Dell Xeon E3-1200 v3/4th Gen Core Processor DRAM Controller $ Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Ste$ Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- Kernel modules: ie31200_edac 00:01.0 PCI bridge [0604]: Intel Corporation Xeon E3-1200 v3/4th Gen Core Proce$ Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Ste$ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- TAbort- Reset- FastB2B- --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jason 3481 F pulseaudio /dev/snd/pcmC1D0p: jason 3481 F...m pulseaudio /dev/snd/controlC0: jason 3481 F pulseaudio /dev/snd/controlC2: jason 3481 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: XFCE DistroRelease: Linux Mint 21.1 InstallationDate: Installed on 2022-02-04 (502 days ago) InstallationMedia: Linux Mint 20 "Ulyana" - Release amd64 20200624 MachineType: Dell Inc. Precision M6800 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-67-generic root=UUID=1e080b6a-a43a-43c0-8098-7d61b1482ac7 ro quiet splash zswap.enabled=1 zswap.zpool=z3fold zswap.compressor=lz4 vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-67.74-generic 5.15.85 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: linux-restricted-modules-5.15.0-67-generic N/A linux-backports-modules-5.15.0-67-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.13 Tags: vera Uname: Linux 5.15.0-67-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip fax floppy lpadmin netdev news plugdev sambashare scanner sudo tape video _MarkForUpload: True dmi.bios.date: 10/08/2018 dmi.bios.release: 65.25 dmi.bios.vendor: Dell Inc. dmi.bios.version: A25 dmi.board.name: 0F5HF3 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA25:bd10/08/2018:br65.25:svnDellInc.:pnPrecisionM6800:pvr00:rvnDellInc.:rn0F5HF3:rvrA00:cvnDellInc.:ct9:cvr:sku05CD: dmi.product.name: Precision M6800 dmi.product.sku: 05CD dmi.product.version: 00 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2024677/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2024677] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/2024677/+attachment/5681500/+files/RfKill.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2024677 Title: This kernel fails to install properly Status in linux package in Ubuntu: Confirmed Bug description: After updates, this kernel fails to install properly then causes failed package installs afterwards, fixing broken package does no good. I used TIMESHIFT to step back before that update, and placed an IGNORE on this kernel, and everything is fine now. Ubuntu 5.15.0-67.74-generic 5.15.85 00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v3/4th Gen Core Proc$ Subsystem: Dell Xeon E3-1200 v3/4th Gen Core Processor DRAM Controller $ Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Ste$ Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- Kernel modules: ie31200_edac 00:01.0 PCI bridge [0604]: Intel Corporation Xeon E3-1200 v3/4th Gen Core Proce$ Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Ste$ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- TAbort- Reset- FastB2B- --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jason 3481 F pulseaudio /dev/snd/pcmC1D0p: jason 3481 F...m pulseaudio /dev/snd/controlC0: jason 3481 F pulseaudio /dev/snd/controlC2: jason 3481 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: XFCE DistroRelease: Linux Mint 21.1 InstallationDate: Installed on 2022-02-04 (502 days ago) InstallationMedia: Linux Mint 20 "Ulyana" - Release amd64 20200624 MachineType: Dell Inc. Precision M6800 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-67-generic root=UUID=1e080b6a-a43a-43c0-8098-7d61b1482ac7 ro quiet splash zswap.enabled=1 zswap.zpool=z3fold zswap.compressor=lz4 vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-67.74-generic 5.15.85 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: linux-restricted-modules-5.15.0-67-generic N/A linux-backports-modules-5.15.0-67-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.13 Tags: vera Uname: Linux 5.15.0-67-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip fax floppy lpadmin netdev news plugdev sambashare scanner sudo tape video _MarkForUpload: True dmi.bios.date: 10/08/2018 dmi.bios.release: 65.25 dmi.bios.vendor: Dell Inc. dmi.bios.version: A25 dmi.board.name: 0F5HF3 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA25:bd10/08/2018:br65.25:svnDellInc.:pnPrecisionM6800:pvr00:rvnDellInc.:rn0F5HF3:rvrA00:cvnDellInc.:ct9:cvr:sku05CD: dmi.product.name: Precision M6800 dmi.product.sku: 05CD dmi.product.version: 00 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2024677/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2024677] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/2024677/+attachment/5681496/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2024677 Title: This kernel fails to install properly Status in linux package in Ubuntu: Confirmed Bug description: After updates, this kernel fails to install properly then causes failed package installs afterwards, fixing broken package does no good. I used TIMESHIFT to step back before that update, and placed an IGNORE on this kernel, and everything is fine now. Ubuntu 5.15.0-67.74-generic 5.15.85 00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v3/4th Gen Core Proc$ Subsystem: Dell Xeon E3-1200 v3/4th Gen Core Processor DRAM Controller $ Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Ste$ Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- Kernel modules: ie31200_edac 00:01.0 PCI bridge [0604]: Intel Corporation Xeon E3-1200 v3/4th Gen Core Proce$ Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Ste$ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- TAbort- Reset- FastB2B- --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jason 3481 F pulseaudio /dev/snd/pcmC1D0p: jason 3481 F...m pulseaudio /dev/snd/controlC0: jason 3481 F pulseaudio /dev/snd/controlC2: jason 3481 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: XFCE DistroRelease: Linux Mint 21.1 InstallationDate: Installed on 2022-02-04 (502 days ago) InstallationMedia: Linux Mint 20 "Ulyana" - Release amd64 20200624 MachineType: Dell Inc. Precision M6800 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-67-generic root=UUID=1e080b6a-a43a-43c0-8098-7d61b1482ac7 ro quiet splash zswap.enabled=1 zswap.zpool=z3fold zswap.compressor=lz4 vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-67.74-generic 5.15.85 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: linux-restricted-modules-5.15.0-67-generic N/A linux-backports-modules-5.15.0-67-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.13 Tags: vera Uname: Linux 5.15.0-67-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip fax floppy lpadmin netdev news plugdev sambashare scanner sudo tape video _MarkForUpload: True dmi.bios.date: 10/08/2018 dmi.bios.release: 65.25 dmi.bios.vendor: Dell Inc. dmi.bios.version: A25 dmi.board.name: 0F5HF3 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA25:bd10/08/2018:br65.25:svnDellInc.:pnPrecisionM6800:pvr00:rvnDellInc.:rn0F5HF3:rvrA00:cvnDellInc.:ct9:cvr:sku05CD: dmi.product.name: Precision M6800 dmi.product.sku: 05CD dmi.product.version: 00 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2024677/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2024677] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/2024677/+attachment/5681497/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2024677 Title: This kernel fails to install properly Status in linux package in Ubuntu: Confirmed Bug description: After updates, this kernel fails to install properly then causes failed package installs afterwards, fixing broken package does no good. I used TIMESHIFT to step back before that update, and placed an IGNORE on this kernel, and everything is fine now. Ubuntu 5.15.0-67.74-generic 5.15.85 00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v3/4th Gen Core Proc$ Subsystem: Dell Xeon E3-1200 v3/4th Gen Core Processor DRAM Controller $ Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Ste$ Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- Kernel modules: ie31200_edac 00:01.0 PCI bridge [0604]: Intel Corporation Xeon E3-1200 v3/4th Gen Core Proce$ Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Ste$ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- TAbort- Reset- FastB2B- --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jason 3481 F pulseaudio /dev/snd/pcmC1D0p: jason 3481 F...m pulseaudio /dev/snd/controlC0: jason 3481 F pulseaudio /dev/snd/controlC2: jason 3481 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: XFCE DistroRelease: Linux Mint 21.1 InstallationDate: Installed on 2022-02-04 (502 days ago) InstallationMedia: Linux Mint 20 "Ulyana" - Release amd64 20200624 MachineType: Dell Inc. Precision M6800 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-67-generic root=UUID=1e080b6a-a43a-43c0-8098-7d61b1482ac7 ro quiet splash zswap.enabled=1 zswap.zpool=z3fold zswap.compressor=lz4 vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-67.74-generic 5.15.85 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: linux-restricted-modules-5.15.0-67-generic N/A linux-backports-modules-5.15.0-67-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.13 Tags: vera Uname: Linux 5.15.0-67-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip fax floppy lpadmin netdev news plugdev sambashare scanner sudo tape video _MarkForUpload: True dmi.bios.date: 10/08/2018 dmi.bios.release: 65.25 dmi.bios.vendor: Dell Inc. dmi.bios.version: A25 dmi.board.name: 0F5HF3 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA25:bd10/08/2018:br65.25:svnDellInc.:pnPrecisionM6800:pvr00:rvnDellInc.:rn0F5HF3:rvrA00:cvnDellInc.:ct9:cvr:sku05CD: dmi.product.name: Precision M6800 dmi.product.sku: 05CD dmi.product.version: 00 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2024677/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2024677] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/2024677/+attachment/5681499/+files/PulseList.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2024677 Title: This kernel fails to install properly Status in linux package in Ubuntu: Confirmed Bug description: After updates, this kernel fails to install properly then causes failed package installs afterwards, fixing broken package does no good. I used TIMESHIFT to step back before that update, and placed an IGNORE on this kernel, and everything is fine now. Ubuntu 5.15.0-67.74-generic 5.15.85 00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v3/4th Gen Core Proc$ Subsystem: Dell Xeon E3-1200 v3/4th Gen Core Processor DRAM Controller $ Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Ste$ Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- Kernel modules: ie31200_edac 00:01.0 PCI bridge [0604]: Intel Corporation Xeon E3-1200 v3/4th Gen Core Proce$ Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Ste$ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- TAbort- Reset- FastB2B- --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jason 3481 F pulseaudio /dev/snd/pcmC1D0p: jason 3481 F...m pulseaudio /dev/snd/controlC0: jason 3481 F pulseaudio /dev/snd/controlC2: jason 3481 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: XFCE DistroRelease: Linux Mint 21.1 InstallationDate: Installed on 2022-02-04 (502 days ago) InstallationMedia: Linux Mint 20 "Ulyana" - Release amd64 20200624 MachineType: Dell Inc. Precision M6800 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-67-generic root=UUID=1e080b6a-a43a-43c0-8098-7d61b1482ac7 ro quiet splash zswap.enabled=1 zswap.zpool=z3fold zswap.compressor=lz4 vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-67.74-generic 5.15.85 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: linux-restricted-modules-5.15.0-67-generic N/A linux-backports-modules-5.15.0-67-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.13 Tags: vera Uname: Linux 5.15.0-67-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip fax floppy lpadmin netdev news plugdev sambashare scanner sudo tape video _MarkForUpload: True dmi.bios.date: 10/08/2018 dmi.bios.release: 65.25 dmi.bios.vendor: Dell Inc. dmi.bios.version: A25 dmi.board.name: 0F5HF3 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA25:bd10/08/2018:br65.25:svnDellInc.:pnPrecisionM6800:pvr00:rvnDellInc.:rn0F5HF3:rvrA00:cvnDellInc.:ct9:cvr:sku05CD: dmi.product.name: Precision M6800 dmi.product.sku: 05CD dmi.product.version: 00 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2024677/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2024677] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/2024677/+attachment/5681498/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2024677 Title: This kernel fails to install properly Status in linux package in Ubuntu: Confirmed Bug description: After updates, this kernel fails to install properly then causes failed package installs afterwards, fixing broken package does no good. I used TIMESHIFT to step back before that update, and placed an IGNORE on this kernel, and everything is fine now. Ubuntu 5.15.0-67.74-generic 5.15.85 00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v3/4th Gen Core Proc$ Subsystem: Dell Xeon E3-1200 v3/4th Gen Core Processor DRAM Controller $ Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Ste$ Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- Kernel modules: ie31200_edac 00:01.0 PCI bridge [0604]: Intel Corporation Xeon E3-1200 v3/4th Gen Core Proce$ Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Ste$ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- TAbort- Reset- FastB2B- --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jason 3481 F pulseaudio /dev/snd/pcmC1D0p: jason 3481 F...m pulseaudio /dev/snd/controlC0: jason 3481 F pulseaudio /dev/snd/controlC2: jason 3481 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: XFCE DistroRelease: Linux Mint 21.1 InstallationDate: Installed on 2022-02-04 (502 days ago) InstallationMedia: Linux Mint 20 "Ulyana" - Release amd64 20200624 MachineType: Dell Inc. Precision M6800 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-67-generic root=UUID=1e080b6a-a43a-43c0-8098-7d61b1482ac7 ro quiet splash zswap.enabled=1 zswap.zpool=z3fold zswap.compressor=lz4 vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-67.74-generic 5.15.85 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: linux-restricted-modules-5.15.0-67-generic N/A linux-backports-modules-5.15.0-67-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.13 Tags: vera Uname: Linux 5.15.0-67-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip fax floppy lpadmin netdev news plugdev sambashare scanner sudo tape video _MarkForUpload: True dmi.bios.date: 10/08/2018 dmi.bios.release: 65.25 dmi.bios.vendor: Dell Inc. dmi.bios.version: A25 dmi.board.name: 0F5HF3 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA25:bd10/08/2018:br65.25:svnDellInc.:pnPrecisionM6800:pvr00:rvnDellInc.:rn0F5HF3:rvrA00:cvnDellInc.:ct9:cvr:sku05CD: dmi.product.name: Precision M6800 dmi.product.sku: 05CD dmi.product.version: 00 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2024677/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2024677] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/2024677/+attachment/5681495/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2024677 Title: This kernel fails to install properly Status in linux package in Ubuntu: Confirmed Bug description: After updates, this kernel fails to install properly then causes failed package installs afterwards, fixing broken package does no good. I used TIMESHIFT to step back before that update, and placed an IGNORE on this kernel, and everything is fine now. Ubuntu 5.15.0-67.74-generic 5.15.85 00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v3/4th Gen Core Proc$ Subsystem: Dell Xeon E3-1200 v3/4th Gen Core Processor DRAM Controller $ Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Ste$ Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- Kernel modules: ie31200_edac 00:01.0 PCI bridge [0604]: Intel Corporation Xeon E3-1200 v3/4th Gen Core Proce$ Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Ste$ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- TAbort- Reset- FastB2B- --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jason 3481 F pulseaudio /dev/snd/pcmC1D0p: jason 3481 F...m pulseaudio /dev/snd/controlC0: jason 3481 F pulseaudio /dev/snd/controlC2: jason 3481 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: XFCE DistroRelease: Linux Mint 21.1 InstallationDate: Installed on 2022-02-04 (502 days ago) InstallationMedia: Linux Mint 20 "Ulyana" - Release amd64 20200624 MachineType: Dell Inc. Precision M6800 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-67-generic root=UUID=1e080b6a-a43a-43c0-8098-7d61b1482ac7 ro quiet splash zswap.enabled=1 zswap.zpool=z3fold zswap.compressor=lz4 vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-67.74-generic 5.15.85 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: linux-restricted-modules-5.15.0-67-generic N/A linux-backports-modules-5.15.0-67-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.13 Tags: vera Uname: Linux 5.15.0-67-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip fax floppy lpadmin netdev news plugdev sambashare scanner sudo tape video _MarkForUpload: True dmi.bios.date: 10/08/2018 dmi.bios.release: 65.25 dmi.bios.vendor: Dell Inc. dmi.bios.version: A25 dmi.board.name: 0F5HF3 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA25:bd10/08/2018:br65.25:svnDellInc.:pnPrecisionM6800:pvr00:rvnDellInc.:rn0F5HF3:rvrA00:cvnDellInc.:ct9:cvr:sku05CD: dmi.product.name: Precision M6800 dmi.product.sku: 05CD dmi.product.version: 00 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2024677/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2024677] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/2024677/+attachment/5681492/+files/Lsusb-v.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2024677 Title: This kernel fails to install properly Status in linux package in Ubuntu: Confirmed Bug description: After updates, this kernel fails to install properly then causes failed package installs afterwards, fixing broken package does no good. I used TIMESHIFT to step back before that update, and placed an IGNORE on this kernel, and everything is fine now. Ubuntu 5.15.0-67.74-generic 5.15.85 00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v3/4th Gen Core Proc$ Subsystem: Dell Xeon E3-1200 v3/4th Gen Core Processor DRAM Controller $ Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Ste$ Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- Kernel modules: ie31200_edac 00:01.0 PCI bridge [0604]: Intel Corporation Xeon E3-1200 v3/4th Gen Core Proce$ Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Ste$ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- TAbort- Reset- FastB2B- --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jason 3481 F pulseaudio /dev/snd/pcmC1D0p: jason 3481 F...m pulseaudio /dev/snd/controlC0: jason 3481 F pulseaudio /dev/snd/controlC2: jason 3481 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: XFCE DistroRelease: Linux Mint 21.1 InstallationDate: Installed on 2022-02-04 (502 days ago) InstallationMedia: Linux Mint 20 "Ulyana" - Release amd64 20200624 MachineType: Dell Inc. Precision M6800 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-67-generic root=UUID=1e080b6a-a43a-43c0-8098-7d61b1482ac7 ro quiet splash zswap.enabled=1 zswap.zpool=z3fold zswap.compressor=lz4 vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-67.74-generic 5.15.85 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: linux-restricted-modules-5.15.0-67-generic N/A linux-backports-modules-5.15.0-67-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.13 Tags: vera Uname: Linux 5.15.0-67-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip fax floppy lpadmin netdev news plugdev sambashare scanner sudo tape video _MarkForUpload: True dmi.bios.date: 10/08/2018 dmi.bios.release: 65.25 dmi.bios.vendor: Dell Inc. dmi.bios.version: A25 dmi.board.name: 0F5HF3 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA25:bd10/08/2018:br65.25:svnDellInc.:pnPrecisionM6800:pvr00:rvnDellInc.:rn0F5HF3:rvrA00:cvnDellInc.:ct9:cvr:sku05CD: dmi.product.name: Precision M6800 dmi.product.sku: 05CD dmi.product.version: 00 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2024677/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2024677] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/2024677/+attachment/5681494/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2024677 Title: This kernel fails to install properly Status in linux package in Ubuntu: Confirmed Bug description: After updates, this kernel fails to install properly then causes failed package installs afterwards, fixing broken package does no good. I used TIMESHIFT to step back before that update, and placed an IGNORE on this kernel, and everything is fine now. Ubuntu 5.15.0-67.74-generic 5.15.85 00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v3/4th Gen Core Proc$ Subsystem: Dell Xeon E3-1200 v3/4th Gen Core Processor DRAM Controller $ Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Ste$ Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- Kernel modules: ie31200_edac 00:01.0 PCI bridge [0604]: Intel Corporation Xeon E3-1200 v3/4th Gen Core Proce$ Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Ste$ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- TAbort- Reset- FastB2B- --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jason 3481 F pulseaudio /dev/snd/pcmC1D0p: jason 3481 F...m pulseaudio /dev/snd/controlC0: jason 3481 F pulseaudio /dev/snd/controlC2: jason 3481 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: XFCE DistroRelease: Linux Mint 21.1 InstallationDate: Installed on 2022-02-04 (502 days ago) InstallationMedia: Linux Mint 20 "Ulyana" - Release amd64 20200624 MachineType: Dell Inc. Precision M6800 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-67-generic root=UUID=1e080b6a-a43a-43c0-8098-7d61b1482ac7 ro quiet splash zswap.enabled=1 zswap.zpool=z3fold zswap.compressor=lz4 vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-67.74-generic 5.15.85 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: linux-restricted-modules-5.15.0-67-generic N/A linux-backports-modules-5.15.0-67-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.13 Tags: vera Uname: Linux 5.15.0-67-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip fax floppy lpadmin netdev news plugdev sambashare scanner sudo tape video _MarkForUpload: True dmi.bios.date: 10/08/2018 dmi.bios.release: 65.25 dmi.bios.vendor: Dell Inc. dmi.bios.version: A25 dmi.board.name: 0F5HF3 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA25:bd10/08/2018:br65.25:svnDellInc.:pnPrecisionM6800:pvr00:rvnDellInc.:rn0F5HF3:rvrA00:cvnDellInc.:ct9:cvr:sku05CD: dmi.product.name: Precision M6800 dmi.product.sku: 05CD dmi.product.version: 00 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2024677/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2024677] PaInfo.txt
apport information ** Attachment added: "PaInfo.txt" https://bugs.launchpad.net/bugs/2024677/+attachment/5681493/+files/PaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2024677 Title: This kernel fails to install properly Status in linux package in Ubuntu: Confirmed Bug description: After updates, this kernel fails to install properly then causes failed package installs afterwards, fixing broken package does no good. I used TIMESHIFT to step back before that update, and placed an IGNORE on this kernel, and everything is fine now. Ubuntu 5.15.0-67.74-generic 5.15.85 00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v3/4th Gen Core Proc$ Subsystem: Dell Xeon E3-1200 v3/4th Gen Core Processor DRAM Controller $ Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Ste$ Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- Kernel modules: ie31200_edac 00:01.0 PCI bridge [0604]: Intel Corporation Xeon E3-1200 v3/4th Gen Core Proce$ Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Ste$ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- TAbort- Reset- FastB2B- --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jason 3481 F pulseaudio /dev/snd/pcmC1D0p: jason 3481 F...m pulseaudio /dev/snd/controlC0: jason 3481 F pulseaudio /dev/snd/controlC2: jason 3481 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: XFCE DistroRelease: Linux Mint 21.1 InstallationDate: Installed on 2022-02-04 (502 days ago) InstallationMedia: Linux Mint 20 "Ulyana" - Release amd64 20200624 MachineType: Dell Inc. Precision M6800 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-67-generic root=UUID=1e080b6a-a43a-43c0-8098-7d61b1482ac7 ro quiet splash zswap.enabled=1 zswap.zpool=z3fold zswap.compressor=lz4 vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-67.74-generic 5.15.85 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: linux-restricted-modules-5.15.0-67-generic N/A linux-backports-modules-5.15.0-67-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.13 Tags: vera Uname: Linux 5.15.0-67-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip fax floppy lpadmin netdev news plugdev sambashare scanner sudo tape video _MarkForUpload: True dmi.bios.date: 10/08/2018 dmi.bios.release: 65.25 dmi.bios.vendor: Dell Inc. dmi.bios.version: A25 dmi.board.name: 0F5HF3 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA25:bd10/08/2018:br65.25:svnDellInc.:pnPrecisionM6800:pvr00:rvnDellInc.:rn0F5HF3:rvrA00:cvnDellInc.:ct9:cvr:sku05CD: dmi.product.name: Precision M6800 dmi.product.sku: 05CD dmi.product.version: 00 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2024677/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2024677] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/2024677/+attachment/5681491/+files/Lsusb-t.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2024677 Title: This kernel fails to install properly Status in linux package in Ubuntu: Confirmed Bug description: After updates, this kernel fails to install properly then causes failed package installs afterwards, fixing broken package does no good. I used TIMESHIFT to step back before that update, and placed an IGNORE on this kernel, and everything is fine now. Ubuntu 5.15.0-67.74-generic 5.15.85 00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v3/4th Gen Core Proc$ Subsystem: Dell Xeon E3-1200 v3/4th Gen Core Processor DRAM Controller $ Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Ste$ Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- Kernel modules: ie31200_edac 00:01.0 PCI bridge [0604]: Intel Corporation Xeon E3-1200 v3/4th Gen Core Proce$ Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Ste$ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- TAbort- Reset- FastB2B- --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jason 3481 F pulseaudio /dev/snd/pcmC1D0p: jason 3481 F...m pulseaudio /dev/snd/controlC0: jason 3481 F pulseaudio /dev/snd/controlC2: jason 3481 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: XFCE DistroRelease: Linux Mint 21.1 InstallationDate: Installed on 2022-02-04 (502 days ago) InstallationMedia: Linux Mint 20 "Ulyana" - Release amd64 20200624 MachineType: Dell Inc. Precision M6800 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-67-generic root=UUID=1e080b6a-a43a-43c0-8098-7d61b1482ac7 ro quiet splash zswap.enabled=1 zswap.zpool=z3fold zswap.compressor=lz4 vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-67.74-generic 5.15.85 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: linux-restricted-modules-5.15.0-67-generic N/A linux-backports-modules-5.15.0-67-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.13 Tags: vera Uname: Linux 5.15.0-67-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip fax floppy lpadmin netdev news plugdev sambashare scanner sudo tape video _MarkForUpload: True dmi.bios.date: 10/08/2018 dmi.bios.release: 65.25 dmi.bios.vendor: Dell Inc. dmi.bios.version: A25 dmi.board.name: 0F5HF3 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA25:bd10/08/2018:br65.25:svnDellInc.:pnPrecisionM6800:pvr00:rvnDellInc.:rn0F5HF3:rvrA00:cvnDellInc.:ct9:cvr:sku05CD: dmi.product.name: Precision M6800 dmi.product.sku: 05CD dmi.product.version: 00 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2024677/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2024677] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/2024677/+attachment/5681489/+files/Lspci-vt.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2024677 Title: This kernel fails to install properly Status in linux package in Ubuntu: Confirmed Bug description: After updates, this kernel fails to install properly then causes failed package installs afterwards, fixing broken package does no good. I used TIMESHIFT to step back before that update, and placed an IGNORE on this kernel, and everything is fine now. Ubuntu 5.15.0-67.74-generic 5.15.85 00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v3/4th Gen Core Proc$ Subsystem: Dell Xeon E3-1200 v3/4th Gen Core Processor DRAM Controller $ Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Ste$ Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- Kernel modules: ie31200_edac 00:01.0 PCI bridge [0604]: Intel Corporation Xeon E3-1200 v3/4th Gen Core Proce$ Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Ste$ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- TAbort- Reset- FastB2B- --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jason 3481 F pulseaudio /dev/snd/pcmC1D0p: jason 3481 F...m pulseaudio /dev/snd/controlC0: jason 3481 F pulseaudio /dev/snd/controlC2: jason 3481 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: XFCE DistroRelease: Linux Mint 21.1 InstallationDate: Installed on 2022-02-04 (502 days ago) InstallationMedia: Linux Mint 20 "Ulyana" - Release amd64 20200624 MachineType: Dell Inc. Precision M6800 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-67-generic root=UUID=1e080b6a-a43a-43c0-8098-7d61b1482ac7 ro quiet splash zswap.enabled=1 zswap.zpool=z3fold zswap.compressor=lz4 vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-67.74-generic 5.15.85 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: linux-restricted-modules-5.15.0-67-generic N/A linux-backports-modules-5.15.0-67-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.13 Tags: vera Uname: Linux 5.15.0-67-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip fax floppy lpadmin netdev news plugdev sambashare scanner sudo tape video _MarkForUpload: True dmi.bios.date: 10/08/2018 dmi.bios.release: 65.25 dmi.bios.vendor: Dell Inc. dmi.bios.version: A25 dmi.board.name: 0F5HF3 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA25:bd10/08/2018:br65.25:svnDellInc.:pnPrecisionM6800:pvr00:rvnDellInc.:rn0F5HF3:rvrA00:cvnDellInc.:ct9:cvr:sku05CD: dmi.product.name: Precision M6800 dmi.product.sku: 05CD dmi.product.version: 00 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2024677/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2024677] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/2024677/+attachment/5681488/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2024677 Title: This kernel fails to install properly Status in linux package in Ubuntu: Confirmed Bug description: After updates, this kernel fails to install properly then causes failed package installs afterwards, fixing broken package does no good. I used TIMESHIFT to step back before that update, and placed an IGNORE on this kernel, and everything is fine now. Ubuntu 5.15.0-67.74-generic 5.15.85 00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v3/4th Gen Core Proc$ Subsystem: Dell Xeon E3-1200 v3/4th Gen Core Processor DRAM Controller $ Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Ste$ Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- Kernel modules: ie31200_edac 00:01.0 PCI bridge [0604]: Intel Corporation Xeon E3-1200 v3/4th Gen Core Proce$ Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Ste$ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- TAbort- Reset- FastB2B- --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jason 3481 F pulseaudio /dev/snd/pcmC1D0p: jason 3481 F...m pulseaudio /dev/snd/controlC0: jason 3481 F pulseaudio /dev/snd/controlC2: jason 3481 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: XFCE DistroRelease: Linux Mint 21.1 InstallationDate: Installed on 2022-02-04 (502 days ago) InstallationMedia: Linux Mint 20 "Ulyana" - Release amd64 20200624 MachineType: Dell Inc. Precision M6800 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-67-generic root=UUID=1e080b6a-a43a-43c0-8098-7d61b1482ac7 ro quiet splash zswap.enabled=1 zswap.zpool=z3fold zswap.compressor=lz4 vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-67.74-generic 5.15.85 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: linux-restricted-modules-5.15.0-67-generic N/A linux-backports-modules-5.15.0-67-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.13 Tags: vera Uname: Linux 5.15.0-67-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip fax floppy lpadmin netdev news plugdev sambashare scanner sudo tape video _MarkForUpload: True dmi.bios.date: 10/08/2018 dmi.bios.release: 65.25 dmi.bios.vendor: Dell Inc. dmi.bios.version: A25 dmi.board.name: 0F5HF3 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA25:bd10/08/2018:br65.25:svnDellInc.:pnPrecisionM6800:pvr00:rvnDellInc.:rn0F5HF3:rvrA00:cvnDellInc.:ct9:cvr:sku05CD: dmi.product.name: Precision M6800 dmi.product.sku: 05CD dmi.product.version: 00 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2024677/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2024677] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/2024677/+attachment/5681490/+files/Lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2024677 Title: This kernel fails to install properly Status in linux package in Ubuntu: Confirmed Bug description: After updates, this kernel fails to install properly then causes failed package installs afterwards, fixing broken package does no good. I used TIMESHIFT to step back before that update, and placed an IGNORE on this kernel, and everything is fine now. Ubuntu 5.15.0-67.74-generic 5.15.85 00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v3/4th Gen Core Proc$ Subsystem: Dell Xeon E3-1200 v3/4th Gen Core Processor DRAM Controller $ Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Ste$ Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- Kernel modules: ie31200_edac 00:01.0 PCI bridge [0604]: Intel Corporation Xeon E3-1200 v3/4th Gen Core Proce$ Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Ste$ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- TAbort- Reset- FastB2B- --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jason 3481 F pulseaudio /dev/snd/pcmC1D0p: jason 3481 F...m pulseaudio /dev/snd/controlC0: jason 3481 F pulseaudio /dev/snd/controlC2: jason 3481 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: XFCE DistroRelease: Linux Mint 21.1 InstallationDate: Installed on 2022-02-04 (502 days ago) InstallationMedia: Linux Mint 20 "Ulyana" - Release amd64 20200624 MachineType: Dell Inc. Precision M6800 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-67-generic root=UUID=1e080b6a-a43a-43c0-8098-7d61b1482ac7 ro quiet splash zswap.enabled=1 zswap.zpool=z3fold zswap.compressor=lz4 vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-67.74-generic 5.15.85 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: linux-restricted-modules-5.15.0-67-generic N/A linux-backports-modules-5.15.0-67-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.13 Tags: vera Uname: Linux 5.15.0-67-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip fax floppy lpadmin netdev news plugdev sambashare scanner sudo tape video _MarkForUpload: True dmi.bios.date: 10/08/2018 dmi.bios.release: 65.25 dmi.bios.vendor: Dell Inc. dmi.bios.version: A25 dmi.board.name: 0F5HF3 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA25:bd10/08/2018:br65.25:svnDellInc.:pnPrecisionM6800:pvr00:rvnDellInc.:rn0F5HF3:rvrA00:cvnDellInc.:ct9:cvr:sku05CD: dmi.product.name: Precision M6800 dmi.product.sku: 05CD dmi.product.version: 00 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2024677/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2024677] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/2024677/+attachment/5681487/+files/IwConfig.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2024677 Title: This kernel fails to install properly Status in linux package in Ubuntu: Confirmed Bug description: After updates, this kernel fails to install properly then causes failed package installs afterwards, fixing broken package does no good. I used TIMESHIFT to step back before that update, and placed an IGNORE on this kernel, and everything is fine now. Ubuntu 5.15.0-67.74-generic 5.15.85 00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v3/4th Gen Core Proc$ Subsystem: Dell Xeon E3-1200 v3/4th Gen Core Processor DRAM Controller $ Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Ste$ Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- Kernel modules: ie31200_edac 00:01.0 PCI bridge [0604]: Intel Corporation Xeon E3-1200 v3/4th Gen Core Proce$ Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Ste$ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- TAbort- Reset- FastB2B- --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jason 3481 F pulseaudio /dev/snd/pcmC1D0p: jason 3481 F...m pulseaudio /dev/snd/controlC0: jason 3481 F pulseaudio /dev/snd/controlC2: jason 3481 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: XFCE DistroRelease: Linux Mint 21.1 InstallationDate: Installed on 2022-02-04 (502 days ago) InstallationMedia: Linux Mint 20 "Ulyana" - Release amd64 20200624 MachineType: Dell Inc. Precision M6800 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-67-generic root=UUID=1e080b6a-a43a-43c0-8098-7d61b1482ac7 ro quiet splash zswap.enabled=1 zswap.zpool=z3fold zswap.compressor=lz4 vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-67.74-generic 5.15.85 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: linux-restricted-modules-5.15.0-67-generic N/A linux-backports-modules-5.15.0-67-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.13 Tags: vera Uname: Linux 5.15.0-67-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip fax floppy lpadmin netdev news plugdev sambashare scanner sudo tape video _MarkForUpload: True dmi.bios.date: 10/08/2018 dmi.bios.release: 65.25 dmi.bios.vendor: Dell Inc. dmi.bios.version: A25 dmi.board.name: 0F5HF3 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA25:bd10/08/2018:br65.25:svnDellInc.:pnPrecisionM6800:pvr00:rvnDellInc.:rn0F5HF3:rvrA00:cvnDellInc.:ct9:cvr:sku05CD: dmi.product.name: Precision M6800 dmi.product.sku: 05CD dmi.product.version: 00 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2024677/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2024677] Re: This kernel fails to install properly
apport information ** Tags added: apport-collected vera ** Description changed: After updates, this kernel fails to install properly then causes failed package installs afterwards, fixing broken package does no good. I used TIMESHIFT to step back before that update, and placed an IGNORE on this kernel, and everything is fine now. Ubuntu 5.15.0-67.74-generic 5.15.85 00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v3/4th Gen Core Proc$ Subsystem: Dell Xeon E3-1200 v3/4th Gen Core Processor DRAM Controller $ Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Ste$ Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- Kernel modules: ie31200_edac 00:01.0 PCI bridge [0604]: Intel Corporation Xeon E3-1200 v3/4th Gen Core Proce$ Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Ste$ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- TAbort- Reset- FastB2B- + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu82.5 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC1: jason 3481 F pulseaudio + /dev/snd/pcmC1D0p: jason 3481 F...m pulseaudio + /dev/snd/controlC0: jason 3481 F pulseaudio + /dev/snd/controlC2: jason 3481 F pulseaudio + CasperMD5CheckResult: unknown + CurrentDesktop: XFCE + DistroRelease: Linux Mint 21.1 + InstallationDate: Installed on 2022-02-04 (502 days ago) + InstallationMedia: Linux Mint 20 "Ulyana" - Release amd64 20200624 + MachineType: Dell Inc. Precision M6800 + NonfreeKernelModules: nvidia_modeset nvidia + Package: linux (not installed) + ProcFB: 0 i915drmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-67-generic root=UUID=1e080b6a-a43a-43c0-8098-7d61b1482ac7 ro quiet splash zswap.enabled=1 zswap.zpool=z3fold zswap.compressor=lz4 vt.handoff=7 + ProcVersionSignature: Ubuntu 5.15.0-67.74-generic 5.15.85 + RebootRequiredPkgs: Error: path contained symlinks. + RelatedPackageVersions: + linux-restricted-modules-5.15.0-67-generic N/A + linux-backports-modules-5.15.0-67-generic N/A + linux-firmware 20220329.git681281e4-0ubuntu3.13 + Tags: vera + Uname: Linux 5.15.0-67-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm audio cdrom dialout dip fax floppy lpadmin netdev news plugdev sambashare scanner sudo tape video + _MarkForUpload: True + dmi.bios.date: 10/08/2018 + dmi.bios.release: 65.25 + dmi.bios.vendor: Dell Inc. + dmi.bios.version: A25 + dmi.board.name: 0F5HF3 + dmi.board.vendor: Dell Inc. + dmi.board.version: A00 + dmi.chassis.type: 9 + dmi.chassis.vendor: Dell Inc. + dmi.modalias: dmi:bvnDellInc.:bvrA25:bd10/08/2018:br65.25:svnDellInc.:pnPrecisionM6800:pvr00:rvnDellInc.:rn0F5HF3:rvrA00:cvnDellInc.:ct9:cvr:sku05CD: + dmi.product.name: Precision M6800 + dmi.product.sku: 05CD + dmi.product.version: 00 + dmi.sys.vendor: Dell Inc. ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/2024677/+attachment/5681484/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2024677 Title: This kernel fails to install properly Status in linux package in Ubuntu: Confirmed Bug description: After updates, this kernel fails to install properly then causes failed package installs afterwards, fixing broken package does no good. I used TIMESHIFT to step back before that update, and placed an IGNORE on this kernel, and everything is fine now. Ubuntu 5.15.0-67.74-generic 5.15.85 00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v3/4th Gen Core Proc$ Subsystem: Dell Xeon E3-1200 v3/4th Gen Core Processor DRAM Controller $ Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Ste$ Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- Kernel modules: ie31200_edac 00:01.0 PCI bridge [0604]: Intel Corporation Xeon E3-1200 v3/4th Gen Core Proce$ Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Ste$ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- TAbort- Reset- FastB2B- --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jason 3481 F pulseaudio /dev/snd/pcmC1D0p: jason 3481 F...m pulseaudio /dev/snd/controlC0: jason 3481 F pulseaudio /dev/snd/controlC2: jason 3481 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: XFCE DistroRelease: Linux Mint 21.1 InstallationDate: Installed on 2022-02-04 (502 days ago) InstallationMedia: Linux Mint 20 "Ulyana" - Release amd64 2
[Kernel-packages] [Bug 2024677] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/2024677/+attachment/5681485/+files/CRDA.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2024677 Title: This kernel fails to install properly Status in linux package in Ubuntu: Confirmed Bug description: After updates, this kernel fails to install properly then causes failed package installs afterwards, fixing broken package does no good. I used TIMESHIFT to step back before that update, and placed an IGNORE on this kernel, and everything is fine now. Ubuntu 5.15.0-67.74-generic 5.15.85 00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v3/4th Gen Core Proc$ Subsystem: Dell Xeon E3-1200 v3/4th Gen Core Processor DRAM Controller $ Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Ste$ Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- Kernel modules: ie31200_edac 00:01.0 PCI bridge [0604]: Intel Corporation Xeon E3-1200 v3/4th Gen Core Proce$ Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Ste$ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- TAbort- Reset- FastB2B- --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jason 3481 F pulseaudio /dev/snd/pcmC1D0p: jason 3481 F...m pulseaudio /dev/snd/controlC0: jason 3481 F pulseaudio /dev/snd/controlC2: jason 3481 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: XFCE DistroRelease: Linux Mint 21.1 InstallationDate: Installed on 2022-02-04 (502 days ago) InstallationMedia: Linux Mint 20 "Ulyana" - Release amd64 20200624 MachineType: Dell Inc. Precision M6800 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-67-generic root=UUID=1e080b6a-a43a-43c0-8098-7d61b1482ac7 ro quiet splash zswap.enabled=1 zswap.zpool=z3fold zswap.compressor=lz4 vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-67.74-generic 5.15.85 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: linux-restricted-modules-5.15.0-67-generic N/A linux-backports-modules-5.15.0-67-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.13 Tags: vera Uname: Linux 5.15.0-67-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip fax floppy lpadmin netdev news plugdev sambashare scanner sudo tape video _MarkForUpload: True dmi.bios.date: 10/08/2018 dmi.bios.release: 65.25 dmi.bios.vendor: Dell Inc. dmi.bios.version: A25 dmi.board.name: 0F5HF3 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA25:bd10/08/2018:br65.25:svnDellInc.:pnPrecisionM6800:pvr00:rvnDellInc.:rn0F5HF3:rvrA00:cvnDellInc.:ct9:cvr:sku05CD: dmi.product.name: Precision M6800 dmi.product.sku: 05CD dmi.product.version: 00 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2024677/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2024677] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/2024677/+attachment/5681486/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2024677 Title: This kernel fails to install properly Status in linux package in Ubuntu: Confirmed Bug description: After updates, this kernel fails to install properly then causes failed package installs afterwards, fixing broken package does no good. I used TIMESHIFT to step back before that update, and placed an IGNORE on this kernel, and everything is fine now. Ubuntu 5.15.0-67.74-generic 5.15.85 00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v3/4th Gen Core Proc$ Subsystem: Dell Xeon E3-1200 v3/4th Gen Core Processor DRAM Controller $ Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Ste$ Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- Kernel modules: ie31200_edac 00:01.0 PCI bridge [0604]: Intel Corporation Xeon E3-1200 v3/4th Gen Core Proce$ Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Ste$ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- TAbort- Reset- FastB2B- --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jason 3481 F pulseaudio /dev/snd/pcmC1D0p: jason 3481 F...m pulseaudio /dev/snd/controlC0: jason 3481 F pulseaudio /dev/snd/controlC2: jason 3481 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: XFCE DistroRelease: Linux Mint 21.1 InstallationDate: Installed on 2022-02-04 (502 days ago) InstallationMedia: Linux Mint 20 "Ulyana" - Release amd64 20200624 MachineType: Dell Inc. Precision M6800 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-67-generic root=UUID=1e080b6a-a43a-43c0-8098-7d61b1482ac7 ro quiet splash zswap.enabled=1 zswap.zpool=z3fold zswap.compressor=lz4 vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-67.74-generic 5.15.85 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: linux-restricted-modules-5.15.0-67-generic N/A linux-backports-modules-5.15.0-67-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.13 Tags: vera Uname: Linux 5.15.0-67-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip fax floppy lpadmin netdev news plugdev sambashare scanner sudo tape video _MarkForUpload: True dmi.bios.date: 10/08/2018 dmi.bios.release: 65.25 dmi.bios.vendor: Dell Inc. dmi.bios.version: A25 dmi.board.name: 0F5HF3 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA25:bd10/08/2018:br65.25:svnDellInc.:pnPrecisionM6800:pvr00:rvnDellInc.:rn0F5HF3:rvrA00:cvnDellInc.:ct9:cvr:sku05CD: dmi.product.name: Precision M6800 dmi.product.sku: 05CD dmi.product.version: 00 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2024677/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2024677] [NEW] This kernel fails to install properly
Public bug reported: After updates, this kernel fails to install properly then causes failed package installs afterwards, fixing broken package does no good. I used TIMESHIFT to step back before that update, and placed an IGNORE on this kernel, and everything is fine now. Ubuntu 5.15.0-67.74-generic 5.15.85 00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v3/4th Gen Core Proc$ Subsystem: Dell Xeon E3-1200 v3/4th Gen Core Processor DRAM Controller $ Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Ste$ Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- Kernel modules: ie31200_edac 00:01.0 PCI bridge [0604]: Intel Corporation Xeon E3-1200 v3/4th Gen Core Proce$ Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Ste$ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- TAbort- Reset- FastB2B- ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2024677 Title: This kernel fails to install properly Status in linux package in Ubuntu: Incomplete Bug description: After updates, this kernel fails to install properly then causes failed package installs afterwards, fixing broken package does no good. I used TIMESHIFT to step back before that update, and placed an IGNORE on this kernel, and everything is fine now. Ubuntu 5.15.0-67.74-generic 5.15.85 00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v3/4th Gen Core Proc$ Subsystem: Dell Xeon E3-1200 v3/4th Gen Core Processor DRAM Controller $ Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Ste$ Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- Kernel modules: ie31200_edac 00:01.0 PCI bridge [0604]: Intel Corporation Xeon E3-1200 v3/4th Gen Core Proce$ Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Ste$ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- TAbort- Reset- FastB2B- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2024677/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2012818] Re: Computer does not wake up after sleep mode
For me, the issue disappeared with Ubuntu 23.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/2012818 Title: Computer does not wake up after sleep mode Status in linux package in Ubuntu: Confirmed Bug description: Hello, My computer Dell Inspiron 5515 does not always wake up after sleeping, since Linux generic 5.19.0-35, under Ubuntu 22.10. The problem was not solved with Linux 5.19.0-38. Before this version, it worked well. If I start with Linux 5.19.0-29, the sleep mode works well. I have not tested the sleep mode with Linux 5.19.0-31. It appears that there is a regression with the published Linux kernel. I stay available if any more information needs to be transmitted. Thank you in advance, Have a nice day, Jason. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-38-generic 5.19.0-38.39 ProcVersionSignature: Ubuntu 5.19.0-38.39-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Mar 26 13:29:31 2023 InstallationDate: Installed on 2022-05-16 (313 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Dell Inc. Inspiron 5515 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-38-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 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.19.0-38-generic N/A linux-backports-modules-5.19.0-38-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1.4 SourcePackage: linux UpgradeStatus: Upgraded to kinetic on 2022-10-01 (175 days ago) dmi.bios.date: 02/13/2023 dmi.bios.release: 1.15 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.0 dmi.board.name: 0KDKG8 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.asset.tag: 6B1Z8G3 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.15.0 dmi.modalias: dmi:bvnDellInc.:bvr1.15.0:bd02/13/2023:br1.15:svnDellInc.:pnInspiron5515:pvr1.15.0:rvnDellInc.:rn0KDKG8:rvrA01:cvnDellInc.:ct10:cvr1.15.0:sku0A78: dmi.product.family: Inspiron dmi.product.name: Inspiron 5515 dmi.product.sku: 0A78 dmi.product.version: 1.15.0 dmi.sys.vendor: Dell Inc. modified.conffile..etc.default.apport: [modified] mtime.conffile..etc.default.apport: 2022-10-01T21:45:58.694231 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2012818/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2012818] Re: Computer does not wake up after sleep mode
** Description changed: Hello, - My computer Dell Inspiron 5515 does not always wake up after sleeping, since Linux generic 5.19.0-35. The problem was not solved with Linux 5.19.0-38. Before this version, it worked well. If I start with Linux 5.19.0-29, the sleep mode works well. I have not tested the sleep mode with Linux 5.19.0-31. + My computer Dell Inspiron 5515 does not always wake up after sleeping, since Linux generic 5.19.0-35, under Ubuntu 22.10. The problem was not solved with Linux 5.19.0-38. Before this version, it worked well. If I start with Linux 5.19.0-29, the sleep mode works well. I have not tested the sleep mode with Linux 5.19.0-31. + It appears that there is a regression with the published Linux kernel. I stay available if any more information needs to be transmitted. + Thank you in advance, Have a nice day, Jason. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-38-generic 5.19.0-38.39 ProcVersionSignature: Ubuntu 5.19.0-38.39-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Mar 26 13:29:31 2023 InstallationDate: Installed on 2022-05-16 (313 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Dell Inc. Inspiron 5515 ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=fr_FR.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=fr_FR.UTF-8 + SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-38-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 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.19.0-38-generic N/A - linux-backports-modules-5.19.0-38-generic N/A - linux-firmware 20220923.gitf09bebf3-0ubuntu1.4 + linux-restricted-modules-5.19.0-38-generic N/A + linux-backports-modules-5.19.0-38-generic N/A + linux-firmware 20220923.gitf09bebf3-0ubuntu1.4 SourcePackage: linux UpgradeStatus: Upgraded to kinetic on 2022-10-01 (175 days ago) dmi.bios.date: 02/13/2023 dmi.bios.release: 1.15 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.0 dmi.board.name: 0KDKG8 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.asset.tag: 6B1Z8G3 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.15.0 dmi.modalias: dmi:bvnDellInc.:bvr1.15.0:bd02/13/2023:br1.15:svnDellInc.:pnInspiron5515:pvr1.15.0:rvnDellInc.:rn0KDKG8:rvrA01:cvnDellInc.:ct10:cvr1.15.0:sku0A78: dmi.product.family: Inspiron dmi.product.name: Inspiron 5515 dmi.product.sku: 0A78 dmi.product.version: 1.15.0 dmi.sys.vendor: Dell Inc. modified.conffile..etc.default.apport: [modified] mtime.conffile..etc.default.apport: 2022-10-01T21:45:58.694231 -- 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/2012818 Title: Computer does not wake up after sleep mode Status in linux package in Ubuntu: New Bug description: Hello, My computer Dell Inspiron 5515 does not always wake up after sleeping, since Linux generic 5.19.0-35, under Ubuntu 22.10. The problem was not solved with Linux 5.19.0-38. Before this version, it worked well. If I start with Linux 5.19.0-29, the sleep mode works well. I have not tested the sleep mode with Linux 5.19.0-31. It appears that there is a regression with the published Linux kernel. I stay available if any more information needs to be transmitted. Thank you in advance, Have a nice day, Jason. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-38-generic 5.19.0-38.39 ProcVersionSignature: Ubuntu 5.19.0-38.39-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Mar 26 13:29:31 2023 InstallationDate: Installed on 2022-05-16 (313 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Dell Inc. Inspiron 5515 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-38-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-module
[Kernel-packages] [Bug 2012818] [NEW] Computer does not wake up after sleep mode
Public bug reported: Hello, My computer Dell Inspiron 5515 does not always wake up after sleeping, since Linux generic 5.19.0-35, under Ubuntu 22.10. The problem was not solved with Linux 5.19.0-38. Before this version, it worked well. If I start with Linux 5.19.0-29, the sleep mode works well. I have not tested the sleep mode with Linux 5.19.0-31. It appears that there is a regression with the published Linux kernel. I stay available if any more information needs to be transmitted. Thank you in advance, Have a nice day, Jason. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-38-generic 5.19.0-38.39 ProcVersionSignature: Ubuntu 5.19.0-38.39-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Mar 26 13:29:31 2023 InstallationDate: Installed on 2022-05-16 (313 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Dell Inc. Inspiron 5515 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-38-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 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.19.0-38-generic N/A linux-backports-modules-5.19.0-38-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1.4 SourcePackage: linux UpgradeStatus: Upgraded to kinetic on 2022-10-01 (175 days ago) dmi.bios.date: 02/13/2023 dmi.bios.release: 1.15 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.0 dmi.board.name: 0KDKG8 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.asset.tag: 6B1Z8G3 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.15.0 dmi.modalias: dmi:bvnDellInc.:bvr1.15.0:bd02/13/2023:br1.15:svnDellInc.:pnInspiron5515:pvr1.15.0:rvnDellInc.:rn0KDKG8:rvrA01:cvnDellInc.:ct10:cvr1.15.0:sku0A78: dmi.product.family: Inspiron dmi.product.name: Inspiron 5515 dmi.product.sku: 0A78 dmi.product.version: 1.15.0 dmi.sys.vendor: Dell Inc. modified.conffile..etc.default.apport: [modified] mtime.conffile..etc.default.apport: 2022-10-01T21:45:58.694231 ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kinetic wayland-session -- 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/2012818 Title: Computer does not wake up after sleep mode Status in linux package in Ubuntu: New Bug description: Hello, My computer Dell Inspiron 5515 does not always wake up after sleeping, since Linux generic 5.19.0-35, under Ubuntu 22.10. The problem was not solved with Linux 5.19.0-38. Before this version, it worked well. If I start with Linux 5.19.0-29, the sleep mode works well. I have not tested the sleep mode with Linux 5.19.0-31. It appears that there is a regression with the published Linux kernel. I stay available if any more information needs to be transmitted. Thank you in advance, Have a nice day, Jason. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-38-generic 5.19.0-38.39 ProcVersionSignature: Ubuntu 5.19.0-38.39-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Mar 26 13:29:31 2023 InstallationDate: Installed on 2022-05-16 (313 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Dell Inc. Inspiron 5515 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-38-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 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.19.0-38-generic N/A linux-backports-modules-5.19.0-38-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1.4 SourcePackage: linux UpgradeStatus: Upgraded to kinetic on 2022-10-01 (175 days ago) dmi.bios.date: 02/13/2023 dmi.bios.release: 1.15 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.0 dmi.board.name: 0KDKG8 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.asset.tag: 6B1Z8G3 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.15.0 dmi.modalias: dmi:bvnDellI
[Kernel-packages] [Bug 1971460] Re: [amdgpu] System freezes coming out from suspension or randomly from screen power save (5.15.0 fails but 5.18.14 works)
Has this been backported to 5.15 in the meantime? I think I have the same issue using 22.04 with kernel 5.15.0-56-generic also with a rx6000 (using kisak mesa 22.3.0). I'm using 1080p @ 144hz. When entering sleep mode, my monitor wouldn't turn on, but the pc itself seemed to be running. I can also reproduce this issue using xrandr: xrandr --output DisplayPort-0 --primary --mode 1920x1080 --scale-from 1280x960 --rate 144 --pos 0x0 I used to use this command for a game which does not support changing resolution using vulkan. It worked perfectly fine with my old install of ubuntu 20.04, same gpu and driver. -- 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/1971460 Title: [amdgpu] System freezes coming out from suspension or randomly from screen power save (5.15.0 fails but 5.18.14 works) Status in linux package in Ubuntu: Confirmed Bug description: I've Ubuntu 22.04 with Wayland and Sapphire Radeon RX 6600 with Xiaomi 34" curved gaming monitor capable of 3440x1440 @144,00hz. Using refresh of 120hz or 144hz, the system freezes coming out from suspension or randomly from screen power save. Setting @60hz it's more stable. It seems something related to wrong Modeline for this VGA and monitor resolution/frequencies. The problem is with both DP or HDMI cable. With HDMI it supports only 99,99hz I had no problem with the provious HP RX 460 HanSolo or XFX GTX 1060 3GB with proprietary nVidia drivers. 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] Permesso negato: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue May 3 18:29:05 2022 DistUpgraded: Fresh install 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, if not too technical GpuHangFrequency: Several times a day GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Navi 23 [Radeon RX 6600/6600 XT/6600M] [1002:73ff] (rev c7) (prog-if 00 [VGA controller]) Subsystem: Sapphire Technology Limited Navi 23 [Radeon RX 6600/6600 XT/6600M] [1da2:e447] InstallationDate: Installed on 2022-04-23 (9 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: System manufacturer System Product Name ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=be1c4139-f2bc-472b-87c1-099f2be97b1a ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/25/2022 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3604 dmi.board.asset.tag: Default string dmi.board.name: TUF B450M-PRO 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.:bvr3604:bd02/25/2022:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFB450M-PROGAMING: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 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 N/A 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/1971460/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1990190] Re: Focal update: v5.4.211 upstream stable release
The earlier node-exporter problems seem to be the same issue as reported here: https://bugs.launchpad.net/ubuntu/+source/containerd/+bug/1996678 I've observed kubelet suffer PLEG issues on bionic hwe 5.4.0-132.148 that did not occur on 5.4.0-131.147. Re-compiling 5.4.0-132.148 from source with the "epoll: autoremove wakers even more aggressively" commit reverted appears to resolve the issue for me. See also this thread from the kernel mailing list: https://lore.kernel.org/all/20221130003402.hu3l4hehge5xq...@u46989501580c5c.ant.amazon.com/#t -- 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/1990190 Title: Focal update: v5.4.211 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: Fix Released Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.4.211 upstream stable release from git://git.kernel.org/ Makefile: link with -z noexecstack --no-warn-rwx-segments x86: link vdso and boot with -z noexecstack --no-warn-rwx-segments scsi: Revert "scsi: qla2xxx: Fix disk failure to rediscover" ALSA: bcd2000: Fix a UAF bug on the error path of probing igc: Remove _I_PHY_ID checking wifi: mac80211_hwsim: fix race condition in pending packet wifi: mac80211_hwsim: add back erroneously removed cast wifi: mac80211_hwsim: use 32-bit skb cookie add barriers to buffer_uptodate and set_buffer_uptodate HID: wacom: Only report rotation for art pen HID: wacom: Don't register pad_input for touch switch KVM: nVMX: Snapshot pre-VM-Enter BNDCFGS for !nested_run_pending case KVM: nVMX: Snapshot pre-VM-Enter DEBUGCTL for !nested_run_pending case KVM: SVM: Don't BUG if userspace injects an interrupt with GIF=0 KVM: nVMX: Let userspace set nVMX MSR to any _host_ supported value KVM: x86: Mark TSS busy during LTR emulation _after_ all fault checks KVM: x86: Set error code to segment selector on LLDT/LTR non-canonical #GP mm/mremap: hold the rmap lock in write mode when moving page table entries. ALSA: hda/conexant: Add quirk for LENOVO 20149 Notebook model ALSA: hda/cirrus - support for iMac 12,1 model ALSA: hda/realtek: Add quirk for another Asus K42JZ model tty: vt: initialize unicode screen buffer vfs: Check the truncate maximum size in inode_newsize_ok() fs: Add missing umask strip in vfs_tmpfile thermal: sysfs: Fix cooling_device_stats_setup() error code path fbcon: Fix boundary checks for fbcon=vc:n1-n2 parameters usbnet: Fix linkwatch use-after-free on disconnect ovl: drop WARN_ON() dentry is NULL in ovl_encode_fh() parisc: Fix device names in /proc/iomem parisc: io_pgetevents_time64() needs compat syscall in 32-bit compat mode drm/gem: Properly annotate WW context on drm_gem_lock_reservations() error drm/nouveau: fix another off-by-one in nvbios_addr drm/amdgpu: Check BO's requested pinning domains against its preferred_domains iio: light: isl29028: Fix the warning in isl29028_remove() fuse: limit nsec serial: mvebu-uart: uart2 error bits clearing md-raid10: fix KASAN warning ia64, processor: fix -Wincompatible-pointer-types in ia64_get_irr() PCI: Add defines for normal and subtractive PCI bridges powerpc/fsl-pci: Fix Class Code of PCIe Root Port powerpc/ptdump: Fix display of RW pages on FSL_BOOK3E powerpc/powernv: Avoid crashing if rng is NULL MIPS: cpuinfo: Fix a warning for CONFIG_CPUMASK_OFFSTACK coresight: Clear the connection field properly USB: HCD: Fix URB giveback issue in tasklet function ARM: dts: uniphier: Fix USB interrupts for PXs2 SoC arm64: dts: uniphier: Fix USB interrupts for PXs3 SoC netfilter: nf_tables: fix null deref due to zeroed list head epoll: autoremove wakers even more aggressively x86: Handle idle=nomwait cmdline properly for x86_idle arm64: Do not forget syscall when starting a new thread. arm64: fix oops in concurrently setting insn_emulation sysctls ext2: Add more validity checks for inode counts genirq: Don't return error on missing optional irq_request_resources() wait: Fix __wait_event_hrtimeout for RT/DL tasks ARM: dts: imx6ul: add missing properties for sram ARM: dts: imx6ul: change operating-points to uint32-matrix ARM: dts: imx6ul: fix csi node compatible ARM: dts: imx6ul: fix lcdif node compatible ARM: dts: imx6ul: fix qspi node compatible spi: synquacer: Add missing clk_disable_unprepare() ARM: OMAP2+: display: Fix refcount leak bug ACPI: EC: Remove duplic
[Kernel-packages] [Bug 1992118] Re: AX210 (8086:e024) WLAN init failed ucode -5 after upgrading to 5.15 intel IoTG kernel
Checked with the customer who impacted by this regression. They confirmed the fix in proposed channel. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel-iotg-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/1992118 Title: AX210 (8086:e024) WLAN init failed ucode -5 after upgrading to 5.15 intel IoTG kernel Status in HWE Next: New Status in linux-firmware package in Ubuntu: Fix Committed Status in linux-intel-iotg-5.15 package in Ubuntu: Invalid Status in linux-firmware source package in Focal: Fix Committed Bug description: [Summary] AX210 (8086:e024) WLAN init failed ucode -5 after upgrading to 5.15 Intel IoTG kernel. [Steps to reproduce] $ sudo apt update $ sudo apt upgrade $ reboot [Expected result] WLAN works with no problem. [Actual result] Can't detect WLAN. [Failure rate] 100% [Other Info] [4.485407] iwlwifi :02:00.0: enabling device ( -> 0002) [4.512442] iwlwifi :02:00.0: api flags index 2 larger than supported by driver [4.512500] iwlwifi :02:00.0: TLV_FW_FSEQ_VERSION: FSEQ Version: 0.63.2.2 [4.514725] iwlwifi :02:00.0: loaded firmware version 66.f1c864e0.0 ty-a0-gf-a0-66.ucode op_mode iwlmvm [4.636133] iwlwifi :02:00.0: Detected Intel(R) Wi-Fi 6 AX210 160MHz, REV=0x420 [4.811565] iwlwifi :02:00.0: Detected RF GF, rfid=0x10d000 [4.812366] iwlwifi :02:00.0: Microcode SW error detected. Restarting 0x0. [4.812478] iwlwifi :02:00.0: Start IWL Error Log Dump: [4.812484] iwlwifi :02:00.0: Transport status: 0x004A, valid: 6 [4.812489] iwlwifi :02:00.0: Loaded firmware version: 66.f1c864e0.0 ty-a0-gf-a0-66.ucode [4.812494] iwlwifi :02:00.0: 0x0071 | NMI_INTERRUPT_UMAC_FATAL [4.812499] iwlwifi :02:00.0: 0x002002F0 | trm_hw_status0 [4.812503] iwlwifi :02:00.0: 0x | trm_hw_status1 [4.812507] iwlwifi :02:00.0: 0x004DA722 | branchlink2 [4.812510] iwlwifi :02:00.0: 0x004D0CCE | interruptlink1 [4.812514] iwlwifi :02:00.0: 0x004D0CCE | interruptlink2 [4.812517] iwlwifi :02:00.0: 0x004D94DA | data1 [4.812520] iwlwifi :02:00.0: 0x0010 | data2 [4.812523] iwlwifi :02:00.0: 0x | data3 [4.812527] iwlwifi :02:00.0: 0x | beacon time [4.812530] iwlwifi :02:00.0: 0x0001324E | tsf low [4.812533] iwlwifi :02:00.0: 0x | tsf hi [4.812536] iwlwifi :02:00.0: 0x | time gp1 [4.812540] iwlwifi :02:00.0: 0x000244E1 | time gp2 [4.812543] iwlwifi :02:00.0: 0x0001 | uCode revision type [4.812546] iwlwifi :02:00.0: 0x0042 | uCode version major [4.812550] iwlwifi :02:00.0: 0xF1C864E0 | uCode version minor [4.812553] iwlwifi :02:00.0: 0x0420 | hw version [4.812557] iwlwifi :02:00.0: 0x18C89002 | board version [4.812560] iwlwifi :02:00.0: 0x8008FF05 | hcmd [4.812563] iwlwifi :02:00.0: 0x0002 | isr0 [4.812566] iwlwifi :02:00.0: 0x6000 | isr1 [4.812569] iwlwifi :02:00.0: 0x48F2 | isr2 [4.812572] iwlwifi :02:00.0: 0x00C0001C | isr3 [4.812575] iwlwifi :02:00.0: 0x | isr4 [4.812578] iwlwifi :02:00.0: 0x | last cmd Id [4.812581] iwlwifi :02:00.0: 0x004D94DA | wait_event [4.812584] iwlwifi :02:00.0: 0x | l2p_control [4.812588] iwlwifi :02:00.0: 0x | l2p_duration [4.812591] iwlwifi :02:00.0: 0x | l2p_mhvalid [4.812594] iwlwifi :02:00.0: 0x | l2p_addr_match [4.812597] iwlwifi :02:00.0: 0x0009 | lmpm_pmg_sel [4.812600] iwlwifi :02:00.0: 0x | timestamp [4.812603] iwlwifi :02:00.0: 0x0024 | flow_handler [4.812640] iwlwifi :02:00.0: Start IWL Error Log Dump: [4.812643] iwlwifi :02:00.0: Transport status: 0x004A, valid: 7 [4.812647] iwlwifi :02:00.0: 0x2010070D | ADVANCED_SYSASSERT [4.812651] iwlwifi :02:00.0: 0x | umac branchlink1 [4.812654] iwlwifi :02:00.0: 0x8045DFC6 | umac branchlink2 [4.812658] iwlwifi :02:00.0: 0x010910FE | umac interruptlink1 [4.812661] iwlwifi :02:00.0: 0x | umac interruptlink2 [4.812664] iwlwifi :02:00.0: 0x0005 | umac data1 [4.812667] iwlwifi :02:00.0: 0xDEADBEEF | umac data2 [4.812670] iwlwifi :02:00.0: 0xDEADBEEF | umac data3 [4.812673] iwlwifi :02:00.0: 0x0042 | umac major [4.812677] iwlwifi :02:00.0: 0xF1C864E0 | umac minor [4.812680] iwlwifi :02:00.0: 0x000244D8 | frame pointer [4.812683] iwlwifi :02:00.0: 0xC0885E88 | stack pointer [4.812686] iwlwifi :02:00.0: 0x00010C00 | last host cmd [4.812689] iwlwifi :02:00.0: 0x | isr status reg
[Kernel-packages] [Bug 1993040] Re: After resuming from suspend, NIC has WOL disabled
** 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/1993040 Title: After resuming from suspend, NIC has WOL disabled Status in linux package in Ubuntu: Confirmed Bug description: I have my NIC configured with WOL in magic packet mode: ``` $ sudo ethtool enp5s0 Settings for enp5s0: ... Supports Wake-on: pumbg Wake-on: g ``` However, every time I resume the system from suspend once, WOL becomes disabled: ``` $ sudo ethtool enp5s0 Settings for enp5s0: ... Supports Wake-on: pumbg Wake-on: d ``` I can re-enable it and it'll work fine. If I don't re-enable it, I am unable to use magic packet to WOL if I suspend the system again (as expected, since it gets disabled). This seems to be new behaviour with Jammy - I didn't experience this problem on Bionic with the same hardware. Driver info: ``` $ sudo ethtool -i enp5s0 driver: igb version: 5.15.0-48-generic firmware-version: 0. 6-1 expansion-rom-version: bus-info: :05:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes ``` --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-id', '/dev/snd/controlC3', '/dev/snd/pcmC3D0c', '/dev/snd/controlC2', '/dev/snd/hwC2D0', '/dev/snd/pcmC2D2c', '/dev/snd/pcmC2D1p', '/dev/snd/pcmC2D0c', '/dev/snd/pcmC2D0p', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D12p', '/dev/snd/pcmC0D11p', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: unknown DistroRelease: Ubuntu 22.04 MachineType: Gigabyte Technology Co., Ltd. X570 AORUS ULTRA NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=screen.xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/zsh ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-48-generic root=UUID=bf8ca071-393b-42bf-9259-3e4b410e9ad2 ro nvidia-drm.modeset=0 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: XDG_RUNTIME_DIR (/run/user/1000) is not owned by us (uid 0), but by uid 1000! (This could e.g. happen if you try to connect to a non-root PulseAudio as a root user, over the native protocol. Don't do that.) No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-48-generic N/A linux-backports-modules-5.15.0-48-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 Tags: jammy Uname: Linux 5.15.0-48-generic x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False dmi.bios.date: 05/12/2022 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F36c dmi.board.asset.tag: Default string dmi.board.name: X570 AORUS ULTRA dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF36c:bd05/12/2022:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSULTRA:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSULTRA:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: X570 MB dmi.product.name: X570 AORUS ULTRA dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1993040/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1993040] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1993040/+attachment/5624564/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1993040 Title: After resuming from suspend, NIC has WOL disabled Status in linux package in Ubuntu: Incomplete Bug description: I have my NIC configured with WOL in magic packet mode: ``` $ sudo ethtool enp5s0 Settings for enp5s0: ... Supports Wake-on: pumbg Wake-on: g ``` However, every time I resume the system from suspend once, WOL becomes disabled: ``` $ sudo ethtool enp5s0 Settings for enp5s0: ... Supports Wake-on: pumbg Wake-on: d ``` I can re-enable it and it'll work fine. If I don't re-enable it, I am unable to use magic packet to WOL if I suspend the system again (as expected, since it gets disabled). This seems to be new behaviour with Jammy - I didn't experience this problem on Bionic with the same hardware. Driver info: ``` $ sudo ethtool -i enp5s0 driver: igb version: 5.15.0-48-generic firmware-version: 0. 6-1 expansion-rom-version: bus-info: :05:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes ``` --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-id', '/dev/snd/controlC3', '/dev/snd/pcmC3D0c', '/dev/snd/controlC2', '/dev/snd/hwC2D0', '/dev/snd/pcmC2D2c', '/dev/snd/pcmC2D1p', '/dev/snd/pcmC2D0c', '/dev/snd/pcmC2D0p', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D12p', '/dev/snd/pcmC0D11p', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: unknown DistroRelease: Ubuntu 22.04 MachineType: Gigabyte Technology Co., Ltd. X570 AORUS ULTRA NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=screen.xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/zsh ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-48-generic root=UUID=bf8ca071-393b-42bf-9259-3e4b410e9ad2 ro nvidia-drm.modeset=0 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: XDG_RUNTIME_DIR (/run/user/1000) is not owned by us (uid 0), but by uid 1000! (This could e.g. happen if you try to connect to a non-root PulseAudio as a root user, over the native protocol. Don't do that.) No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-48-generic N/A linux-backports-modules-5.15.0-48-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 Tags: jammy Uname: Linux 5.15.0-48-generic x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False dmi.bios.date: 05/12/2022 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F36c dmi.board.asset.tag: Default string dmi.board.name: X570 AORUS ULTRA dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF36c:bd05/12/2022:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSULTRA:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSULTRA:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: X570 MB dmi.product.name: X570 AORUS ULTRA dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1993040/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1993040] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1993040/+attachment/5624565/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1993040 Title: After resuming from suspend, NIC has WOL disabled Status in linux package in Ubuntu: Incomplete Bug description: I have my NIC configured with WOL in magic packet mode: ``` $ sudo ethtool enp5s0 Settings for enp5s0: ... Supports Wake-on: pumbg Wake-on: g ``` However, every time I resume the system from suspend once, WOL becomes disabled: ``` $ sudo ethtool enp5s0 Settings for enp5s0: ... Supports Wake-on: pumbg Wake-on: d ``` I can re-enable it and it'll work fine. If I don't re-enable it, I am unable to use magic packet to WOL if I suspend the system again (as expected, since it gets disabled). This seems to be new behaviour with Jammy - I didn't experience this problem on Bionic with the same hardware. Driver info: ``` $ sudo ethtool -i enp5s0 driver: igb version: 5.15.0-48-generic firmware-version: 0. 6-1 expansion-rom-version: bus-info: :05:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes ``` --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-id', '/dev/snd/controlC3', '/dev/snd/pcmC3D0c', '/dev/snd/controlC2', '/dev/snd/hwC2D0', '/dev/snd/pcmC2D2c', '/dev/snd/pcmC2D1p', '/dev/snd/pcmC2D0c', '/dev/snd/pcmC2D0p', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D12p', '/dev/snd/pcmC0D11p', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: unknown DistroRelease: Ubuntu 22.04 MachineType: Gigabyte Technology Co., Ltd. X570 AORUS ULTRA NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=screen.xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/zsh ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-48-generic root=UUID=bf8ca071-393b-42bf-9259-3e4b410e9ad2 ro nvidia-drm.modeset=0 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: XDG_RUNTIME_DIR (/run/user/1000) is not owned by us (uid 0), but by uid 1000! (This could e.g. happen if you try to connect to a non-root PulseAudio as a root user, over the native protocol. Don't do that.) No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-48-generic N/A linux-backports-modules-5.15.0-48-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 Tags: jammy Uname: Linux 5.15.0-48-generic x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False dmi.bios.date: 05/12/2022 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F36c dmi.board.asset.tag: Default string dmi.board.name: X570 AORUS ULTRA dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF36c:bd05/12/2022:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSULTRA:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSULTRA:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: X570 MB dmi.product.name: X570 AORUS ULTRA dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1993040/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1993040] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1993040/+attachment/5624566/+files/RfKill.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1993040 Title: After resuming from suspend, NIC has WOL disabled Status in linux package in Ubuntu: Incomplete Bug description: I have my NIC configured with WOL in magic packet mode: ``` $ sudo ethtool enp5s0 Settings for enp5s0: ... Supports Wake-on: pumbg Wake-on: g ``` However, every time I resume the system from suspend once, WOL becomes disabled: ``` $ sudo ethtool enp5s0 Settings for enp5s0: ... Supports Wake-on: pumbg Wake-on: d ``` I can re-enable it and it'll work fine. If I don't re-enable it, I am unable to use magic packet to WOL if I suspend the system again (as expected, since it gets disabled). This seems to be new behaviour with Jammy - I didn't experience this problem on Bionic with the same hardware. Driver info: ``` $ sudo ethtool -i enp5s0 driver: igb version: 5.15.0-48-generic firmware-version: 0. 6-1 expansion-rom-version: bus-info: :05:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes ``` --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-id', '/dev/snd/controlC3', '/dev/snd/pcmC3D0c', '/dev/snd/controlC2', '/dev/snd/hwC2D0', '/dev/snd/pcmC2D2c', '/dev/snd/pcmC2D1p', '/dev/snd/pcmC2D0c', '/dev/snd/pcmC2D0p', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D12p', '/dev/snd/pcmC0D11p', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: unknown DistroRelease: Ubuntu 22.04 MachineType: Gigabyte Technology Co., Ltd. X570 AORUS ULTRA NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=screen.xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/zsh ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-48-generic root=UUID=bf8ca071-393b-42bf-9259-3e4b410e9ad2 ro nvidia-drm.modeset=0 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: XDG_RUNTIME_DIR (/run/user/1000) is not owned by us (uid 0), but by uid 1000! (This could e.g. happen if you try to connect to a non-root PulseAudio as a root user, over the native protocol. Don't do that.) No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-48-generic N/A linux-backports-modules-5.15.0-48-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 Tags: jammy Uname: Linux 5.15.0-48-generic x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False dmi.bios.date: 05/12/2022 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F36c dmi.board.asset.tag: Default string dmi.board.name: X570 AORUS ULTRA dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF36c:bd05/12/2022:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSULTRA:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSULTRA:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: X570 MB dmi.product.name: X570 AORUS ULTRA dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1993040/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1993040] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1993040/+attachment/5624569/+files/acpidump.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1993040 Title: After resuming from suspend, NIC has WOL disabled Status in linux package in Ubuntu: Incomplete Bug description: I have my NIC configured with WOL in magic packet mode: ``` $ sudo ethtool enp5s0 Settings for enp5s0: ... Supports Wake-on: pumbg Wake-on: g ``` However, every time I resume the system from suspend once, WOL becomes disabled: ``` $ sudo ethtool enp5s0 Settings for enp5s0: ... Supports Wake-on: pumbg Wake-on: d ``` I can re-enable it and it'll work fine. If I don't re-enable it, I am unable to use magic packet to WOL if I suspend the system again (as expected, since it gets disabled). This seems to be new behaviour with Jammy - I didn't experience this problem on Bionic with the same hardware. Driver info: ``` $ sudo ethtool -i enp5s0 driver: igb version: 5.15.0-48-generic firmware-version: 0. 6-1 expansion-rom-version: bus-info: :05:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes ``` --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-id', '/dev/snd/controlC3', '/dev/snd/pcmC3D0c', '/dev/snd/controlC2', '/dev/snd/hwC2D0', '/dev/snd/pcmC2D2c', '/dev/snd/pcmC2D1p', '/dev/snd/pcmC2D0c', '/dev/snd/pcmC2D0p', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D12p', '/dev/snd/pcmC0D11p', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: unknown DistroRelease: Ubuntu 22.04 MachineType: Gigabyte Technology Co., Ltd. X570 AORUS ULTRA NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=screen.xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/zsh ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-48-generic root=UUID=bf8ca071-393b-42bf-9259-3e4b410e9ad2 ro nvidia-drm.modeset=0 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: XDG_RUNTIME_DIR (/run/user/1000) is not owned by us (uid 0), but by uid 1000! (This could e.g. happen if you try to connect to a non-root PulseAudio as a root user, over the native protocol. Don't do that.) No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-48-generic N/A linux-backports-modules-5.15.0-48-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 Tags: jammy Uname: Linux 5.15.0-48-generic x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False dmi.bios.date: 05/12/2022 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F36c dmi.board.asset.tag: Default string dmi.board.name: X570 AORUS ULTRA dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF36c:bd05/12/2022:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSULTRA:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSULTRA:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: X570 MB dmi.product.name: X570 AORUS ULTRA dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1993040/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1993040] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1993040/+attachment/5624568/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1993040 Title: After resuming from suspend, NIC has WOL disabled Status in linux package in Ubuntu: Incomplete Bug description: I have my NIC configured with WOL in magic packet mode: ``` $ sudo ethtool enp5s0 Settings for enp5s0: ... Supports Wake-on: pumbg Wake-on: g ``` However, every time I resume the system from suspend once, WOL becomes disabled: ``` $ sudo ethtool enp5s0 Settings for enp5s0: ... Supports Wake-on: pumbg Wake-on: d ``` I can re-enable it and it'll work fine. If I don't re-enable it, I am unable to use magic packet to WOL if I suspend the system again (as expected, since it gets disabled). This seems to be new behaviour with Jammy - I didn't experience this problem on Bionic with the same hardware. Driver info: ``` $ sudo ethtool -i enp5s0 driver: igb version: 5.15.0-48-generic firmware-version: 0. 6-1 expansion-rom-version: bus-info: :05:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes ``` --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-id', '/dev/snd/controlC3', '/dev/snd/pcmC3D0c', '/dev/snd/controlC2', '/dev/snd/hwC2D0', '/dev/snd/pcmC2D2c', '/dev/snd/pcmC2D1p', '/dev/snd/pcmC2D0c', '/dev/snd/pcmC2D0p', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D12p', '/dev/snd/pcmC0D11p', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: unknown DistroRelease: Ubuntu 22.04 MachineType: Gigabyte Technology Co., Ltd. X570 AORUS ULTRA NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=screen.xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/zsh ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-48-generic root=UUID=bf8ca071-393b-42bf-9259-3e4b410e9ad2 ro nvidia-drm.modeset=0 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: XDG_RUNTIME_DIR (/run/user/1000) is not owned by us (uid 0), but by uid 1000! (This could e.g. happen if you try to connect to a non-root PulseAudio as a root user, over the native protocol. Don't do that.) No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-48-generic N/A linux-backports-modules-5.15.0-48-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 Tags: jammy Uname: Linux 5.15.0-48-generic x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False dmi.bios.date: 05/12/2022 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F36c dmi.board.asset.tag: Default string dmi.board.name: X570 AORUS ULTRA dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF36c:bd05/12/2022:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSULTRA:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSULTRA:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: X570 MB dmi.product.name: X570 AORUS ULTRA dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1993040/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1993040] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1993040/+attachment/5624567/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1993040 Title: After resuming from suspend, NIC has WOL disabled Status in linux package in Ubuntu: Incomplete Bug description: I have my NIC configured with WOL in magic packet mode: ``` $ sudo ethtool enp5s0 Settings for enp5s0: ... Supports Wake-on: pumbg Wake-on: g ``` However, every time I resume the system from suspend once, WOL becomes disabled: ``` $ sudo ethtool enp5s0 Settings for enp5s0: ... Supports Wake-on: pumbg Wake-on: d ``` I can re-enable it and it'll work fine. If I don't re-enable it, I am unable to use magic packet to WOL if I suspend the system again (as expected, since it gets disabled). This seems to be new behaviour with Jammy - I didn't experience this problem on Bionic with the same hardware. Driver info: ``` $ sudo ethtool -i enp5s0 driver: igb version: 5.15.0-48-generic firmware-version: 0. 6-1 expansion-rom-version: bus-info: :05:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes ``` --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-id', '/dev/snd/controlC3', '/dev/snd/pcmC3D0c', '/dev/snd/controlC2', '/dev/snd/hwC2D0', '/dev/snd/pcmC2D2c', '/dev/snd/pcmC2D1p', '/dev/snd/pcmC2D0c', '/dev/snd/pcmC2D0p', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D12p', '/dev/snd/pcmC0D11p', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: unknown DistroRelease: Ubuntu 22.04 MachineType: Gigabyte Technology Co., Ltd. X570 AORUS ULTRA NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=screen.xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/zsh ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-48-generic root=UUID=bf8ca071-393b-42bf-9259-3e4b410e9ad2 ro nvidia-drm.modeset=0 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: XDG_RUNTIME_DIR (/run/user/1000) is not owned by us (uid 0), but by uid 1000! (This could e.g. happen if you try to connect to a non-root PulseAudio as a root user, over the native protocol. Don't do that.) No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-48-generic N/A linux-backports-modules-5.15.0-48-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 Tags: jammy Uname: Linux 5.15.0-48-generic x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False dmi.bios.date: 05/12/2022 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F36c dmi.board.asset.tag: Default string dmi.board.name: X570 AORUS ULTRA dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF36c:bd05/12/2022:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSULTRA:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSULTRA:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: X570 MB dmi.product.name: X570 AORUS ULTRA dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1993040/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1993040] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1993040/+attachment/5624563/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1993040 Title: After resuming from suspend, NIC has WOL disabled Status in linux package in Ubuntu: Incomplete Bug description: I have my NIC configured with WOL in magic packet mode: ``` $ sudo ethtool enp5s0 Settings for enp5s0: ... Supports Wake-on: pumbg Wake-on: g ``` However, every time I resume the system from suspend once, WOL becomes disabled: ``` $ sudo ethtool enp5s0 Settings for enp5s0: ... Supports Wake-on: pumbg Wake-on: d ``` I can re-enable it and it'll work fine. If I don't re-enable it, I am unable to use magic packet to WOL if I suspend the system again (as expected, since it gets disabled). This seems to be new behaviour with Jammy - I didn't experience this problem on Bionic with the same hardware. Driver info: ``` $ sudo ethtool -i enp5s0 driver: igb version: 5.15.0-48-generic firmware-version: 0. 6-1 expansion-rom-version: bus-info: :05:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes ``` --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-id', '/dev/snd/controlC3', '/dev/snd/pcmC3D0c', '/dev/snd/controlC2', '/dev/snd/hwC2D0', '/dev/snd/pcmC2D2c', '/dev/snd/pcmC2D1p', '/dev/snd/pcmC2D0c', '/dev/snd/pcmC2D0p', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D12p', '/dev/snd/pcmC0D11p', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: unknown DistroRelease: Ubuntu 22.04 MachineType: Gigabyte Technology Co., Ltd. X570 AORUS ULTRA NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=screen.xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/zsh ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-48-generic root=UUID=bf8ca071-393b-42bf-9259-3e4b410e9ad2 ro nvidia-drm.modeset=0 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: XDG_RUNTIME_DIR (/run/user/1000) is not owned by us (uid 0), but by uid 1000! (This could e.g. happen if you try to connect to a non-root PulseAudio as a root user, over the native protocol. Don't do that.) No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-48-generic N/A linux-backports-modules-5.15.0-48-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 Tags: jammy Uname: Linux 5.15.0-48-generic x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False dmi.bios.date: 05/12/2022 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F36c dmi.board.asset.tag: Default string dmi.board.name: X570 AORUS ULTRA dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF36c:bd05/12/2022:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSULTRA:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSULTRA:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: X570 MB dmi.product.name: X570 AORUS ULTRA dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1993040/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1993040] PaInfo.txt
apport information ** Attachment added: "PaInfo.txt" https://bugs.launchpad.net/bugs/1993040/+attachment/5624562/+files/PaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1993040 Title: After resuming from suspend, NIC has WOL disabled Status in linux package in Ubuntu: Incomplete Bug description: I have my NIC configured with WOL in magic packet mode: ``` $ sudo ethtool enp5s0 Settings for enp5s0: ... Supports Wake-on: pumbg Wake-on: g ``` However, every time I resume the system from suspend once, WOL becomes disabled: ``` $ sudo ethtool enp5s0 Settings for enp5s0: ... Supports Wake-on: pumbg Wake-on: d ``` I can re-enable it and it'll work fine. If I don't re-enable it, I am unable to use magic packet to WOL if I suspend the system again (as expected, since it gets disabled). This seems to be new behaviour with Jammy - I didn't experience this problem on Bionic with the same hardware. Driver info: ``` $ sudo ethtool -i enp5s0 driver: igb version: 5.15.0-48-generic firmware-version: 0. 6-1 expansion-rom-version: bus-info: :05:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes ``` --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-id', '/dev/snd/controlC3', '/dev/snd/pcmC3D0c', '/dev/snd/controlC2', '/dev/snd/hwC2D0', '/dev/snd/pcmC2D2c', '/dev/snd/pcmC2D1p', '/dev/snd/pcmC2D0c', '/dev/snd/pcmC2D0p', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D12p', '/dev/snd/pcmC0D11p', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: unknown DistroRelease: Ubuntu 22.04 MachineType: Gigabyte Technology Co., Ltd. X570 AORUS ULTRA NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=screen.xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/zsh ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-48-generic root=UUID=bf8ca071-393b-42bf-9259-3e4b410e9ad2 ro nvidia-drm.modeset=0 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: XDG_RUNTIME_DIR (/run/user/1000) is not owned by us (uid 0), but by uid 1000! (This could e.g. happen if you try to connect to a non-root PulseAudio as a root user, over the native protocol. Don't do that.) No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-48-generic N/A linux-backports-modules-5.15.0-48-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 Tags: jammy Uname: Linux 5.15.0-48-generic x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False dmi.bios.date: 05/12/2022 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F36c dmi.board.asset.tag: Default string dmi.board.name: X570 AORUS ULTRA dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF36c:bd05/12/2022:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSULTRA:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSULTRA:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: X570 MB dmi.product.name: X570 AORUS ULTRA dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1993040/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1993040] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1993040/+attachment/5624561/+files/Lsusb-v.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1993040 Title: After resuming from suspend, NIC has WOL disabled Status in linux package in Ubuntu: Incomplete Bug description: I have my NIC configured with WOL in magic packet mode: ``` $ sudo ethtool enp5s0 Settings for enp5s0: ... Supports Wake-on: pumbg Wake-on: g ``` However, every time I resume the system from suspend once, WOL becomes disabled: ``` $ sudo ethtool enp5s0 Settings for enp5s0: ... Supports Wake-on: pumbg Wake-on: d ``` I can re-enable it and it'll work fine. If I don't re-enable it, I am unable to use magic packet to WOL if I suspend the system again (as expected, since it gets disabled). This seems to be new behaviour with Jammy - I didn't experience this problem on Bionic with the same hardware. Driver info: ``` $ sudo ethtool -i enp5s0 driver: igb version: 5.15.0-48-generic firmware-version: 0. 6-1 expansion-rom-version: bus-info: :05:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes ``` --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-id', '/dev/snd/controlC3', '/dev/snd/pcmC3D0c', '/dev/snd/controlC2', '/dev/snd/hwC2D0', '/dev/snd/pcmC2D2c', '/dev/snd/pcmC2D1p', '/dev/snd/pcmC2D0c', '/dev/snd/pcmC2D0p', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D12p', '/dev/snd/pcmC0D11p', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: unknown DistroRelease: Ubuntu 22.04 MachineType: Gigabyte Technology Co., Ltd. X570 AORUS ULTRA NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=screen.xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/zsh ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-48-generic root=UUID=bf8ca071-393b-42bf-9259-3e4b410e9ad2 ro nvidia-drm.modeset=0 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: XDG_RUNTIME_DIR (/run/user/1000) is not owned by us (uid 0), but by uid 1000! (This could e.g. happen if you try to connect to a non-root PulseAudio as a root user, over the native protocol. Don't do that.) No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-48-generic N/A linux-backports-modules-5.15.0-48-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 Tags: jammy Uname: Linux 5.15.0-48-generic x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False dmi.bios.date: 05/12/2022 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F36c dmi.board.asset.tag: Default string dmi.board.name: X570 AORUS ULTRA dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF36c:bd05/12/2022:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSULTRA:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSULTRA:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: X570 MB dmi.product.name: X570 AORUS ULTRA dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1993040/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1993040] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1993040/+attachment/5624559/+files/Lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1993040 Title: After resuming from suspend, NIC has WOL disabled Status in linux package in Ubuntu: Incomplete Bug description: I have my NIC configured with WOL in magic packet mode: ``` $ sudo ethtool enp5s0 Settings for enp5s0: ... Supports Wake-on: pumbg Wake-on: g ``` However, every time I resume the system from suspend once, WOL becomes disabled: ``` $ sudo ethtool enp5s0 Settings for enp5s0: ... Supports Wake-on: pumbg Wake-on: d ``` I can re-enable it and it'll work fine. If I don't re-enable it, I am unable to use magic packet to WOL if I suspend the system again (as expected, since it gets disabled). This seems to be new behaviour with Jammy - I didn't experience this problem on Bionic with the same hardware. Driver info: ``` $ sudo ethtool -i enp5s0 driver: igb version: 5.15.0-48-generic firmware-version: 0. 6-1 expansion-rom-version: bus-info: :05:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes ``` --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-id', '/dev/snd/controlC3', '/dev/snd/pcmC3D0c', '/dev/snd/controlC2', '/dev/snd/hwC2D0', '/dev/snd/pcmC2D2c', '/dev/snd/pcmC2D1p', '/dev/snd/pcmC2D0c', '/dev/snd/pcmC2D0p', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D12p', '/dev/snd/pcmC0D11p', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: unknown DistroRelease: Ubuntu 22.04 MachineType: Gigabyte Technology Co., Ltd. X570 AORUS ULTRA NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=screen.xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/zsh ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-48-generic root=UUID=bf8ca071-393b-42bf-9259-3e4b410e9ad2 ro nvidia-drm.modeset=0 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: XDG_RUNTIME_DIR (/run/user/1000) is not owned by us (uid 0), but by uid 1000! (This could e.g. happen if you try to connect to a non-root PulseAudio as a root user, over the native protocol. Don't do that.) No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-48-generic N/A linux-backports-modules-5.15.0-48-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 Tags: jammy Uname: Linux 5.15.0-48-generic x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False dmi.bios.date: 05/12/2022 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F36c dmi.board.asset.tag: Default string dmi.board.name: X570 AORUS ULTRA dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF36c:bd05/12/2022:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSULTRA:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSULTRA:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: X570 MB dmi.product.name: X570 AORUS ULTRA dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1993040/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1993040] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1993040/+attachment/5624557/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1993040 Title: After resuming from suspend, NIC has WOL disabled Status in linux package in Ubuntu: Incomplete Bug description: I have my NIC configured with WOL in magic packet mode: ``` $ sudo ethtool enp5s0 Settings for enp5s0: ... Supports Wake-on: pumbg Wake-on: g ``` However, every time I resume the system from suspend once, WOL becomes disabled: ``` $ sudo ethtool enp5s0 Settings for enp5s0: ... Supports Wake-on: pumbg Wake-on: d ``` I can re-enable it and it'll work fine. If I don't re-enable it, I am unable to use magic packet to WOL if I suspend the system again (as expected, since it gets disabled). This seems to be new behaviour with Jammy - I didn't experience this problem on Bionic with the same hardware. Driver info: ``` $ sudo ethtool -i enp5s0 driver: igb version: 5.15.0-48-generic firmware-version: 0. 6-1 expansion-rom-version: bus-info: :05:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes ``` --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-id', '/dev/snd/controlC3', '/dev/snd/pcmC3D0c', '/dev/snd/controlC2', '/dev/snd/hwC2D0', '/dev/snd/pcmC2D2c', '/dev/snd/pcmC2D1p', '/dev/snd/pcmC2D0c', '/dev/snd/pcmC2D0p', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D12p', '/dev/snd/pcmC0D11p', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: unknown DistroRelease: Ubuntu 22.04 MachineType: Gigabyte Technology Co., Ltd. X570 AORUS ULTRA NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=screen.xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/zsh ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-48-generic root=UUID=bf8ca071-393b-42bf-9259-3e4b410e9ad2 ro nvidia-drm.modeset=0 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: XDG_RUNTIME_DIR (/run/user/1000) is not owned by us (uid 0), but by uid 1000! (This could e.g. happen if you try to connect to a non-root PulseAudio as a root user, over the native protocol. Don't do that.) No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-48-generic N/A linux-backports-modules-5.15.0-48-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 Tags: jammy Uname: Linux 5.15.0-48-generic x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False dmi.bios.date: 05/12/2022 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F36c dmi.board.asset.tag: Default string dmi.board.name: X570 AORUS ULTRA dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF36c:bd05/12/2022:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSULTRA:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSULTRA:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: X570 MB dmi.product.name: X570 AORUS ULTRA dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1993040/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1993040] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1993040/+attachment/5624558/+files/Lspci-vt.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1993040 Title: After resuming from suspend, NIC has WOL disabled Status in linux package in Ubuntu: Incomplete Bug description: I have my NIC configured with WOL in magic packet mode: ``` $ sudo ethtool enp5s0 Settings for enp5s0: ... Supports Wake-on: pumbg Wake-on: g ``` However, every time I resume the system from suspend once, WOL becomes disabled: ``` $ sudo ethtool enp5s0 Settings for enp5s0: ... Supports Wake-on: pumbg Wake-on: d ``` I can re-enable it and it'll work fine. If I don't re-enable it, I am unable to use magic packet to WOL if I suspend the system again (as expected, since it gets disabled). This seems to be new behaviour with Jammy - I didn't experience this problem on Bionic with the same hardware. Driver info: ``` $ sudo ethtool -i enp5s0 driver: igb version: 5.15.0-48-generic firmware-version: 0. 6-1 expansion-rom-version: bus-info: :05:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes ``` --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-id', '/dev/snd/controlC3', '/dev/snd/pcmC3D0c', '/dev/snd/controlC2', '/dev/snd/hwC2D0', '/dev/snd/pcmC2D2c', '/dev/snd/pcmC2D1p', '/dev/snd/pcmC2D0c', '/dev/snd/pcmC2D0p', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D12p', '/dev/snd/pcmC0D11p', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: unknown DistroRelease: Ubuntu 22.04 MachineType: Gigabyte Technology Co., Ltd. X570 AORUS ULTRA NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=screen.xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/zsh ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-48-generic root=UUID=bf8ca071-393b-42bf-9259-3e4b410e9ad2 ro nvidia-drm.modeset=0 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: XDG_RUNTIME_DIR (/run/user/1000) is not owned by us (uid 0), but by uid 1000! (This could e.g. happen if you try to connect to a non-root PulseAudio as a root user, over the native protocol. Don't do that.) No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-48-generic N/A linux-backports-modules-5.15.0-48-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 Tags: jammy Uname: Linux 5.15.0-48-generic x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False dmi.bios.date: 05/12/2022 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F36c dmi.board.asset.tag: Default string dmi.board.name: X570 AORUS ULTRA dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF36c:bd05/12/2022:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSULTRA:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSULTRA:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: X570 MB dmi.product.name: X570 AORUS ULTRA dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1993040/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1993040] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1993040/+attachment/5624560/+files/Lsusb-t.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1993040 Title: After resuming from suspend, NIC has WOL disabled Status in linux package in Ubuntu: Incomplete Bug description: I have my NIC configured with WOL in magic packet mode: ``` $ sudo ethtool enp5s0 Settings for enp5s0: ... Supports Wake-on: pumbg Wake-on: g ``` However, every time I resume the system from suspend once, WOL becomes disabled: ``` $ sudo ethtool enp5s0 Settings for enp5s0: ... Supports Wake-on: pumbg Wake-on: d ``` I can re-enable it and it'll work fine. If I don't re-enable it, I am unable to use magic packet to WOL if I suspend the system again (as expected, since it gets disabled). This seems to be new behaviour with Jammy - I didn't experience this problem on Bionic with the same hardware. Driver info: ``` $ sudo ethtool -i enp5s0 driver: igb version: 5.15.0-48-generic firmware-version: 0. 6-1 expansion-rom-version: bus-info: :05:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes ``` --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-id', '/dev/snd/controlC3', '/dev/snd/pcmC3D0c', '/dev/snd/controlC2', '/dev/snd/hwC2D0', '/dev/snd/pcmC2D2c', '/dev/snd/pcmC2D1p', '/dev/snd/pcmC2D0c', '/dev/snd/pcmC2D0p', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D12p', '/dev/snd/pcmC0D11p', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: unknown DistroRelease: Ubuntu 22.04 MachineType: Gigabyte Technology Co., Ltd. X570 AORUS ULTRA NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=screen.xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/zsh ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-48-generic root=UUID=bf8ca071-393b-42bf-9259-3e4b410e9ad2 ro nvidia-drm.modeset=0 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: XDG_RUNTIME_DIR (/run/user/1000) is not owned by us (uid 0), but by uid 1000! (This could e.g. happen if you try to connect to a non-root PulseAudio as a root user, over the native protocol. Don't do that.) No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-48-generic N/A linux-backports-modules-5.15.0-48-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 Tags: jammy Uname: Linux 5.15.0-48-generic x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False dmi.bios.date: 05/12/2022 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F36c dmi.board.asset.tag: Default string dmi.board.name: X570 AORUS ULTRA dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF36c:bd05/12/2022:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSULTRA:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSULTRA:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: X570 MB dmi.product.name: X570 AORUS ULTRA dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1993040/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1993040] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1993040/+attachment/5624555/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1993040 Title: After resuming from suspend, NIC has WOL disabled Status in linux package in Ubuntu: Incomplete Bug description: I have my NIC configured with WOL in magic packet mode: ``` $ sudo ethtool enp5s0 Settings for enp5s0: ... Supports Wake-on: pumbg Wake-on: g ``` However, every time I resume the system from suspend once, WOL becomes disabled: ``` $ sudo ethtool enp5s0 Settings for enp5s0: ... Supports Wake-on: pumbg Wake-on: d ``` I can re-enable it and it'll work fine. If I don't re-enable it, I am unable to use magic packet to WOL if I suspend the system again (as expected, since it gets disabled). This seems to be new behaviour with Jammy - I didn't experience this problem on Bionic with the same hardware. Driver info: ``` $ sudo ethtool -i enp5s0 driver: igb version: 5.15.0-48-generic firmware-version: 0. 6-1 expansion-rom-version: bus-info: :05:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes ``` --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-id', '/dev/snd/controlC3', '/dev/snd/pcmC3D0c', '/dev/snd/controlC2', '/dev/snd/hwC2D0', '/dev/snd/pcmC2D2c', '/dev/snd/pcmC2D1p', '/dev/snd/pcmC2D0c', '/dev/snd/pcmC2D0p', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D12p', '/dev/snd/pcmC0D11p', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: unknown DistroRelease: Ubuntu 22.04 MachineType: Gigabyte Technology Co., Ltd. X570 AORUS ULTRA NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=screen.xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/zsh ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-48-generic root=UUID=bf8ca071-393b-42bf-9259-3e4b410e9ad2 ro nvidia-drm.modeset=0 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: XDG_RUNTIME_DIR (/run/user/1000) is not owned by us (uid 0), but by uid 1000! (This could e.g. happen if you try to connect to a non-root PulseAudio as a root user, over the native protocol. Don't do that.) No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-48-generic N/A linux-backports-modules-5.15.0-48-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 Tags: jammy Uname: Linux 5.15.0-48-generic x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False dmi.bios.date: 05/12/2022 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F36c dmi.board.asset.tag: Default string dmi.board.name: X570 AORUS ULTRA dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF36c:bd05/12/2022:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSULTRA:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSULTRA:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: X570 MB dmi.product.name: X570 AORUS ULTRA dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1993040/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1993040] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1993040/+attachment/5624556/+files/IwConfig.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1993040 Title: After resuming from suspend, NIC has WOL disabled Status in linux package in Ubuntu: Incomplete Bug description: I have my NIC configured with WOL in magic packet mode: ``` $ sudo ethtool enp5s0 Settings for enp5s0: ... Supports Wake-on: pumbg Wake-on: g ``` However, every time I resume the system from suspend once, WOL becomes disabled: ``` $ sudo ethtool enp5s0 Settings for enp5s0: ... Supports Wake-on: pumbg Wake-on: d ``` I can re-enable it and it'll work fine. If I don't re-enable it, I am unable to use magic packet to WOL if I suspend the system again (as expected, since it gets disabled). This seems to be new behaviour with Jammy - I didn't experience this problem on Bionic with the same hardware. Driver info: ``` $ sudo ethtool -i enp5s0 driver: igb version: 5.15.0-48-generic firmware-version: 0. 6-1 expansion-rom-version: bus-info: :05:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes ``` --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-id', '/dev/snd/controlC3', '/dev/snd/pcmC3D0c', '/dev/snd/controlC2', '/dev/snd/hwC2D0', '/dev/snd/pcmC2D2c', '/dev/snd/pcmC2D1p', '/dev/snd/pcmC2D0c', '/dev/snd/pcmC2D0p', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D12p', '/dev/snd/pcmC0D11p', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: unknown DistroRelease: Ubuntu 22.04 MachineType: Gigabyte Technology Co., Ltd. X570 AORUS ULTRA NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=screen.xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/zsh ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-48-generic root=UUID=bf8ca071-393b-42bf-9259-3e4b410e9ad2 ro nvidia-drm.modeset=0 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: XDG_RUNTIME_DIR (/run/user/1000) is not owned by us (uid 0), but by uid 1000! (This could e.g. happen if you try to connect to a non-root PulseAudio as a root user, over the native protocol. Don't do that.) No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-48-generic N/A linux-backports-modules-5.15.0-48-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 Tags: jammy Uname: Linux 5.15.0-48-generic x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False dmi.bios.date: 05/12/2022 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F36c dmi.board.asset.tag: Default string dmi.board.name: X570 AORUS ULTRA dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF36c:bd05/12/2022:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSULTRA:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSULTRA:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: X570 MB dmi.product.name: X570 AORUS ULTRA dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1993040/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1993040] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1993040/+attachment/5624554/+files/CRDA.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1993040 Title: After resuming from suspend, NIC has WOL disabled Status in linux package in Ubuntu: Incomplete Bug description: I have my NIC configured with WOL in magic packet mode: ``` $ sudo ethtool enp5s0 Settings for enp5s0: ... Supports Wake-on: pumbg Wake-on: g ``` However, every time I resume the system from suspend once, WOL becomes disabled: ``` $ sudo ethtool enp5s0 Settings for enp5s0: ... Supports Wake-on: pumbg Wake-on: d ``` I can re-enable it and it'll work fine. If I don't re-enable it, I am unable to use magic packet to WOL if I suspend the system again (as expected, since it gets disabled). This seems to be new behaviour with Jammy - I didn't experience this problem on Bionic with the same hardware. Driver info: ``` $ sudo ethtool -i enp5s0 driver: igb version: 5.15.0-48-generic firmware-version: 0. 6-1 expansion-rom-version: bus-info: :05:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes ``` --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-id', '/dev/snd/controlC3', '/dev/snd/pcmC3D0c', '/dev/snd/controlC2', '/dev/snd/hwC2D0', '/dev/snd/pcmC2D2c', '/dev/snd/pcmC2D1p', '/dev/snd/pcmC2D0c', '/dev/snd/pcmC2D0p', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D12p', '/dev/snd/pcmC0D11p', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: unknown DistroRelease: Ubuntu 22.04 MachineType: Gigabyte Technology Co., Ltd. X570 AORUS ULTRA NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=screen.xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/zsh ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-48-generic root=UUID=bf8ca071-393b-42bf-9259-3e4b410e9ad2 ro nvidia-drm.modeset=0 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: XDG_RUNTIME_DIR (/run/user/1000) is not owned by us (uid 0), but by uid 1000! (This could e.g. happen if you try to connect to a non-root PulseAudio as a root user, over the native protocol. Don't do that.) No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-48-generic N/A linux-backports-modules-5.15.0-48-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 Tags: jammy Uname: Linux 5.15.0-48-generic x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False dmi.bios.date: 05/12/2022 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F36c dmi.board.asset.tag: Default string dmi.board.name: X570 AORUS ULTRA dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF36c:bd05/12/2022:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSULTRA:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSULTRA:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: X570 MB dmi.product.name: X570 AORUS ULTRA dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1993040/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1993040] Re: After resuming from suspend, NIC has WOL disabled
apport information ** Tags added: apport-collected jammy ** Description changed: I have my NIC configured with WOL in magic packet mode: ``` $ sudo ethtool enp5s0 Settings for enp5s0: ... Supports Wake-on: pumbg Wake-on: g ``` However, every time I resume the system from suspend once, WOL becomes disabled: ``` $ sudo ethtool enp5s0 Settings for enp5s0: ... Supports Wake-on: pumbg Wake-on: d ``` I can re-enable it and it'll work fine. If I don't re-enable it, I am unable to use magic packet to WOL if I suspend the system again (as expected, since it gets disabled). This seems to be new behaviour with Jammy - I didn't experience this problem on Bionic with the same hardware. Driver info: ``` $ sudo ethtool -i enp5s0 driver: igb version: 5.15.0-48-generic firmware-version: 0. 6-1 expansion-rom-version: bus-info: :05:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes ``` + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu82.1 + Architecture: amd64 + AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-id', '/dev/snd/controlC3', '/dev/snd/pcmC3D0c', '/dev/snd/controlC2', '/dev/snd/hwC2D0', '/dev/snd/pcmC2D2c', '/dev/snd/pcmC2D1p', '/dev/snd/pcmC2D0c', '/dev/snd/pcmC2D0p', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D12p', '/dev/snd/pcmC0D11p', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: + CasperMD5CheckResult: unknown + DistroRelease: Ubuntu 22.04 + MachineType: Gigabyte Technology Co., Ltd. X570 AORUS ULTRA + NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia + Package: linux (not installed) + ProcEnviron: + TERM=screen.xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/usr/bin/zsh + ProcFB: 0 EFI VGA + ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-48-generic root=UUID=bf8ca071-393b-42bf-9259-3e4b410e9ad2 ro nvidia-drm.modeset=0 quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 + PulseList: + Error: command ['pacmd', 'list'] failed with exit code 1: XDG_RUNTIME_DIR (/run/user/1000) is not owned by us (uid 0), but by uid 1000! (This could e.g. happen if you try to connect to a non-root PulseAudio as a root user, over the native protocol. Don't do that.) + No PulseAudio daemon running, or not running as session daemon. + RelatedPackageVersions: + linux-restricted-modules-5.15.0-48-generic N/A + linux-backports-modules-5.15.0-48-generic N/A + linux-firmware 20220329.git681281e4-0ubuntu3.5 + Tags: jammy + Uname: Linux 5.15.0-48-generic x86_64 + UnreportableReason: This report is about a package that is not installed. + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: N/A + _MarkForUpload: False + dmi.bios.date: 05/12/2022 + dmi.bios.release: 5.17 + dmi.bios.vendor: American Megatrends International, LLC. + dmi.bios.version: F36c + dmi.board.asset.tag: Default string + dmi.board.name: X570 AORUS ULTRA + dmi.board.vendor: Gigabyte Technology Co., Ltd. + dmi.board.version: x.x + dmi.chassis.asset.tag: Default string + dmi.chassis.type: 3 + dmi.chassis.vendor: Default string + dmi.chassis.version: Default string + dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF36c:bd05/12/2022:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSULTRA:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSULTRA:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: + dmi.product.family: X570 MB + dmi.product.name: X570 AORUS ULTRA + dmi.product.sku: Default string + dmi.product.version: -CF + dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1993040/+attachment/5624553/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1993040 Title: After resuming from suspend, NIC has WOL disabled Status in linux package in Ubuntu: Incomplete Bug description: I have my NIC configured with WOL in magic packet mode: ``` $ sudo ethtool enp5s0 Settings for enp5s0: ... Supports Wake-on: pumbg Wake-on: g ``` However, every time I resume the system from suspend once, WOL becomes disabled: ``` $ sudo ethtool enp5s0 Settings for enp5s0: ... Supports Wake-on: pumbg Wake-on: d ``` I can re-enable it and it'll work fine. If I don't re-enable it, I am unable to use magic packet to WOL if I suspend the system again (as expected, since it gets disabled). This seems to be new behaviour with Jammy - I didn't experience
[Kernel-packages] [Bug 1993040] Re: After resuming from suspend, NIC has WOL disabled
** Project changed: launchpad => 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/1993040 Title: After resuming from suspend, NIC has WOL disabled Status in linux package in Ubuntu: New Bug description: I have my NIC configured with WOL in magic packet mode: ``` $ sudo ethtool enp5s0 Settings for enp5s0: ... Supports Wake-on: pumbg Wake-on: g ``` However, every time I resume the system from suspend once, WOL becomes disabled: ``` $ sudo ethtool enp5s0 Settings for enp5s0: ... Supports Wake-on: pumbg Wake-on: d ``` I can re-enable it and it'll work fine. If I don't re-enable it, I am unable to use magic packet to WOL if I suspend the system again (as expected, since it gets disabled). This seems to be new behaviour with Jammy - I didn't experience this problem on Bionic with the same hardware. Driver info: ``` $ sudo ethtool -i enp5s0 driver: igb version: 5.15.0-48-generic firmware-version: 0. 6-1 expansion-rom-version: bus-info: :05:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1993040/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1983404] Re: e1000e on Alder Lake does not resume successfully
This may be the missing patch. Willing the try a build with it at least.
commit b49feacbeffc7635cc6692cbcc6a1eae2c17da6f
Author: Sasha Neftin
Date: Sun May 8 10:09:05 2022 +0300
e1000e: Enable GPT clock before sending message to CSME
On corporate (CSME) ADL systems, the Ethernet Controller may stop working
("HW unit hang") after exiting from the s0ix state. The reason is that
CSME misses the message sent by the host. Enabling the dynamic GPT clock
solves this problem. This clock is cleared upon HW initialization.
Fixes: 3e55d231716e ("e1000e: Add handshake with the CSME to support S0ix")
Bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=214821
Reviewed-by: Dima Ruinskiy
Signed-off-by: Sasha Neftin
Tested-by: Chia-Lin Kao (AceLan)
Tested-by: Naama Meir
Signed-off-by: Tony Nguyen
--
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/1983404
Title:
e1000e on Alder Lake does not resume successfully
Status in linux package in Ubuntu:
New
Bug description:
This is a Dell Precision 3460 workstation (Alder Lake CPU) with latest
BIOS and Intel AMT turned off in the BIOS.
When enabling the Power -> 'Automatic Suspend' setting the e1000e
wired ethernet is always broken on wake up. rmmoding and modprobing
the e1000e driver will eventually heal it.
On resume the kernel logs:
Aug 01 14:41:01 wakko kernel: e1000e :00:1f.6 enp0s31f6: NIC Link is Down
Aug 01 14:41:01 wakko kernel: ata8: SATA link down (SStatus 4 SControl 300)
Aug 01 14:41:01 wakko kernel: ata5: SATA link down (SStatus 4 SControl 300)
Aug 01 14:41:01 wakko kernel: ata7: SATA link down (SStatus 4 SControl 300)
Aug 01 14:41:01 wakko kernel: ata6: SATA link down (SStatus 4 SControl 300)
Aug 01 14:41:05 wakko kernel: e1000e :00:1f.6 enp0s31f6: Error reading
PHY register
Aug 01 14:41:05 wakko kernel: e1000e :00:1f.6 enp0s31f6: NIC Link is Up
1000 Mbps Full Duplex, Flow Control: Rx/Tx
Aug 01 14:41:05 wakko kernel: IPv6: ADDRCONF(NETDEV_CHANGE): enp0s31f6: link
becomes ready
Aug 01 14:41:05 wakko kernel: kauditd_printk_skb: 15 callbacks suppressed
Aug 01 14:41:08 wakko kernel: e1000e :00:1f.6 enp0s31f6: Detected
Hardware Unit Hang:
TDH <1>
TDT <5>
next_to_use <5>
next_to_clean<1>
buffer_info[next_to_clean]:
time_stamp <10017d3a0>
next_to_watch<1>
jiffies <10017d680>
next_to_watch.status <0>
MAC Status <40080283>
PHY Status <796d>
PHY 1000BASE-T Status <3800>
PHY Extended Status<3000>
PCI Status <10>
And then it just loops repeatedly resetting and failing the adaptor.
I see some upstream chatter on this but the most likely fix from
commit 1866aa0d0d64 ("e1000e: Fix possible HW unit hang after an s0ix
exit") is already in this ubuntu kernel.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-5.15.0-43-generic 5.15.0-43.46
ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39
Uname: Linux 5.15.0-43-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: jgg2250 F pulseaudio
/dev/snd/pcmC0D3p: jgg2250 F...m pulseaudio
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Aug 2 14:37:16 2022
InstallationDate: Installed on 2022-06-25 (38 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64
(20220419)
MachineType: Dell Inc. Precision 3460
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-43-generic
root=UUID=4734cc66-fe16-4d2f-ba78-727597040f9a ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-5.15.0-43-generic N/A
linux-backports-modules-5.15.0-43-generic N/A
linux-firmware 20220329.git681281e4-0ubuntu3.3
RfKill:
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/21/2022
dmi.bios.release: 1.3
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.3.72
dmi.board.name: 08WXMX
dmi.board.vendor: Dell Inc.
dmi.board.version: A01
dmi.chassis.type: 3
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr1.3.72:bd06/21/2022:br1.3:svnDellInc.:pnPrecision3460:pvr:rvnDellInc.:r
[Kernel-packages] [Bug 1983404] [NEW] e1000e on Alder Lake does not resume successfully
Public bug reported:
This is a Dell Precision 3460 workstation (Alder Lake CPU) with latest
BIOS and Intel AMT turned off in the BIOS.
When enabling the Power -> 'Automatic Suspend' setting the e1000e wired
ethernet is always broken on wake up. rmmoding and modprobing the e1000e
driver will eventually heal it.
On resume the kernel logs:
Aug 01 14:41:01 wakko kernel: e1000e :00:1f.6 enp0s31f6: NIC Link is Down
Aug 01 14:41:01 wakko kernel: ata8: SATA link down (SStatus 4 SControl 300)
Aug 01 14:41:01 wakko kernel: ata5: SATA link down (SStatus 4 SControl 300)
Aug 01 14:41:01 wakko kernel: ata7: SATA link down (SStatus 4 SControl 300)
Aug 01 14:41:01 wakko kernel: ata6: SATA link down (SStatus 4 SControl 300)
Aug 01 14:41:05 wakko kernel: e1000e :00:1f.6 enp0s31f6: Error reading PHY
register
Aug 01 14:41:05 wakko kernel: e1000e :00:1f.6 enp0s31f6: NIC Link is Up
1000 Mbps Full Duplex, Flow Control: Rx/Tx
Aug 01 14:41:05 wakko kernel: IPv6: ADDRCONF(NETDEV_CHANGE): enp0s31f6: link
becomes ready
Aug 01 14:41:05 wakko kernel: kauditd_printk_skb: 15 callbacks suppressed
Aug 01 14:41:08 wakko kernel: e1000e :00:1f.6 enp0s31f6: Detected Hardware
Unit Hang:
TDH <1>
TDT <5>
next_to_use <5>
next_to_clean<1>
buffer_info[next_to_clean]:
time_stamp <10017d3a0>
next_to_watch<1>
jiffies <10017d680>
next_to_watch.status <0>
MAC Status <40080283>
PHY Status <796d>
PHY 1000BASE-T Status <3800>
PHY Extended Status<3000>
PCI Status <10>
And then it just loops repeatedly resetting and failing the adaptor.
I see some upstream chatter on this but the most likely fix from commit
1866aa0d0d64 ("e1000e: Fix possible HW unit hang after an s0ix exit") is
already in this ubuntu kernel.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-5.15.0-43-generic 5.15.0-43.46
ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39
Uname: Linux 5.15.0-43-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: jgg2250 F pulseaudio
/dev/snd/pcmC0D3p: jgg2250 F...m pulseaudio
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Aug 2 14:37:16 2022
InstallationDate: Installed on 2022-06-25 (38 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
MachineType: Dell Inc. Precision 3460
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-43-generic
root=UUID=4734cc66-fe16-4d2f-ba78-727597040f9a ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-5.15.0-43-generic N/A
linux-backports-modules-5.15.0-43-generic N/A
linux-firmware 20220329.git681281e4-0ubuntu3.3
RfKill:
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/21/2022
dmi.bios.release: 1.3
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.3.72
dmi.board.name: 08WXMX
dmi.board.vendor: Dell Inc.
dmi.board.version: A01
dmi.chassis.type: 3
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr1.3.72:bd06/21/2022:br1.3:svnDellInc.:pnPrecision3460:pvr:rvnDellInc.:rn08WXMX:rvrA01:cvnDellInc.:ct3:cvr:sku0AC7:
dmi.product.family: OptiPlex
dmi.product.name: Precision 3460
dmi.product.sku: 0AC7
dmi.sys.vendor: Dell Inc.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug jammy
** Bug watch added: Linux Kernel Bug Tracker #214821
https://bugzilla.kernel.org/show_bug.cgi?id=214821
--
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/1983404
Title:
e1000e on Alder Lake does not resume successfully
Status in linux package in Ubuntu:
New
Bug description:
This is a Dell Precision 3460 workstation (Alder Lake CPU) with latest
BIOS and Intel AMT turned off in the BIOS.
When enabling the Power -> 'Automatic Suspend' setting the e1000e
wired ethernet is always broken on wake up. rmmoding and modprobing
the e1000e driver will eventually heal it.
On resume the kernel logs:
Aug 01 14:41:01 wakko kernel: e1000e :00:1f.6 enp0s31f6: NIC Link is Down
Aug 01 14:41:01 wakko kernel: ata8: SATA link down (SStatus 4 SControl 300)
Aug 01 14:41:01 wakko kernel: ata5: SATA link down (SStatus 4 SControl 300)
Aug 01 14:41:01 wakko kernel: ata7: SATA
[Kernel-packages] [Bug 1981922] Re: Upgrade yellow carp DMCUB firmware to fix suspend failure
Any ETA for the fix landed focal proposed or update channel? Thanks. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1981922 Title: Upgrade yellow carp DMCUB firmware to fix suspend failure Status in HWE Next: New Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Focal: In Progress Status in linux-firmware source package in Impish: Won't Fix Status in linux-firmware source package in Jammy: In Progress Status in linux-firmware source package in Kinetic: Fix Released Bug description: [Impact] Certain Rembrandt designs use LPDDR memory and current firmware in linux-firmware package in Focal and Jammy has a failure resuming from s0i3 on DC power with it. Some sample designs affected by the failure are Thinkpad X13, Z13, Z16. This failure doesn't affect resume with AC power or designs without LPDDR memory. [Fix] Upgrade yellow carp DMCUB firmware binary. https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux- firmware.git/commit/?id=4458bb4185b6d6e1f5c586fcf4b8cf6f5d3c8e24 [Test] Verify suspend/resume works. Verify that externally plugged displays haven't regressed. [Where problems could occur] Firmware is only loaded to Rembrandt designs. Regressions would be tied to those platforms. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1981922/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1981658] Re: BUG: kernel NULL pointer dereference, address: 0000000000000008
Also want to confirm that I am seeing the same kernel panic in the last couple of days with v5.4.0-122. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.4 in Ubuntu. https://bugs.launchpad.net/bugs/1981658 Title: BUG: kernel NULL pointer dereference, address: 0008 Status in linux package in Ubuntu: Confirmed Status in linux-hwe-5.4 package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Status in linux-hwe-5.4 source package in Bionic: Confirmed Bug description: Hi, On one of the main US Ubuntu Archive servers (banjo), we decided to reboot into a HWE kernel. The latest being 5.4.0-122 but on doing so, ran into this kernel panic: | [ 350.776585] BUG: kernel NULL pointer dereference, address: 0008 | [ 350.783674] #PF: supervisor read access in kernel mode | [ 350.788846] #PF: error_code(0x) - not-present page | [ 350.794019] PGD 0 P4D 0 | [ 350.796631] Oops: [#1] SMP NOPTI | [ 350.800425] CPU: 8 PID: 0 Comm: swapper/8 Not tainted 5.4.0-122-generic #138~18.04.1-Ubuntu | [ 350.808918] Hardware name: HPE ProLiant DL385 Gen10/ProLiant DL385 Gen10, BIOS A40 02/10/2022 | [ 350.817666] RIP: 0010:tcp_create_openreq_child+0x2e1/0x3e0 | [ 350.823187] Code: 08 00 00 41 8b 84 24 18 01 00 00 48 c7 83 80 08 00 00 00 00 00 00 4c 89 e6 4c 89 ef 89 83 c4 05 00 00 49 8b 84 24 f8 00 00 00 <48> 8b 40 08 e8 96 28 42 00 48 85 c0 0f b7 83 68 05 00 00 74 0a 83 | [ 350.842068] RSP: 0018:9a958cce8858 EFLAGS: 00010246 | [ 350.847324] RAX: RBX: 897618739c80 RCX: 0007 | [ 350.854502] RDX: 0020 RSI: 897607afb0b0 RDI: 897605c85580 | [ 350.861682] RBP: 9a958cce8878 R08: 0178 R09: 89763e407800 | [ 350.868859] R10: 04c4 R11: 9a958cce89c7 R12: 897607afb0b0 | [ 350.876039] R13: 897605c85580 R14: 8976205fbe00 R15: 89762688b400 | [ 350.883219] FS: () GS:89763ec0() knlGS: | [ 350.891358] CS: 0010 DS: ES: CR0: 80050033 | [ 350.897138] CR2: 0008 CR3: 001fd7914000 CR4: 00340ee0 | [ 350.904319] Call Trace: | [ 350.906787] | [ 350.908824] tcp_v6_syn_recv_sock+0x8d/0x710 | [ 350.913259] ? ip6_route_output_flags_noref+0xd0/0x110 | [ 350.918435] tcp_get_cookie_sock+0x48/0x140 | [ 350.922688] cookie_v6_check+0x5a2/0x700 | [ 350.926714] tcp_v6_do_rcv+0x36c/0x3e0 | [ 350.930589] ? tcp_v6_do_rcv+0x36c/0x3e0 | [ 350.934589] tcp_v6_rcv+0xa16/0xa60 | [ 350.938102] ip6_protocol_deliver_rcu+0xd8/0x4d0 | [ 350.942750] ip6_input+0x41/0xb0 | [ 350.946000] ip6_sublist_rcv_finish+0x42/0x60 | [ 350.950385] ip6_sublist_rcv+0x235/0x260 | [ 350.954333] ? __netif_receive_skb_core+0x19d/0xc60 | [ 350.959245] ipv6_list_rcv+0x110/0x140 | [ 350.963018] __netif_receive_skb_list_core+0x157/0x260 | [ 350.968192] ? build_skb+0x17/0x80 | [ 350.971615] netif_receive_skb_list_internal+0x187/0x2a0 | [ 350.976961] gro_normal_list.part.131+0x1e/0x40 | [ 350.981519] napi_complete_done+0x94/0x120 | [ 350.985700] mlx5e_napi_poll+0x178/0x630 [mlx5_core] | [ 350.990697] net_rx_action+0x140/0x3e0 | [ 350.994475] __do_softirq+0xe4/0x2da | [ 350.998079] irq_exit+0xae/0xb0 | [ 351.001239] do_IRQ+0x59/0xe0 | [ 351.004228] common_interrupt+0xf/0xf | [ 351.007913] | [ 351.010029] RIP: 0010:cpuidle_enter_state+0xbc/0x440 | [ 351.015023] Code: ff e8 b8 ca 80 ff 80 7d d3 00 74 17 9c 58 0f 1f 44 00 00 f6 c4 02 0f 85 54 03 00 00 31 ff e8 4b 4f 87 ff fb 66 0f 1f 44 00 00 <45> 85 ed 0f 88 1a 03 00 00 4c 2b 7d c8 48 ba cf f7 53 e3 a5 9b c4 | [ 351.033952] RSP: 0018:9a958026fe48 EFLAGS: 0246 ORIG_RAX: ffd6 | [ 351.041633] RAX: 89763ec2fe00 RBX: 84b66b40 RCX: 001f | [ 351.048816] RDX: 0051abe96150 RSI: 2abf3234 RDI: | [ 351.055997] RBP: 9a958026fe88 R08: 0002 R09: 0002f680 | [ 351.063176] R10: 9a958026fe18 R11: 0115 R12: 8976274c3800 | [ 351.070355] R13: 0001 R14: 84b66bb8 R15: 0051abe96150 | [ 351.077540] ? cpuidle_enter_state+0x98/0x440 | [ 351.081930] ? menu_select+0x377/0x600 | [ 351.085706] cpuidle_enter+0x2e/0x40 | [ 351.089310] call_cpuidle+0x23/0x40 | [ 351.092821] do_idle+0x1f6/0x270 | [ 351.096069] cpu_startup_entry+0x1d/0x20 | [ 351.100024] start_secondary+0x166/0x1c0 | [ 351.103977] secondary_startup_64+0xa4/0xb0 | [ 351.108186] Modules linked in: binfmt_misc bonding nls_iso8859_1 ipmi_ssif edac_mce_amd kvm_amd kvm hpilo ccp ipmi_si ipmi_devintf ipmi_msghandler acpi_tad k10temp mac_hid acpi_power_meter sch_fq tcp_bbr ib_iser rdma_cm iw_cm ib_cm iscsi_tcp libiscsi_tcp libi
[Kernel-packages] [Bug 1977919] Re: Docker container creation causes kernel oops on linux-aws 5.13.0.1028.31~20.04.22
Not sure if it will work on GCP but in Azure you hold escape to get into Grub while the system is booting. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1977919 Title: Docker container creation causes kernel oops on linux-aws 5.13.0.1028.31~20.04.22 Status in linux-aws-5.13 package in Ubuntu: Confirmed Status in linux-azure-5.13 package in Ubuntu: Confirmed Status in linux-gcp-5.13 package in Ubuntu: Confirmed Status in linux-intel-iotg-5.15 package in Ubuntu: Confirmed Status in linux-oracle-5.13 package in Ubuntu: Confirmed Status in linux-aws-5.13 source package in Focal: Fix Committed Status in linux-azure-5.13 source package in Focal: Fix Committed Status in linux-gcp-5.13 source package in Focal: Fix Committed Status in linux-intel-iotg-5.15 source package in Focal: Won't Fix Status in linux-oracle-5.13 source package in Focal: Fix Committed Bug description: Running the attached script on the latest AWS AMI for Ubuntu 20.04, I get a kernel panic and hard reset of the node. [ 12.314552] VFS: Close: file count is 0 [ 12.351090] [ cut here ] [ 12.351093] kernel BUG at include/linux/fs.h:3104! [ 12.355272] invalid opcode: [#1] SMP PTI [ 12.358963] CPU: 1 PID: 863 Comm: sed Not tainted 5.13.0-1028-aws #31~20.04.1-Ubuntu [ 12.366241] Hardware name: Amazon EC2 m5.large/, BIOS 1.0 10/16/2017 [ 12.371130] RIP: 0010:__fput+0x247/0x250 [ 12.374897] Code: 00 48 85 ff 0f 84 8b fe ff ff f6 c7 40 0f 85 82 fe ff ff e8 ab 38 00 00 e9 78 fe ff ff 4c 89 f7 e8 2e 88 02 00 e9 b5 fe ff ff <0f> 0b 0f 1f 80 00 00 00 00 0f 1f 44 00 00 55 48 89 e5 53 31 db 48 [ 12.389075] RSP: 0018:b50280d9fd88 EFLAGS: 00010246 [ 12.393425] RAX: RBX: 000a801d RCX: 9152e0716000 [ 12.398679] RDX: 9152cf075280 RSI: 0001 RDI: [ 12.403879] RBP: b50280d9fdb0 R08: 0001 R09: 9152dfcba2c8 [ 12.409102] R10: b50280d9fd88 R11: 9152d04e9d10 R12: 9152d04e9d00 [ 12.414333] R13: 9152dfcba2c8 R14: 9152cf0752a0 R15: 9152dfc2e180 [ 12.419533] FS: () GS:9153ea90() knlGS: [ 12.426937] CS: 0010 DS: ES: CR0: 80050033 [ 12.431506] CR2: 556cf30250a8 CR3: bce10006 CR4: 007706e0 [ 12.436716] DR0: DR1: DR2: [ 12.441941] DR3: DR6: fffe0ff0 DR7: 0400 [ 12.447170] PKRU: 5554 [ 12.450355] Call Trace: [ 12.453408] [ 12.456296] fput+0xe/0x10 [ 12.459633] task_work_run+0x70/0xb0 [ 12.463157] do_exit+0x37b/0xaf0 [ 12.466570] do_group_exit+0x43/0xb0 [ 12.470142] __x64_sys_exit_group+0x18/0x20 [ 12.473989] do_syscall_64+0x61/0xb0 [ 12.477565] ? exit_to_user_mode_prepare+0x9b/0x1c0 [ 12.481734] ? do_user_addr_fault+0x1d0/0x650 [ 12.485665] ? irqentry_exit_to_user_mode+0x9/0x20 [ 12.489790] ? irqentry_exit+0x19/0x30 [ 12.493443] ? exc_page_fault+0x8f/0x170 [ 12.497199] ? asm_exc_page_fault+0x8/0x30 [ 12.501013] entry_SYSCALL_64_after_hwframe+0x44/0xae [ 12.505289] RIP: 0033:0x7f80d42a1bd6 [ 12.508868] Code: Unable to access opcode bytes at RIP 0x7f80d42a1bac. [ 12.513783] RSP: 002b:7ffe924f9ed8 EFLAGS: 0246 ORIG_RAX: 00e7 [ 12.520897] RAX: ffda RBX: 7f80d45a4740 RCX: 7f80d42a1bd6 [ 12.526115] RDX: RSI: 003c RDI: [ 12.531328] RBP: R08: 00e7 R09: fe98 [ 12.536484] R10: 7f80d3d422a0 R11: 0246 R12: 7f80d45a4740 [ 12.541687] R13: 0002 R14: 7f80d45ad708 R15: [ 12.546916] [ 12.549829] Modules linked in: xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo xt_addrtype iptable_filter iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c bpfilter br_netfilter bridge stp llc aufs overlay nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua crct10dif_pclmul ppdev crc32_pclmul ghash_clmulni_intel aesni_intel crypto_simd psmouse cryptd parport_pc input_leds parport ena serio_raw sch_fq_codel ipmi_devintf ipmi_msghandler msr drm ip_tables x_tables autofs4 [ 12.583913] ---[ end trace 77367fed4d782aa4 ]--- [ 12.587963] RIP: 0010:__fput+0x247/0x250 [ 12.591729] Code: 00 48 85 ff 0f 84 8b fe ff ff f6 c7 40 0f 85 82 fe ff ff e8 ab 38 00 00 e9 78 fe ff ff 4c 89 f7 e8 2e 88 02 00 e9 b5 fe ff ff <0f> 0b 0f 1f 80 00 00 00 00 0f 1f 44 00 00 55 48 89 e5 53 31 db 48 [ 12.605796] RSP: 0018:b50280d9fd88 EFLAGS: 00010246 [ 12.610166] RAX: RBX: 000
[Kernel-packages] [Bug 1970923] Re: [SRU][F/J] Update firmware of MT7922
@ Juerg, Thanks for the help to comment the new firmware for mt7922. Can you help to advise when will be the new linux-firmware with this fix landing? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1970923 Title: [SRU][F/J] Update firmware of MT7922 Status in HWE Next: New Status in linux-firmware package in Ubuntu: New Status in linux-firmware source package in Focal: Fix Committed Status in linux-firmware source package in Jammy: Fix Committed Bug description: [Impact] MT7922 is not stable to connect. [Fix] Update firmware of MT7922 wifi and bluetooth. [Test] Verified on RZ616, it works fine, suspend OK. Wifi b/g can be connected. iperf test result looks fine. Bluetooth is stable. [Where problems could occur] These firmware is specific for MT7922, it should be low risk. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1970923/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1957847] [NEW] display output detection problem
Public bug reported: dell precision M6800 KERNEL 5.4.0-94 attempts to activate vga while not plugged in, deactivates, cyclic screen blackout, shape/size ** 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/1957847 Title: display output detection problem Status in linux package in Ubuntu: New Bug description: dell precision M6800 KERNEL 5.4.0-94 attempts to activate vga while not plugged in, deactivates, cyclic screen blackout, shape/size To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1957847/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1939177] Re: Ubuntu 20.04.2 LTS kernel 5.11.0-25 zfs send | receive broken
The amd64 version still isn't built after the build failure, how can we get that build restarted? Cheers -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1939177 Title: Ubuntu 20.04.2 LTS kernel 5.11.0-25 zfs send | receive broken Status in zfs-linux package in Ubuntu: Confirmed Status in zfs-linux source package in Focal: Fix Committed Bug description: == SRU Justification Focal == [Impact] https://github.com/openzfs/zfs/issues/12462 Ubuntu 20.04.2 LTS Kernel: 5.11.0-25-generic #27~20.04.1-Ubuntu zfs-0.8.3-1ubuntu12.12 zfs-kmod-2.0.2-1ubuntu5 Trying to run zfs send | receive and getting an error: # zfs send 'rpool/home'@'autosnap_2020-08-01_00:59:01_monthly' | zfs receive -s -F 'nas/rpool_backup/home' cannot receive: failed to read from stream cannot receive new filesystem stream: dataset does not exist This used to work before the recent Ubuntu kernel update from 5.8 to 5.11 Kernel 5.8 came with zfs-kmod-0.8.4-1ubuntu11.2 Ubuntu updates that broke it: Upgrade: linux-headers-generic-hwe-20.04:amd64 (5.8.0.63.71~20.04.45, 5.11.0.25.27~20.04.10), linux- image-generic-hwe-20.04:amd64 (5.8.0.63.71~20.04.45, 5.11.0.25.27~20.04.10), linux-generic-hwe-20.04 :amd64 (5.8.0.63.71~20.04.45, 5.11.0.25.27~20.04.10) Sending the zfs send part to a file works, but then sending the file to zfs receive also fails. The dump file size seems reasonable but the contents may not be correct. [Test Plan] 1. create test pool and backup pool sudo zpool create pool /dev/vdb1 sudo zpool create backup /dev/vdc1 2. populate pool with some files and create some snapshots sudo zfs snapshot pool@now1 create some more files etc, make another snapshot sudo zfs snapshot pool@now2 3. perform send/recv using -s option: sudo zfs send pool@now1 | sudo zfs receive -vFs backup sudo zfs send -i pool@now1 pool@now2 | sudo zfs receive -vFs backup Without the fix, the -s option on the receive fails. With the fix it works fine. Test with focal 5.4 and 5.11 kernel to exercise 0.8.x and 2.x kernel ZFS drivers. [Where problems could occur] The main fix nullifies the deprecated action_handle option so that it's not checked, this allows 0.8.x userspace it to be forwardly compatible with 2.x kernel ZFS and also since it is deprecated in 0.8.x it makes not difference to the 0.8.x kernel ZFS driver. Thus the risk with patch action_handle is very small. Included in the fix is a send/recv upstream bug fix 4910-Fix-EIO-after-resuming-receive-of-new-dataset-over-a.patch that makes send/recv more resilient by making zfs receive to always unmount and remount the destination, regardless of whether the stream is a new stream or a resumed stream. The change is upstream for ~10 months and has minimal impact on current recv functionality. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1939177/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1826691] Re: fwupd hangs after 19.04 upgrade from 18.10
I tried to reproduce using the same read-dpcd as above on #11. I don't see the hang anymore using 5.4 on 20.04. Thanks for following up. -- 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/1826691 Title: fwupd hangs after 19.04 upgrade from 18.10 Status in Linux: Unknown Status in fwupd package in Ubuntu: Fix Released Status in linux package in Ubuntu: Triaged Status in fwupd source package in Disco: Won't Fix Status in linux source package in Disco: Won't Fix Status in fwupd source package in Eoan: Fix Released Status in linux source package in Eoan: Won't Fix Bug description: 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu $ lsb_release -rd Description:Ubuntu 19.04 Release:19.04 Being a firmware updater, the machine is probably relevant - Dell 7730. 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center $ apt policy fwupd fwupd: Installed: (none) Candidate: 1.2.5-1ubuntu1 Version table: 1.2.5-1ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu disco/main amd64 Packages 100 /var/lib/dpkg/status 3) What you expected to happen I expected few/no issues after 19.04 upgrade. The fwupd process worked perfectly in 18.10. It's upgraded the firmware on my laptop twice since I installed 18.10. 4) What happened instead After upgrading from 18.10 to 19.04 I had an issues that when I tried to suspend my laptop using the same button press as previous, the laptop would be hot and screen flickering when I returned to reopen it. I thought there were power management issues in the upgrade, but I've traced it to fwupd not letting the PM suspend process complete (see dmesg below). I tried shutting down the fwupd daemon with systemctl but the command hangs forever. All of the fwupdmgr commands timeout. Thinking something might have broken in the upgrade, I tried uninstalling (purge) the fwupd package and reinstalling. Starting the process with systemctl hangs forever like stopping it. Trying to kill -9 the process does not work - in uninterruptible sleep (D). This crash is probably related. It happened a couple of ours before I tried to put it to sleep the last time before uninstalling fwupd. Apr 23 19:29:14 texas kernel: [ 133.673290] [drm] REG_WAIT timeout 10us * 160 tries - submit_channel_request line:246 Apr 23 19:29:14 texas kernel: [ 133.673348] WARNING: CPU: 6 PID: 2467 at drivers/gpu/drm/amd/amdgpu/../display/dc/dc_helper.c:249 generic_reg_wait.cold.3+0x25/0x2c [amdgpu] Apr 23 19:29:14 texas kernel: [ 133.673349] Modules linked in: thunderbolt rfcomm xt_owner ip6table_filter ip6_tables ipt_MASQUERADE iptable_nat nf_nat_ipv4 nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c bridge xt_CHECKSUM xt_tcpudp stp llc iptable_filter iptable_mangle bpfilter ccm snd_hda_codec_realtek snd_hda_codec_generic pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) cmac vboxdrv(OE) bnep binfmt_misc dell_rbtn nls_iso8859_1 joydev arc4 snd_soc_skl snd_soc_hdac_hda snd_hda_ext_core snd_soc_skl_ipc snd_soc_sst_ipc snd_soc_sst_dsp snd_soc_acpi_intel_match snd_soc_acpi snd_soc_core snd_compress ac97_bus intel_rapl snd_pcm_dmaengine x86_pkg_temp_thermal intel_powerclamp coretemp snd_hda_codec_hdmi kvm_intel snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep crct10dif_pclmul i915 snd_pcm crc32_pclmul iwlmvm uvcvideo amdgpu snd_seq_midi ghash_clmulni_intel snd_seq_midi_event mac80211 videobuf2_vmalloc kvmgt videobuf2_memops vfio_mdev videobuf2_v4l2 snd_rawmidi dell_laptop mdev videobuf2_common Apr 23 19:29:14 texas kernel: [ 133.673362] ledtrig_audio vfio_iommu_type1 videodev dell_smm_hwmon vfio snd_seq dell_wmi media kvm chash btusb snd_seq_device amd_iommu_v2 btrtl snd_timer btbcm dell_smbios gpu_sched irqbypass btintel dcdbas ttm aesni_intel iwlwifi bluetooth drm_kms_helper aes_x86_64 crypto_simd cryptd glue_helper rtsx_pci_ms input_leds snd drm ecdh_generic intel_cstate mei_me ucsi_acpi cfg80211 serio_raw dell_wmi_descriptor intel_wmi_thunderbolt wmi_bmof memstick i2c_algo_bit mei fb_sys_fops intel_rapl_perf idma64 syscopyarea hid_multitouch processor_thermal_device soundcore sysfillrect virt_dma typec_ucsi sysimgblt intel_soc_dts_iosf intel_pch_thermal typec int3403_thermal int340x_thermal_zone dell_smo8800 acpi_pad intel_hid int3400_thermal mac_hid acpi_thermal_rel sparse_keymap sch_fq_codel parport_pc ppdev lp parport ip_tables x_tables autofs4 hid_generic rtsx_pci_sdmmc nvme e1000e i2c_i801 intel_lpss_pci rtsx_pci nvme_core intel_lpss i2c_hid wmi hid video pinctrl_cannonlake pinctrl_intel Apr 23 19:29:14 texas kernel: [ 133.673381] CPU: 6 PID: 2467 Comm: fwupd Tainted: G OE 5.0.0-13-generic #14-Ubuntu Apr 23 19:29:14 texas kernel: [
[Kernel-packages] [Bug 1762672] Re: TPM intermittently fails after cold-boot
After upgrading from 18.04 to 21.04, my XPS 13 fails to boot, giving the message "a TPM error (2314) occurred attempting the self test". How can this be fixed? Thanks, jason -- 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/1762672 Title: TPM intermittently fails after cold-boot Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Bug description: [Impact] On an 18.04 LTS system with a TPM, the TPM will fail intermittently on cold boots. The problem seems to be that the TPM gets into a state where the partial self-test doesn't return TPM_RC_SUCCESS (meaning all tests have run to completion), but instead returns TPM_RC_TESTING (meaning some tests are still running in the background). A reboot can sometimes restore TPM functionality. This bug was originally reported on a Dell XPS 13, but has also recently been reported on a Dell Edge Gateway 3000. The bug has been confirmed to be fixed in the current development release (19.04/Cosmic). [Test Case] Cold boot a Dell XPS 13 or Dell Edge Gateway 3000 running 18.04 LTS Desktop or Server and grep for the following error log message: "tpm tpm0: A TPM error (2314) occurred continue selftest" Any attempts at using the TPM via tpm2-tss libraries or tpm2-tools should produce errors. As this bug is due to a race condition, ideally this test case would be run multiple times (20+ cold boots). Once the patch is installed the following error message may still be present in the syslog, however attempts to use the TPM should work: "tpm tpm0: A TPM error (2314) occurred attempting the self test" [Regression Potential] The chance of regression is low, as this patch was written by a well respected kernel developer with deep TPM experience. The patch is also being cherry-picked from the upstream stable and LTS kernels, and as mentioned, has already landed in Disco. [Original Description] After updating a Dell XPS 13 to 18.04 LTS, the TPM started to intermittently fail on cold boot. The following log messages could be observed in syslog: [0.801334] tpm_tis MSFT0101:00: 2.0 TPM (device-id 0xFE, rev-id 4) [0.812132] tpm tpm0: A TPM error (2314) occurred continue selftest [0.843629] tpm tpm0: A TPM error (2314) occurred continue selftest [0.895424] tpm tpm0: A TPM error (2314) occurred continue selftest [0.987230] tpm tpm0: A TPM error (2314) occurred continue selftest [1.159026] tpm tpm0: A TPM error (2314) occurred continue selftest [1.490819] tpm tpm0: A TPM error (2314) occurred continue selftest [2.142530] tpm tpm0: A TPM error (2314) occurred continue selftest [3.423100] tpm tpm0: TPM self test failed [3.456304] ima: No TPM chip found, activating TPM-bypass! (rc=-19) Discussion https://lkml.org/lkml/2017/12/6/284 Fix https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/char/tpm/tpm2-cmd.c?id=2be8ffed093b91536d52b5cd2c99b52f605c9ba6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762672/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1908108] [NEW] tg3: transmit timed out, resetting
Public bug reported: On a deploy of kubernetes, we're seeing a machine have issues with its tg3 driven nics. We see: Dec 14 07:44:08 juju-fcf29c-0-lxd-1 kernel: [ 1496.772960] tg3 :02:00.1 eth1: transmit timed out, resetting Around that time, we have issues with services losing network connections. A juju crashdump with logs is available here: https://oil-jenkins.canonical.com/artifacts/c15028dc-46fa-4f08-8895-55e9d500c362/generated/generated/kubernetes/juju-crashdump-kubernetes-2020-12-14-07.48.49.tar.gz syslog is at kubernetes-master_0/var/log/syslog this is on focal: [0.00] kernel: Linux version 5.4.0-58-generic (buildd@lcy01-amd64-004) (gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)) #64-Ubuntu SMP Wed Dec 9 08:16:25 UTC 2020 (Ubuntu 5.4.0-58.64-generic 5.4.73) ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Description changed: On a deploy of kubernetes, we're seeing a machine have issues with its tg3 driven nics. We see: Dec 14 07:44:08 juju-fcf29c-0-lxd-1 kernel: [ 1496.772960] tg3 :02:00.1 eth1: transmit timed out, resetting Around that time, we have issues with services losing network connections. + A juju crashdump with logs is available here: + https://oil-jenkins.canonical.com/artifacts/c15028dc-46fa-4f08-8895-55e9d500c362/generated/generated/kubernetes/juju-crashdump-kubernetes-2020-12-14-07.48.49.tar.gz + + syslog is at kubernetes-master_0/var/log/syslog this is on focal: [0.00] kernel: Linux version 5.4.0-58-generic (buildd@lcy01-amd64-004) (gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)) #64-Ubuntu SMP Wed Dec 9 08:16:25 UTC 2020 (Ubuntu 5.4.0-58.64-generic 5.4.73) -- 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/1908108 Title: tg3: transmit timed out, resetting Status in linux package in Ubuntu: New Bug description: On a deploy of kubernetes, we're seeing a machine have issues with its tg3 driven nics. We see: Dec 14 07:44:08 juju-fcf29c-0-lxd-1 kernel: [ 1496.772960] tg3 :02:00.1 eth1: transmit timed out, resetting Around that time, we have issues with services losing network connections. A juju crashdump with logs is available here: https://oil-jenkins.canonical.com/artifacts/c15028dc-46fa-4f08-8895-55e9d500c362/generated/generated/kubernetes/juju-crashdump-kubernetes-2020-12-14-07.48.49.tar.gz syslog is at kubernetes-master_0/var/log/syslog this is on focal: [0.00] kernel: Linux version 5.4.0-58-generic (buildd@lcy01-amd64-004) (gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)) #64-Ubuntu SMP Wed Dec 9 08:16:25 UTC 2020 (Ubuntu 5.4.0-58.64-generic 5.4.73) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1908108/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1861009] Re: Asus Zenbook Flip 15 ux563fd no sound
Thanks a lot! https://www.piramalaranya.com/ -- 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/1861009 Title: Asus Zenbook Flip 15 ux563fd no sound Status in linux package in Ubuntu: Confirmed Bug description: Bought a new laptop for a couple weeks ago and want to have a dual boot with W10 and Linux like my older one. First, I installed Ubuntu 18.04 and tried to make sound working via the speakers. I tried alsamixer, made sure everything was on OO, reinstalled both alsamixer and pulseaudio couple times, checked permissions on the config of pulseaudio and more what could fix it in regular terms including installing and replacing kernels older and new ones. As a last option, I installed version 19.10 from Ubuntu as someone mentioned that the higher version could fix it because of the different supported packages but is not resolving it. Nothing of the above mentioned things where fixing it, but I still see some movement at streaming bar in the sound option menu when I'm playing some music. I hope there is a workaround for this issue, I just found the whole Zenbook laptop line that has this problem so I really hope for a solution to this. Version - kernel: Ubuntu 5.3.0-26.28-generic 5.3.13 lspci -vnvn 00:00.0 Host bridge [0600]: Intel Corporation Device [8086:9b61] (rev 0c) Subsystem: ASUSTeK Computer Inc. Device [1043:1b31] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:9b41] (rev 02) (prog-if 00 [VGA controller]) DeviceName: VGA Subsystem: ASUSTeK Computer Inc. Device [1043:1b31] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Capabilities: [70] Express (v2) Root Complex Integrated Endpoint, MSI 00 DevCap: MaxPayload 128 bytes, PhantFunc 0 ExtTag- RBE+ DevCtl: CorrErr- NonFatalErr- FatalErr- UnsupReq- RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop- MaxPayload 128 bytes, MaxReadReq 128 bytes DevSta: CorrErr- NonFatalErr- FatalErr- UnsupReq- AuxPwr- TransPend- DevCap2: Completion Timeout: Not Supported, TimeoutDis-, LTR-, OBFF Not Supported AtomicOpsCap: 32bit- 64bit- 128bitCAS- DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, OBFF Disabled AtomicOpsCtl: ReqEn- Capabilities: [ac] MSI: Enable+ Count=1/1 Maskable- 64bit- Address: fee00018 Data: Capabilities: [d0] Power Management version 2 Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Capabilities: [100 v1] Process Address Space ID (PASID) PASIDCap: Exec- Priv-, Max PASID Width: 14 PASIDCtl: Enable- Exec- Priv- Capabilities: [200 v1] Address Translation Service (ATS) ATSCap: Invalidate Queue Depth: 00 ATSCtl: Enable-, Smallest Translation Unit: 00 Capabilities: [300 v1] Page Request Interface (PRI) PRICtl: Enable- Reset- PRISta: RF- UPRGI- Stopped+ Page Request Capacity: 8000, Page Request Allocation: Kernel driver in use: i915 Kernel modules: i915 00:04.0 Signal processing controller [1180]: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem [8086:1903] (rev 0c) Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem [1043:1b31] Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: proc_thermal Kernel modules: processor_thermal_device 00:08.0 System peripheral [0880]: Intel Corporation Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th Gen Core Processor Gaussian Mixture Model [8086:1911] Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th Gen Core Processor Gaussian Mixture Model [1043:1b31] Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- SERR- Kernel driver in use: intel_ish_ipc Kernel modules: intel_ish_ipc 00:14.0 USB controller
[Kernel-packages] [Bug 1895010] Re: ocfs2 shared volume causing hang
hopefully this ticket gets some notice soon as this bug appears to be a kernel level regression in a "major" kernel level feature: ocfs2 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1895010 Title: ocfs2 shared volume causing hang Status in linux package in Ubuntu: Confirmed Status in linux-signed package in Ubuntu: Confirmed Bug description: This vm is running on a vmware backed system with a multiwriter shared volume mounted via ocfs2. in kernel version 4.4.0-187 or -189 any attempt at writting to the volume results in kernel errors root@hostname:/mnt/NewsroomImageShare# touch text.txt Killed kernel version 186 this issue does not occur. root@hostname:~# lsb_release -rd Description:Ubuntu 16.04.7 LTS Release:16.04 package ii linux-image-4.4.0-187-generic 4.4.0-187.217 amd64Signed kernel image generic what I expect to happen: writing to a ocfs2 shared disk should not crash what happens: writting to an ocfs2 shared disk crashes the terminal/ssh session, and make the vm unusable. and logs errors in dmesg [Sep 3 04:09] general protection fault: [#1] SMP [ +0.000346] Modules linked in: mptctl ocfs2 quota_tree ocfs2_dlmfs ocfs2_stack_o2cb ocfs2_dlm ocfs2_nodemanager ocfs2_stackglue configfs vmw_balloon joydev input_leds serio_raw shpchp i2c_piix4 vmw_vsock_vmci_transport vsock vmw_vmci mac_hid ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi autofs4 btrfs raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd psmouse vmwgfx ttm drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops ahci vmxnet3 libahci mptspi mptscsih drm pata_acpi mptbase scsi_transport_spi fjes [ +0.001534] CPU: 0 PID: 1553 Comm: java Not tainted 4.4.0-189-generic #219-Ubuntu [ +0.49] Hardware name: VMware, Inc. VMware Virtual Platform/440BX Desktop Reference Platform, BIOS 6.00 12/12/2018 [ +0.67] task: 880073863900 ti: 8800798e task.ti: 8800798e [ +0.47] RIP: 0010:[] [] _raw_spin_lock+0xe/0x70 [ +0.86] RSP: 0018:8800798e3998 EFLAGS: 00010206 [ +0.35] RAX: 0002 RBX: 6d612d7972616e69 RCX: [ +0.46] RDX: 8000 RSI: 0009 RDI: 6d612d7972616ef1 [ +0.45] RBP: 8800798e3998 R08: R09: [ +0.45] R10: 880075729060 R11: 8000 R12: 6d612d7972616ef1 [ +0.44] R13: 8800748aeaa8 R14: 880076399650 R15: [ +0.46] FS: 7f9a50ad9700() GS:88007b60() knlGS: [ +0.51] CS: 0010 DS: ES: CR0: 80050033 [ +0.37] CR2: 7f9a1d4f2000 CR3: 79936000 CR4: 00160670 [ +0.000160] Stack: [ +0.19] 8800798e39b8 8123953e 0009 8800748ae000 [ +0.55] 8800798e3a38 c057bb77 c053309a [ +0.54] 88007958e498 88007958e4e0 0001 88007958e3c8 [ +0.55] Call Trace: [ +0.25] [] igrab+0x1e/0x50 [ +0.84] [] ocfs2_get_system_file_inode+0x67/0x300 [ocfs2] [ +0.88] [] ? ocfs2_read_virt_blocks+0x1ca/0x310 [ocfs2] [ +0.72] [] ? dx_leaf_sort_swap+0x40/0x40 [ocfs2] [ +0.75] [] ocfs2_reserve_suballoc_bits+0x4e/0x430 [ocfs2] [ +0.74] [] ocfs2_steal_resource+0x9b/0x130 [ocfs2] [ +0.001659] [] ocfs2_reserve_new_inode+0xb5/0x370 [ocfs2] [ +0.001326] [] ocfs2_mknod+0x4be/0x10e0 [ocfs2] [ +0.001622] [] ? ocfs2_should_refresh_lock_res+0x113/0x160 [ocfs2] [ +0.001571] [] ocfs2_create+0x4c/0x160 [ocfs2] [ +0.001318] [] vfs_create+0x12d/0x190 [ +0.001218] [] path_openat+0x1232/0x1360 [ +0.001255] [] ? file_update_time+0xcc/0x110 [ +0.001167] [] do_filp_open+0x91/0x100 [ +0.001132] [] ? new_sync_write+0xa5/0xf0 [ +0.001131] [] ? __alloc_fd+0xc7/0x190 [ +0.001072] [] do_sys_open+0x138/0x2a0 [ +0.001040] [] SyS_open+0x1e/0x20 [ +0.001028] [] entry_SYSCALL_64_fastpath+0x22/0xd0 [ +0.001041] Code: e2 fe 8d 72 02 0f b7 f6 0f 1f 80 00 00 00 00 eb d2 66 90 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 55 48 89 e5 b8 00 00 02 00 0f c1 07 89 c2 c1 ea 10 66 39 c2 75 02 5d c3 41 89 d0 0f b7 [ +0.003174] RIP [] _raw_spin_lock+0xe/0x70 [ +0.001007] RSP [ +0.002867] ---[ end trace 6fd21d2a8e763939 ]--- - [Sep 4 03:56] (java,5847,1):ocfs2_reserve_suballoc_bits:796 ERROR: status = -22 [ +0.98] (java,5847,1):ocfs2_reserve_n
[Kernel-packages] [Bug 1895010] Re: ocfs2 shared volume causing hang
** 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-signed in Ubuntu. https://bugs.launchpad.net/bugs/1895010 Title: ocfs2 shared volume causing hang Status in linux package in Ubuntu: Confirmed Status in linux-signed package in Ubuntu: Confirmed Bug description: This vm is running on a vmware backed system with a multiwriter shared volume mounted via ocfs2. in kernel version 4.4.0-187 or -189 any attempt at writting to the volume results in kernel errors root@hostname:/mnt/NewsroomImageShare# touch text.txt Killed kernel version 186 this issue does not occur. root@hostname:~# lsb_release -rd Description:Ubuntu 16.04.7 LTS Release:16.04 package ii linux-image-4.4.0-187-generic 4.4.0-187.217 amd64Signed kernel image generic what I expect to happen: writing to a ocfs2 shared disk should not crash what happens: writting to an ocfs2 shared disk crashes the terminal/ssh session, and make the vm unusable. and logs errors in dmesg [Sep 3 04:09] general protection fault: [#1] SMP [ +0.000346] Modules linked in: mptctl ocfs2 quota_tree ocfs2_dlmfs ocfs2_stack_o2cb ocfs2_dlm ocfs2_nodemanager ocfs2_stackglue configfs vmw_balloon joydev input_leds serio_raw shpchp i2c_piix4 vmw_vsock_vmci_transport vsock vmw_vmci mac_hid ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi autofs4 btrfs raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd psmouse vmwgfx ttm drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops ahci vmxnet3 libahci mptspi mptscsih drm pata_acpi mptbase scsi_transport_spi fjes [ +0.001534] CPU: 0 PID: 1553 Comm: java Not tainted 4.4.0-189-generic #219-Ubuntu [ +0.49] Hardware name: VMware, Inc. VMware Virtual Platform/440BX Desktop Reference Platform, BIOS 6.00 12/12/2018 [ +0.67] task: 880073863900 ti: 8800798e task.ti: 8800798e [ +0.47] RIP: 0010:[] [] _raw_spin_lock+0xe/0x70 [ +0.86] RSP: 0018:8800798e3998 EFLAGS: 00010206 [ +0.35] RAX: 0002 RBX: 6d612d7972616e69 RCX: [ +0.46] RDX: 8000 RSI: 0009 RDI: 6d612d7972616ef1 [ +0.45] RBP: 8800798e3998 R08: R09: [ +0.45] R10: 880075729060 R11: 8000 R12: 6d612d7972616ef1 [ +0.44] R13: 8800748aeaa8 R14: 880076399650 R15: [ +0.46] FS: 7f9a50ad9700() GS:88007b60() knlGS: [ +0.51] CS: 0010 DS: ES: CR0: 80050033 [ +0.37] CR2: 7f9a1d4f2000 CR3: 79936000 CR4: 00160670 [ +0.000160] Stack: [ +0.19] 8800798e39b8 8123953e 0009 8800748ae000 [ +0.55] 8800798e3a38 c057bb77 c053309a [ +0.54] 88007958e498 88007958e4e0 0001 88007958e3c8 [ +0.55] Call Trace: [ +0.25] [] igrab+0x1e/0x50 [ +0.84] [] ocfs2_get_system_file_inode+0x67/0x300 [ocfs2] [ +0.88] [] ? ocfs2_read_virt_blocks+0x1ca/0x310 [ocfs2] [ +0.72] [] ? dx_leaf_sort_swap+0x40/0x40 [ocfs2] [ +0.75] [] ocfs2_reserve_suballoc_bits+0x4e/0x430 [ocfs2] [ +0.74] [] ocfs2_steal_resource+0x9b/0x130 [ocfs2] [ +0.001659] [] ocfs2_reserve_new_inode+0xb5/0x370 [ocfs2] [ +0.001326] [] ocfs2_mknod+0x4be/0x10e0 [ocfs2] [ +0.001622] [] ? ocfs2_should_refresh_lock_res+0x113/0x160 [ocfs2] [ +0.001571] [] ocfs2_create+0x4c/0x160 [ocfs2] [ +0.001318] [] vfs_create+0x12d/0x190 [ +0.001218] [] path_openat+0x1232/0x1360 [ +0.001255] [] ? file_update_time+0xcc/0x110 [ +0.001167] [] do_filp_open+0x91/0x100 [ +0.001132] [] ? new_sync_write+0xa5/0xf0 [ +0.001131] [] ? __alloc_fd+0xc7/0x190 [ +0.001072] [] do_sys_open+0x138/0x2a0 [ +0.001040] [] SyS_open+0x1e/0x20 [ +0.001028] [] entry_SYSCALL_64_fastpath+0x22/0xd0 [ +0.001041] Code: e2 fe 8d 72 02 0f b7 f6 0f 1f 80 00 00 00 00 eb d2 66 90 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 55 48 89 e5 b8 00 00 02 00 0f c1 07 89 c2 c1 ea 10 66 39 c2 75 02 5d c3 41 89 d0 0f b7 [ +0.003174] RIP [] _raw_spin_lock+0xe/0x70 [ +0.001007] RSP [ +0.002867] ---[ end trace 6fd21d2a8e763939 ]--- - [Sep 4 03:56] (java,5847,1):ocfs2_reserve_suballoc_bits:796 ERROR: status = -22 [ +0.98] (java,5847,1):ocfs2_reserve_new_inode:1120 ERROR: status = -22 [ +0.47] (java,5847,1):ocfs
[Kernel-packages] [Bug 1894247] Re: virtual machine locks up when accessing mounted share
*** This bug is a duplicate of bug 1895010 *** https://bugs.launchpad.net/bugs/1895010 I cannot run then command as the vm where the issue occurred is no longer running the problematic kernel. And yes this appears by all intents and purpose to be a kernel level regression ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** This bug has been marked a duplicate of bug 1895010 ocfs2 shared volume causing hang -- 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/1894247 Title: virtual machine locks up when accessing mounted share Status in linux package in Ubuntu: Confirmed Status in ocfs2-tools package in Ubuntu: Incomplete Bug description: I have a virtual machine that locks up every time any file access is done to the mounted ocsfs2 shared volume. the volume is backed by vmware multiwriter virtual disk. I do not have a lot of diagnostics other than the various dmesg logs it seems to be an ocfs2 issue or at least ocfs2 is "crashing" when this happens the ssh session locks up and is un usable. and as a result of monitoring services that try to read disk status the cpu load goes high attempts to reboot the vm during this state sometimes result in user@hostname:~$ sudo shutdown -r now Failed to start reboot.target: Connection timed out See system logs and 'systemctl status reboot.target' for details. lsb_release -rd Description:Ubuntu 16.04.7 LTS Release:16.04 apt-cache policy ocfs2-tools ocfs2-tools: Installed: 1.6.4-3.1 number #1 [Sep 4 14:33] BUG: unable to handle kernel paging request at c0504088 [ +0.000101] IP: [] _raw_spin_lock+0xe/0x70 [ +0.000100] PGD 1e0f067 PUD 1e11067 PMD 33756067 PTE 778f3061 [ +0.48] Oops: 0003 [#1] SMP [ +0.27] Modules linked in: ocfs2 quota_tree ocfs2_dlmfs ocfs2_stack_o2cb ocfs2_dlm ocfs2_nodemanager ocfs2_stackglue mptctl configfs vmw_balloon joydev input_leds serio_raw i2c_piix4 shpchp mac_hid vmw_vsock_vmci_transport vsock vmw_vmci ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi autofs4 btrfs raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd psmouse mptspi mptscsih mptbase scsi_transport_spi vmwgfx ahci ttm drm_kms_helper syscopyarea vmxnet3 sysfillrect sysimgblt fb_sys_fops libahci drm pata_acpi fjes [ +0.000591] CPU: 0 PID: 5568 Comm: touch Not tainted 4.4.0-189-generic #219-Ubuntu [ +0.49] Hardware name: VMware, Inc. VMware Virtual Platform/440BX Desktop Reference Platform, BIOS 6.00 12/12/2018 [ +0.67] task: 880034f25580 ti: 8800767c4000 task.ti: 8800767c4000 [ +0.47] RIP: 0010:[] [] _raw_spin_lock+0xe/0x70 [ +0.57] RSP: 0018:8800767c7998 EFLAGS: 00010286 [ +0.35] RAX: 0002 RBX: c0504000 RCX: [ +0.45] RDX: 8000 RSI: 0009 RDI: c0504088 [ +0.44] RBP: 8800767c7998 R08: R09: [ +0.45] R10: 880078ea5f00 R11: 8000 R12: c0504088 [ +0.44] R13: 880077a63aa8 R14: 880077a510d0 R15: [ +0.47] FS: 7fe66bc9e700() GS:88007b60() knlGS: [ +0.50] CS: 0010 DS: ES: CR0: 80050033 [ +0.000117] CR2: c0504088 CR3: 763c CR4: 00160670 [ +0.000203] Stack: [ +0.18] 8800767c79b8 8123953e 0009 880077a63000 [ +0.55] 8800767c7a38 c0582b77 c053a09a [ +0.54] 8800784b7c98 8800784b7ce0 0001 8800784b7bc8 [ +0.54] Call Trace: [ +0.84] [] igrab+0x1e/0x50 [ +0.000393] [] ocfs2_get_system_file_inode+0x67/0x300 [ocfs2] [ +0.001444] [] ? ocfs2_read_virt_blocks+0x1ca/0x310 [ocfs2] [ +0.001374] [] ? dx_leaf_sort_swap+0x40/0x40 [ocfs2] [ +0.001347] [] ocfs2_reserve_suballoc_bits+0x4e/0x430 [ocfs2] [ +0.001329] [] ocfs2_steal_resource+0x9b/0x130 [ocfs2] [ +0.001313] [] ocfs2_reserve_new_inode+0xb5/0x370 [ocfs2] [ +0.001294] [] ocfs2_mknod+0x4be/0x10e0 [ocfs2] [ +0.001296] [] ? ocfs2_should_refresh_lock_res+0x113/0x160 [ocfs2] [ +0.001300] [] ocfs2_create+0x4c/0x160 [ocfs2] [ +0.001279] [] vfs_create+0x12d/0x190 [ +0.001790] [] path_openat+0x1232/0x1360 [ +0.001198] [] do_filp_open+0x91/0x100 [ +0.001217] [] ? do_mmap+0x309/0x480 [ +0.001132] [] ? __alloc_fd+0xc7/0x190 [ +0.001110] [] do_sys_open+0x138/0x2a0 [ +0.001099] [] ? __do_page_fault+0x1c1/0x410 [ +0.001043] [] SyS_open+0x1
[Kernel-packages] [Bug 1894247] Re: virtual machine locks up when accessing mounted share
at the time when i filed the bug I had not yet determined that it was a kernel issue. I am now sure, and there is a proper kernel bug filed for the issue: https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1895010, close, marked as duplicate, etc. Do as you see fit. -- 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/1894247 Title: virtual machine locks up when accessing mounted share Status in linux package in Ubuntu: Incomplete Status in ocfs2-tools package in Ubuntu: Incomplete Bug description: I have a virtual machine that locks up every time any file access is done to the mounted ocsfs2 shared volume. the volume is backed by vmware multiwriter virtual disk. I do not have a lot of diagnostics other than the various dmesg logs it seems to be an ocfs2 issue or at least ocfs2 is "crashing" when this happens the ssh session locks up and is un usable. and as a result of monitoring services that try to read disk status the cpu load goes high attempts to reboot the vm during this state sometimes result in user@hostname:~$ sudo shutdown -r now Failed to start reboot.target: Connection timed out See system logs and 'systemctl status reboot.target' for details. lsb_release -rd Description:Ubuntu 16.04.7 LTS Release:16.04 apt-cache policy ocfs2-tools ocfs2-tools: Installed: 1.6.4-3.1 number #1 [Sep 4 14:33] BUG: unable to handle kernel paging request at c0504088 [ +0.000101] IP: [] _raw_spin_lock+0xe/0x70 [ +0.000100] PGD 1e0f067 PUD 1e11067 PMD 33756067 PTE 778f3061 [ +0.48] Oops: 0003 [#1] SMP [ +0.27] Modules linked in: ocfs2 quota_tree ocfs2_dlmfs ocfs2_stack_o2cb ocfs2_dlm ocfs2_nodemanager ocfs2_stackglue mptctl configfs vmw_balloon joydev input_leds serio_raw i2c_piix4 shpchp mac_hid vmw_vsock_vmci_transport vsock vmw_vmci ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi autofs4 btrfs raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd psmouse mptspi mptscsih mptbase scsi_transport_spi vmwgfx ahci ttm drm_kms_helper syscopyarea vmxnet3 sysfillrect sysimgblt fb_sys_fops libahci drm pata_acpi fjes [ +0.000591] CPU: 0 PID: 5568 Comm: touch Not tainted 4.4.0-189-generic #219-Ubuntu [ +0.49] Hardware name: VMware, Inc. VMware Virtual Platform/440BX Desktop Reference Platform, BIOS 6.00 12/12/2018 [ +0.67] task: 880034f25580 ti: 8800767c4000 task.ti: 8800767c4000 [ +0.47] RIP: 0010:[] [] _raw_spin_lock+0xe/0x70 [ +0.57] RSP: 0018:8800767c7998 EFLAGS: 00010286 [ +0.35] RAX: 0002 RBX: c0504000 RCX: [ +0.45] RDX: 8000 RSI: 0009 RDI: c0504088 [ +0.44] RBP: 8800767c7998 R08: R09: [ +0.45] R10: 880078ea5f00 R11: 8000 R12: c0504088 [ +0.44] R13: 880077a63aa8 R14: 880077a510d0 R15: [ +0.47] FS: 7fe66bc9e700() GS:88007b60() knlGS: [ +0.50] CS: 0010 DS: ES: CR0: 80050033 [ +0.000117] CR2: c0504088 CR3: 763c CR4: 00160670 [ +0.000203] Stack: [ +0.18] 8800767c79b8 8123953e 0009 880077a63000 [ +0.55] 8800767c7a38 c0582b77 c053a09a [ +0.54] 8800784b7c98 8800784b7ce0 0001 8800784b7bc8 [ +0.54] Call Trace: [ +0.84] [] igrab+0x1e/0x50 [ +0.000393] [] ocfs2_get_system_file_inode+0x67/0x300 [ocfs2] [ +0.001444] [] ? ocfs2_read_virt_blocks+0x1ca/0x310 [ocfs2] [ +0.001374] [] ? dx_leaf_sort_swap+0x40/0x40 [ocfs2] [ +0.001347] [] ocfs2_reserve_suballoc_bits+0x4e/0x430 [ocfs2] [ +0.001329] [] ocfs2_steal_resource+0x9b/0x130 [ocfs2] [ +0.001313] [] ocfs2_reserve_new_inode+0xb5/0x370 [ocfs2] [ +0.001294] [] ocfs2_mknod+0x4be/0x10e0 [ocfs2] [ +0.001296] [] ? ocfs2_should_refresh_lock_res+0x113/0x160 [ocfs2] [ +0.001300] [] ocfs2_create+0x4c/0x160 [ocfs2] [ +0.001279] [] vfs_create+0x12d/0x190 [ +0.001790] [] path_openat+0x1232/0x1360 [ +0.001198] [] do_filp_open+0x91/0x100 [ +0.001217] [] ? do_mmap+0x309/0x480 [ +0.001132] [] ? __alloc_fd+0xc7/0x190 [ +0.001110] [] do_sys_open+0x138/0x2a0 [ +0.001099] [] ? __do_page_fault+0x1c1/0x410 [ +0.001043] [] SyS_open+0x1e/0x20 [ +0.001029] [] entry_SYSCALL_64_fastpath+0x22/0xd0 [ +0.001036] Code: e2 fe 8d 72 02 0f b7 f6 0f 1f 80 00 00 00 00 eb d2 66 90 66 2e 0f 1f 84 00 0
[Kernel-packages] [Bug 1895010] [NEW] ocfs2 shared volume causing hang
Public bug reported: This vm is running on a vmware backed system with a multiwriter shared volume mounted via ocfs2. in kernel version 4.4.0-187 or -189 any attempt at writting to the volume results in kernel errors root@hostname:/mnt/NewsroomImageShare# touch text.txt Killed kernel version 186 this issue does not occur. root@hostname:~# lsb_release -rd Description:Ubuntu 16.04.7 LTS Release:16.04 package ii linux-image-4.4.0-187-generic 4.4.0-187.217 amd64Signed kernel image generic what I expect to happen: writing to a ocfs2 shared disk should not crash what happens: writting to an ocfs2 shared disk crashes the terminal/ssh session, and make the vm unusable. and logs errors in dmesg [Sep 3 04:09] general protection fault: [#1] SMP [ +0.000346] Modules linked in: mptctl ocfs2 quota_tree ocfs2_dlmfs ocfs2_stack_o2cb ocfs2_dlm ocfs2_nodemanager ocfs2_stackglue configfs vmw_balloon joydev input_leds serio_raw shpchp i2c_piix4 vmw_vsock_vmci_transport vsock vmw_vmci mac_hid ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi autofs4 btrfs raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd psmouse vmwgfx ttm drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops ahci vmxnet3 libahci mptspi mptscsih drm pata_acpi mptbase scsi_transport_spi fjes [ +0.001534] CPU: 0 PID: 1553 Comm: java Not tainted 4.4.0-189-generic #219-Ubuntu [ +0.49] Hardware name: VMware, Inc. VMware Virtual Platform/440BX Desktop Reference Platform, BIOS 6.00 12/12/2018 [ +0.67] task: 880073863900 ti: 8800798e task.ti: 8800798e [ +0.47] RIP: 0010:[] [] _raw_spin_lock+0xe/0x70 [ +0.86] RSP: 0018:8800798e3998 EFLAGS: 00010206 [ +0.35] RAX: 0002 RBX: 6d612d7972616e69 RCX: [ +0.46] RDX: 8000 RSI: 0009 RDI: 6d612d7972616ef1 [ +0.45] RBP: 8800798e3998 R08: R09: [ +0.45] R10: 880075729060 R11: 8000 R12: 6d612d7972616ef1 [ +0.44] R13: 8800748aeaa8 R14: 880076399650 R15: [ +0.46] FS: 7f9a50ad9700() GS:88007b60() knlGS: [ +0.51] CS: 0010 DS: ES: CR0: 80050033 [ +0.37] CR2: 7f9a1d4f2000 CR3: 79936000 CR4: 00160670 [ +0.000160] Stack: [ +0.19] 8800798e39b8 8123953e 0009 8800748ae000 [ +0.55] 8800798e3a38 c057bb77 c053309a [ +0.54] 88007958e498 88007958e4e0 0001 88007958e3c8 [ +0.55] Call Trace: [ +0.25] [] igrab+0x1e/0x50 [ +0.84] [] ocfs2_get_system_file_inode+0x67/0x300 [ocfs2] [ +0.88] [] ? ocfs2_read_virt_blocks+0x1ca/0x310 [ocfs2] [ +0.72] [] ? dx_leaf_sort_swap+0x40/0x40 [ocfs2] [ +0.75] [] ocfs2_reserve_suballoc_bits+0x4e/0x430 [ocfs2] [ +0.74] [] ocfs2_steal_resource+0x9b/0x130 [ocfs2] [ +0.001659] [] ocfs2_reserve_new_inode+0xb5/0x370 [ocfs2] [ +0.001326] [] ocfs2_mknod+0x4be/0x10e0 [ocfs2] [ +0.001622] [] ? ocfs2_should_refresh_lock_res+0x113/0x160 [ocfs2] [ +0.001571] [] ocfs2_create+0x4c/0x160 [ocfs2] [ +0.001318] [] vfs_create+0x12d/0x190 [ +0.001218] [] path_openat+0x1232/0x1360 [ +0.001255] [] ? file_update_time+0xcc/0x110 [ +0.001167] [] do_filp_open+0x91/0x100 [ +0.001132] [] ? new_sync_write+0xa5/0xf0 [ +0.001131] [] ? __alloc_fd+0xc7/0x190 [ +0.001072] [] do_sys_open+0x138/0x2a0 [ +0.001040] [] SyS_open+0x1e/0x20 [ +0.001028] [] entry_SYSCALL_64_fastpath+0x22/0xd0 [ +0.001041] Code: e2 fe 8d 72 02 0f b7 f6 0f 1f 80 00 00 00 00 eb d2 66 90 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 55 48 89 e5 b8 00 00 02 00 0f c1 07 89 c2 c1 ea 10 66 39 c2 75 02 5d c3 41 89 d0 0f b7 [ +0.003174] RIP [] _raw_spin_lock+0xe/0x70 [ +0.001007] RSP [ +0.002867] ---[ end trace 6fd21d2a8e763939 ]--- - [Sep 4 03:56] (java,5847,1):ocfs2_reserve_suballoc_bits:796 ERROR: status = -22 [ +0.98] (java,5847,1):ocfs2_reserve_new_inode:1120 ERROR: status = -22 [ +0.47] (java,5847,1):ocfs2_reserve_new_inode:1132 ERROR: status = -22 [ +0.46] (java,5847,1):ocfs2_mknod:314 ERROR: status = -22 [ +0.49] (java,5847,1):ocfs2_mknod:499 ERROR: status = -22 [ +0.40] (java,5847,1):ocfs2_create:679 ERROR: status = -22 [ +8.987127] (java,2088,0):ocfs2_reserve_suballoc_bits:796 ERROR: status = -22 [ +0.93] (java,2088,0):ocfs2_reserve_new_inode:1120 ERROR: status = -22 [ +0.000146] (java,2088,0):ocfs2_reserve_new_inode:1132 ERROR: status = -22 [ +0.47] (java,2088,0):ocfs2_mknod:314
[Kernel-packages] [Bug 1894988] Re: ocfs2 crashing
filed against wrong kernel version. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1894988 Title: ocfs2 crashing Status in linux-signed package in Ubuntu: Invalid Bug description: a ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-176-generic 4.4.0-176.206 ProcVersionSignature: Ubuntu 4.4.0-176.206-generic 4.4.211 Uname: Linux 4.4.0-176-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.24 Architecture: amd64 Date: Wed Sep 9 12:48:41 2020 InstallationDate: Installed on 2016-10-21 (1418 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1894988/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1894988] [NEW] ocfs2 crashing
Public bug reported: a ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-176-generic 4.4.0-176.206 ProcVersionSignature: Ubuntu 4.4.0-176.206-generic 4.4.211 Uname: Linux 4.4.0-176-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.24 Architecture: amd64 Date: Wed Sep 9 12:48:41 2020 InstallationDate: Installed on 2016-10-21 (1418 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed (Ubuntu) Importance: Undecided Status: Invalid ** Tags: amd64 apport-bug xenial ** Changed in: linux-signed (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1894988 Title: ocfs2 crashing Status in linux-signed package in Ubuntu: Invalid Bug description: a ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-176-generic 4.4.0-176.206 ProcVersionSignature: Ubuntu 4.4.0-176.206-generic 4.4.211 Uname: Linux 4.4.0-176-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.24 Architecture: amd64 Date: Wed Sep 9 12:48:41 2020 InstallationDate: Installed on 2016-10-21 (1418 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1894988/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1861284] Re: Build and ship a signed wireguard.ko
** Tags added: verification-needed-xenial -- 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/1861284 Title: Build and ship a signed wireguard.ko Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: In Progress Status in linux source package in Eoan: Fix Released Bug description: .. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861284/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1881097] Re: [Thinkpad X1C7][Thinkpad X1C8]F1 and F4 Hotkey LED Light Stays ON/OFF when USB Headset is attached.
@Miguel, Thanks for the report of this issue. This is a known issue/limitation that the USB peripheral driver is not in sync of the Hotkey LED status. The Hotkey LED should connect to the audio codec by GPIO. We will check with the Desktop team to see if we can do some improvement in the future. -- 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/1881097 Title: [Thinkpad X1C7][Thinkpad X1C8]F1 and F4 Hotkey LED Light Stays ON/OFF when USB Headset is attached. Status in linux package in Ubuntu: Confirmed Bug description: Problem Description: Using Ubuntu 20.04 on a Thinkpad X1C7 machine. Speaker(F1) and Microphone(F4) Hotkey LED Light Stays ON/OFF when USB Headset is attached. - $ lsb_release -rd Description: Ubuntu 20.04 LTS Release: 20.04 Ubuntu Software: 3.36.1 - Expected Result: When LED light of Speaker(F1)/Microphone (F4) hotkeys is ON/OFF and then we connect USB Headset and press Speaker(F1)/Microphone (F4) hotkeys again -> LED light state will change accordingly. Actual Result: 1. When LED light of Speaker(F1)/Microphone (F4) hotkeys is OFF and then we connect USB Headset and press Speaker(F1)/Microphone (F4) hotkeys again -> LED light will STAY OFF and remains in OFF State always on the duration that the USB headset is attached to the machine. 2. If LED light of Speaker(F1)/Microphone (F4) hotkeys is ON and then we connect USB Headset and press Speaker(F1)/Microphone (F4) hotkeys again -> LED will STAY ON and remains in ON State on the duration that the USB headset is attached to the machine. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-33-generic 5.4.0-33.37 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1410 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu May 28 18:48:04 2020 InstallationDate: Installed on 2020-05-28 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 20U9SITR38 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=ab59da99-085b-4f8d-af14-4fc4240a8f83 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-33-generic N/A linux-backports-modules-5.4.0-33-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/12/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2WET11C (1.01C ) dmi.board.asset.tag: Not Available dmi.board.name: 20U9SITR38 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2WET11C(1.01C):bd02/12/2020:svnLENOVO:pn20U9SITR38:pvrThinkPadX1CarbonGen8:rvnLENOVO:rn20U9SITR38:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon Gen 8 dmi.product.name: 20U9SITR38 dmi.product.sku: LENOVO_MT_20U9_BU_Think_FM_ThinkPad X1 Carbon Gen 8 dmi.product.version: ThinkPad X1 Carbon Gen 8 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881097/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1861028] Re: Fan control stops working on resume for Dell Precision
This still happens on a fresh Focal install using linux- image-5.4.0-26-generic version 5.4.0-26.30 ** Also affects: linux-signed (Ubuntu) Importance: Undecided Status: New ** Tags removed: bionic ** Tags added: focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1861028 Title: Fan control stops working on resume for Dell Precision Status in linux-signed package in Ubuntu: New Status in linux-signed-hwe package in Ubuntu: New Bug description: This system is a Dell Precision Tower 3420 with the latest BIOS 2.13.1, kernel version is 5.3.0-26-generic (HWE, bionic) Freshly booting the system and doing something CPU intensive, like compiling a kernel, cause the CPU fan to ramp up as expected and the CPU temperatures remain acceptable. After suspending (ie Alt-clicking the power button in Unity) and then resuming, the CPU fan runs at a permanent low frequency and does not ramp up. Doing something like a kernel build causes the CPU to overheat and logs messages to dmesg. Investigating I see that the dell_smm_hwmon driver has a 'temp2' input that reflects the CPU temperature. Upon power up the value works properly, after resume it returns -ENODATA. The other sensor for CPU temperature (thermal_zone3/temp, x86_pkg_temp) still works correctly. Blacklisting the dell_smm_hwmon driver has no impact Dell Precisions are listed as compatible with Ubuntu, and this system was purchased with Ubuntu pre-installed from Dell, so it is surpsing something so basic isn't working? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.3.0-26-generic 5.3.0-26.28~18.04.1 ProcVersionSignature: Ubuntu 5.3.0-26.28~18.04.1-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jan 27 15:48:39 2020 InstallationDate: Installed on 2018-08-04 (540 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: linux-signed-hwe UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1861028/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1873288] Re: wireguard-tools should NOT recommend wireguard-dkms
All set now! zx2c4@thinkpad ~ $ curl -s http://archive.ubuntu.com/ubuntu/dists/focal-updates/main/binary-amd64/Packages.xz | unxz | grep -B11 Provides:.*wireguard | grep ^Package: Package: linux-image-aws Package: linux-image-azure Package: linux-image-gcp Package: linux-image-generic Package: linux-image-generic-hwe-20.04 Package: linux-image-gke Package: linux-image-kvm Package: linux-image-lowlatency Package: linux-image-lowlatency-hwe-20.04 Package: linux-image-oracle Package: linux-image-virtual Package: linux-image-virtual-hwe-20.04 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/1873288 Title: wireguard-tools should NOT recommend wireguard-dkms Status in linux-meta package in Ubuntu: Fix Released Status in wireguard package in Ubuntu: Confirmed Bug description: With 20.04, the wireguard-dkms is not strictly needed as the wireguard.ko is now shipped with kernel packages. # apt-cache show wireguard-tools | grep Recommends Recommends: nftables | iptables, wireguard-dkms (>= 0.0.20191219) | wireguard-modules (>= 0.0.20171001) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1873288/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1873288] Re: wireguard-tools should NOT recommend wireguard-dkms
Looks like it's still in -proposed, not -updates: zx2c4@thinkpad ~ $ curl -s http://archive.ubuntu.com/ubuntu/dists/focal-proposed/main/binary-amd64/Packages.xz | unxz | grep -B11 Provides:.*wireguard | grep ^Package: Package: linux-image-aws Package: linux-image-azure Package: linux-image-gcp Package: linux-image-generic Package: linux-image-generic-hwe-20.04 Package: linux-image-gke Package: linux-image-kvm Package: linux-image-lowlatency Package: linux-image-lowlatency-hwe-20.04 Package: linux-image-oracle Package: linux-image-virtual Package: linux-image-virtual-hwe-20.04 zx2c4@thinkpad ~ $ curl -s http://archive.ubuntu.com/ubuntu/dists/focal-updates/main/binary-amd64/Packages.xz | unxz | grep -B11 Provides:.*wireguard | grep ^Package: Package: linux-image-generic Package: linux-image-generic-hwe-20.04 Package: linux-image-lowlatency Package: linux-image-lowlatency-hwe-20.04 Package: linux-image-virtual Package: linux-image-virtual-hwe-20.04 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/1873288 Title: wireguard-tools should NOT recommend wireguard-dkms Status in linux-meta package in Ubuntu: Fix Released Status in wireguard package in Ubuntu: Confirmed Bug description: With 20.04, the wireguard-dkms is not strictly needed as the wireguard.ko is now shipped with kernel packages. # apt-cache show wireguard-tools | grep Recommends Recommends: nftables | iptables, wireguard-dkms (>= 0.0.20191219) | wireguard-modules (>= 0.0.20171001) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1873288/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1873288] Re: wireguard-tools should NOT recommend wireguard-dkms
Reopening this until we have some conclusion on (2) and (3) of #9. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/1873288 Title: wireguard-tools should NOT recommend wireguard-dkms Status in linux-meta package in Ubuntu: Fix Released Status in wireguard package in Ubuntu: Confirmed Bug description: With 20.04, the wireguard-dkms is not strictly needed as the wireguard.ko is now shipped with kernel packages. # apt-cache show wireguard-tools | grep Recommends Recommends: nftables | iptables, wireguard-dkms (>= 0.0.20191219) | wireguard-modules (>= 0.0.20171001) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1873288/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1873288] Re: wireguard-tools should NOT recommend wireguard-dkms
Ah, looks like I can't. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/1873288 Title: wireguard-tools should NOT recommend wireguard-dkms Status in linux-meta package in Ubuntu: Fix Released Status in wireguard package in Ubuntu: Confirmed Bug description: With 20.04, the wireguard-dkms is not strictly needed as the wireguard.ko is now shipped with kernel packages. # apt-cache show wireguard-tools | grep Recommends Recommends: nftables | iptables, wireguard-dkms (>= 0.0.20191219) | wireguard-modules (>= 0.0.20171001) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1873288/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1873288] Re: wireguard-tools should NOT recommend wireguard-dkms
Simon - to keep you updated on the bug you reported, this fixes issue (1), as described in comment #9: https://git.launchpad.net/~ubuntu- kernel/ubuntu/+source/linux- meta/+git/focal/commit/?id=204fb3b2ae6b0c8c41c339f47949b45d571c4953 We'll keep this open until there's a decision/fix on (2) and (3), as described in comment #9. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/1873288 Title: wireguard-tools should NOT recommend wireguard-dkms Status in linux-meta package in Ubuntu: In Progress Status in wireguard package in Ubuntu: Confirmed Bug description: With 20.04, the wireguard-dkms is not strictly needed as the wireguard.ko is now shipped with kernel packages. # apt-cache show wireguard-tools | grep Recommends Recommends: nftables | iptables, wireguard-dkms (>= 0.0.20191219) | wireguard-modules (>= 0.0.20171001) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1873288/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1870746] Re: System froze during suspension since Linux kernel v5.3.0-42.
I know that suspension works on kernel v5.3.0-40. -- 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/1870746 Title: System froze during suspension since Linux kernel v5.3.0-42. Status in linux package in Ubuntu: Incomplete Bug description: Hello, I found that my system froze during the suspension process since Linux kernel v5.3.0-42. When the display switches to a blank terminal with a cursor on the top-left corner, the system got stuck. Sometimes I was able to switch to a virtual TTY with Control+Alt+[F2-F7], but it got stuck as well within a few seconds. Also, I've noticed that the backlight of my keyboard stays on indefinitely after the system froze, even though I've set a timeout for it to turn off. I've tried the ways to debug system crash mentioned in the Community Help Wiki, but with no luck. But it seems that I was able to connect to my computer via SSH if I was not connected to it before it froze, otherwise the SSH server will freeze as well. After some investigation, I found some information in "/var/log/syslog" that might be useful. I've found that "systemd- sleep[5261]: Suspending system..." was the last message that was logged to that file if the system froze, although there might be one more random or garbage message follow it. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] 是個目錄: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2) ApportVersion: 2.20.11-0ubuntu8.7 Architecture: amd64 BootLog: Error: [Errno 13] 拒絕不符權限的操作: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: KDE Date: Sat Apr 4 16:08:25 2020 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.3.0-40-generic, x86_64: installed nvidia, 435.21, 5.3.0-42-generic, x86_64: installed nvidia, 435.21, 5.3.0-45-generic, x86_64: installed ExtraDebuggingInterest: I just need to know a workaround (Update: Yes, if it's not too technical) GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 630 (Mobile) [1028:0922] Subsystem: Dell Device [1028:0922] InstallationDate: Installed on 2019-10-20 (166 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0bda:5538 Realtek Semiconductor Corp. Integrated_Webcam_HD Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 7590 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic root=UUID=4ddf851b-8d25-493d-92b4-e10623bc1531 ro quiet splash nouveau.modeset=0 vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/22/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.0 dmi.board.name: 0JKGD4 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.0:bd07/22/2019:svnDellInc.:pnInspiron7590:pvr:rvnDellInc.:rn0JKGD4:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 7590 dmi.product.sku: 0922 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~19.10.3 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1870746/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.ne
[Kernel-packages] [Bug 1856539] Re: wireguard package doesn't work on ubuntu eon
The Ubuntu kernel team seems to be behind in deploying a fix for this. In the interim you can solve this by using the WireGuard project's PPA, which now has backports for 19.10. Run this command to fix your issue: sudo add-apt-repository ppa:wireguard/wireguard && sudo apt-get update && sudo apt-get upgrade -- 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/1856539 Title: wireguard package doesn't work on ubuntu eon Status in linux package in Ubuntu: Incomplete Bug description: After upgrading to ubuntu eon, i've tried to install wireguard. Install went well but wireguard module can't be loaded and so wireguard can't be used. Ubuntu version: 19.10 Wireguard version: 0.0.20190913-1ubuntu1 When trying to use wireguard: > sudo systemctl start wg-quick@wg0.service Job for wg-quick@wg0.service failed because the control process exited with error code. See "systemctl status wg-quick@wg0.service" and "journalctl -xe" for details. 10:19:32 ~/ (feat/start-vm-choose-power-state u=) > systemctl status wg-quick@wg0.service ● wg-quick@wg0.service - WireGuard via wg-quick(8) for wg0 Loaded: loaded (/lib/systemd/system/wg-quick@.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Mon 2019-12-16 10:19:32 CET; 5s ago Docs: man:wg-quick(8) man:wg(8) https://www.wireguard.com/ https://www.wireguard.com/quickstart/ https://git.zx2c4.com/WireGuard/about/src/tools/man/wg-quick.8 https://git.zx2c4.com/WireGuard/about/src/tools/man/wg.8 Process: 31063 ExecStart=/usr/bin/wg-quick up wg0 (code=exited, status=1/FAILURE) Main PID: 31063 (code=exited, status=1/FAILURE) déc. 16 10:19:32 benjamin-XPS-13-9370 systemd[1]: Starting WireGuard via wg-quick(8) for wg0... déc. 16 10:19:32 benjamin-XPS-13-9370 wg-quick[31063]: Warning: `/etc/wireguard/wg0.conf' is world accessible déc. 16 10:19:32 benjamin-XPS-13-9370 wg-quick[31063]: [#] ip link add wg0 type wireguard déc. 16 10:19:32 benjamin-XPS-13-9370 wg-quick[31063]: RTNETLINK answers: Operation not supported déc. 16 10:19:32 benjamin-XPS-13-9370 wg-quick[31063]: Unable to access interface: Protocol not supported déc. 16 10:19:32 benjamin-XPS-13-9370 wg-quick[31063]: [#] ip link delete dev wg0 déc. 16 10:19:32 benjamin-XPS-13-9370 wg-quick[31063]: Cannot find device "wg0" déc. 16 10:19:32 benjamin-XPS-13-9370 systemd[1]: wg-quick@wg0.service: Main process exited, code=exited, status=1/FAILURE déc. 16 10:19:32 benjamin-XPS-13-9370 systemd[1]: wg-quick@wg0.service: Failed with result 'exit-code'. déc. 16 10:19:32 benjamin-XPS-13-9370 systemd[1]: Failed to start WireGuard via wg-quick(8) for wg0. When trying to load wireguard module: > sudo modprobe wireguard modprobe: ERROR: could not insert 'wireguard': Exec format error I'm happy to provide more info if needed. Any help would be greatly appreciated! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856539/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1851295] Re: dkms error with wireguard on upgrafe to 19.10
Seems dkms related. ** Package changed: wireguard (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/1851295 Title: dkms error with wireguard on upgrafe to 19.10 Status in linux package in Ubuntu: Confirmed Bug description: Loading new wireguard-0.0.20190913 DKMS files... Building for 5.0.0-27-generic 5.3.0-19-generic Building initial module for 5.0.0-27-generic ERROR (dkms apport): kernel package linux-headers-5.0.0-27-generic is not supported Error! Bad return status for module build on kernel: 5.0.0-27-generic (x86_64) Consult /var/lib/dkms/wireguard/0.0.20190913/build/make.log for more information. dpkg: error processing package wireguard-dkms (--configure): installed wireguard-dkms package post-installation script subprocess returned error exit status 10 dpkg: dependency problems prevent configuration of wireguard: wireguard depends on wireguard-dkms (= 0.0.20190913-1ubuntu1) | wireguard-modules (= 0.0.20190913); however: Package wireguard-dkms is not configured yet. Package wireguard-modules is not installed. dpkg: error processing package wireguard (--configure): dependency problems - leaving unconfigured Errors were encountered while processing: wireguard-dkms wireguard ProblemType: Package DistroRelease: Ubuntu 19.10 Package: wireguard-dkms 0.0.20190913-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-27.28-generic 5.0.21 Uname: Linux 5.0.0-27-generic x86_64 NonfreeKernelModules: wireguard ApportVersion: 2.20.11-0ubuntu8.1 Architecture: amd64 Date: Mon Nov 4 23:58:10 2019 ErrorMessage: installed wireguard-dkms package post-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2018-10-12 (388 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all Python3Details: /usr/bin/python3.7, Python 3.7.5rc1, python3-minimal, 3.7.5-1 PythonDetails: /usr/bin/python2.7, Python 2.7.17rc1, python-minimal, 2.7.17-1 RelatedPackageVersions: dpkg 1.19.7ubuntu2 apt 1.9.4 SourcePackage: wireguard Title: package wireguard-dkms 0.0.20190913-1ubuntu1 failed to install/upgrade: installed wireguard-dkms package post-installation script subprocess returned error exit status 10 UpgradeStatus: Upgraded to eoan on 2019-11-04 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1851295/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1856539] Re: wireguard package doesn't work on ubuntu eon
[ 15.589541] module: x86/modules: Skipping invalid relocation target, existing value is nonzero for type 1, loc f4677a21, val c1171b82 Looks like a dkms issue? Thankfully we won't need that for 20.04 and also earlier kernels once things are backported. I'll reassign this to the canonical kernel people. ** Package changed: wireguard (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/1856539 Title: wireguard package doesn't work on ubuntu eon Status in linux package in Ubuntu: Incomplete Bug description: After upgrading to ubuntu eon, i've tried to install wireguard. Install went well but wireguard module can't be loaded and so wireguard can't be used. Ubuntu version: 19.10 Wireguard version: 0.0.20190913-1ubuntu1 When trying to use wireguard: > sudo systemctl start wg-quick@wg0.service Job for wg-quick@wg0.service failed because the control process exited with error code. See "systemctl status wg-quick@wg0.service" and "journalctl -xe" for details. 10:19:32 ~/ (feat/start-vm-choose-power-state u=) > systemctl status wg-quick@wg0.service ● wg-quick@wg0.service - WireGuard via wg-quick(8) for wg0 Loaded: loaded (/lib/systemd/system/wg-quick@.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Mon 2019-12-16 10:19:32 CET; 5s ago Docs: man:wg-quick(8) man:wg(8) https://www.wireguard.com/ https://www.wireguard.com/quickstart/ https://git.zx2c4.com/WireGuard/about/src/tools/man/wg-quick.8 https://git.zx2c4.com/WireGuard/about/src/tools/man/wg.8 Process: 31063 ExecStart=/usr/bin/wg-quick up wg0 (code=exited, status=1/FAILURE) Main PID: 31063 (code=exited, status=1/FAILURE) déc. 16 10:19:32 benjamin-XPS-13-9370 systemd[1]: Starting WireGuard via wg-quick(8) for wg0... déc. 16 10:19:32 benjamin-XPS-13-9370 wg-quick[31063]: Warning: `/etc/wireguard/wg0.conf' is world accessible déc. 16 10:19:32 benjamin-XPS-13-9370 wg-quick[31063]: [#] ip link add wg0 type wireguard déc. 16 10:19:32 benjamin-XPS-13-9370 wg-quick[31063]: RTNETLINK answers: Operation not supported déc. 16 10:19:32 benjamin-XPS-13-9370 wg-quick[31063]: Unable to access interface: Protocol not supported déc. 16 10:19:32 benjamin-XPS-13-9370 wg-quick[31063]: [#] ip link delete dev wg0 déc. 16 10:19:32 benjamin-XPS-13-9370 wg-quick[31063]: Cannot find device "wg0" déc. 16 10:19:32 benjamin-XPS-13-9370 systemd[1]: wg-quick@wg0.service: Main process exited, code=exited, status=1/FAILURE déc. 16 10:19:32 benjamin-XPS-13-9370 systemd[1]: wg-quick@wg0.service: Failed with result 'exit-code'. déc. 16 10:19:32 benjamin-XPS-13-9370 systemd[1]: Failed to start WireGuard via wg-quick(8) for wg0. When trying to load wireguard module: > sudo modprobe wireguard modprobe: ERROR: could not insert 'wireguard': Exec format error I'm happy to provide more info if needed. Any help would be greatly appreciated! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856539/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1854225] Re: Kernel oops and system lock up when invoking wg-quick up
Doesn't look like a WireGuard bug. ** Package changed: wireguard (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/1854225 Title: Kernel oops and system lock up when invoking wg-quick up Status in linux package in Ubuntu: Incomplete Bug description: On 2 occasions over the past week I have had full system crashes after running "wg-quick up wg0". On the terminal, the command does not complete (i.e. it does not return to the prompt), the fans on my laptop start whirring and the system gradually becomes unresponsive before my desktop crashes and the system becomes completely unresponsive. On both occasions I opened another window to run "top" to see what process was consuming resources but "top" never actually runs. On the second occasion I managed to run "dmesg" before the system crashed completely and saw multiple lines of text about a kernel oops and red-highlighted text about a null-pointer dereference. I could reboot with "Alt-PrtScr_REISUB". On reboot I was confronted with the "system problem detected" dialog, but selecting the "report" option didn't seem to do anything. I have 2 reports in /var/crash from the last oops which I will attach to this report. I cannot reproduce this on demand. Most of the time, wg-quick performs normally. On both occasions the laptop had recently woken from suspend, but invoking "wg-quick" after waking from suspend doesn't trigger it on demand. On the first occasion I was running with stock boot options. On the second, I was running with "mitigations=off" as an experiment. $ lsb_release -rd Description: Ubuntu 19.10 Release: 19.10 $ apt policy wireguard wireguard: Installed: 0.0.20190913-1ubuntu1 Candidate: 0.0.20190913-1ubuntu1 Version table: *** 0.0.20190913-1ubuntu1 500 500 http://gb.archive.ubuntu.com/ubuntu eoan/universe amd64 Packages 500 http://gb.archive.ubuntu.com/ubuntu eoan/universe i386 Packages 100 /var/lib/dpkg/status $ apt policy wireguard-tools wireguard-tools: Installed: 0.0.20190913-1ubuntu1 Candidate: 0.0.20190913-1ubuntu1 Version table: *** 0.0.20190913-1ubuntu1 500 500 http://gb.archive.ubuntu.com/ubuntu eoan/universe amd64 Packages 100 /var/lib/dpkg/status $ uname -a Linux padbeast 5.3.0-23-generic #25-Ubuntu SMP Tue Nov 12 09:22:33 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux # cat /etc/wireguard/wg0.conf [Interface] PrivateKey = MyPrivateKey= Address = 10.66.66.5/24,fd42:42:42::5/64 DNS = 8.8.8.8,1.1.1.1 [Peer] PublicKey = MyPublicKey= Endpoint = my.domain.com:1195 AllowedIPs = 0.0.0.0/0,::/0 I'm reporting this as a security bug due to the "Null pointer dereference" in the kernel, but don't know if that is relevant. I don't know how to access or send the old dmesg information, so please let me know how to access this or how to collect it if the crash recurs. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: wireguard 0.0.20190913-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: MATE Date: Wed Nov 27 20:44:24 2019 InstallationDate: Installed on 2019-10-11 (47 days ago) InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Beta amd64 (20190926.2) PackageArchitecture: all SourcePackage: wireguard UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1854225/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1858807] Re: Wireguard install fails on 19.10
The kernel team can backport things need be. ** Package changed: wireguard (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/1858807 Title: Wireguard install fails on 19.10 Status in linux package in Ubuntu: Incomplete Bug description: # apt install wireguard-tools Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: wireguard-dkms The following NEW packages will be installed: wireguard-dkms wireguard-tools 0 upgraded, 2 newly installed, 0 to remove and 0 not upgraded. Need to get 0 B/330 kB of archives. After this operation, 2,126 kB of additional disk space will be used. Do you want to continue? [Y/n] Y Selecting previously unselected package wireguard-dkms. (Reading database ... 298438 files and directories currently installed.) Preparing to unpack .../wireguard-dkms_0.0.20190913-1ubuntu1_all.deb ... Unpacking wireguard-dkms (0.0.20190913-1ubuntu1) ... Selecting previously unselected package wireguard-tools. Preparing to unpack .../wireguard-tools_0.0.20190913-1ubuntu1_amd64.deb ... Unpacking wireguard-tools (0.0.20190913-1ubuntu1) ... Setting up wireguard-dkms (0.0.20190913-1ubuntu1) ... Loading new wireguard-0.0.20190913 DKMS files... Building for 5.5.0-050500rc5-generic Building initial module for 5.5.0-050500rc5-generic ERROR (dkms apport): kernel package linux-headers-5.5.0-050500rc5-generic is not supported Error! Bad return status for module build on kernel: 5.5.0-050500rc5-generic (x86_64) Consult /var/lib/dkms/wireguard/0.0.20190913/build/make.log for more information. dpkg: error processing package wireguard-dkms (--configure): installed wireguard-dkms package post-installation script subprocess returned error exit status 10 Setting up wireguard-tools (0.0.20190913-1ubuntu1) ... Processing triggers for man-db (2.8.7-3) ... Errors were encountered while processing: wireguard-dkms E: Sub-process /usr/bin/dpkg returned an error code (1) make.log: - KMS make.log for wireguard-0.0.20190913 for kernel 5.5.0-050500rc5-generic (x86_64) Wed 08 Jan 2020 03:43:59 PM CET make: Entering directory '/usr/src/linux-headers-5.5.0-050500rc5-generic' AR /var/lib/dkms/wireguard/0.0.20190913/build/built-in.a CC [M] /var/lib/dkms/wireguard/0.0.20190913/build/main.o CC [M] /var/lib/dkms/wireguard/0.0.20190913/build/noise.o CC [M] /var/lib/dkms/wireguard/0.0.20190913/build/device.o CC [M] /var/lib/dkms/wireguard/0.0.20190913/build/peer.o CC [M] /var/lib/dkms/wireguard/0.0.20190913/build/timers.o CC [M] /var/lib/dkms/wireguard/0.0.20190913/build/queueing.o CC [M] /var/lib/dkms/wireguard/0.0.20190913/build/send.o CC [M] /var/lib/dkms/wireguard/0.0.20190913/build/receive.o CC [M] /var/lib/dkms/wireguard/0.0.20190913/build/socket.o CC [M] /var/lib/dkms/wireguard/0.0.20190913/build/peerlookup.o CC [M] /var/lib/dkms/wireguard/0.0.20190913/build/allowedips.o CC [M] /var/lib/dkms/wireguard/0.0.20190913/build/ratelimiter.o CC [M] /var/lib/dkms/wireguard/0.0.20190913/build/cookie.o CC [M] /var/lib/dkms/wireguard/0.0.20190913/build/netlink.o CC [M] /var/lib/dkms/wireguard/0.0.20190913/build/crypto/zinc/chacha20/chacha20.o PERLASM /var/lib/dkms/wireguard/0.0.20190913/build/crypto/zinc/chacha20/chacha20-x86_64.S CC [M] /var/lib/dkms/wireguard/0.0.20190913/build/crypto/zinc/poly1305/poly1305.o /var/lib/dkms/wireguard/0.0.20190913/build/socket.c: In function ‘send6’: /var/lib/dkms/wireguard/0.0.20190913/build/socket.c:145:20: error: ‘const struct ipv6_stub’ has no member named ‘ipv6_dst_lookup’; did you mean ‘ipv6_dst_lookup_flow’? 145 | ret = ipv6_stub->ipv6_dst_lookup(sock_net(sock), sock, &dst, |^~~ |ipv6_dst_lookup_flow make[1]: *** [scripts/Makefile.build:266: /var/lib/dkms/wireguard/0.0.20190913/build/socket.o] Error 1 make[1]: *** Waiting for unfinished jobs /var/lib/dkms/wireguard/0.0.20190913/build/netlink.c: In function ‘wg_get_device_start’: /var/lib/dkms/wireguard/0.0.20190913/build/netlink.c:199:26: error: implicit declaration of function ‘genl_family_attrbuf’ [-Werror=implicit-function-declaration] 199 | struct nlattr **attrs = genl_family_attrbuf(&genl_family); | ^~~ /var/lib/dkms/wireguard/0.0.20190913/build/netlink.c:199:26: warning: initialization of ‘struct nlattr **’ from ‘int’ makes pointer from integer without a cast [-Wint-conversion] cc1: some warnings being treated as errors make[1]: *** [scripts/Makefile.build:265: /var/lib/
[Kernel-packages] [Bug 1845046] Re: Bluetooth headphones/speaker such as Sony WH-1000XM3 default to low quality headset mode and fails to switch to A2DP when selected
Applying the patch fixed my problem with my Sony WH-H900N headphones. Probably a different bug but if I open Sound Settings -> Input and change the input from "Internal Microphone Built-in Audio" to "Headset WH-H900N (h.ear)" the quality degrades and the Output profile changes to "Headset Head Unit (HSP/HFP)". If I change the Output profile back to "High Fidelity Playback (A2DP Sink)" I get high quality audio again but the Input changes back to "Internal Microphone Built-in Audio". Or is it that you can't use the headset microphone and get high quality audio at the same time? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1845046 Title: Bluetooth headphones/speaker such as Sony WH-1000XM3 default to low quality headset mode and fails to switch to A2DP when selected Status in PulseAudio: Unknown Status in bluez package in Ubuntu: Fix Released Status in gnome-control-center package in Ubuntu: Invalid Status in pulseaudio package in Ubuntu: Invalid Bug description: Whenever I turn on my headphones theyll connect to my computer but im able to hear the input audio from my microphone and low quality output audio. I have to disconnect the headphones in the bluetooth devices and reconnect for it to fix the problem. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.2 ProcVersionSignature: Ubuntu 5.0.0-29.31~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: litleck1398 F pulseaudio /dev/snd/controlC0: litleck1398 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Sep 23 17:07:59 2019 InstallationDate: Installed on 2019-09-22 (0 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio Symptom_Card: WH-1000XM3 Symptom_Type: High background noise, or volume is too low Title: [WH-1000XM3, playback] Background noise or low volume UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/12/2019 dmi.bios.vendor: Alienware dmi.bios.version: 1.0.19 dmi.board.name: 01NYPT dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Alienware dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnAlienware:bvr1.0.19:bd02/12/2019:svnAlienware:pnAlienwareAuroraR5:pvr1.0.19:rvnAlienware:rn01NYPT:rvrA00:cvnAlienware:ct3:cvrNotSpecified: dmi.product.family: Alienware dmi.product.name: Alienware Aurora R5 dmi.product.sku: 0729 dmi.product.version: 1.0.19 dmi.sys.vendor: Alienware To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1845046/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1849890] Re: Please add brcmfmac43430a0-sdio.bin to linux-firmware
Excellent news. Feel free to close this bug after adding the new txt file you mentioned. Thank you for getting to this bug. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1849890 Title: Please add brcmfmac43430a0-sdio.bin to linux-firmware Status in linux-firmware package in Ubuntu: Incomplete Bug description: brcm/brcmfmac43430a0-* is needed to be added to the firmware bundle. This will make devices such as Acer One 10 (S1003) have working bluetooth and WiFi, which is always a good thing to have when booting off a tablet via live image. Stuff to comply with bug reporting guidelines: $ cat /proc/version_signature > version.log cat: /proc/version_signature: No such file or directory $ cat /proc/version Linux version 5.4.0-050400rc4-generic (kernel@kathleen) (gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2)) #201910202130 SMP Sun Oct 20 21:32:54 UTC 2019 $ lsb_release -rd Description:Ubuntu 19.10 Release:19.10 $ apt-cache policy linux-firmware linux-firmware: Installed: 1.183.1 Candidate: 1.183.1 Version table: *** 1.183.1 500 500 http://us.archive.ubuntu.com/ubuntu eoan-updates/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu eoan-updates/main i386 Packages 500 http://security.ubuntu.com/ubuntu eoan-security/main amd64 Packages 500 http://security.ubuntu.com/ubuntu eoan-security/main i386 Packages 100 /var/lib/dpkg/status 1.183 500 500 http://us.archive.ubuntu.com/ubuntu eoan/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu eoan/main i386 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1849890/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1766076] Re: USB over thunderbolt turns off every once in a while
The lastest journal log I saw right when I lost connectivity to HDMI and ethernet follows. There was no other logs associated. No clue if this is relevant. Nov 14 14:52:32 deimos kernel: perf: interrupt took too long (4998 > 4990), lowering kernel.perf_event_max_sample_rate to 4 -- 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/1766076 Title: USB over thunderbolt turns off every once in a while Status in Dell Sputnik: New Status in linux package in Ubuntu: Incomplete Bug description: I'm using a USB hub in the Dell TB16 (240W) connected to a Dell Precision 5520 using Thunderbolt 3. Every so often (can be several times in an hour if I'm really unlucky, some days it is less of a problem), the USB hub disconnects from the computer and the devices connected to it lose power and stop responding. disconnecting and reconnecting the USB cables has no effect. I can restore functionality by instructing the xhci_hcd driver to unbind from the USB 3.0 Host Controller in the dock and to rebind to it using the commands: echo -n ":0e:00.0" > /sys/bus/pci/drivers/xhci_hcd/unbind echo -n ":0e:00.0" > /sys/bus/pci/drivers/xhci_hcd/bind Here's the dmesg output when the USB hub disconnects: 279278.102701] xhci_hcd :0e:00.0: ERROR unknown event type 15 [279283.021802] xhci_hcd :0e:00.0: xHCI host not responding to stop endpoint command. [279283.022145] xhci_hcd :0e:00.0: xHCI host controller not responding, assume dead [279283.022161] r8152 4-1.2:1.0 enxd481d731b2b1: Tx status -108 [279283.022199] xhci_hcd :0e:00.0: HC died; cleaning up [279283.07] usb 3-1.5: Failed to suspend device, error -22 [279283.022234] usb 3-1: USB disconnect, device number 2 [279283.022235] usb 3-1.1: USB disconnect, device number 3 [279283.022236] usb 3-1.1.1: USB disconnect, device number 5 [279283.022237] usb 3-1.1.1.1: USB disconnect, device number 8 [279283.022238] usb 3-1.1.1.1.4: USB disconnect, device number 11 [279283.022326] usb 4-1: USB disconnect, device number 2 [279283.022328] usb 4-1.1: USB disconnect, device number 3 [279283.022329] usb 4-1.1.1: USB disconnect, device number 5 [279283.022998] usb 4-1.2: USB disconnect, device number 4 [279283.191217] usb 3-1.1.1.5: USB disconnect, device number 9 [279283.191730] usb 3-1.1.3: USB disconnect, device number 6 [279283.260810] usb 3-1.1.5: USB disconnect, device number 7 [279283.261350] usb 3-1.5: USB disconnect, device number 4 Here's dmesg output during the USB host controller reset: 279389.813889] xhci_hcd :0e:00.0: remove, state 1 [279389.813894] usb usb4: USB disconnect, device number 1 [279389.814103] xhci_hcd :0e:00.0: USB bus 4 deregistered [279389.814107] xhci_hcd :0e:00.0: remove, state 1 [279389.814110] usb usb3: USB disconnect, device number 1 [279389.881651] xhci_hcd :0e:00.0: USB bus 3 deregistered [279389.882133] xhci_hcd :0e:00.0: xHCI Host Controller [279389.882138] xhci_hcd :0e:00.0: new USB bus registered, assigned bus number 3 [279389.949391] xhci_hcd :0e:00.0: hcc params 0x0200e081 hci version 0x100 quirks 0x1410 [279389.949979] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002 [279389.949981] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [279389.949982] usb usb3: Product: xHCI Host Controller [279389.949983] usb usb3: Manufacturer: Linux 4.15.0-15-generic xhci-hcd
[Kernel-packages] [Bug 1766076] Re: USB over thunderbolt turns off every once in a while
Dell Precision 5530 Latest 5530 BIOS (1.13.0) ikling usb-c hub 5.0.0-32-generic I dont think this has anything to do with the Dell HUB as noted above Im not using it but some off brand. Using ethernet, hdmi and one usb 3.0 port. I see the screen attached every 30 minutes or so go blank then become active within a second or two. At this time I also lose network and the USB. All devices come back but it disrupts vpn connections. Its extremely problematic. This is also connected to a usb kvm switch which I use to flip between the two systems. I have not noticed this bouncing back and forth to be related so I dont think disconnects of usb devices impact it. I see similar logs as those posting above. -- 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/1766076 Title: USB over thunderbolt turns off every once in a while Status in Dell Sputnik: New Status in linux package in Ubuntu: Incomplete Bug description: I'm using a USB hub in the Dell TB16 (240W) connected to a Dell Precision 5520 using Thunderbolt 3. Every so often (can be several times in an hour if I'm really unlucky, some days it is less of a problem), the USB hub disconnects from the computer and the devices connected to it lose power and stop responding. disconnecting and reconnecting the USB cables has no effect. I can restore functionality by instructing the xhci_hcd driver to unbind from the USB 3.0 Host Controller in the dock and to rebind to it using the commands: echo -n ":0e:00.0" > /sys/bus/pci/drivers/xhci_hcd/unbind echo -n ":0e:00.0" > /sys/bus/pci/drivers/xhci_hcd/bind Here's the dmesg output when the USB hub disconnects: 279278.102701] xhci_hcd :0e:00.0: ERROR unknown event type 15 [279283.021802] xhci_hcd :0e:00.0: xHCI host not responding to stop endpoint command. [279283.022145] xhci_hcd :0e:00.0: xHCI host controller not responding, assume dead [279283.022161] r8152 4-1.2:1.0 enxd481d731b2b1: Tx status -108 [279283.022199] xhci_hcd :0e:00.0: HC died; cleaning up [279283.07] usb 3-1.5: Failed to suspend device, error -22 [279283.022234] usb 3-1: USB disconnect, device number 2 [279283.022235] usb 3-1.1: USB disconnect, device number 3 [279283.022236] usb 3-1.1.1: USB disconnect, device number 5 [279283.022237] usb 3-1.1.1.1: USB disconnect, device number 8 [279283.022238] usb 3-1.1.1.1.4: USB disconnect, device number 11 [279283.022326] usb 4-1: USB disconnect, device number 2 [279283.022328] usb 4-1.1: USB disconnect, device number 3 [279283.022329] usb 4-1.1.1: USB disconnect, device number 5 [279283.022998] usb 4-1.2: USB disconnect, device number 4 [279283.191217] usb 3-1.1.1.5: USB disconnect, device number 9 [279283.191730] usb 3-1.1.3: USB disconnect, device number 6 [279283.260810] usb 3-1.1.5: USB disconnect, device number 7 [279283.261350] usb 3-1.5: USB disconnect, device number 4 Here's dmesg output during the USB host controller reset: 279389.813889] xhci_hcd :0e:00.0: remove, state 1 [279389.813894] usb usb4: USB disconnect, device number 1 [279389.814103] xhci_hcd :0e:00.0: USB bus 4 deregistered [279389.814107] xhci_hcd :0e:00.0: remove, state 1 [279389.814110] usb usb3: USB disconnect, device number 1 [279389.881651] xhci_hcd :0e:00.0: USB bus 3 deregistered [279389.882133] xhci_hcd :0e:00.0: xHCI Host Controller [279389.882138] xhci_hcd :0e:00.0: new USB bus registered, assigned bus number 3 [279389.949391] xhci_hcd :0e:00.0: hcc params 0x0200e081 hci version 0x100 quirks 0x1410 [279389.949979] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002 [279389.949981] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[Kernel-packages] [Bug 1849720] Re: KVM with e1000e and WinGuest Host OS on kernel 5.3 (ok with 5.0)
I can confirm this issue with Eoan Ermine (5.3.0-19-generic). I tried disabling AppArmor (security_driver=none), but my laptop still locks up at the Windows login screen (Windows 10). Using the virtio NIC does work around the problem though. (root) ~ uname -a Linux pi.aqdx.us 5.3.0-19-generic #20-Ubuntu SMP Fri Oct 18 09:04:39 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux (root) ~ lscpu Architecture:x86_64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian Address sizes: 39 bits physical, 48 bits virtual CPU(s): 4 On-line CPU(s) list: 0-3 Thread(s) per core: 2 Core(s) per socket: 2 Socket(s): 1 NUMA node(s):1 Vendor ID: GenuineIntel CPU family: 6 Model: 142 Model name: Intel(R) Core(TM) i7-7500U CPU @ 2.70GHz Stepping:9 CPU MHz: 2070.601 CPU max MHz: 3500. CPU min MHz: 400. BogoMIPS:5799.77 Virtualization: VT-x L1d cache: 64 KiB L1i cache: 64 KiB L2 cache:512 KiB L3 cache:4 MiB NUMA node0 CPU(s): 0-3 Vulnerability L1tf: Mitigation; PTE Inversion; VMX conditional cache flushes, SMT vulnerable Vulnerability Mds: Mitigation; Clear CPU buffers; SMT vulnerable Vulnerability Meltdown: Mitigation; PTI Vulnerability Spec store bypass: Mitigation; Speculative Store Bypass disabled via prctl and seccomp Vulnerability Spectre v1:Mitigation; usercopy/swapgs barriers and __user pointer sanitization Vulnerability Spectre v2:Mitigation; Full generic retpoline, IBPB conditional, IBRS_FW, STIBP conditional, RSB filling Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx est t m2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch cpuid_fault epb invpcid_single pti ssbd ibrs ibpb stibp tpr_shadow vnmi flexpriority ept vpid ept_ad fsgsbase tsc_adjust bmi1 avx2 smep bmi2 er ms invpcid mpx rdseed adx smap clflushopt intel_pt xsaveopt xsavec xgetbv1 xsaves dtherm ida arat pln pts hwp hwp_notify hwp_act_window hwp_epp md_clear flush_l1d I've been able to re-create the same issue using mainline (5.3.9-050309-generic). Has anybody bisected kernel versions yet? -- 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/1849720 Title: KVM with e1000e and WinGuest Host OS on kernel 5.3 (ok with 5.0) Status in linux package in Ubuntu: Confirmed Status in qemu package in Ubuntu: In Progress Bug description: After upgrading to Ubuntu 19.10 I noticed that all of my Windows Servers VMs would cause a hard crash on the Host OS shortly after starting up the VM. I tracked it down to the Guest OS attempting to use the Network Connection, and if I disabled the virtual NIC for the VM, everything runs OK (albeit without a working network connection for the Guest OS). Note that I'm just using the built in virtual network called "default" that get's installed by default and uses NAT forwarding. I believe the problem is related to AppArmor, as I noticed some errors present in various log files. Unfortunately, due to a time critical project I had to roll back to Ubuntu 19.04 and didn't capture any of the log files. I did, however, find another user on Reddit with the exact same problems that I encountered and he agreed to let me post the log files. Here are what are think are the relevant pieces from the log files: === Oct 22 22:59:23 brian-pc dnsmasq[2178]: exiting on receipt of SIGTERM Oct 22 22:59:23 brian-pc kernel: [ 67.001284] device virbr0-nic left promiscuous mode Oct 22 22:59:23 brian-pc kernel: [ 67.001298] virbr0: port 1(virbr0-nic) entered disabled state Oct 22 22:59:23 brian-pc NetworkManager[3557]: [1571799563.3862] device (virbr0-nic): released from master device virbr0 Oct 22 22:59:23 brian-pc gnome-shell[4401]: Removing a network device that was not added Oct 22 22:59:23 brian-pc gnome-shell[2463]: Removing a network device that was not added Oct 22 22:59:23 brian-pc avahi-daemon[1621]: Interface virbr0.IPv4 no longer
[Kernel-packages] [Bug 1849890] [NEW] Please add brcmfmac43430a0-sdio.bin to linux-firmware
Public bug reported: brcm/brcmfmac43430a0-* is needed to be added to the firmware bundle. This will make devices such as Acer One 10 (S1003) have working bluetooth and WiFi, which is always a good thing to have when booting off a tablet via live image. Stuff to comply with bug reporting guidelines: $ cat /proc/version_signature > version.log cat: /proc/version_signature: No such file or directory $ cat /proc/version Linux version 5.4.0-050400rc4-generic (kernel@kathleen) (gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2)) #201910202130 SMP Sun Oct 20 21:32:54 UTC 2019 $ lsb_release -rd Description:Ubuntu 19.10 Release:19.10 $ apt-cache policy linux-firmware linux-firmware: Installed: 1.183.1 Candidate: 1.183.1 Version table: *** 1.183.1 500 500 http://us.archive.ubuntu.com/ubuntu eoan-updates/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu eoan-updates/main i386 Packages 500 http://security.ubuntu.com/ubuntu eoan-security/main amd64 Packages 500 http://security.ubuntu.com/ubuntu eoan-security/main i386 Packages 100 /var/lib/dpkg/status 1.183 500 500 http://us.archive.ubuntu.com/ubuntu eoan/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu eoan/main i386 Packages ** Affects: linux-firmware (Ubuntu) Importance: Undecided Status: New ** Package changed: linux (Ubuntu) => linux-firmware (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/1849890 Title: Please add brcmfmac43430a0-sdio.bin to linux-firmware Status in linux-firmware package in Ubuntu: New Bug description: brcm/brcmfmac43430a0-* is needed to be added to the firmware bundle. This will make devices such as Acer One 10 (S1003) have working bluetooth and WiFi, which is always a good thing to have when booting off a tablet via live image. Stuff to comply with bug reporting guidelines: $ cat /proc/version_signature > version.log cat: /proc/version_signature: No such file or directory $ cat /proc/version Linux version 5.4.0-050400rc4-generic (kernel@kathleen) (gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2)) #201910202130 SMP Sun Oct 20 21:32:54 UTC 2019 $ lsb_release -rd Description:Ubuntu 19.10 Release:19.10 $ apt-cache policy linux-firmware linux-firmware: Installed: 1.183.1 Candidate: 1.183.1 Version table: *** 1.183.1 500 500 http://us.archive.ubuntu.com/ubuntu eoan-updates/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu eoan-updates/main i386 Packages 500 http://security.ubuntu.com/ubuntu eoan-security/main amd64 Packages 500 http://security.ubuntu.com/ubuntu eoan-security/main i386 Packages 100 /var/lib/dpkg/status 1.183 500 500 http://us.archive.ubuntu.com/ubuntu eoan/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu eoan/main i386 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1849890/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836742] Re: Please enable CONFIG_PMIC_OPREGION and it's components to resolve issues with enabling integrated display on some BayTrail/CherryTrail-based devices
Bug is still happening as of this date with 19.10 on Acer One 10 (s1003). -- 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/1836742 Title: Please enable CONFIG_PMIC_OPREGION and it's components to resolve issues with enabling integrated display on some BayTrail/CherryTrail- based devices Status in linux package in Ubuntu: Confirmed Bug description: Please enable CONFIG_PMIC_OPREGION and it's components (CONFIG_CRC_PMIC_OPREGION, CONFIG_XPOWER_PMIC_OPREGION, CONFIG_BXT_WC_PMIC_OPREGION, CONFIG_CHT_WC_PMIC_OPREGION, CONFIG_CHT_DC_TI_PMIC_OPREGION). On GPD Win 1 and GPD Pocket 1 this should allow to use integrated display when external display is connected. More details is here: https://github.com/torvalds/linux/commit/7b5618f4b834330a052958db934c3dffad4a15c2 https://github.com/torvalds/linux/commit/4e8052af858a6ea2cf656bdb6dbcf16dd87a39c1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1836742/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1847478] Re: eoan kernel does not contain "ipv6: do not free rt if FIB_LOOKUP_NOREF is set on suppress rule"
** Summary changed: - wireguard crashes system shortly after wg-quick down wg0 + eoan kernel does not contain "ipv6: do not free rt if FIB_LOOKUP_NOREF is set on suppress rule" ** Package changed: wireguard (Ubuntu) => linux-meta (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/1847478 Title: eoan kernel does not contain "ipv6: do not free rt if FIB_LOOKUP_NOREF is set on suppress rule" Status in linux package in Ubuntu: In Progress Status in linux-meta package in Ubuntu: Invalid Bug description: [Impact] An unprivileged local attacker could cause a denial of service, or possibly execute arbitrary code due to an ipv6 regression. [Test Case] An unpatched system will crash with the following command: $ unshare -rUn sh -c 'ip link add dummy1 type dummy && ip link set dummy1 up && ip -6 route add default dev dummy1 && ip -6 rule add table main suppress_prefixlength 0 && ping -f 1234::1' [Regression Potential] Low. The change could theoretically introduce a memory leak but that would still be an improvement over immediate loss of system availability. [Original Description] Having recently upgraded to Eoan Ermine from Disco Dingo, my previously rock-solid wireguard now locks the system up shortly after I take the connection down with wg-quick down wg0. Package: wireguard: Installed: 0.0.20190913-1ubuntu1 Candidate: 0.0.20190913-1ubuntu1 Version table: *** 0.0.20190913-1ubuntu1 500 500 http://gb.archive.ubuntu.com/ubuntu eoan/universe amd64 Packages 500 http://gb.archive.ubuntu.com/ubuntu eoan/universe i386 Packages 100 /var/lib/dpkg/status Kernel: 5.3.0-13-generic Snipped from /var/log/syslog: kernel: [ 776.930804] BUG: unable to handle page fault for address: 1070 kernel: [ 776.930807] #PF: supervisor read access in kernel mode kernel: [ 776.930808] #PF: error_code(0x) - not-present page kernel: [ 776.930809] PGD 0 P4D 0 kernel: [ 776.930811] Oops: [#1] SMP NOPTI kernel: [ 776.930813] CPU: 3 PID: 2598 Comm: Chrome_ChildIOT Tainted: G OE 5.3.0-13-generic #14-Ubuntu kernel: [ 776.930813] Hardware name: Dell Inc. XPS 13 9380/0KTW76, BIOS 1.7.0 08/05/2019 kernel: [ 776.930817] RIP: 0010:ip6_sk_dst_store_flow+0x80/0xc0 kernel: [ 776.930819] Code: 48 8b 42 30 48 33 47 40 48 09 c1 0f b6 4f 12 b8 01 00 00 00 4d 0f 45 e9 31 db d3 e0 a9 bf ef ff ff 74 07 48 8b 9f f8 02 00 00 <48> 8b 46 70 31 d2 48 85 c0 74 0c 48 8b 40 10 48 85 c0 74 03 8b 50 kernel: [ 776.930820] RSP: 0018:beb841a9fcd8 EFLAGS: 00010202 kernel: [ 776.930821] RAX: 0080 RBX: a0933c829360 RCX: 0007 kernel: [ 776.930822] RDX: beb841a9fd20 RSI: 1000 RDI: a0933c828f00 kernel: [ 776.930823] RBP: beb841a9fcf0 R08: R09: kernel: [ 776.930823] R10: R11: a093948fd800 R12: a0933c829360 kernel: [ 776.930824] R13: a0933c828f38 R14: 0001 R15: a0933c829360 kernel: [ 776.930825] FS: 7fbcd8a82700() GS:a0939e4c() knlGS: kernel: [ 776.930826] CS: 0010 DS: ES: CR0: 80050033 kernel: [ 776.930827] CR2: 1070 CR3: 00049172a004 CR4: 003606e0 kernel: [ 776.930828] Call Trace: kernel: [ 776.930832] ip6_datagram_dst_update+0x15e/0x280 kernel: [ 776.930835] ? _raw_read_unlock_bh+0x20/0x30 kernel: [ 776.930837] __ip6_datagram_connect+0x1da/0x380 kernel: [ 776.930839] ip6_datagram_connect+0x2d/0x50 kernel: [ 776.930841] inet_dgram_connect+0x3f/0xc0 kernel: [ 776.930843] __sys_connect+0xf1/0x130 kernel: [ 776.930846] ? do_fcntl+0xe4/0x550 kernel: [ 776.930848] ? fput+0x13/0x15 kernel: [ 776.930849] __x64_sys_connect+0x1a/0x20 kernel: [ 776.930852] do_syscall_64+0x5a/0x130 kernel: [ 776.930854] entry_SYSCALL_64_after_hwframe+0x44/0xa9 kernel: [ 776.930855] RIP: 0033:0x7fbcde6324eb kernel: [ 776.930856] Code: 83 ec 18 89 54 24 0c 48 89 34 24 89 7c 24 08 e8 ab fa ff ff 8b 54 24 0c 48 8b 34 24 41 89 c0 8b 7c 24 08 b8 2a 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 2f 44 89 c7 89 44 24 08 e8 e1 fa ff ff 8b 44 kernel: [ 776.930857] RSP: 002b:7fbcd8a7ec90 EFLAGS: 0293 ORIG_RAX: 002a kernel: [ 776.930859] RAX: ffda RBX: ff94 RCX: 7fbcde6324eb kernel: [ 776.930859] RDX: 001c RSI: 7fbcd8a7ecf0 RDI: 0022 kernel: [ 776.930860] RBP: 7fbcd8a7edb0 R08: R09: 7fbcd8a7edf8 kernel: [ 776.930861] R10: 7fbcd8a7edf0 R11: 0293 R12: 250e77c19710 kernel: [ 776.930862] R13: 250e77c19900 R14: 7fbcd8a7edc8 R15: 7fbcd8a7edc8 kernel: [ 776.930863] Modules linked in: binfmt_misc
[Kernel-packages] [Bug 1829620] Re: intel-microcode on ASUS makes kernel stuck during loading initramfs on bionic-updates, bionic-security
Hello Same issue with purple screen when login screen should be displayed. By adding nomodeset to the Linux kernel line in Grub I was able to get to the login screen. But now I am just left at the purple screen once I have entered my login credentials and pressed enter. I have checked for BIOS update, none available. I am on a Dell Inspiron 7720. Moving the mouse on the login screen is also very sluggish. Regards Jason -- 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/1829620 Title: intel-microcode on ASUS makes kernel stuck during loading initramfs on bionic-updates, bionic-security Status in intel-microcode package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux-hwe package in Ubuntu: Confirmed Status in linux-hwe-edge package in Ubuntu: Confirmed Bug description: Description: - my system gets stuck at "Booting, Loading initramfs" (the first 2 lines of booting, after grub) - does not even show the enter cryptsetup passphrase - affected kernels: # apt list --installed |grep linux-signed WARNING: apt does not have a stable CLI interface. Use with caution in scripts. linux-signed-generic/bionic-security,bionic-updates,now 4.15.0.50.52 amd64 [installed] linux-signed-generic-hwe-18.04/bionic-security,bionic-updates,now 4.18.0.20.70 amd64 [installed] linux-signed-generic-hwe-18.04-edge/bionic-security,bionic-updates,now 5.0.0.15.71 amd64 [installed] - the setup is not new, has been working perfectly before (about 7 days since my last restart?) System: - HW: ASUS Zenbook 14 UX433FN - Ubuntu 18.04, runing latest HWE, fully updated - grub(-pc), cryptsetup (crypttab entries for custom encrypted LUKS setup), Suspected/possible cause?: - recent intel-microcode package update - recent kernel package updates Steps taken: - tried to remove "splash quiet" from grub/kernel cmd line (also tried adding nosplash, noplymouth) - completely removed nvidia drivers (apt purge *nvidia*) - completely purged and reinstalled grub (grup-pc) - completely purged and reinstalled all kernels (headers, modules, image, ..) - toggle BIOS "fastboot" (now using OFF) - toggle UEFI SecureBoot (now using ON) - remove plymouth (apt remove *plymouth* , but the workaround is working with plymouth installed) Workaround: - so far, I'm only able to boot with non-Ubuntu kernel! (linux-image-liquorix-amd64) - which needs "splash" option ON - reinstall cryptsetup & update-grub (as suggested in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829620/comments/10 ) I am not sure how to get you more debug info, as this setup has been working before, and it's a very eary boot-process bug, so I can't even access dmesg etc. EDIT: Hypothesis: Only affects ASUS with i7-8565U Whiskey Lake Intel CPU Upstream Bug Report: https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files/issues/1 WORKAROUND 1: disable intel microcode updates during boot From this bug: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1759920 1/ add the boot parameter: dis_ucode_ldr to /etc/default/grub 2/ update-grub WORKAROUND 2: downgrade (and hold) intel-microcode to older version from bionic/main apt install --reinstall intel-microcode=3.20180312.0~ubuntu18.04.1 WORKAROUND 3: upgrade BIOS Asus has released updated BIOSes, which probably include the newest microcode. After upgrading workarounds 1,2 are not needed. Please NOTE, unlike workarounds 1,2, BIOS upgrade is permanent and cannot be (easily) reverted. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: KDE DistroRelease: KDE neon 18.04 InstallationDate: Installed on 2012-12-23 (2337 days ago) InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.1) Package: linux-hwe-edge (not installed) Tags: bionic wayland-session Uname: Linux 5.0.0-17.1-liquorix-amd64 x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm libvirtd lpadmin netdev plugdev sudo vboxusers video _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: KDE DistroRelease: KDE neon 18.04 InstallationDate: Installed on 2012-12-23 (2339 days ago) InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.1) Package: linux-hwe-edge PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.0.0-15.16~18.04.1-generic 5.0.6 Tags: third-party-packages bionic wayland-session Uname: Linux 5.0.0-15-generic x86_64 UnreportableReason: Toto není oficiální KDE balík. Prosíme odstraňte všechny balíky třetích s
[Kernel-packages] [Bug 1842447] Re: Kernel Panic with linux-image-4.15.0-60-generic when specifying nameserver in docker-compose
It's possible this same issue is responsible for this crash in WireGuard: https://lists.zx2c4.com/pipermail/wireguard/2019-September/004495.html -- 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/1842447 Title: Kernel Panic with linux-image-4.15.0-60-generic when specifying nameserver in docker-compose Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Fix Committed Bug description: [Impact] Some fragmentation+NAT workloads will cause kernel BUG/Ooops. [Test case] sudo iptables -t nat -I POSTROUTING -j MASQUERADE sudo hping3 192.168.122.1 -s 1000 -p 2000 -d 6 [Regression potential] This could make fragmented packets stop flowing. So, make sure fragmented pings still work. ping 192.168.122.1 -s 6 still works, even with the above nat rule. Hello, there are multiple inquries in the mailcow GitHub issues over at https://github.com/mailcow/mailcow-dockerized/issues/2904 that the latest kernel linux-image-4.15.0-60-generic causes kernel panics when "- dns" setting is used within the docker-compose.yml file, for yet some unclear reasons. Multiple users on different systems (e.g. virtualized ones on VMware ESXi and KVM) were able to reproduce the same issue. I was also able to reproduce this constantly on a completely new deployed Ubuntu 18.04 VM (KVM) with a fresh mailcow installation. Steps to reproduce: 1. Install a clean Ubuntu 18.04(.03) machine 2. Upgrade the installation to linux-image-4.15.0-60-generic 3. Setup mailcow as instructed at https://mailcow.github.io/mailcow-dockerized-docs/i_u_m_install/ (just takes less than a minute, easy to reproduce) 4. Start mailcow with "dns"-settings specified in docker-compose file (Make sure using the older docker-compose version with dns settings: https://raw.githubusercontent.com/mailcow/mailcow-dockerized/a1403b7a5969637df23001d05c59c2a20774fbb5/docker-compose.yml) 5. Wait a few minutes, then kernel crash appears Using this workaround it appears to be stable again: https://github.com/mailcow/mailcow- dockerized/commit/dc6eea5142c063e26408a685b66fbb7754408ec2 I've attached the apport file to this bug. Please let me know if you need any kind of further information. (As this is my first bug report here, I hope I have included all required information helping you finding the cause.) Kind regards, Patrik To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1842447/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1784665] Re: bcache: bch_allocator_thread(): hung task timeout
@ Ryan we do not test Xenial or Disco On Thu, Aug 22, 2019 at 7:41 PM Ryan Harper <1784...@bugs.launchpad.net> wrote: > Finally, I did verify xenial proposed with our original test. I had > over 100 installs with no issue. > > @Jason > > Have you had any runs on Xenial or Disco? (or do you not test those)? > > -- > You received this bug notification because you are a member of Canonical > Field Critical, which is subscribed to a duplicate bug report (1796292). > https://bugs.launchpad.net/bugs/1784665 > > Title: > bcache: bch_allocator_thread(): hung task timeout > > Status in linux package in Ubuntu: > Fix Committed > Status in linux source package in Xenial: > Fix Committed > Status in linux source package in Bionic: > New > Status in linux source package in Disco: > Fix Committed > Status in linux source package in Eoan: > Fix Committed > > Bug description: > [Impact] > > bcache_allocator() can call the following: > >bch_allocator_thread() > -> bch_prio_write() >-> bch_bucket_alloc() > -> wait on &ca->set->bucket_wait > > But the wake up event on bucket_wait is supposed to come from > bch_allocator_thread() itself causing a deadlock. > > [Test Case] > > This is a simple script that can easily trigger the deadlock condition: > https://launchpadlibrarian.net/381282009/bcache-basic-repro.sh > > A better test case has been also provided in bug 1796292 (duplicate of > this bug): > > https://bugs.launchpad.net/curtin/+bug/1796292/+attachment/5280353/+files/curtin-nvme.sh > > [Fix] > > Fix by making the call to bch_prio_write() non-blocking, so that > bch_allocator_thread() never waits on itself. Moreover, make sure to > wake up the garbage collector thread when bch_prio_write() is failing > to allocate buckets to increase the chance of freeing up more buckets. > > In addition to that it would be safe to also import other upstream > bcache fixes (all clean cherry picks): > > 7e865eba00a3df2dc8c4746173a8ca1c1c7f042e bcache: fix potential deadlock > in cached_def_free() > 80265d8dfd77792e133793cef44a21323aac2908 bcache: acquire > bch_register_lock later in cached_dev_free() > ce4c3e19e5201424357a0c82176633b32a98d2ec bcache: Replace > bch_read_string_list() by __sysfs_match_string() > ecb37ce9baac653cc09e2b631393dde3df82979f bcache: Move couple of > functions to sysfs.c > 04cbc21137bfa4d7b8771a5b14f3d6c9b2aee671 bcache: Move couple of string > arrays to sysfs.c > 5f2b18ec8e1643410a2369f06888951cdedea0bf bcache: Fix a compiler warning > in bcache_device_init() > 20d3a518713e394efa5a899c84574b4b79ec5098 bcache: Reduce the number of > sparse complaints about lock imbalances > 42361469ae84c851e40cb1f94c8c9a14cdd94039 bcache: Suppress more warnings > about set-but-not-used variables > f0d3814090ac77de94c42b7124c37ece23629197 bcache: Remove an unused > variable > 47344e330eabc1515cbe6061eb337100a3ab6d37 bcache: Fix kernel-doc warnings > 9dfbdec7b7fea1ff1b7b5d5d12980dbc7dca46c7 bcache: Annotate switch > fall-through > 4a4e443835a43a79113cc237c472c0d268eb1e1c bcache: Add __printf annotation > to __bch_check_keys() > fd01991d5c20098c5c1ffc4dca6c821cc60a2f74 bcache: Fix indentation > ca71df31661a0518ed58a1a59cf1993962153ebb bcache: fix using of loop > variable in memory shrink > f3641c3abd1da978ee969b0203b71b86ec1bfa93 bcache: fix error return value > in memory shrink > 688892b3bc05e25da94866e32210e5f503f16f69 bcache: fix incorrect sysfs > output value of strip size > 09a44ca2114737e0932257619c16a2b50c7807f1 bcache: use pr_info() to inform > duplicated CACHE_SET_IO_DISABLE set > c4dc2497d50d9c6fb16aa0d07b6a14f3b2adb1e0 bcache: fix high CPU occupancy > during journal > a728eacbbdd229d1d903e46261c57d5206f87a4a bcache: add journal statistic > 616486ab52ab7f9739b066d958bdd20e65aefd74 bcache: fix writeback target > calc on large devices > 1f0ffa67349c56ea54c03ccfd1e073c990e7411e bcache: only set > BCACHE_DEV_WB_RUNNING when cached device attached > eb8cbb6df38f6e5124a3d5f1f8a3dbf519537c60 bcache: improve bcache_reboot() > 9951379b0ca88c95876ad9778b9099e19a95d566 bcache: never writeback a > discard operation > > [Regression Potential] > > The upstream fixes are all clean cherry picks from stable (most of > them are small cleanups), so regression potential is minimal. > > The only special patch is "UBUNTU: SAUCE: bcache: fix deadlock in > bcache_allocator()" that is addressing the main deadlock bug (that > seems to be a mainline bug - not fixed yet). We should spend more time > trying to reproduce this deadlock with a mainl
[Kernel-packages] [Bug 1784665] Re: bcache: bch_allocator_thread(): hung task timeout
** Changed in: linux (Ubuntu Bionic) Status: Fix Committed => 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/1784665 Title: bcache: bch_allocator_thread(): hung task timeout Status in linux package in Ubuntu: Fix Committed Status in linux source package in Xenial: Fix Committed Status in linux source package in Bionic: New Status in linux source package in Disco: Fix Committed Status in linux source package in Eoan: Fix Committed Bug description: [Impact] bcache_allocator() can call the following: bch_allocator_thread() -> bch_prio_write() -> bch_bucket_alloc() -> wait on &ca->set->bucket_wait But the wake up event on bucket_wait is supposed to come from bch_allocator_thread() itself causing a deadlock. [Test Case] This is a simple script that can easily trigger the deadlock condition: https://launchpadlibrarian.net/381282009/bcache-basic-repro.sh A better test case has been also provided in bug 1796292 (duplicate of this bug): https://bugs.launchpad.net/curtin/+bug/1796292/+attachment/5280353/+files/curtin-nvme.sh [Fix] Fix by making the call to bch_prio_write() non-blocking, so that bch_allocator_thread() never waits on itself. Moreover, make sure to wake up the garbage collector thread when bch_prio_write() is failing to allocate buckets to increase the chance of freeing up more buckets. In addition to that it would be safe to also import other upstream bcache fixes (all clean cherry picks): 7e865eba00a3df2dc8c4746173a8ca1c1c7f042e bcache: fix potential deadlock in cached_def_free() 80265d8dfd77792e133793cef44a21323aac2908 bcache: acquire bch_register_lock later in cached_dev_free() ce4c3e19e5201424357a0c82176633b32a98d2ec bcache: Replace bch_read_string_list() by __sysfs_match_string() ecb37ce9baac653cc09e2b631393dde3df82979f bcache: Move couple of functions to sysfs.c 04cbc21137bfa4d7b8771a5b14f3d6c9b2aee671 bcache: Move couple of string arrays to sysfs.c 5f2b18ec8e1643410a2369f06888951cdedea0bf bcache: Fix a compiler warning in bcache_device_init() 20d3a518713e394efa5a899c84574b4b79ec5098 bcache: Reduce the number of sparse complaints about lock imbalances 42361469ae84c851e40cb1f94c8c9a14cdd94039 bcache: Suppress more warnings about set-but-not-used variables f0d3814090ac77de94c42b7124c37ece23629197 bcache: Remove an unused variable 47344e330eabc1515cbe6061eb337100a3ab6d37 bcache: Fix kernel-doc warnings 9dfbdec7b7fea1ff1b7b5d5d12980dbc7dca46c7 bcache: Annotate switch fall-through 4a4e443835a43a79113cc237c472c0d268eb1e1c bcache: Add __printf annotation to __bch_check_keys() fd01991d5c20098c5c1ffc4dca6c821cc60a2f74 bcache: Fix indentation ca71df31661a0518ed58a1a59cf1993962153ebb bcache: fix using of loop variable in memory shrink f3641c3abd1da978ee969b0203b71b86ec1bfa93 bcache: fix error return value in memory shrink 688892b3bc05e25da94866e32210e5f503f16f69 bcache: fix incorrect sysfs output value of strip size 09a44ca2114737e0932257619c16a2b50c7807f1 bcache: use pr_info() to inform duplicated CACHE_SET_IO_DISABLE set c4dc2497d50d9c6fb16aa0d07b6a14f3b2adb1e0 bcache: fix high CPU occupancy during journal a728eacbbdd229d1d903e46261c57d5206f87a4a bcache: add journal statistic 616486ab52ab7f9739b066d958bdd20e65aefd74 bcache: fix writeback target calc on large devices 1f0ffa67349c56ea54c03ccfd1e073c990e7411e bcache: only set BCACHE_DEV_WB_RUNNING when cached device attached eb8cbb6df38f6e5124a3d5f1f8a3dbf519537c60 bcache: improve bcache_reboot() 9951379b0ca88c95876ad9778b9099e19a95d566 bcache: never writeback a discard operation [Regression Potential] The upstream fixes are all clean cherry picks from stable (most of them are small cleanups), so regression potential is minimal. The only special patch is "UBUNTU: SAUCE: bcache: fix deadlock in bcache_allocator()" that is addressing the main deadlock bug (that seems to be a mainline bug - not fixed yet). We should spend more time trying to reproduce this deadlock with a mainline kernel and post the patch to the LKML for review / feedback. However, considering that this patch seems to fix/prevent the specific deadlock problem reported in this bug (tested on the affected platform) it can be considered safe to apply it. [Original Bug Report] $ cat /proc/version_signature Ubuntu 4.15.0-29.31-generic 4.15.18 $ lsb_release -rd Description: Ubuntu Cosmic Cuttlefish (development branch) Release: 18.10 $ apt-cache policy linux-image-`uname -r` linux-image-4.15.0-29-generic: Installed: 4.15.0-29.31 Candidate: 4.15.0-29.31 Version table: *** 4.15.0-29.31 500 500 http://archive.ubuntu.com/ubuntu cosmic/main amd64 Packages 100 /var/lib/dpkg/status 3) mkfs.ext4 /dev/bcache0 returns successful creating an ext4
[Kernel-packages] [Bug 1784665] Re: bcache: bch_allocator_thread(): hung task timeout
** Attachment added: "spinda.maas-curtin_config.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784665/+attachment/5284072/+files/spinda.maas-curtin_config.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1784665 Title: bcache: bch_allocator_thread(): hung task timeout Status in linux package in Ubuntu: Fix Committed Status in linux source package in Xenial: Fix Committed Status in linux source package in Bionic: Fix Committed Status in linux source package in Disco: Fix Committed Status in linux source package in Eoan: Fix Committed Bug description: [Impact] bcache_allocator() can call the following: bch_allocator_thread() -> bch_prio_write() -> bch_bucket_alloc() -> wait on &ca->set->bucket_wait But the wake up event on bucket_wait is supposed to come from bch_allocator_thread() itself causing a deadlock. [Test Case] This is a simple script that can easily trigger the deadlock condition: https://launchpadlibrarian.net/381282009/bcache-basic-repro.sh A better test case has been also provided in bug 1796292 (duplicate of this bug): https://bugs.launchpad.net/curtin/+bug/1796292/+attachment/5280353/+files/curtin-nvme.sh [Fix] Fix by making the call to bch_prio_write() non-blocking, so that bch_allocator_thread() never waits on itself. Moreover, make sure to wake up the garbage collector thread when bch_prio_write() is failing to allocate buckets to increase the chance of freeing up more buckets. In addition to that it would be safe to also import other upstream bcache fixes (all clean cherry picks): 7e865eba00a3df2dc8c4746173a8ca1c1c7f042e bcache: fix potential deadlock in cached_def_free() 80265d8dfd77792e133793cef44a21323aac2908 bcache: acquire bch_register_lock later in cached_dev_free() ce4c3e19e5201424357a0c82176633b32a98d2ec bcache: Replace bch_read_string_list() by __sysfs_match_string() ecb37ce9baac653cc09e2b631393dde3df82979f bcache: Move couple of functions to sysfs.c 04cbc21137bfa4d7b8771a5b14f3d6c9b2aee671 bcache: Move couple of string arrays to sysfs.c 5f2b18ec8e1643410a2369f06888951cdedea0bf bcache: Fix a compiler warning in bcache_device_init() 20d3a518713e394efa5a899c84574b4b79ec5098 bcache: Reduce the number of sparse complaints about lock imbalances 42361469ae84c851e40cb1f94c8c9a14cdd94039 bcache: Suppress more warnings about set-but-not-used variables f0d3814090ac77de94c42b7124c37ece23629197 bcache: Remove an unused variable 47344e330eabc1515cbe6061eb337100a3ab6d37 bcache: Fix kernel-doc warnings 9dfbdec7b7fea1ff1b7b5d5d12980dbc7dca46c7 bcache: Annotate switch fall-through 4a4e443835a43a79113cc237c472c0d268eb1e1c bcache: Add __printf annotation to __bch_check_keys() fd01991d5c20098c5c1ffc4dca6c821cc60a2f74 bcache: Fix indentation ca71df31661a0518ed58a1a59cf1993962153ebb bcache: fix using of loop variable in memory shrink f3641c3abd1da978ee969b0203b71b86ec1bfa93 bcache: fix error return value in memory shrink 688892b3bc05e25da94866e32210e5f503f16f69 bcache: fix incorrect sysfs output value of strip size 09a44ca2114737e0932257619c16a2b50c7807f1 bcache: use pr_info() to inform duplicated CACHE_SET_IO_DISABLE set c4dc2497d50d9c6fb16aa0d07b6a14f3b2adb1e0 bcache: fix high CPU occupancy during journal a728eacbbdd229d1d903e46261c57d5206f87a4a bcache: add journal statistic 616486ab52ab7f9739b066d958bdd20e65aefd74 bcache: fix writeback target calc on large devices 1f0ffa67349c56ea54c03ccfd1e073c990e7411e bcache: only set BCACHE_DEV_WB_RUNNING when cached device attached eb8cbb6df38f6e5124a3d5f1f8a3dbf519537c60 bcache: improve bcache_reboot() 9951379b0ca88c95876ad9778b9099e19a95d566 bcache: never writeback a discard operation [Regression Potential] The upstream fixes are all clean cherry picks from stable (most of them are small cleanups), so regression potential is minimal. The only special patch is "UBUNTU: SAUCE: bcache: fix deadlock in bcache_allocator()" that is addressing the main deadlock bug (that seems to be a mainline bug - not fixed yet). We should spend more time trying to reproduce this deadlock with a mainline kernel and post the patch to the LKML for review / feedback. However, considering that this patch seems to fix/prevent the specific deadlock problem reported in this bug (tested on the affected platform) it can be considered safe to apply it. [Original Bug Report] $ cat /proc/version_signature Ubuntu 4.15.0-29.31-generic 4.15.18 $ lsb_release -rd Description: Ubuntu Cosmic Cuttlefish (development branch) Release: 18.10 $ apt-cache policy linux-image-`uname -r` linux-image-4.15.0-29-generic: Installed: 4.15.0-29.31 Candidate: 4.15.0-29.31 Version table: *** 4.15.0-29.31 500 500 http://archive.ubuntu.com/ubuntu cosmic/main amd6
[Kernel-packages] [Bug 1784665] Re: bcache: bch_allocator_thread(): hung task timeout
We're still seeing a bcache timeout failure during curtin install 2019-08-22T10:16:40+00:00 spinda cloud-init[1604]: finish: cmd-install/stage-partitioning/builtin/cmd-block-meta/clear-holders: FAIL: removing previous storage devices 2019-08-22T10:16:40+00:00 spinda cloud-init[1604]: TIMED BLOCK_META: 1203.679 I attached the rsyslog from a unit that failed. Linux version 4.15.0-59-generic (buildd@lgw01-amd64-035) (gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1)) #66-Ubuntu SMP Wed Aug 14 10:56:44 UTC 2019 (Ubuntu 4.15.0-59.66-generic 4.15.18) ** Attachment added: "messages" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784665/+attachment/5284071/+files/messages ** Tags removed: verification-done-bionic ** Tags added: verification-failed-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1784665 Title: bcache: bch_allocator_thread(): hung task timeout Status in linux package in Ubuntu: Fix Committed Status in linux source package in Xenial: Fix Committed Status in linux source package in Bionic: Fix Committed Status in linux source package in Disco: Fix Committed Status in linux source package in Eoan: Fix Committed Bug description: [Impact] bcache_allocator() can call the following: bch_allocator_thread() -> bch_prio_write() -> bch_bucket_alloc() -> wait on &ca->set->bucket_wait But the wake up event on bucket_wait is supposed to come from bch_allocator_thread() itself causing a deadlock. [Test Case] This is a simple script that can easily trigger the deadlock condition: https://launchpadlibrarian.net/381282009/bcache-basic-repro.sh A better test case has been also provided in bug 1796292 (duplicate of this bug): https://bugs.launchpad.net/curtin/+bug/1796292/+attachment/5280353/+files/curtin-nvme.sh [Fix] Fix by making the call to bch_prio_write() non-blocking, so that bch_allocator_thread() never waits on itself. Moreover, make sure to wake up the garbage collector thread when bch_prio_write() is failing to allocate buckets to increase the chance of freeing up more buckets. In addition to that it would be safe to also import other upstream bcache fixes (all clean cherry picks): 7e865eba00a3df2dc8c4746173a8ca1c1c7f042e bcache: fix potential deadlock in cached_def_free() 80265d8dfd77792e133793cef44a21323aac2908 bcache: acquire bch_register_lock later in cached_dev_free() ce4c3e19e5201424357a0c82176633b32a98d2ec bcache: Replace bch_read_string_list() by __sysfs_match_string() ecb37ce9baac653cc09e2b631393dde3df82979f bcache: Move couple of functions to sysfs.c 04cbc21137bfa4d7b8771a5b14f3d6c9b2aee671 bcache: Move couple of string arrays to sysfs.c 5f2b18ec8e1643410a2369f06888951cdedea0bf bcache: Fix a compiler warning in bcache_device_init() 20d3a518713e394efa5a899c84574b4b79ec5098 bcache: Reduce the number of sparse complaints about lock imbalances 42361469ae84c851e40cb1f94c8c9a14cdd94039 bcache: Suppress more warnings about set-but-not-used variables f0d3814090ac77de94c42b7124c37ece23629197 bcache: Remove an unused variable 47344e330eabc1515cbe6061eb337100a3ab6d37 bcache: Fix kernel-doc warnings 9dfbdec7b7fea1ff1b7b5d5d12980dbc7dca46c7 bcache: Annotate switch fall-through 4a4e443835a43a79113cc237c472c0d268eb1e1c bcache: Add __printf annotation to __bch_check_keys() fd01991d5c20098c5c1ffc4dca6c821cc60a2f74 bcache: Fix indentation ca71df31661a0518ed58a1a59cf1993962153ebb bcache: fix using of loop variable in memory shrink f3641c3abd1da978ee969b0203b71b86ec1bfa93 bcache: fix error return value in memory shrink 688892b3bc05e25da94866e32210e5f503f16f69 bcache: fix incorrect sysfs output value of strip size 09a44ca2114737e0932257619c16a2b50c7807f1 bcache: use pr_info() to inform duplicated CACHE_SET_IO_DISABLE set c4dc2497d50d9c6fb16aa0d07b6a14f3b2adb1e0 bcache: fix high CPU occupancy during journal a728eacbbdd229d1d903e46261c57d5206f87a4a bcache: add journal statistic 616486ab52ab7f9739b066d958bdd20e65aefd74 bcache: fix writeback target calc on large devices 1f0ffa67349c56ea54c03ccfd1e073c990e7411e bcache: only set BCACHE_DEV_WB_RUNNING when cached device attached eb8cbb6df38f6e5124a3d5f1f8a3dbf519537c60 bcache: improve bcache_reboot() 9951379b0ca88c95876ad9778b9099e19a95d566 bcache: never writeback a discard operation [Regression Potential] The upstream fixes are all clean cherry picks from stable (most of them are small cleanups), so regression potential is minimal. The only special patch is "UBUNTU: SAUCE: bcache: fix deadlock in bcache_allocator()" that is addressing the main deadlock bug (that seems to be a mainline bug - not fixed yet). We should spend more time trying to reproduce this deadlock with a mainline kernel and post the patch to the LKML for review / feedback. However,
[Kernel-packages] [Bug 1807406] Re: hid-sensor-hub 001F:8086:22D8.0003: timeout waiting for response from ISHTP device
I also started having this same issue on my HP Spectre x360. -- 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/1807406 Title: hid-sensor-hub 001F:8086:22D8.0003: timeout waiting for response from ISHTP device Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Hello, Message after returning from suspension dmesg: [13383.967611] hid-sensor-hub 001F:8086:22D8.0003: timeout waiting for response from ISHTP device [13383.967615] hid-sensor-hub 001F:8086:22D8.0002: timeout waiting for response from ISHTP device Best regards, -- Cristian Aravena Romero (caravena) ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-4.19.0-8-generic 4.19.0-8.9 ProcVersionSignature: Ubuntu 4.19.0-8.9-generic 4.19.6 Uname: Linux 4.19.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: caravena 2769 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Dec 7 12:02:26 2018 HibernationDevice: RESUME=UUID=efcf081f-0bb0-4907-b78c-1299aa4aee57 InstallationDate: Installed on 2018-12-02 (4 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: HP HP Pavilion x360 Convertible 14-cd0xxx ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.19.0-8-generic root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.19.0-8-generic N/A linux-backports-modules-4.19.0-8-generic N/A linux-firmware1.176 SourcePackage: linux UpgradeStatus: Upgraded to disco on 2018-12-02 (4 days ago) dmi.bios.date: 06/14/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.13 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8486 dmi.board.vendor: HP dmi.board.version: 72.19 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.13:bd06/14/2018:svnHP:pnHPPavilionx360Convertible14-cd0xxx:pvrType1ProductConfigId:rvnHP:rn8486:rvr72.19:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion x360 Convertible 14-cd0xxx dmi.product.sku: 3PX63LA#ABM dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1807406/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
