求教斑竹，关于网卡芯片DM9000的问题
求教斑竹，我们自己的底板和友善的底板在网卡上用的相同的芯片，都为DM9000，现遇到了问题请教下。用的友善的核心板，我在超级终端上ping网关ping不通，显示eth0反复上电下电。
开机显示
Try to bring eth0 interface up......eth0: link down
Done
然后
Please press Enter to activate this console. eth0: link up, 100Mbps, full-duplex
, lpa 0x45E1
eth0: link down
eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
eth0: link down
eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
这个时候我Ping 网关会出现如下信息
[root@FriendlyARM /]# ping 192.168.1.1
PING 192.168.1.1 (192.168.1.1): 56 data bytes
------------[ cut here ]------------
WARNING: at net/sched/sch_generic.c:261 dev_watchdog+0x248/0x26c()
NETDEV WATCHDOG: eth0 (dm9000): transmit queue 0 timed out
Modules linked in:
Backtrace:
[<c00341cc>] (dump_backtrace+0x0/0x10c) from [<c03317d0>] (dump_stack+0x18/0x1c)
r7:c042c4b0 r6:00000105 r5:c02d22a8 r4:c044de08
[<c03317b8>] (dump_stack+0x0/0x1c) from [<c0048a80>] (warn_slowpath_common+0x4c/
0x64)
[<c0048a34>] (warn_slowpath_common+0x0/0x64) from [<c0048ae4>] (warn_slowpath_fm
t+0x30/0x38)
r7:c04b7de4 r6:c0454508 r5:00000000 r4:c38a4400
[<c0048ab4>] (warn_slowpath_fmt+0x0/0x38) from [<c02d22a8>] (dev_watchdog+0x248/
0x26c)
r3:c38a4400 r2:c042c4c8
[<c02d2060>] (dev_watchdog+0x0/0x26c) from [<c0052e90>] (run_timer_softirq+0x1a4
/0x228)
r7:c0454508 r6:c02d2060 r5:c044dea0 r4:00000100
[<c0052cec>] (run_timer_softirq+0x0/0x228) from [<c004defc>] (__do_softirq+0x9c/
0x130)
[<c004de60>] (__do_softirq+0x0/0x130) from [<c004dfd8>] (irq_exit+0x48/0x50)
[<c004df90>] (irq_exit+0x0/0x50) from [<c002f048>] (asm_do_IRQ+0x48/0x8c)
[<c002f000>] (asm_do_IRQ+0x0/0x8c) from [<c002fac4>] (__irq_svc+0x24/0xa0)
Exception stack(0xc044df48 to 0xc044df90)
df40: 00fbfff4 f4100000 f4100000 60000013 c044c000 c0489d24
df60: c0450430 c0450428 3001ec38 41129200 3001ec04 c044df9c c044dfa0 c044df90
df80: c00315fc c00310a4 60000013 ffffffff
r7:c0450428 r6:00004000 r5:f4000000 r4:ffffffff
[<c0031018>] (default_idle+0x0/0x98) from [<c00315fc>] (cpu_idle+0x78/0xb0)
[<c0031584>] (cpu_idle+0x0/0xb0) from [<c032f9a4>] (rest_init+0x5c/0x70)
r7:c0450428 r6:c0020c9c r5:c0020ca0 r4:c04ad4dc
[<c032f948>] (rest_init+0x0/0x70) from [<c000893c>] (start_kernel+0x204/0x24c)
[<c0008738>] (start_kernel+0x0/0x24c) from [<30008034>] (0x30008034)
---[ end trace 7032fe4ec11ae91a ]---
64 bytes from 192.168.1.1: seq=9 ttl=64 time=1.073 ms
eth0: link down
dm9000 dm9000: status check fail: 255
dm9000 dm9000: status check fail: 255
eth0: link up, 100Mbps, full-duplex, lpa 0xFFFF
eth0: link down
eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
dm9000 dm9000: status check fail: 255
dm9000 dm9000: status check fail: 255
eth0: link up, 100Mbps, full-duplex, lpa 0xFFFF
eth0: link down
eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
64 bytes from 192.168.1.1: seq=59 ttl=64 time=1626.686 ms
64 bytes from 192.168.1.1: seq=60 ttl=64 time=621.859 ms
64 bytes from 192.168.1.1: seq=61 ttl=64 time=0.652 ms
64 bytes from 192.168.1.1: seq=62 ttl=64 time=0.654 ms
64 bytes from 192.168.1.1: seq=63 ttl=64 time=0.655 ms
64 bytes from 192.168.1.1: seq=72 ttl=64 time=3561.345 ms
64 bytes from 192.168.1.1: seq=71 ttl=64 time=4566.658 ms
64 bytes from 192.168.1.1: seq=75 ttl=64 time=546.905 ms
64 bytes from 192.168.1.1: seq=76 ttl=64 time=0.660 ms
64 bytes from 192.168.1.1: seq=77 ttl=64 time=0.665 ms
eth0: link down
eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
64 bytes from 192.168.1.1: seq=125 ttl=64 time=3296.204 ms
64 bytes from 192.168.1.1: seq=124 ttl=64 time=4301.624 ms
64 bytes from 192.168.1.1: seq=128 ttl=64 time=281.870 ms
64 bytes from 192.168.1.1: seq=129 ttl=64 time=0.658 ms
64 bytes from 192.168.1.1: seq=130 ttl=64 time=0.588 ms
64 bytes from 192.168.1.1: seq=133 ttl=64 time=5256.076 ms
64 bytes from 192.168.1.1: seq=137 ttl=64 time=1236.523 ms
64 bytes from 192.168.1.1: seq=136 ttl=64 time=2241.759 ms
64 bytes from 192.168.1.1: seq=135 ttl=64 time=3247.002 ms
64 bytes from 192.168.1.1: seq=134 ttl=64 time=4252.241 ms
64 bytes from 192.168.1.1: seq=138 ttl=64 time=232.474 ms
64 bytes from 192.168.1.1: seq=139 ttl=64 time=0.673 ms
eth0: link down
eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
eth0: link down
eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
64 bytes from 192.168.1.1: seq=199 ttl=64 time=4271.438 ms
64 bytes from 192.168.1.1: seq=201 ttl=64 time=2261.747 ms
64 bytes from 192.168.1.1: seq=202 ttl=64 time=1256.987 ms
64 bytes from 192.168.1.1: seq=203 ttl=64 time=252.207 ms
dm9000 dm9000: status check fail: 255
dm9000 dm9000: status check fail: 255
64 bytes from 192.168.1.1: seq=213 ttl=64 time=5336.101 ms
64 bytes from 192.168.1.1: seq=216 ttl=64 time=2321.513 ms
64 bytes from 192.168.1.1: seq=215 ttl=64 time=3326.725 ms
64 bytes from 192.168.1.1: seq=214 ttl=64 time=4331.893 ms
64 bytes from 192.168.1.1: seq=218 ttl=64 time=312.071 ms
64 bytes from 192.168.1.1: seq=217 ttl=64 time=1317.251 ms
64 bytes from 192.168.1.1: seq=219 ttl=64 time=7.880 ms
64 bytes from 192.168.1.1: seq=220 ttl=64 time=0.668 ms
64 bytes from 192.168.1.1: seq=256 ttl=64 time=2121.437 ms
64 bytes from 192.168.1.1: seq=257 ttl=64 time=1116.569 ms
dm9000 dm9000: status check fail: 255
eth0: link down
eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
64 bytes from 192.168.1.1: seq=285 ttl=64 time=1976.398 ms
64 bytes from 192.168.1.1: seq=284 ttl=64 time=2981.702 ms
64 bytes from 192.168.1.1: seq=283 ttl=64 time=3986.955 ms
64 bytes from 192.168.1.1: seq=322 ttl=64 time=4791.302 ms
64 bytes from 192.168.1.1: seq=326 ttl=64 time=771.788 ms
64 bytes from 192.168.1.1: seq=325 ttl=64 time=1776.965 ms
64 bytes from 192.168.1.1: seq=324 ttl=64 time=2782.188 ms
64 bytes from 192.168.1.1: seq=338 ttl=64 time=20.148 ms
64 bytes from 192.168.1.1: seq=339 ttl=64 time=0.655 ms
^C
--- 192.168.1.1 ping statistics ---
351 packets transmitted, 52 packets received, 85% packet loss
round-trip min/avg/max = 0.588/1953.031/6426.112 ms
[root@FriendlyARM /]#
丢包率很高，我换了个DM9000也是这样。我用示波器打了正常的板子（友善的底板+核心板）和我们的板子（友善核心板+我们的底板）的DM9000的几个管脚，发现nRESET（PIN80）和EINT7（pin100）在我们的板子上没有波形，其他的使用中的管脚和正常的板子的波形差不多。
请教版主这个问题可能会出在什么地方？望赐教。
