From: Lorenz Kolb <linuxppcemb@lkmail.de>
To: linuxppc-embedded@ozlabs.org
Subject: Re: Virtex TEMAC 1000Mb/s trouble, but 100b/s is working
Date: Wed, 14 Nov 2007 05:10:57 -0800 (PST) [thread overview]
Message-ID: <13746324.post@talk.nabble.com> (raw)
In-Reply-To: <13743302.post@talk.nabble.com>
alex_snippet wrote:
>
> Hi all!
>
> I'm porting Linux for custom board based on Virtex4 FX, vanilla kernel
> 2.6.22.5 , Xilinx EDK 9.1 BSP,
> ELDK41 - cross-compiler
> target nfs-root pointed to ELDK41/ppc_4xx
>
> Kernel command line:
> Linux/PPC load: root=/dev/nfs rw console=ttyS0,9600
> nfsroot=192.168.0.1:/target
> ip=on
>
> All work successfully was done, i tested all at 100Mb's connection speed,
> but yesterday my customer said that with 1Gbit connection it did't work :(
> end of log following:
>
> 3.341532] eth0: XTemac: Options: 0xb8f2
> [ 11.855386] eth0: XTemac: We renegotiated the speed to: 1000
> [ 11.923237] eth0: XTemac: speed set to 1000Mb/s
> [ 13.000064] Sending DHCP requests ......, OK
> [ 65.484075] IP-Config: Got DHCP answer from 0.0.0.0, my address is
> 192.168.0.
> 192
> [ 65.573684] IP-Config: Complete:
> [ 65.610416] device=eth0, addr=192.168.0.192, mask=255.255.255.0,
> gw=192
> .168.0.1,
> [ 65.705572] host=192.168.0.192, domain=, nis-domain=(none),
> [ 65.777872] bootserver=0.0.0.0, rootserver=192.168.0.1, rootpath=
> [ 65.861982] Looking up port of RPC 100003/2 on 192.168.0.1
> [ 65.929093] Looking up port of RPC 100005/1 on 192.168.0.1
> [ 66.024134] VFS: Mounted root (nfs filesystem).
> [ 66.079160] Freeing unused kernel memory: 104k init
> [ 71.640314] nfs: server 192.168.0.1 not responding, still trying
> [ 76.040311] nfs: server 192.168.0.1 not responding, still trying
>
> Load process was friezed at this point. When connection speed is 100Mb/s
> everything is ok.
>
> Please advise me what to do, i tried to increase ppc core frequency from
> 100 to 300 MHz - the same problem.
> When i'm using virtual machine instead of real hardware it's working on
> 1000Gb/s :) but isn't on real hardware.
>
We have it working for our ML403. But we are not using the builtin-support
from the kernel.
We are using an initrd/initramfs for mounting the NFS (as this is much
easier for debugging (you can get a shell)).
alex_snippet wrote:
>
> I'm using Fedora 7 as a host.
>
We had problems with ubuntu as a host. Debian (Kernel 2.6.18) works fine for
us.
alex_snippet wrote:
>
> May be there are some nfs-demon settings?
>
we use
tcp,no_lock
here.
Regards,
Lorenz Kolb
ESIC-Solutions
--
View this message in context: http://www.nabble.com/Virtex-TEMAC-1000Mb-s-trouble%2C-but-100b-s-is-working-tf4803823.html#a13746324
Sent from the linuxppc-embedded mailing list archive at Nabble.com.
next prev parent reply other threads:[~2007-11-14 13:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-14 9:45 Virtex TEMAC 1000Mb/s trouble, but 100b/s is working alex_snippet
2007-11-14 12:03 ` schardt
2007-11-14 13:10 ` Lorenz Kolb [this message]
2007-11-14 15:44 ` alex_snippet
-- strict thread matches above, loose matches on Subject: below --
2007-11-14 16:36 g.schardt
2007-11-14 17:00 ` jozsef imrek
2007-11-14 17:01 g.schardt
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=13746324.post@talk.nabble.com \
--to=linuxppcemb@lkmail.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.