From: Yuji Nishimura <yujin@pp.iij4u.or.jp>
To: Kumar Gala <kumar.gala@freescale.com>
Cc: linuxppc-embedded <linuxppc-embedded@lists.linuxppc.org>,
Stefan Nickl <Stefan.Nickl@kontron.com>
Subject: Re: Stability of network/io on MPC8540ADS?
Date: Sat, 15 May 2004 04:11:49 +0900 [thread overview]
Message-ID: <40A519F5.6010407@pp.iij4u.or.jp> (raw)
In-Reply-To: <D0320B10-A5D7-11D8-AB97-000393DBC2E8@freescale.com>
Hi Kumar ,
You can check same patch on your internal SF server (Motorola internal).
I uploaded patch on 5/6 or 5/7.
Please check it...
Best Regards,
Yuji Nishimura -Tokyo Japan (rty922@email.sps.mot.com)
Kumar Gala wrote:
> Y.Nishimura ,
>
> It looks like the patch was not included in your email. I would
> appreciate seeing it and evaluating if it is something we should
> include in the stock kernel.
>
> - kumar
>
> On May 14, 2004, at 1:54 PM, Yuji Nishimura wrote:
>
>>
>> Helo Stefan,
>>
>> I evaluated MPC8540ADS and found out similar problem few weeks ago. I
>> made tiny patch and it works well.
>> I also evaluated with NEC ehci pci device. The result was fine.
>> I wrote 1GB data to external usb-2.0 HDD via USB-2.0(ehci), that
>> works well.
>> I also try to use ftp(MPC8540=server) and transfer (R/W) 2047MB data via
>> TSEC(gianfar) and it also works well.
>> If you try to use this patch, please let me know. I think patch requires
>> more evaluation...
>>
>> Best Regards,
>> Y.Nishimura - Tokyo, Japan.
>>
>>
>>
>> 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
>>>
>>>
>>>
>>
>>
>
>
>
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-05-14 19:11 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
2004-05-14 18:54 ` Yuji Nishimura
2004-05-14 18:52 ` Kumar Gala
2004-05-14 19:11 ` Yuji Nishimura [this message]
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=40A519F5.6010407@pp.iij4u.or.jp \
--to=yujin@pp.iij4u.or.jp \
--cc=Stefan.Nickl@kontron.com \
--cc=kumar.gala@freescale.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).