This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

TDA4VM: SDK of V7.0 Linux Kernel Error

Part Number: TDA4VM

Hi experts,

When i start the Linux system by SDK V7.0, i got some error message shown blew:

[ 0.000000] Reserved memory: created DMA memory pool at 0x00000000fb000000, size 1 MiB
[ 0.000000] OF: reserved mem: initialized node r5f-dma-memory@fb000000, compatible id shared-dma-pool
[ 0.000000] Reserved memory: created DMA memory pool at 0x00000000fb100000, size 15 MiB
[ 0.000000] OF: reserved mem: initialized node r5f-memory@fb100000, compatible id shared-dma-pool
[ 0.000000] cma: Failed to reserve 512 MiB

...

[ 0.622400] debugfs: Directory '31010000.pat' with parent 'regmap' already present!
[ 0.630377] ti-pat 31011000.pat: Found PAT Rev 1.0 with 16384 pages
[ 0.636788] debugfs: Directory '31011000.pat' with parent 'regmap' already present!
[ 0.644710] ti-pat 31012000.pat: Found PAT Rev 1.0 with 16384 pages
[ 0.651120] debugfs: Directory '31012000.pat' with parent 'regmap' already present!
[ 0.659038] ti-pat 31013000.pat: Found PAT Rev 1.0 with 2048 pages
[ 0.665361] debugfs: Directory '31013000.pat' with parent 'regmap' already present!
[ 0.673277] ti-pat 31014000.pat: Found PAT Rev 1.0 with 2048 pages
[ 0.679598] debugfs: Directory '31014000.pat' with parent 'regmap' already present!
[ 0.688839] Serial: 8250/16550 driver, 10 ports, IRQ sharing enabled
[ 0.700280] brd: module loaded
[ 0.706318] loop: module loaded
[ 0.709838] sysfs: cannot create duplicate filename '/devices/platform/dma_buf_phys'
[ 0.717767] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 5.4.40-g66cf445b76 #1
[ 0.724876] Hardware name: Texas Instruments K3 J721E SoC (DT)
[ 0.730830] Call trace:
[ 0.733327] dump_backtrace+0x0/0x140
[ 0.737062] show_stack+0x14/0x20
[ 0.740447] dump_stack+0xb4/0xf8
[ 0.743832] sysfs_warn_dup+0x5c/0x78
[ 0.747566] sysfs_create_dir_ns+0xd8/0xf0
[ 0.751746] kobject_add_internal+0x94/0x280
[ 0.756101] kobject_add+0x90/0xf8
[ 0.759571] device_add+0xdc/0x600
[ 0.763039] platform_device_add+0xfc/0x228
[ 0.767306] platform_device_register_full+0xc8/0x140
[ 0.772464] dma_buf_phys_init+0x68/0x94
[ 0.776465] do_one_initcall+0x50/0x190
[ 0.780379] kernel_init_freeable+0x194/0x22c
[ 0.784824] kernel_init+0x10/0xfc
[ 0.788292] ret_from_fork+0x10/0x18
[ 0.791948] kobject_add_internal failed for dma_buf_phys with -EEXIST, don't try to register things with the same name in the same directory.

Could you help me to solve this issue?

Thanks,

Hutian

  • Hi Hutian,

    Please answer the following questions:

    1) Is this you custom board?
    2) Are you using PSDKLA 7.0?
    3) Do you have any code modifications on top of PSDKLA 7.0?

    Best Regards,
    Keerthy

  • Hi Hutian,

    I see them on PSDKRA 7.0 but they have no functionality impact as
    they both are more of warnings that come due to duplication.

    "cma: Failed to reserve 512 MiB"

    Just above that we have 720 MiB success.

    Coming to "duplicate filename" this is also harmless. We will get this fixed in the next
    release. Thanks for notifying.

    Let me know if you have any other question.

    Best Regards,
    Keerthy

  • Hi Keerthy,

    Thanks for your information. Could you also check the NFS boot feature, if it is convenient to you? 

    Using the PSDKRA&PSDKLA 7.0 on EVM board, i get the checksum error for NFS boot. The error log is shown below:

     

    [ 16.732163] eth0: hw csum failure
    [ 16.735502] skb len=4252 headroom=78 headlen=1500 tailroom=0
    [ 16.735502] mac=(64,14) net=(78,20) trans=98
    [ 16.735502] shinfo(txflags=0 nr_frags=0 gso(size=0 type=0 segs=0))
    [ 16.735502] csum(0x6e13ea80 ip_summed=2 complete_sw=0 valid=0 level=0)
    [ 16.735502] hash(0x0 sw=0 l4=0) proto=0x0800 pkttype=0 iif=3
    [ 16.763712] dev name=eth0 feat=0x0x0001008000004a09
    [ 16.768587] skb headroom: 00000000: 20 07 00 00 3b 05 00 00 9a 07 00 00 ec 00 00 00
    [ 16.776228] skb headroom: 00000010: 13 05 00 00 00 00 00 00 bd 05 00 00 00 00 00 00

    ....

    Thanks,

    Hutian

  • Hi Hutian,

    Can you resolve this thread and give details about the nfs failure so that can investigated separately?

    Best Regards,
    Keerthy