From: robin.randhawa@gmail.com (Robin Randhawa)
To: linux-arm-kernel@lists.infradead.org
Subject: Elusive crash in SMC91X/PXA network code?
Date: Mon, 18 Jan 2010 21:35:20 +0000 [thread overview]
Message-ID: <20100118213519.GA58659@gmail.com> (raw)
In-Reply-To: <alpine.DEB.1.10.1001181825560.22774@venus.araneidae.co.uk>
On Mon, Jan 18, 2010 at 06:27:19PM +0000, Michael Abbott wrote:
> The bug in question is most reliably forced by transferring a very large
> file over NFS while the embedded driver is performing DMA transfers (from
> FPGA to XCEP RAM); it is also possible to force the crash by sending
> enough UDP packets to the device; I've had no success in forcing the crash
> with any other form of network load. It can take anything from a few
> seconds to many minutes of such stress for the crash to occur.
This sounds almost exactly like a problem I've experienced before,
although that was on a development board built around a different
processor architecture. Kept experiencing mysterious memory junking
which seemed to precipitate quicker when performing large file transfers
over NFS.
The ethernet controller (an Intel eepro 100 IIRC) had diagnostics which
seemed to indicate checksumming errors. After trying virtually every
trick in the book, it turned out to be a subtle misconfiguration of the
SDRAM RAS-to-CAS delay timing which the bootloader had messed up. With
that fixed, everything worked without a hitch.
Worth a shot, IMHO.
Cheers,
Robin
prev parent reply other threads:[~2010-01-18 21:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-18 18:27 Elusive crash in SMC91X/PXA network code? Michael Abbott
2010-01-18 18:43 ` Daniel Mack
2010-01-18 21:35 ` Robin Randhawa [this message]
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=20100118213519.GA58659@gmail.com \
--to=robin.randhawa@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).