Re: [Kernel-packages] [Bug 1990064] Re: unconfined profile denies userns_create for chromium based processes
> Previously we only had the option of using a system wide sysctl > kernel.unprivileged_userns_clone to disable unprivileged user > namespaces. Debian defaults this to off, and you have to opt in. Just to avoid misunderstandings (I failed to parse the above sentence unambiguously): in Debian, unprivileged user namespaces have been enabled by default since Bullseye. -- 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/1990064 Title: unconfined profile denies userns_create for chromium based processes Status in apparmor package in Ubuntu: Confirmed Status in linux package in Ubuntu: Incomplete Bug description: For Ubuntu 22.10, since the last kernel update, i can´t launch any chromium based browser, due to apparmor denying userns_create dmesg shows: apparmor="DENIED" operation="userns_create" class="namespace" info="User namespace creation restricted" error=-13 profile="unconfined" pid=21323 comm="steamwebhelper" requested="userns_create" denied="userns_create" This happens for every process which uses a chromium engine, like google chrome itself or in this case steamwebhelper. Might be related to this change?: https://patchwork.kernel.org/project/netdevbpf/patch/20220801180146.1157914-5-f...@cloudflare.com/ not sure if it got merged in this form though.. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1990064/+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 1990621] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1990621 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1990621 Title: PXE Boot contains wrong suggested link to ISO for live file system Status in linux package in Ubuntu: Incomplete Bug description: When PXE booting without pulling in squashfs correctly the system tried to be helpful (:-) and grab an ISO. The 22.04.1 Jammy release contains a link to the old version which is not present anymore. --- Unable to find a medium containing a live file system Attempt interactive netboot from a URL? yes no (default yes): Two methods available for IP configuration: * static: for static IP configuration * dhcp: for automatic IP configuration static dhcp (default 'dhcp'): vlan id (optional): https://releases.ubuntu.com/jammy/ubuntu-22.04-live-server-amd64.iso (default) https://releases.ubuntu.com/jammy/ubuntu-22.04-desktop-amd64.iso url: http_proxy (optional): [ 125.454385] igb :00:14.0 eno1: igb: eno1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX [ 125.566067] IPv6: ADDRCONF(NETDEV_CHANGE): eno1: link becomes ready Begin: Trying netboot from 10.0.~.1: ... Begin: Trying to download and mount https://releases.ubuntu.com/jammy/ubuntu-22.04-live-server-amd64.iso ... BusyBox v1.30.1 (Ubuntu 1:1.30.1-7ubuntu3) built-in shell (ash) Enter 'help' for a list of built-in commands. (initramfs) Connecting to releases.ubuntu.com (185.125.190.37:443) wget: server returned error: HTTP/1.1 404 Not Found done. Unable to find a medium containing a live file system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1990621/+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 1990379] Re: [UBUNTU 20.04] zlib: inflate() does not update strm.adler if DFLTCC is used
** Package changed: linux (Ubuntu) => zlib (Ubuntu) ** Also affects: ubuntu-z-systems Importance: Undecided Status: New ** Changed in: ubuntu-z-systems Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team) ** Changed in: ubuntu-z-systems Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1990379 Title: [UBUNTU 20.04] zlib: inflate() does not update strm.adler if DFLTCC is used Status in Ubuntu on IBM z Systems: New Status in zlib package in Ubuntu: New Bug description: == Comment: #0 - Ilya Leoshkevich - 2022-09-21 05:02:24 == inflate() does not update strm.adler if DFLTCC is used. Found with a JDK test. zlib-ng PR: https://github.com/zlib-ng/zlib-ng/pull/1349 Updated zlib PR: https://github.com/madler/zlib/pull/410 zlib tag: https://github.com/iii-i/zlib/releases/tag/dfltcc-20220920 zlib diff: https://github.com/madler/zlib/compare/e6aed68ff815be74855ec6a19d6ae35065a4adb4..171d0ff3c9ed40da0ac14085ab16b766b1162069#diff-325baa03829572a9f26b4bb8b3cada1ddc637854529d6a6cb111b8c3ca785620 Ubuntu 20.04 and later need to be fixed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1990379/+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 1990618] Re: PXE Boot - errors in dhclient-script
I can not boot into the full environment to collect logs. ** 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/1990618 Title: PXE Boot - errors in dhclient-script Status in linux package in Ubuntu: Confirmed Bug description: When booting 22.04.1 using ISO pulled vmlinuz/initrd/squashfs there are some errors in /sbin/dhclient-script. IDs redacted. Internet Systems Consortium DHCP Client 4.4.1 Copyright 2004-2018 Internet Systems Consortium. All rights reserved. For info, please visit https://www.isc.org/software/dhcp/ Listening on LPF/eno1/f0:92:~:~:~:~ Sending on LPF/eno1/f0:92:~:~:~:~ Sending on Socket/fallback DHCPDISCOVER on eno1 to 255.255.255.255 port 67 interval 3 (xid=0xa9d4e16d) DHCPOFFER of 10.0.~.~ from 10.0.~.1 DHCPREQUEST for 10.0.~.~ on eno1 to 255.255.255.255 port 67 (xid=0x6de1d4a9) DHCPACK of 10.0.~.~ from 10.0.~.1 (xid=0xa9d4e16d) /sbin/dhclient-script: line 99: chown: not found chmod: unrecognized option '--reference=/etc/resolv.conf' BusyBox v1.30.1 (Ubuntu 1:1.30.1-7ubuntu3) multi-call binary. Usage: chmod [-R] MODE[,MODE]... FILE... Each MODE is one or more of the letters ugoa, one of the symbols +-= and one or more of the letters rwxst -R Recurse bound to 10.0.~.~ -- renewal in 2963 seconds. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1990618/+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 1990621] [NEW] PXE Boot contains wrong suggested link to ISO for live file system
Public bug reported: When PXE booting without pulling in squashfs correctly the system tried to be helpful (:-) and grab an ISO. The 22.04.1 Jammy release contains a link to the old version which is not present anymore. --- Unable to find a medium containing a live file system Attempt interactive netboot from a URL? yes no (default yes): Two methods available for IP configuration: * static: for static IP configuration * dhcp: for automatic IP configuration static dhcp (default 'dhcp'): vlan id (optional): https://releases.ubuntu.com/jammy/ubuntu-22.04-live-server-amd64.iso (default) https://releases.ubuntu.com/jammy/ubuntu-22.04-desktop-amd64.iso url: http_proxy (optional): [ 125.454385] igb :00:14.0 eno1: igb: eno1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX [ 125.566067] IPv6: ADDRCONF(NETDEV_CHANGE): eno1: link becomes ready Begin: Trying netboot from 10.0.~.1: ... Begin: Trying to download and mount https://releases.ubuntu.com/jammy/ubuntu-22.04-live-server-amd64.iso ... BusyBox v1.30.1 (Ubuntu 1:1.30.1-7ubuntu3) built-in shell (ash) Enter 'help' for a list of built-in commands. (initramfs) Connecting to releases.ubuntu.com (185.125.190.37:443) wget: server returned error: HTTP/1.1 404 Not Found done. Unable to find a medium containing a live file system ** 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/1990621 Title: PXE Boot contains wrong suggested link to ISO for live file system Status in linux package in Ubuntu: New Bug description: When PXE booting without pulling in squashfs correctly the system tried to be helpful (:-) and grab an ISO. The 22.04.1 Jammy release contains a link to the old version which is not present anymore. --- Unable to find a medium containing a live file system Attempt interactive netboot from a URL? yes no (default yes): Two methods available for IP configuration: * static: for static IP configuration * dhcp: for automatic IP configuration static dhcp (default 'dhcp'): vlan id (optional): https://releases.ubuntu.com/jammy/ubuntu-22.04-live-server-amd64.iso (default) https://releases.ubuntu.com/jammy/ubuntu-22.04-desktop-amd64.iso url: http_proxy (optional): [ 125.454385] igb :00:14.0 eno1: igb: eno1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX [ 125.566067] IPv6: ADDRCONF(NETDEV_CHANGE): eno1: link becomes ready Begin: Trying netboot from 10.0.~.1: ... Begin: Trying to download and mount https://releases.ubuntu.com/jammy/ubuntu-22.04-live-server-amd64.iso ... BusyBox v1.30.1 (Ubuntu 1:1.30.1-7ubuntu3) built-in shell (ash) Enter 'help' for a list of built-in commands. (initramfs) Connecting to releases.ubuntu.com (185.125.190.37:443) wget: server returned error: HTTP/1.1 404 Not Found done. Unable to find a medium containing a live file system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1990621/+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 1990618] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1990618 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1990618 Title: PXE Boot - errors in dhclient-script Status in linux package in Ubuntu: Incomplete Bug description: When booting 22.04.1 using ISO pulled vmlinuz/initrd/squashfs there are some errors in /sbin/dhclient-script. IDs redacted. Internet Systems Consortium DHCP Client 4.4.1 Copyright 2004-2018 Internet Systems Consortium. All rights reserved. For info, please visit https://www.isc.org/software/dhcp/ Listening on LPF/eno1/f0:92:~:~:~:~ Sending on LPF/eno1/f0:92:~:~:~:~ Sending on Socket/fallback DHCPDISCOVER on eno1 to 255.255.255.255 port 67 interval 3 (xid=0xa9d4e16d) DHCPOFFER of 10.0.~.~ from 10.0.~.1 DHCPREQUEST for 10.0.~.~ on eno1 to 255.255.255.255 port 67 (xid=0x6de1d4a9) DHCPACK of 10.0.~.~ from 10.0.~.1 (xid=0xa9d4e16d) /sbin/dhclient-script: line 99: chown: not found chmod: unrecognized option '--reference=/etc/resolv.conf' BusyBox v1.30.1 (Ubuntu 1:1.30.1-7ubuntu3) multi-call binary. Usage: chmod [-R] MODE[,MODE]... FILE... Each MODE is one or more of the letters ugoa, one of the symbols +-= and one or more of the letters rwxst -R Recurse bound to 10.0.~.~ -- renewal in 2963 seconds. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1990618/+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 1990618] [NEW] PXE Boot - errors in dhclient-script
Public bug reported: When booting 22.04.1 using ISO pulled vmlinuz/initrd/squashfs there are some errors in /sbin/dhclient-script. IDs redacted. Internet Systems Consortium DHCP Client 4.4.1 Copyright 2004-2018 Internet Systems Consortium. All rights reserved. For info, please visit https://www.isc.org/software/dhcp/ Listening on LPF/eno1/f0:92:~:~:~:~ Sending on LPF/eno1/f0:92:~:~:~:~ Sending on Socket/fallback DHCPDISCOVER on eno1 to 255.255.255.255 port 67 interval 3 (xid=0xa9d4e16d) DHCPOFFER of 10.0.~.~ from 10.0.~.1 DHCPREQUEST for 10.0.~.~ on eno1 to 255.255.255.255 port 67 (xid=0x6de1d4a9) DHCPACK of 10.0.~.~ from 10.0.~.1 (xid=0xa9d4e16d) /sbin/dhclient-script: line 99: chown: not found chmod: unrecognized option '--reference=/etc/resolv.conf' BusyBox v1.30.1 (Ubuntu 1:1.30.1-7ubuntu3) multi-call binary. Usage: chmod [-R] MODE[,MODE]... FILE... Each MODE is one or more of the letters ugoa, one of the symbols +-= and one or more of the letters rwxst -R Recurse bound to 10.0.~.~ -- renewal in 2963 seconds. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: boot pxe ** Summary changed: - PXE Boot + PXE Boot - errors in dhclient-script -- 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/1990618 Title: PXE Boot - errors in dhclient-script Status in linux package in Ubuntu: New Bug description: When booting 22.04.1 using ISO pulled vmlinuz/initrd/squashfs there are some errors in /sbin/dhclient-script. IDs redacted. Internet Systems Consortium DHCP Client 4.4.1 Copyright 2004-2018 Internet Systems Consortium. All rights reserved. For info, please visit https://www.isc.org/software/dhcp/ Listening on LPF/eno1/f0:92:~:~:~:~ Sending on LPF/eno1/f0:92:~:~:~:~ Sending on Socket/fallback DHCPDISCOVER on eno1 to 255.255.255.255 port 67 interval 3 (xid=0xa9d4e16d) DHCPOFFER of 10.0.~.~ from 10.0.~.1 DHCPREQUEST for 10.0.~.~ on eno1 to 255.255.255.255 port 67 (xid=0x6de1d4a9) DHCPACK of 10.0.~.~ from 10.0.~.1 (xid=0xa9d4e16d) /sbin/dhclient-script: line 99: chown: not found chmod: unrecognized option '--reference=/etc/resolv.conf' BusyBox v1.30.1 (Ubuntu 1:1.30.1-7ubuntu3) multi-call binary. Usage: chmod [-R] MODE[,MODE]... FILE... Each MODE is one or more of the letters ugoa, one of the symbols +-= and one or more of the letters rwxst -R Recurse bound to 10.0.~.~ -- renewal in 2963 seconds. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1990618/+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 1990212] Re: [ADL-P-IOTG graphics cause Ubuntu 22.10 hang
we have done following testing。 we revert 4 commits in comment #4 on the 5.19.7 kernel of Canonical and hang issue still happens. https://bugs.launchpad.net/bugs/1980621 7ab7e6aff32de14 UBUNTU: SAUCE: Revert "drm/i915/display: Re-add check for low voltage sku for max dp source rate" (483e3d87a37e in dinq) 727f893039a8f2a UBUNTU: SAUCE: drm/i915: Implement WaEdpLinkRateDataReload (25899c590cb5ba in dinq https://launchpad.net/bugs/1736393 10e940ae5c47622 UBUNTU: SAUCE: drm/i915: make previous commit affects Wyse 3040 only 765fb9d913bec47 UBUNTU: SAUCE: drm/i915:Don't set chip specific data and based on above updates and plus the fix 458ec0c8f35963626cc still 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/1990212 Title: [ADL-P-IOTG graphics cause Ubuntu 22.10 hang Status in intel: New Status in linux package in Ubuntu: Incomplete Bug description: [Bug Description] ADL-P platform from IOTG will have hang issue. when blacklist i915, the system will back to well. but with official 5.19 kernel which support ADL-P (IOTG), we don't find this issue. Canonical please check what addition patches has been included your i915 driver that cause system hang. [HW/SW Information] Target Kernel: 5.19 Target Release: 22.10 Alder Lake -P from Intel IOTG [Business Justification] Function enabling To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1990212/+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 1990212] Re: [ADL-P-IOTG graphics cause Ubuntu 22.10 hang
I will build a canonical kernel with this patch and then test again. hold on. -- 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/1990212 Title: [ADL-P-IOTG graphics cause Ubuntu 22.10 hang Status in intel: New Status in linux package in Ubuntu: Incomplete Bug description: [Bug Description] ADL-P platform from IOTG will have hang issue. when blacklist i915, the system will back to well. but with official 5.19 kernel which support ADL-P (IOTG), we don't find this issue. Canonical please check what addition patches has been included your i915 driver that cause system hang. [HW/SW Information] Target Kernel: 5.19 Target Release: 22.10 Alder Lake -P from Intel IOTG [Business Justification] Function enabling To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1990212/+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 1990212] Re: [ADL-P-IOTG graphics cause Ubuntu 22.10 hang
let us double confirm the previous result. -- 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/1990212 Title: [ADL-P-IOTG graphics cause Ubuntu 22.10 hang Status in intel: New Status in linux package in Ubuntu: Incomplete Bug description: [Bug Description] ADL-P platform from IOTG will have hang issue. when blacklist i915, the system will back to well. but with official 5.19 kernel which support ADL-P (IOTG), we don't find this issue. Canonical please check what addition patches has been included your i915 driver that cause system hang. [HW/SW Information] Target Kernel: 5.19 Target Release: 22.10 Alder Lake -P from Intel IOTG [Business Justification] Function enabling To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1990212/+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 1990212] Re: [ADL-P-IOTG graphics cause Ubuntu 22.10 hang
public 5.19.7 kernel works well which doesn't have this fix. 5.19-rc3 which doesn't have this fix, also don't come across the hang issue. so make me confused. -- 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/1990212 Title: [ADL-P-IOTG graphics cause Ubuntu 22.10 hang Status in intel: New Status in linux package in Ubuntu: Incomplete Bug description: [Bug Description] ADL-P platform from IOTG will have hang issue. when blacklist i915, the system will back to well. but with official 5.19 kernel which support ADL-P (IOTG), we don't find this issue. Canonical please check what addition patches has been included your i915 driver that cause system hang. [HW/SW Information] Target Kernel: 5.19 Target Release: 22.10 Alder Lake -P from Intel IOTG [Business Justification] Function enabling To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1990212/+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 1988721] Re: [SRU][OEM-5.17][PATCH 0/1] Fix output issue of USB-C to DP dongle on AMD
I didn't reproduce this issue on 5.15. Did anyone reproduce it and can verify it? If so I can do SRU for it. -- 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/1988721 Title: [SRU][OEM-5.17][PATCH 0/1] Fix output issue of USB-C to DP dongle on AMD Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Released Bug description: [Impact] There is no output of external 4k DP monitor via USB-C to DP dongle. [Fix] Isolate link training sequence, the external DP monitor will be good. [Test] Verified on hardware, external 4k monitor works fine after re-plugin and suspend. [Where problems could occur] It may break the display output on AMD GPU. This commit is from 5.18-rc1, and no issue on jammy kernel. SRU for oem-5.17 only. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1988721/+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 1990212] Re: [ADL-P-IOTG graphics cause Ubuntu 22.10 hang
it's been picked up in later 5.19. git tag --contains c2798203315f4729bab0b917bf4c17a159abf9f8 v5.19.10 v5.19.8 v5.19.9 -- 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/1990212 Title: [ADL-P-IOTG graphics cause Ubuntu 22.10 hang Status in intel: New Status in linux package in Ubuntu: Incomplete Bug description: [Bug Description] ADL-P platform from IOTG will have hang issue. when blacklist i915, the system will back to well. but with official 5.19 kernel which support ADL-P (IOTG), we don't find this issue. Canonical please check what addition patches has been included your i915 driver that cause system hang. [HW/SW Information] Target Kernel: 5.19 Target Release: 22.10 Alder Lake -P from Intel IOTG [Business Justification] Function enabling To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1990212/+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 1990447] Re: New linux makes wifi driver unstable again
** Tags added: apport-collected una ** Changed in: linux (Ubuntu) Status: Incomplete => Opinion ** Changed in: linux (Ubuntu) Status: Opinion => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1990447 Title: New linux makes wifi driver unstable again Status in linux package in Ubuntu: Invalid Bug description: I'm new to this, sorry if I get it wrong. I'm using Mint, but the update manager links to here as kernels aren't changed by the Mint team. I'm using the rtl8821ce wifi driver which previously had trouble loading again after waking up from sleep. Not every time though and without any pattern. The recent kernel, 5.15.0.46.49~20.04.16 had fixed this problem, which had gone on for over a year before that. Just now I updated again to linux_5.15.0-48.54~20.04.18 and the problem is back. Waking up, sometimes the wifi doesn't work, NetworkManager icon says it's connected but nothing works. I have found that suspending and waking back up, then sudo modprobe -r rtl8821ce, sudo modprobe rtl8821ce will get it working again but that's the only way without shutting down. cat /proc/version_signature Ubuntu 5.15.0-48.54~20.04.1-generic 5.15.53 sudo lspci -vnvn 00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Root Complex [1022:15d0] Subsystem: Hewlett-Packard Company Raven/Raven2 Root Complex [103c:87b7] 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- Capabilities: [64] MSI: Enable+ Count=1/4 Maskable- 64bit+ Address: fee0 Data: 0022 Capabilities: [74] HyperTransport: MSI Mapping Enable+ Fixed+ 00:01.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge [1022:1452] 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- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: [50] Power Management version 3 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Capabilities: [58] Express (v2) Root Port (Slot+), MSI 00 DevCap: MaxPayload 512 bytes, PhantFunc 0 ExtTag+ RBE+ DevCtl: CorrErr+ NonFatalErr+ FatalErr+ UnsupReq+ RlxdOrd+ ExtTag+ PhantFunc- AuxPwr- NoSnoop+ MaxPayload 256 bytes, MaxReadReq 512 bytes DevSta: CorrErr- NonFatalErr- FatalErr- UnsupReq- AuxPwr- TransPend- LnkCap: Port #1, Speed 8GT/s, Width x2, ASPM L1, Exit Latency L1 <64us ClockPM- Surprise- LLActRep+ BwNot+ ASPMOptComp+ LnkCtl: ASPM L1 Enabled; RCB 64 bytes Disabled- CommClk+ ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt- LnkSta: Speed 8GT/s (ok), Width x2 (ok) TrErr- Train- SlotClk+ DLActive+ BWMgmt- ABWMgmt- SltCap: AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd- HotPlug- Surprise- Slot #0, PowerLimit 0.000W; Interlock- NoCompl+ SltCtl: Enable: AttnBtn- PwrFlt- MRL- PresDet- CmdCplt- HPIrq- LinkChg- Control: AttnInd Unknown, PwrInd Unknown, Power- Interlock- SltSta: Status: AttnBtn- PowerFlt- MRL- CmdCplt- PresDet+ Interlock- Changed: MRL- PresDet- LinkState+ RootCap: CRSVisible+ RootCtl: ErrCorrectable- ErrNon-Fatal- ErrFatal- PMEIntEna+ CRSVisible+ RootSta: PME ReqID , PMEStatus- PMEPending- DevCap2: Completion Timeout: Range ABCD, TimeoutDis+, NROPrPrP-, LTR+ 10BitTagComp-, 10BitTagReq-, OBFF Not Supported, ExtFmt+, EETLPPrefix+, MaxEETLPPrefixes 1 EmergencyPowerReduction Not Supported, EmergencyPowerReductionInit- FRS-, LN System CLS Not Supported, TPHComp-, ExtTPHComp-, ARIFwd+ AtomicOpsCap: Routing- 32bit+ 64bit+ 128bitCAS- DevCtl2: Completion Timeout: 65ms to 210ms, TimeoutDis-, LTR+, OBFF Disabled ARIFwd- AtomicOpsCtl: ReqEn- EgressBlck- LnkCtl2: Target Link Speed: 8GT/s, EnterCompliance- SpeedDis- Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS- Compliance De-emphasis: -6dB
[Kernel-packages] [Bug 1842320] Re: Can't boot: "error: out of memory." immediately after the grub menu
Hi Julian, I didn't see the 'boot failures on older system' from comment#90. Would you please point it out more specifically? -- 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/1842320 Title: Can't boot: "error: out of memory." immediately after the grub menu Status in grub: Unknown Status in OEM Priority Project: Triaged Status in grub2-signed package in Ubuntu: Confirmed Status in initramfs-tools package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: [Impact] * In some cases, if the users’ initramfs grow bigger, then it’ll likely not be able to be loaded by grub2. * Some real cases from OEM projects: In many built-in 4k monitor laptops with nvidia drivers, the u-d-c puts the nvidia*.ko to initramfs which grows the initramfs to ~120M. Also the gfxpayload=auto will remain to use 4K resolution since it’s what EFI POST passed. In this case, the grub isn't able to load initramfs because the grub_memalign() won't be able to get suitable memory for the larger file: ``` #0 grub_memalign (align=1, size=592214020) at ../../../grub-core/kern/mm.c:376 #1 0x7dd7b074 in grub_malloc (size=592214020) at ../../../grub-core/kern/mm.c:408 #2 0x7dd7a2c8 in grub_verifiers_open (io=0x7bc02d80, type=131076) at ../../../grub-core/kern/verifiers.c:150 #3 0x7dd801d4 in grub_file_open (name=0x7bc02f00 "/boot/initrd.img-5.17.0-1011-oem", type=131076) at ../../../grub-core/kern/file.c:121 #4 0x7bcd5a30 in ?? () #5 0x7fe21247 in ?? () #6 0x7bc030c8 in ?? () #7 0x00017fe21238 in ?? () #8 0x7bcd5320 in ?? () #9 0x7fe21250 in ?? () #10 0x in ?? () ``` Based on grub_mm_dump, we can see the memory fragment (some parts seem likely be used because of 4K resolution?) and doesn’t have available contiguous memory for larger file as: ``` grub_real_malloc(...) ... if (cur->size >= n + extra) ``` Based on UEFI Specification Section 7.2[1] and UEFI driver writers’ guide 4.2.3[2], we can ask 32bits+ on AllocatePages(). As most X86_64 platforms should support 64 bits addressing, we should extend GRUB_EFI_MAX_USABLE_ADDRESS to 64 bits to get more available memory. * When users grown the initramfs, then probably will get initramfs not found which really annoyed and impact the user experience (system not able to boot). [Test Plan] * detailed instructions how to reproduce the bug: 1. Any method to grow the initramfs, such as install nvidia-driver. 2. If developers would like to reproduce, then could dd if=/dev/random of=... bs=1M count=500, something like: ``` $ cat /usr/share/initramfs-tools/hooks/zzz-touch-a-file #!/bin/sh PREREQ="" prereqs() { echo "$PREREQ" } case $1 in # get pre-requisites prereqs) prereqs exit 0 ;; esac . /usr/share/initramfs-tools/hook-functions dd if=/dev/random of=${DESTDIR}/test-500M bs=1M count=500 ``` And then update-initramfs * After applying my patches, the issue is gone. * I did also test my test grubx64.efi in: 1. X86_64 qemu with 1.1. 60M initramfs + 5.15.0-37-generic kernel 1.2. 565M initramfs + 5.17.0-1011-oem kernel 2. Amd64 HP mobile workstation with 2.1. 65M initramfs + 5.15.0-39-generic kernel 2.2. 771M initramfs + 5.17.0-1011-oem kernel All working well. [Where problems could occur] * The changes almost in i386/efi, thus the impact will be in the i386 / x86_64 EFI system. The other change is to modify the “grub-core/kern/efi/mm.c” but I use the original addressing for “arm/arm64/ia64/riscv32/riscv64”. Thus it should not impact them. * There is a “#if defined(__x86_64__)” which intent to limit the > 32bits code in i386 system and also ``` #if defined (__code_model_large__) -#define GRUB_EFI_MAX_USABLE_ADDRESS 0x +#define GRUB_EFI_MAX_USABLE_ADDRESS __UINTPTR_MAX__ +#define GRUB_EFI_MAX_ALLOCATION_ADDRESS 0x7fff #else #define GRUB_EFI_MAX_USABLE_ADDRESS 0x7fff +#define GRUB_EFI_MAX_ALLOCATION_ADDRESS 0x3fff #endif ``` If everything works as expected, then i386 should working good. If not lucky, based on “UEFI writers’ guide”[2], the i386 will get > 4GB memory region and never be able to access. [Other Info] * Upstream grub2 bug #61058 https://savannah.gnu.org/bugs/index.php?61058 * Test PPA: https://launchpad.net/~os369510/+archive/ubuntu/lp1842320 * Test grubx64.efi: https://people.canonical.com/~jeremysu/lp1842320/grubx64.efi.lp1842320 * Test source code: https://github.com/os369510/grub2/tree/lp1842320 * If you built the package, then test grubx64.efi is under “obj/monolithic/grub-efi-amd64/grubx64.efi”, in my case:
[Kernel-packages] [Bug 1990212] Re: [ADL-P-IOTG graphics cause Ubuntu 22.10 hang
just a minute, this fix has been in v6.0-rc4, so v6.0-rc6 should have it. but it doesn't work on ADL-P (IOTG) -- 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/1990212 Title: [ADL-P-IOTG graphics cause Ubuntu 22.10 hang Status in intel: New Status in linux package in Ubuntu: Incomplete Bug description: [Bug Description] ADL-P platform from IOTG will have hang issue. when blacklist i915, the system will back to well. but with official 5.19 kernel which support ADL-P (IOTG), we don't find this issue. Canonical please check what addition patches has been included your i915 driver that cause system hang. [HW/SW Information] Target Kernel: 5.19 Target Release: 22.10 Alder Lake -P from Intel IOTG [Business Justification] Function enabling To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1990212/+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 1990212] Re: [ADL-P-IOTG graphics cause Ubuntu 22.10 hang
git tag --contains 458ec0c8f35963626ccd51c3d50b752de5f1b9d4 v6.0-rc4 v6.0-rc5 v6.0-rc6 -- 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/1990212 Title: [ADL-P-IOTG graphics cause Ubuntu 22.10 hang Status in intel: New Status in linux package in Ubuntu: Incomplete Bug description: [Bug Description] ADL-P platform from IOTG will have hang issue. when blacklist i915, the system will back to well. but with official 5.19 kernel which support ADL-P (IOTG), we don't find this issue. Canonical please check what addition patches has been included your i915 driver that cause system hang. [HW/SW Information] Target Kernel: 5.19 Target Release: 22.10 Alder Lake -P from Intel IOTG [Business Justification] Function enabling To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1990212/+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 1990212] Re: [ADL-P-IOTG graphics cause Ubuntu 22.10 hang
ok, I will have a try for that. -- 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/1990212 Title: [ADL-P-IOTG graphics cause Ubuntu 22.10 hang Status in intel: New Status in linux package in Ubuntu: Incomplete Bug description: [Bug Description] ADL-P platform from IOTG will have hang issue. when blacklist i915, the system will back to well. but with official 5.19 kernel which support ADL-P (IOTG), we don't find this issue. Canonical please check what addition patches has been included your i915 driver that cause system hang. [HW/SW Information] Target Kernel: 5.19 Target Release: 22.10 Alder Lake -P from Intel IOTG [Business Justification] Function enabling To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1990212/+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 1990595] [NEW] Kernel Module usbserial not available on Jammy 22.04 (Raspi 4)
Public bug reported: After installing a USB to Serial Adapter on a Raspberry Pi 4 running Ubuntu Server 22.04 LTS, no tty device is created under /dev/ttyUSB... dmesg: [3.793123] usb 1-1.2.1: New USB device found, idVendor=0403, idProduct=6001, bcdDevice= 6.00 [3.793142] usb 1-1.2.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [3.793149] usb 1-1.2.1: Product: FT232R USB UART [3.793155] usb 1-1.2.1: Manufacturer: FTDI [3.793160] usb 1-1.2.1: SerialNumber: A504D2PO The usbserial and ftdi_sio kernel modules are not included in the linux- modules-extra-5.15.0-1015-raspi package. dpkg-query -L linux-modules-extra-5.15.0-1015-raspi |grep -E 'usbserial|ftdio_sio' => NO OUTPUT lsb_release -rd: Description:Ubuntu 22.04.1 LTS Release:22.04 uname -a: Linux Host 5.15.0-1014-raspi #16-Ubuntu SMP PREEMPT Thu Aug 25 09:50:55 UTC 2022 aarch64 aarch64 aarch64 GNU/Linux For Reference: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1947723 Configuration from /boot/config-5.15.0-1014-raspi: grep USB_SERIAL /boot/config-5.15.0-1014-raspi CONFIG_USB_SERIAL=m <= set CONFIG_USB_SERIAL_GENERIC=y <= set CONFIG_USB_SERIAL_FTDI_SIO=m <= set Fix: According to the configuration, the modules should be built. Include the modules in the package. ** Affects: linux-raspi (Ubuntu) Importance: Undecided Status: New ** Description changed: - After installing a USB to Serial Adapter on a Raspberry PI 4 running + After installing a USB to Serial Adapter on a Raspberry Pi 4 running Ubuntu Server 22.04 LTS, no tty device is created under /dev/ttyUSB... dmesg: [3.793123] usb 1-1.2.1: New USB device found, idVendor=0403, idProduct=6001, bcdDevice= 6.00 [3.793142] usb 1-1.2.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [3.793149] usb 1-1.2.1: Product: FT232R USB UART [3.793155] usb 1-1.2.1: Manufacturer: FTDI [3.793160] usb 1-1.2.1: SerialNumber: A504D2PO The usbserial and ftdi_sio kernel modules are not included in the linux- modules-extra-5.15.0-1015-raspi package. dpkg-query -L linux-modules-extra-5.15.0-1015-raspi |grep -E 'usbserial|ftdio_sio' => NO OUTPUT lsb_release -rd: Description:Ubuntu 22.04.1 LTS Release:22.04 uname -a: Linux Host 5.15.0-1014-raspi #16-Ubuntu SMP PREEMPT Thu Aug 25 09:50:55 UTC 2022 aarch64 aarch64 aarch64 GNU/Linux For Reference: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1947723 - Configuration from /boot/config-5.15.0-1014-raspi: grep USB_SERIAL /boot/config-5.15.0-1014-raspi CONFIG_USB_SERIAL=m <= set CONFIG_USB_SERIAL_GENERIC=y <= set CONFIG_USB_SERIAL_FTDI_SIO=m <= set - Fix: + Fix: According to the configuration, the modules should be built. Include the modules in the package. -- 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/1990595 Title: Kernel Module usbserial not available on Jammy 22.04 (Raspi 4) Status in linux-raspi package in Ubuntu: New Bug description: After installing a USB to Serial Adapter on a Raspberry Pi 4 running Ubuntu Server 22.04 LTS, no tty device is created under /dev/ttyUSB... dmesg: [3.793123] usb 1-1.2.1: New USB device found, idVendor=0403, idProduct=6001, bcdDevice= 6.00 [3.793142] usb 1-1.2.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [3.793149] usb 1-1.2.1: Product: FT232R USB UART [3.793155] usb 1-1.2.1: Manufacturer: FTDI [3.793160] usb 1-1.2.1: SerialNumber: A504D2PO The usbserial and ftdi_sio kernel modules are not included in the linux-modules-extra-5.15.0-1015-raspi package. dpkg-query -L linux-modules-extra-5.15.0-1015-raspi |grep -E 'usbserial|ftdio_sio' => NO OUTPUT lsb_release -rd: Description:Ubuntu 22.04.1 LTS Release:22.04 uname -a: Linux Host 5.15.0-1014-raspi #16-Ubuntu SMP PREEMPT Thu Aug 25 09:50:55 UTC 2022 aarch64 aarch64 aarch64 GNU/Linux For Reference: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1947723 Configuration from /boot/config-5.15.0-1014-raspi: grep USB_SERIAL /boot/config-5.15.0-1014-raspi CONFIG_USB_SERIAL=m <= set CONFIG_USB_SERIAL_GENERIC=y <= set CONFIG_USB_SERIAL_FTDI_SIO=m <= set Fix: According to the configuration, the modules should be built. Include the modules in the package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1990595/+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 1990064] Re: unconfined profile denies userns_create for chromium based processes
In short unprivileged user namespaces a vector for exploit chains, as they expose interfaces that otherwise would not be available. 4 out 5 exploits chains in pwn2own 2022 used unprivileged user namespaces. They were also used in 2021, 2020, ... Yes the actual vulnerabilities were in other interface io_uring, ebpf, nftables, ... but none of them would have been available without unprivileged user namespaces. Previously we only had the option of using a system wide sysctl kernel.unprivileged_userns_clone to disable unprivileged user namespaces. Debian defaults this to off, and you have to opt in. Ubuntu is now moving towards a more fine grained approach where they can be selectively turned on for some applications but aren't generally available. For 22.10 the apparmor sysctl will be defaulted to off, while further packaging work is done for applications that need access to unprivileged user namespaces. -- 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/1990064 Title: unconfined profile denies userns_create for chromium based processes Status in apparmor package in Ubuntu: Confirmed Status in linux package in Ubuntu: Incomplete Bug description: For Ubuntu 22.10, since the last kernel update, i can´t launch any chromium based browser, due to apparmor denying userns_create dmesg shows: apparmor="DENIED" operation="userns_create" class="namespace" info="User namespace creation restricted" error=-13 profile="unconfined" pid=21323 comm="steamwebhelper" requested="userns_create" denied="userns_create" This happens for every process which uses a chromium engine, like google chrome itself or in this case steamwebhelper. Might be related to this change?: https://patchwork.kernel.org/project/netdevbpf/patch/20220801180146.1157914-5-f...@cloudflare.com/ not sure if it got merged in this form though.. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1990064/+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 1990064] Re: unconfined profile denies userns_create for chromium based processes
NB, also broke Steam (from .deb). Is there a link anywhere to some of this discussion, happy for security to be improved, but I'd like to understand what is being disabled, and what the specific issue is. -- 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/1990064 Title: unconfined profile denies userns_create for chromium based processes Status in apparmor package in Ubuntu: Confirmed Status in linux package in Ubuntu: Incomplete Bug description: For Ubuntu 22.10, since the last kernel update, i can´t launch any chromium based browser, due to apparmor denying userns_create dmesg shows: apparmor="DENIED" operation="userns_create" class="namespace" info="User namespace creation restricted" error=-13 profile="unconfined" pid=21323 comm="steamwebhelper" requested="userns_create" denied="userns_create" This happens for every process which uses a chromium engine, like google chrome itself or in this case steamwebhelper. Might be related to this change?: https://patchwork.kernel.org/project/netdevbpf/patch/20220801180146.1157914-5-f...@cloudflare.com/ not sure if it got merged in this form though.. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1990064/+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 1990064] Re: unconfined profile denies userns_create for chromium based processes
It broke for me between 5.19.0-15 and 5.19.0-17, and breaks every flatpak app I have installed. -- 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/1990064 Title: unconfined profile denies userns_create for chromium based processes Status in apparmor package in Ubuntu: Confirmed Status in linux package in Ubuntu: Incomplete Bug description: For Ubuntu 22.10, since the last kernel update, i can´t launch any chromium based browser, due to apparmor denying userns_create dmesg shows: apparmor="DENIED" operation="userns_create" class="namespace" info="User namespace creation restricted" error=-13 profile="unconfined" pid=21323 comm="steamwebhelper" requested="userns_create" denied="userns_create" This happens for every process which uses a chromium engine, like google chrome itself or in this case steamwebhelper. Might be related to this change?: https://patchwork.kernel.org/project/netdevbpf/patch/20220801180146.1157914-5-f...@cloudflare.com/ not sure if it got merged in this form though.. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1990064/+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 1987232] Re: WARN in trace_event_dyn_put_ref
I ran the original reproducer on a VM that was running linux/5.15.0-50.56 and linux/linux/5.15.0-46.49. On the former the problem did not reproduce, but on the latter it did. Marking this as verified via testing and setting 'verification-done-jammy'. ** Tags added: 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/1987232 Title: WARN in trace_event_dyn_put_ref Status in linux package in Ubuntu: Confirmed Status in linux source package in Jammy: Fix Committed Status in linux source package in Kinetic: Confirmed Bug description: [SRU Justification] Impact: Some imbalanced ref-counting produces kernel warnings regularly. Since it is a warning level, this triggers system monitoring on servers which in turn causes unnecessary work for inspecting the logs. Fix: There is a fix upstream and also backported to the upstream stable branch. However we are still a bit behind catching up with the latest versions. Since this is having quite an impact and the fix is rather straight forward, we pull this in from upstream stable ahead of time. Test case: tbd Regression potential: Regressions would manifest as different errors related to ref-counting. --- I have systems that are regularly hitting a WARN in trace_event_dyn_put_ref. The exact message is: WARNING: CPU: 1 PID: 30309 at kernel/trace/trace_dynevent.c:46 +trace_event_dyn_put_ref+0x15/0x20 With the following stacktrace: perf_trace_init+0x8f/0xd0 perf_tp_event_init+0x1f/0x40 perf_try_init_event+0x4a/0x130 perf_event_alloc+0x497/0xf40 __do_sys_perf_event_open+0x1d4/0xf70 __x64_sys_perf_event_open+0x20/0x30 do_syscall_64+0x5c/0xc0 entry_SYSCALL_64_after_hwframe+0x44/0xae I've debugged this and worked with upstream to get a fix into Linux. It was recently merged in 6.0-rc2. See here: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v6.0-rc2=7249921d94ff64f67b733eca0b68853a62032b3d The problem started appearing as soon as our systems picked up the linux-aws-5.15 branch for Focal. (That was 5.15.0-1015-aws, if memory serves). Could you please cherry pick this fix and pull it back to the the linux and linux-aws kernels for Focal? There's test here: https://lore.kernel.org/all/cover.1660347763.git.k...@templeofstupid.com/ that reproduces the problem very reliably for me. With the patch applied, I no longer get the WARNs. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Aug 22 17:32 seq crw-rw 1 root audio 116, 33 Aug 22 17:32 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: Amazon EC2 c5d.12xlarge Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-1015-aws root=PARTUUID=4986e35b-1bd5-45d3-b528-fa2edb861a38 ro console=tty1 console=ttyS0 nvme_core.io_timeout=4294967295 panic=-1 ProcVersionSignature: Ubuntu 5.15.0-1015.19~20.04.1-aws 5.15.39 RelatedPackageVersions: linux-restricted-modules-5.15.0-1015-aws N/A linux-backports-modules-5.15.0-1015-aws N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal uec-images Uname: Linux 5.15.0-1015-aws 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: 10/16/2017 dmi.bios.release: 1.0 dmi.bios.vendor: Amazon EC2 dmi.bios.version: 1.0 dmi.board.asset.tag: i-03f5d8581c7ad94aa dmi.board.vendor: Amazon EC2 dmi.chassis.asset.tag: Amazon EC2 dmi.chassis.type: 1 dmi.chassis.vendor: Amazon EC2 dmi.modalias: dmi:bvnAmazonEC2:bvr1.0:bd10/16/2017:br1.0:svnAmazonEC2:pnc5d.12xlarge:pvr:rvnAmazonEC2:rn:rvr:cvnAmazonEC2:ct1:cvr:sku: dmi.product.name: c5d.12xlarge dmi.sys.vendor: Amazon EC2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1987232/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages
[Kernel-packages] [Bug 1990564] [NEW] Jammy update: v5.15.63 upstream stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.15.63 upstream stable release from git://git.kernel.org/ ALSA: info: Fix llseek return value when using callback ALSA: hda/realtek: Add quirk for Clevo NS50PU, NS70PU KVM: Unconditionally get a ref to /dev/kvm module when creating a VM x86/mm: Use proper mask when setting PUD mapping rds: add missing barrier to release_refill locking/atomic: Make test_and_*_bit() ordered on failure drm/nouveau: recognise GA103 drm/ttm: Fix dummy res NULL ptr deref bug drm/amd/display: Check correct bounds for stream encoder instances for DCN303 ata: libata-eh: Add missing command name mmc: pxamci: Fix another error handling path in pxamci_probe() mmc: pxamci: Fix an error handling path in pxamci_probe() mmc: meson-gx: Fix an error handling path in meson_mmc_probe() btrfs: unset reloc control if transaction commit fails in prepare_to_relocate() btrfs: reset RO counter on block group if we fail to relocate btrfs: fix lost error handling when looking up extended ref on log replay cifs: Fix memory leak on the deferred close x86/kprobes: Fix JNG/JNLE emulation tracing/eprobes: Do not allow eprobes to use $stack, or % for regs tracing/eprobes: Do not hardcode $comm as a string tracing/eprobes: Have event probes be consistent with kprobes and uprobes tracing/probes: Have kprobes and uprobes use $COMM too tracing: Have filter accept "common_cpu" to be consistent ALSA: usb-audio: More comprehensive mixer map for ASUS ROG Zenith II dt-bindings: usb: mtk-xhci: Allow wakeup interrupt-names to be optional can: ems_usb: fix clang's -Wunaligned-access warning apparmor: fix quiet_denied for file rules Revert "UBUNTU: SAUCE: apparmor: drop prefixing abs root labels with '='" apparmor: fix absroot causing audited secids to begin with = apparmor: Fix failed mount permission check error message apparmor: fix aa_label_asxprint return check apparmor: fix setting unconfined mode on a loaded profile apparmor: fix overlapping attachment computation apparmor: fix reference count leak in aa_pivotroot() apparmor: Fix memleak in aa_simple_write_to_buffer() Documentation: ACPI: EINJ: Fix obsolete example NFSv4.1: Don't decrease the value of seq_nr_highest_sent NFSv4.1: Handle NFS4ERR_DELAY replies to OP_SEQUENCE correctly NFSv4: Fix races in the legacy idmapper upcall NFSv4.1: RECLAIM_COMPLETE must handle EACCES NFSv4/pnfs: Fix a use-after-free bug in open BPF: Fix potential bad pointer dereference in bpf_sys_bpf() bpf: Don't reinit map value in prealloc_lru_pop bpf: Acquire map uref in .init_seq_private for array map iterator bpf: Acquire map uref in .init_seq_private for hash map iterator bpf: Acquire map uref in .init_seq_private for sock local storage map iterator bpf: Acquire map uref in .init_seq_private for sock{map,hash} iterator bpf: Check the validity of max_rdwr_access for sock local storage map iterator can: mcp251x: Fix race condition on receive interrupt can: j1939: j1939_session_destroy(): fix memory leak of skbs net: atlantic: fix aq_vec index out of range error m68k: coldfire/device.c: protect FLEXCAN blocks sunrpc: fix expiry of auth creds SUNRPC: Fix xdr_encode_bool() SUNRPC: Reinitialise the backchannel request buffers before reuse virtio_net: fix memory leak inside XPD_TX with mergeable devlink: Fix use-after-free after a failed reload net: phy: Warn about incorrect mdio_bus_phy_resume() state net: bcmgenet: Indicate MAC is in charge of PHY PM net: bgmac: Fix a BUG triggered by wrong bytes_compl selftests: forwarding: Fix failing tests with old libnet dt-bindings: arm: qcom: fix Alcatel OneTouch Idol 3 compatibles pinctrl: nomadik: Fix refcount leak in nmk_pinctrl_dt_subnode_to_map pinctrl: qcom: msm8916: Allow CAMSS GP clocks to be muxed pinctrl: amd: Don't save/restore interrupt status and wake status bits pinctrl: sunxi: Add I/O bias setting for H6 R-PIO pinctrl: qcom: sm8250: Fix PDC map Input: exc3000 - fix return value check of wait_for_completion_timeout octeontx2-pf: Fix NIX_AF_TL3_TL2X_LINKX_CFG register configuration octeontx2-af: Apply tx nibble fixup always octeontx2-af: suppress external profile loading warning octeontx2-af: Fix mcam entry resource leak octeontx2-af: Fix key checking for source mac ACPI: property: Return type of acpi_add_nondev_subnodes() should be bool geneve: do not use RT_TOS for IPv6 flowlabel mlx5: do not use RT_TOS for IPv6 flowlabel ipv6: do not use RT_TOS for IPv6 flowlabel plip: avoid rcu debug splat vsock: Fix memory leak in vsock_connect() vsock: Set socket state back to SS_UNCONNECTED in vsock_connect_timeout()
[Kernel-packages] [Bug 1990554] [NEW] Jammy update: v5.15.62 upstream stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.15.62 upstream stable release from git://git.kernel.org/ io_uring: use original request task for inflight tracking tee: add overflow check in register_shm_helper() net_sched: cls_route: disallow handle of 0 ksmbd: prevent out of bound read for SMB2_WRITE ksmbd: fix heap-based overflow in set_ntacl_dacl() btrfs: only write the sectors in the vertical stripe which has data stripes btrfs: raid56: don't trust any cached sector in __raid56_parity_recover() Linux 5.15.62 UBUNTU: Upstream stable to v5.15.62 ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Jammy) Importance: Medium Assignee: Kamal Mostafa (kamalmostafa) Status: In Progress ** Tags: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid ** Changed in: linux (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Jammy) Assignee: (unassigned) => Kamal Mostafa (kamalmostafa) ** Description changed: + SRU Justification - SRU Justification + Impact: + The upstream process for stable tree updates is quite similar + in scope to the Ubuntu SRU process, e.g., each patch has to + demonstrably fix a bug, and each patch is vetted by upstream + by originating either directly from a mainline/stable Linux tree or + a minimally backported form of that patch. The following upstream + stable patches should be included in the Ubuntu kernel: - Impact: -The upstream process for stable tree updates is quite similar -in scope to the Ubuntu SRU process, e.g., each patch has to -demonstrably fix a bug, and each patch is vetted by upstream -by originating either directly from a mainline/stable Linux tree or -a minimally backported form of that patch. The following upstream -stable patches should be included in the Ubuntu kernel: + v5.15.62 upstream stable release + from git://git.kernel.org/ -v5.15.62 upstream stable release -from git://git.kernel.org/ + io_uring: use original request task for inflight tracking + tee: add overflow check in register_shm_helper() + net_sched: cls_route: disallow handle of 0 + ksmbd: prevent out of bound read for SMB2_WRITE + ksmbd: fix heap-based overflow in set_ntacl_dacl() + btrfs: only write the sectors in the vertical stripe which has data stripes + btrfs: raid56: don't trust any cached sector in __raid56_parity_recover() + Linux 5.15.62 + UBUNTU: Upstream stable to v5.15.62 -- 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/1990554 Title: Jammy update: v5.15.62 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: In Progress Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.15.62 upstream stable release from git://git.kernel.org/ io_uring: use original request task for inflight tracking tee: add overflow check in register_shm_helper() net_sched: cls_route: disallow handle of 0 ksmbd: prevent out of bound read for SMB2_WRITE ksmbd: fix heap-based overflow in set_ntacl_dacl() btrfs: only write the sectors in the vertical stripe which has data stripes btrfs: raid56: don't trust any cached sector in __raid56_parity_recover() Linux 5.15.62 UBUNTU: Upstream stable to v5.15.62 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1990554/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help :
[Kernel-packages] [Bug 1842320] Re: Can't boot: "error: out of memory." immediately after the grub menu
@jeremyszu (os369510) Did you see #90, it seems your patch would cause boot failures on older system unable to handle this memory range. -- 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/1842320 Title: Can't boot: "error: out of memory." immediately after the grub menu Status in grub: Unknown Status in OEM Priority Project: Triaged Status in grub2-signed package in Ubuntu: Confirmed Status in initramfs-tools package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: [Impact] * In some cases, if the users’ initramfs grow bigger, then it’ll likely not be able to be loaded by grub2. * Some real cases from OEM projects: In many built-in 4k monitor laptops with nvidia drivers, the u-d-c puts the nvidia*.ko to initramfs which grows the initramfs to ~120M. Also the gfxpayload=auto will remain to use 4K resolution since it’s what EFI POST passed. In this case, the grub isn't able to load initramfs because the grub_memalign() won't be able to get suitable memory for the larger file: ``` #0 grub_memalign (align=1, size=592214020) at ../../../grub-core/kern/mm.c:376 #1 0x7dd7b074 in grub_malloc (size=592214020) at ../../../grub-core/kern/mm.c:408 #2 0x7dd7a2c8 in grub_verifiers_open (io=0x7bc02d80, type=131076) at ../../../grub-core/kern/verifiers.c:150 #3 0x7dd801d4 in grub_file_open (name=0x7bc02f00 "/boot/initrd.img-5.17.0-1011-oem", type=131076) at ../../../grub-core/kern/file.c:121 #4 0x7bcd5a30 in ?? () #5 0x7fe21247 in ?? () #6 0x7bc030c8 in ?? () #7 0x00017fe21238 in ?? () #8 0x7bcd5320 in ?? () #9 0x7fe21250 in ?? () #10 0x in ?? () ``` Based on grub_mm_dump, we can see the memory fragment (some parts seem likely be used because of 4K resolution?) and doesn’t have available contiguous memory for larger file as: ``` grub_real_malloc(...) ... if (cur->size >= n + extra) ``` Based on UEFI Specification Section 7.2[1] and UEFI driver writers’ guide 4.2.3[2], we can ask 32bits+ on AllocatePages(). As most X86_64 platforms should support 64 bits addressing, we should extend GRUB_EFI_MAX_USABLE_ADDRESS to 64 bits to get more available memory. * When users grown the initramfs, then probably will get initramfs not found which really annoyed and impact the user experience (system not able to boot). [Test Plan] * detailed instructions how to reproduce the bug: 1. Any method to grow the initramfs, such as install nvidia-driver. 2. If developers would like to reproduce, then could dd if=/dev/random of=... bs=1M count=500, something like: ``` $ cat /usr/share/initramfs-tools/hooks/zzz-touch-a-file #!/bin/sh PREREQ="" prereqs() { echo "$PREREQ" } case $1 in # get pre-requisites prereqs) prereqs exit 0 ;; esac . /usr/share/initramfs-tools/hook-functions dd if=/dev/random of=${DESTDIR}/test-500M bs=1M count=500 ``` And then update-initramfs * After applying my patches, the issue is gone. * I did also test my test grubx64.efi in: 1. X86_64 qemu with 1.1. 60M initramfs + 5.15.0-37-generic kernel 1.2. 565M initramfs + 5.17.0-1011-oem kernel 2. Amd64 HP mobile workstation with 2.1. 65M initramfs + 5.15.0-39-generic kernel 2.2. 771M initramfs + 5.17.0-1011-oem kernel All working well. [Where problems could occur] * The changes almost in i386/efi, thus the impact will be in the i386 / x86_64 EFI system. The other change is to modify the “grub-core/kern/efi/mm.c” but I use the original addressing for “arm/arm64/ia64/riscv32/riscv64”. Thus it should not impact them. * There is a “#if defined(__x86_64__)” which intent to limit the > 32bits code in i386 system and also ``` #if defined (__code_model_large__) -#define GRUB_EFI_MAX_USABLE_ADDRESS 0x +#define GRUB_EFI_MAX_USABLE_ADDRESS __UINTPTR_MAX__ +#define GRUB_EFI_MAX_ALLOCATION_ADDRESS 0x7fff #else #define GRUB_EFI_MAX_USABLE_ADDRESS 0x7fff +#define GRUB_EFI_MAX_ALLOCATION_ADDRESS 0x3fff #endif ``` If everything works as expected, then i386 should working good. If not lucky, based on “UEFI writers’ guide”[2], the i386 will get > 4GB memory region and never be able to access. [Other Info] * Upstream grub2 bug #61058 https://savannah.gnu.org/bugs/index.php?61058 * Test PPA: https://launchpad.net/~os369510/+archive/ubuntu/lp1842320 * Test grubx64.efi: https://people.canonical.com/~jeremysu/lp1842320/grubx64.efi.lp1842320 * Test source code: https://github.com/os369510/grub2/tree/lp1842320 * If you built the package, then test grubx64.efi is under “obj/monolithic/grub-efi-amd64/grubx64.efi”, in my case:
[Kernel-packages] [Bug 1990543] [NEW] package linux-nvidia-tools-common (not installed) failed to install/upgrade: prøver å skrive over «/usr/bin/acpidbg» som også finnes i pakken linux-tools-common 5
Public bug reported: I'm trying to install drivers for an older Nvidia card, the Quadro 5200. That means I can't use the newest drivers, but the 470 package should work. If it only could work, that is... ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-nvidia-tools-common (not installed) ProcVersionSignature: Ubuntu 5.17.0-1016.17-oem 5.17.15 Uname: Linux 5.17.0-1016-oem x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown Date: Thu Sep 22 16:30:05 2022 DuplicateSignature: package:linux-nvidia-tools-common:(not installed) Unpacking linux-nvidia-tools-common (5.15.0-1005.5) ... dpkg: error processing archive /tmp/apt-dpkg-install-aIXziz/23-linux-nvidia-tools-common_5.15.0-1005.5_all.deb (--unpack): prøver å skrive over «/usr/bin/acpidbg» som også finnes i pakken linux-tools-common 5.15.0-48.54 ErrorMessage: prøver å skrive over «/usr/bin/acpidbg» som også finnes i pakken linux-tools-common 5.15.0-48.54 Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 3.10.4-0ubuntu2 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.7 SourcePackage: linux-nvidia Title: package linux-nvidia-tools-common (not installed) failed to install/upgrade: prøver å skrive over «/usr/bin/acpidbg» som også finnes i pakken linux-tools-common 5.15.0-48.54 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-nvidia (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package jammy need-duplicate-check -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia in Ubuntu. https://bugs.launchpad.net/bugs/1990543 Title: package linux-nvidia-tools-common (not installed) failed to install/upgrade: prøver å skrive over «/usr/bin/acpidbg» som også finnes i pakken linux-tools-common 5.15.0-48.54 Status in linux-nvidia package in Ubuntu: New Bug description: I'm trying to install drivers for an older Nvidia card, the Quadro 5200. That means I can't use the newest drivers, but the 470 package should work. If it only could work, that is... ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-nvidia-tools-common (not installed) ProcVersionSignature: Ubuntu 5.17.0-1016.17-oem 5.17.15 Uname: Linux 5.17.0-1016-oem x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown Date: Thu Sep 22 16:30:05 2022 DuplicateSignature: package:linux-nvidia-tools-common:(not installed) Unpacking linux-nvidia-tools-common (5.15.0-1005.5) ... dpkg: error processing archive /tmp/apt-dpkg-install-aIXziz/23-linux-nvidia-tools-common_5.15.0-1005.5_all.deb (--unpack): prøver å skrive over «/usr/bin/acpidbg» som også finnes i pakken linux-tools-common 5.15.0-48.54 ErrorMessage: prøver å skrive over «/usr/bin/acpidbg» som også finnes i pakken linux-tools-common 5.15.0-48.54 Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 3.10.4-0ubuntu2 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.7 SourcePackage: linux-nvidia Title: package linux-nvidia-tools-common (not installed) failed to install/upgrade: prøver å skrive over «/usr/bin/acpidbg» som også finnes i pakken linux-tools-common 5.15.0-48.54 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia/+bug/1990543/+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
Still present in 5.15.0-50-generic 9/21/22 7:54 AM kernel 9/21/22 7:54 AM kernel UBSAN: array-index-out-of-bounds in /build/linux-lU2d47/linux-5.15.0/drivers/net/ethernet/aquantia/atlantic/aq_nic.c:1262:48 9/21/22 7:54 AM kernel index 8 is out of range for type 'aq_vec_s *[8]' 9/21/22 7:54 AM kernel CPU: 4 PID: 1930 Comm: daemon-init Tainted: G O 5.15.0-50-generic #56-Ubuntu 9/21/22 7:54 AM kernel Hardware name: To Be Filled By O.E.M. X570 Creator/X570 Creator, BIOS P3.72 05/17/2022 9/21/22 7:54 AM kernel Call Trace: 9/21/22 7:54 AM kernel 9/21/22 7:54 AM kernel show_stack+0x52/0x5c 9/21/22 7:54 AM kernel dump_stack_lvl+0x4a/0x63 9/21/22 7:54 AM kernel dump_stack+0x10/0x16 9/21/22 7:54 AM kernel ubsan_epilogue+0x9/0x49 9/21/22 7:54 AM kernel __ubsan_handle_out_of_bounds.cold+0x44/0x49 9/21/22 7:54 AM kernel ? dev_get_port_parent_id+0x18/0x160 9/21/22 7:54 AM kernel ? aq_vec_stop+0x72/0x80 [atlantic] 9/21/22 7:54 AM kernel aq_nic_stop+0x10a/0x110 [atlantic] 9/21/22 7:54 AM kernel aq_ndev_set_features+0x143/0x1a0 [atlantic] 9/21/22 7:54 AM kernel __netdev_update_features+0x184/0x820 9/21/22 7:54 AM kernel dev_disable_lro+0x34/0x150 9/21/22 7:54 AM kernel devinet_sysctl_forward+0x1fb/0x230 9/21/22 7:54 AM kernel proc_sys_call_handler+0x16a/0x2f0 9/21/22 7:54 AM kernel proc_sys_write+0x13/0x20 9/21/22 7:54 AM kernel new_sync_write+0x114/0x1a0 9/21/22 7:54 AM kernel vfs_write+0x1d5/0x270 9/21/22 7:54 AM kernel ksys_write+0x67/0xf0 9/21/22 7:54 AM kernel __x64_sys_write+0x19/0x20 9/21/22 7:54 AM kernel do_syscall_64+0x5c/0xc0 9/21/22 7:54 AM kernel ? exit_to_user_mode_prepare+0x37/0xb0 9/21/22 7:54 AM kernel ? syscall_exit_to_user_mode+0x27/0x50 9/21/22 7:54 AM kernel ? do_syscall_64+0x69/0xc0 9/21/22 7:54 AM kernel ? exit_to_user_mode_loop+0x10d/0x160 9/21/22 7:54 AM kernel entry_SYSCALL_64_after_hwframe+0x61/0xcb 9/21/22 7:54 AM kernel RIP: 0033:0x7fed8a694a6f 9/21/22 7:54 AM kernel Code: 89 54 24 18 48 89 74 24 10 89 7c 24 08 e8 19 c0 f7 ff 48 8b 54 24 18 48 8b 74 24 10 41 89 c0 8b 7c 24 08 b8 01 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 31 44 89 c7 48 89 44 24 08 e8 5c c0 f7 ff 48 9/21/22 7:54 AM kernel RSP: 002b:7fed4e7fb810 EFLAGS: 0293 ORIG_RAX: 0001 9/21/22 7:54 AM kernel RAX: ffda RBX: 0002 RCX: 7fed8a694a6f 9/21/22 7:54 AM kernel RDX: 0002 RSI: 7fed8b01c5e5 RDI: 0013 9/21/22 7:54 AM kernel RBP: 7fed8b01c5e5 R08: R09: 0001 9/21/22 7:54 AM kernel R10: R11: 0293 R12: 0013 9/21/22 7:54 AM kernel R13: 0013 R14: R15: 7fed38024ab0 9/21/22 7:54 AM kernel 9/21/22 7:54 AM kernel -- 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/1958770 Title: Aquantia GbE LAN driver causes UBSAN error during kernel boot Status in linux package in Ubuntu: Confirmed 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 Released Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Released 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:
[Kernel-packages] [Bug 1980730] Re: OVS internal port Hardware Offload implementation is missing in Jammy kernel
*** This bug is a duplicate of bug 1983498 *** https://bugs.launchpad.net/bugs/1983498 Hello Itai, We have tracked the inclusion of this feature request via bug 1983498. The patches have been released to jammy-updates with jammy/linux: 5.15.0-48.54. I'll mark this bug report as a duplicate to make it easier to track it using a single bug. Thank you. ** This bug has been marked a duplicate of bug 1983498 Jammy: Add OVS Internal Port HW Offload to mlx5 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/1980730 Title: OVS internal port Hardware Offload implementation is missing in Jammy kernel Status in linux package in Ubuntu: Incomplete Status in linux source package in Jammy: In Progress Bug description: Platform: OpenStack Yoga, Ubuntu 22.04 Jammy, Kernel 5.15.0-37-generic When deploying Charmed Openstack deployment with HW Offload over Jammy series, some of the traffic workloads (mainly those related to Floating IP and NAT) will not be properly offloaded. In order to solve it, "OVS internal port offload" feature was introduced and pushed to upstream kernel. These are the main base patches for the feature we call "OVS internal port offload": b16eb3c81fe27978afdb2c111908d4d627a88d99 net/mlx5: Support internal port as decap route device 5e9942721749fc96b9df4b0545474153316c0571 net/mlx5e: Term table handling of internal port rules 166f431ec6beaf472bc2e116a202a127b64779e4 net/mlx5e: Add indirect tc offload of ovs internal port 100ad4e2d75837c9b42f49b3814b4b42ec9ebe46 net/mlx5e: Offload internal port as encap route device 27484f7170edabbda7b53650cd24d38295cffe60 net/mlx5e: Offload tc rules that redirect to ovs internal port dbac71f22954276633e525f958994f84a7bd303f net/mlx5e: Accept action skbedit in the tc actions list 4f4edcc2b84fecec66748ecbb90a84b981ecdaae net/mlx5: E-Switch, Add ovs internal port mapping to metadata support 189ce08ebf876df2b51f625877731055475352df net/mlx5e: Use generic name for the forwarding dev pointer 28e7606fa8f106cdc0355e0548396c037443e063 net/mlx5e: Refactor rx handler of represetor device Please make sure to take as well all patches the came later on top of those base patches To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1980730/+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 1897972] Re: "snapd" is not installed
This appears to be a proxy setting for snapd. You can try clearing the proxy setting for snapd or setting it to your proxy server. In my scenario, this bug popped up during an upgrade to ubuntu server v22.04 lts. Snapd was installed to the latest version, but it reported during the upgrade: Connection to Snap Store failed Your system does not have a connection to the Snap Store. For the best upgrade experience make sure that your system can connect to api.snapcraft.io. Do you still want to continue with the upgrade? I got around this by setting the proxy server for snap. Put your proxy url in between the quotes below of the following commands: sudo snap set system proxy.http="" sudo snap set system proxy.https="" I tried doing a 'snap refresh snapd' after setting the proxy, but it still indicated snapd wasn't installed (when it was). I believe this is the actual bug. Regardless of it saying it wasn't installed, after setting the proxy server for snapd (to my proxy settings), I was able to perform the upgrade and it connected to api.snapcraft.io without any problems. I would assume if you have no proxy and clear the proxy settings (just by entering in snap commands as they are with no proxy) it would work for you as well. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.4 in Ubuntu. https://bugs.launchpad.net/bugs/1897972 Title: "snapd" is not installed Status in linux-signed-hwe-5.4 package in Ubuntu: Confirmed Bug description: Connection to Snap Store failed Your system does not have a connection to the Snap Store. For the best upgrade experience make sure that your system can connect to api.snapcraft.io. Do you still want to continue with the upgrade? I got the error snap snapd is not installed and tried to apt get snapd, which said it was already installed. So I ignored, typed systemctl restart snapd and tried again but upgrade still failed. $ snap refresh snapd snap "snapd" is not installed $ sudo apt install snapd Reading package lists... Done Building dependency tree Reading state information... Done snapd is already the newest version (2.46.1+18.04). The following packages were automatically installed and are no longer required: linux-hwe-5.4-headers-5.4.0-42 linux-hwe-5.4-headers-5.4.0-45 Use 'sudo apt autoremove' to remove them. 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.4.0-48-generic 5.4.0-48.52~18.04.1 ProcVersionSignature: Ubuntu 5.4.0-48.52~18.04.1-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Sep 30 14:47:56 2020 InstallationDate: Installed on 2019-12-29 (276 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: linux-signed-hwe-5.4 UpgradeStatus: Upgraded to bionic on 2020-09-30 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.4/+bug/1897972/+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 1988721] Re: [SRU][OEM-5.17][PATCH 0/1] Fix output issue of USB-C to DP dongle on AMD
Aaron, I got a request to backport this to jammy/5.15 as well ** Changed in: hwe-next Status: New => Fix Committed ** Changed in: hwe-next Status: Fix Committed => In Progress ** Changed in: hwe-next Status: In Progress => Fix Released -- 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/1988721 Title: [SRU][OEM-5.17][PATCH 0/1] Fix output issue of USB-C to DP dongle on AMD Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Released Bug description: [Impact] There is no output of external 4k DP monitor via USB-C to DP dongle. [Fix] Isolate link training sequence, the external DP monitor will be good. [Test] Verified on hardware, external 4k monitor works fine after re-plugin and suspend. [Where problems could occur] It may break the display output on AMD GPU. This commit is from 5.18-rc1, and no issue on jammy kernel. SRU for oem-5.17 only. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1988721/+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 1988809] Re: ip/nexthop: fix default address selection for connected nexthop
Before the update: ++ root@ubuntu2004:~/linux# uname -a Linux ubuntu2004 5.4.0-124-generic #140-Ubuntu SMP Thu Aug 4 02:23:37 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux root@ubuntu2004:~/linux# tools/testing/selftests/net/fib_nexthop_nongw.sh TEST: nexthop: get route with nexthop without gw[FAIL] TEST: nexthop: ping through nexthop without gw [FAIL] With the new focal kernel: ++ root@ubuntu2004:~/linux# uname -a Linux ubuntu2004 5.4.0-128-generic #144-Ubuntu SMP Tue Sep 20 11:00:04 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux root@ubuntu2004:~/linux# tools/testing/selftests/net/fib_nexthop_nongw.sh TEST: nexthop: get route with nexthop without gw[ OK ] TEST: nexthop: ping through nexthop without gw [ OK ] With the new jammy kernel: ++ root@ubuntu2004:~/linux# uname -a Linux ubuntu2004 5.15.0-50-generic #56-Ubuntu SMP Tue Sep 20 13:23:26 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux root@ubuntu2004:~/linux# tools/testing/selftests/net/fib_nexthop_nongw.sh TEST: nexthop: get route with nexthop without gw[ OK ] TEST: nexthop: ping through nexthop without gw [ OK ] -- 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/1988809 Title: ip/nexthop: fix default address selection for connected nexthop Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Committed Status in linux source package in Jammy: Fix Committed Bug description: [Impact] Packets sent by userland apps are rejected/dropped if the source address is not specified and the corresponding route is using a connected nexthop object. This bug exists since linux v5.3 and has been fixed in v5.19 by the following upstream commits: - 747c14307214 ("ip: fix dflt addr selection for connected nexthop") https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=747c14307214 - cd72e61bad14 ("selftests/net: test nexthop without gw") https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=cd72e61bad14 - eb55dc09b5dd ("ip: fix triggering of 'icmp redirect'") https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=eb55dc09b5dd The last commit (v6.0) fixes a regression introduced by the first commit. [Test Case] A detailed test case is explained in the first commit and a self-test is added in the second commit. [Regression Potential] The patch modifies some internal routing states. It has been living in the upstream trees for 2 months and the reported regression about icmp redirects has been fixed. The risk of regression should be contained. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1988809/+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 1786013] Autopkgtest regression report (linux-meta/5.4.0.128.129)
All autopkgtests for the newly accepted linux-meta (5.4.0.128.129) for focal have finished running. The following regressions have been reported in tests triggered by the package: systemd/245.4-4ubuntu3.17 (armhf) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#linux-meta [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packing resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+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 1988809] Re: ip/nexthop: fix default address selection for connected nexthop
** 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/1988809 Title: ip/nexthop: fix default address selection for connected nexthop Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Committed Status in linux source package in Jammy: Fix Committed Bug description: [Impact] Packets sent by userland apps are rejected/dropped if the source address is not specified and the corresponding route is using a connected nexthop object. This bug exists since linux v5.3 and has been fixed in v5.19 by the following upstream commits: - 747c14307214 ("ip: fix dflt addr selection for connected nexthop") https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=747c14307214 - cd72e61bad14 ("selftests/net: test nexthop without gw") https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=cd72e61bad14 - eb55dc09b5dd ("ip: fix triggering of 'icmp redirect'") https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=eb55dc09b5dd The last commit (v6.0) fixes a regression introduced by the first commit. [Test Case] A detailed test case is explained in the first commit and a self-test is added in the second commit. [Regression Potential] The patch modifies some internal routing states. It has been living in the upstream trees for 2 months and the reported regression about icmp redirects has been fixed. The risk of regression should be contained. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1988809/+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 1990524] [NEW] [Ubuntu 22.04] zkey: KMIP plugin fails to connection to KMIP server
Public bug reported: Description: zkey: KMIP plugin fails to connection to KMIP server Symptom: When a zkey key repository is bound to the KMIP plugin, and the connection to the KMIP server is to be configired using command 'zkey kms configure --kmip-server ', it fails to connect to the specified KMIP server. Problem: When trying to establish a TSL connection to the KMIP server, the KMIP client sets up an OpenSSL SSL context with its certificate and its private key (which is a secure key) using OpenSSL function SSL_CTX_use_PrivateKey(). When running with OpenSSL 3.0, This calls the secure key provider's match function to check if the private key specified matches the public key of the certificate using EVP_PKEY_eq(). EVP_PKEY_eq() includes the private key into the selector bits for the match call, although the certificate only contains the public key part. OpenSSL commit ee22a3741e3fc27c981e7f7e9bcb8d3342b0c65a changed the OpenSSL provider's keymgmt_match() function to be not so strict with the selector bits in regards to matching different key parts. This means, that if the public key is selected to be matched, and the public key matches (together with any also selected parameters), then the private key is no longer checked, although it may also be selected to be matched. This is according to how the OpenSSL function EVP_PKEY_eq() is supposed to behave. Solution: Adapt the secure key provider's match function to behave like the match functions of the providers coming with OpenSSL. Reproduction: Configure a connection to a KMIP server on a system that comes with OpenSSL 3.0. Problem-ID:198268 Preventive:yes Upstream-ID: 6c5c5f7e558c114ddaa475e96c9ec708049aa423 Date: 2022-05-17 Author:Ingo Franzki Component: s390-tools == Comment: #1 - Ingo Franzki - 2022-05-17 07:40:03 == Upstream commit: https://github.com/ibm-s390-linux/s390-tools/commit/6c5c5f7e558c114ddaa475e96c9ec708049aa423 ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Skipper Bug Screeners (skipper-screen-team) Status: New ** Tags: architecture-s39064 bugnameltc-198269 severity-high targetmilestone-inin--- ** Tags added: architecture-s39064 bugnameltc-198269 severity-high targetmilestone-inin--- ** Changed in: ubuntu Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team) ** Package changed: 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/1990524 Title: [Ubuntu 22.04] zkey: KMIP plugin fails to connection to KMIP server Status in linux package in Ubuntu: New Bug description: Description: zkey: KMIP plugin fails to connection to KMIP server Symptom: When a zkey key repository is bound to the KMIP plugin, and the connection to the KMIP server is to be configired using command 'zkey kms configure --kmip-server ', it fails to connect to the specified KMIP server. Problem: When trying to establish a TSL connection to the KMIP server, the KMIP client sets up an OpenSSL SSL context with its certificate and its private key (which is a secure key) using OpenSSL function SSL_CTX_use_PrivateKey(). When running with OpenSSL 3.0, This calls the secure key provider's match function to check if the private key specified matches the public key of the certificate using EVP_PKEY_eq(). EVP_PKEY_eq() includes the private key into the selector bits for the match call, although the certificate only contains the public key part. OpenSSL commit ee22a3741e3fc27c981e7f7e9bcb8d3342b0c65a changed the OpenSSL provider's keymgmt_match() function to be not so strict with the selector bits in regards to matching different key parts. This means, that if the public key is selected to be matched, and the public key matches (together with any also selected parameters), then the private key is no longer checked, although it may also be selected to be matched. This is according to how the OpenSSL function EVP_PKEY_eq() is supposed to behave. Solution: Adapt the secure key provider's match function to behave like the match functions of the providers coming with OpenSSL. Reproduction: Configure a connection to a KMIP server on a system that comes with OpenSSL 3.0. Problem-ID:198268 Preventive:yes Upstream-ID: 6c5c5f7e558c114ddaa475e96c9ec708049aa423 Date: 2022-05-17 Author:Ingo Franzki Component: s390-tools == Comment: #1 - Ingo Franzki - 2022-05-17 07:40:03 == Upstream commit: https://github.com/ibm-s390-linux/s390-tools/commit/6c5c5f7e558c114ddaa475e96c9ec708049aa423 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1990524/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to :
[Kernel-packages] [Bug 1990524] [NEW] [Ubuntu 22.04] zkey: KMIP plugin fails to connection to KMIP server
You have been subscribed to a public bug: Description: zkey: KMIP plugin fails to connection to KMIP server Symptom: When a zkey key repository is bound to the KMIP plugin, and the connection to the KMIP server is to be configired using command 'zkey kms configure --kmip-server ', it fails to connect to the specified KMIP server. Problem: When trying to establish a TSL connection to the KMIP server, the KMIP client sets up an OpenSSL SSL context with its certificate and its private key (which is a secure key) using OpenSSL function SSL_CTX_use_PrivateKey(). When running with OpenSSL 3.0, This calls the secure key provider's match function to check if the private key specified matches the public key of the certificate using EVP_PKEY_eq(). EVP_PKEY_eq() includes the private key into the selector bits for the match call, although the certificate only contains the public key part. OpenSSL commit ee22a3741e3fc27c981e7f7e9bcb8d3342b0c65a changed the OpenSSL provider's keymgmt_match() function to be not so strict with the selector bits in regards to matching different key parts. This means, that if the public key is selected to be matched, and the public key matches (together with any also selected parameters), then the private key is no longer checked, although it may also be selected to be matched. This is according to how the OpenSSL function EVP_PKEY_eq() is supposed to behave. Solution: Adapt the secure key provider's match function to behave like the match functions of the providers coming with OpenSSL. Reproduction: Configure a connection to a KMIP server on a system that comes with OpenSSL 3.0. Problem-ID:198268 Preventive:yes Upstream-ID: 6c5c5f7e558c114ddaa475e96c9ec708049aa423 Date: 2022-05-17 Author:Ingo Franzki Component: s390-tools == Comment: #1 - Ingo Franzki - 2022-05-17 07:40:03 == Upstream commit: https://github.com/ibm-s390-linux/s390-tools/commit/6c5c5f7e558c114ddaa475e96c9ec708049aa423 ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Skipper Bug Screeners (skipper-screen-team) Status: New ** Tags: architecture-s39064 bugnameltc-198269 severity-high targetmilestone-inin--- -- [Ubuntu 22.04] zkey: KMIP plugin fails to connection to KMIP server https://bugs.launchpad.net/bugs/1990524 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1990212] Re: [ADL-P-IOTG graphics cause Ubuntu 22.10 hang
quanxian, so can you confirm if you build the distro kernel plus the fix from #11 that it works for you too? -- 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/1990212 Title: [ADL-P-IOTG graphics cause Ubuntu 22.10 hang Status in intel: New Status in linux package in Ubuntu: Incomplete Bug description: [Bug Description] ADL-P platform from IOTG will have hang issue. when blacklist i915, the system will back to well. but with official 5.19 kernel which support ADL-P (IOTG), we don't find this issue. Canonical please check what addition patches has been included your i915 driver that cause system hang. [HW/SW Information] Target Kernel: 5.19 Target Release: 22.10 Alder Lake -P from Intel IOTG [Business Justification] Function enabling To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1990212/+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 1978986] Re: [SRU][J/OEM-5.17][PATCH 0/1] Fix oled brightness set above frame-average luminance
** Changed in: linux (Ubuntu) Status: Confirmed => Fix Released -- 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/1978986 Title: [SRU][J/OEM-5.17][PATCH 0/1] Fix oled brightness set above frame- average luminance Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Released Bug description: [Impact] The brightness is not changed obviously during 200 to 255 on AMD or 400 to 512 on Intel.. [Fix] Read HDR meta to detect the max and min luminance. max_cll defines the content light luminance for individual pixel. max_fall defines frame-average level luminance. Use max_fall value instead of max_cll as a limit for brightness control. [Test] Verified on AMD Cezanne, Barcelo, Rembrandt and Intel ADL, also on LCD panel and OLED panel. The brightness is changed more obivously on OLED panel, and no affect on LCD panel. [Where problems could occur] Low risk, It may cause the max brightness can't be set. All 3 patches are in drm-misc tree. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1978986/+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 1990520] Re: [Ubuntu 22.04] zkey: Fix re-enciphering of EP11 identity key of KMIP plugin
** Package changed: linux (Ubuntu) => s390-tools (Ubuntu) ** Also affects: ubuntu-z-systems Importance: Undecided Status: New ** Also affects: s390-tools-signed (Ubuntu) Importance: Undecided Status: New ** Changed in: ubuntu-z-systems Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team) ** Changed in: ubuntu-z-systems Importance: Undecided => High -- 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/1990520 Title: [Ubuntu 22.04] zkey: Fix re-enciphering of EP11 identity key of KMIP plugin Status in Ubuntu on IBM z Systems: New Status in s390-tools package in Ubuntu: New Status in s390-tools-signed package in Ubuntu: New Bug description: Description: zkey: Fix re-enciphering of EP11 identity key of KMIP plugin Symptom: When re-enciphering the identity key and/or wrapping key of the zkey KMIP plugin via 'zkey kms reencipher', the operation completes without an error, but the secure keys are left un-reenciphered. A subsequent connection attempt with the KMIP server will fail because the identity key is no longer valid. Problem: The re-enciphered secure key is not copied back into the key token buffer. Also, the the public key part, i.e. the MACed SubjectPublicKeyInfo (SPKI) structure must also be re-enciphered (i.e. re-MACed), since the MAC is calculated with the EP11 master key. Solution: Copy the re-enciphered secure key back into the key token buffer, and also re-encipher the public key part. Reproduction: Perform a master key change on the EP11 APQNs used with the KMIP plugin. Problem-ID:197605 Upstream-ID: 4e2ebe0370d9fb036b7554d5ac5df4418dbe0397 Preventive:yes Date: 2022-04-08 Author:Ingo Franzki Component: s390-tools == Comment: #1 - Ingo Franzki - 2022-04-08 09:57:45 == Upstream commit: https://github.com/ibm-s390-linux/s390-tools/commit/4e2ebe0370d9fb036b7554d5ac5df4418dbe0397 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1990520/+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) (fixed in 5.17.7 and later)
The screen flicker also happened to me after updating to 22.04. I think the cause for the error is actually Memtest86+. When I tried to do the fix by adding parameters to /etc/default/grub and update I got the following. :~$ uname -a Linux alwayssk 5.15.0-50-generic #56-Ubuntu SMP Tue Sep 20 13:23:26 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux :~$ sudo update-grub Sourcing file `/etc/default/grub' Sourcing file `/etc/default/grub.d/init-select.cfg' Generating grub configuration file ... Found linux image: /boot/vmlinuz-5.15.0-50-generic Found initrd image: /boot/initrd.img-5.15.0-50-generic Found linux image: /boot/vmlinuz-5.15.0-48-generic Found initrd image: /boot/initrd.img-5.15.0-48-generic Memtest86+ needs a 16-bit boot, that is not available on EFI, exiting Warning: os-prober will be executed to detect other bootable partitions. Its output will be used to detect bootable binaries on them and create new boot entries. Adding boot menu entry for UEFI Firmware Settings ... done -- 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) (fixed in 5.17.7 and later) Status in linux package in Ubuntu: Fix Released 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 1990520] [NEW] [Ubuntu 22.04] zkey: Fix re-enciphering of EP11 identity key of KMIP plugin
Public bug reported: Description: zkey: Fix re-enciphering of EP11 identity key of KMIP plugin Symptom: When re-enciphering the identity key and/or wrapping key of the zkey KMIP plugin via 'zkey kms reencipher', the operation completes without an error, but the secure keys are left un-reenciphered. A subsequent connection attempt with the KMIP server will fail because the identity key is no longer valid. Problem: The re-enciphered secure key is not copied back into the key token buffer. Also, the the public key part, i.e. the MACed SubjectPublicKeyInfo (SPKI) structure must also be re-enciphered (i.e. re-MACed), since the MAC is calculated with the EP11 master key. Solution: Copy the re-enciphered secure key back into the key token buffer, and also re-encipher the public key part. Reproduction: Perform a master key change on the EP11 APQNs used with the KMIP plugin. Problem-ID:197605 Upstream-ID: 4e2ebe0370d9fb036b7554d5ac5df4418dbe0397 Preventive:yes Date: 2022-04-08 Author:Ingo Franzki Component: s390-tools == Comment: #1 - Ingo Franzki - 2022-04-08 09:57:45 == Upstream commit: https://github.com/ibm-s390-linux/s390-tools/commit/4e2ebe0370d9fb036b7554d5ac5df4418dbe0397 ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Skipper Bug Screeners (skipper-screen-team) Status: New ** Tags: architecture-s39064 bugnameltc-197607 severity-high targetmilestone-inin--- ** Tags added: architecture-s39064 bugnameltc-197607 severity-high targetmilestone-inin--- ** Changed in: ubuntu Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team) ** Package changed: 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/1990520 Title: [Ubuntu 22.04] zkey: Fix re-enciphering of EP11 identity key of KMIP plugin Status in linux package in Ubuntu: New Bug description: Description: zkey: Fix re-enciphering of EP11 identity key of KMIP plugin Symptom: When re-enciphering the identity key and/or wrapping key of the zkey KMIP plugin via 'zkey kms reencipher', the operation completes without an error, but the secure keys are left un-reenciphered. A subsequent connection attempt with the KMIP server will fail because the identity key is no longer valid. Problem: The re-enciphered secure key is not copied back into the key token buffer. Also, the the public key part, i.e. the MACed SubjectPublicKeyInfo (SPKI) structure must also be re-enciphered (i.e. re-MACed), since the MAC is calculated with the EP11 master key. Solution: Copy the re-enciphered secure key back into the key token buffer, and also re-encipher the public key part. Reproduction: Perform a master key change on the EP11 APQNs used with the KMIP plugin. Problem-ID:197605 Upstream-ID: 4e2ebe0370d9fb036b7554d5ac5df4418dbe0397 Preventive:yes Date: 2022-04-08 Author:Ingo Franzki Component: s390-tools == Comment: #1 - Ingo Franzki - 2022-04-08 09:57:45 == Upstream commit: https://github.com/ibm-s390-linux/s390-tools/commit/4e2ebe0370d9fb036b7554d5ac5df4418dbe0397 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1990520/+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 1990520] [NEW] [Ubuntu 22.04] zkey: Fix re-enciphering of EP11 identity key of KMIP plugin
You have been subscribed to a public bug: Description: zkey: Fix re-enciphering of EP11 identity key of KMIP plugin Symptom: When re-enciphering the identity key and/or wrapping key of the zkey KMIP plugin via 'zkey kms reencipher', the operation completes without an error, but the secure keys are left un-reenciphered. A subsequent connection attempt with the KMIP server will fail because the identity key is no longer valid. Problem: The re-enciphered secure key is not copied back into the key token buffer. Also, the the public key part, i.e. the MACed SubjectPublicKeyInfo (SPKI) structure must also be re-enciphered (i.e. re-MACed), since the MAC is calculated with the EP11 master key. Solution: Copy the re-enciphered secure key back into the key token buffer, and also re-encipher the public key part. Reproduction: Perform a master key change on the EP11 APQNs used with the KMIP plugin. Problem-ID:197605 Upstream-ID: 4e2ebe0370d9fb036b7554d5ac5df4418dbe0397 Preventive:yes Date: 2022-04-08 Author:Ingo Franzki Component: s390-tools == Comment: #1 - Ingo Franzki - 2022-04-08 09:57:45 == Upstream commit: https://github.com/ibm-s390-linux/s390-tools/commit/4e2ebe0370d9fb036b7554d5ac5df4418dbe0397 ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Skipper Bug Screeners (skipper-screen-team) Status: New ** Tags: architecture-s39064 bugnameltc-197607 severity-high targetmilestone-inin--- -- [Ubuntu 22.04] zkey: Fix re-enciphering of EP11 identity key of KMIP plugin https://bugs.launchpad.net/bugs/1990520 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1987287] Re: [UBUNTU 20.04] mlx5 driver crashes on accessing device attributes during recovery
This bug is awaiting verification that the linux/5.4.0-128.144 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! -- 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/1987287 Title: [UBUNTU 20.04] mlx5 driver crashes on accessing device attributes during recovery Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: Fix Committed Bug description: SRU Justification: -- [Impact] * If the mlx5 driver is reloading while the recovery flow is happening, and if it receives new commands before the command interface is up again, this can lead to null pointer that tries to access non- initialized command structures. * So it's required to avoid processing commands before the command interface is up again. * This is accomplished by a new cmdif state that helps to avoid processing commands while cmdif is not ready. [Fix] * backport of f7936ddd35d8 f7936ddd35d8b849daf0372770c7c9dbe7910fca "net/mlx5: Avoid processing commands before cmdif is ready" [Test Plan] * An Ubuntu Server for s390x 18.04 or 20.04 LPAR or z/VM installation is needed that has Mellanox cards (RoCE Express 2.1) assigned, configured and enabled and that runs a 5.4 kernel (on bionic hwe-5.4). * Now trigger a recovery (guess that can be done at the Support Element) and reload the driver at the same time. * Make sure the module/driver mlx5 is loaded and in use (otherwise it can't be removed/unloaded). * Now remove/unload the module with: sudo modprobe -r mlx5 and (re-)load it again with: sudo modprobe mlx5 * Due to the lack of RoCE Express 2.1 hardware, IBM needs to do the verification. [Where problems could occur] * In case there is an issue with 'cmdif' it might not have the correct interface state, which: - either might lead to the fact that commands are not properly blocked and the situation is similar like before - or the commands may get always blocked, which render the hardware useless - or might block in wrong situation, which will cause unexpected issues and broken behavior. * Since the patch got upstream accepted with v5.7-rc7 it's not new to the kernel, was already part of groovy (and above) and is therefor already in use by newer Ubuntu releases. [Other Info] * Since the patch is upstream since v5.7-rc7, it's already included in jammy and kinetic. * Since the upstream patch incl. the line: Fixes: e126ba97dba9 ("mlx5: Add driver for Mellanox Connect-IB adapters") it looks to me that it was forgotten to mark the patch for upstream stable updates. * Such SRUs for focal's 5.4 will automatically land in bionic's hwe-5.4, too. But since this was especially requested for bionic's hwe-5.4, I wanted to mention this here. __ We recently got a bug report for systems running Ubuntu 20.04 that were crashing with backtraces pointing at the mlx5 driver's handling of mlx5_ethtool_get_link_ksettings() when this is called through the sysfs (going through ethtool might have different checks). I managed to find a reliable way to reproduce the issue that I believe isn't tied to IBM Z at all. The procedure to reproduce is as follows. I created a script to read the sysfs attributes for the link's speed and duplex mode in a loop: #!/usr/bin/env bash if [ $# -lt 1 ]; then echo "Usage: $0 " exit 1 fi while true; do cat /sys/class/net/$1/duplex > /dev/null cat /sys/class/net/$1/speed > /dev/null done Executed with: # ./script.sh enP10p0s0 I ran this in one bash session and then in another one I triggered a PCI reset with the follwoing command where one needs to replace with the PCI address of the NIC: echo 1 > /sys/bus/pci/devices//reset Then first I got a lot of the following messages: mlx5_core 0010:00:00.0 enP16p0s0: mlx5e_ethtool_get_link_ksettings: query port ptys failed: -5 And then as the mlx5 driver's recovery kicks in the oops as below: [ 659.103947] mlx5_core 0010:00:00.0: wait vital counter value 0x7b399f after 1 iterations [ 659.103947] mlx5_core 0010:00:00.0: mlx5_pci_resume was called [ 659.103966] mlx5_core
[Kernel-packages] [Bug 1988809] Re: ip/nexthop: fix default address selection for connected nexthop
This bug is awaiting verification that the linux/5.4.0-128.144 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! -- 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/1988809 Title: ip/nexthop: fix default address selection for connected nexthop Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Committed Status in linux source package in Jammy: Fix Committed Bug description: [Impact] Packets sent by userland apps are rejected/dropped if the source address is not specified and the corresponding route is using a connected nexthop object. This bug exists since linux v5.3 and has been fixed in v5.19 by the following upstream commits: - 747c14307214 ("ip: fix dflt addr selection for connected nexthop") https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=747c14307214 - cd72e61bad14 ("selftests/net: test nexthop without gw") https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=cd72e61bad14 - eb55dc09b5dd ("ip: fix triggering of 'icmp redirect'") https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=eb55dc09b5dd The last commit (v6.0) fixes a regression introduced by the first commit. [Test Case] A detailed test case is explained in the first commit and a self-test is added in the second commit. [Regression Potential] The patch modifies some internal routing states. It has been living in the upstream trees for 2 months and the reported regression about icmp redirects has been fixed. The risk of regression should be contained. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1988809/+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 1990124] Re: icmp_redirect.sh in ubuntu_kernel_selftests failed on Jammy 5.15.0-49.55
This bug is awaiting verification that the linux/5.4.0-128.144 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! -- 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/1990124 Title: icmp_redirect.sh in ubuntu_kernel_selftests failed on Jammy 5.15.0-49.55 Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Committed Status in linux source package in Jammy: Fix Committed Bug description: icmp_redirect.sh in ubuntu_kernel_selftests failed on Jammy 5.15.0-49.55 This looks like a potential regression as there is no change to the test script. Manual test show this issue does not exist on: * J-5.15.0-47 * J-5.15.0-48 Test log: ### Legacy routing ### TEST: IPv4: redirect exception [FAIL] TEST: IPv6: redirect exception [ OK ] TEST: IPv4: redirect exception plus mtu [FAIL] TEST: IPv6: redirect exception plus mtu [ OK ] TEST: IPv4: routing reset [ OK ] TEST: IPv6: routing reset [ OK ] TEST: IPv4: mtu exception [ OK ] TEST: IPv6: mtu exception [ OK ] TEST: IPv4: mtu exception plus redirect [FAIL] TEST: IPv6: mtu exception plus redirect [ OK ] ### Legacy routing with VRF ### TEST: IPv4: redirect exception [FAIL] TEST: IPv6: redirect exception [ OK ] TEST: IPv4: redirect exception plus mtu [FAIL] TEST: IPv6: redirect exception plus mtu [ OK ] TEST: IPv4: routing reset [ OK ] TEST: IPv6: routing reset [ OK ] TEST: IPv4: mtu exception [ OK ] TEST: IPv6: mtu exception [ OK ] TEST: IPv4: mtu exception plus redirect [FAIL] TEST: IPv6: mtu exception plus redirect [ OK ] ### Routing with nexthop objects ### TEST: IPv4: redirect exception [FAIL] TEST: IPv6: redirect exception [ OK ] TEST: IPv4: redirect exception plus mtu [FAIL] TEST: IPv6: redirect exception plus mtu [ OK ] TEST: IPv4: routing reset [ OK ] TEST: IPv6: routing reset [ OK ] TEST: IPv4: mtu exception [ OK ] TEST: IPv6: mtu exception [ OK ] TEST: IPv4: mtu exception plus redirect [FAIL] TEST: IPv6: mtu exception plus redirect [ OK ] ### Routing with nexthop objects and VRF ### TEST: IPv4: redirect exception [FAIL] TEST: IPv6: redirect exception [ OK ] TEST: IPv4: redirect exception plus mtu [FAIL] TEST: IPv6: redirect exception plus mtu [ OK ] TEST: IPv4: routing reset [ OK ] TEST: IPv6: routing reset [ OK ] TEST: IPv4: mtu exception [ OK ] TEST: IPv6: mtu exception
[Kernel-packages] [Bug 1989172] Re: mlxbf-pmc: error when reading unprogrammed events
** Also affects: linux-bluefield (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux-bluefield (Ubuntu) Status: New => Invalid ** Changed in: linux-bluefield (Ubuntu Focal) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/1989172 Title: mlxbf-pmc: error when reading unprogrammed events Status in linux-bluefield package in Ubuntu: Invalid Status in linux-bluefield source package in Focal: Fix Committed Bug description: SRU Justification: [Impact] When the counters are not programmed to monitor any events, reading the "event" file results in the following error: cat: /sys/class/hwmon/hwmon0/smmu0/event0: Invalid argument This is misleading and instead needs to indicate that the counter is currently not enabled. [Fix] * First, skip the check for whether the counter is enabled when reading the event info. If the counter is not enabled, it should return 0, which is the default value when coming out of reset. * 0 is not a valid event in most blocks as per the respective event lists, so add a "Disable" event to all the event lists. [Test Case] Without the fix, reading any "event" file right after reset when the counters are not programmed should result in the following error: cat: /sys/class/hwmon/hwmon0/smmu0/event0: Invalid argumen With the fix, it should instead print: 0x0: DISABLE [Regression Potential] Can be considered minimal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1989172/+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 1989495] Re: mlxbf_gige: need to clear MDIO gateway lock after read
** Changed in: linux-bluefield (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/1989495 Title: mlxbf_gige: need to clear MDIO gateway lock after read Status in linux-bluefield package in Ubuntu: Invalid Status in linux-bluefield source package in Focal: Fix Committed Bug description: SRU Justification: [Impact] The BlueField-2 GIGE logic accesses the MDIO device via reads/writes to a gateway (GW) register. The MDIO GW lock is set after read. Make sure to always clear to indicate that the GW register is not being used. If the lock is mistakenly interpreted as ACTIVE, then subsequent MDIO accesses will be blocked and PHY device will be inaccessible. [Fix] For each MDIO read and write transaction, the last step should be to clear the MDIO GW lock. [Test Case] Boot the BlueField-2 platform Bring up the "oob_net0" interface via DHCP or static IP Ping and file transfer over "oob_net0" should work properly Bounce the "oob_net0" interface a few times and repeat tests [Regression Potential] * Low risk for causing a regression, tested well in our lab. [Other] * None To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1989495/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1965927] Re: [Ubuntu 22.04] mpt3sas: Request to include latest bug fix patches
Hi, I have tested the mpt3sas driver embodied in the above provided test kernel. Results are positive and no issue is found during the testing. Below are the main test cases that got executed during the testing and results of these test cases are positive, 1. All drives attached to the controller are Enumerated in OS 2. IO stress for 5Hrs 3. Created a filesystem and done some IO transitions 4. Controller reset and TMs and while IOs are running 5. driver load and unload 6. Reboot loop 7. Verified that the diag trigger settings are persistent across the reboots. Thanks, Sreekanth -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1965927 Title: [Ubuntu 22.04] mpt3sas: Request to include latest bug fix patches Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: In Progress Bug description: Request to include below mpt3sas driver bug fix patches in Ubuntu 22.04 kernel. These patches got accepted by the upstream and please find the corresponding commit IDs as below, 5db207d66d mpt3sas: Fix incorrect 4gb boundary check ca23ac823c mpt3sas: Remove scsi_dma_map errors messages 9211faa39a scsi: mpt3sas: Update persistent trigger pages from sysfs interface Below is the summary of each of the above bug fix commits, 1. mpt3sas: Fix incorrect 4gb boundary check: Without this patch, driver was checking whether any of it's pool crosses the 4gb boundary or not using the pool's virtual address instead of using it's dma address. So some time driver may false positively assume that the pool as crossed the 4gb boundary region (as it observes that pool's virtual address is crossing the 4gb boundary) even though it is really not. 2. mpt3sas: Remove scsi_dma_map errors messages: When driver set the DMA mask to 32bit then we observe that the SWIOTLB bounce buffers are getting exhausted quickly. For most of the IOs driver observe that scsi_dma_map() API returned with failure status and hence driver was printing below error message. Since this error message is getting printed per IO and if user issues heavy IOs then we observe that kernel overwhelmed with this error message. Also we will observe the kernel panic when the serial console is enabled. So to limit this issue, we removed this error message though this patch. "scsi_dma_map failed: request for 1310720 bytes!" 3. mpt3sas: Update persistent trigger pages from sysfs interface: When user set's any diag buffer trigger conditions then driver has to save these trigger conditions in the controller Firmware's NVRAM region. So that when system reboots then driver can get these trigger conditions from Firmware's NVRAM region and set these trigger conditions automatically. so that user no need to set these conditions again. Without this patch driver was not not saving these user provided trigger conditions in the Firmware's NVRAM region. Please let me if I have missed to add any data. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1965927/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1988488] Re: Screen freeze at the moment of login on VirtualBox: [drm:vmw_msg_ioctl [vmwgfx]] *ERROR* Failed to open channel.
Another try to send the journalctl file, using Email. On Tue, 2022-09-20 at 10:30 +, Daniel van Vugt wrote: > Please use one of these commands to provide a full log. > > If you have not rebooted since the freeze: > > journalctl -b0 > journal.txt > > Or after you have rebooted: > > journalctl -b-1 > prevboot.txt > > and attach the resulting text file here. > > > ** Changed in: linux (Ubuntu) > Status: Confirmed => Incomplete > ** Attachment added: "previous-boot.txt" https://bugs.launchpad.net/bugs/1988488/+attachment/5618037/+files/previous-boot.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/1988488 Title: Screen freeze at the moment of login on VirtualBox: [drm:vmw_msg_ioctl [vmwgfx]] *ERROR* Failed to open channel. Status in linux package in Ubuntu: Incomplete Bug description: The problem started to appear 2 weeks ago after one of my daily updates. It also happens after I re-install the system from a freshly downloaded ISO file. The system freezes at the moment, it starts the gnome display manager. I file the bug-report after a partial upgrade just before I will reboot the system. If needed I can reboot in recovery mode, since the gnome display manager is not started in that case. I tried the continue button without effect and also "apt upgrade" and "apt dist-upgrade" do have the same effect I run the VM from the Host-OpenZFS file system, so I can restore to before the update. Recently I use a Virtualbox snapshot to restore the system to before the update/upgrade. If you need log files, let me know. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: systemd 251.4-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.23.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Sep 1 19:42:04 2022 InstallationDate: Installed on 2022-05-28 (96 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220526) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet 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/6p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: innotek GmbH VirtualBox ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=9eaf84b0-b69b-4760-80b5-310e3a258bda ro quiet splash RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:sku: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1988488/+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 1988488] Re: Screen freeze at the moment of login on VirtualBox: [drm:vmw_msg_ioctl [vmwgfx]] *ERROR* Failed to open channel.
Again the program crashes, if I add the text file. So I attach the last lines: sep 21 16:08:33 VM-Ubuntu-2210 systemd[1082]: snap.snapd-desktop-integration.snapd-desktop-integration.service: Scheduled restart job, restart counter is at 4. sep 21 16:08:33 VM-Ubuntu-2210 systemd[1082]: Starting Virtual filesystem service - disk device monitor... sep 21 16:08:33 VM-Ubuntu-2210 systemd[1082]: Stopped Service for snap application snapd-desktop-integration.snapd-desktop-integration. sep 21 16:08:33 VM-Ubuntu-2210 systemd[1082]: Started Service for snap application snapd-desktop-integration.snapd-desktop-integration. sep 21 16:08:33 VM-Ubuntu-2210 snapd-desktop-integration.snapd-desktop-integration[1262]: Sorry, home directories outside of /home are not currently supported. sep 21 16:08:33 VM-Ubuntu-2210 snapd-desktop-integration.snapd-desktop-integration[1262]: See https://forum.snapcraft.io/t/11209 for details. sep 21 16:08:33 VM-Ubuntu-2210 systemd[1082]: snap.snapd-desktop-integration.snapd-desktop-integration.service: Main process exited, code=exited, status=1/FAILURE sep 21 16:08:33 VM-Ubuntu-2210 systemd[1082]: snap.snapd-desktop-integration.snapd-desktop-integration.service: Failed with result 'exit-code'. sep 21 16:08:33 VM-Ubuntu-2210 dbus-daemon[1102]: [session uid=128 pid=1102] Successfully activated service 'org.gtk.vfs.UDisks2VolumeMonitor' sep 21 16:08:33 VM-Ubuntu-2210 systemd[1082]: Started Virtual filesystem service - disk device monitor. sep 21 16:08:33 VM-Ubuntu-2210 dbus-daemon[1102]: [session uid=128 pid=1102] Activating via systemd: service name='org.gtk.vfs.GoaVolumeMonitor' unit='gvfs-goa-volume-monitor.service' requested by ':1.15' (uid=128 pid=1203 comm="/usr/libexec/tracker-miner-fs-3" label="unconfined") sep 21 16:08:33 VM-Ubuntu-2210 systemd[1082]: Starting Virtual filesystem service - GNOME Online Accounts monitor... sep 21 16:08:33 VM-Ubuntu-2210 dbus-daemon[1102]: [session uid=128 pid=1102] Activating service name='org.gnome.OnlineAccounts' requested by ':1.17' (uid=128 pid=1288 comm="/usr/libexec/gvfs-goa-volume-monitor" label="unconfined") sep 21 16:08:34 VM-Ubuntu-2210 /usr/libexec/gdm-wayland-session[1115]: dbus-daemon[1115]: [session uid=128 pid=1115] Activating service name='org.a11y.Bus' requested by ':1.4' (uid=128 pid=1163 comm="/usr/bin/gnome-shell" label="unconfined") sep 21 16:08:34 VM-Ubuntu-2210 /usr/libexec/gdm-wayland-session[1115]: dbus-daemon[1115]: [session uid=128 pid=1115] Successfully activated service 'org.a11y.Bus' sep 21 16:08:34 VM-Ubuntu-2210 goa-daemon[1292]: goa-daemon version 3.45.2 starting sep 21 16:08:34 VM-Ubuntu-2210 dbus-daemon[1102]: [session uid=128 pid=1102] Activating service name='org.gnome.Identity' requested by ':1.18' (uid=128 pid=1292 comm="/usr/libexec/goa-daemon" label="unconfined") sep 21 16:08:34 VM-Ubuntu-2210 dbus-daemon[1102]: [session uid=128 pid=1102] Successfully activated service 'org.gnome.OnlineAccounts' sep 21 16:08:34 VM-Ubuntu-2210 dbus-daemon[1102]: [session uid=128 pid=1102] Successfully activated service 'org.gnome.Identity' sep 21 16:08:34 VM-Ubuntu-2210 dbus-daemon[1102]: [session uid=128 pid=1102] Successfully activated service 'org.gtk.vfs.GoaVolumeMonitor' sep 21 16:08:34 VM-Ubuntu-2210 systemd[1082]: Started Virtual filesystem service - GNOME Online Accounts monitor. sep 21 16:08:34 VM-Ubuntu-2210 systemd[1082]: snap.snapd-desktop-integration.snapd-desktop-integration.service: Scheduled restart job, restart counter is at 5. sep 21 16:08:34 VM-Ubuntu-2210 systemd[1082]: Stopped Service for snap application snapd-desktop-integration.snapd-desktop-integration. sep 21 16:08:34 VM-Ubuntu-2210 systemd[1082]: snap.snapd-desktop-integration.snapd-desktop-integration.service: Start request repeated too quickly. sep 21 16:08:34 VM-Ubuntu-2210 systemd[1082]: snap.snapd-desktop-integration.snapd-desktop-integration.service: Failed with result 'exit-code'. sep 21 16:08:34 VM-Ubuntu-2210 systemd[1082]: Failed to start Service for snap application snapd-desktop-integration.snapd-desktop-integration. sep 21 16:08:34 VM-Ubuntu-2210 dbus-daemon[1102]: [session uid=128 pid=1102] Activating via systemd: service name='org.gtk.vfs.MTPVolumeMonitor' unit='gvfs-mtp-volume-monitor.service' requested by ':1.15' (uid=128 pid=1203 comm="/usr/libexec/tracker-miner-fs-3" label="unconfined") sep 21 16:08:34 VM-Ubuntu-2210 systemd[1082]: Starting Virtual filesystem service - Media Transfer Protocol monitor... sep 21 16:08:34 VM-Ubuntu-2210 dbus-daemon[1102]: [session uid=128 pid=1102] Successfully activated service 'org.gtk.vfs.MTPVolumeMonitor' sep 21 16:08:34 VM-Ubuntu-2210 systemd[1082]: Started Virtual filesystem service - Media Transfer Protocol monitor. sep 21 16:08:34 VM-Ubuntu-2210 dbus-daemon[1102]: [session uid=128 pid=1102] Activating via systemd: service name='org.gtk.vfs.GPhoto2VolumeMonitor' unit='gvfs-gphoto2-volume-monitor.service' requested by ':1.15' (uid=128 pid=1203
[Kernel-packages] [Bug 1990212] Re: [ADL-P-IOTG graphics cause Ubuntu 22.10 hang
when ADL-P from IOTG was available for us, we use 5.19-rc3 public kernel with ubuntu 22.04. it works well. that is all our verification on ADL-P (IOTG). Totally we ever did testing with public kernel version, 5.19-rc3, 5.19, 5.19.7, 6.0-rc6(latest kernel at that time), don't find hang issue. this time, we testing Canonical Ubuntu 22.10 cycle, we come across this issue. otherwise, we will get it earlier and contact upstream about this kind of critical issue. -- 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/1990212 Title: [ADL-P-IOTG graphics cause Ubuntu 22.10 hang Status in intel: New Status in linux package in Ubuntu: Incomplete Bug description: [Bug Description] ADL-P platform from IOTG will have hang issue. when blacklist i915, the system will back to well. but with official 5.19 kernel which support ADL-P (IOTG), we don't find this issue. Canonical please check what addition patches has been included your i915 driver that cause system hang. [HW/SW Information] Target Kernel: 5.19 Target Release: 22.10 Alder Lake -P from Intel IOTG [Business Justification] Function enabling To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1990212/+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 1990212] Re: [ADL-P-IOTG graphics cause Ubuntu 22.10 hang
yes, 5.19.7, 6.0-rc6, we used. also we use 5.19 public kernel, all works well. only Canonical default kernel has the hang issue. -- 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/1990212 Title: [ADL-P-IOTG graphics cause Ubuntu 22.10 hang Status in intel: New Status in linux package in Ubuntu: Incomplete Bug description: [Bug Description] ADL-P platform from IOTG will have hang issue. when blacklist i915, the system will back to well. but with official 5.19 kernel which support ADL-P (IOTG), we don't find this issue. Canonical please check what addition patches has been included your i915 driver that cause system hang. [HW/SW Information] Target Kernel: 5.19 Target Release: 22.10 Alder Lake -P from Intel IOTG [Business Justification] Function enabling To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1990212/+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 1988461] Re: intel_pmc_core not load on Raptor Lake
** Changed in: linux-oem-6.0 (Ubuntu Jammy) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1988461 Title: intel_pmc_core not load on Raptor Lake Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux source package in Jammy: Won't Fix Status in linux-oem-5.17 source package in Jammy: Fix Committed Status in linux-oem-6.0 source package in Jammy: Fix Committed Status in linux source package in Kinetic: In Progress Status in linux-oem-5.17 source package in Kinetic: Invalid Status in linux-oem-6.0 source package in Kinetic: Invalid Bug description: [Summary] intel_pmc_core not load on Raptor Lake [Reproduce Steps] 1. Boot into Ubuntu desktop 2. Check if /sys/kernel/debug/pmc_core folder exist [Results] Expected: folder /sys/kernel/debug/pmc_core folder been created Actual: /sys/kernel/debug/pmc_core not exist To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1988461/+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 1990212] Re: [ADL-P-IOTG graphics cause Ubuntu 22.10 hang
Applying the patch mentioned in #11 on kinetic kernel would solve the issue. -- 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/1990212 Title: [ADL-P-IOTG graphics cause Ubuntu 22.10 hang Status in intel: New Status in linux package in Ubuntu: Incomplete Bug description: [Bug Description] ADL-P platform from IOTG will have hang issue. when blacklist i915, the system will back to well. but with official 5.19 kernel which support ADL-P (IOTG), we don't find this issue. Canonical please check what addition patches has been included your i915 driver that cause system hang. [HW/SW Information] Target Kernel: 5.19 Target Release: 22.10 Alder Lake -P from Intel IOTG [Business Justification] Function enabling To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1990212/+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 1826228] Re: api3a+ hang when reading /sys/devices/platform/soc/driver_override
** Changed in: linux-raspi2 (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1826228 Title: api3a+ hang when reading /sys/devices/platform/soc/driver_override Status in linux-raspi2 package in Ubuntu: Invalid Bug description: I discovered this when running some tests on a core16 image with various rpi3 devices. Rpi3b, b+, cm3, rpi2, etc... don't have this problem, only rpi3a+. Kernel version: Linux localhost 4.4.0-1107-raspi2 #115-Ubuntu SMP Wed Apr 10 18:06:42 UTC 2019 armv7l armv7l armv7l GNU/Linux To reproduce, simply 'cat /sys/devices/platform/soc/driver_override' The process just hangs and cannot be killed. On other rpi devices, I just get this output immediately: (null) There was nothing in dmesg or syslog when it happened, no kernel crash, and I can still ssh into the system. The process that ran that command just silently hangs and can't be killed even with sudo kill -9. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1826228/+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 1990212] Re: [ADL-P-IOTG graphics cause Ubuntu 22.10 hang
jhlee found out that the kinetic kernel is missing this commit: commit 458ec0c8f35963626ccd51c3d50b752de5f1b9d4 Author: Łukasz Bartosik Date: Tue Feb 1 16:33:54 2022 +0100 drm/i915: fix null pointer dereference but it's not in 5.19.7 either, 5.19.8 and up has it. So are you absolutely sure that it was 5.19.7 you used and found to be good? -- 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/1990212 Title: [ADL-P-IOTG graphics cause Ubuntu 22.10 hang Status in intel: New Status in linux package in Ubuntu: Incomplete Bug description: [Bug Description] ADL-P platform from IOTG will have hang issue. when blacklist i915, the system will back to well. but with official 5.19 kernel which support ADL-P (IOTG), we don't find this issue. Canonical please check what addition patches has been included your i915 driver that cause system hang. [HW/SW Information] Target Kernel: 5.19 Target Release: 22.10 Alder Lake -P from Intel IOTG [Business Justification] Function enabling To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1990212/+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 1982070] Re: scsi: hisi_sas: Increase debugfs_dump_index after dump is completed
Jammy kernel 5.15.0-50.56 works for me. Thanks. ** Tags added: 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/1982070 Title: scsi: hisi_sas: Increase debugfs_dump_index after dump is completed Status in kunpeng920: Fix Committed Status in kunpeng920 ubuntu-20.04-hwe series: Fix Committed Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: Fix Committed Status in linux source package in Kinetic: Fix Released Bug description: [Impact] Trigger dump on hisi_sas in debugfs will cause kernel oops. [Test Plan] 1) modprobe hisi_sas_main with "debugfs_enable=1" 2) echo 1 | sudo tee /sys/kernel/debug/hisi_sas/\:74\:02.0/trigger_dump 3) dmesg | grep Oops [Regression Risk] Only touch code in hisi_sas. Need to run full test on hisi_sas. Other drivers/platforms are not affected. [Bug Description] When the hisi_sas_main driver is loaded, the DFX function is enabled. When the dump is triggered or the SAS controller is reset, call_trace is displayed. In addition, the hisi_sas_v3_hw driver is occupied and cannot be uninstalled. [Steps to Reproduce] 1)dmesg -C 2)dmesg 3)lsblk 4)lsscsi -p 5)lsmod | grep hisi_sas_v3 6)rmmod hisi_sas_v3_hw 7)rmmod hisi_sas_main 8)modprobe hisi_sas_main debugfs_enable=1 9)modprobe hisi_sas_v3_hw 10)cd /sys/kernel/debug/hisi_sas/\:74\:02.0/ 11)ll 12)echo 1 > trigger_dump 13)echo 1 > trigger_dump 14)dmesg [Actual Results] [ 1005.899976] sas: broadcast received: 0 [ 1005.87] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.901775] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.901777] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.901793] sas: broadcast received: 0 [ 1005.901820] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.903563] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.903570] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.903586] sas: broadcast received: 0 [ 1005.903611] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.905387] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.905388] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.905404] sas: broadcast received: 0 [ 1005.905429] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.907161] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.907168] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.907182] sas: broadcast received: 0 [ 1005.907207] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.908944] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.908946] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.909025] sas: broadcast received: 0 [ 1005.909062] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.910912] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.910919] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.910947] sas: broadcast received: 0 [ 1005.910985] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.912843] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.912847] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.912877] sas: broadcast received: 0 [ 1005.912911] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.915191] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.915198] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.915221] sas: broadcast received: 0 [ 1005.915259] sas: REVALIDATING DOMAIN on port 0, pid:1170 [ 1005.917957] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.917965] sas: done REVALIDATING DOMAIN on port 0, pid:1170, res 0x0 [ 1005.920337] sd 4:0:11:0: [sdl] Attached SCSI disk [ 1005.921692] sd 4:0:4:0: [sde] Attached SCSI disk [ 1008.107610] hisi_sas_v3_hw :b4:02.0: 16 hw queues [ 1008.112712] scsi host6: hisi_sas_v3_hw [ 1010.428061] hisi_sas_v3_hw :b4:04.0: 16 hw queues [ 1010.433120] scsi host7: hisi_sas_v3_hw root@ubuntu:/sys/kernel/debug/hisi_sas/:74:02.0# [Expected Results] Recurrence Logs: [ 360.441633] SET = 0, FnV = 0 [ 360.444689] EA = 0, S1PTW = 0 [ 360.447863] Data abort info: [ 360.450783] ISV = 0, ISS = 0x0044 [ 360.454663] CM = 0, WnR = 1 [ 360.457673] user pgtable: 4k pages, 48-bit VAs, pgdp=00211b7ae000 [ 360.464140] [] pgd=, p4d= [ 360.470969] Internal error: Oops: 9644 [#2] SMP [ 360.475844] Modules linked in: hisi_sas_v3_hw hisi_sas_main nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua ipmi_ssif joydev input_leds efi_pstore arm_spe_pmu hisi_hpre ecdh_generic libcurve25519_generic hns_roce_hw_v2 ecc hisi_zip uio_pdrv_genirq uio hisi_sec2 hisi_qm uacce authenc acpi_ipmi ipmi_si ipmi_devintf ipmi_msghandler hisi_trng_v2 cppc_cpufreq sch_fq_codel ip_tables x_tables autofs4