linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: stigge@antcom.de (Roland Stigge)
To: linux-arm-kernel@lists.infradead.org
Subject: NXP LPC3250 broken?
Date: Mon, 13 Apr 2015 10:01:14 +0200	[thread overview]
Message-ID: <552B77CA.2070604@antcom.de> (raw)
In-Reply-To: <CAGhQ9VysMCJzRYz-C_VmWqBAVKXfh2ydq5iNu96RxfD4k0cWvw@mail.gmail.com>

Hi,

have you tried to compare with an NXP dev kit?

I also have an EA board but not currently connected. Will need to test
when I have access to it again.

Thanks for reporting,

Roland


On 04/12/2015 04:20 PM, Joachim Eastwood wrote:
> Hi,
> 
> I recently got a Embedded Artist LPC3250 (ea3250.dts) board that I
> wanted to test mainline Linux on.
> 
> But with lpc32xx_defconfig, ea3250.dts and the latest rc (v4.0-rc7) I am
> not getting very far.
> 
> First I got a "kernel NULL pointer dereference". See
> http://slexy.org/raw/s211rzbZL1
> I got around this one by disabling the leds-gpio driver.
> 
> Then, without leds-gpio, I get an endless stream of "unexpected IRQ trap
> at vector 00" messages.
> See: http://slexy.org/raw/s2S5Z9TtoV
> 
> I also tried an older kernel (3.18). This one seemed at first to hang
> but after a short while I got lots of backtraces which seem to involve
> rcu, tick and timer interrupt.
> See: http://slexy.org/raw/s2024RXCkX
> 
> Does anyone got any ideas on what may be going on?
> 
> 
> When I get a bit more time to play around with the kit I will try even
> older kernels to see if I can get it working at all.
> 
> best regards,
> Joachim Eastwood

       reply	other threads:[~2015-04-13  8:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAGhQ9VysMCJzRYz-C_VmWqBAVKXfh2ydq5iNu96RxfD4k0cWvw@mail.gmail.com>
2015-04-13  8:01 ` Roland Stigge [this message]
2015-04-13 11:59   ` NXP LPC3250 broken? Joachim Eastwood
2015-04-13 13:01     ` Roland Stigge
2015-04-13 13:26       ` Arnd Bergmann
2015-04-13 15:19         ` Joachim Eastwood
2015-04-13 15:35           ` Arnd Bergmann
2015-04-13 15:15       ` Joachim Eastwood

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=552B77CA.2070604@antcom.de \
    --to=stigge@antcom.de \
    --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).