linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: James Black <jblack547@gmail.com>
To: linuxppc-dev@ozlabs.org
Subject: mpc8270 and fs_enet
Date: Thu, 29 Jan 2009 15:41:10 -0700	[thread overview]
Message-ID: <b77025b40901291441j7790f85ewd70ee81dc09ed55b@mail.gmail.com> (raw)

I've got an mpc8270 running the fs_enet v1.0 driver and we are having
problems with randomly corrupted tx buffer descriptor ready bits. The
CPM never clears the bit. This is a 2.6.19.2 kernel. We have the same
kernel with the 8260_io driver (kernel is from the denx ELDK4.2)
running on the mpc8250 that works perfect.

I've been through the clock tree in u-boot and the kernel with both
processors and they are configured corrected. I've checked all the
pins and they are configured correctly. I back ported some spin_lock
tx issues from 2.6.27.xx and still it is not working on the mpc8270.

These are the tests I am failing.

nmap -sS -v <target ip>

mpc8270 Target Output
~ # fs_enet: eth0 FS_ENET ERROR(s) 0xe
fs_enet: eth0 FS_ENET ERROR(s) 0xe
fs_enet: eth0 FS_ENET ERROR(s) 0xc
fs_enet: eth0 FS_ENET ERROR(s) 0x4
fs_enet: eth0 FS_ENET ERROR(s) 0x4
fs_enet: eth0 FS_ENET ERROR(s) 0xc
fs_enet: eth0 FS_ENET ERROR(s) 0xc
fs_enet: eth0 FS_ENET ERROR(s) 0xc
fs_enet: eth0 FS_ENET ERROR(s) 0xc
fs_enet: eth0 FS_ENET ERROR(s) 0x4
fs_enet: eth0 FS_ENET ERROR(s) 0x4

Host output-------------------------------------------------------------------------
[root@localhost linux]# nmap -sS -v 172.22.250.113
Starting Nmap 4.52 ( http://insecure.org ) at 2009-01-29 14:59 MST
Initiating Ping Scan at 14:59
Scanning 172.22.250.113 [2 ports]
Completed Ping Scan at 14:59, 0.00s elapsed (1 total hosts)
Initiating Parallel DNS resolution of 1 host. at 14:59
Completed Parallel DNS resolution of 1 host. at 14:59, 0.27s elapsed
Initiating SYN Stealth Scan at 14:59
Scanning 172.22.250.113 [1714 ports]
Discovered open port 23/tcp on 172.22.250.113
Discovered open port 80/tcp on 172.22.250.113
Discovered open port 21/tcp on 172.22.250.113
<eventually times out>

telnet <target ip>
ftpput -u <user name> -p <password> <host ip> <big file> <big file>

The telnet session hangs. Below is a BDI dump of the buffer
descriptors for the tx side.
Notice the BDs with a leading 0xd such as the ones at address
0x0e6e2100 and 0x0efe21d0. I can go in and clear the ready bit by hand
with the BDI and everything starts working again without a reboot. The
BDs on the rx side look text book perfect.

0e6e2100 : dc0005ea 0df8709e 1c0005ea 0df5f89e  ......p.........
0e6e2110 : 5c0005ea 0e29e89e 5c0005ea 0e29609e  \....)..\....)`.
0e6e2120 : 1c000358 0e29389e 5c00002a 0fa293c2  ...X.)8.\..*....
0e6e2130 : 5c00005a 0c42c202 5c00005a 0c42c802  \..Z.B..\..Z.B..
0e6e2140 : 1c00005a 0c42c602 5c00002a 0fa292c2  ...Z.B..\..*....
0e6e2150 : 5c0005ea 0df8909e 1c0005ea 0df8c09e  \...............
0e6e2160 : 5c0005ea 0e29a09e 1c0005ea 0e29a89e  \....).......)..
0e6e2170 : 5c0005ea 0e29989e 5c0005ea 0e29189e  \....)..\....)..
0e6e2180 : 1c0005ea 0df8989e 5c0005ea 0e29789e  ........\....)x.
0e6e2190 : 1c0005ea 0df8189e 5c0005ea 0df8109e  ........\.......
0e6e21a0 : 1c0005ea 0d86c09e 1c0005ea 0d86c89e  ................
0e6e21b0 : 5c0005ea 0e29d89e 1c0005ea 0e29d09e  \....).......)..
0e6e21c0 : 5c0005ea 0e2bd89e 5c0005ea 0e2bd09e  \....+..\....+..
0e6e21d0 : dc0005ea 0e29289e 5c0005ea 0df8689e  .....)(.\.....h.
0e6e21e0 : 1c0005ea 0e29f09e 5c0005ea 0e29909e  .....)..\....)..
0e6e21f0 : dc0005ea 0df8609e 3c0005ea 0df6109e  ......`.<.......

Anyone have any experience about what could make such a difference
between the two processors?

-- 
Jim Black
Senior Software Engineer
Aztek Networks, Inc.
2477 55th Street, Suite 202
Boulder, CO 80301
www.azteknetworks.com

             reply	other threads:[~2009-01-29 22:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-29 22:41 James Black [this message]
2009-01-29 23:05 ` mpc8270 and fs_enet Scott Wood
2009-01-29 23:27   ` James Black
2009-02-19 16:18     ` James Black

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=b77025b40901291441j7790f85ewd70ee81dc09ed55b@mail.gmail.com \
    --to=jblack547@gmail.com \
    --cc=linuxppc-dev@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).