R28.2 mmcblk0p1 error

Autonomous Machines Jetson & Embedded Systems Jetson TX1
1

Hi,
When testing TX1 platform several days, the system will reboot and not show any crash information.
However, there are some information got from kernel log.

mmc0: Timeout waiting for hardware interrupt.
sdhci: =========== REGISTER DUMP (mmc0)===========
sdhci: Sys addr: 0x80000000 | Version: 0x00000303
sdhci: Blk size: 0x00007200 | Blk cnt: 0x00000000
sdhci: Argument: 0x00c7d4e2 | Trn mode: 0x0000002b
sdhci: Present: 0x01fb00f0 | Host ctl: 0x00000034
sdhci: Power: 0x00000001 | Blk gap: 0x00000000
sdhci: Wake-up: 0x00000000 | Clock: 0x00000007
sdhci: Timeout: 0x0000000e | Int stat: 0x00000000
sdhci: Int enab: 0x02ff000b | Sig enab: 0x02fc000b
sdhci: AC12 err: 0x00000000 | Slot int: 0x00000001
sdhci: Caps: 0x376cd08c | Caps_1: 0x10006f73
sdhci: Cmd: 0x0000193a | Max curr: 0x00000000
sdhci: Host ctl2: 0x0000300d
sdhci: ADMA Err: 0x00000000 | ADMA Ptr: 0x0000000080000010
…snippet…

mmcblk0: timed out sending r/w cmd command, card status 0x900
mmcblk0: not retrying timeout
blk_update_request: I/O error, dev mmcblk0, sector 1309612
blk_update_request: I/O error, dev mmcblk0, sector 1309612
Aborting journal on device mmcblk0p1-8
…snippet…
EXT4-fs error (device mmcblk0p1): ext4_journal_check_start:56: Detected aborted journl
EXT4-fs error (device mmcblk0p1): ext4_journal_check_start:56: Detected aborted journl
EXT4-fs (mmcblk0p1): ext4_writepages: jbd2_start: 13312 pages, ino 263132; err -30
…snippet…
EXT4-fs (mmcblk0p1): error count since last fsck: 2
EXT4-fs (mmcblk0p1): initial error at time 1557581302: ext4_journal_check_start:56
EXT4-fs (mmcblk0p1): last error at time 1557581302: ext4_journal_check_start:56

These log looks like this discussion.

Is it the same issue?
Thanks.

2

Hi,

  1. Please paste the full log.
  2. What is your test case to make this board crash?
  3. Are you using devkit?
4

Hi,

  1. Please paste the full log.
    =>
    loglog.log (113.5 KB)
  2. What is your test case to make this board crash?
    => We use TX1 to connect some peripheral devices and communicate with those devices to get some data then save in file. After UBUNTU system started, the system will print out EXT4 error randomly. However, the system is not crash rapidly. When burn-in over 72 hours, the message (RXData DMA copy to tty layer failed) will go along with EXT4 error. If the system is not crash, the system sometimes becomes read-only file system.
    1
    11920×1080 473 KB
    2
    21920×1080 400 KB
  3. Are you using devkit?
    => no
5

There is no update from you for a period, assuming this is not an issue any more.
Hence we are closing this topic. If need further support, please open a new one.
Thanks

Hi,

Are you able to reproduce this issue on devkit?
Such case seems not common and we may need to reproduce this issue locally.

Also, how frequently is “communicate with those devices to get some data then save in file.” and how large is each file?