linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Kumar Gala <kumar.gala@freescale.com>
To: Stefan Nickl <Stefan.Nickl@kontron.com>
Cc: linuxppc-embedded <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: Stability of network/io on MPC8540ADS?
Date: Thu, 13 May 2004 17:55:43 -0500	[thread overview]
Message-ID: <AA210AA0-A530-11D8-8C0F-000393DBC2E8@freescale.com> (raw)
In-Reply-To: <1084462045.4683.68.camel@lucy.pep-kaufbeuren.de>


Stefan,

We have found an issue with the TSEC driver that I'm working on pushing
a fix out for.  It is possible that might be causing your problem.  It
shows itself as a memory leak.  (this may at least explain #1 & #2)

- kumar

On May 13, 2004, at 10:27 AM, Stefan Nickl wrote:

> Hello,
> since the linuxppc-2.4 port to our custom 8540 board
> has made some progress now, I went back to the ADS
> board for some cross-checking.
> I've experienced several reproducible lockups that
> are triggered by heavy IO and/or networking.
> Kernel is vanilla linuxppc-2.4.27-pre2, gcc 3.2.3,
> root=/dev/nfs (Gentoo -Os -mcpu=603e)
> 1) Using netcat to write data over tcp:
>    cat /dev/zero | nc lucy 3000
>    "lucy" is running "nc -l -p 3000 |pipeworks > /dev/null"
>    This freezes the ADS after a few seconds.
> 2) Writing to the nfsroot server:
>    cat /dev/urandom > /test
>    The same. Reading seems ok.
> 3) Writing to a USB2.0 HDD connected via PCI
>    interface board (OHCI compatible).
>    Lockup after ~70MB of writing
> I haven't tested explicitly, but the kernel that
> was shipped with the board (some 2.4.20?) didn't
> seem to have such problems.
> Any ideas?
> --
> Stefan Nickl
> Kontron Modular Computers
>
> <.config>


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2004-05-13 22:55 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-13 15:27 Stability of network/io on MPC8540ADS? Stefan Nickl
2004-05-13 22:55 ` Kumar Gala [this message]
2004-05-14 18:54 ` Yuji Nishimura
2004-05-14 18:52   ` Kumar Gala
2004-05-14 19:11     ` Yuji Nishimura
2004-05-17  6:48   ` Stefan Nickl
2004-05-17 21:42     ` Kumar Gala
2004-05-17 22:16       ` Wolfgang Denk
2004-05-17 23:24         ` Dan Malek
2004-05-18 13:39         ` Kumar Gala

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=AA210AA0-A530-11D8-8C0F-000393DBC2E8@freescale.com \
    --to=kumar.gala@freescale.com \
    --cc=Stefan.Nickl@kontron.com \
    --cc=linuxppc-embedded@lists.linuxppc.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).