• State Resolved
  • Locked Locked
  • Replies 26 replies
  • Subscribers 101 subscribers
  • Views 2528 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

Linux/DRA74: MMC driver crash while flashing

Ishaqe Ahamed
Intellectual 645 points

Part Number: DRA74

Tool/software: Linux

Hi ,

We are  observing Random om omap_hsmmc driver crashes in our system during the system flashing process.

We are using following emmc connected to the DRA6 (Jacinto 6)

Samsung  KLM8G1GESD-B04P 8GB 16 5.1 DE

Have you observed this issue ?

Is there any specific omap hsmmc  driver configuration to support  samsung  KLM8G1GESD-B04P 8GB 16 5.1 DE

rodata/fmdab/21334.png

tar: rodata/fmdab/21334.png: time stamp 2018-07-18 01:49:39 is 1531878254.233206112 s in the future

rodata/fmdab/30979.png

tar: rodata/fmdab/30979.png: time stamp 2018-07-18 01:51:24 is 1531878359.232801309 s in the future

rodata/fmdab/17111.png

tar: rodata/fmdab/17111.png: time stamp 2018-07-18 01:48:55 is 1531878210.232340759 s in the future

rodata/fmdab/21603.png

tar: rodata/fmdab/21603.png: time stamp 2018-07-18 01:49:53 is 1531878268.231586732 s in the future

rodata/fmdab/16213.png

tar: rodata/fmdab/16213.png: time stamp 2018-07-18 01:48:27 is 1531878182.231206329 s in the future

rodata/fmdab/28053.png

tar: rodata/fmdab/28053.png: time stamp 2018-07-18 01:50:50 is 1531878325.230899804 s in the future

rodata/fmdab/35022.png

tar: rodata/fmdab/35022.png: time stamp 2018-07-18 01:51:59 is 1531878394.230169498 s in the future

rodata/fmdab/24708.png

tar: rodata/fmdab/24708.png: time stamp 2018-07-18 01:50:37 is 1531878312.229707593 s in the future

rodata/fmdab/21562.png

tar: rodata/fmdab/21562.png: time stamp 2018-07-18 01:49:51 is 1531878266.226199246 s in the future

rodata/fmdab/61002.png

tar: rodata/fmdab/61002.png: time stamp 2018-07-18 01:52:50 is 1531878445.222613463 s in the future

rodata/fmdab/20244.png

tar: rodata/fmdab/20244.png: time stamp 2018-07-18 01:49:19 is 1531878234.222265763 s in the future

rodata/fmdab/28119.png

tar: rodata/fmdab/28119.png: time stamp 2018-07-18 01:50:53 is 1531878328.221964999 s in the future

rodata/fmdab/10221.png

tar: rodata/fmdab/10221.png: time stamp 2018-07-18 01:47:43 is 1531878138.221623569 s in the future

rodata/fmdab/79045.png

tar: rodata/fmdab/79045.png: time stamp 2018-07-18 01:53:41 is 1531878496.22136093 s in the future

rodata/fmdab/17118.png

tar: rodata/fmdab/17118.png: time stamp 2018-07-18 01:48:55 is 1531878210.22098578 s in the future

rodata/fmdab/30069.png

tar: rodata/fmdab/30069.png: time stamp 2018-07-18 01:51:04 is 1531878339.220600802 s in the future

rodata/fmdab/21590.png

tar: rodata/fmdab/21590.png: time stamp 2018-07-18 01:49:52 is 1531878267.217084322 s in the future

rodata/fmdab/30104.png

tar: rodata/fmdab/30104.png: time stamp 2018-07-18 01:51:05 is 1531878340.216771019 s in the future

rodata/fmdab/30186.png

tar: rodata/fmdab/30186.png: time stamp 2018-07-18 01:51:07 is 1531878342.214013989 s in the future

rodata/fmdab/22011.png

tar: rodata/fmdab/22011.png: time stamp 2018-07-18 01:50:11 is 1531878286.212830081 s in the future

rodata/fmdab/37188.png

tar: rodata/fmdab/37188.png: time stamp 2018-07-18 01:52:10 is 1531878405.21240952 s in the future

rodata/fmdab/31394.png

tar: rodata/fmdab/31394.png: time stamp 2018-07-18 01:51:41 is 1531878376.212016917 s in the future

rodata/fmdab/31578.png

tar: rodata/fmdab/31578.png: time stamp 2018-07-18 01:51:49 is 1531878384.21168972 s in the future

rodata/fmdab/17361.png

tar: rodata/fmdab/17361.png: time stamp 2018-07-18 01:49:04 is 1531878219.211407595 s in the future

rodata/fmdab/54123.png

tar: rodata/fmdab/54123.png: time stamp 2018-07-18 01:52:29 is 1531878424.211065487 s in the future

rodata/fmdab/24047.png

tar: rodata/fmdab/24047.png: time stamp 2018-07-18 01:50:15 is 1531878290.210620526 s in the future

rodata/fmdab/60048.png

tar: rodata/fmdab/60048.png: time stamp 2018-07-18 01:52:43 is 1531878438.210262828 s in the future

rodata/fmdab/31125.png

tar: rodata/fmdab/31125.png: time stamp 2018-07-18 01:51:30 is 1531878365.19962731 s in the future

rodata/fmdab/21580.png

tar: rodata/fmdab/21580.png: time stamp 2018-07-18 01:49:52 is 1531878267.199185399 s in the future

rodata/fmdab/15034.png

tar: rodata/fmdab/15034.png: time stamp 2018-07-18 01:48:10 is 1531878165.198859896 s in the future

rodata/fmdab/16559.png

tar: rodata/fmdab/16559.png: time stamp 2018-07-18 01:48:45 is 1531878200.198561166 s in the future

rodata/fmdab/30108.png

tar: rodata/fmdab/30108.png: time stamp 2018-07-18 01:51:05 is 1531878340.198096041 s in the future

rodata/fmdab/21383.png

tar: rodata/fmdab/21383.png: time stamp 2018-07-18 01:49:42 is 1531878257.197709199 s in the future

rodata/fmdab/10090.png

tar: rodata/fmdab/10090.png: time stamp 2018-07-18 01:47:37 is 1531878131.864397272 s in the future

rodata/fmdab/80138.png

tar: rodata/fmdab/80138.png: time stamp 2018-07-18 01:53:49 is 1531878503.864052114 s in the future

rodata/fmdab/13082.png

tar: rodata/fmdab/13082.png: time stamp 2018-07-18 01:48:01 is 1531878155.86377575 s in the future

rodata/fmdab/24126.png

tar: rodata/fmdab/24126.png: time stamp 2018-07-18 01:50:18 is 1531878292.863406192 s in the future

rodata/fmdab/31614.png

tar: rodata/fmdab/31614.png: time stamp 2018-07-18 01:51:51 is 1531878385.863087467 s in the future

rodata/fmdab/17141.png

tar: rodata/fmdab/17141.png: time stamp 2018-07-18 01:48:56 is 1531878210.862823134 s in the future

rodata/fmdab/68164.png

tar: rodata/fmdab/68164.png: time stamp 2018-07-18 01:53:08 is 1531878462.862449509 s in the future

rodata/fmdab/13010.png

tar: rodata/fmdab/13010.png: time stamp 2018-07-18 01:47:57 is 1531878151.862131462 s in the future

rodata/fmdab/31442.png

tar: rodata/fmdab/31442.png: time stamp 2018-07-18 01:51:43 is 1531878377.861610928 s in the future

rodata/fmdab/21443.png

tar: rodata/fmdab/21443.png: time stamp 2018-07-18 01:49:45 is 1531878259.861191553 s in the future

rodata/fmdab/68177.png

tar: rodata/fmdab/68177.png: time stamp 2018-07-18 01:53:08 is 1531878462.860863339 s in the future

rodata/fmdab/21622.png

tar: rodata/fmdab/21622.png: time stamp 2018-07-18 01:49:54 is 1531878268.860511912 s in the future

rodata/fmdab/31251.png

tar: rodata/fmdab/31251.png: time stamp 2018-07-18 01:51:35 is 1531878369.860206573 s in the future

rodata/fmdab/68190.png

tar: rodata/fmdab/68190.png: time stamp 2018-07-18 01:53:09 is 1531878463.859747209 s in the future

rodata/fmdab/10023.png

tar: rodata/fmdab/10023.png: time stamp 2018-07-18 01:47:34 is 1531878128.85936579 s in the future

rodata/fmdab/50067.png

tar: rodata/fmdab/50067.png: time stamp 2018-07-18 01:52:19 is 1531878413.858982337 s in the future

rodata/fmdab/21531.png

tar: rodata/fmdab/21531.png: time stamp 2018-07-18 01:49:50 is 1531878264.858602104 s in the future

rodata/fmdab/77091.png

tar: rodata/fmdab/77091.png: time stamp 2018-07-18 01:53:34 is 1531878488.858281345 s in the future

rodata/fmdab/17230.png

tar: rodata/fmdab/17230.png: time stamp 2018-07-18 01:48:59 is 1531878213.857953131 s in the future

rodata/fmdab/31027.png

tar: rodata/fmdab/31027.png: time stamp 2018-07-18 01:51:26 is 1531878360.857575779 s in the future

rodata/fmdab/16569.png

tar: rodata/fmdab/16569.png: time stamp 2018-07-18 01:48:45 is 1531878199.857200629 s in the future

rodata/fmdab/27132.png

tar: rodata/fmdab/27132.png: time stamp 2018-07-18 01:50:44 is 1531878318.856854454 s in the future

rodata/fmdab/21920.png

tar: rodata/fmdab/21920.png: time stamp 2018-07-18 01:50:08 is 1531878282.856581818 s in the future

rodata/fmdab/86114.png

tar: rodata/fmdab/86114.png: time stamp 2018-07-18 01:54:06 is 1531878520.856210904 s in the future

rodata/fmdab/20060.png

tar: rodata/fmdab/20060.png: time stamp 2018-07-18 01:49:14 is 1531878228.855844734 s in the future

rodata/fmdab/79001.png

tar: rodata/fmdab/79001.png: time stamp 2018-07-18 01:53:38 is 1531878492.855512454 s in the future

rodata/fmdab/24711.png

tar: rodata/fmdab/24711.png: time stamp 2018-07-18 01:50:37 is 1531878311.855215926 s in the future

rodata/fmdab/28151.png

tar: rodata/fmdab/28151.png: time stamp 2018-07-18 01:50:55 is 1531878329.853655343 s in the future

rodata/fmdab/21877.png

tar: rodata/fmdab/21877.png: time stamp 2018-07-18 01:50:06 is 1531878280.851246182 s in the future

rodata/fmdab/28123.png

tar: rodata/fmdab/28123.png: time stamp 2018-07-18 01:50:54 is 1531878328.850813252 s in the future

rodata/fmdab/31363.png

tar: rodata/fmdab/31363.png: time stamp 2018-07-18 01:51:40 is 1531878374.849698138 s i[  325.766605] Unable to handle kernel paging request at virtual address f1a12002

n the future

rodata/fmdab/24060.png

tar: rodata/fmdab/24060.pn[  325.779366] pgd = c0004000

g: time stamp 2018-07-18 01:50:16 is 1531878290.84639431 s in th[  325.787584] [f1a12002] *pgd=aebeb811e future

rodata/fmdab/80095.png

tar: rodata/fmdab/80095.png: t, *pte=00000000ime stamp 2018-07-18 01:53:47 is 1531878501.508903037 s in the f, *ppte=00000000uture

rodata/fmdab/65000.png

 

[  325.813358] Internal error: Oops: 807 [#1] PREEMPT SMP ARM

[  325.818873] Modules linked in: texfat(PO) tntfs(PO)

[  325.823816] CPU: 1 PID: 821 Comm: mmcqd/0 Tainted: P           O    4.4.84 #Rel_Elina_J6_MMT_18252A_C0

[  325.833166] Hardware name: Generic DRA74X (Flattened Device Tree)

[  325.839290] task: ee9f6d00 ti: eebc4000 task.ti: eebc4000

[  325.844721] PC is at omap_hsmmc_request+0xec/0x648

[  325.849537] LR is at omap_hsmmc_request+0x128/0x648

[  325.854441] pc : [<c0557efc>]    lr : [<c0557f38>]    psr: 800b0013

[  325.854441] sp : eebc5d70  ip : eebc5d70  fp : eebc5dd4

[  325.865971] r10: eeb12000  r9 : f1a11000  r8 : 00000200

[  325.871221] r7 : 910b6800  r6 : 00000400  r5 : f1a12000  r4 : ef170400

[  325.877779] r3 : 00000000  r2 : 000003d5  r1 : 009b650c  r0 : eeb12000

[  325.884339] Flags: Nzcv  IRQs on  FIQs on  Mode SVC_32  ISA ARM  Segment none

[  325.891509] Control: 10c5387d  Table: 85f8006a  DAC: 00000051

[  325.897283] Process mmcqd/0 (pid: 821, stack limit = 0xeebc4218)

[  325.903318] Stack: (0xeebc5d70 to 0xeebc6000)

[  325.907699] 5d60:                                     ef2c9610 000003d4 ef170834 ef1706c0

[  325.915918] 5d80: c001e7e8 c0379448 00000001 00000000 eeb10000 000003d5 00000001 c001e754

[  325.924136] 5da0: ef1708f8 ef17074c c1ed147c ef170834 ef170400 ef170834 ef170834 ef170940

[  325.932355] 5dc0: eebc5ea4 ef170830 eebc5df4 eebc5dd8 c053f5a4 c0557e1c ef170834 ef170400

[  325.940573] 5de0: c1f48ef8 ef170834 eebc5e24 eebc5df8 c053f784 c053f560 eebc5ea4 ef170830

[  325.948791] 5e00: eebc5e24 eebc5e10 c0557064 ef170400 cff7bc48 00000000 eebc5e74 eebc5e28

[  325.957009] 5e20: c0540dec c053f640 00000000 c0550758 eebc5e74 eebc5e40 c0550758 c0553b50

[  325.965227] 5e40: 00000000 ef170800 c0450aac ef170834 cff7bc48 ef170808 ee9ca800 ef170800

[  325.973445] 5e60: 00000000 ef170830 eebc5ed4 eebc5e78 c05508b4 c0540b60 ee9ca86c 00000000

[  325.981663] 5e80: ee9f6d00 c00615c0 00000000 00000000 00000000 ef170800 00000000 cff7bc48

[  325.989880] 5ea0: ef170800 eebc4000 00000001 ef170808 ee9ca800 00000000 ef170800 ef170800

[  325.998098] 5ec0: 00000001 cff7bc48 eebc5f24 eebc5ed8 c0551518 c0550800 cff7bc48 ef170810

[  326.006316] 5ee0: 00000000 eeb4bad8 eebc5f0c eebc5ef8 ef170400 24590411 cff7bc48 ef170808

[  326.014534] 5f00: 24590411 00000000 eeb4bad8 eebc4000 00000001 00000000 eebc5f5c eebc5f28

[  326.022752] 5f20: c0552f90 c05512bc c0552ed0 ef170810 00000000 00000000 eeae6a00 ef170808

[  326.030970] 5f40: c0552ed0 00000000 00000000 00000000 eebc5fac eebc5f60 c0056c7c c0552edc

[  326.039188] 5f60: eebc5f8c 00000000 c003a874 ef170808 00000000 00000000 eebc5f78 eebc5f78

[  326.047406] 5f80: 00000000 00000000 eebc5f88 eebc5f88 eeae6a00 c0056b7c 00000000 00000000

[  326.055624] 5fa0: 00000000 eebc5fb0 c0010b58 c0056b88 00000000 00000000 00000000 00000000

[  326.063841] 5fc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000

[  326.072060] 5fe0: 00000000 00000000 00000000 00000000 00000013 00000000 c46f5cfd 22db0bc6

[  326.080273] Backtrace:

[  326.082752] [<c0557e10>] (omap_hsmmc_request) from [<c053f5a4>] (__mmc_start_request+0x50/0xe0)

[  326.091491]  r10:ef170830 r9:eebc5ea4 r8:ef170940 r7:ef170834 r6:ef170834 r5:ef170400

[  326.099423]  r4:ef170834

[  326.101985] [<c053f554>] (__mmc_start_request) from [<c053f784>] (mmc_start_request+0x150/0x28c)

[  326.110811]  r7:ef170834 r6:c1f48ef8 r5:ef170400 r4:ef170834

[  326.116553] [<c053f634>] (mmc_start_request) from [<c0540dec>] (mmc_start_req+0x298/0x3e0)

[  326.124856]  r6:00000000 r5:cff7bc48 r4:ef170400

[  326.129540] [<c0540b54>] (mmc_start_req) from [<c05508b4>] (mmc_blk_issue_rw_rq+0xc0/0xabc)

[  326.137930]  r10:ef170830 r9:00000000 r8:ef170800 r7:ee9ca800 r6:ef170808 r5:cff7bc48

[  326.145857]  r4:ef170834

[  326.148420] [<c05507f4>] (mmc_blk_issue_rw_rq) from [<c0551518>] (mmc_blk_issue_rq+0x268/0x4f4)

[  326.157156]  r10:cff7bc48 r9:00000001 r8:ef170800 r7:ef170800 r6:00000000 r5:ee9ca800

[  326.165082]  r4:ef170808

[  326.167646] [<c05512b0>] (mmc_blk_issue_rq) from [<c0552f90>] (mmc_queue_thread+0xc0/0x190)

[  326.176034]  r10:00000000 r9:00000001 r8:eebc4000 r7:eeb4bad8 r6:00000000 r5:24590411

[  326.183960]  r4:ef170808

[  326.186524] [<c0552ed0>] (mmc_queue_thread) from [<c0056c7c>] (kthread+0x100/0x11c)

[  326.194215]  r10:00000000 r9:00000000 r8:00000000 r7:c0552ed0 r6:ef170808 r5:eeae6a00

[  326.202142]  r4:00000000

[  326.204706] [<c0056b7c>] (kthread) from [<c0010b58>] (ret_from_fork+0x14/0x3c)

[  326.211961]  r7:00000000 r6:00000000 r5:c0056b7c r4:eeae6a00

[  326.217700] Code: e1a0a002 ea000016 e6ff6076 e3a03000 (e5c56002)

[  326.224248] systemd[1]: nodestatemanager.service: Got notification message from PID 973 (WATCHDOG=1)

[  326.236251] ---[ end trace 63aef0365dbbb347 ]---

[  326.245813] Kernel panic - not syncing: Fatal exception

[  326.251068] CPU0: stopping

[  326.253797] CPU: 0 PID: 0 Comm: swapper/0 Tainted: P      D    O    4.4.84 #Rel_Elina_J6_MMT_18252A_C0

[  326.263145] Hardware name: Generic DRA74X (Flattened Device Tree)

[  326.269266] Backtrace:

[  326.271741] [<c0015410>] (dump_backtrace) from [<c001565c>] (show_stack+0x20/0x24)

[  326.279344]  r7:c1f0f530 r6:20030193 r5:ffffffff r4:00000000

[  326.285086] [<c001563c>] (show_stack) from [<c036a25c>] (dump_stack+0x8c/0xa8)

[  326.292347] [<c036a1d0>] (dump_stack) from [<c00178f0>] (handle_IPI+0x320/0x360)

[  326.299775]  r9:c1ecbf08 r8:00000000 r7:00000000 r6:c1ec5510 r5:c1ec5510 r4:00000005

[  326.307616] [<c00175d0>] (handle_IPI) from [<c00095a0>] (gic_handle_irq+0x84/0x8c)

[  326.315219]  r9:fa213000 r8:00000000 r7:fa212000 r6:c1ecd054 r5:c1ecbf08 r4:fa21200c

[  326.323062] [<c000951c>] (gic_handle_irq) from [<c06908f4>] (__irq_svc+0x54/0x90)

[  326.330579] Exception stack(0xc1ecbf08 to 0xc1ecbf50)

[  326.335657] bf00:                   00000000 00325fc8 00000000 fe600000 c1eca000 c1ecc544

[  326.343874] bf20: 00000001 c0698174 c1f33f78 c1ec3404 c095ea28 c1ecbf64 c1ecbf44 c1ecbf58

[  326.352088] bf40: c002ac78 c00115fc 60030013 ffffffff

[  326.357162]  r9:c1ec3404 r8:c1f33f78 r7:c1ecbf3c r6:ffffffff r5:60030013 r4:c00115fc

[  326.365005] [<c00115d0>] (arch_cpu_idle) from [<c007965c>] (default_idle_call+0x30/0x3c)

[  326.373138] [<c007962c>] (default_idle_call) from [<c00798d0>] (cpu_startup_entry+0x268/0x308)

[  326.381796] [<c0079668>] (cpu_startup_entry) from [<c0689910>] (rest_init+0x84/0x9c)

[  326.389573]  r7:c1ecc440

[  326.392135] [<c068988c>] (rest_init) from [<c0916cd8>] (start_kernel+0x354/0x3c8)

[  326.399650]  r5:ffffffff r4:c1f4c040

[  326.403268] [<c0916984>] (start_kernel) from [<8000807c>] (0x8000807c)

[  326.422719] Rebooting in 1 seconds..

[  327.426257] Elina Reboot in progress...

  • 0
    TI__Mastermind 33050 points
    Hi,

    There are no additional configs needed for different eMMC cards.
    The logs you are showing are Kernel crash logs. Are you trying to flash after Kernel has booted?

    What mode are you configuring the eMMC (HS200, DDR50, etc..)?

    Regards,
    Vishal
  • 0 in reply to Vishal Mahaveer
    Intellectual 645 points
    It is based on PROCESSOR-SDK-LINUX-AUTOMOTIVE 03_03
  • 0 in reply to Ishaqe Ahamed
    TI__Mastermind 33050 points
    Could you provide more details on the error/crash scenario?
  • 0 in reply to Vishal Mahaveer
    Intellectual 645 points
    Yes ..
    We are in booted into initramfs and flashing the file system after kernel booted up

    Here is the DTB configuration.

    mmc@480b4000 {
    compatible = "ti,dra7-hsmmc", "ti,omap4-hsmmc";
    reg = <0x480b4000 0x400>;
    interrupts = <0x0 0x51 0x4>;
    ti,hwmods = "mmc2";
    ti,needs-special-reset;
    dmas = <0xc6 0x2f 0xc6 0x30>;
    dma-names = "tx", "rx";
    status = "okay";
    sd-uhs-sdr25;
    sd-uhs-sdr12;
    mmc-hs200-1_8v;
    mmc-ddr-1_8v;
    vmmc-supply = <0xc7>;
    bus-width = <0x8>;
    pbias_setup;
    ti,non-removable;
    max-frequency = <0xb71b000>;
    };
  • 0 in reply to Ishaqe Ahamed
    Intellectual 645 points
    it is not always seen issues, but seen sometimes
  • 0 in reply to Ishaqe Ahamed
    TI__Mastermind 33050 points
    Could you share the final dtb that gets generated?
  • 0 in reply to Vishal Mahaveer
    Intellectual 645 points
    the above share one is generated out of dtb converted to dts .
    Do you need any specific dtb node information ?
  • 0 in reply to Ishaqe Ahamed
    TI__Mastermind 33050 points
    That doesn't look like complete for mmc2.
    Are you not configuring IODELAY values? Like in TI EVM reference dra7xx-evm.dts?
  • 0 in reply to Vishal Mahaveer
    TI__Mastermind 33050 points
    Also, share the full Kernel log when the issue happens.
  • 0 in reply to Vishal Mahaveer
    Intellectual 645 points

    logs_emmc_failure.txt
    Fullscreen
    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    13
    14
    15
    16
    17
    18
    19
    20
    21
    22
    23
    24
    25
    26
    27
    28
    29
    30
    31
    32
    33
    34
    35
    36
    37
    38
    39
    40
    41
    42
    43
    44
    45
    46
    47
    48
    49
    50
    51
    52
    53
    54
    55
    56
    57
    58
    59
    60
    61
    62
    63
    64
    65
    66
    67
    rodata/fmdab/31049.png
    tar: rodata/fmdab/31049.png: time stamp 2018-07-18 01:51:27 is 1531878362.914950847 s in the future
    rodata/fmdab/21315.png
    tar: rodata/fmdab/21315.png: time stamp 2018-07-18 01:49:38 is 1531878253.91451385 s in the future
    rodata/fmdab/30187.png
    tar: rodata/fmdab/30187.png: time stamp 2018-07-18 01:51:07 is 1531878342.580095621 s in the future
    rodata/fmdab/10458.png
    tar: rodata/fmdab/10458.png: time stamp 2018-07-18 01:47:55 is 1531878150.579698443 s in the future
    rodata/fmdab/31342.png
    tar: rodata/fmdab/31342.png: time stamp 2018-07-18 01:51:39 is 1531878374.579296351 s in the future
    rodata/fmdab/24472.png
    tar: rodata/fmdab/24472.png: time stamp 2018-07-18 01:50:30 is 1531878305.578953904 s in the future
    rodata/fmdab/50072.png
    tar: rodata/fmdab/50072.png: time stamp 2018-07-18 01:52:19 is 1531878414.578605188 s in the future
    rodata/fmdab/28037.png
    tar: rodata/fmdab/28037.png: time stamp 2018-07-18 01:50:49 is 1531878324.578310863 s in the future
    rodata/fmdab/17097.png
    tar: rodata/fmdab/17097.png: time stamp 2018-07-18 01:48:54 is 1531878209.577832352 s in the future
    rodata/fmdab/80012.png
    tar: rodata/fmdab/80012.png: time stamp 2018-07-18 01:53:42 is 1531878497.577459913 s in the future
    rodata/fmdab/30801.png
    tar: rodata/fmdab/30801.png: time stamp 2018-07-18 01:51:17 is 1531878352.57701546 s in the future
    rodata/fmdab/51031.png
    tar: rodata/fmdab/51031.png: time stamp 2018-07-18 01:52:22 is 1531878417.576709782 s in the future
    rodata/fmdab/51033.png
    tar: rodata/fmdab/51033.png: time stamp 2018-07-18 01:52:22 is 1531878417.576407663 s in the future
    rodata/fmdab/31340.png
    tar: rodata/fmdab/31340.png: time stamp 2018-07-18 01:51:39 is 1531878374.575923052 s in the future
    rodata/fmdab/21854.png
    tar: rodata/fmdab/21854.png: time stamp 2018-07-18 01:50:05 is 1531878280.575407941 s in the future
    rodata/fmdab/28112.png
    tar: rodata/fmdab/28112.png: time stamp 2018-07-18 01:50:53 is 1531878328.575075999 s in the future
    rodata/fmdab/20226.png
    tar: rodata/fmdab/20226.png: time stamp 2018-07-18 01:49:19 is 1531878234.574763205 s in the future
    rodata/fmdab/16549.png
    tar: rodata/fmdab/16549.png: time stamp 2018-07-18 01:48:44 is 1531878199.574155069 s in the future
    rodata/fmdab/39003.png
    tar: rodata/fmdab/39003.png: time stamp 2018-07-18 01:52:14 is 1531878409.573748402 s in the future
    rodata/fmdab/30876.png
    tar: rodata/fmdab/30876.png: time stamp 2018-07-18 01:51:20 is 1531878355.573013691 s in the future
    rodata/fmdab/31184.png
    tar: rodata/fmdab/31184.png: time stamp 2018-07-18 01:51:32 is 1531878367.572456049 s in the future
    rodata/fmdab/10082.png
    tar: rodata/fmdab/10082.png: time stamp 2018-07-18 01:47:36 is 1531878131.571813177 s in the future
    rodata/fmdab/31629.png
    tar: rodata/fmdab/31629.png: time stamp 2018-07-18 01:51:52 is 1531878387.571548505 s in the future
    rodata/fmdab/13090.png
    tar: rodata/fmdab/13090.png: time stamp 2018-07-18 01:48:01 is 1531878156.571241811 s in the future
    rodata/fmdab/17267.png
    tar: rodata/fmdab/17267.png: time stamp 2018-07-18 01:49:00 is 1531878215.570936641 s in the future
    rodata/fmdab/30204.png
    tar: rodata/fmdab/30204.png: time stamp 2018-07-18 01:51:07 is 1531878342.570640791 s in the future
    rodata/fmdab/68025.png
    tar: rodata/fmdab/68025.png: time stamp 2018-07-18 01:53:01 is 1531878456.570303936 s in the future
    rodata/fmdab/80093.png
    tar: rodata/fmdab/80093.png: time stamp 2018-07-18 01:53:47 is 1531878502.569737144 s in the future
    rodata/fmdab/30667.png
    tar: rodata/fmdab/30667.png: time stamp 2018-07-18 01:51:15 is 1531878350.569383683 s in the future
    rodata/fmdab/16155.png
    tar: rodata/fmdab/16155.png: time stamp 2018-07-18 01:48:24 is 1531878179.568941433 s in the future
    rodata/fmdab/60103.png
    tar: rodata/fmdab/60103.png: time stamp 2018-07-18 01:52:46 is 1531878441.568514941 s in the future
    rodata/fmdab/24624.png
    tar: rodata/fmdab/24624.png: time stamp 2018-07-18 01:50:35 is 1531878310.56550832 s in the future
    rodata/fmdab/54011.png
    tar: rodata/fmdab/54011.png: time stamp 2018-07-18 01:52:23 is 1531878418.565106567 s in the future
    rodata/fmdab/70039.png
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

  • 0 in reply to Ishaqe Ahamed
    Intellectual 450 points

    fs-corruption-tundb-flash.txtVishal, Ishaqe, Complete kernel logs are attached here.

  • 0 in reply to Pradeep G
    TI__Mastermind 33050 points
    Hi Pradeep,

    According to the log, eMMC is coming up in HS200 mode and you also have a SD card and Wi-Fi card connected to different MMC interface.
    The crash happens when you are trying to flash data from SD card to one of the eMMC partitions, is this statement correct?

    The dts shared earlier was incomplete, could you share the final generated dtb or dts?

    Regards,
    Vishal
  • 0 in reply to Ishaqe Ahamed
    TI__Mastermind 33050 points

    -1-

    IODELAY configurations are missing for MMC, could you guys add it. ANy reason why these were not taken.
    Reference from TI EVM  - http://git.omapzoom.org/?p=kernel/omap.git;a=blob;f=arch/arm/boot/dts/dra7-evm.dts;h=aee34b6d45c1a5c28e9b2c090008c270bee50dc6;hb=9906a0f58aa1e80d22b3fc1f73cf334681028617#l879

    -2-

    Are there any erase operations in your flashing script? If yes, could you try the below patch?
    http://review.omapzoom.org/#/c/38932

    -3-

    If the above patch doesn't help, could you try reproducing the issue with CONFIG_MMC_DEBUG option enabled in Kernel?
    Disable Wi-Fi to prevent logs from that instance of MMC.


    Regards,
    Vishal

  • 0 in reply to Vishal Mahaveer
    Intellectual 645 points

    The IODelay configuration are done from the bootloader in our cases.

    It is found to be correct 

  • 0 in reply to Ishaqe Ahamed
    Intellectual 645 points
    IS there any specific eMMC cache settings we can modify in the omap hsmmc Driver
  • 0 in reply to Ishaqe Ahamed
    TI__Mastermind 33050 points

    Ishaqe Ahamed said:
    IS there any specific eMMC cache settings we can modify in the omap hsmmc Driver

    I need to check on this, I don't know if there are such settings in omap_hsmmc driver.


    Could you try the patch mentioned in point #2 above and if that doesn't help could you reproduce the issue with MMC_DEBUG as suggested  in point #3?

  • 0 in reply to Vishal Mahaveer
    Intellectual 450 points

    Hi Vishal,

    Issue seen with given patch.

    Attached log file with path applied and MMC_DEBUG enabled.mmc_debug_TI-patch.txt

  • 0 in reply to Pradeep G
    TI__Mastermind 33050 points
    Hi Pradeep,

    The debug logs don't have MMC_DEBUG logs.
    Could you try increasing the loglevel of Kernel? Try adding loglevel=9 to Kernel bootargs.

    Regards,
    Vishal
  • 0 in reply to Vishal Mahaveer
    Intellectual 450 points

    Hi Vishal, 

    Attached are the new logs with mmc debug.

    Also attached eMMC extcsd read details.

    Please check and let know the feedack.

    vvk-50mhz-deb.txt

    Samsung-emmc.txt
    Fullscreen
    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    13
    14
    15
    16
    17
    18
    19
    20
    21
    22
    23
    24
    25
    26
    27
    28
    29
    30
    31
    32
    33
    34
    35
    36
    37
    38
    39
    40
    41
    42
    43
    44
    45
    46
    47
    48
    49
    50
    51
    52
    53
    54
    55
    56
    57
    58
    59
    60
    61
    62
    63
    64
    65
    66
    67
    root@emergency-mmt2020-a880:~# mmc extcsd read /dev/mmcblk0
    =============================================
    Extended CSD rev 1.8 (MMC 5.1)
    =============================================
    Card Supported Command sets [S_CMD_SET: 0x01]
    HPI Features [HPI_FEATURE: 0x01]: implementation based on CMD13
    Background operations support [BKOPS_SUPPORT: 0x01]
    Max Packet Read Cmd [MAX_PACKED_READS: 0x3f]
    Max Packet Write Cmd [MAX_PACKED_WRITES: 0x3f]
    Data TAG support [DATA_TAG_SUPPORT: 0x01]
    Data TAG Unit Size [TAG_UNIT_SIZE: 0x02]
    Tag Resources Size [TAG_RES_SIZE: 0x00]
    Context Management Capabilities [CONTEXT_CAPABILITIES: 0x05]
    Large Unit Size [LARGE_UNIT_SIZE_M1: 0x07]
    Extended partition attribute support [EXT_SUPPORT: 0x03]
    Generic CMD6 Timer [GENERIC_CMD6_TIME: 0x0a]
    Power off notification [POWER_OFF_LONG_TIME: 0x3c]
    Cache Size [CACHE_SIZE] is 65536 KiB
    Background operations status [BKOPS_STATUS: 0x00]
    1st Initialisation Time after programmed sector [INI_TIMEOUT_AP: 0x1e]
    Power class for 52MHz, DDR at 3.6V [PWR_CL_DDR_52_360: 0x00]
    Power class for 52MHz, DDR at 1.95V [PWR_CL_DDR_52_195: 0x00]
    Power class for 200MHz at 3.6V [PWR_CL_200_360: 0x00]
    Power class for 200MHz, at 1.95V [PWR_CL_200_195: 0x00]
    Minimum Performance for 8bit at 52MHz in DDR mode:
    [MIN_PERF_DDR_W_8_52: 0x00]
    [MIN_PERF_DDR_R_8_52: 0x00]
    TRIM Multiplier [TRIM_MULT: 0x02]
    Secure Feature support [SEC_FEATURE_SUPPORT: 0x55]
    Boot Information [BOOT_INFO: 0x07]
    Device supports alternative boot method
    Device supports dual data rate during boot
    Device supports high speed timing during boot
    Boot partition size [BOOT_SIZE_MULTI: 0xff]
    Access size [ACC_SIZE: 0x07]
    High-capacity erase unit size [HC_ERASE_GRP_SIZE: 0x01]
    i.e. 512 KiB
    High-capacity erase timeout [ERASE_TIMEOUT_MULT: 0x01]
    Reliable write sector count [REL_WR_SEC_C: 0x01]
    High-capacity W protect group size [HC_WP_GRP_SIZE: 0x10]
    i.e. 8192 KiB
    Sleep current (VCC) [S_C_VCC: 0x07]
    Sleep current (VCCQ) [S_C_VCCQ: 0x07]
    Sleep/awake timeout [S_A_TIMEOUT: 0x11]
    Sector Count [SEC_COUNT: 0x00e90000]
    Device is block-addressed
    Minimum Write Performance for 8bit:
    [MIN_PERF_W_8_52: 0x00]
    [MIN_PERF_R_8_52: 0x00]
    [MIN_PERF_W_8_26_4_52: 0x00]
    [MIN_PERF_R_8_26_4_52: 0x00]
    Minimum Write Performance for 4bit:
    [MIN_PERF_W_4_26: 0x00]
    [MIN_PERF_R_4_26: 0x00]
    Power classes registers:
    [PWR_CL_26_360: 0x00]
    [PWR_CL_52_360: 0x00]
    [PWR_CL_26_195: 0x00]
    [PWR_CL_52_195: 0x00]
    Partition switching timing [PARTITION_SWITCH_TIME: 0x01]
    Out-of-interrupt busy timing [OUT_OF_INTERRUPT_TIME: 0x02]
    I/O Driver Strength [DRIVER_STRENGTH: 0x1f]
    Card Type [CARD_TYPE: 0x57]
    HS200 Single Data Rate eMMC @200MHz 1.8VI/O
    HS Dual Data Rate eMMC @52MHz 1.8V or 3VI/O
    HS eMMC @52MHz - at rated device voltage(s)
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

  • 0 in reply to Pradeep G
    TI__Mastermind 33050 points
    Hi Pradeep,

    Thanks for the logs.

    It was mentioned that this issue is seen sometimes. Do you know how many boards exhibit this behavior?
    Also, do you know what was the operating conditions at time of error.

    Regards,
    Vishal
  • 0 in reply to Vishal Mahaveer
    Intellectual 645 points

    HI could you please let us know the recommended value for max_segs ?

    what is the impact if we reduce the value to half ?

    if (host->pdata->controller_flags & OMAP_HSMMC_HAS_HWPARAM) {
    val = OMAP_HSMMC_READ(base, HL_HWINFO);
    if (val & MADMA_EN)
    host->use_adma = true;
    }

    /* Since we do only SG emulation, we can have as many segs
    * as we want. */
    mmc->max_segs = 1024;

    mmc->max_blk_size = 512; /* Block Length at max can be 1024 */
    mmc->max_blk_count = 0xFFFF; /* No. of Blocks is 16 bits */
    mmc->max_req_size = mmc->max_blk_size * mmc->max_blk_count;

  • 0 in reply to Ishaqe Ahamed
    TI__Mastermind 33050 points

    Hi,

    Let me get back to you on the question about max_segs.

    Could you answer the previous questions on how many boards and operating condition of the board where the MMC crash is seen while flashing?

    Regards,
    Vishal

  • 0 in reply to Ishaqe Ahamed
    TI__Mastermind 33050 points
    Regarding max_segs:

    Changing max_segs might have throughput impact. It should neither be too large nor too small. Having 1024 (sg entries) has worked well for us so far in omap_hsmmc

    You can reduce it to half if you want, but do enough testing to make sure the change does not have adverse effect on you throughput.
  • 0 in reply to Vishal Mahaveer
    TI__Mastermind 33050 points
    Hi,

    Any update on previous questions.
    If the issue is resolved, please mark it as resolved.