On Mon, Aug 11, 2014 at 10:32 AM, Mattis Lorentzon <mattis.lorent...@autoliv.com> wrote: > Russell and Fabio, > >> I'd be interested to hear whether removing the >> >> interrupts-extended = ... >> >> property from your board's DT file, thereby causing you to revert back to the >> default I list above, also fixes the instability you are seeing. > > We have tried to remove the board specific interrupts-extended field and the > MX6QDL_PAD_GPIO_6__ENET_IRQ entry. Sadly this did not seem to improve > the stalls. Our interrupts look like this now: > > 150: 15519 0 0 0 GIC 150 > 2188000.ethernet > 151: 0 0 0 0 GIC 151 > 2188000.ethernet > > Our device tree might still be slightly incorrect. We have noticed that our > RGMII_INT is connected to GPIO 19 (P5) which might be nonstandard (we are > a bit surprised that this works at all). We are not quite sure how to > configure > this properly.
In order to try to narrow down whether this is a board issue, could you try to run the same kernel on a mx6q development board, such as mx6qsabresd, cubox-i, wandboard, etc? -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
