From: Siju Viswanath K E <siju@india.tejasnetworks.com>
To: linuxppc-embedded@ozlabs.org
Cc: siju@india.tejasnetworks.com
Subject: "transmit timed out" on FCC in MPC8260 as well as MPC8247
Date: 24 Mar 2006 10:50:51 +0530 [thread overview]
Message-ID: <1143177651.22246.3.camel@Blaze> (raw)
Hi,
I am using denk's linuxppc-2.4.20 . I am getting this problem of
"transmit timed out" on FCC in MPC8260 as well as MPC8247. It seems to
be a case of late collision. I checked out earlier posts similar to this
also. The problem occurs if I attempt to transfer large files and is not
seen on all systems.
The messages on console are given below. I am seeing the
same 5th BD reporting LC. FCC_PSMR_LPB is already set in
arch/ppc/8260_io/fcc_enet.c .
Can the 8247 errata CPM119 or some other errata be the cause ? What is
the solution for this ?
console messages:
NETDEV WATCHDOG: eth0: transmit timed out
eth0: transmit timed out.
Ring data dump: cur_tx c01ef560 (full) cur_rx c01ef4d0.
Tx @base c01ef508 :
5c00 0036 016d7da2
1c00 003e 00c25892
5c00 0036 00c2529a
1c00 0121 066b489a
1c00 05ea 0652e89a
1c80 01f0 0652e09a
9c00 0056 00c25c7a
9c00 003e 00c25e92
9c00 0056 00ad527a
9c00 003e 00ad5092
dc00 0036 00ad549a
9c00 004e 00c25682
1c00 003e 00c25492
5c00 0036 00c25a9a
1c00 0123 065c009a
3c00 040d 066b409a
Rx @base c01ef408 :
9c00 0040 07b34000
<deleted>
bc00 0040 07b25800
+++++++++++++++++ similar problems ++++++++++++++++++++
1. http://patchwork.ozlabs.org/linuxppc/patch?id=1853
2. From: hubert loewenguth <hubert.loewenguth@thales-bm.com>
To: linuxppc-embedded@ozlabs.org
Subject: MPC8260 fcc_enet transmit timed out
Date: Mon, 14 Nov 2005 18:34:32 +0100
<deleted>
I have found some personns in this mailling list who has encounter a
problem wich seems similar:
http://ozlabs.org/pipermail/linuxppc-embedded/2005-January/016539.html
http://ozlabs.org/pipermail/linuxppc-embedded/2001-December/005714.html
<deleted>
+++++++++++++++++ similar problems ++++++++++++++++++++
Thanks,
Siju Viswanath K E
Tejas Networks
next reply other threads:[~2006-03-24 6:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-24 5:20 Siju Viswanath K E [this message]
2006-03-24 7:51 ` "transmit timed out" on FCC in MPC8260 as well as MPC8247 Wolfgang Denk
2006-03-24 9:47 ` [BULK] " Siju Viswanath K E
2006-03-24 11:44 ` "transmit timed out" on FCC in MPC8260 => bug corrected hubert.loewenguth
2006-03-27 4:31 ` [BULK] " Siju Viswanath K E
2006-03-25 0:10 ` [BULK] Re: "transmit timed out" on FCC in MPC8260 as well as MPC8247 Wolfgang Denk
2006-03-27 4:34 ` Siju Viswanath K E
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=1143177651.22246.3.camel@Blaze \
--to=siju@india.tejasnetworks.com \
--cc=linuxppc-embedded@ozlabs.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).