[Kernel-packages] [Bug 1845818] Re: arm64: system does not boot after installing linux-generic-hwe-18.04-edge/bionic-proposed
*** This bug is a duplicate of bug 1845820 *** https://bugs.launchpad.net/bugs/1845820 adding console log ** Attachment added: "console_log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1845818/+attachment/5295197/+files/gigabyte_bionic_hwe-edge-proposed_console_log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1845818 Title: arm64: system does not boot after installing linux-generic- hwe-18.04-edge/bionic-proposed Status in linux package in Ubuntu: Incomplete Bug description: Description: system does not boot after installing linux-generic-hwe-18.04-edge/bionic-proposed System: Board Model:gbt-mt30 Board name: MT30-GS1-00 System name:R120-T33-00 SKU: CN8890-2000BG2601-AAP-Y-G 1) Ubuntu 18.04.3 LTS (GNU/Linux 5.0.0-23-generic aarch64) Description: Ubuntu 18.04.3 LTS Release: 18.04 2) ((enable -proposed archive)) linux-generic-hwe-18.04-edge: Installed: 5.0.0.23.79 Candidate: 5.3.0.12.83 Version table: 5.3.0.12.83 500 500 http://ports.ubuntu.com/ubuntu-ports bionic-proposed/main arm64 Packages *** 5.0.0.23.79 500 500 http://ports.ubuntu.com/ubuntu-ports bionic-updates/main arm64 Packages 100 /var/lib/dpkg/status 5.0.0.20.76 500 500 http://ports.ubuntu.com/ubuntu-ports bionic-security/main arm64 Packages 3) a. install linux-generic-hwe-18.04-edge/bionic-proposed 5.3.0.12.83 arm64 [upgradable from: 5.0.0.23.79] b. reboot c. ssh into the system 4) a. installed linux-generic-hwe-18.04-edge/bionic-proposed b. system does not boot ``` linux-generic-hwe-18.04-edge/bionic-proposed 5.3.0.12.83 arm64 [upgradable from: 5.0.0.23.79] Complete Generic Linux kernel and headers ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1845818/+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 1959532] Re: [22.04 FEAT] Transparent PCI device recovery
built kernel available and tested: https://people.canonical.com/~patriciasd/kernel-lp1959532/ ``` ubuntu@s1lp13:~$ uname -a Linux s1lp13 5.15.0-23-generic #23 SMP Wed Mar 16 00:21:04 UTC 2022 s390x s390x s390x GNU/Linux ``` -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1959532 Title: [22.04 FEAT] Transparent PCI device recovery Status in Ubuntu on IBM z Systems: New Status in linux package in Ubuntu: New Bug description: A Linux on Z admin can make use of PCI-based devices in case of errors without the need to perform manual recovery. Details: Use cooperative recovery strategies that allow drivers to recover from error scenarios without complete tear-down + re-init. See approach documented for Linux on Power in Linux/Documentation/PCI/pci-error-recovery.rst. Business value: Improved reliability, reduced down-times. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1959532/+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 1959532] Re: [22.04 FEAT] Transparent PCI device recovery
kernel with the patches: https://launchpad.net/~fheimes/+archive/ubuntu/lp1959532 -- 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/1959532 Title: [22.04 FEAT] Transparent PCI device recovery Status in Ubuntu on IBM z Systems: New Status in linux package in Ubuntu: New Bug description: A Linux on Z admin can make use of PCI-based devices in case of errors without the need to perform manual recovery. Details: Use cooperative recovery strategies that allow drivers to recover from error scenarios without complete tear-down + re-init. See approach documented for Linux on Power in Linux/Documentation/PCI/pci-error-recovery.rst. Business value: Improved reliability, reduced down-times. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1959532/+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 1893897] Re: [Regression] Do not initiate shutdown for EPOW_SHUTDOWN_ON_UPS event
** Description changed: - == Comment: #0 - VASANT HEGDE - 2020-09-02 01:00:25 == - --Problem Description--- - Do not initiate shutdown for EPOW_SHUTDOWN_ON_UPS event. Instead wait for predefined time before initiating shtudown. - - Contact Information = Vasant hegde - Date: Thu Aug 20 11:48:44 2020 +0530 + [Impact] - powerpc/pseries: Do not initiate shutdown when system is running on UPS - + * With commit 79872e35469b "powerpc/pseries: All events of + EPOW_SYSTEM_SHUTDOWN must initiate shutdown" it was introduced that all + EPOW_SYSTEM_SHUTDOWN events cause immediate shutdowns. - Note that I have requested this fix for upstream v4.4 stable tree. This - will hit stable tree soon. + * But on LPARs there is a user space tool (rtas_errd) that monitor for + EPOW_SHUTDOWN_ON_UPS events. - This is impacting all kernel after v4.0. This is critical fix. Hence - I'd like to request to backport to Ubuntu 16.04 LTS release. + * Once rtas_errd gets an event it initiates a shutdown after predefined + time. + * Therefore immediate shutdowns must not be triggered if the system is + running on UPS (means for EPOW_SHUTDOWN_ON_UPS events). - -Vasant + [Fix] + + * 90a9b102eddf6a3f987d15f4454e26a2532c1c98 90a9b102eddf + "powerpc/pseries: Do not initiate shutdown when system is running on + UPS" + + [Test Case] + + * Setup a Power system on (D)LPAR and run it on UPS with Ubuntu 16.04 or + higher (kernel 4.x is needed). + + * Verify that the user space tool (rtas_errd) is active and running. + + * Define a time for a potential shutdown in case an EPOW_SHUTDOWN_ON_UPS + event occurs. + + * Trigger an EPOW_SHUTDOWN_ON_UPS event. + + * Verify if the system got shutdown immediately - or after the pre- + defined time. + + [Regression Potential] + + * The regression risk is very low, because of the very limited + modification in a case statement for EPOW_SHUTDOWN_ON_UPS events. + + * What may happen is that the system doesn't power off anymore if + running on UPS due to the EPOW_SHUTDOWN_ON_UPS case changes - especially + if there is a potential problem with rtas_errd that should monitor for + these events and should initiate the delayed shutdown. + + * Other than that I cannot see much potential harm. + + [Other] + + * The patch got upstream accepted in v5.9-rc2 and already landed in + groovy's kernel 'Ubuntu-5.8.0-18.19', based on the v5.8.4 upstream + stable release ticket LP 1893048. -- 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/1893897 Title: [Regression] Do not initiate shutdown for EPOW_SHUTDOWN_ON_UPS event Status in The Ubuntu-power-systems project: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: New Status in linux source package in Bionic: New Status in linux source package in Focal: New Status in linux source package in Groovy: Fix Released Bug description: SRU Justification: [Impact] * With commit 79872e35469b "powerpc/pseries: All events of EPOW_SYSTEM_SHUTDOWN must initiate shutdown" it was introduced that all EPOW_SYSTEM_SHUTDOWN events cause immediate shutdowns. * But on LPARs there is a user space tool (rtas_errd) that monitor for EPOW_SHUTDOWN_ON_UPS events. * Once rtas_errd gets an event it initiates a shutdown after predefined time. * Therefore immediate shutdowns must not be triggered if the system is running on UPS (means for EPOW_SHUTDOWN_ON_UPS events). [Fix] * 90a9b102eddf6a3f987d15f4454e26a2532c1c98 90a9b102eddf "powerpc/pseries: Do not initiate shutdown when system is running on UPS" [Test Case] * Setup a Power system on (D)LPAR and run it on UPS with Ubuntu 16.04 or higher (kernel 4.x is needed). * Verify that the user space tool (rtas_errd) is active and running. * Define a time for a potential shutdown in case an EPOW_SHUTDOWN_ON_UPS event occurs. * Trigger an EPOW_SHUTDOWN_ON_UPS event. * Verify if the system got shutdown immediately - or after the pre- defined time. [Regression Potential] * The regression risk is very low, because of the very limited modification in a case statement for EPOW_SHUTDOWN_ON_UPS events. * What may happen is that the system doesn't power off anymore if running on UPS due to the EPOW_SHUTDOWN_ON_UPS case changes - especially if there is a potential problem with rtas_errd that should monitor for these events and should initiate the delayed shutdown. * Other than that I cannot see much potential harm. [Other] * The patch got upstream accepted in v5.9-rc2 and already landed in groovy's kernel 'Ubuntu-5.8.0-18.19', based on the v5.8.4 upstream stable release ticket LP 1893048. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1893897/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to
[Kernel-packages] [Bug 1892546] Re: Novalink (mkvterm command failure)
Ok. I see the patch got upstream accepted (commit `63ffcbdad738e3d1c857027789a2273df3337624`). We believe this need to be SRUed to Groovy, Focal, Bionic and Xenial. Do you agree? -- 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/1892546 Title: Novalink (mkvterm command failure) Status in The Ubuntu-power-systems project: Triaged Status in linux package in Ubuntu: New Status in linux source package in Xenial: New Status in linux source package in Bionic: New Status in linux source package in Focal: New Status in linux source package in Groovy: New Bug description: -- Problem Description -- drmgr command is failing while trying to open console for IBMi. Log snap shot: Please make sure you have specified a valid locale (check your NLSPATH and LANG environment variables. Your application will use english as the default. 2 07/15/20 16:01:25.393.531 UTC DEBUG pvmutil[12687.70366696995648]: (common/util/HmclDrmgrHelper.cpp:1036) Command /usr/sbin/pvmdrmgr drmgr -c slot -s 'U9080.MHE.218BA37-V1-C8' -r -w 3 returned 255. Additional messages: /usr/sbin/pvmdrmgr drmgr -c slot -s 'U9080.MHE.218BA37-V1-C8' -r -w 3 Validating I/O DLPAR capability...yes. failed to open /sys/bus/pci/slots/U9080.MHE.218BA37-V1-C8/power: No such file or directory failed to disable hotplug children Isolation failed for 3008 with -9001 Valid outstanding translations exist. ---Steps to Reproduce--- Create a VM from PowerVC on a Novalink managed host. Unmanage and manage the VM, this problem gets reproduced == I've tested a proposed fix and it does fix both the -9001 isolation errors after DLPAR remove and vterm state is still open, as well as the /dev/hcvsX index changing after a DLPAR remove/add. I will get that patch sent out to the upstream mailing list for merging. Patch submitted upstream: https://lore.kernel.org/linuxppc- dev/20200820234643.70412-1-tyr...@linux.ibm.com/T/#u To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1892546/+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 1892546] Re: Novalink (mkvterm command failure)
** Description changed: - -- Problem Description -- - drmgr command is failing while trying to open console for IBMi. + SRU Justification: - Log snap shot: - Please make sure you have specified a valid locale (check your NLSPATH and LANG environment variables. Your application will use english as the default. 2 - 07/15/20 16:01:25.393.531 UTC DEBUG pvmutil[12687.70366696995648]: (common/util/HmclDrmgrHelper.cpp:1036) Command /usr/sbin/pvmdrmgr drmgr -c slot -s 'U9080.MHE.218BA37-V1-C8' -r -w 3 returned 255. Additional messages: /usr/sbin/pvmdrmgr drmgr -c slot -s 'U9080.MHE.218BA37-V1-C8' -r -w 3 - Validating I/O DLPAR capability...yes. - failed to open /sys/bus/pci/slots/U9080.MHE.218BA37-V1-C8/power: No such file or directory - failed to disable hotplug children - Isolation failed for 3008 with -9001 - Valid outstanding translations exist. + [Impact] + * drmgr command is failing while trying to open console for IBMi on PowerVM LPAR - ---Steps to Reproduce--- - Create a VM from PowerVC on a Novalink managed host. Unmanage and manage the VM, this problem gets reproduced - - == - I've tested a proposed fix and it does fix both the -9001 isolation errors after DLPAR remove and vterm state is still open, as well as the /dev/hcvsX index changing after a DLPAR remove/add. I will get that patch sent out to the upstream mailing list for merging. + [Fix] + * 63ffcbdad738 "tty: hvcs: Don't NULL tty->driver_data until hvcs_cleanup()" - Patch submitted upstream: + [Test Case] + * Create a VM from PowerVC on a Novalink managed host. + * Unmanage and manage the VM, this problem gets reproduced. + * grep the logs for "drmgr" - https://lore.kernel.org/linuxppc- - dev/20200820234643.70412-1-tyr...@linux.ibm.com/T/#u + + [Regression Potential] + The regression can be considered as very low, since: + * limited to the IBM Hypervisor Virtual Console Server. + * patched kernel where shared and successfully tested by IBM. + * the worse case, if the cleanup is broken a new opened connection might break. + + [Other] + * The patch got upstream accepted. -- 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/1892546 Title: Novalink (mkvterm command failure) Status in The Ubuntu-power-systems project: Triaged Status in linux package in Ubuntu: New Status in linux source package in Xenial: New Status in linux source package in Bionic: New Status in linux source package in Focal: New Status in linux source package in Groovy: New Bug description: SRU Justification: [Impact] * drmgr command is failing while trying to open console for IBMi on PowerVM LPAR [Fix] * 63ffcbdad738 "tty: hvcs: Don't NULL tty->driver_data until hvcs_cleanup()" [Test Case] * Create a VM from PowerVC on a Novalink managed host. * Unmanage and manage the VM, this problem gets reproduced. * grep the logs for "drmgr" [Regression Potential] The regression can be considered as very low, since: * limited to the IBM Hypervisor Virtual Console Server. * patched kernel where shared and successfully tested by IBM. * the worse case, if the cleanup is broken a new opened connection might break. [Other] * The patch got upstream accepted. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1892546/+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 1893897] Re: [Regression] Do not initiate shutdown for EPOW_SHUTDOWN_ON_UPS event
built and tested kernel versions available on: https://people.canonical.com/~patriciasd/kernel-lp1893897/ -- 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/1893897 Title: [Regression] Do not initiate shutdown for EPOW_SHUTDOWN_ON_UPS event Status in The Ubuntu-power-systems project: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: New Status in linux source package in Bionic: New Status in linux source package in Focal: New Status in linux source package in Groovy: Fix Released Bug description: SRU Justification: [Impact] * With commit 79872e35469b "powerpc/pseries: All events of EPOW_SYSTEM_SHUTDOWN must initiate shutdown" it was introduced that all EPOW_SYSTEM_SHUTDOWN events cause immediate shutdowns. * But on LPARs there is a user space tool (rtas_errd) that monitor for EPOW_SHUTDOWN_ON_UPS events. * Once rtas_errd gets an event it initiates a shutdown after predefined time. * Therefore immediate shutdowns must not be triggered if the system is running on UPS (means for EPOW_SHUTDOWN_ON_UPS events). [Fix] * 90a9b102eddf6a3f987d15f4454e26a2532c1c98 90a9b102eddf "powerpc/pseries: Do not initiate shutdown when system is running on UPS" [Test Case] * Setup a Power system on (D)LPAR and run it on UPS with Ubuntu 16.04 or higher (kernel 4.x is needed). * Verify that the user space tool (rtas_errd) is active and running. * Define a time for a potential shutdown in case an EPOW_SHUTDOWN_ON_UPS event occurs. * Trigger an EPOW_SHUTDOWN_ON_UPS event. * Verify if the system got shutdown immediately - or after the pre- defined time. [Regression Potential] * The regression risk is very low, because of the very limited modification in a case statement for EPOW_SHUTDOWN_ON_UPS events. * What may happen is that the system doesn't power off anymore if running on UPS due to the EPOW_SHUTDOWN_ON_UPS case changes - especially if there is a potential problem with rtas_errd that should monitor for these events and should initiate the delayed shutdown. * Other than that I cannot see much potential harm. [Other] * The patch got upstream accepted in v5.9-rc2 and already landed in groovy's kernel 'Ubuntu-5.8.0-18.19', based on the v5.8.4 upstream stable release ticket LP 1893048. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1893897/+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 1893897] Re: [Regression] Do not initiate shutdown for EPOW_SHUTDOWN_ON_UPS event
hi Vasant, according to: - https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895031 - https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895328 - https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1893115 "powerpc/pseries: Do not initiate shutdown when system is running on UPS" has landed on proposed kernels. Please, test the kernel in -proposed (Xenial, Bionic and Focal) and update this bug with the results. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thanks! -- 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/1893897 Title: [Regression] Do not initiate shutdown for EPOW_SHUTDOWN_ON_UPS event Status in The Ubuntu-power-systems project: Fix Committed Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Status in linux source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Groovy: Fix Released Bug description: SRU Justification: [Impact] * With commit 79872e35469b "powerpc/pseries: All events of EPOW_SYSTEM_SHUTDOWN must initiate shutdown" it was introduced that all EPOW_SYSTEM_SHUTDOWN events cause immediate shutdowns. * But on LPARs there is a user space tool (rtas_errd) that monitor for EPOW_SHUTDOWN_ON_UPS events. * Once rtas_errd gets an event it initiates a shutdown after predefined time. * Therefore immediate shutdowns must not be triggered if the system is running on UPS (means for EPOW_SHUTDOWN_ON_UPS events). [Fix] * 90a9b102eddf6a3f987d15f4454e26a2532c1c98 90a9b102eddf "powerpc/pseries: Do not initiate shutdown when system is running on UPS" [Test Case] * Setup a Power system on (D)LPAR and run it on UPS with Ubuntu 16.04 or higher (kernel 4.x is needed). * Verify that the user space tool (rtas_errd) is active and running. * Define a time for a potential shutdown in case an EPOW_SHUTDOWN_ON_UPS event occurs. * Trigger an EPOW_SHUTDOWN_ON_UPS event. * Verify if the system got shutdown immediately - or after the pre- defined time. [Regression Potential] * The regression risk is very low, because of the very limited modification in a case statement for EPOW_SHUTDOWN_ON_UPS events. * What may happen is that the system doesn't power off anymore if running on UPS due to the EPOW_SHUTDOWN_ON_UPS case changes - especially if there is a potential problem with rtas_errd that should monitor for these events and should initiate the delayed shutdown. * Other than that I cannot see much potential harm. [Other] * The patch got upstream accepted in v5.9-rc2 and already landed in groovy's kernel 'Ubuntu-5.8.0-18.19', based on the v5.8.4 upstream stable release ticket LP 1893048. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1893897/+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 1892546] Re: Novalink (mkvterm command failure)
Thierry, thanks. Did you check it on Bionic ? (comment #15) -- 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/1892546 Title: Novalink (mkvterm command failure) Status in The Ubuntu-power-systems project: Fix Committed Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: Fix Committed Status in linux source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Groovy: In Progress Bug description: SRU Justification: [Impact] * drmgr command is failing while trying to open console for IBMi on PowerVM LPAR [Fix] * 63ffcbdad738 "tty: hvcs: Don't NULL tty->driver_data until hvcs_cleanup()" [Test Case] * Create a VM from PowerVC on a Novalink managed host. * Unmanage and manage the VM, this problem gets reproduced. * grep the logs for "drmgr" [Regression Potential] The regression can be considered as very low, since: * limited to the IBM Hypervisor Virtual Console Server. * patched kernel where shared and successfully tested by IBM. * the worse case, if the cleanup is broken a new opened connection might break. [Other] * The patch got upstream accepted. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1892546/+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 1903288] Re: [24.04] Power guest secure boot with static keys: kernel portion
** Summary changed: - Power guest secure boot with static keys: kernel portion + [24.04] Power guest secure boot with static keys: kernel portion -- 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/1903288 Title: [24.04] Power guest secure boot with static keys: kernel portion Status in The Ubuntu-power-systems project: Incomplete Status in linux package in Ubuntu: Expired Bug description: == Comment: #2 - Daniel John Axtens - 2020-11-05 20:15:10 == This is the kernel side of changes needed for LPAR/guest secure boot. Because Ubuntu keeps its kernels so wonderfully up to date, I don't think there are any extra patches you need to pick up. (I'll double- check against the 21.04 tree once my git pulls finish!) However, we potentially need some configuration changes to make sure kexec-ing into a crashdump kernel still works. Because Lockdown requires that kexec kernels are signed by a key trusted by IMA, the public key for used for signing the kdump kernel needs to be in the IMA keyring or the platform keyring. For host secure boot (and in the UEFI case), it's loaded into the platform keyring. But in the case of guest secure boot with static keys, it's not loaded into the platform keyring so it needs to be loaded into the IMA keyring. This is easy enough to do. Firstly, load the Secure Boot CA into the .primary_trusted_keys keyring via the CONFIG_SYSTEM_TRUSTED_KEYS property. We assume the key used to sign the kernel is signed by this CA. Then, enable IMA_LOAD_X509, which allows certificates signed by a key on the .primary_trusted_keys keyring to be loaded into the IMA keyring. Then set IMA_X509_PATH to provide a path to the signing key on installed file system. (It may also be possible to do this step in userspace, so long as the CA is trusted by the kernel.) Then that key will be loaded into the .ima keyring at boot and be used to appraise the kexec kernel for crashdumps. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1903288/+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 2029261] Re: [UBUNTU 23.04] vlan interface lost after rebooting the operating system
** Also affects: ubuntu-z-systems 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/2029261 Title: [UBUNTU 23.04] vlan interface lost after rebooting the operating system Status in Ubuntu on IBM z Systems: New Status in linux package in Ubuntu: New Bug description: ---Problem Description--- [ubuntu 23.04] vlan interface lost after reboot of operating system Contact Information = mayi...@cn.ibm.com ---uname output--- Linux a257ubut02 6.2.0-25-generic #25-Ubuntu SMP Fri Jun 16 16:15:36 UTC 2023 s390x s390x s390x GNU/Linux Machine Type = 3932 - LA2 (LinuxONE 4) ---Steps to Reproduce--- Hi, In the test, I found the vlan interface will lost after I reboot the operating system, when the system boot up done, log in the system, restart the systemd-networkd service, the vlan interface can show up again. test environment: Linux distros: ubut 22.04 and 23.04, I used the ubut23.04 in the attached log HW platform: LinuxONE 4 on DPM mode network: set vNic using an OSA adapter as the backend adapter in trunk mode, I tried the adapter in access mode (assign the IP addr to enc device directly), no this issue. I'll attach the systemd-networkd log (systemd-networkd-restart- network.log), here are some timestamps I did: > > Jul 17 04:15:10 -- reboot the operating system After the system boot up down, login to the system, the vlan interface disappeared in the 'ip a' command > Jul 17 04:25:02 -- restart the systemd-networkd service by 'sudo systemctl restart systemd-networkd.service' command After restart service, the vlan interface appearred in the 'ip a' list, and the IP address assigned to the vlan is usable. >> I opened the log and found some logs with issue point while IPLing, it shows the 'Lost carrier' in enc1000 (enc1000 is the physical device of the vlan interface), but I think there is no hardware issue in the lab, we are using the adapters for testing other distros like rhel, suse, and old ubut versions, like 20.04, all are Ok. >>> Jul 17 04:15:51 a257ubut02 systemd-networkd[1066]: enc1000: Link UP Jul 17 04:15:51 a257ubut02 systemd-networkd[1066]: enc1000: Gained carrier Jul 17 04:15:51 a257ubut02 systemd-networkd[1066]: enc1000: Link DOWN Jul 17 04:15:51 a257ubut02 systemd-networkd[1066]: enc1000: Lost carrier Jul 17 04:15:51 a257ubut02 systemd-networkd[1066]: enc1000: Could not create stacked netdev: No such device Jul 17 04:15:51 a257ubut02 systemd-networkd[1066]: enc1000: Failed Jul 17 04:15:51 a257ubut02 systemd-networkd[1066]: enc1000: Link UP Jul 17 04:15:51 a257ubut02 systemd-networkd[1066]: enc1000: Gained carrier Jul 17 04:15:52 a257ubut02 systemd-networkd[1066]: enc1000: Gained IPv6LL >>> Could you please help to take a look, thanks~ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2029261/+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 1902694] Re: Ubuntu 20.10- Undetected Data corruption in MPI workloads that use VSX for reductions on POWER9 DD2.1 systems
Hi Waiki, thanks for raising this bug.
Please, could you share a test scenario for the verification of these patches -
how it can be tested? This is needed for every kernel SRU. Thanks in advance.
--
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/1902694
Title:
Ubuntu 20.10- Undetected Data corruption in MPI workloads that use VSX
for reductions on POWER9 DD2.1 systems
Status in The Ubuntu-power-systems project:
New
Status in linux package in Ubuntu:
New
Bug description:
== Comment: #0 - Waiki Wright - 2020-11-02 17:00:07
==
---Problem Description---
A data integrity issue was observed with the Ubuntu 20.04 - 5.4.0-52
and 20.10 - 5.8.0-26 kernel on Power 9. The root cause is found in
the compiling of p9_hmi_special_emu(). When doing a VMX store (in
__get_user_atomic_128_aligned()) to a buffer (vbuf), the buffer is not
128 bit aligned.
The fixes of this bug are accepted upstream:
1.
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=fixes&id=1da4a0272c5469169f78cd76cf175ff984f52f06
("powerpc: Fix undetected data corruption with P9N DD2.1 VSX CI load
emulation")
2.
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=fixes&id=d1781f23704707d350b8c9006e2bdf5394bf91b2
("selftests/powerpc: Make alignment handler test P9N DD2.1 vector CI load
workaround")
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1902694/+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 1902694] Re: Ubuntu 20.10- Undetected Data corruption in MPI workloads that use VSX for reductions on POWER9 DD2.1 systems
** Description changed:
- == Comment: #0 - Waiki Wright - 2020-11-02 17:00:07
- ==
+ SRU Justification:
- ---Problem Description---
+ [Impact]
- A data integrity issue was observed with the Ubuntu 20.04 - 5.4.0-52 and
- 20.10 - 5.8.0-26 kernel on Power 9. The root cause is found in the
- compiling of p9_hmi_special_emu(). When doing a VMX store (in
- __get_user_atomic_128_aligned()) to a buffer (vbuf), the buffer is not
- 128 bit aligned.
+ * A data integrity issue was observed on POWER 9 (DD2.1) systems.
- The fixes of this bug are accepted upstream:
- 1.
-
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=fixes&id=1da4a0272c5469169f78cd76cf175ff984f52f06
- ("powerpc: Fix undetected data corruption with P9N DD2.1 VSX CI load
emulation")
- 2.
-
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=fixes&id=d1781f23704707d350b8c9006e2bdf5394bf91b2
- ("selftests/powerpc: Make alignment handler test P9N DD2.1 vector CI load
workaround")
+ * It affects Ubuntu 20.04 with kernel 5.4.0-52 and Ubuntu 20.10 with
+ kernel 5.8.0-26 kernel.
+
+ * The root cause is found in the compiling of p9_hmi_special_emu().
+
+ * When doing a VMX store (in __get_user_atomic_128_aligned()) to a
+ buffer (vbuf), the buffer is not 128 bit aligned.
+
+ [Fix]
+
+ * 1da4a0272c54 "powerpc: Fix undetected data corruption with P9N DD2.1
+ VSX CI load emulation"
+
+ * d1781f237047 "selftests/powerpc: Make alignment handler test P9N DD2.1
+ vector CI load workaround"
+
+ [Test Case]
+
+ * A POWER 9 (DD2.1) bare metal system is needed that has either Ubuntu
+ 20.04, 20.10 or 21.04 installed.
+
+ * It's best to test this based on a sample application and test case
+ "selftests/powerpc: Make alignment handler test P9N DD2.1 vector CI load
workaround"
+
+ [Regression Potential]
+
+ * The regression risk is relatively moderate, because:
+
+ * it only happens with special VSX (vector) instructions in use, e.g. in
+ p9_hmi_special_emu
+
+ * it happens on bare metal only and only on POWER 9 (DD2.1)
+
+ * and the changes are very overseeable (in total one effective code line
+ per patch/commit)
+
+ * Since only p9_hmi_special_emu is touched, this will break in case of
+ any regressions, but this is already broken based on this bug.
+
+ [Other]
+
+ * According to the reporter this affects Ubuntu 20.04 / 5.4.0-52 and
+ 20.10 / 5.8.0-26.
+
+ * Since the development of Hirsute is already open the SRU is requested
+ for Hirsute, too.
+
+ * Patches got upstream accepted in v5.10-rc1 and v5.10-rc2.
** Summary changed:
- Ubuntu 20.10- Undetected Data corruption in MPI workloads that use VSX for
reductions on POWER9 DD2.1 systems
+ Undetected Data corruption in MPI workloads that use VSX for reductions on
POWER9 DD2.1 systems
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1902694
Title:
Undetected Data corruption in MPI workloads that use VSX for
reductions on POWER9 DD2.1 systems
Status in The Ubuntu-power-systems project:
New
Status in linux package in Ubuntu:
New
Bug description:
SRU Justification:
[Impact]
* A data integrity issue was observed on POWER 9 (DD2.1) systems.
* It affects Ubuntu 20.04 with kernel 5.4.0-52 and Ubuntu 20.10 with
kernel 5.8.0-26 kernel.
* The root cause is found in the compiling of p9_hmi_special_emu().
* When doing a VMX store (in __get_user_atomic_128_aligned()) to a
buffer (vbuf), the buffer is not 128 bit aligned.
[Fix]
* 1da4a0272c54 "powerpc: Fix undetected data corruption with P9N DD2.1
VSX CI load emulation"
* d1781f237047 "selftests/powerpc: Make alignment handler test P9N
DD2.1 vector CI load workaround"
[Test Case]
* A POWER 9 (DD2.1) bare metal system is needed that has either Ubuntu
20.04, 20.10 or 21.04 installed.
* It's best to test this based on a sample application and test case
"selftests/powerpc: Make alignment handler test P9N DD2.1 vector CI load
workaround"
[Regression Potential]
* The regression risk is relatively moderate, because:
* it only happens with special VSX (vector) instructions in use, e.g.
in p9_hmi_special_emu
* it happens on bare metal only and only on POWER 9 (DD2.1)
* and the changes are very overseeable (in total one effective code
line per patch/commit)
* Since only p9_hmi_special_emu is touched, this will break in case of
any regressions, but this is already broken based on this bug.
[Other]
* According to the reporter this affects Ubuntu 20.04 / 5.4.0-52 and
20.10 / 5.8.0-26.
* Since the development of Hirsute is already open the SRU is
requested for Hirsute, too.
* Patches got upstream accepted in v5.10-rc1 and v5.10-rc2.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1902694/+subscriptions
--
Mailing list: https://launchpad.net/~kernel
[Kernel-packages] [Bug 1902694] Re: Undetected Data corruption in MPI workloads that use VSX for reductions on POWER9 DD2.1 systems
** Changed in: ubuntu-power-systems Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) => Patricia Domingues (patriciasd) -- 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/1902694 Title: Undetected Data corruption in MPI workloads that use VSX for reductions on POWER9 DD2.1 systems Status in The Ubuntu-power-systems project: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: In Progress Status in linux source package in Groovy: In Progress Status in linux source package in Hirsute: In Progress Bug description: SRU Justification: [Impact] * A data integrity issue was observed on POWER 9 (DD2.1) systems. * It affects Ubuntu 20.04 with kernel 5.4.0-52 and Ubuntu 20.10 with kernel 5.8.0-26 kernel. * The root cause is found in the compiling of p9_hmi_special_emu(). * When doing a VMX store (in __get_user_atomic_128_aligned()) to a buffer (vbuf), the buffer is not 128 bit aligned. [Fix] * 1da4a0272c54 "powerpc: Fix undetected data corruption with P9N DD2.1 VSX CI load emulation" * d1781f237047 "selftests/powerpc: Make alignment handler test P9N DD2.1 vector CI load workaround" [Test Case] * A POWER 9 (DD2.1) bare metal system is needed that has either Ubuntu 20.04, 20.10 or 21.04 installed. * It's best to test this based on a sample application and test case "selftests/powerpc: Make alignment handler test P9N DD2.1 vector CI load workaround" [Regression Potential] * The regression risk is relatively moderate, because: * it only happens with special VSX (vector) instructions in use, e.g. in p9_hmi_special_emu * it happens on bare metal only and only on POWER 9 (DD2.1) * and the changes are very overseeable (in total one effective code line per patch/commit) * Since only p9_hmi_special_emu is touched, this will break in case of any regressions, but this is already broken based on this bug. [Other] * According to the reporter this affects Ubuntu 20.04 / 5.4.0-52 and 20.10 / 5.8.0-26. * Since the development of Hirsute is already open the SRU is requested for Hirsute, too. * Patches got upstream accepted in v5.10-rc1 and v5.10-rc2. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1902694/+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 1902694] Re: Undetected Data corruption in MPI workloads that use VSX for reductions on POWER9 DD2.1 systems
Thanks Waiki! -- 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/1902694 Title: Undetected Data corruption in MPI workloads that use VSX for reductions on POWER9 DD2.1 systems Status in The Ubuntu-power-systems project: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: Fix Committed Status in linux source package in Groovy: Fix Committed Status in linux source package in Hirsute: In Progress Bug description: SRU Justification: [Impact] * A data integrity issue was observed on POWER 9 (DD2.1) systems. * It affects Ubuntu 20.04 with kernel 5.4.0-52 and Ubuntu 20.10 with kernel 5.8.0-26 kernel. * The root cause is found in the compiling of p9_hmi_special_emu(). * When doing a VMX store (in __get_user_atomic_128_aligned()) to a buffer (vbuf), the buffer is not 128 bit aligned. [Fix] * 1da4a0272c54 "powerpc: Fix undetected data corruption with P9N DD2.1 VSX CI load emulation" * d1781f237047 "selftests/powerpc: Make alignment handler test P9N DD2.1 vector CI load workaround" [Test Case] * A POWER 9 (DD2.1) bare metal system is needed that has either Ubuntu 20.04, 20.10 or 21.04 installed. * It's best to test this based on a sample application and test case "selftests/powerpc: Make alignment handler test P9N DD2.1 vector CI load workaround" [Regression Potential] * The regression risk is relatively moderate, because: * it only happens with special VSX (vector) instructions in use, e.g. in p9_hmi_special_emu * it happens on bare metal only and only on POWER 9 (DD2.1) * and the changes are very overseeable (in total one effective code line per patch/commit) * Since only p9_hmi_special_emu is touched, this will break in case of any regressions, but this is already broken based on this bug. [Other] * According to the reporter this affects Ubuntu 20.04 / 5.4.0-52 and 20.10 / 5.8.0-26. * Since the development of Hirsute is already open the SRU is requested for Hirsute, too. * Patches got upstream accepted in v5.10-rc1 and v5.10-rc2. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1902694/+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 1892546] Re: Novalink (mkvterm command failure)
Here the patch applied to Xenial-GA kernel: https://people.canonical.com/~patriciasd/kernel-lp1892546/kernel_custom_xenial_ga/ Added some information about the system where I have tested/installed it and how: https://people.canonical.com/~patriciasd/kernel-lp1892546/notes Let me know if you have any questions. -- 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/1892546 Title: Novalink (mkvterm command failure) Status in The Ubuntu-power-systems project: In Progress Status in linux package in Ubuntu: New Bug description: -- Problem Description -- drmgr command is failing while trying to open console for IBMi. Log snap shot: Please make sure you have specified a valid locale (check your NLSPATH and LANG environment variables. Your application will use english as the default. 2 07/15/20 16:01:25.393.531 UTC DEBUG pvmutil[12687.70366696995648]: (common/util/HmclDrmgrHelper.cpp:1036) Command /usr/sbin/pvmdrmgr drmgr -c slot -s 'U9080.MHE.218BA37-V1-C8' -r -w 3 returned 255. Additional messages: /usr/sbin/pvmdrmgr drmgr -c slot -s 'U9080.MHE.218BA37-V1-C8' -r -w 3 Validating I/O DLPAR capability...yes. failed to open /sys/bus/pci/slots/U9080.MHE.218BA37-V1-C8/power: No such file or directory failed to disable hotplug children Isolation failed for 3008 with -9001 Valid outstanding translations exist. ---Steps to Reproduce--- Create a VM from PowerVC on a Novalink managed host. Unmanage and manage the VM, this problem gets reproduced == I've tested a proposed fix and it does fix both the -9001 isolation errors after DLPAR remove and vterm state is still open, as well as the /dev/hcvsX index changing after a DLPAR remove/add. I will get that patch sent out to the upstream mailing list for merging. Patch submitted upstream: https://lore.kernel.org/linuxppc- dev/20200820234643.70412-1-tyr...@linux.ibm.com/T/#u To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1892546/+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 1904906] Re: 5.10 kernel fails to boot with secure boot disabled
** Changed in: ubuntu-power-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/1904906 Title: 5.10 kernel fails to boot with secure boot disabled Status in The Ubuntu-power-systems project: New Status in linux package in Ubuntu: New Bug description: Canonical requests to test the secure boot for the 5.10 kernel but kernel fails to boot with secure boot disabled. The 5.10 kernel can be found in: https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/bootstrap They can be installed by installing the linux-generic-wip package with this PPA enabled. As usual, they are only signed using a key specific to that PPA. This key can be retrieved from the signing tarballs for the kernels, e.g.: http://ppa.launchpad.net/canonical-kernel- team/bootstrap/ubuntu/dists/hirsute/main/signed/linux-5.10-ppc64el/5.10.0-2.3/signed.tar.gz Our tester installed the 5.10 kernel via aptitude. If booting directly from the bootmenu, it stucks at: "kexec_core: Starting new kernel" If booting recovery kernel for 5.10.0, it proceeds farther and after kexec_core, it failed at: " [0.029830] LSM: Security Framework initializing [0.029916] Yama: b " Two attempts with a different scenario; running with 5.8 kernel and boot via commandline for 5.10: kexec -l /boot/vmlinux-5.10.0-0-generic --initrd=/boot/initrd.img-5.10.0-0-generic --append="root=UUID=49d000cb-dba2-4d70-809e-38f2b31d0f09 ro quiet splash" kexec -e Both attempts also failed while rebooting, once with the same error as the error from booting with bootmenu; the other failure occurred a lot earlier. Wondering what new CONFIGs and/or features for the 5.10 kernel? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1904906/+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 1927076] Re: IPv6 TCP in reuseport_bpf_cpu from ubuntu_kernel_selftests/net crash P8 node entei on 5.8 kernel (Oops: Exception in kernel mode, sig: 4 [#1])
Po-Hsu Lin, Thanks for the info. I was able to reproduce the issue on other 2 Power8 servers, but just running the `reuseport_bpf_cpu test` more than once (as you mentioned on comment#3). I've tested this with focal-hwe (Linux thiel 5.11.0-27-generic) and hirsute (5.11.0-31-generic). steps: 1. Run the cpu-hotplug test; 2. Run the reuseport_bpf_cpu test; 3. re-run the reuseport_bpf_cpu test. ``` thiel login: [24669.414656] Oops: Exception in kernel mode, sig: 4 [#1] [24669.414710] LE PAGE_SIZE=64K MMU=Hash SMP NR_CPUS=2048 NUMA PowerNV ``` ``` gulpin login: [277274.876010] Oops: Exception in kernel mode, sig: 4 [#1] [277274.876235] LE PAGE_SIZE=64K MMU=Hash SMP NR_CPUS=2048 NUMA PowerNV ``` I've also tested this 2 servers above with the upstream kernel from `https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.11.22/` I put the `reuseport_bpf_cpu test` on 20x loop and did not hit the issue, so I'd say we may have an issue with ubuntu-kernel. all 20x the test reported a success and the server did not reboot. ``` send cpu 157, receive socket 157 send cpu 159, receive socket 159 SUCCESS ``` -- 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/1927076 Title: IPv6 TCP in reuseport_bpf_cpu from ubuntu_kernel_selftests/net crash P8 node entei on 5.8 kernel (Oops: Exception in kernel mode, sig: 4 [#1]) Status in ubuntu-kernel-tests: New Status in The Ubuntu-power-systems project: Confirmed Status in linux package in Ubuntu: Incomplete Status in linux source package in Hirsute: New Bug description: It looks like our P8 node "entei" tend to fail with the IPv6 TCP test from reuseport_bpf_cpu in ubuntu_kernel_selftests/net on 5.8 kernels: # send cpu 119, receive socket 119 # send cpu 121, receive socket 121 # send cpu 123, receive socket 123 # send cpu 125, receive socket 125 # send cpu 127, receive socket 127 # IPv6 TCP publish-job-status: using request.json It failed silently here, this can be 100% reproduced with Groovy 5.8 and Focal 5.8. This will cause the ubuntu_kernel_selftests being interrupted, the test result for other tests cannot be processed to our result page. Please find attachment for the complete "net" test result on this node with Groovy 5.8.0-52.59 Add the kqa-blocker tag as this might needs to be manually verified. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1927076/+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 1927076] Re: IPv6 TCP in reuseport_bpf_cpu from ubuntu_kernel_selftests/net crash P8 node entei on 5.8 kernel (Oops: Exception in kernel mode, sig: 4 [#1])
** Attachment added: "lscpu_thiel" https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1927076/+attachment/5524414/+files/lscpu_thiel -- 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/1927076 Title: IPv6 TCP in reuseport_bpf_cpu from ubuntu_kernel_selftests/net crash P8 node entei on 5.8 kernel (Oops: Exception in kernel mode, sig: 4 [#1]) Status in ubuntu-kernel-tests: New Status in The Ubuntu-power-systems project: Confirmed Status in linux package in Ubuntu: Incomplete Status in linux source package in Hirsute: New Bug description: It looks like our P8 node "entei" tend to fail with the IPv6 TCP test from reuseport_bpf_cpu in ubuntu_kernel_selftests/net on 5.8 kernels: # send cpu 119, receive socket 119 # send cpu 121, receive socket 121 # send cpu 123, receive socket 123 # send cpu 125, receive socket 125 # send cpu 127, receive socket 127 # IPv6 TCP publish-job-status: using request.json It failed silently here, this can be 100% reproduced with Groovy 5.8 and Focal 5.8. This will cause the ubuntu_kernel_selftests being interrupted, the test result for other tests cannot be processed to our result page. Please find attachment for the complete "net" test result on this node with Groovy 5.8.0-52.59 Add the kqa-blocker tag as this might needs to be manually verified. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1927076/+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 1927076] Re: IPv6 TCP in reuseport_bpf_cpu from ubuntu_kernel_selftests/net crash P8 node entei on 5.8 kernel (Oops: Exception in kernel mode, sig: 4 [#1])
** Attachment added: "lscpu_gulpin" https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1927076/+attachment/5524415/+files/lscpu_gulpin -- 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/1927076 Title: IPv6 TCP in reuseport_bpf_cpu from ubuntu_kernel_selftests/net crash P8 node entei on 5.8 kernel (Oops: Exception in kernel mode, sig: 4 [#1]) Status in ubuntu-kernel-tests: New Status in The Ubuntu-power-systems project: Confirmed Status in linux package in Ubuntu: Incomplete Status in linux source package in Hirsute: New Bug description: It looks like our P8 node "entei" tend to fail with the IPv6 TCP test from reuseport_bpf_cpu in ubuntu_kernel_selftests/net on 5.8 kernels: # send cpu 119, receive socket 119 # send cpu 121, receive socket 121 # send cpu 123, receive socket 123 # send cpu 125, receive socket 125 # send cpu 127, receive socket 127 # IPv6 TCP publish-job-status: using request.json It failed silently here, this can be 100% reproduced with Groovy 5.8 and Focal 5.8. This will cause the ubuntu_kernel_selftests being interrupted, the test result for other tests cannot be processed to our result page. Please find attachment for the complete "net" test result on this node with Groovy 5.8.0-52.59 Add the kqa-blocker tag as this might needs to be manually verified. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1927076/+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 1927076] Re: IPv6 TCP in reuseport_bpf_cpu from ubuntu_kernel_selftests/net crash P8 node entei on 5.8 kernel (Oops: Exception in kernel mode, sig: 4 [#1])
Ok I've re-ran the test with latest kernel versions on the same systems: `thiel` (8001-22C) with focal-hwe (5.11.0-34-generic): ``` [ 3255.763649] Oops: Exception in kernel mode, sig: 5 [#1] [ 3255.763723] LE PAGE_SIZE=64K MMU=Hash SMP NR_CPUS=2048 NUMA PowerNV ``` And `gulpin` (8335-GTA) with hirsute (5.11.0-34-generic) 2nd run of `reuseport_bpf_cpu`: ``` [ 760.451968] BUG: Unable to handle kernel instruction fetch (NULL pointer?) [ 760.452035] Faulting instruction address: 0x [ 760.452196] Oops: Kernel access of bad area, sig: 11 [#1] [ 760.452212] LE PAGE_SIZE=64K MMU=Hash SMP NR_CPUS=2048 NUMA PowerNV ``` -- 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/1927076 Title: IPv6 TCP in reuseport_bpf_cpu from ubuntu_kernel_selftests/net crash P8 node entei on 5.8 kernel (Oops: Exception in kernel mode, sig: 4 [#1]) Status in ubuntu-kernel-tests: New Status in The Ubuntu-power-systems project: Confirmed Status in linux package in Ubuntu: Incomplete Status in linux source package in Hirsute: New Bug description: It looks like our P8 node "entei" tend to fail with the IPv6 TCP test from reuseport_bpf_cpu in ubuntu_kernel_selftests/net on 5.8 kernels: # send cpu 119, receive socket 119 # send cpu 121, receive socket 121 # send cpu 123, receive socket 123 # send cpu 125, receive socket 125 # send cpu 127, receive socket 127 # IPv6 TCP publish-job-status: using request.json It failed silently here, this can be 100% reproduced with Groovy 5.8 and Focal 5.8. This will cause the ubuntu_kernel_selftests being interrupted, the test result for other tests cannot be processed to our result page. Please find attachment for the complete "net" test result on this node with Groovy 5.8.0-52.59 Add the kqa-blocker tag as this might needs to be manually verified. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1927076/+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 1927076] Re: IPv6 TCP in reuseport_bpf_cpu from ubuntu_kernel_selftests/net crash P8 node entei on 5.8 kernel (Oops: Exception in kernel mode, sig: 4 [#1])
** Attachment added: "lscpu_entei" https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1927076/+attachment/5524453/+files/lscpu_entei -- 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/1927076 Title: IPv6 TCP in reuseport_bpf_cpu from ubuntu_kernel_selftests/net crash P8 node entei on 5.8 kernel (Oops: Exception in kernel mode, sig: 4 [#1]) Status in ubuntu-kernel-tests: New Status in The Ubuntu-power-systems project: Confirmed Status in linux package in Ubuntu: Incomplete Status in linux source package in Hirsute: New Bug description: It looks like our P8 node "entei" tend to fail with the IPv6 TCP test from reuseport_bpf_cpu in ubuntu_kernel_selftests/net on 5.8 kernels: # send cpu 119, receive socket 119 # send cpu 121, receive socket 121 # send cpu 123, receive socket 123 # send cpu 125, receive socket 125 # send cpu 127, receive socket 127 # IPv6 TCP publish-job-status: using request.json It failed silently here, this can be 100% reproduced with Groovy 5.8 and Focal 5.8. This will cause the ubuntu_kernel_selftests being interrupted, the test result for other tests cannot be processed to our result page. Please find attachment for the complete "net" test result on this node with Groovy 5.8.0-52.59 Add the kqa-blocker tag as this might needs to be manually verified. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1927076/+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 1927076] Re: IPv6 TCP in reuseport_bpf_cpu from ubuntu_kernel_selftests/net crash P8 node entei on 5.8 kernel (Oops: Exception in kernel mode, sig: 4 [#1])
Also re-ran on `entei` it is also a POWER8 (8335-GTA) with Hirsute latest kernel (5.11.0-34-generic) hit the same error - second run of `reuseport_bpf_cpu`: ``` [ 232.349547] Oops: Exception in kernel mode, sig: 4 [#1] [ 232.349647] LE PAGE_SIZE=64K MMU=Hash SMP NR_CPUS=2048 NUMA PowerNV ... [ 232.355607] LR [08d19f3b15a8] 0x8d19f3b15a8 [ 232.355855] --- interrupt: c00 [ 232.355869] Instruction dump: [ 232.356114] [ 232.356374] [ 232.356905] ---[ end trace c99c88cea832039b ]--- [ 232.508560] [ 233.508662] Kernel panic - not syncing: Aiee, killing interrupt handler! [ 233.950570] Rebooting in 10 seconds.. ``` -- 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/1927076 Title: IPv6 TCP in reuseport_bpf_cpu from ubuntu_kernel_selftests/net crash P8 node entei on 5.8 kernel (Oops: Exception in kernel mode, sig: 4 [#1]) Status in ubuntu-kernel-tests: New Status in The Ubuntu-power-systems project: Confirmed Status in linux package in Ubuntu: Incomplete Status in linux source package in Hirsute: New Bug description: It looks like our P8 node "entei" tend to fail with the IPv6 TCP test from reuseport_bpf_cpu in ubuntu_kernel_selftests/net on 5.8 kernels: # send cpu 119, receive socket 119 # send cpu 121, receive socket 121 # send cpu 123, receive socket 123 # send cpu 125, receive socket 125 # send cpu 127, receive socket 127 # IPv6 TCP publish-job-status: using request.json It failed silently here, this can be 100% reproduced with Groovy 5.8 and Focal 5.8. This will cause the ubuntu_kernel_selftests being interrupted, the test result for other tests cannot be processed to our result page. Please find attachment for the complete "net" test result on this node with Groovy 5.8.0-52.59 Add the kqa-blocker tag as this might needs to be manually verified. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1927076/+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 1927076] Re: IPv6 TCP in reuseport_bpf_cpu from ubuntu_kernel_selftests/net crash P8 node entei on 5.8 kernel (Oops: Exception in kernel mode, sig: 4 [#1])
Krzysztof, you were on a PowerVM LPAR (P8LPAR05), just let me know if there's anything that need to be tested -- 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/1927076 Title: IPv6 TCP in reuseport_bpf_cpu from ubuntu_kernel_selftests/net crash P8 node entei on 5.8 kernel (Oops: Exception in kernel mode, sig: 4 [#1]) Status in ubuntu-kernel-tests: New Status in The Ubuntu-power-systems project: Confirmed Status in linux package in Ubuntu: Incomplete Status in linux source package in Hirsute: New Bug description: It looks like our P8 node "entei" tend to fail with the IPv6 TCP test from reuseport_bpf_cpu in ubuntu_kernel_selftests/net on 5.8 kernels: # send cpu 119, receive socket 119 # send cpu 121, receive socket 121 # send cpu 123, receive socket 123 # send cpu 125, receive socket 125 # send cpu 127, receive socket 127 # IPv6 TCP publish-job-status: using request.json It failed silently here, this can be 100% reproduced with Groovy 5.8 and Focal 5.8. This will cause the ubuntu_kernel_selftests being interrupted, the test result for other tests cannot be processed to our result page. Please find attachment for the complete "net" test result on this node with Groovy 5.8.0-52.59 Add the kqa-blocker tag as this might needs to be manually verified. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1927076/+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 1927076] Re: IPv6 TCP in reuseport_bpf_cpu from ubuntu_kernel_selftests/net crash P8 node entei on 5.8 kernel (Oops: Exception in kernel mode, sig: 4 [#1])
Cascardo, I was trying to reproduce the issue as Po-Hsu Lin has mentioned (#3), but the hotplug leaves the system in the same state (shows this output): ``` ./cpu-hotplug/cpu-on-off-test.sh pid 21291's current affinity mask: pid 21291's new affinity mask: 1 CPU online/offline summary: present_cpus = 0-127 present_max = 127 Cpus in online state: 0-127 Cpus in offline state: 0 Limited scope test: one hotplug cpu (leaves cpu in the original state): online to offline to online: cpu 127 ``` I was running this way: ``` ubuntu@gulpin:~/ubuntu-hirsute/tools/testing/selftests$ make TARGETS=net ./cpu-hotplug/cpu-on-off-test.sh ./net/reuseport_bpf_cpu ``` Let me know if there's anything else needed. -- 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/1927076 Title: IPv6 TCP in reuseport_bpf_cpu from ubuntu_kernel_selftests/net crash P8 node entei on 5.8 kernel (Oops: Exception in kernel mode, sig: 4 [#1]) Status in ubuntu-kernel-tests: New Status in The Ubuntu-power-systems project: Confirmed Status in linux package in Ubuntu: Incomplete Status in linux source package in Hirsute: New Bug description: It looks like our P8 node "entei" tend to fail with the IPv6 TCP test from reuseport_bpf_cpu in ubuntu_kernel_selftests/net on 5.8 kernels: # send cpu 119, receive socket 119 # send cpu 121, receive socket 121 # send cpu 123, receive socket 123 # send cpu 125, receive socket 125 # send cpu 127, receive socket 127 # IPv6 TCP publish-job-status: using request.json It failed silently here, this can be 100% reproduced with Groovy 5.8 and Focal 5.8. This will cause the ubuntu_kernel_selftests being interrupted, the test result for other tests cannot be processed to our result page. Please find attachment for the complete "net" test result on this node with Groovy 5.8.0-52.59 Add the kqa-blocker tag as this might needs to be manually verified. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1927076/+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 1823994] [NEW] arm64: not able to install linux-generic-hwe-18.04-edge/bionic-proposed
Public bug reported: 1. linux-generic-hwe-18.04-edge from bionic-updates is installed: `linux-generic-hwe-18.04-edge/bionic-updates,bionic-security,now 4.18.0.16.65 arm64 [installed]` ``` $ dpkg -l |grep linux-generic ii linux-generic-hwe-18.04-edge 4.18.0.16.65 arm64Complete Generic Linux kernel and headers ``` 2. enable -proposed archive and update: ``` $ sudo add-apt-repository "deb http://ports.ubuntu.com/ubuntu-ports/ $(lsb_release -sc)-proposed main restricted" $ sudo apt update ``` 3. shows it is upgradable: ``` $ apt search --names-only linux-generic linux-generic-hwe-18.04-edge/bionic-proposed 5.0.0.8.66 arm64 [upgradable from: 4.18.0.16.65] Complete Generic Linux kernel and headers ``` 4. try to install it, but: ``` $ sudo apt install linux-generic-hwe-18.04-edge Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: linux-generic-hwe-18.04-edge : Depends: linux-image-generic-hwe-18.04-edge (= 5.0.0.8.66) but 4.18.0.16.65 is to be installed E: Unable to correct problems, you have held broken packages. ``` 5. same happens trying to install `linux-image-generic-hwe-18.04-edge`: ``` $ sudo apt install linux-image-generic-hwe-18.04-edge Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: linux-image-generic-hwe-18.04-edge : Depends: linux-image-5.0.0-8-generic but it is not installable E: Unable to correct problems, you have held broken packages. ``` 6. also not able to install `linux-image-5.0.0-8-generic`: ``` $ sudo apt install linux-image-5.0.0-8-generic Reading package lists... Done Building dependency tree Reading state information... Done Package linux-image-5.0.0-8-generic is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another source E: Package 'linux-image-5.0.0-8-generic' has no installation candidate ``` more info: ~$ lsb_release -rd Description:Ubuntu 18.04.2 LTS Release:18.04 ~$ apt-cache policy linux-generic-hwe-18.04-edge linux-generic-hwe-18.04-edge: Installed: 4.18.0.16.65 Candidate: 5.0.0.8.66 Version table: 5.0.0.8.66 500 500 http://ports.ubuntu.com/ubuntu-ports bionic-proposed/main arm64 Packages *** 4.18.0.16.65 500 500 http://ports.ubuntu.com/ubuntu-ports bionic-updates/main arm64 Packages 500 http://ports.ubuntu.com/ubuntu-ports bionic-security/main arm64 Packages 100 /var/lib/dpkg/status ** 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-meta in Ubuntu. https://bugs.launchpad.net/bugs/1823994 Title: arm64: not able to install linux-generic-hwe-18.04-edge/bionic- proposed Status in linux package in Ubuntu: New Bug description: 1. linux-generic-hwe-18.04-edge from bionic-updates is installed: `linux-generic-hwe-18.04-edge/bionic-updates,bionic-security,now 4.18.0.16.65 arm64 [installed]` ``` $ dpkg -l |grep linux-generic ii linux-generic-hwe-18.04-edge 4.18.0.16.65 arm64Complete Generic Linux kernel and headers ``` 2. enable -proposed archive and update: ``` $ sudo add-apt-repository "deb http://ports.ubuntu.com/ubuntu-ports/ $(lsb_release -sc)-proposed main restricted" $ sudo apt update ``` 3. shows it is upgradable: ``` $ apt search --names-only linux-generic linux-generic-hwe-18.04-edge/bionic-proposed 5.0.0.8.66 arm64 [upgradable from: 4.18.0.16.65] Complete Generic Linux kernel and headers ``` 4. try to install it, but: ``` $ sudo apt install linux-generic-hwe-18.04-edge Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: linux-generic-hwe-18.04-edge : Depe
[Kernel-packages] [Bug 1823994] Re: arm64: not able to install linux-generic-hwe-18.04-edge/bionic-proposed
adding 'lspci -vnvn' output and ``` $ cat /proc/version_signature Ubuntu 4.15.0-47.50-generic 4.15.18 ``` ** Attachment added: "lspci_output" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823994/+attachment/5254524/+files/lspci-vnvn.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1823994 Title: arm64: not able to install linux-generic-hwe-18.04-edge/bionic- proposed Status in linux package in Ubuntu: Incomplete Bug description: 1. linux-generic-hwe-18.04-edge from bionic-updates is installed: `linux-generic-hwe-18.04-edge/bionic-updates,bionic-security,now 4.18.0.16.65 arm64 [installed]` ``` $ dpkg -l |grep linux-generic ii linux-generic-hwe-18.04-edge 4.18.0.16.65 arm64Complete Generic Linux kernel and headers ``` 2. enable -proposed archive and update: ``` $ sudo add-apt-repository "deb http://ports.ubuntu.com/ubuntu-ports/ $(lsb_release -sc)-proposed main restricted" $ sudo apt update ``` 3. shows it is upgradable: ``` $ apt search --names-only linux-generic linux-generic-hwe-18.04-edge/bionic-proposed 5.0.0.8.66 arm64 [upgradable from: 4.18.0.16.65] Complete Generic Linux kernel and headers ``` 4. try to install it, but: ``` $ sudo apt install linux-generic-hwe-18.04-edge Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: linux-generic-hwe-18.04-edge : Depends: linux-image-generic-hwe-18.04-edge (= 5.0.0.8.66) but 4.18.0.16.65 is to be installed E: Unable to correct problems, you have held broken packages. ``` 5. same happens trying to install `linux-image-generic-hwe-18.04-edge`: ``` $ sudo apt install linux-image-generic-hwe-18.04-edge Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: linux-image-generic-hwe-18.04-edge : Depends: linux-image-5.0.0-8-generic but it is not installable E: Unable to correct problems, you have held broken packages. ``` 6. also not able to install `linux-image-5.0.0-8-generic`: ``` $ sudo apt install linux-image-5.0.0-8-generic Reading package lists... Done Building dependency tree Reading state information... Done Package linux-image-5.0.0-8-generic is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another source E: Package 'linux-image-5.0.0-8-generic' has no installation candidate ``` more info: ~$ lsb_release -rd Description: Ubuntu 18.04.2 LTS Release: 18.04 ~$ apt-cache policy linux-generic-hwe-18.04-edge linux-generic-hwe-18.04-edge: Installed: 4.18.0.16.65 Candidate: 5.0.0.8.66 Version table: 5.0.0.8.66 500 500 http://ports.ubuntu.com/ubuntu-ports bionic-proposed/main arm64 Packages *** 4.18.0.16.65 500 500 http://ports.ubuntu.com/ubuntu-ports bionic-updates/main arm64 Packages 500 http://ports.ubuntu.com/ubuntu-ports bionic-security/main arm64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823994/+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 1853485] [NEW] Bionic kernel panic on Cavium ThunderX CN88XX
Public bug reported: Description: kernel panic while trying to deploy Bionic 18.04.3 Linux version 4.15.0-70-generic on Cavium ThunderX CN88XX (arm64) System: Board Model: gbt-mt30 Board name: MT30-GS0 System name:MT30-GS0 SKU: CN8890-2000BG2601-AAP-Y22-G ** 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/1853485 Title: Bionic kernel panic on Cavium ThunderX CN88XX Status in linux package in Ubuntu: New Bug description: Description: kernel panic while trying to deploy Bionic 18.04.3 Linux version 4.15.0-70-generic on Cavium ThunderX CN88XX (arm64) System: Board Model: gbt-mt30 Board name: MT30-GS0 System name:MT30-GS0 SKU: CN8890-2000BG2601-AAP-Y22-G To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853485/+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 1853485] Re: Bionic kernel panic on Cavium ThunderX CN88XX
attaching Console log ** Attachment added: "console_log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853485/+attachment/5306902/+files/console_lippmann_kernel_panic -- 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/1853485 Title: Bionic kernel panic on Cavium ThunderX CN88XX Status in linux package in Ubuntu: New Bug description: Description: kernel panic while trying to deploy Bionic 18.04.3 Linux version 4.15.0-70-generic on Cavium ThunderX CN88XX (arm64) System: Board Model: gbt-mt30 Board name: MT30-GS0 System name:MT30-GS0 SKU: CN8890-2000BG2601-AAP-Y22-G To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853485/+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 1853485] Re: Bionic kernel panic on Cavium ThunderX CN88XX
tested it in a 10 times loop and yes, it always have the same - it get stuck here: `[ 18.640574] ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x000b ` `[ 18.641172] ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x000b ` `[ 18.609838] ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x000b ` -- 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/1853485 Title: Bionic kernel panic on Cavium ThunderX CN88XX Status in linux package in Ubuntu: Incomplete Bug description: Description: kernel panic while trying to deploy Bionic 18.04.3 Linux version 4.15.0-70-generic on Cavium ThunderX CN88XX (arm64) System: Board Model: gbt-mt30 Board name: MT30-GS0 System name:MT30-GS0 SKU: CN8890-2000BG2601-AAP-Y22-G To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853485/+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 1848127] Re: [LTCTest][OPAL][OP930] Machine hangs after injecting the Machine Check Error
** Changed in: linux (Ubuntu Bionic) Status: Fix Committed => Fix Released ** Changed in: linux (Ubuntu Disco) Status: Fix Committed => Fix Released ** Changed in: linux (Ubuntu Eoan) Status: Fix Committed => Fix Released -- 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/1848127 Title: [LTCTest][OPAL][OP930] Machine hangs after injecting the Machine Check Error Status in The Ubuntu-power-systems project: Fix Committed Status in linux package in Ubuntu: Fix Committed Status in linux source package in Bionic: Fix Released Status in linux source package in Disco: Fix Released Status in linux source package in Eoan: Fix Released Bug description: [IMPACT] MCE test renders the system unresponsive on P9 open power hardware (Withersoon) [TEST] A test kernel is available in ppa:ubuntu-power-triage/lp1848127. Please see the [OTHER] section for test details and comment #7 for results with the PPA kernel. [FIX] IBM has identified the following patch that fixes this issue: commit 99ead78afd1128bfcebe7f88f3b102fb2da09aee Author: Balbir Singh Date: Tue Aug 20 13:43:47 2019 +0530 powerpc/mce: Fix MCE handling for huge pages [REGRESSION POTENTIAL] The patch is applicable the powerpc architecture and limited in scope to MCE handling for huge pages. Patch does not touch any generic code. Regression if any is limited to powerpc MCE handling. [OTHER] == Comment: #0 - PAVAMAN SUBRAMANIYAM - 2019-05-07 23:31:20 == Install a P9 Open Power Hardware with the latest OP930 Firmware images built from the upstream op-build git tree. root@witherspoon:~# cat /etc/os-release ID="openbmc-phosphor" NAME="Phosphor OpenBMC (Phosphor OpenBMC Project Reference Distro)" VERSION="ibm-v2.3" VERSION_ID="ibm-v2.3-476-g2d622cb-r32-0-g9973ab0" PRETTY_NAME="Phosphor OpenBMC (Phosphor OpenBMC Project Reference Distro) ibm-v2.3" BUILD_ID="ibm-v2.3-476-g2d622cb-r32" root@witherspoon:~# cat /var/lib/phosphor-software-manager/pnor/ro/VERSION open-power-witherspoon-v2.3-rc2-58-g59fd0743 buildroot-2019.02.2-17-g93b841d204 skiboot-v6.3-rc2 hostboot-19a436e occ-58e422d linux-5.0.9-openpower1-p3a4d5a4 petitboot-v1.10.3 machine-xml-a6f4df3 hostboot-binaries-hw043019a.940 capp-ucode-p9-dd2-v4 sbe-249671d hcode-hw040319a.940 Then enable sw xstop manually by using below command: root@ltc-wspoon11:~# nvram -p ibm,skiboot --update-config opal-sw-xstop=enable root@ltc-wspoon11:~# nvram -p ibm,skiboot --print-config "ibm,skiboot" Partition -- experimental-fast-reset=1 snarf-mode=noo opal-sw-xstop=enable Then from the Linux HOST injected the MCE UE Error on the machine as follows: root@ltc-wspoon11:~# ./probe_cpus.sh -L CHIP ID: 0 CORE ID: 0 THREADS: 4 CPUs: 0 1 2 3 CHIP ID: 0 CORE ID: 1 THREADS: 4 CPUs: 4 5 6 7 CHIP ID: 0 CORE ID: 2 THREADS: 4 CPUs: 8 9 10 11 CHIP ID: 0 CORE ID: 3 THREADS: 4 CPUs: 12 13 14 15 CHIP ID: 0 CORE ID: 6 THREADS: 4 CPUs: 16 17 18 19 CHIP ID: 0 CORE ID: 7 THREADS: 4 CPUs: 20 21 22 23 CHIP ID: 0 CORE ID: 8 THREADS: 4 CPUs: 24 25 26 27 CHIP ID: 0 CORE ID: 9 THREADS: 4 CPUs: 28 29 30 31 CHIP ID: 0 CORE ID: 10 THREADS: 4 CPUs: 32 33 34 35 CHIP ID: 0 CORE ID: 11 THREADS: 4 CPUs: 36 37 38 39 CHIP ID: 0 CORE ID: 12 THREADS: 4 CPUs: 40 41 42 43 CHIP ID: 0 CORE ID: 13 THREADS: 4 CPUs: 44 45 46 47 CHIP ID: 0 CORE ID: 16 THREADS: 4 CPUs: 48 49 50 51 CHIP ID: 0 CORE ID: 17 THREADS: 4 CPUs: 52 53 54 55 CHIP ID: 0 CORE ID: 18 THREADS: 4 CPUs: 56 57 58 59 CHIP ID: 0 CORE ID: 19 THREADS: 4 CPUs: 60 61 62 63 CHIP ID: 0 CORE ID: 20 THREADS: 4 CPUs: 64 65 66 67 CHIP ID: 0 CORE ID: 21 THREADS: 4 CPUs: 68 69 70 71 CHIP ID: 8 CORE ID: 6 THREADS: 4 CPUs: 72 73 74 75 CHIP ID: 8 CORE ID: 7 THREADS: 4 CPUs: 76 77 78 79 CHIP ID: 8 CORE ID: 8 THREADS: 4 CPUs: 80 81 82 83 CHIP ID: 8 CORE ID: 9 THREADS: 4 CPUs: 84 85 86 87 CHIP ID: 8 CORE ID: 10 THREADS: 4 CPUs: 88 89 90 91 CHIP ID: 8 CORE ID: 11 THREADS: 4 CPUs: 92 93 94 95 CHIP ID: 8 CORE ID: 12 THREADS: 4 CPUs: 96 97 98 99 CHIP ID: 8 CORE ID: 13 THREADS: 4 CPUs: 100 101 102 103 CHIP ID: 8 CORE ID: 14 THREADS: 4 CPUs: 104 105 106 107 CHIP ID: 8 CORE ID: 15 THREADS: 4 CPUs: 108 109 110 111 CHIP ID: 8 CORE ID: 16 THREADS: 4 CPUs: 112 113 114 115 CHIP ID: 8 CORE ID: 17 THREADS: 4 CPUs: 116 117 118 119 CHIP ID: 8 CORE ID: 18 THREADS: 4 CPUs: 120 121 122 123 CHIP ID: 8 CORE ID: 19 THREADS: 4 CPUs: 124 125 126 127 CHIP ID: 8 CORE ID: 20 THREADS: 4 CPUs: 128 129 130 131 CHIP ID: 8 CORE ID: 21 THREADS: 4 CPUs: 132 133 134 135 CHIP ID: 8 CORE ID: 22 THREADS: 4 CPUs: 136 137 138 139 CHIP ID: 8 CORE ID: 23 THREADS: 4 CPUs: 140 141 142 143
[Kernel-packages] [Bug 1854071] Re: Backport In-Memory Collection Counters (IMC) trace-mode patches
** Changed in: ubuntu-power-systems Status: New => Triaged -- 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/1854071 Title: Backport In-Memory Collection Counters (IMC) trace-mode patches Status in The Ubuntu-power-systems project: Triaged Status in linux package in Ubuntu: New Bug description: == Comment: #0 - Murilo Opsfelder Araujo - 2019-11-08 06:30:06 == ---Problem Description--- The following patches may be wanted in >= Bionic kernels: 1. powerpc/include: Add data structures and macros for IMC trace mode https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=next&id=d1720adff3783a2ba7c128e304a385d18962835b 2. powerpc/perf: Rearrange setting of ldbar for thread-imc https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=next&id=dd50cf7cbc7bdd86483b797ac3d27b37d5aeeaa4 3. powerpc/perf: Add privileged access check for thread_imc https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=next&id=216c3087a346db8d7c8a064d2b8f0f49e4694934 4. powerpc/perf: Trace imc events detection and cpuhotplug https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=next&id=72c69dcddce103338de558c5c6e9ef9e4f607ce1 5. powerpc/perf: Trace imc PMU functions https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=next&id=012ae244845f19d5f6ca2a90426851bc5044a0dc Patch #3 addresses a security issue. ---uname output--- na Machine Type = na ---Debugger--- A debugger is not configured Stack trace output: no Oops output: no System Dump Info: The system is not configured to capture a system dump. == Comment: #12 - Murilo Opsfelder Araujo - 2019-11-22 07:41:20 == Please mirror to Canonical to backporting this single patch for >= Bionic kernels (or for which kernels they find appropriate): https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?id=216c3087a346db8d7c8a064d2b8f0f49e4694934 commit 216c3087a346db8d7c8a064d2b8f0f49e4694934 Author: Madhavan Srinivasan Date: Tue Apr 16 15:18:29 2019 +0530 powerpc/perf: Add privileged access check for thread_imc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1854071/+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 2056491] Re: not able to install noble on PowerVM LPARs `Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block`
This is happening with Kernel 6.8 (currently available image noble-live- server-ppc64el.iso `2024-03-05 09:03`). I was able to install noble on the same systems last week, when Noble still had kernel 6.6. I'm also able to install Jammy 22.04.4 on both mentioned LPARs - P9 and P10. The issue is not happening on a Power9 bare metal. -- 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/2056491 Title: not able to install noble on PowerVM LPARs `Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block` Status in linux package in Ubuntu: New Bug description: After I select `Try or Install Ubuntu Server` on a PowerVM ppc64le Power9 or Power10 : error: out of memory. Press any key to continue... OF stdout device is: /vdevice/vty@3000 Preparing to boot Linux version 6.8.0-11-generic (buildd@bos01-ppc64el-003) (powerpc64le-linux-gnu-gcc-13 (Ubuntu 13.2.0-13ubuntu1) 13.2.0, GNU ld (GNU Binutils for Ubuntu) 2.42) #11-Ubuntu SMP Wed Feb 14 00:33:03 UTC 2024 (Ubuntu 6.8.0-11.11-generic 6.8.0-rc4) Detected machine type: 0101 command line: BOOT_IMAGE=/casper/vmlinux quiet --- Max number of cores passed to firmware: 256 (NR_CPUS = 2048) Calling ibm,client-architecture-support... done memory layout at init: memory_limit : (16 MB aligned) alloc_bottom : 0e67 alloc_top: 2000 alloc_top_hi : 2000 rmo_top : 2000 ram_top : 2000 instantiating rtas at 0x1ec3... done prom_hold_cpus: skipped copying OF device tree... Building dt strings... Building dt structure... Device tree strings 0x1078 -> 0x1078179e Device tree struct 0x1079 -> 0x107a Quiescing Open Firmware ... Booting Linux via __start() @ 0x0a75 ... [0.019184] plpks: POWER LPAR Platform KeyStore is not supported or enabled [0.114052] SED: plpks not available [0.114507] /dev/root: Can't open blockdev [0.114520] List of all bdev filesystems: [0.114523] ext3 [0.114523] ext2 [0.114525] ext4 [0.114527] squashfs [0.114529] vfat [0.114531] fuseblk [0.114532] [0.114535] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) [0.114540] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 6.8.0-11-generic #11-Ubuntu [0.114545] Hardware name: IBM,9080-HEX POWER10 (raw) 0x800200 0xf06 of:IBM,FW1030.00 (NH1030_017) hv:phyp pSeries [0.114551] Call Trace: [0.114553] [c6403b40] [c16b2f28] dump_stack_lvl+0x70/0xb4 (unreliable) [0.114562] [c6403b70] [c01926ec] panic+0x300/0x524 [0.114568] [c6403c10] [c301146c] mount_root_generic+0x208/0x448 [0.114574] [c6403ce0] [c30118d8] prepare_namespace+0x98/0x430 [0.114580] [c6403d70] [c3010820] kernel_init_freeable+0x32c/0x37c [0.114585] [c6403de0] [c00115ec] kernel_init+0x34/0x298 [0.114591] [c6403e50] [c000dfbc] ret_from_kernel_user_thread+0x14/0x1c [0.114596] --- interrupt: 0 at 0x0 [0.117006] pstore: backend (nvram) writing error (-1) [0.119362] Rebooting in 10 seconds.. This is the message from a Power10(9080-HEX), but the same is happening on a PowrerVM-Power9 (9009-22A) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2056491/+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 2056491] [NEW] not able to install noble on PowerVM LPARs `Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block`
Public bug reported: After I select `Try or Install Ubuntu Server` on a PowerVM ppc64le Power9 or Power10 : error: out of memory. Press any key to continue... OF stdout device is: /vdevice/vty@3000 Preparing to boot Linux version 6.8.0-11-generic (buildd@bos01-ppc64el-003) (powerpc64le-linux-gnu-gcc-13 (Ubuntu 13.2.0-13ubuntu1) 13.2.0, GNU ld (GNU Binutils for Ubuntu) 2.42) #11-Ubuntu SMP Wed Feb 14 00:33:03 UTC 2024 (Ubuntu 6.8.0-11.11-generic 6.8.0-rc4) Detected machine type: 0101 command line: BOOT_IMAGE=/casper/vmlinux quiet --- Max number of cores passed to firmware: 256 (NR_CPUS = 2048) Calling ibm,client-architecture-support... done memory layout at init: memory_limit : (16 MB aligned) alloc_bottom : 0e67 alloc_top: 2000 alloc_top_hi : 2000 rmo_top : 2000 ram_top : 2000 instantiating rtas at 0x1ec3... done prom_hold_cpus: skipped copying OF device tree... Building dt strings... Building dt structure... Device tree strings 0x1078 -> 0x1078179e Device tree struct 0x1079 -> 0x107a Quiescing Open Firmware ... Booting Linux via __start() @ 0x0a75 ... [0.019184] plpks: POWER LPAR Platform KeyStore is not supported or enabled [0.114052] SED: plpks not available [0.114507] /dev/root: Can't open blockdev [0.114520] List of all bdev filesystems: [0.114523] ext3 [0.114523] ext2 [0.114525] ext4 [0.114527] squashfs [0.114529] vfat [0.114531] fuseblk [0.114532] [0.114535] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) [0.114540] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 6.8.0-11-generic #11-Ubuntu [0.114545] Hardware name: IBM,9080-HEX POWER10 (raw) 0x800200 0xf06 of:IBM,FW1030.00 (NH1030_017) hv:phyp pSeries [0.114551] Call Trace: [0.114553] [c6403b40] [c16b2f28] dump_stack_lvl+0x70/0xb4 (unreliable) [0.114562] [c6403b70] [c01926ec] panic+0x300/0x524 [0.114568] [c6403c10] [c301146c] mount_root_generic+0x208/0x448 [0.114574] [c6403ce0] [c30118d8] prepare_namespace+0x98/0x430 [0.114580] [c6403d70] [c3010820] kernel_init_freeable+0x32c/0x37c [0.114585] [c6403de0] [c00115ec] kernel_init+0x34/0x298 [0.114591] [c6403e50] [c000dfbc] ret_from_kernel_user_thread+0x14/0x1c [0.114596] --- interrupt: 0 at 0x0 [0.117006] pstore: backend (nvram) writing error (-1) [0.119362] Rebooting in 10 seconds.. This is the message from a Power10(9080-HEX), but the same is happening on a PowrerVM-Power9 (9009-22A) ** 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/2056491 Title: not able to install noble on PowerVM LPARs `Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block` Status in linux package in Ubuntu: New Bug description: After I select `Try or Install Ubuntu Server` on a PowerVM ppc64le Power9 or Power10 : error: out of memory. Press any key to continue... OF stdout device is: /vdevice/vty@3000 Preparing to boot Linux version 6.8.0-11-generic (buildd@bos01-ppc64el-003) (powerpc64le-linux-gnu-gcc-13 (Ubuntu 13.2.0-13ubuntu1) 13.2.0, GNU ld (GNU Binutils for Ubuntu) 2.42) #11-Ubuntu SMP Wed Feb 14 00:33:03 UTC 2024 (Ubuntu 6.8.0-11.11-generic 6.8.0-rc4) Detected machine type: 0101 command line: BOOT_IMAGE=/casper/vmlinux quiet --- Max number of cores passed to firmware: 256 (NR_CPUS = 2048) Calling ibm,client-architecture-support... done memory layout at init: memory_limit : (16 MB aligned) alloc_bottom : 0e67 alloc_top: 2000 alloc_top_hi : 2000 rmo_top : 2000 ram_top : 2000 instantiating rtas at 0x1ec3... done prom_hold_cpus: skipped copying OF device tree... Building dt strings... Building dt structure... Device tree strings 0x1078 -> 0x1078179e Device tree struct 0x1079 -> 0x107a Quiescing Open Firmware ... Booting Linux via __start() @ 0x0a75 ... [0.019184] plpks: POWER LPAR Platform KeyStore is not supported or enabled [0.114052] SED: plpks not available [0.114507] /dev/root: Can't open blockdev [0.114520] List of all bdev filesystems: [0.114523] ext3 [0.114523] ext2 [0.114525] ext4 [0.114527] squashfs [0.114529] vfat [0.114531] fuseblk [0.114532] [0.114535] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) [0.11454
[Kernel-packages] [Bug 2056491] Re: not able to install noble on PowerVM LPARs `Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block`
re-tested with today's image http://cdimage.ubuntu.com/ubuntu- server/daily-live/20240307/ - same -- 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/2056491 Title: not able to install noble on PowerVM LPARs `Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block` Status in linux package in Ubuntu: New Bug description: After I select `Try or Install Ubuntu Server` on a PowerVM ppc64le Power9 or Power10 : error: out of memory. Press any key to continue... OF stdout device is: /vdevice/vty@3000 Preparing to boot Linux version 6.8.0-11-generic (buildd@bos01-ppc64el-003) (powerpc64le-linux-gnu-gcc-13 (Ubuntu 13.2.0-13ubuntu1) 13.2.0, GNU ld (GNU Binutils for Ubuntu) 2.42) #11-Ubuntu SMP Wed Feb 14 00:33:03 UTC 2024 (Ubuntu 6.8.0-11.11-generic 6.8.0-rc4) Detected machine type: 0101 command line: BOOT_IMAGE=/casper/vmlinux quiet --- Max number of cores passed to firmware: 256 (NR_CPUS = 2048) Calling ibm,client-architecture-support... done memory layout at init: memory_limit : (16 MB aligned) alloc_bottom : 0e67 alloc_top: 2000 alloc_top_hi : 2000 rmo_top : 2000 ram_top : 2000 instantiating rtas at 0x1ec3... done prom_hold_cpus: skipped copying OF device tree... Building dt strings... Building dt structure... Device tree strings 0x1078 -> 0x1078179e Device tree struct 0x1079 -> 0x107a Quiescing Open Firmware ... Booting Linux via __start() @ 0x0a75 ... [0.019184] plpks: POWER LPAR Platform KeyStore is not supported or enabled [0.114052] SED: plpks not available [0.114507] /dev/root: Can't open blockdev [0.114520] List of all bdev filesystems: [0.114523] ext3 [0.114523] ext2 [0.114525] ext4 [0.114527] squashfs [0.114529] vfat [0.114531] fuseblk [0.114532] [0.114535] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) [0.114540] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 6.8.0-11-generic #11-Ubuntu [0.114545] Hardware name: IBM,9080-HEX POWER10 (raw) 0x800200 0xf06 of:IBM,FW1030.00 (NH1030_017) hv:phyp pSeries [0.114551] Call Trace: [0.114553] [c6403b40] [c16b2f28] dump_stack_lvl+0x70/0xb4 (unreliable) [0.114562] [c6403b70] [c01926ec] panic+0x300/0x524 [0.114568] [c6403c10] [c301146c] mount_root_generic+0x208/0x448 [0.114574] [c6403ce0] [c30118d8] prepare_namespace+0x98/0x430 [0.114580] [c6403d70] [c3010820] kernel_init_freeable+0x32c/0x37c [0.114585] [c6403de0] [c00115ec] kernel_init+0x34/0x298 [0.114591] [c6403e50] [c000dfbc] ret_from_kernel_user_thread+0x14/0x1c [0.114596] --- interrupt: 0 at 0x0 [0.117006] pstore: backend (nvram) writing error (-1) [0.119362] Rebooting in 10 seconds.. This is the message from a Power10(9080-HEX), but the same is happening on a PowrerVM-Power9 (9009-22A) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2056491/+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 2056491] Re: not able to install noble on PowerVM LPARs `Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block`
Paolo, I was able to install it (image from March 1st `20240301`) , update to the bootstrap kernel from the PPA you sent: patricia@noble-1mar:~$ cat /var/log/installer/media-info Ubuntu-Server 24.04 LTS "Noble Numbat" - Daily ppc64el (20240301)patricia@noble-1mar:~$ patricia@noble-1mar:~$ apt list --upgradable |grep linux-gen linux-generic/noble 6.8.0-15.15 ppc64el [upgradable from: 6.8.0-11.11+1] ... and boot: patricia@noble-1mar:~$ uname -a Linux noble-1mar 6.8.0-15-generic #15-Ubuntu SMP Mon Mar 4 12:38:17 UTC 2024 ppc64le ppc64le ppc64le GNU/Linux -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2056491 Title: not able to install noble on PowerVM LPARs `Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block` Status in The Ubuntu-power-systems project: New Status in linux package in Ubuntu: New Bug description: After I select `Try or Install Ubuntu Server` on a PowerVM ppc64le Power9 or Power10 : error: out of memory. Press any key to continue... OF stdout device is: /vdevice/vty@3000 Preparing to boot Linux version 6.8.0-11-generic (buildd@bos01-ppc64el-003) (powerpc64le-linux-gnu-gcc-13 (Ubuntu 13.2.0-13ubuntu1) 13.2.0, GNU ld (GNU Binutils for Ubuntu) 2.42) #11-Ubuntu SMP Wed Feb 14 00:33:03 UTC 2024 (Ubuntu 6.8.0-11.11-generic 6.8.0-rc4) Detected machine type: 0101 command line: BOOT_IMAGE=/casper/vmlinux quiet --- Max number of cores passed to firmware: 256 (NR_CPUS = 2048) Calling ibm,client-architecture-support... done memory layout at init: memory_limit : (16 MB aligned) alloc_bottom : 0e67 alloc_top: 2000 alloc_top_hi : 2000 rmo_top : 2000 ram_top : 2000 instantiating rtas at 0x1ec3... done prom_hold_cpus: skipped copying OF device tree... Building dt strings... Building dt structure... Device tree strings 0x1078 -> 0x1078179e Device tree struct 0x1079 -> 0x107a Quiescing Open Firmware ... Booting Linux via __start() @ 0x0a75 ... [0.019184] plpks: POWER LPAR Platform KeyStore is not supported or enabled [0.114052] SED: plpks not available [0.114507] /dev/root: Can't open blockdev [0.114520] List of all bdev filesystems: [0.114523] ext3 [0.114523] ext2 [0.114525] ext4 [0.114527] squashfs [0.114529] vfat [0.114531] fuseblk [0.114532] [0.114535] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) [0.114540] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 6.8.0-11-generic #11-Ubuntu [0.114545] Hardware name: IBM,9080-HEX POWER10 (raw) 0x800200 0xf06 of:IBM,FW1030.00 (NH1030_017) hv:phyp pSeries [0.114551] Call Trace: [0.114553] [c6403b40] [c16b2f28] dump_stack_lvl+0x70/0xb4 (unreliable) [0.114562] [c6403b70] [c01926ec] panic+0x300/0x524 [0.114568] [c6403c10] [c301146c] mount_root_generic+0x208/0x448 [0.114574] [c6403ce0] [c30118d8] prepare_namespace+0x98/0x430 [0.114580] [c6403d70] [c3010820] kernel_init_freeable+0x32c/0x37c [0.114585] [c6403de0] [c00115ec] kernel_init+0x34/0x298 [0.114591] [c6403e50] [c000dfbc] ret_from_kernel_user_thread+0x14/0x1c [0.114596] --- interrupt: 0 at 0x0 [0.117006] pstore: backend (nvram) writing error (-1) [0.119362] Rebooting in 10 seconds.. This is the message from a Power10(9080-HEX), but the same is happening on a PowrerVM-Power9 (9009-22A) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/2056491/+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 2056491] Re: not able to install noble on PowerVM LPARs `Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block`
Hi Chavez, thanks for checking it. I see this output: ``` Memory Keyboard Network Speaker ok 0 > printenv real-base -- Partition: common Signature: 0x70 --- real-basec0 c0 ok 0 > ``` I'm able to install Ubuntu Jammy 22.04 LTS into the same partitions. ISO via Virtual target device. I don't see the same error when trying an older image - working installation. Let me know if you need any other info. -- 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/2056491 Title: not able to install noble on PowerVM LPARs `Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block` Status in The Ubuntu-power-systems project: New Status in linux package in Ubuntu: New Bug description: After I select `Try or Install Ubuntu Server` on a PowerVM ppc64le Power9 or Power10 : error: out of memory. Press any key to continue... OF stdout device is: /vdevice/vty@3000 Preparing to boot Linux version 6.8.0-11-generic (buildd@bos01-ppc64el-003) (powerpc64le-linux-gnu-gcc-13 (Ubuntu 13.2.0-13ubuntu1) 13.2.0, GNU ld (GNU Binutils for Ubuntu) 2.42) #11-Ubuntu SMP Wed Feb 14 00:33:03 UTC 2024 (Ubuntu 6.8.0-11.11-generic 6.8.0-rc4) Detected machine type: 0101 command line: BOOT_IMAGE=/casper/vmlinux quiet --- Max number of cores passed to firmware: 256 (NR_CPUS = 2048) Calling ibm,client-architecture-support... done memory layout at init: memory_limit : (16 MB aligned) alloc_bottom : 0e67 alloc_top: 2000 alloc_top_hi : 2000 rmo_top : 2000 ram_top : 2000 instantiating rtas at 0x1ec3... done prom_hold_cpus: skipped copying OF device tree... Building dt strings... Building dt structure... Device tree strings 0x1078 -> 0x1078179e Device tree struct 0x1079 -> 0x107a Quiescing Open Firmware ... Booting Linux via __start() @ 0x0a75 ... [0.019184] plpks: POWER LPAR Platform KeyStore is not supported or enabled [0.114052] SED: plpks not available [0.114507] /dev/root: Can't open blockdev [0.114520] List of all bdev filesystems: [0.114523] ext3 [0.114523] ext2 [0.114525] ext4 [0.114527] squashfs [0.114529] vfat [0.114531] fuseblk [0.114532] [0.114535] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) [0.114540] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 6.8.0-11-generic #11-Ubuntu [0.114545] Hardware name: IBM,9080-HEX POWER10 (raw) 0x800200 0xf06 of:IBM,FW1030.00 (NH1030_017) hv:phyp pSeries [0.114551] Call Trace: [0.114553] [c6403b40] [c16b2f28] dump_stack_lvl+0x70/0xb4 (unreliable) [0.114562] [c6403b70] [c01926ec] panic+0x300/0x524 [0.114568] [c6403c10] [c301146c] mount_root_generic+0x208/0x448 [0.114574] [c6403ce0] [c30118d8] prepare_namespace+0x98/0x430 [0.114580] [c6403d70] [c3010820] kernel_init_freeable+0x32c/0x37c [0.114585] [c6403de0] [c00115ec] kernel_init+0x34/0x298 [0.114591] [c6403e50] [c000dfbc] ret_from_kernel_user_thread+0x14/0x1c [0.114596] --- interrupt: 0 at 0x0 [0.117006] pstore: backend (nvram) writing error (-1) [0.119362] Rebooting in 10 seconds.. This is the message from a Power10(9080-HEX), but the same is happening on a PowrerVM-Power9 (9009-22A) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/2056491/+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 2056491] Re: not able to install noble on PowerVM LPARs `Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block`
I was able to successfully install and boot PowerVM partitions - Power9 and Power10 with the latest kernel `6.8.0-20.20` (today's image - 20240405) : POWER10 LPAR: ``` patricia@noble-a5:~$ cat /var/log/installer/media-info Ubuntu-Server 24.04 LTS "Noble Numbat" - Daily ppc64el (20240405)patricia@noble-a5:~$ patricia@noble-a5:~$ uname -a Linux noble-a5 6.8.0-20-generic #20-Ubuntu SMP Mon Mar 18 11:46:05 UTC 2024 ppc64le ppc64le ppc64le GNU/Linux patricia@noble-a5:~$ lscpu |grep Model Model name: POWER10 (architected), altivec supported ``` and POWER9 LPAR: ``` patricia@p9g-lpar-i:~$ lscpu |grep Model && uname -a Model name: POWER9 (architected), altivec supported Model:2.2 (pvr 004e 0202) Linux p9g-lpar-i 6.8.0-20-generic #20-Ubuntu SMP Mon Mar 18 11:46:05 UTC 2024 ppc64le ppc64le ppc64le GNU/Linux ``` -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2056491 Title: not able to install noble on PowerVM LPARs `Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block` Status in The Ubuntu-power-systems project: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: After I select `Try or Install Ubuntu Server` on a PowerVM ppc64le Power9 or Power10 : error: out of memory. Press any key to continue... OF stdout device is: /vdevice/vty@3000 Preparing to boot Linux version 6.8.0-11-generic (buildd@bos01-ppc64el-003) (powerpc64le-linux-gnu-gcc-13 (Ubuntu 13.2.0-13ubuntu1) 13.2.0, GNU ld (GNU Binutils for Ubuntu) 2.42) #11-Ubuntu SMP Wed Feb 14 00:33:03 UTC 2024 (Ubuntu 6.8.0-11.11-generic 6.8.0-rc4) Detected machine type: 0101 command line: BOOT_IMAGE=/casper/vmlinux quiet --- Max number of cores passed to firmware: 256 (NR_CPUS = 2048) Calling ibm,client-architecture-support... done memory layout at init: memory_limit : (16 MB aligned) alloc_bottom : 0e67 alloc_top: 2000 alloc_top_hi : 2000 rmo_top : 2000 ram_top : 2000 instantiating rtas at 0x1ec3... done prom_hold_cpus: skipped copying OF device tree... Building dt strings... Building dt structure... Device tree strings 0x1078 -> 0x1078179e Device tree struct 0x1079 -> 0x107a Quiescing Open Firmware ... Booting Linux via __start() @ 0x0a75 ... [0.019184] plpks: POWER LPAR Platform KeyStore is not supported or enabled [0.114052] SED: plpks not available [0.114507] /dev/root: Can't open blockdev [0.114520] List of all bdev filesystems: [0.114523] ext3 [0.114523] ext2 [0.114525] ext4 [0.114527] squashfs [0.114529] vfat [0.114531] fuseblk [0.114532] [0.114535] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) [0.114540] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 6.8.0-11-generic #11-Ubuntu [0.114545] Hardware name: IBM,9080-HEX POWER10 (raw) 0x800200 0xf06 of:IBM,FW1030.00 (NH1030_017) hv:phyp pSeries [0.114551] Call Trace: [0.114553] [c6403b40] [c16b2f28] dump_stack_lvl+0x70/0xb4 (unreliable) [0.114562] [c6403b70] [c01926ec] panic+0x300/0x524 [0.114568] [c6403c10] [c301146c] mount_root_generic+0x208/0x448 [0.114574] [c6403ce0] [c30118d8] prepare_namespace+0x98/0x430 [0.114580] [c6403d70] [c3010820] kernel_init_freeable+0x32c/0x37c [0.114585] [c6403de0] [c00115ec] kernel_init+0x34/0x298 [0.114591] [c6403e50] [c000dfbc] ret_from_kernel_user_thread+0x14/0x1c [0.114596] --- interrupt: 0 at 0x0 [0.117006] pstore: backend (nvram) writing error (-1) [0.119362] Rebooting in 10 seconds.. This is the message from a Power10(9080-HEX), but the same is happening on a PowrerVM-Power9 (9009-22A) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/2056491/+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 2060039] Re: [Ubuntu-24.04] FADump with recommended crash size is making the L1 hang
Hello, we have started to work on this, but it will take a while, as we need to follow the SRU (Stable Release Update) process. 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/2060039 Title: [Ubuntu-24.04] FADump with recommended crash size is making the L1 hang Status in The Ubuntu-power-systems project: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Problem description : == Triggered FADump with the recommended crash. L1 host got hung. As per the public document https://wiki.ubuntu.com/ppc64el/Recommendations recommended crash kernel size is 1024M for the system. But with 1024M and 2048M, the L1 is getting hanged. with 4096, crash is generated and collected. root@ubuntu2404:~# uname -ar Linux ubuntu2404 6.8.0-11-generic #11-Ubuntu SMP Wed Feb 14 00:33:03 UTC 2024 ppc64le ppc64le ppc64le GNU/Linux root@ubuntu2404:~# free -h totalusedfree shared buff/cache available Mem:48Gi 1.7Gi46Gi13Mi 687Mi 46Gi Swap: 8.0Gi 0B 8.0Gi root@ubuntu2404:~# cat /proc/cmdline BOOT_IMAGE=/vmlinux-6.8.0-11-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro fadump=on crashkernel=1024M root@ubuntu2404:~# dmesg | grep -i reser [0.00] fadump: Reserved 1024MB of memory at 0x004000 (System RAM: 51200MB) [0.00] fadump: Initialized 0x4000 bytes cma area at 1024MB from 0x4007 bytes of memory reserved for firmware-assisted dump [0.00] Memory: 49316672K/52428800K available (23616K kernel code, 4096K rwdata, 25536K rodata, 8832K init, 2487K bss, 2063552K reserved, 1048576K cma-reserved) [0.396408] ibmvscsi 3066: Client reserve enabled root@ubuntu2404:~# kdump-config show DUMP_MODE:fadump USE_KDUMP:1 KDUMP_COREDIR:/var/crash /var/lib/kdump/vmlinuz kdump initrd: /var/lib/kdump/initrd.img current state:ready to fadump IBM is looking to update the crash kernel reservations section of the wiki for Power. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/2060039/+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 2074376] Re: Disable PCI_DYNAMIC_OF_NODES in Ubuntu
** Also affects: ubuntu-power-systems 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/2074376 Title: Disable PCI_DYNAMIC_OF_NODES in Ubuntu Status in The Ubuntu-power-systems project: New Status in linux package in Ubuntu: Fix Committed Status in linux source package in Noble: Fix Committed Status in linux source package in Oracular: Fix Committed Bug description: This came in via KTML from upstream. It is part of a discussion between upstream and IBM reporting a bug which occurs in KVM: Rob Herring writes: >> On 2024/07/11 06:20 AM, Rob Herring wrote: >>> On Wed, Jul 3, 2024 at 8:17 AM Amit Machhiwal wrote: With CONFIG_PCI_DYNAMIC_OF_NODES [1], a hot-plug and hot-unplug sequence of a PCI device attached to a PCI-bridge causes following kernel Oops on a pseries KVM guest: >>> >>> Can I ask why you have this option on in the first place? Do you have >>> a use for it or it's just a case of distros turn on every kconfig >>> option. >> >> Yes, this option is turned on in Ubuntu's distro kernel config where the issue >> was originally reported, while Fedora is keeping this turned off. >> >> root@ubuntu:~# cat /boot/config-6.8.0-38-generic | grep PCI_DYN >> CONFIG_PCI_DYNAMIC_OF_NODES=y > > Ubuntu should turn off this option. For starters, it is not complete > to be usable. Eventually, it should get removed in favor of some TBD > runtime option. > > (And we should fix the crash too) This option is described in the config system as: This option enables support for generating device tree nodes for some PCI devices. Thus, the driver of this kind can load and overlay flattened device tree for its downstream devices. . Once this option is selected, the device tree nodes will be generated for all PCI bridges. Open Firmware (OF) would be used for KVM for UEFI mode. The reported bug was related to hot-unplugging PCI devices. My guess would be that this probably is not of much use to the majority of users and might even go away. So it should really be disabled in Ubuntu, too. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/2074376/+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 2060039] Re: [Ubuntu-24.04] FADump with recommended crash size is making the L1 hang
** Description changed: + SRU Justification: + + [Impact] + * L1 host hangs when triggering FADump with recommended crash + + [Fix] + * 353d7a84c214f184d5a6b62acdec8b4424159b7c 353d7a84c214 "powerpc/64s/radix/kfence: map __kfence_pool at page granularity" + + [Test Case] + * Have a Ubuntu Server 24.04 LTS installation on ppc64el. + * Enable FADump with 1GB: fadump=on crashkernel=1024M + * A kernel panic will happen when dump got triggered + + [Regression Potential] + * There is a certain risk of a regression, but it is mapping only the memory + allocated for KFENCE pool at page granularity, reducing memory consumption + when KFENCE is used. + + * On top the commit is already upstream reviewed and accepted. + + * The modifications were done and tested by IBM. + + * The fadump feature is supported only on IBM POWER systems. + + [Other] + * The fix/commit got upstream accepted with kernel v6.11-rc4, + hence Oracular (with a planned kernel of 6.11) is not affected. + + ... + Problem description : == Triggered FADump with the recommended crash. L1 host got hung. As per the public document https://wiki.ubuntu.com/ppc64el/Recommendations recommended crash kernel size is 1024M for the system. But with 1024M and 2048M, the L1 is getting hanged. with 4096, crash is generated and collected. - root@ubuntu2404:~# uname -ar Linux ubuntu2404 6.8.0-11-generic #11-Ubuntu SMP Wed Feb 14 00:33:03 UTC 2024 ppc64le ppc64le ppc64le GNU/Linux - root@ubuntu2404:~# free -h -totalusedfree shared buff/cache available + totalusedfree shared buff/cache available Mem:48Gi 1.7Gi46Gi13Mi 687Mi 46Gi Swap: 8.0Gi 0B 8.0Gi - - root@ubuntu2404:~# cat /proc/cmdline + root@ubuntu2404:~# cat /proc/cmdline BOOT_IMAGE=/vmlinux-6.8.0-11-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro fadump=on crashkernel=1024M - root@ubuntu2404:~# dmesg | grep -i reser [0.00] fadump: Reserved 1024MB of memory at 0x004000 (System RAM: 51200MB) [0.00] fadump: Initialized 0x4000 bytes cma area at 1024MB from 0x4007 bytes of memory reserved for firmware-assisted dump [0.00] Memory: 49316672K/52428800K available (23616K kernel code, 4096K rwdata, 25536K rodata, 8832K init, 2487K bss, 2063552K reserved, 1048576K cma-reserved) [0.396408] ibmvscsi 3066: Client reserve enabled - root@ubuntu2404:~# kdump-config show DUMP_MODE:fadump USE_KDUMP:1 KDUMP_COREDIR:/var/crash -/var/lib/kdump/vmlinuz - kdump initrd: -/var/lib/kdump/initrd.img + /var/lib/kdump/vmlinuz + kdump initrd: + /var/lib/kdump/initrd.img current state:ready to fadump IBM is looking to update the crash kernel reservations section of the wiki for Power. -- 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/2060039 Title: [Ubuntu-24.04] FADump with recommended crash size is making the L1 hang Status in The Ubuntu-power-systems project: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: SRU Justification: [Impact] * L1 host hangs when triggering FADump with recommended crash [Fix] * 353d7a84c214f184d5a6b62acdec8b4424159b7c 353d7a84c214 "powerpc/64s/radix/kfence: map __kfence_pool at page granularity" [Test Case] * Have a Ubuntu Server 24.04 LTS installation on ppc64el. * Enable FADump with 1GB: fadump=on crashkernel=1024M * A kernel panic will happen when dump got triggered [Regression Potential] * There is a certain risk of a regression, but it is mapping only the memory allocated for KFENCE pool at page granularity, reducing memory consumption when KFENCE is used. * On top the commit is already upstream reviewed and accepted. * The modifications were done and tested by IBM. * The fadump feature is supported only on IBM POWER systems. [Other] * The fix/commit got upstream accepted with kernel v6.11-rc4, hence Oracular (with a planned kernel of 6.11) is not affected. ... Problem description : == Triggered FADump with the recommended crash. L1 host got hung. As per the
[Kernel-packages] [Bug 2060039] Re: [Ubuntu-24.04] FADump with recommended crash size is making the L1 hang
** Changed in: ubuntu-power-systems Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) => Patricia Domingues (patriciasd) -- 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/2060039 Title: [Ubuntu-24.04] FADump with recommended crash size is making the L1 hang Status in The Ubuntu-power-systems project: In Progress Status in linux package in Ubuntu: Fix Committed Status in linux source package in Noble: In Progress Status in linux source package in Oracular: Fix Committed Bug description: SRU Justification: [Impact] * L1 host hangs when triggering FADump that results in crash [Fix] * 353d7a84c214f184d5a6b62acdec8b4424159b7c 353d7a84c214 "powerpc/64s/radix/kfence: map __kfence_pool at page granularity" [Test Case] * Have a Ubuntu Server 24.04 LTS installation on ppc64el. * Enable FADump with 1GB: fadump=on crashkernel=1024M * A kernel panic will happen when dump got triggered [Regression Potential] * There is a certain risk of a regression, but it is mapping only the memory allocated for KFENCE pool at page granularity, reducing memory consumption when KFENCE is used. * On top the commit is already upstream reviewed and accepted. * The modifications were done and tested by IBM. * The fadump feature is supported only on IBM POWER systems. [Other] * The fix/commit got upstream accepted with kernel v6.11-rc4, hence Oracular (with a planned kernel of 6.11) is not affected. ... Problem description : == Triggered FADump with the recommended crash. L1 host got hung. As per the public document https://wiki.ubuntu.com/ppc64el/Recommendations recommended crash kernel size is 1024M for the system. But with 1024M and 2048M, the L1 is getting hanged. with 4096, crash is generated and collected. root@ubuntu2404:~# uname -ar Linux ubuntu2404 6.8.0-11-generic #11-Ubuntu SMP Wed Feb 14 00:33:03 UTC 2024 ppc64le ppc64le ppc64le GNU/Linux root@ubuntu2404:~# free -h totalusedfree shared buff/cache available Mem:48Gi 1.7Gi46Gi13Mi 687Mi 46Gi Swap: 8.0Gi 0B 8.0Gi root@ubuntu2404:~# cat /proc/cmdline BOOT_IMAGE=/vmlinux-6.8.0-11-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro fadump=on crashkernel=1024M root@ubuntu2404:~# dmesg | grep -i reser [0.00] fadump: Reserved 1024MB of memory at 0x004000 (System RAM: 51200MB) [0.00] fadump: Initialized 0x4000 bytes cma area at 1024MB from 0x4007 bytes of memory reserved for firmware-assisted dump [0.00] Memory: 49316672K/52428800K available (23616K kernel code, 4096K rwdata, 25536K rodata, 8832K init, 2487K bss, 2063552K reserved, 1048576K cma-reserved) [0.396408] ibmvscsi 3066: Client reserve enabled root@ubuntu2404:~# kdump-config show DUMP_MODE:fadump USE_KDUMP:1 KDUMP_COREDIR:/var/crash /var/lib/kdump/vmlinuz kdump initrd: /var/lib/kdump/initrd.img current state:ready to fadump IBM is looking to update the crash kernel reservations section of the wiki for Power. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/2060039/+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
