linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Eugene Surovegin <ebs@ebshome.net>
To: Brian Kuschak <bkuschak@yahoo.com>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: 440gx ethernet lockup
Date: Thu, 20 Nov 2003 18:36:49 -0800	[thread overview]
Message-ID: <20031121023649.GA5602@gate.ebshome.net> (raw)
In-Reply-To: <20031121015449.28462.qmail@web40911.mail.yahoo.com>


On Thu, Nov 20, 2003 at 05:54:49PM -0800, Brian Kuschak wrote:
>
> Is anyone actively working with ethernet on the 440GX?
>  I'm seeing TX lockups when stressing the 10/100 EMAC
> with heavy NFS traffic:
>
> find /nfs_mnt -type f |xargs grep blahblahblah
>
> This is the only way I can make it happen, but it does
> happen quickly.
>
> The 'get_next_packet' bit is set but never clears.
> The EMAC_ISR doesn't have any unusual errors (except
> for some deferrals).  The 'dead_bit' is _not_
> asserted.  The MAL channels are enabled, and so is the
> EMAC.  No TXDE interrupts have occurred.  The BD ring
> is filled with packets ready to send.  The same code
> on a 440GP works fine.  This version of the CPU (PVR
> 0x51b21851) is supposed to have all the EMAC-related
> errata fixed, but this smells like a silicon bug to
> me.

What kernel version? What board? Eval or your custom one?
If the custom one, did you try your test on eval?

How long does it usually take to get into lock up state?

I've just ran your "find" cmd for 10 minutes on our 440GX board
without any problems.

What clock mode are you using (533/152, 500/166 or smth else)?
Do you have L2C enabled? If yes, please check L2C0_SR for parity
errors (we have some problems with several our 440GX boards).

Eugene.


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

  reply	other threads:[~2003-11-21  2:36 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-21  1:54 440gx ethernet lockup Brian Kuschak
2003-11-21  2:36 ` Eugene Surovegin [this message]
2003-11-21  6:32   ` Brian Kuschak
2003-11-21  7:11     ` Eugene Surovegin
2003-12-02 21:01       ` Brian Kuschak
2003-12-02 21:57         ` Cort Dougan
2003-12-03  3:43         ` Eugene Surovegin
2003-12-03 18:28           ` Brian Kuschak

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=20031121023649.GA5602@gate.ebshome.net \
    --to=ebs@ebshome.net \
    --cc=bkuschak@yahoo.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).