OVS/CT kernel stack trace during boot on Jammy OS
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Fix Committed
|
Undecided
|
Unassigned | ||
openvswitch (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Charmed Openstack deployment (Yoga) with Jammy series
(For testing OVN Hardware Offload with Connection Tracking)
# cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_
DISTRIB_
DISTRIB_
root@node3:
Linux node3 5.15.0-35-generic #36-Ubuntu SMP Sat May 21 02:24:07 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
root@node3:
ovs-vsctl (Open vSwitch) 2.17.0
DB Schema 8.3.0
I see the following trace on dmesg every time the server boots up (full trace in the attached file):
[Mon Jun 6 10:51:09 2022] RIP: 0010:__
[Mon Jun 6 10:51:09 2022] Call Trace:
[Mon Jun 6 10:51:09 2022] <TASK>
[Mon Jun 6 10:51:09 2022] ovs_ct_
[Mon Jun 6 10:51:09 2022] do_execute_
[Mon Jun 6 10:51:09 2022] ? __ovs_nla_
[Mon Jun 6 10:51:09 2022] ? __kmalloc+
[Mon Jun 6 10:51:09 2022] ovs_execute_
[Mon Jun 6 10:51:09 2022] ovs_packet_
[Mon Jun 6 10:51:09 2022] genl_family_
[Mon Jun 6 10:51:09 2022] genl_rcv_
[Mon Jun 6 10:51:09 2022] ? ovs_vport_
I see the same trace when deploying OpenStack with Focal series and HWE-Edge kernel...
affects: | ubuntu → openvswitch (Ubuntu) |
Changed in linux (Ubuntu): | |
status: | Confirmed → Fix Committed |
Status changed to 'Confirmed' because the bug affects multiple users.