* Change FEC and SCC1 sequence,But SCC1 not work?
@ 2004-06-10 9:12 hjzgq
2004-06-10 16:52 ` Mark Chambers
2004-06-10 17:17 ` Wolfgang Denk
0 siblings, 2 replies; 4+ messages in thread
From: hjzgq @ 2004-06-10 9:12 UTC (permalink / raw)
To: linuxppc-embedded
Hi all,
I'm having a peculiar problem.
Briefly, my platform is MPC860T from Motorola. I'm using ppcboot 1.1.16
to tftp the kernel 2.4.4 through FEC and then load NFS/RAMDISK. If I
configure the kernel with only FEC, then everything works well(NFS
works and ping through eth0 works). If I configure the kernel with both
FEC(as eth0) and SCC1(as eth1),it works well too,but when I configure
ther kernel with both SCC1(eth0) and FEC(as eth1) (net/setup.c)! . I
try to ping out through FEC(eth1), I get ring buffer dumps and no ping
response:
NETDEV WATCHDOG: eth1: transmit timed out
eth1: transmit timed out.
Ring data dump: cur_tx c1fa8100, tx_free 0, dirty_tx c1fa8100, cur_rx
c1fa8020
tx: 16 buffers
c1fa8100: 9c00 002a 01f868c2
c1fa8108: 9c00 002a 01f86842
c1fa8110: 9c00 002a 01f867c2
c1fa8118: 9c00 002a 01f86742
c1fa8120: 9c00 002a 01f866c2
c1fa8128: 9c00 002a 01f86642
c1fa8130: 9c00 002a 01f865c2
c1fa8138: 9c00 002a 01f86542
c1fa8140: 9c00 002a 01f864c2
c1fa8148: 9c00 002a 01f86442
c1fa8150: 9c00 002a 01f863c2
c1fa8158: 9c00 002a 01f86342
c1fa8160: 9c00 002a 01f862c2
c1fa8168: 9c00 002a 01dafbe2
c1fa8170: 9c00 002a 01dafb62
c1fa8178: bc00 002a 01dafce2
rx: 32 buffers
c1fa8000: 8880 0252 01fa7000
c1fa8008: 8880 0040 01fa7800
c1fa8010: 8880 0162 01fa6000
c1fa8018: 8880 0040 01fa6800
c1fa8020: 8000 0000 01fa5000
c1fa8028: 8000 0000 01fa5800
c1fa8030: 8000 0000 01fa4000
c1fa8038: 8000 0000 01fa4800
c1fa8040: 8000 0000 01fa3000
c1fa8048: 8000 0000 01fa3800
c1fa8050: 8000 0000 01fa2000
c1fa8058: 8000 0000 01fa2800
c1fa8060: 8000 0000 01fa1000
c1fa8068: 8000 0000 01fa1800
c1fa8070: 8000 0000 01fa0000
c1fa8078: 8000 0000 01fa0800
c1fa8080: 8000 0000 01f9f000
c1fa8088: 8000 0000 01f9f800
c1fa8090: 8000 0000 01f9e000
c1fa8098: 8000 0000 01f9e800
c1fa80a0: 8000 0000 01f9d000
c1fa80a8: 8000 0000 01f9d800
c1fa80b0: 8000 0000 01f9c000
c1fa80b8: 8000 0000 01f9c800
c1fa80c0: 8000 0000 01f9b000
c1fa80c8: 8000 0000 01f9b800
c1fa80d0: 8000 0000 01f9a000
c1fa80d8: 8000 0000 01f9a800
c1fa80e0: 8000 0000 01f99000
c1fa80e8: 8000 0000 01f99800
c1fa80f0: 8000 0000 01f98000
c1fa80f8: a000 0000 01f98800
Doing an ifconfig gives me......(TX errors continue to accumulate
indefinitely even after I stop ping)
eth0 Link encap:Ethernet HWaddr 00:02:87:55:66:77
inet addr:199.199.199.129 Bcast:199.199.199.255
Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1538 errors:0 dropped:0 overruns:0 frame:0
TX packets:698 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:1787601 (1.7 Mb) TX bytes:102816 (100.4 kb)
Base address:0x3c00
eth1 Link encap:Ethernet HWaddr 00:02:87:D5:66:77
inet addr:192.168.2.129 Bcast:192.168.2.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:4 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:5 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:1076 (1.0 kb) TX bytes:672 (672.0 b)
Base address:0xe00
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:21 errors:0 dropped:0 overruns:0 frame:0
TX packets:21 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:2352 (2.2 kb) TX bytes:2352 (2.2 kb)
Any help is deeply appreciated.
Thanks
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Change FEC and SCC1 sequence,But SCC1 not work?
2004-06-10 9:12 Change FEC and SCC1 sequence,But SCC1 not work? hjzgq
@ 2004-06-10 16:52 ` Mark Chambers
2004-06-10 17:17 ` Wolfgang Denk
1 sibling, 0 replies; 4+ messages in thread
From: Mark Chambers @ 2004-06-10 16:52 UTC (permalink / raw)
To: hjzgq, linuxppc-embedded
I notice that the MAC and IP for eth0 and eth1 are the same in the ifconfig
dump.
----- Original Message -----
From: <hjzgq@sohu.com>
To: <linuxppc-embedded@lists.linuxppc.org>
Sent: Thursday, June 10, 2004 5:12 AM
Subject: Change FEC and SCC1 sequence,But SCC1 not work?
>
> Hi all,
>
> I'm having a peculiar problem.
>
> Briefly, my platform is MPC860T from Motorola. I'm using ppcboot 1.1.16
> to tftp the kernel 2.4.4 through FEC and then load NFS/RAMDISK. If I
> configure the kernel with only FEC, then everything works well(NFS
> works and ping through eth0 works). If I configure the kernel with both
> FEC(as eth0) and SCC1(as eth1),it works well too,but when I configure
> ther kernel with both SCC1(eth0) and FEC(as eth1) (net/setup.c)! . I
> try to ping out through FEC(eth1), I get ring buffer dumps and no ping
> response:
>
> NETDEV WATCHDOG: eth1: transmit timed out
> eth1: transmit timed out.
> Ring data dump: cur_tx c1fa8100, tx_free 0, dirty_tx c1fa8100, cur_rx
> c1fa8020
> tx: 16 buffers
> c1fa8100: 9c00 002a 01f868c2
> c1fa8108: 9c00 002a 01f86842
> c1fa8110: 9c00 002a 01f867c2
> c1fa8118: 9c00 002a 01f86742
> c1fa8120: 9c00 002a 01f866c2
> c1fa8128: 9c00 002a 01f86642
> c1fa8130: 9c00 002a 01f865c2
> c1fa8138: 9c00 002a 01f86542
> c1fa8140: 9c00 002a 01f864c2
> c1fa8148: 9c00 002a 01f86442
> c1fa8150: 9c00 002a 01f863c2
> c1fa8158: 9c00 002a 01f86342
> c1fa8160: 9c00 002a 01f862c2
> c1fa8168: 9c00 002a 01dafbe2
> c1fa8170: 9c00 002a 01dafb62
> c1fa8178: bc00 002a 01dafce2
> rx: 32 buffers
> c1fa8000: 8880 0252 01fa7000
> c1fa8008: 8880 0040 01fa7800
> c1fa8010: 8880 0162 01fa6000
> c1fa8018: 8880 0040 01fa6800
> c1fa8020: 8000 0000 01fa5000
> c1fa8028: 8000 0000 01fa5800
> c1fa8030: 8000 0000 01fa4000
> c1fa8038: 8000 0000 01fa4800
> c1fa8040: 8000 0000 01fa3000
> c1fa8048: 8000 0000 01fa3800
> c1fa8050: 8000 0000 01fa2000
> c1fa8058: 8000 0000 01fa2800
> c1fa8060: 8000 0000 01fa1000
> c1fa8068: 8000 0000 01fa1800
> c1fa8070: 8000 0000 01fa0000
> c1fa8078: 8000 0000 01fa0800
> c1fa8080: 8000 0000 01f9f000
> c1fa8088: 8000 0000 01f9f800
> c1fa8090: 8000 0000 01f9e000
> c1fa8098: 8000 0000 01f9e800
> c1fa80a0: 8000 0000 01f9d000
> c1fa80a8: 8000 0000 01f9d800
> c1fa80b0: 8000 0000 01f9c000
> c1fa80b8: 8000 0000 01f9c800
> c1fa80c0: 8000 0000 01f9b000
> c1fa80c8: 8000 0000 01f9b800
> c1fa80d0: 8000 0000 01f9a000
> c1fa80d8: 8000 0000 01f9a800
> c1fa80e0: 8000 0000 01f99000
> c1fa80e8: 8000 0000 01f99800
> c1fa80f0: 8000 0000 01f98000
> c1fa80f8: a000 0000 01f98800
>
> Doing an ifconfig gives me......(TX errors continue to accumulate
> indefinitely even after I stop ping)
>
> eth0 Link encap:Ethernet HWaddr 00:02:87:55:66:77
> inet addr:199.199.199.129 Bcast:199.199.199.255
> Mask:255.255.255.0
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:1538 errors:0 dropped:0 overruns:0 frame:0
> TX packets:698 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:100
> RX bytes:1787601 (1.7 Mb) TX bytes:102816 (100.4 kb)
> Base address:0x3c00
>
> eth1 Link encap:Ethernet HWaddr 00:02:87:D5:66:77
> inet addr:192.168.2.129 Bcast:192.168.2.255 Mask:255.255.255.0
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:4 errors:0 dropped:0 overruns:0 frame:0
> TX packets:0 errors:5 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:100
> RX bytes:1076 (1.0 kb) TX bytes:672 (672.0 b)
> Base address:0xe00
>
> lo Link encap:Local Loopback
> inet addr:127.0.0.1 Mask:255.0.0.0
> UP LOOPBACK RUNNING MTU:16436 Metric:1
> RX packets:21 errors:0 dropped:0 overruns:0 frame:0
> TX packets:21 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:2352 (2.2 kb) TX bytes:2352 (2.2 kb)
>
> Any help is deeply appreciated.
>
> Thanks
>
>
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Change FEC and SCC1 sequence,But SCC1 not work?
2004-06-10 9:12 Change FEC and SCC1 sequence,But SCC1 not work? hjzgq
2004-06-10 16:52 ` Mark Chambers
@ 2004-06-10 17:17 ` Wolfgang Denk
1 sibling, 0 replies; 4+ messages in thread
From: Wolfgang Denk @ 2004-06-10 17:17 UTC (permalink / raw)
To: hjzgq; +Cc: linuxppc-embedded
In message <5357004.1086858754080.JavaMail.postfix@mx27.mail.sohu.com> you wrote:
>
> Briefly, my platform is MPC860T from Motorola. I'm using ppcboot 1.1.16
> to tftp the kernel 2.4.4 through FEC and then load NFS/RAMDISK. If I
> configure the kernel with only FEC, then everything works well(NFS
> works and ping through eth0 works). If I configure the kernel with both
> FEC(as eth0) and SCC1(as eth1),it works well too,but when I configure
> ther kernel with both SCC1(eth0) and FEC(as eth1) (net/setup.c)! . I
> try to ping out through FEC(eth1), I get ring buffer dumps and no ping
> response:
Please post the "Kernel command line" as printed when your kernel
boots. You did include a network device parameter in your ip= boot
argument, didn't you?
Best regards,
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd@denx.de
My challenge to the goto-less programmer is to recode tcp_input()
without any gotos ... without any loss of efficiency (there has to be
a catch). - W. R. Stevens
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Change FEC and SCC1 sequence,But SCC1 not work?
2004-06-11 6:22 hjzgq
@ 2004-06-11 16:02 ` Wolfgang Denk
0 siblings, 0 replies; 4+ messages in thread
From: Wolfgang Denk @ 2004-06-11 16:02 UTC (permalink / raw)
To: hjzgq; +Cc: linuxppc-embedded
In message <116411.1086934938680.JavaMail.postfix@mx27.mail.sohu.com> you wrote:
>
> My bootargs is "setenv bootargs root=/dev/ram ip=10.32.5.17:10.32.5.15::255.255.0.0:bug
> :::off"
> Today,I found fec device down when linux kernel running ,but I can see "eth1(fec ethernet)" status with "ifconfig" command,I checked linux kernel and found fec device down when kernel running.
>
> After debugging,I found linux kernel close the device when running "ip_auto_config()" function in "net/ipv4/ipconfig.c",then, I deleted "ic_open_devs()" funtions, AND EVERYING
> WORKS WELL!
But you are removing perfectly valid code. Don't do this!!
Just read the documentation (especially Documentation/nfsroot.txt)
and pass the CORRECT boot arguments, which in case or several network
interfaces MUST specify which interface to configure, i. e. the
minimum information is then
... ip=10.32.5.17:10.32.5.15::255.255.0.0:bug:eth0:off
[Note that your "ip=" string has one colon too many, too.]
Best regards,
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd@denx.de
Software suppliers are trying to make their software packages more
``user-friendly''. . . . Their best approach, so far, has been to
take all the old brochures, and stamp the words, ``user-friendly'' on
the cover. - Bill Gates
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2004-06-11 16:02 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2004-06-10 9:12 Change FEC and SCC1 sequence,But SCC1 not work? hjzgq
2004-06-10 16:52 ` Mark Chambers
2004-06-10 17:17 ` Wolfgang Denk
-- strict thread matches above, loose matches on Subject: below --
2004-06-11 6:22 hjzgq
2004-06-11 16:02 ` Wolfgang Denk
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).