Getting Below error sometimes.

キャンセル
次の結果を表示 
表示  限定  | 次の代わりに検索 
もしかして: 

Getting Below error sometimes.

68件の閲覧回数
Chidananda22
Contributor IV

 

root@localhost:~# [ 245.838268] fsl_mc_dprc dprc.1 (unnamed net_device) (uninitialized): netif_napi_add() called with weight 512

[ 7165.888548] mmc1: Timeout waiting for hardware cmd interrupt.

[ 7165.894288] mmc1: sdhci: ============ SDHCI REGISTER DUMP ===========

[ 7165.900719] mmc1: sdhci: Sys addr: 0x89280000 | Version: 0x00002202

[ 7165.907148] mmc1: sdhci: Blk size: 0x00000200 | Blk cnt: 0x00000000

[ 7165.913577] mmc1: sdhci: Argument: 0x00010000 | Trn mode: 0x00000033

[ 7165.920006] mmc1: sdhci: Present: 0x01f80008 | Host ctl: 0x0000003c

[ 7165.926434] mmc1: sdhci: Power: 0x00000007 | Blk gap: 0x00000000

[ 7165.932863] mmc1: sdhci: Wake-up: 0x00000000 | Clock: 0x00000208

[ 7165.939291] mmc1: sdhci: Timeout: 0x0000000e | Int stat: 0x00000001

[ 7165.945720] mmc1: sdhci: Int enab: 0x037f100f | Sig enab: 0x037f100b

[ 7165.952148] mmc1: sdhci: ACmd stat: 0x00000000 | Slot int: 0x00002202

[ 7165.958576] mmc1: sdhci: Caps: 0x34fa0000 | Caps_1: 0x0000af00

[ 7165.965004] mmc1: sdhci: Cmd: 0x00000d1a | Max curr: 0x00000000

[ 7165.971432] mmc1: sdhci: Resp[0]: 0x00000900 | Resp[1]: 0xffc0038d

[ 7165.977860] mmc1: sdhci: Resp[2]: 0x328f5903 | Resp[3]: 0x00000900

[ 7165.984288] mmc1: sdhci: Host ctl2: 0x00000080

[ 7165.988720] mmc1: sdhci: ADMA Err: 0x00000000 | ADMA Ptr: 0x00000020826b4218

[ 7165.995842] mmc1: sdhci: ============================================

[ 7169.304212] fsl_mc_dprc dprc.1: Disabling DPRC IRQ failed: dprc_set_irq_enable() failed: -13

[ 7169.319848] fsl_mc_dprc dprc.1: Enabling DPRC IRQ failed: dprc_set_irq_mask() failed: -13

0 件の賞賛
返信
1 返信

51件の閲覧回数
Bio_TICFSL
NXP TechSupport
NXP TechSupport

Hello,

Issue 1: mmc1 Timeout Waiting for Hardware CMD Interrupt

At approximately 7165s uptime, the SDHCI controller on mmc1 timed out waiting for a hardware interrupt following a CMD13 (SEND_STATUS) command. The register dump shows:

  • The card did respond (non-zero Resp registers), so the card itself appears healthy.

  • Host ctl2: 0x00000080 confirms the controller is running in HS400 mode.

  • The interrupt complete bit was set (Int stat: 0x00000001), but the interrupt was never delivered to the CPU.

This pattern is consistent with either an IRQ delivery failure under heavy system load, or a known eSDHC interrupt issue in certain LSDK versions (related to QLINUX-6595).

Issue 2: DPRC IRQ Configuration Failures (-EACCES)

Shortly after the MMC timeout, the DPRC driver reported:

  • Disabling DPRC IRQ failed: dprc_set_irq_enable() failed: -13

  • Enabling DPRC IRQ failed: dprc_set_irq_mask() failed: -13

Error -13 is -EACCES (Permission Denied), which indicates the MC firmware rejected the IRQ configuration request. This is likely a downstream effect of the system stall caused by the MMC timeout disrupting the MC portal communication.

Suggested Next Steps

  1. Confirm LSDK/kernel version and check if QLINUX-6595 fixes are included.

  2. Consider disabling HS400 mode (no-mmc-hs400 in the device tree) to reduce eMMC instability under load.

  3. Verify the DPL includes DPRC_CFG_OPT_IRQ_CFG_ALLOWED for dprc@1.

  4. Check MC firmware version via restool -m to confirm compatibility.

Regards

0 件の賞賛
返信