+++ This bug was initially created as a clone of Bug #2211747 +++ openvswitch-3.1.1-2.fc38.x86_64 crashes at boot with "ovs-vsctl kiled by SIGABRT". I found in the logs: ==================== --giu 01 20:34:15 dave.idp.it ovs-vsctl[2625]: ovs|00001|util|EMER|../lib/cpu.c:40: assertion __get_cpuid_max(leaf & X86_LEAF_MASK, NULL) >= leaf failed in x86_has_isa() giu 01 20:34:16 dave.idp.it ovs-vsctl[2639]: ovs|00001|util|EMER|../lib/cpu.c:40: assertion __get_cpuid_max(leaf & X86_LEAF_MASK, NULL) >= leaf failed in x86_has_isa() -- And I verified (running with qemu) that it is the same problem I have with bash on this specific CPU (Bug 2211733). cpu family : 16 model : 6 model name : AMD Athlon(tm) II X2 280 Processor stepping : 3 Maybe the problem comes from a shared component? Reproducible: Always
* Wed Jun 07 2023 Open vSwitch CI <ovs-ci> - 3.1.0-30 - Merging upstream branch-3.1 [RH git: a29d6e27ae] Commit list: 3fcb817840 cpu: Fix cpuid check for some AMD processors. (#2211747) 01f0668fdf tc: Fix crash on malformed reply from kernel. * Wed Jun 07 2023 Timothy Redaelli <tredaelli> - 3.1.0-29 - redhat: Fix an unwanted change that prevent rh-fail-if-dirty to work [RH git: 9c39a6c81f]
Per discussion with ovs-dev, it is not possible to reproduce or verify this issue on RHEL-9 as it does not support AMD Phenom processor which is a requirement for this issue. No issues observed during regression testing so marking BZ Verified.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (openvswitch3.1 bug fix and enhancement update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2023:3989