I am seeing the same kernel oops with a 3.10 kernel as well. I tried with a 4.0
kernel on EL7 and seems like the issue is fixed.
Do we have a bug id for this issue in the 4.0 dev tree? Also, can someone
confirm that the link Russell posted below is in fact the fix for this kernel
oops?
Thanks,
On 04/20/2015 10:26 AM, Russell Bryant wrote:
> On 04/20/2015 04:35 AM, Thomas Graf wrote:
>> On 04/17/15 at 01:56pm, Russell Bryant wrote:
>>> This is the openvswitch module that came with the following Fedora
>>> kernel: 3.19.1-201.fc21.x86_64
>>>
>>> I can easily reproduce this. It happens when
On 04/20/2015 04:35 AM, Thomas Graf wrote:
> On 04/17/15 at 01:56pm, Russell Bryant wrote:
>> This is the openvswitch module that came with the following Fedora
>> kernel: 3.19.1-201.fc21.x86_64
>>
>> I can easily reproduce this. It happens when running devstack multiple
>> times to stand up OpenS
On 04/17/15 at 01:56pm, Russell Bryant wrote:
> This is the openvswitch module that came with the following Fedora
> kernel: 3.19.1-201.fc21.x86_64
>
> I can easily reproduce this. It happens when running devstack multiple
> times to stand up OpenStack + OVS + OVN + OpenStack Neutron OVN
> integr
I'm seeing a kernel oops while doing some OVN testing.
> [69503.759887] BUG: unable to handle kernel NULL pointer dereference at
> 0048
> [69503.759905] IP: [] ovs_lookup_vport+0x5/0x60
> [openvswitch]
> [69503.759915] PGD 11bc28067 PUD 139bc6067 PMD 0
> [69503.759921] Oops: [#
I'm seeing a kernel oops while doing some OVN testing.
> [69503.759887] BUG: unable to handle kernel NULL pointer dereference at
> 0048
> [69503.759905] IP: [] ovs_lookup_vport+0x5/0x60
> [openvswitch]
> [69503.759915] PGD 11bc28067 PUD 139bc6067 PMD 0
> [69503.759921] Oops: [#