[Kernel-packages] [Bug 1973477] Re: unable to upgrade to xubuntu
Thank you for taking the time to report this bug and helping to make Ubuntu better. Bug reporting is about finding & fixing problems thus preventing future users from hitting the same bug. I suspect a Support site would be more appropriate, eg. https://answers.launchpad.net/ubuntu. You can also find help with your problem in the support forum of your local Ubuntu community http://loco.ubuntu.com/ or asking at https://askubuntu.com or https://ubuntuforums.org, or for more support options please look at https://discourse.ubuntu.com/t/community-support/709 You've reported your issue relates to installation (ubiquity is the installer), yet your system was installed 24 days ago? You can convert this bug report into a question which is geared at support. I've marked this report as "incomplete" as it doesn't fit an installation (ubiquity) issue & appears you're after support. ** Changed in: ubiquity (Ubuntu) Status: New => Incomplete ** Package changed: ubiquity (Ubuntu) => linux-firmware (Ubuntu) -- 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/1973477 Title: unable to upgrade to xubuntu Status in linux-firmware package in Ubuntu: Incomplete Bug description: W: Possible missing firmware /lib/firmware/rtl_nic/rtl8125b-2.fw for module r8169 Errors were encountered while processing: klibc-utils E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 5.13.0-40.45~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun May 15 16:59:41 2022 InstallCmdLine: file=/cdrom/preseed/ubuntu.seed initrd=/casper/initrd quiet splash --- maybe-ubiquity InstallationDate: Installed on 2022-04-20 (24 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: ubiquity Symptom: installation UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1973477/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1946303] Re: No video after wake from S3 due to Nvidia driver crash
Resume fails with a black screen won Ubuntu 22.04 RTX 3070 Mobile, driver 510 with: - Xorg. nvidia services enabled: resume fails - Xorg, nvidia services disabled: resume fails - XWayland, nvidia services disabled: resume fails However it does work with: - Xwayland, nvidia services enabled: resume works laptop: Juno Neptune 15 v3 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu. https://bugs.launchpad.net/bugs/1946303 Title: No video after wake from S3 due to Nvidia driver crash Status in nvidia-graphics-drivers-470 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-510 package in Ubuntu: Confirmed Bug description: Since upgrading to Ubuntu 21.10, my computer sometimes fails to properly wake from suspend. It does start running again, but there is no video output. I'm attaching text for two crashes from kernel log output. First is: /var/lib/dkms/nvidia/470.63.01/build/nvidia/nv.c:3967 nv_restore_user_channels+0xce/0xe0 [nvidia] Second is: /var/lib/dkms/nvidia/470.63.01/build/nvidia/nv.c:4162 nv_set_system_power_state+0x2c8/0x3d0 [nvidia] Apparently I'm not the only one having this problem with 470 drivers. https://forums.linuxmint.com/viewtopic.php?t=354445 https://forums.developer.nvidia.com/t/fixed-suspend-resume-issues-with-the-driver-version-470/187150 Driver 470 uses the new suspend mechanism via /usr/lib/systemd/system- sleep/nvidia. But I was using that mechanism with driver 460 in Ubuntu 21.04 and sleep was reliable then. Right now I'm going back to driver 460. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: nvidia-driver-470 470.63.01-0ubuntu4 ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Oct 6 23:24:02 2021 SourcePackage: nvidia-graphics-drivers-470 UpgradeStatus: Upgraded to impish on 2021-10-02 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1946303/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1966417] Re: memcontrol04 in ubuntu_ltp_controllers failed on J-azure (Low events in F)
Found with J-OEM 5.17.0-1004.4 with node wildcat ** Tags added: 5.17 oem sru-20220418 -- 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/1966417 Title: memcontrol04 in ubuntu_ltp_controllers failed on J-azure (Low events in F) Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Bug description: Issue found on I-azure 5.15.0-1002.3 Test failed with: memcontrol04.c:214: TFAIL: Expect: (F low events=419) == 0 HINT: You _MAY_ be hit by known kernel failures: Low events in F: https://bugzilla.suse.com/show_bug.cgi?id=1196298 Test log: INFO: Test start time: Fri Mar 25 10:03:44 UTC 2022 COMMAND:/opt/ltp/bin/ltp-pan -q -e -S -a 119719 -n 119719 -f /tmp/ltp-mFNzOrxoBY/alltests -l /dev/null -C /dev/null -T /dev/null LOG File: /dev/null FAILED COMMAND File: /dev/null TCONF COMMAND File: /dev/null Running tests... tst_device.c:88: TINFO: Found free device 3 '/dev/loop3' tst_supported_fs_types.c:88: TINFO: Kernel supports ext2 tst_supported_fs_types.c:50: TINFO: mkfs.ext2 does exist tst_supported_fs_types.c:88: TINFO: Kernel supports ext3 tst_supported_fs_types.c:50: TINFO: mkfs.ext3 does exist tst_supported_fs_types.c:88: TINFO: Kernel supports ext4 tst_supported_fs_types.c:50: TINFO: mkfs.ext4 does exist tst_supported_fs_types.c:88: TINFO: Kernel supports xfs tst_supported_fs_types.c:50: TINFO: mkfs.xfs does exist tst_supported_fs_types.c:88: TINFO: Kernel supports btrfs tst_supported_fs_types.c:50: TINFO: mkfs.btrfs does exist tst_supported_fs_types.c:155: TINFO: Skipping vfat as requested by the test tst_supported_fs_types.c:155: TINFO: Skipping exfat as requested by the test tst_supported_fs_types.c:155: TINFO: Skipping tmpfs as requested by the test tst_test.c:1528: TINFO: Testing on ext2 tst_test.c:996: TINFO: Formatting /dev/loop3 with ext2 opts='' extra opts='' mke2fs 1.46.5 (30-Dec-2021) tst_test.c:1456: TINFO: Timeout per run is 0h 05m 00s memcontrol04.c:118: TINFO: Child 119783 in leaf_C: Allocating pagecache: 52428800 memcontrol04.c:118: TINFO: Child 119785 in leaf_D: Allocating pagecache: 52428800 memcontrol04.c:118: TINFO: Child 119786 in leaf_F: Allocating pagecache: 52428800 memcontrol04.c:99: TINFO: Child 119787 in trunk_G: Allocating anon: 155189248 memcontrol04.c:170: TPASS: Expect: (A/B memory.current=54177792) ~= 52428800 memcontrol04.c:176: TPASS: Expect: (A/B/C memory.current=30691328) ~= 34603008 memcontrol04.c:178: TPASS: Expect: (A/B/D memory.current=22523904) ~= 17825792 memcontrol04.c:180: TPASS: Expect: (A/B/E memory.current=0) ~= 0 memcontrol04.c:182: TINFO: A/B/F memory.current=950272 memcontrol04.c:99: TINFO: Child 119788 in trunk_G: Allocating anon: 174063616 memcontrol04.c:195: TINFO: A: low events=1645, oom events=0 memcontrol04.c:195: TINFO: B: low events=1645, oom events=0 memcontrol04.c:195: TINFO: G: low events=0, oom events=0 memcontrol04.c:208: TPASS: Expect: (C oom events=0) == 0 memcontrol04.c:211: TPASS: Expect: (C low events=413) > 0 memcontrol04.c:208: TPASS: Expect: (D oom events=0) == 0 memcontrol04.c:211: TPASS: Expect: (D low events=413) > 0 memcontrol04.c:208: TPASS: Expect: (E oom events=0) == 0 memcontrol04.c:214: TPASS: Expect: (E low events=0) == 0 memcontrol04.c:208: TPASS: Expect: (F oom events=0) == 0 memcontrol04.c:214: TFAIL: Expect: (F low events=410) == 0 tst_test.c:1528: TINFO: Testing on ext3 tst_test.c:996: TINFO: Formatting /dev/loop3 with ext3 opts='' extra opts='' mke2fs 1.46.5 (30-Dec-2021) tst_test.c:1456: TINFO: Timeout per run is 0h 05m 00s memcontrol04.c:118: TINFO: Child 119798 in leaf_C: Allocating pagecache: 52428800 memcontrol04.c:118: TINFO: Child 119800 in leaf_D: Allocating pagecache: 52428800 memcontrol04.c:118: TINFO: Child 119801 in leaf_F: Allocating pagecache: 52428800 memcontrol04.c:99: TINFO: Child 119802 in trunk_G: Allocating anon: 155189248 memcontrol04.c:170: TPASS: Expect: (A/B memory.current=54173696) ~= 52428800 memcontrol04.c:176: TPASS: Expect: (A/B/C memory.current=30658560) ~= 34603008 memcontrol04.c:178: TPASS: Expect: (A/B/D memory.current=22560768) ~= 17825792 memcontrol04.c:180: TPASS: Expect: (A/B/E memory.current=0) ~= 0 memcontrol04.c:182: TINFO: A/B/F memory.current=942080 memcontrol04.c:99: TINFO: Child 119803 in trunk_G: Allocating anon: 174063616 memcontrol04.c:195: TINFO: A: low events=1617, oom events=0 memcontrol04.c:195: TINFO: B: low events=1617, oom events=0 memcontrol04.c:195: TINFO: G: low events=0, oom events=0 memcontrol04.c:208: TPASS: Expect: (C oom events=0) == 0 memcontrol04.c:211: TPASS: Expect: (C low events=406) > 0 memcontrol04.c:208: TPASS: Expect: (D oom events=0) == 0 memcontrol04.c:211: TPASS: Expect: (D low events=406) > 0 memcontrol04.c:208: TPASS: Expect: (E oom
[Kernel-packages] [Bug 1973477] [NEW] unable to upgrade to xubuntu
You have been subscribed to a public bug: W: Possible missing firmware /lib/firmware/rtl_nic/rtl8125b-2.fw for module r8169 Errors were encountered while processing: klibc-utils E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 5.13.0-40.45~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun May 15 16:59:41 2022 InstallCmdLine: file=/cdrom/preseed/ubuntu.seed initrd=/casper/initrd quiet splash --- maybe-ubiquity InstallationDate: Installed on 2022-04-20 (24 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: ubiquity Symptom: installation UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-firmware (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: amd64 apport-bug focal ubiquity-20.04.15.10 -- unable to upgrade to xubuntu https://bugs.launchpad.net/bugs/1973477 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1810183] Re: numpad on touchpad doesn't work in ASUS Zenbook 14
** Changed in: linux (Ubuntu) Importance: Undecided => Wishlist -- 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/1810183 Title: numpad on touchpad doesn't work in ASUS Zenbook 14 Status in Linux: New Status in linux package in Ubuntu: Confirmed Bug description: I have Asus Zenbook 14 UX433FA which I have installed Ubuntu 18.10 alongside windows 10. The numeric keypads are within the touchpad and are supposed to be turned on by a button on the touchpad. This works well in Windows but doesn't work in Ubuntu. I have tried to search for any related problems/solutions online but I haven't been able to. I will appreciate any suggestion or help. Thanks, --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-12-30 (4 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Package: linux (not installed) Tags: cosmic Uname: Linux 4.19.11-041911-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-12-30 (4 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Package: linux (not installed) Tags: cosmic Uname: Linux 4.18.10-041810-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1810183/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1958191] Re: [i915] Screen flickering in Ubuntu 22.04 (until i915.enable_dc=0 intel_idle.max_cstate=2 are added)
The monitor going black is a different bug. Please don't discuss that here, but open a new bug by running: ubuntu-bug linux -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1958191 Title: [i915] Screen flickering in Ubuntu 22.04 (until i915.enable_dc=0 intel_idle.max_cstate=2 are added) Status in linux package in Ubuntu: Triaged Bug description: Ubuntu 22.04 development branch on kernel 5.15.0-17-generic @ 18/1/2022 Booting into desktop gets heavy screen flickering and disforming (unusable) both booting on xorg and wayland on kernel 5.13 it did not occur so heavy (only little glitches once in a while see bug 1948778) adding the kernel paramater intel_idle.max_cstate=4 fixed this i had these same bugs on this machine before: https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1838644 https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1948778 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-17-generic 5.15.0-17.17 ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12 Uname: Linux 5.15.0-17-generic x86_64 ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lotuspsychje 1201 F pipewire-media- lotuspsychje 1207 F pulseaudio /dev/snd/seq:lotuspsychje 1193 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Jan 18 04:22:00 2022 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0025 Intel Corp. Wireless-AC 9260 Bluetooth Adapter Bus 001 Device 003: ID 04f2:b59e Chicony Electronics Co., Ltd Chicony USB2.0 Camera Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Notebook N7x0WU ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-17-generic root=UUID=a41247d1-3bc3-453e-849a-e07fdcca6201 ro quiet splash intel_idle.max_cstate=4 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-17-generic N/A linux-backports-modules-5.15.0-17-generic N/A linux-firmware 1.204 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/07/2019 dmi.bios.release: 7.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 7.13 dmi.board.asset.tag: Tag 12345 dmi.board.name: N7x0WU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.ec.firmware.release: 7.14 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr7.13:bd01/07/2019:br7.13:efr7.14:svnNotebook:pnN7x0WU:pvrNotApplicable:rvnNotebook:rnN7x0WU:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A:skuNotApplicable: dmi.product.family: Not Applicable dmi.product.name: N7x0WU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958191/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1958770] Re: Aquantia GbE LAN driver causes UBSAN error during kernel boot
Great! Please consider to send it to upstream mailing list. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1958770 Title: Aquantia GbE LAN driver causes UBSAN error during kernel boot Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.17 package in Ubuntu: Confirmed Bug description: The undefined behaviour sanitiser picks up an array-index-out-of- bounds in the aquantia atlantic driver. The NIC is (I think) built into my gigabyte motherboard (https://www.gigabyte.com/uk/Motherboard/X399-AORUS-XTREME- rev-10/sp#sp). This wasn't an issue before I upgrading from 20.04 to 22.04 (or at least dmesg didn't previously complain). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-17-generic 5.15.0-17.17 ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12 Uname: Linux 5.15.0-17-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Jan 23 13:02:10 2022 InstallationDate: Installed on 2019-08-07 (899 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Gigabyte Technology Co., Ltd. X399 AORUS XTREME ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-17-generic root=UUID=08f6326a-30f9-4f23-bab7-72a48afad354 ro quiet splash resume=UUID=08f6326a-30f9-4f23-bab7-72a48afad354 resume_offset=34816 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-17-generic N/A linux-backports-modules-5.15.0-17-generic N/A linux-firmware 1.204 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/11/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F5 dmi.board.asset.tag: Default string dmi.board.name: X399 AORUS XTREME-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF5:bd12/11/2019:br5.14:svnGigabyteTechnologyCo.,Ltd.:pnX399AORUSXTREME:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX399AORUSXTREME-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: Default string dmi.product.name: X399 AORUS XTREME dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958770/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1972728] Re: Night light not working on Nvidia Wayland
Also tracking in https://github.com/NVIDIA/open-gpu-kernel- modules/issues/162 ** Also affects: nvidia Importance: Undecided Status: New ** No longer affects: nvidia ** Bug watch added: github.com/NVIDIA/open-gpu-kernel-modules/issues #162 https://github.com/NVIDIA/open-gpu-kernel-modules/issues/162 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-510 in Ubuntu. https://bugs.launchpad.net/bugs/1972728 Title: Night light not working on Nvidia Wayland Status in Mutter: Unknown Status in nvidia-graphics-drivers-510 package in Ubuntu: Triaged Bug description: On the Wayland session using an Nvidia GPU, enabling the Night Light setting in the Settings app doesn't change the screen colour temperature to a warmer hue regardless of "Sunset to Sunrise" or "Manual Schedule" being selected. Switching to the X11 session results in Night Light working as expecting. I'm currently using the Nvidia 510.60.02 driver (RTX 2080Ti). $ lsb_release -rd Description: Ubuntu 22.04 LTS Release: 22.04 $ apt-cache policy gnome-shell gnome-shell: Installed: 42.0-2ubuntu1 Candidate: 42.0-2ubuntu1 Version table: *** 42.0-2ubuntu1 500 500 http://gb.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon May 9 22:01:57 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-04-29 (10 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) RelatedPackageVersions: mutter-common 42.0-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1972728/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1973378] Re: kernel BUG in pci_assign_unassigned_bus_resources
Hi, the kernel you're using, 5.4.0-64.72, is relatively old. Can you give the latest Focal kernel 5.4.0-111.125 a try to see if this issue still exist? Thanks ** Changed in: linux (Ubuntu) Status: Confirmed => 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/1973378 Title: kernel BUG in pci_assign_unassigned_bus_resources Status in linux package in Ubuntu: Incomplete Bug description: Tried to re-enumerate the device doing: # echo 1 > /sys/bus/pci/devices/\:d8\:00.2/remove # echo "1" > /sys/bus/pci/rescan ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-64-generic 5.4.0-64.72 ProcVersionSignature: Ubuntu 5.4.0-64.72-generic 5.4.78 Uname: Linux 5.4.0-64-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 13 13:58 seq crw-rw 1 root audio 116, 33 May 13 13:58 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass Date: Fri May 13 14:04:51 2022 InstallationDate: Installed on 2021-04-01 (407 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0557:2419 ATEN International Co., Ltd Bus 001 Device 002: ID 0557:7000 ATEN International Co., Ltd Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/10p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M |__ Port 7: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M |__ Port 1: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M |__ Port 1: Dev 3, If 1, Class=Human Interface Device, Driver=usbhid, 1.5M MachineType: Supermicro SYS-6019U-TR4 PciMultimedia: ProcEnviron: LC_CTYPE=C.UTF-8 TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-64-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro console=tty0 console=ttyS0,115200n8 intel_iommu=on iommu=pt maybe-ubiquity RelatedPackageVersions: linux-restricted-modules-5.4.0-64-generic N/A linux-backports-modules-5.4.0-64-generic N/A linux-firmware1.187.10 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/30/2020 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3.4 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X11DPU dmi.board.vendor: Supermicro dmi.board.version: 1.10 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 1 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3.4:bd10/30/2020:svnSupermicro:pnSYS-6019U-TR4:pvr0123456789:rvnSupermicro:rnX11DPU:rvr1.10:cvnSupermicro:ct1:cvr0123456789: dmi.product.family: To be filled by O.E.M. dmi.product.name: SYS-6019U-TR4 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 13 14:05 seq crw-rw 1 root audio 116, 33 May 13 14:05 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckMismatches: ./boot/grub/efi.img CasperMD5CheckResult: fail DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-09-14 (241 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0557:2419 ATEN International Co., Ltd Bus 001 Device 002: ID 0557:7000 ATEN International Co., Ltd Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/10p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M |__ Port 7: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M |__ Port 1: Dev 3, If 0, Class=Human
[Kernel-packages] [Bug 1958006] Re: multiple UBSAN warnings in Intel IPU6 camera driver at boot
Verified by rebasing reverted commits to them.
** Changed in: linux (Ubuntu)
Status: In Progress => Invalid
** Changed in: linux (Ubuntu Jammy)
Assignee: (unassigned) => You-Sheng Yang (vicamo)
** Tags removed: verification-needed-focal verification-needed-jammy
** Tags added: verification-done-focal verification-done-jammy
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1958006
Title:
multiple UBSAN warnings in Intel IPU6 camera driver at boot
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Fix Committed
Bug description:
[SRU Justfication]
[Impact]
Several UBSAN warnings captured on Intel IPU6 camera equipped platforms
running 5.15+ kernels.
[Fix]
Upstream fix commit 8dcb7d8df28f ("media: pci: intel: Avoid UBSAN
warnings of index bound and shift").
[Test Case]
Boot Intel IPU6 camera equipped platforms and check dmesg.
[Where problems could occur]
This patch turns a few return statements to error to stop further
processing that may fall in UBSAN warnings. No other side effect.
[Other Info]
While plan for -generic and oem-5.17 is still under discuss, only Jammy
is nominated for linux-oem-5.14/focal migration (to hwe-5.15).
This depends on the pull request titled "Support Intel IPU6 MIPI camera
on Alder Lake platforms" for bug 1955383 for Jammy.
== original bug report ==
UBSAN is turned on by default in Ubuntu 5.15 kernel. While Intel IPU6
driver is still suffering from bug 1958004, intel_iommu issue, so
these are found with intel_iommu=off.
[ 51.469485]
[ 51.469490] UBSAN: invalid-load in
/tmp/kernel-vicamo-8789bd62d725-b752/build/include/linux/dma-buf-map.h:224:9
[ 51.469494] load of value 2 is not a valid value for type '_Bool'
[ 51.469497] CPU: 8 PID: 1315 Comm: camerasrc0:src Tainted: G O
5.15.0-2017-generic #17~20.04.1+lp1955383.2
[ 51.469500] Hardware name: Dell Inc. XPS 9320/, BIOS 0.2.7 12/02/2021
[ 51.469501] Call Trace:
[ 51.469504]
[ 51.469508] dump_stack_lvl+0x4a/0x5f
[ 51.469516] dump_stack+0x10/0x12
[ 51.469519] ubsan_epilogue+0x9/0x45
[ 51.469523] __ubsan_handle_load_invalid_value.cold+0x44/0x49
[ 51.469530] dma_buf_vmap.cold+0x38/0x3d
[ 51.469537] ipu_psys_mapbuf_locked+0x178/0x450 [intel_ipu6_psys]
[ 51.469545] ipu_psys_ioctl+0x148/0x4f0 [intel_ipu6_psys]
[ 51.469550] ? __fget_files+0xa7/0xd0
[ 51.469556] __x64_sys_ioctl+0x91/0xc0
[ 51.469560] do_syscall_64+0x59/0xc0
[ 51.469564] ? do_user_addr_fault+0x1dc/0x650
[ 51.469567] ? irqentry_exit_to_user_mode+0x9/0x20
[ 51.469570] ? irqentry_exit+0x19/0x30
[ 51.469573] ? exc_page_fault+0x89/0x160
[ 51.469576] ? asm_exc_page_fault+0x8/0x30
[ 51.469581] entry_SYSCALL_64_after_hwframe+0x44/0xae
[ 51.469585] RIP: 0033:0x7fa5e047250b
[ 51.469588] Code: 0f 1e fa 48 8b 05 85 39 0d 00 64 c7 00 26 00 00 00 48 c7
c0 ff ff ff ff c3 66 0f 1f 44 00 00 f3 0f 1e fa b8 10 00 00 00 0f 05 <48> 3d 01
f0 ff ff 73 01 c3 48 8b 0d 55 39 0d 00 f7 d8 64 89 01 48
[ 51.469589] RSP: 002b:7fa5debfa298 EFLAGS: 0246 ORIG_RAX:
0010
[ 51.469592] RAX: ffda RBX: 7fa5d0004000 RCX:
7fa5e047250b
[ 51.469593] RDX: 001f RSI: c0044102 RDI:
001e
[ 51.469595] RBP: 7fa5d4a371e0 R08: R09:
007c
[ 51.469596] R10: 7fa5debfa120 R11: 0246 R12:
[ 51.469597] R13: 7fa5d4a31bc0 R14: 7fa5debfa36c R15:
7fa5debfa430
[ 51.469598]
[ 51.469599]
[ 52.050608]
[ 52.050620] UBSAN: array-index-out-of-bounds in
/tmp/kernel-vicamo-8789bd62d725-b752/build/drivers/media/pci/intel/ipu6/ipu-resources.c:633:30
[ 52.050631] index -1 is out of range for type 'ipu_resource_alloc [128]'
[ 52.050637] CPU: 8 PID: 803 Comm: psys_sched_cmd Tainted: G O
5.15.0-2017-generic #17~20.04.1+lp1955383.2
[ 52.050647] Hardware name: Dell Inc. XPS 9320/, BIOS 0.2.7 12/02/2021
[ 52.050651] Call Trace:
[ 52.050656]
[ 52.050664] dump_stack_lvl+0x4a/0x5f
[ 52.050692] dump_stack+0x10/0x12
[ 52.050703] ubsan_epilogue+0x9/0x45
[ 52.050716] __ubsan_handle_out_of_bounds.cold+0x44/0x49
[ 52.050731] ipu_psys_allocate_resources+0x4de/0x670 [intel_ipu6_psys]
[ 52.050761] ipu_psys_ppg_start+0xff/0x250 [intel_ipu6_psys]
[ 52.050781] ? ipu_psys_scheduler_ppg_start+0x1b6/0x510 [intel_ipu6_psys]
[ 52.050801] ipu_psys_scheduler_ppg_start+0x429/0x510 [intel_ipu6_psys]
[Kernel-packages] [Bug 1949532] Re: ubuntu_ltp_controllers tests failing on Impish ($cgroup_name already mounted or mount point busy)
** Tags removed: azures ** Tags added: azure -- 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/1949532 Title: ubuntu_ltp_controllers tests failing on Impish ($cgroup_name already mounted or mount point busy) Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Impish: Confirmed Bug description: Almost half of the ubuntu_ltp_controllers tests (142 out of 198) are failing due to the general pattern 'cgroup_name already mounted or mount point busy' causing the tests to fail. e.g. mount: /dev/cgroup: ltp_cgroup already mounted or mount point busy. cgroup_fj_function2_memory 1 TBROK: mount -t cgroup -o memory ltp_cgroup /dev/cgroup failed From investigation it seems there could be an issue with the transition to cgroup-v2. There have been rumors on the ltp mailing list that one of these days the tests could break due to the transition. Switching to cgroup-v2, likely due to a systemd update, could cause these tests to break due to different mount and cgroup hierarchy semantics. I could only reproduce a subset of the new failures we are seeing, but after setting systemd.unified_cgroup_hierarchy=0 on the kernel command line which sets cgroup back to v1, a lot of the failures I could produce went away. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1949532/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1972815] Re: Headset mic with Cirrus logic codec doesn't work
** Changed in: linux (Ubuntu) Status: Incomplete => Invalid ** Changed in: linux-oem-5.14 (Ubuntu) Status: New => Invalid ** Changed in: linux-oem-5.17 (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1972815 Title: Headset mic with Cirrus logic codec doesn't work Status in HWE Next: New Status in linux package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.14 source package in Focal: Fix Committed Status in linux-oem-5.17 source package in Focal: Invalid Status in linux source package in Jammy: In Progress Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: In Progress Bug description: [Impact] Headset mic doesn't be selected automatically after headset is plugged in. [Fix] Cirrus provides a fix for this issue https://patchwork.kernel.org/project/alsa-devel/cover/20220504161236.2490532-1-sbind...@opensource.cirrus.com/ [Test] Verified on the target platform, and confirmed these patches work. [Where problems could occur] These affect the mic detection on CS8409_BULLSEYE, CS8409_WARLOCK, CS8409_WARLOCK_MLK, CS8409_WARLOCK_MLK_DUAL_MIC, CS8409_CYBORG, and CS8409_ODIN platforms. Hard to tell if it introduce any regression, will keep an eye on it. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1972815/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1973485] [NEW] upgrade to 22.04 on raspberry pi can leave ethernet interface unreachable if vlans are used
Public bug reported: The 8021q kernel module was moved from the linux-modules package to the linux-modules-extras package for the Raspberry Pi. This means that vlans cannot be configured if the linux-modules-extras package is not installed. The release notes mention that some modules have been moved and to install the linux-modules-extra package if your application doesn't work. This would be adequate warning except for one issue. Systemd-networkd will fail to configure an ip address for the raspberry pi's ethernet interface when the vlans cannot be configured leaving headless systems inaccessible. I suffered this exact scenario upon upgrading since my netplan file included vlans assigned to the Pi's ethernet interface. I would recommend either updating the release notes to specifically call out this scenario or move the 8021q module back to the linux-modules package. ** Affects: linux-raspi (Ubuntu) Importance: Undecided Status: New ** Tags: raspberrypi vlans -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/1973485 Title: upgrade to 22.04 on raspberry pi can leave ethernet interface unreachable if vlans are used Status in linux-raspi package in Ubuntu: New Bug description: The 8021q kernel module was moved from the linux-modules package to the linux-modules-extras package for the Raspberry Pi. This means that vlans cannot be configured if the linux-modules-extras package is not installed. The release notes mention that some modules have been moved and to install the linux-modules-extra package if your application doesn't work. This would be adequate warning except for one issue. Systemd-networkd will fail to configure an ip address for the raspberry pi's ethernet interface when the vlans cannot be configured leaving headless systems inaccessible. I suffered this exact scenario upon upgrading since my netplan file included vlans assigned to the Pi's ethernet interface. I would recommend either updating the release notes to specifically call out this scenario or move the 8021q module back to the linux-modules package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1973485/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1973434] Re: massive performance issues since 22.04 upgrade
Hi Henning, Just a thought, could you try booting with IOMMU disabled? Edit /etc/default/grub, and append "intel_iommu=off" to GRUB_CMDLINE_LINUX_DEFAULT. Then save, and run "sudo update-grub" and reboot. Between 21.10 and 22.04 we enabled CONFIG_INTEL_IOMMU_DEFAULT_ON=y, and it has caused all sorts of odd issues, including performance related ones, so its worth a shot. We will be reverting the change to CONFIG_INTEL_IOMMU_DEFAULT_ON, and turning it off again in a kernel update in the near future. If "intel_iommu=off" doesn't help, then a make oldconfig with the 22.04 config and 5.17.7 would be interesting to see. Thanks, Matthew -- 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/1973434 Title: massive performance issues since 22.04 upgrade Status in linux package in Ubuntu: Confirmed Bug description: Hi, After upgrading to 22.04 i had to fight with massive performance issues. Browsers appeared to hang every other minute, youtube videos being laggy and hang in between, applications in a virtualbox VM where slow and also hanging every other minute to a level of not being useable. On a pretty recent and powerful system just 2 years old. I noticed CPU jumps in top, but also somehow thought it could be a graphics issue so invested some time installing nvidia drivers properly. Also I wondered if it might be the lowlatency kernel I normally use because I do audio stuff, and switched to generic. But nothing helped. ThenI had the idea it could be a kernel/scheduler issue because the system wasn't always slow, but it appeared certain things kept hanging when other processed had a lot of cpu for a few seconds. So I got a recent mainline kernel, configured it with my last running config from 21.10 before the update, made the debs and installed them, and now can tell that a mainline kernel 5.17.7 with all the dkms modules that i had before which got compiled automatically at installation brings back a "normal" performance. I can browse the web, run multiple youtube vids at once, even in another browser, have thunderbird running, and a virtualbox machine open with another browser for some web app testing and everything runs fine and smooth, no lagging. Not sure yet what the real reason is - either the kernel version, or a patch in the ubuntu version, or the 22.04 kernel config so far, or some configuration made in 21.10 that isn't good with 22.04 and it's kernel anymore. I will go ahead tomorrow and see if I can build a vanilla kernel with the config from the ubuntu 22.04 kernel and "make oldconfig", then I will be able to tell if only the config is making the difference. Please let me know of there is anything I should test to further analyze this issue, or any ideas I can try to solve it without having to run a mainline manually installed kernel. Thanks. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-generic 5.15.0.30.33 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 Uname: Linux 5.15.0-30-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: henning6198 F pulseaudio /dev/snd/controlC1: henning6198 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat May 14 23:02:38 2022 InstallationDate: Installed on 2020-04-12 (761 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 20QV00CEGE ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-30-generic root=/dev/mapper/vgubuntu-root ro RelatedPackageVersions: linux-restricted-modules-5.15.0-30-generic N/A linux-backports-modules-5.15.0-30-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-04-28 (15 days ago) dmi.bios.date: 12/06/2021 dmi.bios.release: 1.42 dmi.bios.vendor: LENOVO dmi.bios.version: N2OET55W (1.42 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QV00CEGE dmi.board.vendor: LENOVO dmi.board.version: SDK0T08861 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.23 dmi.modalias: dmi:bvnLENOVO:bvrN2OET55W(1.42):bd12/06/2021:br1.42:efr1.23:svnLENOVO:pn20QV00CEGE:pvrThinkPadX1Extreme2nd:rvnLENOVO:rn20QV00CEGE:rvrSDK0T08861WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20QV_BU_Think_FM_ThinkPadX1Extreme2nd: dmi.product.family: ThinkPad X1 Extreme 2nd dmi.product.name: 20QV00CEGE dmi.product.sku: LENOVO_MT_20QV_BU_Think_FM_ThinkPad X1 Extreme 2nd dmi.product.version: ThinkPad X1 Extreme 2nd dmi.sys.vendor: LENOVO To manage
[Kernel-packages] [Bug 1973482] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1973482 Title: kernel 4.15.0.177 break everything on Dell XPS 15 9570 Status in linux package in Ubuntu: Confirmed Bug description: There are many issues including: - wireless card DISBLED / UNCLAIMED - no sound output device listed - strange electrical noise in the speakers when the cpu is under load - mounting /boot/efi hangs for 1m30 - various services not starting (snap, etc) Rolling back to 4.15.0.176 fixes all the issues. Can you let me know which logs I could provide to help? Thank you ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-177-generic 4.15.0-177.186 ProcVersionSignature: Ubuntu 4.15.0-177.186-generic 4.15.18 Uname: Linux 4.15.0-177-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.27 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Mon May 16 00:39:58 2022 InstallationDate: Installed on 2018-12-15 (1247 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IwConfig: virbr0no wireless extensions. lono wireless extensions. virbr0-nic no wireless extensions. MachineType: Dell Inc. XPS 15 9570 ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-177-generic root=UUID=d62d426c-0675-4dca-a5e1-6c8b79ed8056 ro acpi_rev_override=1 nouveau.modeset=0 pcie_aspm=force drm.vblankoffdelay=1 scsi_mod.use_blk_mq=1 nouveau.runpm=0 mem_sleep_default=deep noibrs noibpb nopti nospectre_v2 nospectre_v1 l1tf=off nospec_store_bypass_disable no_stf_barrier mds=off mitigations=off clocksource=hpet RelatedPackageVersions: linux-restricted-modules-4.15.0-177-generic N/A linux-backports-modules-4.15.0-177-generic N/A linux-firmware 1.173.20 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/07/2021 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.20.0 dmi.board.name: 0D0T05 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.20.0:bd06/07/2021:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0D0T05:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9570 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973482/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1970453] Re: DMAR: ERROR: DMA PTE for vPFN 0x7bf32 already set
Not running any VMs but I did have SR-IOV and VT-X enabled in the BIOS. Server has a HP B120i which is a fakeraid device and the drives are accessed as simple AHCI devices. -- 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/1970453 Title: DMAR: ERROR: DMA PTE for vPFN 0x7bf32 already set Status in linux package in Ubuntu: Confirmed Bug description: I'm running Ubuntu 22.04 with kernel 5.15.0.27.30 on an HPE ProLiant DL20 Gen9 server. The server has an HPE Smart HBA H240 SATA controller. Since Ubuntu 22.04, the kernel runs into trouble after a few hours of uptime. The problem starts with a few instances of a message such as this: Apr 26 12:03:37 kernel: DMAR: ERROR: DMA PTE for vPFN 0x7bf32 already set (to 7bf32003 not 24c563801) Apr 26 12:03:37 kernel: [ cut here ] Apr 26 12:03:37 kernel: WARNING: CPU: 1 PID: 10171 at drivers/iommu/intel/iommu.c:2391 __domain_mapping.cold+0x94/0xcb Apr 26 12:03:37 kernel: Modules linked in: tls rpcsec_gss_krb5 binfmt_misc ip6t_REJECT nf_reject_ipv6 xt_hl ip6_tables ip6t_rt ipt_REJECT nf_reject_ipv4 xt_LOG nf_log_syslog nft_limit xt_limi> Apr 26 12:03:37 kernel: drm_kms_helper aesni_intel syscopyarea sysfillrect sysimgblt fb_sys_fops xhci_pci cec crypto_simd i2c_i801 rc_core cryptd drm xhci_pci_renesas ahci i2c_smbus tg3 hpsa> Apr 26 12:03:37 kernel: CPU: 1 PID: 10171 Comm: kworker/u4:0 Not tainted 5.15.0-27-generic #28-Ubuntu Apr 26 12:03:37 kernel: Hardware name: HP ProLiant DL20 Gen9/ProLiant DL20 Gen9, BIOS U22 04/01/2021 Apr 26 12:03:37 kernel: Workqueue: writeback wb_workfn (flush-253:2) Apr 26 12:03:37 kernel: RIP: 0010:__domain_mapping.cold+0x94/0xcb Apr 26 12:03:37 kernel: Code: 27 9d 4c 89 4d b8 4c 89 45 c0 e8 03 c5 fa ff 8b 05 e7 e6 40 01 4c 8b 45 c0 4c 8b 4d b8 85 c0 74 09 83 e8 01 89 05 d2 e6 40 01 <0f> 0b e9 7e b2 b1 ff 89 ca 48 83 > Apr 26 12:03:37 kernel: RSP: 0018:c077826b2fa0 EFLAGS: 00010202 Apr 26 12:03:37 kernel: RAX: 0004 RBX: 9f0042062990 RCX: Apr 26 12:03:37 kernel: RDX: RSI: 9f02b3d20980 RDI: 9f02b3d20980 Apr 26 12:03:37 kernel: RBP: c077826b2ff0 R08: 00024c563801 R09: 0024c563 Apr 26 12:03:37 kernel: R10: R11: c01550e0 R12: 000f Apr 26 12:03:37 kernel: R13: 0007bf32 R14: 9f00412f5800 R15: 9f0042062938 Apr 26 12:03:37 kernel: FS: () GS:9f02b3d0() knlGS: Apr 26 12:03:37 kernel: CS: 0010 DS: ES: CR0: 80050033 Apr 26 12:03:37 kernel: CR2: 1530f676a01c CR3: 00029c210001 CR4: 002706e0 Apr 26 12:03:37 kernel: Call Trace: Apr 26 12:03:37 kernel: Apr 26 12:03:37 kernel: intel_iommu_map_pages+0xdc/0x120 Apr 26 12:03:37 kernel: ? __alloc_and_insert_iova_range+0x203/0x240 Apr 26 12:03:37 kernel: __iommu_map+0xda/0x270 Apr 26 12:03:37 kernel: __iommu_map_sg+0x8e/0x120 Apr 26 12:03:37 kernel: iommu_map_sg_atomic+0x14/0x20 Apr 26 12:03:37 kernel: iommu_dma_map_sg+0x345/0x4d0 Apr 26 12:03:37 kernel: __dma_map_sg_attrs+0x68/0x70 Apr 26 12:03:37 kernel: dma_map_sg_attrs+0xe/0x20 Apr 26 12:03:37 kernel: scsi_dma_map+0x39/0x50 Apr 26 12:03:37 kernel: hpsa_scsi_ioaccel2_queue_command.constprop.0+0x11e/0x570 [hpsa] Apr 26 12:03:37 kernel: ? __blk_rq_map_sg+0x36/0x160 Apr 26 12:03:37 kernel: hpsa_scsi_ioaccel_queue_command+0x82/0xd0 [hpsa] Apr 26 12:03:37 kernel: hpsa_ioaccel_submit+0x174/0x190 [hpsa] Apr 26 12:03:37 kernel: hpsa_scsi_queue_command+0x19c/0x240 [hpsa] Apr 26 12:03:37 kernel: ? recalibrate_cpu_khz+0x10/0x10 Apr 26 12:03:37 kernel: scsi_dispatch_cmd+0x93/0x1f0 Apr 26 12:03:37 kernel: scsi_queue_rq+0x2d1/0x690 Apr 26 12:03:37 kernel: blk_mq_dispatch_rq_list+0x126/0x600 Apr 26 12:03:37 kernel: ? __sbitmap_queue_get+0x1/0x10 Apr 26 12:03:37 kernel: __blk_mq_do_dispatch_sched+0xba/0x2d0 Apr 26 12:03:37 kernel: __blk_mq_sched_dispatch_requests+0x104/0x150 Apr 26 12:03:37 kernel: blk_mq_sched_dispatch_requests+0x35/0x60 Apr 26 12:03:37 kernel: __blk_mq_run_hw_queue+0x34/0xb0 Apr 26 12:03:37 kernel: __blk_mq_delay_run_hw_queue+0x162/0x170 Apr 26 12:03:37 kernel: blk_mq_run_hw_queue+0x83/0x120 Apr 26 12:03:37 kernel: blk_mq_sched_insert_requests+0x69/0xf0 Apr 26 12:03:37 kernel: blk_mq_flush_plug_list+0x103/0x1c0 Apr 26 12:03:37 kernel: blk_flush_plug_list+0xdd/0x100 Apr 26 12:03:37 kernel: blk_mq_submit_bio+0x2bd/0x600 Apr 26 12:03:37 kernel: __submit_bio+0x1ea/0x220 Apr 26 12:03:37 kernel: ? mempool_alloc_slab+0x17/0x20 Apr 26 12:03:37 kernel: __submit_bio_noacct+0x85/0x1f0 Apr 26 12:03:37 kernel: submit_bio_noacct+0x4e/0x120 Apr 26 12:03:37 kernel: ? radix_tree_lookup+0xd/0x10
[Kernel-packages] [Bug 1973482] [NEW] kernel 4.15.0.177 break everything on Dell XPS 15 9570
Public bug reported: There are many issues including: - wireless card DISBLED / UNCLAIMED - no sound output device listed - strange electrical noise in the speakers when the cpu is under load - mounting /boot/efi hangs for 1m30 - various services not starting (snap, etc) Rolling back to 4.15.0.176 fixes all the issues. Can you let me know which logs I could provide to help? Thank you ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-177-generic 4.15.0-177.186 ProcVersionSignature: Ubuntu 4.15.0-177.186-generic 4.15.18 Uname: Linux 4.15.0-177-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.27 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Mon May 16 00:39:58 2022 InstallationDate: Installed on 2018-12-15 (1247 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IwConfig: virbr0no wireless extensions. lono wireless extensions. virbr0-nic no wireless extensions. MachineType: Dell Inc. XPS 15 9570 ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-177-generic root=UUID=d62d426c-0675-4dca-a5e1-6c8b79ed8056 ro acpi_rev_override=1 nouveau.modeset=0 pcie_aspm=force drm.vblankoffdelay=1 scsi_mod.use_blk_mq=1 nouveau.runpm=0 mem_sleep_default=deep noibrs noibpb nopti nospectre_v2 nospectre_v1 l1tf=off nospec_store_bypass_disable no_stf_barrier mds=off mitigations=off clocksource=hpet RelatedPackageVersions: linux-restricted-modules-4.15.0-177-generic N/A linux-backports-modules-4.15.0-177-generic N/A linux-firmware 1.173.20 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/07/2021 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.20.0 dmi.board.name: 0D0T05 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.20.0:bd06/07/2021:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0D0T05:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9570 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug 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/1973482 Title: kernel 4.15.0.177 break everything on Dell XPS 15 9570 Status in linux package in Ubuntu: New Bug description: There are many issues including: - wireless card DISBLED / UNCLAIMED - no sound output device listed - strange electrical noise in the speakers when the cpu is under load - mounting /boot/efi hangs for 1m30 - various services not starting (snap, etc) Rolling back to 4.15.0.176 fixes all the issues. Can you let me know which logs I could provide to help? Thank you ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-177-generic 4.15.0-177.186 ProcVersionSignature: Ubuntu 4.15.0-177.186-generic 4.15.18 Uname: Linux 4.15.0-177-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.27 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Mon May 16 00:39:58 2022 InstallationDate: Installed on 2018-12-15 (1247 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IwConfig: virbr0no wireless extensions. lono wireless extensions. virbr0-nic no wireless extensions. MachineType: Dell Inc. XPS 15 9570 ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-177-generic root=UUID=d62d426c-0675-4dca-a5e1-6c8b79ed8056 ro acpi_rev_override=1 nouveau.modeset=0 pcie_aspm=force drm.vblankoffdelay=1 scsi_mod.use_blk_mq=1 nouveau.runpm=0 mem_sleep_default=deep noibrs noibpb nopti nospectre_v2 nospectre_v1 l1tf=off nospec_store_bypass_disable no_stf_barrier mds=off mitigations=off clocksource=hpet RelatedPackageVersions: linux-restricted-modules-4.15.0-177-generic N/A linux-backports-modules-4.15.0-177-generic N/A linux-firmware 1.173.20 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/07/2021 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.20.0 dmi.board.name: 0D0T05 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.20.0:bd06/07/2021:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0D0T05:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9570 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to:
[Kernel-packages] [Bug 1971597] Re: amd_gpio AMDI0030:00: Failed to translate GPIO pin 0x0000 to IRQ, err -517
oem-5.17 got this via 5.17.5
** Changed in: linux-oem-5.17 (Ubuntu Jammy)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.14 in Ubuntu.
https://bugs.launchpad.net/bugs/1971597
Title:
amd_gpio AMDI0030:00: Failed to translate GPIO pin 0x to IRQ, err
-517
Status in HWE Next:
New
Status in linux package in Ubuntu:
Invalid
Status in linux-oem-5.14 package in Ubuntu:
Invalid
Status in linux-oem-5.17 package in Ubuntu:
Invalid
Status in linux source package in Focal:
Invalid
Status in linux-oem-5.14 source package in Focal:
Fix Released
Status in linux-oem-5.17 source package in Focal:
Invalid
Status in linux source package in Jammy:
Fix Committed
Status in linux-oem-5.14 source package in Jammy:
Invalid
Status in linux-oem-5.17 source package in Jammy:
Fix Committed
Bug description:
Commit 5467801f1fcb ("gpio: Restrict usage of GPIO chip irq members
before initialization") attempted to fix a race condition that lead to
a NULL pointer, but in the process caused a regression for _AEI/_EVT
declared GPIOs.
This manifests in messages showing deferred probing while trying to
allocate IRQs like so:
amd_gpio AMDI0030:00: Failed to translate GPIO pin 0x to IRQ, err -517
amd_gpio AMDI0030:00: Failed to translate GPIO pin 0x002C to IRQ, err -517
amd_gpio AMDI0030:00: Failed to translate GPIO pin 0x003D to IRQ, err -517
[ .. more of the same .. ]
The code for walking _AEI doesn't handle deferred probing and so this
leads to non-functional GPIO interrupts.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1971597/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1973463] Re: ZFS kernel null pointer dereference
** Package changed: ubuntu => zfs-linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1973463 Title: ZFS kernel null pointer dereference Status in zfs-linux package in Ubuntu: New Bug description: Ubuntu 22.04 LTS Linux server 5.15.0-30-generic #31-Ubuntu SMP Thu May 5 10:00:34 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux zfs-2.1.2-1ubuntu3 zfs-kmod-2.1.2-1ubuntu3 [ 1249.508427] BUG: kernel NULL pointer dereference, address: 002a [ 1249.508435] #PF: supervisor read access in kernel mode [ 1249.508438] #PF: error_code(0x) - not-present page [ 1249.508440] PGD 0 P4D 0 [ 1249.508444] Oops: [#1] SMP NOPTI [ 1249.508447] CPU: 3 PID: 2119 Comm: txg_sync Tainted: PW O 5.15.0-30-generic #31-Ubuntu [ 1249.508452] Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./AB350M Pro4, BIOS P5.90 07/03/2019 [ 1249.508455] RIP: 0010:rw_owner+0x0/0x10 [zfs] [ 1249.508564] Code: 00 00 c3 0f 1f 80 00 00 00 00 65 48 8b 04 25 c0 fb 01 00 48 89 47 28 c3 66 90 48 c7 47 28 00 00 00 00 c3 0f 1f 80 00 00 00 00 <48> 8b 47 28 c3 66 66 2e 0f 1f 84 00 00 00 00 00 55 48 89 e5 e8 e7 [ 1249.508571] RSP: 0018:a8bec92b7c58 EFLAGS: 00010246 [ 1249.508576] RAX: RBX: 8cca7b162348 RCX: 0001 [ 1249.508580] RDX: RSI: c1494df0 RDI: 0002 [ 1249.508583] RBP: a8bec92b7c60 R08: 8cc62bfa4a80 R09: 8cc62bfa4a80 [ 1249.508587] R10: 8cc62bfa4a80 R11: R12: 8cca7b162280 [ 1249.508590] R13: 0009 R14: 8cca70f1ea30 R15: 8cc62bfa4a80 [ 1249.508594] FS: () GS:8ccdfeac() knlGS: [ 1249.508598] CS: 0010 DS: ES: CR0: 80050033 [ 1249.508601] CR2: 002a CR3: 0004c2b7e000 CR4: 003506e0 [ 1249.508607] Call Trace: [ 1249.508610] [ 1249.508613] ? RW_WRITE_HELD+0x9/0x20 [zfs] [ 1249.508689] dmu_buf_will_dirty_impl+0x87/0x110 [zfs] [ 1249.508786] dmu_buf_will_dirty+0x16/0x20 [zfs] [ 1249.508869] space_map_write+0x3f/0x1a0 [zfs] [ 1249.508970] metaslab_sync+0x60a/0x8b0 [zfs] [ 1249.509066] ? __raw_spin_unlock+0x9/0x10 [zfs] [ 1249.509182] vdev_sync+0x72/0x190 [zfs] [ 1249.509281] spa_sync_iterate_to_convergence+0x14f/0x1e0 [zfs] [ 1249.509388] spa_sync+0x2dc/0x5b0 [zfs] [ 1249.509483] txg_sync_thread+0x266/0x2f0 [zfs] [ 1249.509582] ? txg_dispatch_callbacks+0x100/0x100 [zfs] [ 1249.509683] thread_generic_wrapper+0x64/0x70 [spl] [ 1249.509695] ? __thread_exit+0x20/0x20 [spl] [ 1249.509704] kthread+0x12a/0x150 [ 1249.509708] ? set_kthread_struct+0x50/0x50 [ 1249.509712] ret_from_fork+0x22/0x30 [ 1249.509717] [ 1249.509718] Modules linked in: wireguard curve25519_x86_64 libchacha20poly1305 chacha_x86_64 poly1305_x86_64 libblake2s blake2s_x86_64 libcurve25519_generic libchacha libblake2s_generic sctp ip6_udp_tunnel udp_tunnel macvtap macvlan vhost_net vhost vhost_iotlb tap xt_nat veth xt_conntrack xt_MASQUERADE nf_conntrack_netlink xfrm_user xfrm_algo xt_addrtype br_netfilter ipt_REJECT nf_reject_ipv4 xt_tcpudp nft_compat nft_chain_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nft_counter nf_tables libcrc32c nfnetlink bridge stp llc overlay intel_rapl_msr intel_rapl_common amd64_edac edac_mce_amd zfs(PO) zunicode(PO) snd_hda_codec_realtek kvm_amd zzstd(O) snd_hda_codec_generic zlua(O) snd_hda_codec_hdmi ledtrig_audio kvm crct10dif_pclmul ghash_clmulni_intel zcommon(PO) snd_usb_audio aesni_intel crypto_simd znvpair(PO) cryptd snd_usbmidi_lib zavl(PO) snd_hda_codec wmi_bmof snd_rawmidi rapl k10temp efi_pstore nls_iso8859_1 snd_hda_core snd_seq_device snd_hwdep icp(PO) mc snd_pcm spl(O) [ 1249.509765] input_leds snd_timer snd joydev soundcore ccp mac_hid sch_fq_codel nct6775 hwmon_vid parport_pc ppdev lp parport ip_tables x_tables autofs4 hid_generic usbhid mpt3sas hid nvme uas raid_class usb_storage gpio_amdpt r8169 crc32_pclmul xhci_pci scsi_transport_sas ahci i2c_piix4 realtek e1000e nvme_core libahci xhci_pci_renesas wmi gpio_generic [last unloaded: snd_intel_sdw_acpi] [ 1249.509806] CR2: 002a [ 1249.509808] ---[ end trace 09588539e96f5ea2 ]--- [ 1250.063053] RIP: 0010:rw_owner+0x0/0x10 [zfs] [ 1250.063198] Code: 00 00 c3 0f 1f 80 00 00 00 00 65 48 8b 04 25 c0 fb 01 00 48 89 47 28 c3 66 90 48 c7 47 28 00 00 00 00 c3 0f 1f 80 00 00 00 00 <48> 8b 47 28 c3 66 66 2e 0f 1f 84 00 00 00 00 00 55 48 89 e5 e8 e7 [ 1250.063206] RSP: 0018:a8bec92b7c58 EFLAGS: 00010246 [ 1250.063211] RAX: RBX: 8cca7b162348 RCX: 0001 [ 1250.063215] RDX: RSI: c1494df0 RDI: 0002 [ 1250.063218] RBP: a8bec92b7c60 R08: 8cc62bfa4a80 R09: 8cc62bfa4a80 [ 1250.063222]
[Kernel-packages] [Bug 1973463] [NEW] ZFS kernel null pointer dereference
You have been subscribed to a public bug: Ubuntu 22.04 LTS Linux server 5.15.0-30-generic #31-Ubuntu SMP Thu May 5 10:00:34 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux zfs-2.1.2-1ubuntu3 zfs-kmod-2.1.2-1ubuntu3 [ 1249.508427] BUG: kernel NULL pointer dereference, address: 002a [ 1249.508435] #PF: supervisor read access in kernel mode [ 1249.508438] #PF: error_code(0x) - not-present page [ 1249.508440] PGD 0 P4D 0 [ 1249.508444] Oops: [#1] SMP NOPTI [ 1249.508447] CPU: 3 PID: 2119 Comm: txg_sync Tainted: PW O 5.15.0-30-generic #31-Ubuntu [ 1249.508452] Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./AB350M Pro4, BIOS P5.90 07/03/2019 [ 1249.508455] RIP: 0010:rw_owner+0x0/0x10 [zfs] [ 1249.508564] Code: 00 00 c3 0f 1f 80 00 00 00 00 65 48 8b 04 25 c0 fb 01 00 48 89 47 28 c3 66 90 48 c7 47 28 00 00 00 00 c3 0f 1f 80 00 00 00 00 <48> 8b 47 28 c3 66 66 2e 0f 1f 84 00 00 00 00 00 55 48 89 e5 e8 e7 [ 1249.508571] RSP: 0018:a8bec92b7c58 EFLAGS: 00010246 [ 1249.508576] RAX: RBX: 8cca7b162348 RCX: 0001 [ 1249.508580] RDX: RSI: c1494df0 RDI: 0002 [ 1249.508583] RBP: a8bec92b7c60 R08: 8cc62bfa4a80 R09: 8cc62bfa4a80 [ 1249.508587] R10: 8cc62bfa4a80 R11: R12: 8cca7b162280 [ 1249.508590] R13: 0009 R14: 8cca70f1ea30 R15: 8cc62bfa4a80 [ 1249.508594] FS: () GS:8ccdfeac() knlGS: [ 1249.508598] CS: 0010 DS: ES: CR0: 80050033 [ 1249.508601] CR2: 002a CR3: 0004c2b7e000 CR4: 003506e0 [ 1249.508607] Call Trace: [ 1249.508610] [ 1249.508613] ? RW_WRITE_HELD+0x9/0x20 [zfs] [ 1249.508689] dmu_buf_will_dirty_impl+0x87/0x110 [zfs] [ 1249.508786] dmu_buf_will_dirty+0x16/0x20 [zfs] [ 1249.508869] space_map_write+0x3f/0x1a0 [zfs] [ 1249.508970] metaslab_sync+0x60a/0x8b0 [zfs] [ 1249.509066] ? __raw_spin_unlock+0x9/0x10 [zfs] [ 1249.509182] vdev_sync+0x72/0x190 [zfs] [ 1249.509281] spa_sync_iterate_to_convergence+0x14f/0x1e0 [zfs] [ 1249.509388] spa_sync+0x2dc/0x5b0 [zfs] [ 1249.509483] txg_sync_thread+0x266/0x2f0 [zfs] [ 1249.509582] ? txg_dispatch_callbacks+0x100/0x100 [zfs] [ 1249.509683] thread_generic_wrapper+0x64/0x70 [spl] [ 1249.509695] ? __thread_exit+0x20/0x20 [spl] [ 1249.509704] kthread+0x12a/0x150 [ 1249.509708] ? set_kthread_struct+0x50/0x50 [ 1249.509712] ret_from_fork+0x22/0x30 [ 1249.509717] [ 1249.509718] Modules linked in: wireguard curve25519_x86_64 libchacha20poly1305 chacha_x86_64 poly1305_x86_64 libblake2s blake2s_x86_64 libcurve25519_generic libchacha libblake2s_generic sctp ip6_udp_tunnel udp_tunnel macvtap macvlan vhost_net vhost vhost_iotlb tap xt_nat veth xt_conntrack xt_MASQUERADE nf_conntrack_netlink xfrm_user xfrm_algo xt_addrtype br_netfilter ipt_REJECT nf_reject_ipv4 xt_tcpudp nft_compat nft_chain_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nft_counter nf_tables libcrc32c nfnetlink bridge stp llc overlay intel_rapl_msr intel_rapl_common amd64_edac edac_mce_amd zfs(PO) zunicode(PO) snd_hda_codec_realtek kvm_amd zzstd(O) snd_hda_codec_generic zlua(O) snd_hda_codec_hdmi ledtrig_audio kvm crct10dif_pclmul ghash_clmulni_intel zcommon(PO) snd_usb_audio aesni_intel crypto_simd znvpair(PO) cryptd snd_usbmidi_lib zavl(PO) snd_hda_codec wmi_bmof snd_rawmidi rapl k10temp efi_pstore nls_iso8859_1 snd_hda_core snd_seq_device snd_hwdep icp(PO) mc snd_pcm spl(O) [ 1249.509765] input_leds snd_timer snd joydev soundcore ccp mac_hid sch_fq_codel nct6775 hwmon_vid parport_pc ppdev lp parport ip_tables x_tables autofs4 hid_generic usbhid mpt3sas hid nvme uas raid_class usb_storage gpio_amdpt r8169 crc32_pclmul xhci_pci scsi_transport_sas ahci i2c_piix4 realtek e1000e nvme_core libahci xhci_pci_renesas wmi gpio_generic [last unloaded: snd_intel_sdw_acpi] [ 1249.509806] CR2: 002a [ 1249.509808] ---[ end trace 09588539e96f5ea2 ]--- [ 1250.063053] RIP: 0010:rw_owner+0x0/0x10 [zfs] [ 1250.063198] Code: 00 00 c3 0f 1f 80 00 00 00 00 65 48 8b 04 25 c0 fb 01 00 48 89 47 28 c3 66 90 48 c7 47 28 00 00 00 00 c3 0f 1f 80 00 00 00 00 <48> 8b 47 28 c3 66 66 2e 0f 1f 84 00 00 00 00 00 55 48 89 e5 e8 e7 [ 1250.063206] RSP: 0018:a8bec92b7c58 EFLAGS: 00010246 [ 1250.063211] RAX: RBX: 8cca7b162348 RCX: 0001 [ 1250.063215] RDX: RSI: c1494df0 RDI: 0002 [ 1250.063218] RBP: a8bec92b7c60 R08: 8cc62bfa4a80 R09: 8cc62bfa4a80 [ 1250.063222] R10: 8cc62bfa4a80 R11: R12: 8cca7b162280 [ 1250.063225] R13: 0009 R14: 8cca70f1ea30 R15: 8cc62bfa4a80 [ 1250.063229] FS: () GS:8ccdfeac() knlGS: [ 1250.063234] CS: 0010 DS: ES: CR0: 80050033 [ 1250.063237] CR2: 002a CR3: 0004c2b7e000 CR4: 003506e0 ** Affects:
[Kernel-packages] [Bug 1969247] Re: fallocate with FALLOC_FL_ZERO_RANGE produces zero-size files on zfs in Jammy
It still doesn't work. I'm not able to start mysql-server or mariadb on Ubuntu 22.04 LXC Container running on Proxmox 7.2-3 with ZFS. -- 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/1969247 Title: fallocate with FALLOC_FL_ZERO_RANGE produces zero-size files on zfs in Jammy Status in Native ZFS for Linux: Fix Released Status in mysql-8.0 package in Ubuntu: Invalid Status in zfs-linux package in Ubuntu: Fix Released Status in zfs-linux source package in Jammy: Fix Committed Bug description: [Summary] When running Jammy on zfs or LXD with a zfs pool on a Jammy host, fallocate creates a zero-sized file. The issue was originally found when installing mysql on LXD, where fallocate would create a zero-sized ib_logfile1 file. The original information in this bug is based on that. [Steps to Reproduce] touch foo.img fallocate -z -l 10M foo.img ls -la foo.img On a non-zfs Jammy system this will show something like: -rw-r--r-- 1 root root 10M ... while on zfs it will show: -rw-rw-r-- 1 root root 0 ... [Original Description] I came across this error when testing various mysql setups in an LXD container and managed to reproduce it consistently. I'm unable to reproduce on Ubuntu desktop or server though since the prerequisites are probably handled properly there. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: mysql-server-8.0 8.0.28-0ubuntu0.20.04.3 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Apr 15 21:31:09 2022 Dmesg: ErrorMessage: installed mysql-server-8.0 package post-installation script subprocess returned error exit status 1 KernLog: Logs.var.log.daemon.log: MySQLConf.etc.mysql.conf.d.mysql.cnf: [mysql] MySQLConf.etc.mysql.conf.d.mysqldump.cnf: [mysqldump] quick quote-names max_allowed_packet = 16M MySQLConf.etc.mysql.my.cnf: Error: [Errno 40] Too many levels of symbolic links: '/etc/mysql/my.cnf' MySQLVarLibDirListing: ['ibdata1', 'ib_logfile0', '#innodb_temp', 'debian-5.7.flag', '#ib_16384_0.dblwr', 'client-cert.pem', 'undo_001', 'server-cert.pem', 'mysql.ibd', '#ib_16384_1.dblwr', 'client-key.pem', 'ca-key.pem', 'sys', 'private_key.pem', 'mysql', 'undo_002', 'binlog.index', 'performance_schema', 'ib_buffer_pool', 'auto.cnf', 'ib_logfile1', 'public_key.pem', 'ca.pem', 'server-key.pem'] ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic root=UUID=93666562-b5e4-4fb4-ba8c-7b42a3e6bf61 ro quiet splash mem_sleep_default=deep vt.handoff=7 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: mysql-8.0 Title: package mysql-server-8.0 8.0.28-0ubuntu0.20.04.3 failed to install/upgrade: installed mysql-server-8.0 package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/zfs/+bug/1969247/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1973357] Re: Kernel update to 4.15.0-177 fails to load some kernel modules
I just experienced the same problem today on my Asus G752VT Republic of Gaming laptop. I ended up having to force a power-off by holding down the power button for five seconds because it was stuck trying to booting up. It also wouldn't properly reboot with ALT+CTRL+DEL, getting stuck doing that as well. Once I powered it back on again, I could regain control once I had GRUB boot into the previous kernel again (4.15.0-176). I was able to repeat the same problem by letting it boot into the newer kernel (4.15.0-177) and had to repeat the same steps to regain control again. miles@unicron:~$ uname -a Linux unicron 4.15.0-176-generic #185-Ubuntu SMP Tue Mar 29 17:40:04 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux miles@unicron:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 18.04.6 LTS Release:18.04 Codename: bionic Some lshw details on the model: *-core description: Motherboard product: G752VT vendor: ASUSTeK COMPUTER INC. physical id: 0 version: 1.0 serial: BSN12345678901234567 slot: MIDDLE *-firmware description: BIOS vendor: American Megatrends Inc. physical id: 0 version: G752VT.213 date: 01/06/2016 size: 64KiB capacity: 5952KiB capabilities: pci upgrade shadowing cdboot bootselect socketedrom edd int13floppy1200 int13floppy720 int13floppy2880 int5printscreen int9keyboard int14serial int17printer acpi usb smartbattery biosbootspecification uefi -- 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/1973357 Title: Kernel update to 4.15.0-177 fails to load some kernel modules Status in linux package in Ubuntu: Confirmed Bug description: After update and reboot, severe delay occurs to log in due to network not available. After about 2-3 minutes login worked. No network, no sound and maybe other items. Upon further troubleshooting, the network module is not being loaded. Loading it enabled network. Details below: Linux Mint Cinnamon 19.1 kernel: from 4.15.0-176-generic to 4.15.0-177-generic 4.15.0-177-generic #186-Ubuntu SMP Thu Apr 14 20:23:07 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux Lenovo ideapad 330S laptop lsb_release -rd Description: Linux Mint 19.1 Tessa Release: 19.1 1) cat /proc/version_signature > version.log Ubuntu 4.15.0-176.185-generic 4.15.18 2) sudo lspci -vnvn > lspci-vnvn.log 00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers [8086:5914] (rev 08) Subsystem: Lenovo Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers [17aa:383b] 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: skl_uncore 00:02.0 VGA compatible controller [0300]: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 620 [17aa:396b] 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: Report errors: Correctable- Non-Fatal- Fatal- Unsupported- RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop- MaxPayload 128 bytes, MaxReadReq 128 bytes DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend- DevCap2: Completion Timeout: Not Supported, TimeoutDis-, LTR-, OBFF Not Supported DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, OBFF Disabled 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
