Bug 2211747 - openvswitch 3.1.1: ovs-vsctl kiled by SIGABRT (at boot)
Summary: openvswitch 3.1.1: ovs-vsctl kiled by SIGABRT (at boot)
Alias: None
Product: Fedora
Classification: Fedora
Component: openvswitch
Version: 38
Hardware: Unspecified
OS: Linux
Target Milestone: ---
Assignee: Timothy Redaelli
QA Contact: Fedora Extras Quality Assurance
: 2211733 (view as bug list)
Depends On:
TreeView+ depends on / blocked
Reported: 2023-06-01 19:14 UTC by Davide Repetto
Modified: 2023-06-22 02:25 UTC (History)
3 users (show)

Fixed In Version: openvswitch-3.1.1-3.fc38
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2023-06-22 02:25:30 UTC
Type: ---

Attachments (Terms of Use)

Description Davide Repetto 2023-06-01 19:14:31 UTC
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

Comment 1 Timothy Redaelli 2023-06-05 12:48:55 UTC
The 2 bugs are duplicated, bash prints the x86_has_isa errors due to ovs bash completion that runs ovs-vsctl --commands and ovs-vsctl --options in order to populate the list of commands and options to show when you use autocompletion (tab, etc), so the problem is not in bash at all.

This piece of code was introduced it https://github.com/openvswitch/ovs/commit/b366fa, so reassigning the bugzilla to the original submitter of the patch.

I also suggest to close the bash bug (#2211733) as duplicated of this one, since the problem is not in bash

Comment 2 Davide Repetto 2023-06-05 17:30:52 UTC
*** Bug 2211733 has been marked as a duplicate of this bug. ***

Comment 4 Davide Repetto 2023-06-06 20:52:49 UTC
(In reply to David Marchand from comment #3)
> Could you have a try with rpms freshly built?
> https://kojipkgs.fedoraproject.org//work/tasks/4345/101864345/
> https://kojipkgs.fedoraproject.org//work/tasks/4345/101864345/openvswitch-3.
> 1.1-2.bz2211747.fc38.x86_64.rpm

Yep. The new rpms work well for me.

Comment 5 David Marchand 2023-06-07 08:27:28 UTC
Thanks for confirming.
I posted a fix upstream: https://patchwork.ozlabs.org/project/openvswitch/patch/20230607082440.2847980-1-david.marchand@redhat.com/

Comment 6 David Marchand 2023-06-08 07:11:34 UTC
For the record, a fix has been merged (and backported to stable branches down to 2.17) upstream.

Comment 7 Fedora Update System 2023-06-12 10:16:25 UTC
FEDORA-2023-8c98bd8f83 has been submitted as an update to Fedora 38. https://bodhi.fedoraproject.org/updates/FEDORA-2023-8c98bd8f83

Comment 8 Fedora Update System 2023-06-13 01:42:16 UTC
FEDORA-2023-8c98bd8f83 has been pushed to the Fedora 38 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-8c98bd8f83`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-8c98bd8f83

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 9 Fedora Update System 2023-06-22 02:25:30 UTC
FEDORA-2023-8c98bd8f83 has been pushed to the Fedora 38 stable repository.
If problem still persists, please make note of it in this bug report.

Note You need to log in before you can comment on or make changes to this bug.