From: festevam@gmail.com (Fabio Estevam)
To: linux-arm-kernel@lists.infradead.org
Subject: Oops: 17 SMP ARM (v3.16-rc2)
Date: Mon, 11 Aug 2014 14:41:25 -0300 [thread overview]
Message-ID: <CAOMZO5B8GR+ABBoJ=dJcFqw3Wagfaip7HM+C1FTz+aE4CmqiPw@mail.gmail.com> (raw)
In-Reply-To: <C4A61A5CA4AD2246942F4BA6F20ACB8043576356@ALVA-EXMB04.alv.autoliv.int>
On Mon, Aug 11, 2014 at 10:32 AM, Mattis Lorentzon
<Mattis.Lorentzon@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?
next prev parent reply other threads:[~2014-08-11 17:41 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <C4A61A5CA4AD2246942F4BA6F20ACB804356534D@ALVA-EXMB04.alv.autoliv.int>
[not found] ` <20140626140115.GQ32514@n2100.arm.linux.org.uk>
2014-06-26 14:44 ` Oops: 17 SMP ARM (v3.16-rc2) Mattis Lorentzon
2014-06-26 15:14 ` Russell King - ARM Linux
2014-06-27 11:21 ` Russell King - ARM Linux
2014-06-27 16:16 ` Fredrik Noring
2014-06-27 16:31 ` Russell King - ARM Linux
2014-06-30 6:22 ` Fredrik Noring
2014-06-30 12:30 ` Fredrik Noring
2014-06-30 13:00 ` Nathan Lynch
2014-07-02 6:02 ` Fredrik Noring
2014-08-05 13:31 ` Mattis Lorentzon
2014-08-05 13:53 ` Fabio Estevam
2014-08-06 6:48 ` Mattis Lorentzon
2014-08-06 9:50 ` Russell King - ARM Linux
2014-08-06 11:10 ` Mattis Lorentzon
2014-08-06 12:55 ` Russell King - ARM Linux
2014-08-07 11:11 ` Mattis Lorentzon
2014-08-07 12:12 ` Russell King - ARM Linux
2014-08-07 14:20 ` Fabio Estevam
2014-08-07 14:38 ` Fabio Estevam
2014-08-08 1:30 ` Troy Kisky
2014-08-08 14:05 ` Fabio Estevam
2014-08-08 18:09 ` Russell King - ARM Linux
2014-08-11 13:32 ` Mattis Lorentzon
2014-08-11 17:41 ` Fabio Estevam [this message]
2014-08-13 13:39 ` Mattis Lorentzon
2014-08-25 10:18 ` Russell King - ARM Linux
2014-08-26 13:11 ` Iain Paton
2014-08-14 14:43 ` Mattis Lorentzon
2014-08-14 15:30 ` Fabio Estevam
2014-08-15 5:42 ` Mattis Lorentzon
2014-08-17 21:34 ` Iain Paton
2014-08-17 21:46 ` Fabio Estevam
2014-08-19 6:03 ` Iain Paton
2014-08-21 9:39 ` Iain Paton
2014-08-22 0:01 ` Fabio Estevam
2014-08-22 6:39 ` Mattis Lorentzon
2014-08-22 10:36 ` Iain Paton
2014-08-27 6:32 ` Mattis Lorentzon
2014-08-27 10:43 ` Iain Paton
2014-08-29 10:57 ` Mattis Lorentzon
2014-08-29 11:30 ` Fabio Estevam
2014-12-16 14:50 ` Mattis Lorentzon
2014-08-26 13:12 ` Iain Paton
2014-08-22 8:27 ` Russell King - ARM Linux
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAOMZO5B8GR+ABBoJ=dJcFqw3Wagfaip7HM+C1FTz+aE4CmqiPw@mail.gmail.com' \
--to=festevam@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).