From: Tony Lindgren <tony@atomide.com>
To: Casper Lyngesen Mogensen <clmogensen@grundfos.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: OMAP 3630 random crashes
Date: Fri, 20 Jun 2014 02:14:32 -0700 [thread overview]
Message-ID: <20140620091431.GA28884@atomide.com> (raw)
In-Reply-To: <1403254242990.39117@grundfos.com>
Hi,
* Casper Lyngesen Mogensen <clmogensen@grundfos.com> [140620 01:52]:
> Hi
>
> I have custom board with a Gumstix Overo, my board is similar to a
> Tobi board. Right now i have it running with a 3.5.0 kernel. I'm
> trying to upgrade the kernel, and have tried several versions (3.10 ->
> 3.15) and i seem to be hitting the same problem with all versions, i
> get random crashes. Found a way to trigger the crash within
> minutes/seconds:
>
> # dd if=/dev/urandom of=/tmp/test.file bs=1024 count=100000
>
> A count > 10000 will at some point trigger the crash. The hang/crash
> is repeatable everytime but the log is not, sometimes i do not get
> any trace at all. I can provide more logs if necessary. Config and
> crash log are below..
>
> Have tried disabling various peripherals, such as sound, usb,
> ethernet, wifi, bluetooth, but with no luck. Also tried different Overo
> boards.
>
> Hope someone can help me/point me in the right direction
I was seeing similar issues with NFSroot until commit dcf21919
(ARM: dts: Fix GPMC timings for LAN9220). Turns out LAN9220 has
much slower timings compared to LAN9221. So you need to check that
you're using right timings if you have LAN9220.
Also, check what rate your bootloader is setting the L3 speed.
If it's set to 200MHz, then LAN9220 timings seem to overflow the
GPMC registers for the calculated values and bootloader timings
are used instead.
> Starting kernel ...
>
> [ 0.000000] Booting Linux on physical CPU 0x0
> [ 0.000000] Linux version 3.15.0 (clmo@N66266) (gcc version 4.8.1 (crosstool-NG 1.19.0) ) #3 SMP Wed Jun 11 23:50:13 CEST 2014
> [ 0.000000] CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7), cr=10c5387d
> [ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
> [ 0.000000] Machine model: OMAP36xx/AM37xx/DM37xx Gumstix Overo on Tobi
> [ 0.000000] cma: CMA: reserved 16 MiB at 8d800000
> [ 0.000000] Memory policy: Data cache writeback
> [ 0.000000] CPU: All CPU(s) started in SVC mode.
> [ 0.000000] OMAP3630 ES1.2 (l2cache neon isp 192mhz_clk )
> [ 0.000000] PERCPU: Embedded 9 pages/cpu @cecc6000 s14080 r8192 d14592 u36864
> [ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 60704
> [ 0.000000] Kernel command line: console=ttyO2,115200n8 root=/dev/nfs nfsroot=192.168.100.1:/export/bbroot,nolock rw ip=192.168.100.7::192.168.100.1:::eth0:off mem=240M
Maybe also check if your test works with NFSroot idsabled.
Regards,
Tony
next prev parent reply other threads:[~2014-06-20 9:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-20 8:50 OMAP 3630 random crashes Casper Lyngesen Mogensen
2014-06-20 9:14 ` Tony Lindgren [this message]
2014-06-20 14:00 ` Casper Lyngesen Mogensen
2014-06-20 14:17 ` Ash Charles
2014-06-20 14:26 ` Casper Lyngesen Mogensen
2014-06-23 6:07 ` Casper Lyngesen Mogensen
2014-06-23 8:35 ` Tony Lindgren
2014-06-30 13:43 ` Casper Lyngesen Mogensen
2014-06-30 13:47 ` Michael Trimarchi
2014-06-30 14:01 ` Casper Lyngesen Mogensen
2014-07-01 7:54 ` Tony Lindgren
2014-07-01 10:35 ` Casper Lyngesen Mogensen
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=20140620091431.GA28884@atomide.com \
--to=tony@atomide.com \
--cc=clmogensen@grundfos.com \
--cc=linux-omap@vger.kernel.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).