From: Daren Hayward <darenh@4bridgeworks.com>
To: 'Eugene Surovegin' <ebs@ebshome.net>,
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 22:02:36 +0100 [thread overview]
Message-ID: <C18BA5DDB58DD511BD0700C0DF0DD4502941EA@NTSERVER4> (raw)
Version 2.6.9-rc4
-----Original Message-----
From: Eugene Surovegin [mailto:ebs@ebshome.net]
Sent: 21 October 2004 18:49
To: linuxppc
Cc: Linux PPC Dev
Subject: Re: Problem with PPC 440 GX Transmit Path
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
next reply other threads:[~2004-10-21 21:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-21 21:02 Daren Hayward [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-10-21 14:59 Problem with PPC 440 GX Transmit Path Daren Hayward
2004-10-21 14:20 linuxppc
2004-10-21 14:53 ` Jon Masters
2004-10-21 17:49 ` Eugene Surovegin
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=C18BA5DDB58DD511BD0700C0DF0DD4502941EA@NTSERVER4 \
--to=darenh@4bridgeworks.com \
--cc=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