------- Comment From [email protected] 2024-03-06 15:22 EDT------- The version of powerpc-utils tested was 1.3.4-0ubuntu2.1 from the -proposed repository.
Much testing was done with adding and removing slots. See logs below: ########## Mar 06 16:58:32 2024 ########## drmgr: -c slot -s U9080.M9S.13072B8-V1-C7 -a -w 3 Validating I/O DLPAR capability...yes. Getting node types 0x00000003 Could not find DRC property group in path: /proc/device-tree/ibm,platform-keystore. Could not find DRC property group in path: /proc/device-tree/memory@0. Could not find DRC property group in path: /proc/device-tree/ibm,platform-facilities. Could not find DRC property group in path: /proc/device-tree/interrupt-controller@0. Could not find DRC property group in path: /proc/device-tree/rtas. Could not find DRC property group in path: /proc/device-tree/ibm,serial. Could not find DRC property group in path: /proc/device-tree/options. Could not find DRC property group in path: /proc/device-tree/openprom. Could not find DRC property group in path: /proc/device-tree/ibm,dynamic-reconfiguration-memory. Could not find DRC property group in path: /proc/device-tree/event-sources. Could not find DRC property group in path: /proc/device-tree/aliases. Could not find DRC property group in path: /proc/device-tree/packages. Could not find DRC property group in path: /proc/device-tree/chosen. Acquiring drc index 0x30000007 get-sensor for 30000007: 0, 2 Setting allocation state to 'alloc usable' Setting indicator state to 'unisolate' Configuring connector for drc index 30000007 Adding device-tree node /proc/device-tree/vdevice/vty-server@30000007 ofdt update: add_node /vdevice/vty-server@30000007 name 11 vty-server Getting node types 0x00000003 performing kernel op for U9080.M9S.13072B8-V1-C7, file is /sys/bus/pci/slots/control/add_slot ########## Mar 06 16:58:33 2024 ########## ########## Mar 06 16:59:07 2024 ########## drmgr: -c slot -s U9080.M9S.13072B8-V1-C7 -r -w 3 Validating I/O DLPAR capability...yes. Getting node types 0x00000003 get-sensor for 30000007: 0, 1 The sensor-state of drc_index 0x30000007 is 1 performing kernel op for U9080.M9S.13072B8-V1-C7, file is /sys/bus/pci/slots/control/remove_slot Releasing drc index 0x30000007 get-sensor for 30000007: 0, 1 Setting isolation state to 'isolate' Setting allocation state to 'alloc unusable' get-sensor for 30000007: 0, 2 drc_index 30000007 sensor-state: 2 Resource is not available to the partition. Removing device-tree node /proc/device-tree/vdevice/vty-server@30000007 ########## Mar 06 16:59:07 2024 ########## Testing was periodically stalled when I did an strace on pvmutil creating a vterm device (e.g. 'pvmutil -o create_vterm_dev --id 3'). mkvterm calls pvmutil. pvmutil is what uses drmgr. There was confusion when the drmgr logs showed drmgr working properly, however an strace showed writing the slot information to .../add_slot was returning -ENODEV. It was determined that this was not an issue with drmgr, as drmgr was writing the correct slot information. Therefore, the conclusion is the version of powerpc-utils in -proposed is working as expected. I am going to open two additional bugs. One for socat, and one for the HVCS and hotplugging issues that will be addressed with kernel commits. Because this bug title only mentions drmgr, we can close this bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2023243 Title: Multiple issues found on Ubuntu 20.04 against drmgr To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/2023243/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
