AnsweredAssumed Answered

fmc policy with ipv4.ttl value

Question asked by Sedat Altun on Aug 18, 2019
Latest reply on Aug 26, 2019 by Sedat Altun

I am trying to steer the packets received from eth3(fm2-mac10) interface with same ipv4 ttl (time to live) value to a single core by using FMC policies.

My board is T4240RDB with SDK 1.6 components.

 

If I add ipv4.ttl field in my FMC policies I got  core-dump.  But instead of ttl field if I use tos(type of service) there is no error.

 

My policy and core-dump are printed below.

 

POLICY FILE:

 

<?xml version="1.0" encoding="utf-8"?>
<!--
FMAN0/1 FMC policy file

Copyright (C) 2014 Freescale Semiconductor, Inc.

-->
<netpcd xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:noNamespaceSchemaLocation="xmlProject/pcd.xsd" name="example"
         description="FMAN Tester configuration">

      <distribution name="eth3">
                     <queue count="128" base="0x3c80"/>
                     <key>
                           <fieldref name="ipv4.src"/>
                           <fieldref name="ipv4.dst"/>
                           <fieldref name="ipv4.ttl"/>
                     </key>
       </distribution>

 

<distribution name="garbage_dist_eth3">
            <queue count="1" base="0x3c80"/>
</distribution>

 

 

 

      <policy name="fm_policy_eth3">
         <dist_order>
                     <distributionref name="eth3"/>
                     <distributionref name="garbage_dist_eth3"/>
         </dist_order>
      </policy>
</netpcd>

 

CORE_DUMP:

 

ERR : Oops: Kernel access of bad area, sig: 11 [#1]
SMP NR_CPUS=24 Invocation of FMCoreNet Generic
_PCD_KgSchemeSetCPU: 4 PID: 2600 Comm: fmc Tainted: G W 3.12.19-rt30-00066-gcf3b586-dirty #2
tfor fm0/port/10ask: c0000002f9807500 ti: c0000002f6f24000 task.ti: c0000002f6f24000
NIP: c00000000044b614 LR: c00000000044b60c CTR: 0000000000000000
G/1/dist/eth3 faREGS: c0000002f6f27620 TRAP: 0300 Tainted: G W (3.12.19-rt30-00066-gcf3b586-dirty)
MSR: 0000000080029000 iled
<CE,EE,ME> CR: 28000444 XER: 20000000
SOFTE: 1
DEAR: 0000000000006948, ESR: 0000000000000000

GPR00: c00000000044b60c c0000002f6f278a0 c000000000b38740 000000000000002a
GPR04: 0000000000000000 0000000000000000 0000000000000263 0000000000000263
GPR08: 0000000000000001 0000000000000000 0000000000000000 0000000000000262
GPR12: 0000000028000442 c00000000fff5e00 00003ffff740be70 00003ffff740be08
GPR16: 00003ffff740bfd0 000000001015ef50 000000001015dd20 000000001015ee90
GPR20: 000000001015edd8 000000001015ed18 0000000000000001 0000000000000000
GPR24: 000000001015db70 00000000154ed760 000000001015e928 c0000002f5685000
GPR28: 000000002000e15b 0000000000000003 c0000002f7802800 0000000000000000
NIP [c00000000044b614] .FmPcdGetHcHandle+0x70/0x84
LR [c00000000044b60c] .FmPcdGetHcHandle+0x68/0x84
Call Trace:
[c0000002f6f278a0] [c000000000470050] .DetachPCD+0x7c/0x228 (unreliable)
[c0000002f6f27930] [c0000000004808dc] .FM_PORT_DeletePCD+0x318/0x5dc
[c0000002f6f279c0] [c0000000004b3ffc] .LnxwrpFmPortIOCTL+0xd88/0x267c
[c0000002f6f27b70] [c0000000004b5938] .fm_ioctls+0x48/0x130
[c0000002f6f27c00] [c0000000004b5b00] .fm_ioctl+0x58/0x88
[c0000002f6f27ca0] [c000000000122e88] .do_vfs_ioctl+0x3fc/0x6e8
[c0000002f6f27d80] [c0000000001231cc] .SyS_ioctl+0x58/0xa4
[c0000002f6f27e30] [c000000000000598] syscall_exit+0x0/0x8c
Instruction dump:
3ce2ffcb 3c62ffe4 38638808 38a5d420 38c00301 38e74518 4808c7f5 60000000
38600001 4808c7b9 60000000 38210080 <e87f6948> e8010010 ebe1fff8 7c0803a6
---[ end trace ed52d478406a8e91 ]---

Outcomes