From mboxrd@z Thu Jan 1 00:00:00 1970 From: festevam@gmail.com (Fabio Estevam) Date: Mon, 11 Aug 2014 14:41:25 -0300 Subject: Oops: 17 SMP ARM (v3.16-rc2) In-Reply-To: References: <20140626151424.GT32514@n2100.arm.linux.org.uk> <20140627112151.GF32514@n2100.arm.linux.org.uk> <3FFB61A7A8473C49831AF20FA193534A43CADFA7@ALVA-EXMB01.alv.autoliv.int> <20140627163108.GP32514@n2100.arm.linux.org.uk> <20140806095012.GN30282@n2100.arm.linux.org.uk> <20140806125550.GO30282@n2100.arm.linux.org.uk> <20140807121248.GY30282@n2100.arm.linux.org.uk> <20140808180900.GG30282@n2100.arm.linux.org.uk> Message-ID: To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On Mon, Aug 11, 2014 at 10:32 AM, Mattis Lorentzon 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?