From: "jay_chen" <jay_chen@alphanetworks.com>
To: <linuxppc-dev@ozlabs.org>
Subject: MPC8548 eTsec
Date: Mon, 27 Apr 2009 11:55:22 +0800 [thread overview]
Message-ID: <5B765F7640274B7AA46FA26F2CE9AED5@alphajay> (raw)
[-- Attachment #1: Type: text/plain, Size: 5336 bytes --]
Dear All:
I am using linux 2.6.14.5 (with many modification) and MPC8548.
Sometimes(very rare) the nic will boot up with rx problem. (tx is just fine)
I see pkts are all dropped in chip but no any RX or BSY interrupt are ever
raised.
(Receive Drop Counter is increased)
If I down and up the nic, the problem will gone.
Any suggestion is welcome. Thanks.
Jay...
Some dumps:
eth 3:
root@/# cat /proc/interrupts
CPU0
19: 0 OpenPIC Level enet_tx
20: 0 OpenPIC Level enet_rx
21: 12433 OpenPIC Level enet_tx ==> nic with problem, tx good
22: 0 OpenPIC Level enet_rx ==> nic with problem, no rx
23: 0 OpenPIC Level enet_error
24: 0 OpenPIC Level enet_error
26: 5604 OpenPIC Level serial
27: 1698 OpenPIC Level i2c-mpc, i2c-mpc
50: 0 OpenPIC Edge isr
51: 0 OpenPIC Edge isr
52: 0 OpenPIC Edge isr
53: 1 OpenPIC Edge isr
54: 1 OpenPIC Edge isr
55: 0 OpenPIC Edge isr
56: 1 OpenPIC Edge isr
57: 0 OpenPIC Edge isr
BAD: 0
root@/#
ctrl:
tsec_id : 0x1240000
ievent : 0x800000
imask : 0xF1710083
edis : 0x0
ecntrl : 0x1010
minflr : 0x0
ptv : 0x0
dmactrl : 0xC3
tbipa : 0x1F
tctrl : 0x6000
tstat : 0x80008000
dfvlan : 0x81000000
tbdlen : 0x0
txic : 0x82000015
tqueue : 0x8000
tbdbph : 0x0
tbptr0 : 0x7E16B470
tbaseh : 0x0
tbase0 : 0x7E16B000
rctrl : 0x7C0
rstat : 0x0
rxic : 0x0
rqueue : 0x800080
rbifx : 0x0
rqfar : 0x0
rqfcr : 0xF666
rqfpr : 0xBFEBFFBE
mrblr : 0x600
rbdbph : 0x0
rbptr0 : 0x7E16B800
rbaseh : 0x0
rbase0 : 0x7E16B800
maccfg1 : 0x3F
maccfg2 : 0x7205
ipgifg : 0x40605060
hafdup : 0xA1F037
maxfrm : 0x600
miimcfg : 0x7
miimcom : 0x0
miimadd : 0x0
miimcon : 0x0
miimstat : 0x0
miimind : 0x0
ifstat : 0x0
attr : 0xC0
attreli : 0x0
rmon:
Transmit and Receive 64-byte Frame Counter : 25360
Transmit and Receive 65-127 byte Frame Counter : 12546
Transmit and Receive 128-255 byte Frame Counter : 0
Transmit and Receive 256-511 byte Frame Counter : 0
Transmit and Receive 512-1023 byte Frame Counter : 0
Transmit and Receive 1024-1518 byte Frame Counter : 0
Transmit and Receive 1519-1522 byte Good VLAN Frame: 0
Receive Byte Counter : 2053580
Receive Packet Counter : 25475
Receive FCS Error Counter : 0
Receive Multicast Packet Counter : 0
Receive Broadcast Packet Counter : 4
Receive Control Frame Packet Counter : 0
Receive Pause Frame Packet Counter : 0
Receive Unknown OP Code Counter : 0
Receive Alignment Error Counter : 0
Receive Frame Length Error Counter : 0
Receive Code Error Counter : 0
Receive Carrier Sense Error Counter : 0
Receive Undersize Packet Counter : 0
Receive Oversize Packet Counter : 0
Receive Fragments Counter : 0
Receive Jabber Counter : 0
Receive Drop Counter : 25449
Transmit Byte Counter Counter : 795584
Transmit Packet Counter : 12431
Transmit Multicast Packet Counter : 1
Transmit Broadcast Packet Counter : 12430
Transmit Pause Control Frame Counter : 1
Transmit Deferral Packet Counter : 0
Transmit Excessive Deferral Packet Counter : 0
Transmit Single Collision Packet Counter : 0
Transmit Multiple Collision Packet Counter : 0
Transmit Late Collision Packet Counter : 0
Transmit Excessive Collision Packet Counter : 0
Transmit Total Collision Counter : 0
Transmit Drop Frame Counter : 0
Transmit Jabber Frame Counter : 0
Transmit FCS Error Counter : 0
Transmit Control Frame Counter : 1
Transmit Oversize Frame Counter : 0
Transmit Undersize Frame Counter : 0
Transmit Fragments Frame Counter : 0
Carry Register One : 0x0
Carry Register Two : 0x0
Carry Mask Register One : 0xFE03FFFF
Carry Mask Register Two : 0xFFFFD
extra:
kernel_dropped : 0
rx_large : 0
rx_short : 0
rx_nonoctet : 0
rx_crcerr : 0
rx_overrun : 0
rx_bsy : 0
rx_babr : 0
rx_trunc : 0
eberr : 0
tx_babt : 0
tx_underrun : 0
rx_skbmissing : 0
tx_timeout : 0
[-- Attachment #2: Type: text/html, Size: 16526 bytes --]
reply other threads:[~2009-04-27 4:11 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=5B765F7640274B7AA46FA26F2CE9AED5@alphajay \
--to=jay_chen@alphanetworks.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