linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Eugene Surovegin <ebs@ebshome.net>
To: linuxppc <linuxppc@4bridgeworks.com>
Cc: Linux PPC Dev <linuxppc-dev@ozlabs.org>
Subject: Re: Problem with PPC 440 GX Transmit Path
Date: Thu, 21 Oct 2004 10:49:23 -0700	[thread overview]
Message-ID: <20041021174923.GB6234@gate.ebshome.net> (raw)
In-Reply-To: <C18BA5DDB58DD511BD0700C0DF0DD4502941E6@NTSERVER4>

On Thu, Oct 21, 2004 at 03:20:55PM +0100, linuxppc wrote:
> I have found a problem with the driver for the PPC440GX (ibm_emac), while
> reading from the PPC (OCOTEA) BOX doesn't always transmit the last packet, I
> have managed to get it to continue by pinging it or from it, or if the root
> filesystem is mounted as nfs (I am assuming communications using nfs use a
> keepalive test or equivalent). I have also found that by turning on the
> debug options in ibm_emac_core.c (PKT_DEBUG) fixes the problem!! I have
> removed all but one of the debug messages and as long as they are in the tx
> functions (not the rx functions) I have no problems. Any help or guidance
> will be appreciated, for now I am going to try and implement gdb.....

Which kernel version you are using?

--
Eugene

  parent reply	other threads:[~2004-10-21 17:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-21 14:20 Problem with PPC 440 GX Transmit Path linuxppc
2004-10-21 14:53 ` Jon Masters
2004-10-21 17:49 ` Eugene Surovegin [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-10-21 14:59 Daren Hayward
2004-10-21 21:02 Daren Hayward

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=20041021174923.GB6234@gate.ebshome.net \
    --to=ebs@ebshome.net \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=linuxppc@4bridgeworks.com \
    /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).