TK1 MSELECT error detected! status=0x10

Hello!

We are using the TK1 chip on our custom board. Some of the boards have the MSELECT error issue while the other boards work well.

I cannot get any information about the MSELECT error status from the TRM document, could you tell me what is the meaning of the error message?

The detailed kernel messages as follows:
[ 9.199340] MSELECT error detected! status=0x10
[ 9.203862] ------------[ cut here ]------------
[ 9.208472] WARNING: at drivers/platform/tegra/hier_ictlr/hier_ictlr.c:55 tegra_hier_ictlr_irq_handler+0x4c/0x50()
[ 9.218794] Modules linked in: bluetooth rfkill
[ 9.223332] CPU: 0 PID: 601 Comm: X Not tainted 3.10.40-g7d669dfa #1
[ 9.229676] [] (unwind_backtrace+0x0/0x13c) from [] (show_stack+0x18/0x1c)
[ 9.238270] [] (show_stack+0x18/0x1c) from [] (warn_slowpath_common+0x5c/0x74)
[ 9.247208] [] (warn_slowpath_common+0x5c/0x74) from [] (warn_slowpath_null+0x24/0x2c)
[ 9.256840] [] (warn_slowpath_null+0x24/0x2c) from [] (tegra_hier_ictlr_irq_handler+0x4c/0x50)
[ 9.267166] [] (tegra_hier_ictlr_irq_handler+0x4c/0x50) from [] (handle_irq_event_percpu+0x88/0x28c)
[ 9.278011] [] (handle_irq_event_percpu+0x88/0x28c) from [] (handle_irq_event+0x44/0x64)
[ 9.287815] [] (handle_irq_event+0x44/0x64) from [] (handle_fasteoi_irq+0x8c/0x154)
[ 9.297186] [] (handle_fasteoi_irq+0x8c/0x154) from [] (generic_handle_irq+0x30/0x40)
[ 9.306731] [] (generic_handle_irq+0x30/0x40) from [] (handle_IRQ+0x48/0x98)
[ 9.315496] [] (handle_IRQ+0x48/0x98) from [] (gic_handle_irq+0x58/0x15c)
[ 9.324000] [] (gic_handle_irq+0x58/0x15c) from [] (__irq_svc+0x40/0x70)
[ 9.332415] Exception stack(0xecfafc68 to 0xecfafcb0)
[ 9.337451] fc60: 00000000 00000100 00000000 00000000 60000193 0000001d
[ 9.345607] fc80: 00000000 ecfafd68 c0ce8478 00000082 c0ce8478 ecfae030 c0d25380 ecfafcb0
[ 9.353762] fca0: c006d4d4 c006d594 20000113 ffffffff
[ 9.358801] [] (__irq_svc+0x40/0x70) from [] (__do_softirq+0xe0/0x320)
[ 9.367046] [] (__do_softirq+0xe0/0x320) from [] (do_softirq+0x5c/0x64)
[ 9.375378] [] (do_softirq+0x5c/0x64) from [] (irq_exit+0xa4/0xd8)
[ 9.383276] [] (irq_exit+0xa4/0xd8) from [] (handle_IRQ+0x4c/0x98)
[ 9.391172] [] (handle_IRQ+0x4c/0x98) from [] (gic_handle_irq+0x58/0x15c)
[ 9.399676] [] (gic_handle_irq+0x58/0x15c) from [] (__irq_svc+0x40/0x70)
[ 9.408090] Exception stack(0xecfafd68 to 0xecfafdb0)
[ 9.413126] fd60: 00000000 00000001 fbac1000 00000000 ed010000 c0d754a4
[ 9.421282] fd80: 00001000 00000000 f03c1000 00000000 c0d754a4 00000000 00013590 ecfafdb0
[ 9.429437] fda0: c03f1c4c c03f3070 60000013 ffffffff
[ 9.434476] [] (__irq_svc+0x40/0x70) from [] (gk20a_init_fifo_support+0x58/0x460)
[ 9.443675] [] (gk20a_init_fifo_support+0x58/0x460) from [] (gk20a_pm_finalize_poweron+0x288/0x6d4)
[ 9.454436] [] (gk20a_pm_finalize_poweron+0x288/0x6d4) from [] (pm_genpd_runtime_resume+0x1c8/0x2e8)
[ 9.465283] [] (pm_genpd_runtime_resume+0x1c8/0x2e8) from [] (__rpm_callback+0x34/0x68)
[ 9.475000] [] (__rpm_callback+0x34/0x68) from [] (rpm_callback+0x28/0x7c)
[ 9.483590] [] (rpm_callback+0x28/0x7c) from [] (rpm_resume+0x3d8/0x6a0)
[ 9.492008] [] (rpm_resume+0x3d8/0x6a0) from [] (__pm_runtime_resume+0x50/0x68)
[ 9.501033] [] (__pm_runtime_resume+0x50/0x68) from [] (gk20a_busy+0x38/0xa4)
[ 9.509883] [] (gk20a_busy+0x38/0xa4) from [] (gk20a_ctrl_dev_ioctl+0x1f4/0x4cc)
[ 9.518995] [] (gk20a_ctrl_dev_ioctl+0x1f4/0x4cc) from [] (do_vfs_ioctl+0x3f8/0x5bc)
[ 9.528455] [] (do_vfs_ioctl+0x3f8/0x5bc) from [] (SyS_ioctl+0x58/0x180)
[ 9.536873] [] (SyS_ioctl+0x58/0x180) from [] (ret_fast_syscall+0x0/0x30)
[ 9.545375] —[ end trace c42d57dd28a5c44e ]—

How can I debug this issue? Looking forward to your advice, thanks!

Add more information:
We use the package “Tegra124_Linux_R21.7.0_armhf.tbz2”.

Sorry for the late response, have you figured out why some of the boards have the MSELECT error issue while the other boards work well?

Any PCIe device connected?

Thanks for your reply, we still have this issue. We don’t know the meaning of the “status=0x10”.
We have 2 PCIe devices, one is I210-AT (giga), the other one is UPD720202 (USB3.0).
it is a PCIe related issue?