* xilinx Ml405 NFS mount problem
@ 2008-04-01 14:11 MingLiu
2008-04-01 14:29 ` John Linn
0 siblings, 1 reply; 10+ messages in thread
From: MingLiu @ 2008-04-01 14:11 UTC (permalink / raw)
To: linuxppc-embedded
[-- Attachment #1: Type: text/plain, Size: 8191 bytes --]
Dear friends,I am bringing up my kernel from Xilinx git tree. Unfortunately I met some
problem when mounting the root file system. Here is the information
listed. I will appreciate a lot if someone can help me out of the trouble.
Thanks a lot!
loaded at: 00400000 0059F19C
board data at: 0059D120 0059D19C
relocated to: 004050C8 00405144
zimage at: 00405F3F 0059C025
avail ram: 005A0000 08000000
Linux/PPC load: root=/dev/nfs
ip=192.168.0.4:192.168.0.3:192.168.0.3:255.255.255.0 rw
nfsroot=192.168.0.3:/home/mingliu/ml403_rootfs console=ttyUL0,38400
mem=32M
Uncompressing Linux...done.
Now booting the kernel
Linux version 2.6.24-rc8-xlnx-g1db182b8-dirty (mingliu@cca01) (gcc version
3.4.1) #7 Tue Apr 1 14:55:25 CEST 2008
Xilinx Generic PowerPC board support package (Xilinx ML405) (Virtex-4 FX)
Zone PFN ranges:
DMA 0 -> 8192
Normal 8192 -> 8192
HighMem 8192 -> 8192
Movable zone start PFN for each node
early_node_map[1] active PFN ranges
0: 0 -> 8192
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 8128
Kernel command line: root=/dev/nfs
ip=192.168.0.4:192.168.0.3:192.168.0.3:255.255.255.0 rw
nfsroot=192.168.0.3:/home/mingliu/ml403_rootfs console=ttyUL0,38400
mem=32M
Xilinx INTC #0 at 0x81800000 mapped to 0xFDFFF000
PID hash table entries: 128 (order: 7, 512 bytes)
Console: colour dummy device 80x25
Dentry cache hash table entries: 4096 (order: 2, 16384 bytes)
Inode-cache hash table entries: 2048 (order: 1, 8192 bytes)
Memory: 28884k available (2552k kernel code, 944k data, 84k init, 0k highmem)
SLUB: Genslabs=11, HWalign=32, Order=0-1, MinObjects=4, CPUs=1, Nodes=1
Mount-cache hash table entries: 512
net_namespace: 64 bytes
NET: Registered protocol family 16
Registering device uartlite:0
Fixup MAC address for xilinx_lltemac:0
Registering device xilinx_lltemac:0
NET: Registered protocol family 2
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
TCP established hash table entries: 1024 (order: 1, 8192 bytes)
TCP bind hash table entries: 1024 (order: 0, 4096 bytes)
TCP: Hash tables configured (established 1024 bind 1024)
TCP reno registered
sysctl table check failed: /kernel/l2cr .1.31 Missing strategy
Call Trace:
[c1c0fe50] [c0008b70] show_stack+0x40/0x194 (unreliable)
[c1c0fe90] [c003aed4] set_fail+0x68/0x80
[c1c0feb0] [c003b4ec] sysctl_check_table+0x600/0x77c
[c1c0fef0] [c003b4d4] sysctl_check_table+0x5e8/0x77c
[c1c0ff30] [c002605c] register_sysctl_table+0x64/0xb4
[c1c0ff50] [c034579c] register_ppc_htab_sysctl+0x18/0x2c
[c1c0ff60] [c034482c] kernel_init+0x94/0x2bc
[c1c0fff0] [c0004d58] kernel_thread+0x44/0x60
Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
fuse init (API version 7.9)
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered (default)
uartlite.0: ttyUL0 at MMIO 0x84000003 (irq = 3) is a uartlite
console [ttyUL0] enabled
loop: module loaded
nbd: registered device at major 43
xilinx_lltemac xilinx_lltemac.0: MAC address is now 0: a:35: 1: 2: 3
xilinx_lltemac xilinx_lltemac.0: XLlTemac: using DMA mode.
XLlTemac: Dma base address: phy: 0x84600100, virt: 0xc3008100
XLlTemac: buffer descriptor size: 32768 (0x8000)
XLlTemac: Allocating DMA descriptors with kmalloc<6>XLlTemac:
(buffer_descriptor_init) phy: 0x1d18000, virt: 0xc1d18000, size: 0x8000
XTemac: PHY detected at address 7.
xilinx_lltemac xilinx_lltemac.0: eth0: Xilinx TEMAC at 0x81C00000 mapped
to 0xC3004000, irq=2
console [netcon0] enabled
Linux version 2.6.24-rc8-xlnx-g1db182b8-dirty (mingliu@cca01) (gcc version
3.4.1) #7 Tue Apr 1 14:55:25 CEST 2008
Xilinx Generic PowerPC board support package (Xilinx ML405) (Virtex-4 FX)
Zone PFN ranges:
DMA 0 -> 8192
Normal 8192 -> 8192
HighMem 8192 -> 8192
Movable zone start PFN for each node
early_node_map[1] active PFN ranges
0: 0 -> 8192
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 8128
Kernel command line: root=/dev/nfs
ip=192.168.0.4:192.168.0.3:192.168.0.3:255.255.255.0 rw
nfsroot=192.168.0.3:/home/mingliu/ml403_rootfs console=ttyUL0,38400
mem=32M
Xilinx INTC #0 at 0x81800000 mapped to 0xFDFFF000
PID hash table entries: 128 (order: 7, 512 bytes)
Console: colour dummy device 80x25
Dentry cache hash table entries: 4096 (order: 2, 16384 bytes)
Inode-cache hash table entries: 2048 (order: 1, 8192 bytes)
Memory: 28884k available (2552k kernel code, 944k data, 84k init, 0k highmem)
SLUB: Genslabs=11, HWalign=32, Order=0-1, MinObjects=4, CPUs=1, Nodes=1
Mount-cache hash table entries: 512
net_namespace: 64 bytes
NET: Registered protocol family 16
Registering device uartlite:0
Fixup MAC address for xilinx_lltemac:0
Registering device xilinx_lltemac:0
NET: Registered protocol family 2
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
TCP established hash table entries: 1024 (order: 1, 8192 bytes)
TCP bind hash table entries: 1024 (order: 0, 4096 bytes)
TCP: Hash tables configured (established 1024 bind 1024)
TCP reno registered
sysctl table check failed: /kernel/l2cr .1.31 Missing strategy
Call Trace:
[c1c0fe50] [c0008b70] show_stack+0x40/0x194 (unreliable)
[c1c0fe90] [c003aed4] set_fail+0x68/0x80
[c1c0feb0] [c003b4ec] sysctl_check_table+0x600/0x77c
[c1c0fef0] [c003b4d4] sysctl_check_table+0x5e8/0x77c
[c1c0ff30] [c002605c] register_sysctl_table+0x64/0xb4
[c1c0ff50] [c034579c] register_ppc_htab_sysctl+0x18/0x2c
[c1c0ff60] [c034482c] kernel_init+0x94/0x2bc
[c1c0fff0] [c0004d58] kernel_thread+0x44/0x60
Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
fuse init (API version 7.9)
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered (default)
uartlite.0: ttyUL0 at MMIO 0x84000003 (irq = 3) is a uartlite
console [ttyUL0] enabled
loop: module loaded
nbd: registered device at major 43
xilinx_lltemac xilinx_lltemac.0: MAC address is now 0: a:35: 1: 2: 3
xilinx_lltemac xilinx_lltemac.0: XLlTemac: using DMA mode.
XLlTemac: Dma base address: phy: 0x84600100, virt: 0xc3008100
XLlTemac: buffer descriptor size: 32768 (0x8000)
XLlTemac: Allocating DMA descriptors with kmalloc<6>XLlTemac:
(buffer_descriptor_init) phy: 0x1d18000, virt: 0xc1d18000, size: 0x8000
XTemac: PHY detected at address 7.
xilinx_lltemac xilinx_lltemac.0: eth0: Xilinx TEMAC at 0x81C00000 mapped
to 0xC3004000, irq=2
console [netcon0] enabled
netconsole: network logging started
Generic platform RAM MTD, (c) 2004 Simtec Electronics
mice: PS/2 mouse device common for all mice
TCP cubic registered
NET: Registered protocol family 1
NET: Registered protocol family 17
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
eth0: XLlTemac: Options: 0x3fa
eth0: XLlTemac: allocating interrupt 0 for dma mode tx.
eth0: XLlTemac: allocating interrupt 1 for dma mode rx.
eth0: XLlTemac: speed set to 1000Mb/s
eth0: XLlTemac: Send Threshold = 24, Receive Threshold = 4
eth0: XLlTemac: Send Wait bound = 254, Receive Wait bound = 254
IP-Config: Complete:
device=eth0, addr=192.168.0.4, mask=255.255.255.0, gw=192.168.0.3,
host=192.168.0.4, domain=, nis-domain=(none),
bootserver=192.168.0.3, rootserver=192.168.0.3, rootpath=
Looking up port of RPC 100003/2 on 192.168.0.3
rpcbind: server 192.168.0.3 not responding, timed out
Root-NFS: Unable to get nfsd port number from server, using default
Looking up port of RPC 100005/1 on 192.168.0.3
rpcbind: server 192.168.0.3 not responding, timed out
Root-NFS: Unable to get mountd port number from server, using default
mount: server 192.168.0.3 not responding, timed out
Root-NFS: Server returned error -5 while mounting /home/mingliu/ml403_rootfs
VFS: Unable to mount root fs via NFS, trying floppy.
VFS: Cannot open root device "nfs" or unknown-block(2,0)
Please append a correct "root=" boot option; here are the available
partitions:
Kernel panic - not syncing: VFS: Unable to mount root fs on
unknown-block(2,0)
Rebooting in 180 seconds..
BR
Ming
_________________________________________________________________
用手机MSN聊天写邮件看空间，无限沟通，分享精彩！
http://mobile.msn.com.cn/
[-- Attachment #2: Type: text/html, Size: 8675 bytes --]
^ permalink raw reply [flat|nested] 10+ messages in thread
* RE: xilinx Ml405 NFS mount problem
2008-04-01 14:11 xilinx Ml405 NFS mount problem MingLiu
@ 2008-04-01 14:29 ` John Linn
2008-04-01 16:15 ` MingLiu
0 siblings, 1 reply; 10+ messages in thread
From: John Linn @ 2008-04-01 14:29 UTC (permalink / raw)
To: MingLiu, linuxppc-embedded
[-- Attachment #1: Type: text/plain, Size: 9588 bytes --]
Hi Ming,
It’s not obvious to me what the problem is as I don’t see any driver failures. Have you tried using a ramdisk and then seeing if the network is working before using NFS root?
And I’m assuming you have used the NFS root before so you know that it’s good for sure.
I test on the ML405 with NFS root and haven’t seen this problem, but my setup is a little different. I use DHCP rather than a static IP, but other than that it’s similar.
I’m assuming that you accidentally got 2 different powerup outputs in the message below as the 1st stops and a 2nd starts in the middle.
How long has it been since you pulled from the Xilinx Git tree?
Thanks,
John
________________________________
From: linuxppc-embedded-bounces+john.linn=xilinx.com@ozlabs.org [mailto:linuxppc-embedded-bounces+john.linn=xilinx.com@ozlabs.org] On Behalf Of MingLiu
Sent: Tuesday, April 01, 2008 8:12 AM
To: linuxppc-embedded@ozlabs.org
Subject: xilinx Ml405 NFS mount problem
Dear friends,
I am bringing up my kernel from Xilinx git tree. Unfortunately I met some
problem when mounting the root file system. Here is the information
listed. I will appreciate a lot if someone can help me out of the trouble.
Thanks a lot!
loaded at: 00400000 0059F19C
board data at: 0059D120 0059D19C
relocated to: 004050C8 00405144
zimage at: 00405F3F 0059C025
avail ram: 005A0000 08000000
Linux/PPC load: root=/dev/nfs
ip=192.168.0.4:192.168.0.3:192.168.0.3:255.255.255.0 rw
nfsroot=192.168.0.3:/home/mingliu/ml403_rootfs console=ttyUL0,38400
mem=32M
Uncompressing Linux...done.
Now booting the kernel
Linux version 2.6.24-rc8-xlnx-g1db182b8-dirty (mingliu@cca01) (gcc version
3.4.1) #7 Tue Apr 1 14:55:25 CEST 2008
Xilinx Generic PowerPC board support package (Xilinx ML405) (Virtex-4 FX)
Zone PFN ranges:
DMA 0 -> 8192
Normal 8192 -> 8192
HighMem 8192 -> 8192
Movable zone start PFN for each node
early_node_map[1] active PFN ranges
0: 0 -> 8192
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 8128
Kernel command line: root=/dev/nfs
ip=192.168.0.4:192.168.0.3:192.168.0.3:255.255.255.0 rw
nfsroot=192.168.0.3:/home/mingliu/ml403_rootfs console=ttyUL0,38400
mem=32M
Xilinx INTC #0 at 0x81800000 mapped to 0xFDFFF000
PID hash table entries: 128 (order: 7, 512 bytes)
Console: colour dummy device 80x25
Dentry cache hash table entries: 4096 (order: 2, 16384 bytes)
Inode-cache hash table entries: 2048 (order: 1, 8192 bytes)
Memory: 28884k available (2552k kernel code, 944k data, 84k init, 0k highmem)
SLUB: Genslabs=11, HWalign=32, Order=0-1, MinObjects=4, CPUs=1, Nodes=1
Mount-cache hash table entries: 512
net_namespace: 64 bytes
NET: Registered protocol family 16
Registering device uartlite:0
Fixup MAC address for xilinx_lltemac:0
Registering device xilinx_lltemac:0
NET: Registered protocol family 2
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
TCP established hash table entries: 1024 (order: 1, 8192 bytes)
TCP bind hash table entries: 1024 (order: 0, 4096 bytes)
TCP: Hash tables configured (established 1024 bind 1024)
TCP reno registered
sysctl table check failed: /kernel/l2cr .1.31 Missing strategy
Call Trace:
[c1c0fe50] [c0008b70] show_stack+0x40/0x194 (unreliable)
[c1c0fe90] [c003aed4] set_fail+0x68/0x80
[c1c0feb0] [c003b4ec] sysctl_check_table+0x600/0x77c
[c1c0fef0] [c003b4d4] sysctl_check_table+0x5e8/0x77c
[c1c0ff30] [c002605c] register_sysctl_table+0x64/0xb4
[c1c0ff50] [c034579c] register_ppc_htab_sysctl+0x18/0x2c
[c1c0ff60] [c034482c] kernel_init+0x94/0x2bc
[c1c0fff0] [c0004d58] kernel_thread+0x44/0x60
Installing knfsd (copyright (C) 1996 okir@monad.swb.de <https://webmail.sys.kth.se/src/compose.php?send_to=okir%40monad.swb.de> ).
fuse init (API version 7.9)
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered (default)
uartlite.0: ttyUL0 at MMIO 0x84000003 (irq = 3) is a uartlite
console [ttyUL0] enabled
loop: module loaded
nbd: registered device at major 43
xilinx_lltemac xilinx_lltemac.0: MAC address is now 0: a:35: 1: 2: 3
xilinx_lltemac xilinx_lltemac.0: XLlTemac: using DMA mode.
XLlTemac: Dma base address: phy: 0x84600100, virt: 0xc3008100
XLlTemac: buffer descriptor size: 32768 (0x8000)
XLlTemac: Allocating DMA descriptors with kmalloc<6>XLlTemac:
(buffer_descriptor_init) phy: 0x1d18000, virt: 0xc1d18000, size: 0x8000
XTemac: PHY detected at address 7.
xilinx_lltemac xilinx_lltemac.0: eth0: Xilinx TEMAC at 0x81C00000 mapped
to 0xC3004000, irq=2
console [netcon0] enabled
Linux version 2.6.24-rc8-xlnx-g1db182b8-dirty (mingliu@cca01) (gcc version
3.4.1) #7 Tue Apr 1 14:55:25 CEST 2008
Xilinx Generic PowerPC board support package (Xilinx ML405) (Virtex-4 FX)
Zone PFN ranges:
DMA 0 -> 8192
Normal 8192 -> 8192
HighMem 8192 -> 8192
Movable zone start PFN for each node
early_node_map[1] active PFN ranges
0: 0 -> 8192
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 8128
Kernel command line: root=/dev/nfs
ip=192.168.0.4:192.168.0.3:192.168.0.3:255.255.255.0 rw
nfsroot=192.168.0.3:/home/mingliu/ml403_rootfs console=ttyUL0,38400
mem=32M
Xilinx INTC #0 at 0x81800000 mapped to 0xFDFFF000
PID hash table entries: 128 (order: 7, 512 bytes)
Console: colour dummy device 80x25
Dentry cache hash table entries: 4096 (order: 2, 16384 bytes)
Inode-cache hash table entries: 2048 (order: 1, 8192 bytes)
Memory: 28884k available (2552k kernel code, 944k data, 84k init, 0k highmem)
SLUB: Genslabs=11, HWalign=32, Order=0-1, MinObjects=4, CPUs=1, Nodes=1
Mount-cache hash table entries: 512
net_namespace: 64 bytes
NET: Registered protocol family 16
Registering device uartlite:0
Fixup MAC address for xilinx_lltemac:0
Registering device xilinx_lltemac:0
NET: Registered protocol family 2
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
TCP established hash table entries: 1024 (order: 1, 8192 bytes)
TCP bind hash table entries: 1024 (order: 0, 4096 bytes)
TCP: Hash tables configured (established 1024 bind 1024)
TCP reno registered
sysctl table check failed: /kernel/l2cr .1.31 Missing strategy
Call Trace:
[c1c0fe50] [c0008b70] show_stack+0x40/0x194 (unreliable)
[c1c0fe90] [c003aed4] set_fail+0x68/0x80
[c1c0feb0] [c003b4ec] sysctl_check_table+0x600/0x77c
[c1c0fef0] [c003b4d4] sysctl_check_table+0x5e8/0x77c
[c1c0ff30] [c002605c] register_sysctl_table+0x64/0xb4
[c1c0ff50] [c034579c] register_ppc_htab_sysctl+0x18/0x2c
[c1c0ff60] [c034482c] kernel_init+0x94/0x2bc
[c1c0fff0] [c0004d58] kernel_thread+0x44/0x60
Installing knfsd (copyright (C) 1996 okir@monad.swb.de <https://webmail.sys.kth.se/src/compose.php?send_to=okir%40monad.swb.de> ).
fuse init (API version 7.9)
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered (default)
uartlite.0: ttyUL0 at MMIO 0x84000003 (irq = 3) is a uartlite
console [ttyUL0] enabled
loop: module loaded
nbd: registered device at major 43
xilinx_lltemac xilinx_lltemac.0: MAC address is now 0: a:35: 1: 2: 3
xilinx_lltemac xilinx_lltemac.0: XLlTemac: using DMA mode.
XLlTemac: Dma base address: phy: 0x84600100, virt: 0xc3008100
XLlTemac: buffer descriptor size: 32768 (0x8000)
XLlTemac: Allocating DMA descriptors with kmalloc<6>XLlTemac:
(buffer_descriptor_init) phy: 0x1d18000, virt: 0xc1d18000, size: 0x8000
XTemac: PHY detected at address 7.
xilinx_lltemac xilinx_lltemac.0: eth0: Xilinx TEMAC at 0x81C00000 mapped
to 0xC3004000, irq=2
console [netcon0] enabled
netconsole: network logging started
Generic platform RAM MTD, (c) 2004 Simtec Electronics
mice: PS/2 mouse device common for all mice
TCP cubic registered
NET: Registered protocol family 1
NET: Registered protocol family 17
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
eth0: XLlTemac: Options: 0x3fa
eth0: XLlTemac: allocating interrupt 0 for dma mode tx.
eth0: XLlTemac: allocating interrupt 1 for dma mode rx.
eth0: XLlTemac: speed set to 1000Mb/s
eth0: XLlTemac: Send Threshold = 24, Receive Threshold = 4
eth0: XLlTemac: Send Wait bound = 254, Receive Wait bound = 254
IP-Config: Complete:
device=eth0, addr=192.168.0.4, mask=255.255.255.0, gw=192.168.0.3,
host=192.168.0.4, domain=, nis-domain=(none),
bootserver=192.168.0.3, rootserver=192.168.0.3, rootpath=
Looking up port of RPC 100003/2 on 192.168.0.3
rpcbind: server 192.168.0.3 not responding, timed out
Root-NFS: Unable to get nfsd port number from server, using default
Looking up port of RPC 100005/1 on 192.168.0.3
rpcbind: server 192.168.0.3 not responding, timed out
Root-NFS: Unable to get mountd port number from server, using default
mount: server 192.168.0.3 not responding, timed out
Root-NFS: Server returned error -5 while mounting /home/mingliu/ml403_rootfs
VFS: Unable to mount root fs via NFS, trying floppy.
VFS: Cannot open root device "nfs" or unknown-block(2,0)
Please append a correct "root=" boot option; here are the available
partitions:
Kernel panic - not syncing: VFS: Unable to mount root fs on
unknown-block(2,0)
Rebooting in 180 seconds..
BR
Ming
________________________________
Windows Live Writer，支持离线撰写博客内容，随时随地想写就写。 立即使用！ <http://get.live.cn/product/writer.html>
[-- Attachment #2: Type: text/html, Size: 38864 bytes --]
^ permalink raw reply [flat|nested] 10+ messages in thread
* RE: xilinx Ml405 NFS mount problem
2008-04-01 14:29 ` John Linn
@ 2008-04-01 16:15 ` MingLiu
2008-04-01 16:50 ` Robert Woodworth
0 siblings, 1 reply; 10+ messages in thread
From: MingLiu @ 2008-04-01 16:15 UTC (permalink / raw)
To: John Linn, linuxppc-embedded
[-- Attachment #1: Type: text/plain, Size: 9819 bytes --]
Dear John,
Thank you for your replying.
>It’s not obvious to me what the problem is as I don’t see any driver failures. Have you >tried using a ramdisk and then seeing if the network is working before using NFS root?
Not yet. I will try it soon. However from the information on the LL_TEMAC, it seems everything is fine and it should work.
>And I’m assuming you have used the NFS root before so you know that it’s good for sure.
>I test on the ML405 with NFS root and haven’t seen this problem, but my setup is a little different. I use DHCP rather than >a static IP, but other than that it’s similar.
Yes. I used NFS before. I can make sure my NFS server works well. Also in principle, static IP should get a same result as DHCP, I think.
>How long has it been since you pulled from the Xilinx Git tree?
I just pulled the Xilinx tree quite recently. I am using a latest kernel.
BR
Ming
And I’m assuming you have used the NFS root before so you know that it’s good for sure.
I test on the ML405 with NFS root and haven’t seen this problem, but my setup is a little different. I use DHCP rather than a static IP, but other than that it’s similar.
I’m assuming that you accidentally got 2 different powerup outputs in the message below as the 1st stops and a 2nd starts in the middle.
How long has it been since you pulled from the Xilinx Git tree?
Thanks,
John
From: linuxppc-embedded-bounces+john.linn=xilinx.com@ozlabs.org [mailto:linuxppc-embedded-bounces+john.linn=xilinx.com@ozlabs.org] On Behalf Of MingLiuSent: Tuesday, April 01, 2008 8:12 AMTo: linuxppc-embedded@ozlabs.orgSubject: xilinx Ml405 NFS mount problem
Dear friends,I am bringing up my kernel from Xilinx git tree. Unfortunately I met someproblem when mounting the root file system. Here is the informationlisted. I will appreciate a lot if someone can help me out of the trouble. Thanks a lot! loaded at: 00400000 0059F19Cboard data at: 0059D120 0059D19Crelocated to: 004050C8 00405144zimage at: 00405F3F 0059C025avail ram: 005A0000 08000000 Linux/PPC load: root=/dev/nfsip=192.168.0.4:192.168.0.3:192.168.0.3:255.255.255.0 rwnfsroot=192.168.0.3:/home/mingliu/ml403_rootfs console=ttyUL0,38400mem=32MUncompressing Linux...done.Now booting the kernelLinux version 2.6.24-rc8-xlnx-g1db182b8-dirty (mingliu@cca01) (gcc version3.4.1) #7 Tue Apr 1 14:55:25 CEST 2008Xilinx Generic PowerPC board support package (Xilinx ML405) (Virtex-4 FX)Zone PFN ranges: DMA 0 -> 8192 Normal 8192 -> 8192 HighMem 8192 -> 8192Movable zone start PFN for each nodeearly_node_map[1] active PFN ranges 0: 0 -> 8192Built 1 zonelists in Zone order, mobility grouping on. Total pages: 8128Kernel command line: root=/dev/nfsip=192.168.0.4:192.168.0.3:192.168.0.3:255.255.255.0 rwnfsroot=192.168.0.3:/home/mingliu/ml403_rootfs console=ttyUL0,38400mem=32MXilinx INTC #0 at 0x81800000 mapped to 0xFDFFF000PID hash table entries: 128 (order: 7, 512 bytes)Console: colour dummy device 80x25Dentry cache hash table entries: 4096 (order: 2, 16384 bytes)Inode-cache hash table entries: 2048 (order: 1, 8192 bytes)Memory: 28884k available (2552k kernel code, 944k data, 84k init, 0k highmem)SLUB: Genslabs=11, HWalign=32, Order=0-1, MinObjects=4, CPUs=1, Nodes=1Mount-cache hash table entries: 512net_namespace: 64 bytesNET: Registered protocol family 16Registering device uartlite:0Fixup MAC address for xilinx_lltemac:0Registering device xilinx_lltemac:0NET: Registered protocol family 2IP route cache hash table entries: 1024 (order: 0, 4096 bytes)TCP established hash table entries: 1024 (order: 1, 8192 bytes)TCP bind hash table entries: 1024 (order: 0, 4096 bytes)TCP: Hash tables configured (established 1024 bind 1024)TCP reno registeredsysctl table check failed: /kernel/l2cr .1.31 Missing strategyCall Trace:[c1c0fe50] [c0008b70] show_stack+0x40/0x194 (unreliable)[c1c0fe90] [c003aed4] set_fail+0x68/0x80[c1c0feb0] [c003b4ec] sysctl_check_table+0x600/0x77c[c1c0fef0] [c003b4d4] sysctl_check_table+0x5e8/0x77c[c1c0ff30] [c002605c] register_sysctl_table+0x64/0xb4[c1c0ff50] [c034579c] register_ppc_htab_sysctl+0x18/0x2c[c1c0ff60] [c034482c] kernel_init+0x94/0x2bc[c1c0fff0] [c0004d58] kernel_thread+0x44/0x60Installing knfsd (copyright (C) 1996 okir@monad.swb.de).fuse init (API version 7.9)io scheduler noop registeredio scheduler anticipatory registeredio scheduler deadline registeredio scheduler cfq registered (default)uartlite.0: ttyUL0 at MMIO 0x84000003 (irq = 3) is a uartliteconsole [ttyUL0] enabledloop: module loadednbd: registered device at major 43xilinx_lltemac xilinx_lltemac.0: MAC address is now 0: a:35: 1: 2: 3xilinx_lltemac xilinx_lltemac.0: XLlTemac: using DMA mode.XLlTemac: Dma base address: phy: 0x84600100, virt: 0xc3008100XLlTemac: buffer descriptor size: 32768 (0x8000)XLlTemac: Allocating DMA descriptors with kmalloc<6>XLlTemac:(buffer_descriptor_init) phy: 0x1d18000, virt: 0xc1d18000, size: 0x8000XTemac: PHY detected at address 7.xilinx_lltemac xilinx_lltemac.0: eth0: Xilinx TEMAC at 0x81C00000 mappedto 0xC3004000, irq=2console [netcon0] enabledLinux version 2.6.24-rc8-xlnx-g1db182b8-dirty (mingliu@cca01) (gcc version3.4.1) #7 Tue Apr 1 14:55:25 CEST 2008Xilinx Generic PowerPC board support package (Xilinx ML405) (Virtex-4 FX)Zone PFN ranges: DMA 0 -> 8192 Normal 8192 -> 8192 HighMem 8192 -> 8192Movable zone start PFN for each nodeearly_node_map[1] active PFN ranges 0: 0 -> 8192Built 1 zonelists in Zone order, mobility grouping on. Total pages: 8128Kernel command line: root=/dev/nfsip=192.168.0.4:192.168.0.3:192.168.0.3:255.255.255.0 rwnfsroot=192.168.0.3:/home/mingliu/ml403_rootfs console=ttyUL0,38400mem=32MXilinx INTC #0 at 0x81800000 mapped to 0xFDFFF000PID hash table entries: 128 (order: 7, 512 bytes)Console: colour dummy device 80x25Dentry cache hash table entries: 4096 (order: 2, 16384 bytes)Inode-cache hash table entries: 2048 (order: 1, 8192 bytes)Memory: 28884k available (2552k kernel code, 944k data, 84k init, 0k highmem)SLUB: Genslabs=11, HWalign=32, Order=0-1, MinObjects=4, CPUs=1, Nodes=1Mount-cache hash table entries: 512net_namespace: 64 bytesNET: Registered protocol family 16Registering device uartlite:0Fixup MAC address for xilinx_lltemac:0Registering device xilinx_lltemac:0NET: Registered protocol family 2IP route cache hash table entries: 1024 (order: 0, 4096 bytes)TCP established hash table entries: 1024 (order: 1, 8192 bytes)TCP bind hash table entries: 1024 (order: 0, 4096 bytes)TCP: Hash tables configured (established 1024 bind 1024)TCP reno registeredsysctl table check failed: /kernel/l2cr .1.31 Missing strategyCall Trace:[c1c0fe50] [c0008b70] show_stack+0x40/0x194 (unreliable)[c1c0fe90] [c003aed4] set_fail+0x68/0x80[c1c0feb0] [c003b4ec] sysctl_check_table+0x600/0x77c[c1c0fef0] [c003b4d4] sysctl_check_table+0x5e8/0x77c[c1c0ff30] [c002605c] register_sysctl_table+0x64/0xb4[c1c0ff50] [c034579c] register_ppc_htab_sysctl+0x18/0x2c[c1c0ff60] [c034482c] kernel_init+0x94/0x2bc[c1c0fff0] [c0004d58] kernel_thread+0x44/0x60Installing knfsd (copyright (C) 1996 okir@monad.swb.de).fuse init (API version 7.9)io scheduler noop registeredio scheduler anticipatory registeredio scheduler deadline registeredio scheduler cfq registered (default)uartlite.0: ttyUL0 at MMIO 0x84000003 (irq = 3) is a uartliteconsole [ttyUL0] enabledloop: module loadednbd: registered device at major 43xilinx_lltemac xilinx_lltemac.0: MAC address is now 0: a:35: 1: 2: 3xilinx_lltemac xilinx_lltemac.0: XLlTemac: using DMA mode.XLlTemac: Dma base address: phy: 0x84600100, virt: 0xc3008100XLlTemac: buffer descriptor size: 32768 (0x8000)XLlTemac: Allocating DMA descriptors with kmalloc<6>XLlTemac:(buffer_descriptor_init) phy: 0x1d18000, virt: 0xc1d18000, size: 0x8000XTemac: PHY detected at address 7.xilinx_lltemac xilinx_lltemac.0: eth0: Xilinx TEMAC at 0x81C00000 mappedto 0xC3004000, irq=2console [netcon0] enablednetconsole: network logging startedGeneric platform RAM MTD, (c) 2004 Simtec Electronicsmice: PS/2 mouse device common for all miceTCP cubic registeredNET: Registered protocol family 1NET: Registered protocol family 17RPC: Registered udp transport module.RPC: Registered tcp transport module.eth0: XLlTemac: Options: 0x3faeth0: XLlTemac: allocating interrupt 0 for dma mode tx.eth0: XLlTemac: allocating interrupt 1 for dma mode rx.eth0: XLlTemac: speed set to 1000Mb/seth0: XLlTemac: Send Threshold = 24, Receive Threshold = 4eth0: XLlTemac: Send Wait bound = 254, Receive Wait bound = 254IP-Config: Complete: device=eth0, addr=192.168.0.4, mask=255.255.255.0, gw=192.168.0.3, host=192.168.0.4, domain=, nis-domain=(none), bootserver=192.168.0.3, rootserver=192.168.0.3, rootpath=Looking up port of RPC 100003/2 on 192.168.0.3rpcbind: server 192.168.0.3 not responding, timed outRoot-NFS: Unable to get nfsd port number from server, using defaultLooking up port of RPC 100005/1 on 192.168.0.3rpcbind: server 192.168.0.3 not responding, timed outRoot-NFS: Unable to get mountd port number from server, using defaultmount: server 192.168.0.3 not responding, timed outRoot-NFS: Server returned error -5 while mounting /home/mingliu/ml403_rootfsVFS: Unable to mount root fs via NFS, trying floppy.VFS: Cannot open root device "nfs" or unknown-block(2,0)Please append a correct "root=" boot option; here are the availablepartitions:Kernel panic - not syncing: VFS: Unable to mount root fs onunknown-block(2,0)Rebooting in 180 seconds.. BRMing
Windows Live Writer，支持离线撰写博客内容，随时随地想写就写。 立即使用！
_________________________________________________________________
Windows Live Photo gallery 数码相机的超级伴侣，轻松管理和编辑照片，还能制作全景美图！
http://get.live.cn/product/photo.html
[-- Attachment #2: Type: text/html, Size: 32977 bytes --]
^ permalink raw reply [flat|nested] 10+ messages in thread
* RE: xilinx Ml405 NFS mount problem
2008-04-01 16:15 ` MingLiu
@ 2008-04-01 16:50 ` Robert Woodworth
2008-04-01 16:53 ` John Linn
` (2 more replies)
0 siblings, 3 replies; 10+ messages in thread
From: Robert Woodworth @ 2008-04-01 16:50 UTC (permalink / raw)
To: MingLiu; +Cc: John Linn, linuxppc-embedded
I think you may be suffering from the latest LL_TEMAC packet loss
problem. (NFS/UDP really does not like packet loss)
Let me guess.
You are using a base system from "Base System Builder Wizard"?
EDK 9.2i. Default syntheses/P&R options.
I have seen a massive packet loss problems on my ML403 and two other
boards I have with an FX60.
This is probably a hardware problem.
Xilinx has acknowledged an LL_TEMAC problem to me but has not provided a
fix. I have heard that things are better with EDK/ISE-10.1 but I have
not tested it.
The vendor of one of my boards (Pico) has fixed the problem on the FX60
by highly constraining the timing of the LL_TEMAC in map/PR. On my
ML403 I used similar constraints and it fixed the problem, but only if
the device is plugged into a GigE switch. The problem is still there
with the same .bit file on a 100-T switch.
Are you on a GigE switch?
Rob.
On Tue, 2008-04-01 at 16:15 +0000, MingLiu wrote:
> Dear John,
>
> Thank you for your replying.
>
> >It’s not obvious to me what the problem is as I don’t see any driver
> failures. Have you >tried using a ramdisk and then seeing if the
> network is working before using NFS root?
>
> Not yet. I will try it soon. However from the information on the
> LL_TEMAC, it seems everything is fine and it should work.
>
>
>
> >And I’m assuming you have used the NFS root before so you know that
> it’s good for sure.
>
>
>
> >I test on the ML405 with NFS root and haven’t seen this problem, but
> my setup is a little different. I use DHCP rather than >a static IP,
> but other than that it’s similar.
>
>
>
> Yes. I used NFS before. I can make sure my NFS server works well. Also
> in principle, static IP should get a same result as DHCP, I think.
>
>
>
> >How long has it been since you pulled from the Xilinx Git tree?
>
>
>
> I just pulled the Xilinx tree quite recently. I am using a latest
> kernel.
>
>
>
> BR
>
> Ming
>
>
>
>
>
> And I’m assuming you have used the NFS root before so you know
> that it’s good for sure.
>
>
>
> I test on the ML405 with NFS root and haven’t seen this
> problem, but my setup is a little different. I use DHCP
> rather than a static IP, but other than that it’s similar.
>
>
>
> I’m assuming that you accidentally got 2 different powerup
> outputs in the message below as the 1st stops and a 2nd starts
> in the middle.
>
>
>
> How long has it been since you pulled from the Xilinx Git
> tree?
>
>
>
> Thanks,
>
> John
>
>
>
>
> ______________________________________________________________
> From: linuxppc-embedded-bounces
> +john.linn=xilinx.com@ozlabs.org
> [mailto:linuxppc-embedded-bounces
> +john.linn=xilinx.com@ozlabs.org] On Behalf Of MingLiu
> Sent: Tuesday, April 01, 2008 8:12 AM
> To: linuxppc-embedded@ozlabs.org
> Subject: xilinx Ml405 NFS mount problem
>
>
>
>
> Dear friends,
>
> I am bringing up my kernel from Xilinx git tree. Unfortunately I met some
> problem when mounting the root file system. Here is the information
> listed. I will appreciate a lot if someone can help me out of the trouble.
> Thanks a lot!
>
>
> loaded at: 00400000 0059F19C
> board data at: 0059D120 0059D19C
> relocated to: 004050C8 00405144
> zimage at: 00405F3F 0059C025
> avail ram: 005A0000 08000000
>
> Linux/PPC load: root=/dev/nfs
> ip=192.168.0.4:192.168.0.3:192.168.0.3:255.255.255.0 rw
> nfsroot=192.168.0.3:/home/mingliu/ml403_rootfs console=ttyUL0,38400
> mem=32M
> Uncompressing Linux...done.
> Now booting the kernel
> Linux version 2.6.24-rc8-xlnx-g1db182b8-dirty (mingliu@cca01) (gcc version
> 3.4.1) #7 Tue Apr 1 14:55:25 CEST 2008
> Xilinx Generic PowerPC board support package (Xilinx ML405) (Virtex-4 FX)
> Zone PFN ranges:
> DMA 0 -> 8192
>
> Normal 8192 -> 8192
>
> HighMem 8192 -> 8192
> Movable zone start PFN for each node
> early_node_map[1] active PFN ranges
> 0: 0 -> 8192
> Built 1 zonelists in Zone order, mobility grouping on. Total pages: 8128
> Kernel command line: root=/de v/nfs
> ip=192.168.0.4:192.168.0.3:192.168.0.3:255.255.255.0 rw
> nfsroot=192.168.0.3:/home/mingliu/ml403_rootfs console=ttyUL0,38400
> mem=32M
> Xilinx INTC #0 at 0x81800000 mapped to 0xFDFFF000
> PID hash table entries: 128 (order: 7, 512 bytes)
> Console: colour dummy device 80x25
> Dentry cache hash table entries: 4096 (order: 2, 16384 bytes)
> Inode-cache hash table entries: 2048 (order: 1, 8192 bytes)
> Memory: 28884k available (2552k kernel code, 944k data, 84k init, 0k highmem)
> SLUB: Genslabs=11, HWalign=32, Order=0-1, MinObjects=4, CPUs=1, Nodes=1
> Mount-cache hash table entries: 512
> net_namespace: 64 bytes
> NET: Registered protocol family 16
> Registering device uartlite:0
> Fixup MAC address for xilinx_lltemac:0
> Regis tering device xilinx_lltemac:0
> NET: Registered protocol family 2
> IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
> TCP established hash table entries: 1024 (order: 1, 8192 bytes)
> TCP bind hash table entries: 1024 (order: 0, 4096 bytes)
> TCP: Hash tables configured (established 1024 bind 1024)
> TCP reno registered
> sysctl table check failed: /kernel/l2cr .1.31 Missing strategy
> Call Trace:
> [c1c0fe50] [c0008b70] show_stack+0x40/0x194 (unreliable)
> [c1c0fe90] [c003aed4] set_fail+0x68/0x80
> [c1c0feb0] [c003b4ec] sysctl_check_table+0x600/0x77c
> [c1c0fef0] [c003b4d4] sysctl_check_table+0x5e8/0x77c
> [c1c0ff30] [c002605c] register_sysctl_table+0x64/0xb4
> [c1c0ff50] [c034579c] register_ppc_htab_sysctl+0x18/0x2c
> [c1c0ff60] [c034482c] kernel_init+0x94/0x2bc
> [c1c0fff0] [c0004d58] kernel_thread+0x44/0x60
> Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
> fuse init (API version 7.9)
> io scheduler noop registered
> io scheduler anticipatory registered
> io scheduler deadline registered
> io scheduler cfq registered (default)
> uartlite.0: ttyUL0 at MM IO 0x84000003 (irq = 3) is a uartlite
> console [ttyUL0] enabled
> loop: module loaded
> nbd: registered device at major 43
> xilinx_lltemac xilinx_lltemac.0: MAC address is now 0: a:35: 1: 2: 3
> xilinx_lltemac xilinx_lltemac.0: XLlTemac: using DMA mode.
> XLlTemac: Dma base address: phy: 0x84600100, virt: 0xc3008100
> XLlTemac: buffer descriptor size: 32768 (0x8000)
> XLlTemac: Allocating DMA descriptors with kmalloc<6>XLlTemac:
> (buffer_descriptor_init) phy: 0x1d18000, virt: 0xc1d18000, size: 0x8000
> XTemac: PHY detected at address 7.
> xilinx_lltemac xilinx_lltemac.0: eth0: Xilinx TEMAC at 0x81C00000 mapped
> to 0xC3004000, irq=2
> console [netcon0] enabled
> Linux version 2.6.24-rc8-xlnx-g1db182b8-dirty (mingliu@cca01) (gcc version
> 3.4.1) #7 Tue Apr 1 14:55:25 CEST 2008
>
> Xilinx Generic PowerPC board support package (Xilinx ML405)
> (Virtex-4 FX)
>
> Zone PFN ranges:
> DMA 0 -> 8192
> Normal 8192 -> 8192
> HighMem 8192 -> 8192
> Movable zone start PFN for each node
> early_node_map[1] active PFN range
> s
> 0: 0 -> 8192
> Built 1 zonelists in Zone order, mobility grouping on. Total pages: 8128
> Kernel command line: root=/dev/nfs
> ip=192.168.0.4:192.168.0.3:192.168.0.3:255.255.255.0 rw
> nfsroot=192.168.0.3:/home/mingliu/ml403_rootfs console=ttyUL0,38400
> mem=32M
> Xilinx INTC #0 at 0x81800000 mapped to 0xFDFFF000
> PID hash table entries: 128 (order: 7, 512 bytes)
> Console: colour dummy device 80x25
> Dentry cache hash table entries: 4096 (order: 2, 16384 bytes)
> Inode-cache hash table entries: 2048 (order: 1, 8192 bytes)
> Memory: 28884k available (2552k kernel code, 944k data, 84k init, 0k highmem)
> SLUB: Genslabs=11, HWalign=32, Order=0-1, MinObjects=4, CPUs=1, Nodes=1
> Mount-cache hash table entries: 512
> n
> et_namespace: 64 bytes
> NET: Registered protocol family 16
> Registering device uartlite:0
> Fixup MAC address for xilinx_lltemac:0
> Registering device xilinx_lltemac:0
> NET: Registered protocol family 2
> IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
> TCP established hash table entries: 1024 (order: 1, 8192 bytes)
> TCP bind hash table entries: 1024
> (order: 0, 4096 bytes)
> TCP: Hash tables configured (established 1024 bind 1024)
> TCP reno registered
> sysctl table check failed: /kernel/l2cr .1.31 Missing strategy
> Call Trace:
> [c1c0fe50] [c0008b70] show_stack+0x40/0x194 (unreliable)
> [c1c0fe90] [c003aed4] set_fail+0x68/0x80
> [c1c0feb0] [c003b4ec] sysctl_check_table+0x600/0x77c
> [c1c0fef0] [c003b4d4] sysctl_c
> heck_table+0x5e8/0x77c
> [c1c0ff30] [c002605c] register_sysctl_table+0x64/0xb4
> [c1c0ff50] [c034579c] register_ppc_htab_sysctl+0x18/0x2c
> [c1c0ff60] [c034482c] kernel_init+0x94/0x2bc
> [c1c0fff0] [c0004d58] kernel_thread+0x44/0x60
> Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
> fuse init (API version 7.9)
> io scheduler noop registered<
> /SPAN>
> io scheduler anticipatory registered
> io scheduler deadline registered
> io scheduler cfq registered (default)
> uartlite.0: ttyUL0 at MMIO 0x84000003 (irq = 3) is a uartlite
> console [ttyUL0] enabled
> loop: module loaded
> nbd: registered device at major 43
> xilinx_lltemac xilinx_lltemac.0: MAC address is now 0: a:35: 1: 2: 3
> xilinx_lltemac xilinx_lltemac.0: XLlTemac: using DMA mode.
> XLlTemac: Dma base address: phy: 0x84600100, virt: 0xc3008100
> XLlTemac: buffer descriptor size: 32768 (0x8000)
> XLlTemac: Allocating DMA descriptors with kmalloc<6>XLlTemac:
> (buffer_descriptor_init) phy: 0x1d18000, virt: 0xc1d18000, size: 0x8000
> XTemac: PHY detected at address 7.
> xilinx_lltemac xilinx_lltemac.0: eth0: Xilinx TEMAC at 0x81C00000 mapped
> <
> SPAN style="FONT-SIZE: 12pt">to 0xC3004000, irq=2
> console [netcon0] enabled
> netconsole: network logging started
> Generic platform RAM MTD, (c) 2004 Simtec Electronics
> mice: PS/2 mouse device common for all mice
> TCP cubic registered
> NET: Registered protocol family 1
> NET: Registered protocol family 17
> RPC: Registered udp transport module.
> RPC: Registered tcp transport module.
> eth0: XLlTemac: Options: 0x3fa
> eth0: XLlTemac: allocating interrupt 0 for dma mode tx.
> eth0: XLlTemac: allocating interrupt 1 for dma mode rx.
> eth0: XLlTemac: speed set to 1000Mb/s
> eth0: XLlTemac: Send Threshold = 24, Receive Threshold = 4
> eth0: XLlTemac: Send Wait bound = 254, Receive Wait bound = 254
> IP-Config: Complete:
>
> device=eth0, addr=192.168.0.4, mask=255.255.255.0, gw=192.168.0.3,
> host=192.168.0.4, domain=, nis-domain=(none),
> bootserver=192.168.0.3, rootserver=192.168.0.3, rootpath=
> Looking up port of RPC 100003/2 on 192.168.0.3
> rpcbind: server 192.168.0.3 not responding, timed out
> Root-NFS: Unable to get nfsd port number from server, using default
> Looking up port of RPC 10000
> 5/1 on 192.168.0.3
> rpcbind: server 192.168.0.3 not responding, timed out
> Root-NFS: Unable to get mountd port number from server, using default
> mount: server 192.168.0.3 not responding, timed out
> Root-NFS: Server returned error -5 while mounting /home/mingliu/ml403_rootfs
> VFS: Unable to mount root fs via NFS, trying floppy.
> VFS: Cannot open root device "nfs" or unknown-block(2,0)
> Please append a correct "root=" boot option; here are
> the available
> partitions:
> Kernel panic - not syncing: VFS: Unable to mount root fs on
> unknown-block(2,0)
> Rebooting in 180 seconds..
>
>
> BR
> Ming
>
>
>
>
> ______________________________________________________________
> Windows Live Writer，支持离线撰写博客内容，随时随地想写就写。
> 立即使用！
>
>
>
>
> ______________________________________________________________________
> 使用新一代 Windows Live Messenger 轻松交流和共享！ 立即体验！
> _______________________________________________
> Linuxppc-embedded mailing list
> Linuxppc-embedded@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-embedded
^ permalink raw reply [flat|nested] 10+ messages in thread
* RE: xilinx Ml405 NFS mount problem
2008-04-01 16:50 ` Robert Woodworth
@ 2008-04-01 16:53 ` John Linn
2008-04-01 23:43 ` Robert Woodworth
2008-04-01 18:36 ` MingLiu
2008-04-01 20:42 ` MingLiu
2 siblings, 1 reply; 10+ messages in thread
From: John Linn @ 2008-04-01 16:53 UTC (permalink / raw)
To: Robert Woodworth, MingLiu; +Cc: linuxppc-embedded
Now that you say that, I have been running TCP with my NFS mount as I'm =
mounting across a corporate network.
I am also using the latest LL TEMAC with EDK 10.1.
Thanks,
John
-----Original Message-----
From: Robert Woodworth [mailto:rwoodworth@securics.com]=20
Sent: Tuesday, April 01, 2008 10:50 AM
To: MingLiu
Cc: John Linn; linuxppc-embedded@ozlabs.org
Subject: RE: xilinx Ml405 NFS mount problem
I think you may be suffering from the latest LL_TEMAC packet loss
problem. (NFS/UDP really does not like packet loss)
Let me guess. =20
You are using a base system from "Base System Builder Wizard"?
EDK 9.2i. Default syntheses/P&R options.
I have seen a massive packet loss problems on my ML403 and two other
boards I have with an FX60.
This is probably a hardware problem.
Xilinx has acknowledged an LL_TEMAC problem to me but has not provided a
fix. I have heard that things are better with EDK/ISE-10.1 but I have
not tested it.
The vendor of one of my boards (Pico) has fixed the problem on the FX60
by highly constraining the timing of the LL_TEMAC in map/PR. On my
ML403 I used similar constraints and it fixed the problem, but only if
the device is plugged into a GigE switch. The problem is still there
with the same .bit file on a 100-T switch.=20
Are you on a GigE switch?
Rob.
On Tue, 2008-04-01 at 16:15 +0000, MingLiu wrote:
> Dear John,
> =20
> Thank you for your replying.=20
>=20
> >It=A1=AFs not obvious to me what the problem is as I don=A1=AFt see =
any driver
> failures. Have you >tried using a ramdisk and then seeing if the
> network is working before using NFS root? =20
> =20
> Not yet. I will try it soon. However from the information on the
> LL_TEMAC, it seems everything is fine and it should work.=20
> =20
>=20
>=20
> >And I=A1=AFm assuming you have used the NFS root before so you know =
that
> it=A1=AFs good for sure.
>=20
> =20
>=20
> >I test on the ML405 with NFS root and haven=A1=AFt seen this problem, =
but
> my setup is a little different. I use DHCP rather than >a static IP,
> but other than that it=A1=AFs similar.
>=20
> =20
>=20
> Yes. I used NFS before. I can make sure my NFS server works well. Also
> in principle, static IP should get a same result as DHCP, I think.=20
>=20
> =20
>=20
> >How long has it been since you pulled from the Xilinx Git tree?
>=20
> =20
>=20
> I just pulled the Xilinx tree quite recently. I am using a latest
> kernel.
>=20
> =20
>=20
> BR=20
>=20
> Ming
>=20
> =20
>=20
> =20
> =20
> And I=A1=AFm assuming you have used the NFS root before so you =
know
> that it=A1=AFs good for sure.
> =20
> =20
> =20
> I test on the ML405 with NFS root and haven=A1=AFt seen this
> problem, but my setup is a little different. I use DHCP
> rather than a static IP, but other than that it=A1=AFs =
similar.
> =20
> =20
> =20
> I=A1=AFm assuming that you accidentally got 2 different =
powerup
> outputs in the message below as the 1st stops and a 2nd starts
> in the middle.
> =20
> =20
> =20
> How long has it been since you pulled from the Xilinx Git
> tree?
> =20
> =20
> =20
> Thanks,
> =20
> John
> =20
> =20
> =20
> =20
> ______________________________________________________________
> From: linuxppc-embedded-bounces
> +john.linn=3Dxilinx.com@ozlabs.org
> [mailto:linuxppc-embedded-bounces
> +john.linn=3Dxilinx.com@ozlabs.org] On Behalf Of MingLiu
> Sent: Tuesday, April 01, 2008 8:12 AM
> To: linuxppc-embedded@ozlabs.org
> Subject: xilinx Ml405 NFS mount problem
> =20
> =20
> =20
> =20
> Dear friends,
> =20
> I am bringing up my kernel from Xilinx git tree. Unfortunately =
I met some
> problem when mounting the root file system. Here is the =
information
> listed. I will appreciate a lot if someone can help me out of =
the trouble.=20
> Thanks a lot!
> =20
> =20
> loaded at: 00400000 0059F19C
> board data at: 0059D120 0059D19C
> relocated to: 004050C8 00405144
> zimage at: 00405F3F 0059C025
> avail ram: 005A0000 08000000
> =20
> Linux/PPC load: root=3D/dev/nfs
> ip=3D192.168.0.4:192.168.0.3:192.168.0.3:255.255.255.0 rw
> nfsroot=3D192.168.0.3:/home/mingliu/ml403_rootfs =
console=3DttyUL0,38400
> mem=3D32M
> Uncompressing Linux...done.
> Now booting the kernel
> Linux version 2.6.24-rc8-xlnx-g1db182b8-dirty (mingliu@cca01) =
(gcc version
> 3.4.1) #7 Tue Apr 1 14:55:25 CEST 2008
> Xilinx Generic PowerPC board support package (Xilinx ML405) =
(Virtex-4 FX)
> Zone PFN ranges:
> DMA 0 -> 8192
> =20
> Normal 8192 -> 8192
> =20
> HighMem 8192 -> 8192
> Movable zone start PFN for each node
> early_node_map[1] active PFN ranges
> 0: 0 -> 8192
> Built 1 zonelists in Zone order, mobility grouping on. Total =
pages: 8128
> Kernel command line: root=3D/de v/nfs
> ip=3D192.168.0.4:192.168.0.3:192.168.0.3:255.255.255.0 rw
> nfsroot=3D192.168.0.3:/home/mingliu/ml403_rootfs =
console=3DttyUL0,38400
> mem=3D32M
> Xilinx INTC #0 at 0x81800000 mapped to 0xFDFFF000
> PID hash table entries: 128 (order: 7, 512 bytes)
> Console: colour dummy device 80x25
> Dentry cache hash table entries: 4096 (order: 2, 16384 bytes)
> Inode-cache hash table entries: 2048 (order: 1, 8192 bytes)
> Memory: 28884k available (2552k kernel code, 944k data, 84k =
init, 0k highmem)
> SLUB: Genslabs=3D11, HWalign=3D32, Order=3D0-1, =
MinObjects=3D4, CPUs=3D1, Nodes=3D1
> Mount-cache hash table entries: 512
> net_namespace: 64 bytes
> NET: Registered protocol family 16
> Registering device uartlite:0
> Fixup MAC address for xilinx_lltemac:0
> Regis tering device xilinx_lltemac:0
> NET: Registered protocol family 2
> IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
> TCP established hash table entries: 1024 (order: 1, 8192 =
bytes)
> TCP bind hash table entries: 1024 (order: 0, 4096 bytes)
> TCP: Hash tables configured (established 1024 bind 1024)
> TCP reno registered
> sysctl table check failed: /kernel/l2cr .1.31 Missing strategy
> Call Trace:
> [c1c0fe50] [c0008b70] show_stack+0x40/0x194 (unreliable)
> [c1c0fe90] [c003aed4] set_fail+0x68/0x80
> [c1c0feb0] [c003b4ec] sysctl_check_table+0x600/0x77c
> [c1c0fef0] [c003b4d4] sysctl_check_table+0x5e8/0x77c
> [c1c0ff30] [c002605c] register_sysctl_table+0x64/0xb4
> [c1c0ff50] [c034579c] register_ppc_htab_sysctl+0x18/0x2c
> [c1c0ff60] [c034482c] kernel_init+0x94/0x2bc
> [c1c0fff0] [c0004d58] kernel_thread+0x44/0x60
> Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
> fuse init (API version 7.9)
> io scheduler noop registered
> io scheduler anticipatory registered
> io scheduler deadline registered
> io scheduler cfq registered (default)
> uartlite.0: ttyUL0 at MM IO 0x84000003 (irq =3D 3) is a =
uartlite
> console [ttyUL0] enabled
> loop: module loaded
> nbd: registered device at major 43
> xilinx_lltemac xilinx_lltemac.0: MAC address is now 0: a:35: =
1: 2: 3
> xilinx_lltemac xilinx_lltemac.0: XLlTemac: using DMA mode.
> XLlTemac: Dma base address: phy: 0x84600100, virt: 0xc3008100
> XLlTemac: buffer descriptor size: 32768 (0x8000)
> XLlTemac: Allocating DMA descriptors with kmalloc<6>XLlTemac:
> (buffer_descriptor_init) phy: 0x1d18000, virt: 0xc1d18000, =
size: 0x8000
> XTemac: PHY detected at address 7.
> xilinx_lltemac xilinx_lltemac.0: eth0: Xilinx TEMAC at =
0x81C00000 mapped
> to 0xC3004000, irq=3D2
> console [netcon0] enabled
> Linux version 2.6.24-rc8-xlnx-g1db182b8-dirty (mingliu@cca01) =
(gcc version
> 3.4.1) #7 Tue Apr 1 14:55:25 CEST 2008
> =20
> Xilinx Generic PowerPC board support package (Xilinx ML405)
> (Virtex-4 FX)
> =20
> Zone PFN ranges:
> DMA 0 -> 8192
> Normal 8192 -> 8192
> HighMem 8192 -> 8192
> Movable zone start PFN for each node
> early_node_map[1] active PFN range
> s
> 0: 0 -> 8192
> Built 1 zonelists in Zone order, mobility grouping on. Total =
pages: 8128
> Kernel command line: root=3D/dev/nfs
> ip=3D192.168.0.4:192.168.0.3:192.168.0.3:255.255.255.0 rw
> nfsroot=3D192.168.0.3:/home/mingliu/ml403_rootfs =
console=3DttyUL0,38400
> mem=3D32M
> Xilinx INTC #0 at 0x81800000 mapped to 0xFDFFF000
> PID hash table entries: 128 (order: 7, 512 bytes)
> Console: colour dummy device 80x25
> Dentry cache hash table entries: 4096 (order: 2, 16384 bytes)
> Inode-cache hash table entries: 2048 (order: 1, 8192 bytes)
> Memory: 28884k available (2552k kernel code, 944k data, 84k =
init, 0k highmem)
> SLUB: Genslabs=3D11, HWalign=3D32, Order=3D0-1, =
MinObjects=3D4, CPUs=3D1, Nodes=3D1
> Mount-cache hash table entries: 512
> n
> et_namespace: 64 bytes
> NET: Registered protocol family 16
> Registering device uartlite:0
> Fixup MAC address for xilinx_lltemac:0
> Registering device xilinx_lltemac:0
> NET: Registered protocol family 2
> IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
> TCP established hash table entries: 1024 (order: 1, 8192 =
bytes)
> TCP bind hash table entries: 1024
> (order: 0, 4096 bytes)
> TCP: Hash tables configured (established 1024 bind 1024)
> TCP reno registered
> sysctl table check failed: /kernel/l2cr .1.31 Missing strategy
> Call Trace:
> [c1c0fe50] [c0008b70] show_stack+0x40/0x194 (unreliable)
> [c1c0fe90] [c003aed4] set_fail+0x68/0x80
> [c1c0feb0] [c003b4ec] sysctl_check_table+0x600/0x77c
> [c1c0fef0] [c003b4d4] sysctl_c
> heck_table+0x5e8/0x77c
> [c1c0ff30] [c002605c] register_sysctl_table+0x64/0xb4
> [c1c0ff50] [c034579c] register_ppc_htab_sysctl+0x18/0x2c
> [c1c0ff60] [c034482c] kernel_init+0x94/0x2bc
> [c1c0fff0] [c0004d58] kernel_thread+0x44/0x60
> Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
> fuse init (API version 7.9)
> io scheduler noop registered<
> /SPAN>
> io scheduler anticipatory registered
> io scheduler deadline registered
> io scheduler cfq registered (default)
> uartlite.0: ttyUL0 at MMIO 0x84000003 (irq =3D 3) is a =
uartlite
> console [ttyUL0] enabled
> loop: module loaded
> nbd: registered device at major 43
> xilinx_lltemac xilinx_lltemac.0: MAC address is now 0: a:35: =
1: 2: 3
> xilinx_lltemac xilinx_lltemac.0: XLlTemac: using DMA mode.
> XLlTemac: Dma base address: phy: 0x84600100, virt: 0xc3008100
> XLlTemac: buffer descriptor size: 32768 (0x8000)
> XLlTemac: Allocating DMA descriptors with kmalloc<6>XLlTemac:
> (buffer_descriptor_init) phy: 0x1d18000, virt: 0xc1d18000, =
size: 0x8000
> XTemac: PHY detected at address 7.
> xilinx_lltemac xilinx_lltemac.0: eth0: Xilinx TEMAC at =
0x81C00000 mapped
> <
> SPAN style=3D"FONT-SIZE: 12pt">to 0xC3004000, irq=3D2
> console [netcon0] enabled
> netconsole: network logging started
> Generic platform RAM MTD, (c) 2004 Simtec Electronics
> mice: PS/2 mouse device common for all mice
> TCP cubic registered
> NET: Registered protocol family 1
> NET: Registered protocol family 17
> RPC: Registered udp transport module.
> RPC: Registered tcp transport module.
> eth0: XLlTemac: Options: 0x3fa
> eth0: XLlTemac: allocating interrupt 0 for dma mode tx.
> eth0: XLlTemac: allocating interrupt 1 for dma mode rx.
> eth0: XLlTemac: speed set to 1000Mb/s
> eth0: XLlTemac: Send Threshold =3D 24, Receive Threshold =3D 4
> eth0: XLlTemac: Send Wait bound =3D 254, Receive Wait bound =
=3D 254
> IP-Config: Complete:
> =20
> device=3Deth0, addr=3D192.168.0.4, mask=3D255.255.255.0, =
gw=3D192.168.0.3,
> host=3D192.168.0.4, domain=3D, nis-domain=3D(none),
> bootserver=3D192.168.0.3, rootserver=3D192.168.0.3, =
rootpath=3D
> Looking up port of RPC 100003/2 on 192.168.0.3
> rpcbind: server 192.168.0.3 not responding, timed out
> Root-NFS: Unable to get nfsd port number from server, using =
default
> Looking up port of RPC 10000
> 5/1 on 192.168.0.3
> rpcbind: server 192.168.0.3 not responding, timed out
> Root-NFS: Unable to get mountd port number from server, using =
default
> mount: server 192.168.0.3 not responding, timed out
> Root-NFS: Server returned error -5 while mounting =
/home/mingliu/ml403_rootfs
> VFS: Unable to mount root fs via NFS, trying floppy.
> VFS: Cannot open root device "nfs" or unknown-block(2,0)
> Please append a correct "root=3D" boot option; here are=20
> the available
> partitions:
> Kernel panic - not syncing: VFS: Unable to mount root fs on
> unknown-block(2,0)
> Rebooting in 180 seconds..
> =20
> =20
> BR
> Ming
> =20
> =20
> =20
> =20
> ______________________________________________________________
> Windows Live =
Writer=A3=AC=D6=A7=B3=D6=C0=EB=CF=DF=D7=AB=D0=B4=B2=A9=BF=CD=C4=DA=C8=DD=A3=
=AC=CB=E6=CA=B1=CB=E6=B5=D8=CF=EB=D0=B4=BE=CD=D0=B4=A1=A3
> =C1=A2=BC=B4=CA=B9=D3=C3=A3=A1
> =20
> =20
>=20
>=20
> ______________________________________________________________________
> =CA=B9=D3=C3=D0=C2=D2=BB=B4=FA Windows Live Messenger =
=C7=E1=CB=C9=BD=BB=C1=F7=BA=CD=B9=B2=CF=ED=A3=A1 =
=C1=A2=BC=B4=CC=E5=D1=E9=A3=A1=20
> _______________________________________________
> Linuxppc-embedded mailing list
> Linuxppc-embedded@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-embedded
^ permalink raw reply [flat|nested] 10+ messages in thread
* RE: xilinx Ml405 NFS mount problem
2008-04-01 16:50 ` Robert Woodworth
2008-04-01 16:53 ` John Linn
@ 2008-04-01 18:36 ` MingLiu
2008-04-01 20:42 ` MingLiu
2 siblings, 0 replies; 10+ messages in thread
From: MingLiu @ 2008-04-01 18:36 UTC (permalink / raw)
To: Robert Woodworth; +Cc: John Linn, linuxppc-embedded
[-- Attachment #1: Type: text/plain, Size: 2333 bytes --]
Dear Robert> Let me guess. > You are using a base system from "Base System Builder Wizard"?> EDK 9.2i. Default syntheses/P&R options.
I am using EDK 10.1 evaluation version (60 days) from Xilinx. I don't have experience on EDK 9.2 and previously I was working on EDK 8.2.
> I have seen a massive packet loss problems on my ML403 and two other> boards I have with an FX60.> > This is probably a hardware problem.> Xilinx has acknowledged an LL_TEMAC problem to me but has not provided a> fix. I have heard that things are better with EDK/ISE-10.1 but I have> not tested it.
I got the following message from my NFS server PC:
Apr 1 15:08:34 linux kernel: UDP: bad checksum. From 192.168.0.4:839 to
192.168.0.3:627 ulen 48
Apr 1 15:08:40 linux kernel: UDP: bad checksum. From 192.168.0.4:839 to
192.168.0.3:627 ulen 48
Apr 1 15:08:49 linux kernel: UDP: bad checksum. From 192.168.0.4:839 to
192.168.0.3:627 ulen 48
Apr 1 15:13:23 linux kernel: nfsd: last server has exited
Apr 1 15:13:23 linux kernel: nfsd: unexporting all filesystems
Apr 1 15:13:23 linux rpc.mountd: Caught signal 15, un-registering and
exiting.
Apr 1 15:13:24 linux kernel: NFSD: Using /var/lib/nfs/v4recovery as the
NFSv4 state recovery directory
Apr 1 15:13:24 linux kernel: NFSD: recovery directory
/var/lib/nfs/v4recovery doesn't exist
Apr 1 15:13:24 linux kernel: NFSD: starting 90-second grace period
Apr 1 16:02:57 linux syslog-ng[3700]: STATS: dropped 0
Apr 1 17:02:57 linux syslog-ng[3700]: STATS: dropped 0
Apr 1 18:02:58 linux syslog-ng[3700]: STATS: dropped 0
I shows "UDP bad checksum" from my board to the PC. I don't know if it has something to do with the package loss problem.
> The vendor of one of my boards (Pico) has fixed the problem on the FX60> by highly constraining the timing of the LL_TEMAC in map/PR. On my> ML403 I used similar constraints and it fixed the problem, but only if> the device is plugged into a GigE switch. The problem is still there> with the same .bit file on a 100-T switch.
I connect the board with the PC point-to-point with gigabit ethernet. It should be even better than a Gigabit switch, right?
BR
Ming
_________________________________________________________________
Windows Live Photo gallery 数码相机的超级伴侣，轻松管理和编辑照片，还能制作全景美图！
http://get.live.cn/product/photo.html
[-- Attachment #2: Type: text/html, Size: 2638 bytes --]
^ permalink raw reply [flat|nested] 10+ messages in thread
* RE: xilinx Ml405 NFS mount problem
2008-04-01 16:50 ` Robert Woodworth
2008-04-01 16:53 ` John Linn
2008-04-01 18:36 ` MingLiu
@ 2008-04-01 20:42 ` MingLiu
2 siblings, 0 replies; 10+ messages in thread
From: MingLiu @ 2008-04-01 20:42 UTC (permalink / raw)
To: Robert Woodworth; +Cc: John Linn, linuxppc-embedded
[-- Attachment #1: Type: text/plain, Size: 13008 bytes --]
Dear Robert and all friends,
A little more progress on my problem. I just found that if I disable the hardware check-sum offloading options, the root file system could be mounted then. In combination with the previous information of "UDP bad checksum" I mentioned, it seems that you are absolutely right! The problem is on the hardware checksum logic!
For this problem, maybe it will be better if xilinx could solve it. I am not pretty sure if we can rely on a stricter timing constraint. After all, we are not the original designer of the LL_TEMAC control logic.
Any other idea or suggestion? Thanks in advance.
BR
Ming
> Subject: RE: xilinx Ml405 NFS mount problem> From: rwoodworth@securics.com> To: eemingliu@hotmail.com> CC: john.linn@xilinx.com; linuxppc-embedded@ozlabs.org> Date: Tue, 1 Apr 2008 10:50:18 -0600> > I think you may be suffering from the latest LL_TEMAC packet loss> problem. (NFS/UDP really does not like packet loss)> > > Let me guess. > You are using a base system from "Base System Builder Wizard"?> EDK 9.2i. Default syntheses/P&R options.> > I have seen a massive packet loss problems on my ML403 and two other> boards I have with an FX60.> > This is probably a hardware problem.> Xilinx has acknowledged an LL_TEMAC problem to me but has not provided a> fix. I have heard that things are better with EDK/ISE-10.1 but I have> not tested it.> > > The vendor of one of my boards (Pico) has fixed the problem on the FX60> by highly constraining the timing of the LL_TEMAC in map/PR. On my> ML403 I used similar constraints and it fixed the problem, but only if> the device is plugged into a GigE switch. The problem is still there> with the same .bit file on a 100-T switch. > > > Are you on a GigE switch?> > > > Rob.> > > > > > > On Tue, 2008-04-01 at 16:15 +0000, MingLiu wrote:> > Dear John,> > > > Thank you for your replying. > > > > >It’s not obvious to me what the problem is as I don’t see any driver> > failures. Have you >tried using a ramdisk and then seeing if the> > network is working before using NFS root? > > > > Not yet. I will try it soon. However from the information on the> > LL_TEMAC, it seems everything is fine and it should work. > > > > > > > > >And I’m assuming you have used the NFS root before so you know that> > it’s good for sure.> > > > > > > > >I test on the ML405 with NFS root and haven’t seen this problem, but> > my setup is a little different. I use DHCP rather than >a static IP,> > but other than that it’s similar.> > > > > > > > Yes. I used NFS before. I can make sure my NFS server works well. Also> > in principle, static IP should get a same result as DHCP, I think. > > > > > > > > >How long has it been since you pulled from the Xilinx Git tree?> > > > > > > > I just pulled the Xilinx tree quite recently. I am using a latest> > kernel.> > > > > > > > BR > > > > Ming> > > > > > > > > > > > And I’m assuming you have used the NFS root before so you know> > that it’s good for sure.> > > > > > > > I test on the ML405 with NFS root and haven’t seen this> > problem, but my setup is a little different. I use DHCP> > rather than a static IP, but other than that it’s similar.> > > > > > > > I’m assuming that you accidentally got 2 different powerup> > outputs in the message below as the 1st stops and a 2nd starts> > in the middle.> > > > > > > > How long has it been since you pulled from the Xilinx Git> > tree?> > > > > > > > Thanks,> > > > John> > > > > > > > > > ______________________________________________________________> > From: linuxppc-embedded-bounces> > +john.linn=xilinx.com@ozlabs.org> > [mailto:linuxppc-embedded-bounces> > +john.linn=xilinx.com@ozlabs.org] On Behalf Of MingLiu> > Sent: Tuesday, April 01, 2008 8:12 AM> > To: linuxppc-embedded@ozlabs.org> > Subject: xilinx Ml405 NFS mount problem> > > > > > > > > > Dear friends,> > > > I am bringing up my kernel from Xilinx git tree. Unfortunately I met some> > problem when mounting the root file system. Here is the information> > listed. I will appreciate a lot if someone can help me out of the trouble. > > Thanks a lot!> > > > > > loaded at: 00400000 0059F19C> > board data at: 0059D120 0059D19C> > relocated to: 004050C8 00405144> > zimage at: 00405F3F 0059C025> > avail ram: 005A0000 08000000> > > > Linux/PPC load: root=/dev/nfs> > ip=192.168.0.4:192.168.0.3:192.168.0.3:255.255.255.0 rw> > nfsroot=192.168.0.3:/home/mingliu/ml403_rootfs console=ttyUL0,38400> > mem=32M> > Uncompressing Linux...done.> > Now booting the kernel> > Linux version 2.6.24-rc8-xlnx-g1db182b8-dirty (mingliu@cca01) (gcc version> > 3.4.1) #7 Tue Apr 1 14:55:25 CEST 2008> > Xilinx Generic PowerPC board support package (Xilinx ML405) (Virtex-4 FX)> > Zone PFN ranges:> > DMA 0 -> 8192> > > > Normal 8192 -> 8192> > > > HighMem 8192 -> 8192> > Movable zone start PFN for each node> > early_node_map[1] active PFN ranges> > 0: 0 -> 8192> > Built 1 zonelists in Zone order, mobility grouping on. Total pages: 8128> > Kernel command line: root=/de v/nfs> > ip=192.168.0.4:192.168.0.3:192.168.0.3:255.255.255.0 rw> > nfsroot=192.168.0.3:/home/mingliu/ml403_rootfs console=ttyUL0,38400> > mem=32M> > Xilinx INTC #0 at 0x81800000 mapped to 0xFDFFF000> > PID hash table entries: 128 (order: 7, 512 bytes)> > Console: colour dummy device 80x25> > Dentry cache hash table entries: 4096 (order: 2, 16384 bytes)> > Inode-cache hash table entries: 2048 (order: 1, 8192 bytes)> > Memory: 28884k available (2552k kernel code, 944k data, 84k init, 0k highmem)> > SLUB: Genslabs=11, HWalign=32, Order=0-1, MinObjects=4, CPUs=1, Nodes=1> > Mount-cache hash table entries: 512> > net_namespace: 64 bytes> > NET: Registered protocol family 16> > Registering device uartlite:0> > Fixup MAC address for xilinx_lltemac:0> > Regis tering device xilinx_lltemac:0> > NET: Registered protocol family 2> > IP route cache hash table entries: 1024 (order: 0, 4096 bytes)> > TCP established hash table entries: 1024 (order: 1, 8192 bytes)> > TCP bind hash table entries: 1024 (order: 0, 4096 bytes)> > TCP: Hash tables configured (established 1024 bind 1024)> > TCP reno registered> > sysctl table check failed: /kernel/l2cr .1.31 Missing strategy> > Call Trace:> > [c1c0fe50] [c0008b70] show_stack+0x40/0x194 (unreliable)> > [c1c0fe90] [c003aed4] set_fail+0x68/0x80> > [c1c0feb0] [c003b4ec] sysctl_check_table+0x600/0x77c> > [c1c0fef0] [c003b4d4] sysctl_check_table+0x5e8/0x77c> > [c1c0ff30] [c002605c] register_sysctl_table+0x64/0xb4> > [c1c0ff50] [c034579c] register_ppc_htab_sysctl+0x18/0x2c> > [c1c0ff60] [c034482c] kernel_init+0x94/0x2bc> > [c1c0fff0] [c0004d58] kernel_thread+0x44/0x60> > Installing knfsd (copyright (C) 1996 okir@monad.swb.de).> > fuse init (API version 7.9)> > io scheduler noop registered> > io scheduler anticipatory registered> > io scheduler deadline registered> > io scheduler cfq registered (default)> > uartlite.0: ttyUL0 at MM IO 0x84000003 (irq = 3) is a uartlite> > console [ttyUL0] enabled> > loop: module loaded> > nbd: registered device at major 43> > xilinx_lltemac xilinx_lltemac.0: MAC address is now 0: a:35: 1: 2: 3> > xilinx_lltemac xilinx_lltemac.0: XLlTemac: using DMA mode.> > XLlTemac: Dma base address: phy: 0x84600100, virt: 0xc3008100> > XLlTemac: buffer descriptor size: 32768 (0x8000)> > XLlTemac: Allocating DMA descriptors with kmalloc<6>XLlTemac:> > (buffer_descriptor_init) phy: 0x1d18000, virt: 0xc1d18000, size: 0x8000> > XTemac: PHY detected at address 7.> > xilinx_lltemac xilinx_lltemac.0: eth0: Xilinx TEMAC at 0x81C00000 mapped> > to 0xC3004000, irq=2> > console [netcon0] enabled> > Linux version 2.6.24-rc8-xlnx-g1db182b8-dirty (mingliu@cca01) (gcc version> > 3.4.1) #7 Tue Apr 1 14:55:25 CEST 2008> > > > Xilinx Generic PowerPC board support package (Xilinx ML405)> > (Virtex-4 FX)> > > > Zone PFN ranges:> > DMA 0 -> 8192> > Normal 8192 -> 8192> > HighMem 8192 -> 8192> > Movable zone start PFN for each node> > early_node_map[1] active PFN range> > s> > 0: 0 -> 8192> > Built 1 zonelists in Zone order, mobility grouping on. Total pages: 8128> > Kernel command line: root=/dev/nfs> > ip=192.168.0.4:192.168.0.3:192.168.0.3:255.255.255.0 rw> > nfsroot=192.168.0.3:/home/mingliu/ml403_rootfs console=ttyUL0,38400> > mem=32M> > Xilinx INTC #0 at 0x81800000 mapped to 0xFDFFF000> > PID hash table entries: 128 (order: 7, 512 bytes)> > Console: colour dummy device 80x25> > Dentry cache hash table entries: 4096 (order: 2, 16384 bytes)> > Inode-cache hash table entries: 2048 (order: 1, 8192 bytes)> > Memory: 28884k available (2552k kernel code, 944k data, 84k init, 0k highmem)> > SLUB: Genslabs=11, HWalign=32, Order=0-1, MinObjects=4, CPUs=1, Nodes=1> > Mount-cache hash table entries: 512> > n> > et_namespace: 64 bytes> > NET: Registered protocol family 16> > Registering device uartlite:0> > Fixup MAC address for xilinx_lltemac:0> > Registering device xilinx_lltemac:0> > NET: Registered protocol family 2> > IP route cache hash table entries: 1024 (order: 0, 4096 bytes)> > TCP established hash table entries: 1024 (order: 1, 8192 bytes)> > TCP bind hash table entries: 1024> > (order: 0, 4096 bytes)> > TCP: Hash tables configured (established 1024 bind 1024)> > TCP reno registered> > sysctl table check failed: /kernel/l2cr .1.31 Missing strategy> > Call Trace:> > [c1c0fe50] [c0008b70] show_stack+0x40/0x194 (unreliable)> > [c1c0fe90] [c003aed4] set_fail+0x68/0x80> > [c1c0feb0] [c003b4ec] sysctl_check_table+0x600/0x77c> > [c1c0fef0] [c003b4d4] sysctl_c> > heck_table+0x5e8/0x77c> > [c1c0ff30] [c002605c] register_sysctl_table+0x64/0xb4> > [c1c0ff50] [c034579c] register_ppc_htab_sysctl+0x18/0x2c> > [c1c0ff60] [c034482c] kernel_init+0x94/0x2bc> > [c1c0fff0] [c0004d58] kernel_thread+0x44/0x60> > Installing knfsd (copyright (C) 1996 okir@monad.swb.de).> > fuse init (API version 7.9)> > io scheduler noop registered<> > /SPAN>> > io scheduler anticipatory registered> > io scheduler deadline registered> > io scheduler cfq registered (default)> > uartlite.0: ttyUL0 at MMIO 0x84000003 (irq = 3) is a uartlite> > console [ttyUL0] enabled> > loop: module loaded> > nbd: registered device at major 43> > xilinx_lltemac xilinx_lltemac.0: MAC address is now 0: a:35: 1: 2: 3> > xilinx_lltemac xilinx_lltemac.0: XLlTemac: using DMA mode.> > XLlTemac: Dma base address: phy: 0x84600100, virt: 0xc3008100> > XLlTemac: buffer descriptor size: 32768 (0x8000)> > XLlTemac: Allocating DMA descriptors with kmalloc<6>XLlTemac:> > (buffer_descriptor_init) phy: 0x1d18000, virt: 0xc1d18000, size: 0x8000> > XTemac: PHY detected at address 7.> > xilinx_lltemac xilinx_lltemac.0: eth0: Xilinx TEMAC at 0x81C00000 mapped> > <> > SPAN style="FONT-SIZE: 12pt">to 0xC3004000, irq=2> > console [netcon0] enabled> > netconsole: network logging started> > Generic platform RAM MTD, (c) 2004 Simtec Electronics> > mice: PS/2 mouse device common for all mice> > TCP cubic registered> > NET: Registered protocol family 1> > NET: Registered protocol family 17> > RPC: Registered udp transport module.> > RPC: Registered tcp transport module.> > eth0: XLlTemac: Options: 0x3fa> > eth0: XLlTemac: allocating interrupt 0 for dma mode tx.> > eth0: XLlTemac: allocating interrupt 1 for dma mode rx.> > eth0: XLlTemac: speed set to 1000Mb/s> > eth0: XLlTemac: Send Threshold = 24, Receive Threshold = 4> > eth0: XLlTemac: Send Wait bound = 254, Receive Wait bound = 254> > IP-Config: Complete:> > > > device=eth0, addr=192.168.0.4, mask=255.255.255.0, gw=192.168.0.3,> > host=192.168.0.4, domain=, nis-domain=(none),> > bootserver=192.168.0.3, rootserver=192.168.0.3, rootpath=> > Looking up port of RPC 100003/2 on 192.168.0.3> > rpcbind: server 192.168.0.3 not responding, timed out> > Root-NFS: Unable to get nfsd port number from server, using default> > Looking up port of RPC 10000> > 5/1 on 192.168.0.3> > rpcbind: server 192.168.0.3 not responding, timed out> > Root-NFS: Unable to get mountd port number from server, using default> > mount: server 192.168.0.3 not responding, timed out> > Root-NFS: Server returned error -5 while mounting /home/mingliu/ml403_rootfs> > VFS: Unable to mount root fs via NFS, trying floppy.> > VFS: Cannot open root device "nfs" or unknown-block(2,0)> > Please append a correct "root=" boot option; here are > > the available> > partitions:> > Kernel panic - not syncing: VFS: Unable to mount root fs on> > unknown-block(2,0)> > Rebooting in 180 seconds..> > > > > > BR> > Ming> > > > > > > > > > ______________________________________________________________> > Windows Live Writer，支持离线撰写博客内容，随时随地想写就写。> > 立即使用！> > > > > > > > > > ______________________________________________________________________> > 使用新一代 Windows Live Messenger 轻松交流和共享！ 立即体验！ > > _______________________________________________> > Linuxppc-embedded mailing list> > Linuxppc-embedded@ozlabs.org> > https://ozlabs.org/mailman/listinfo/linuxppc-embedded>
_________________________________________________________________
MSN 中文网，最新时尚生活资讯，白领聚集门户。
http://cn.msn.com
[-- Attachment #2: Type: text/html, Size: 16652 bytes --]
^ permalink raw reply [flat|nested] 10+ messages in thread
* RE: xilinx Ml405 NFS mount problem
2008-04-01 16:53 ` John Linn
@ 2008-04-01 23:43 ` Robert Woodworth
2008-04-01 23:54 ` Rick Moleres
2008-04-01 23:55 ` John Linn
0 siblings, 2 replies; 10+ messages in thread
From: Robert Woodworth @ 2008-04-01 23:43 UTC (permalink / raw)
To: John Linn; +Cc: linuxppc-embedded
Can you test your packet loss with your setup??
GigE or 100T??
Do you have hardware checksum turned on in your bitfile?
I strongly believe that there is a timing problem in the MPMC3/LL_TEMAC.
I think the smaller FX12 does not suffer as much as the larger FX60. My
FX12 is fairly good, my FX60 is very bad. Guessing. The FX20 in the
ML405 is somewhere between.
When I make small changes to my bit file (I'm currently working on an
image processing HDL module) the quality of my LL_TEMAC changes
dramatically. If I take out one of my custom modules and re-synthesize
the LL_TEMAC packet loss goes way up. Add another module, re-synthesize
and packet loss is down.
I would *really* like a Xilinx EDK expert give me some advise on this
issue.
Rob.
On Tue, 2008-04-01 at 10:53 -0600, John Linn wrote:
> Now that you say that, I have been running TCP with my NFS mount as I'm mounting across a corporate network.
>
> I am also using the latest LL TEMAC with EDK 10.1.
>
> Thanks,
> John
>
> -----Original Message-----
> From: Robert Woodworth [mailto:rwoodworth@securics.com]
> Sent: Tuesday, April 01, 2008 10:50 AM
> To: MingLiu
> Cc: John Linn; linuxppc-embedded@ozlabs.org
> Subject: RE: xilinx Ml405 NFS mount problem
>
> I think you may be suffering from the latest LL_TEMAC packet loss
> problem. (NFS/UDP really does not like packet loss)
>
>
> Let me guess.
> You are using a base system from "Base System Builder Wizard"?
> EDK 9.2i. Default syntheses/P&R options.
>
> I have seen a massive packet loss problems on my ML403 and two other
> boards I have with an FX60.
>
> This is probably a hardware problem.
> Xilinx has acknowledged an LL_TEMAC problem to me but has not provided a
> fix. I have heard that things are better with EDK/ISE-10.1 but I have
> not tested it.
>
>
> The vendor of one of my boards (Pico) has fixed the problem on the FX60
> by highly constraining the timing of the LL_TEMAC in map/PR. On my
> ML403 I used similar constraints and it fixed the problem, but only if
> the device is plugged into a GigE switch. The problem is still there
> with the same .bit file on a 100-T switch.
>
>
> Are you on a GigE switch?
>
>
>
> Rob.
>
>
>
>
>
>
> On Tue, 2008-04-01 at 16:15 +0000, MingLiu wrote:
> > Dear John,
> >
> > Thank you for your replying.
> >
> > >It’s not obvious to me what the problem is as I don’t see any driver
> > failures. Have you >tried using a ramdisk and then seeing if the
> > network is working before using NFS root?
> >
> > Not yet. I will try it soon. However from the information on the
> > LL_TEMAC, it seems everything is fine and it should work.
> >
> >
> >
> > >And I’m assuming you have used the NFS root before so you know that
> > it’s good for sure.
> >
> >
> >
> > >I test on the ML405 with NFS root and haven’t seen this problem, but
> > my setup is a little different. I use DHCP rather than >a static IP,
> > but other than that it’s similar.
> >
> >
> >
> > Yes. I used NFS before. I can make sure my NFS server works well. Also
> > in principle, static IP should get a same result as DHCP, I think.
> >
> >
> >
> > >How long has it been since you pulled from the Xilinx Git tree?
> >
> >
> >
> > I just pulled the Xilinx tree quite recently. I am using a latest
> > kernel.
> >
> >
> >
> > BR
> >
> > Ming
> >
> >
> >
> >
> >
> > And I’m assuming you have used the NFS root before so you know
> > that it’s good for sure.
> >
> >
> >
> > I test on the ML405 with NFS root and haven’t seen this
> > problem, but my setup is a little different. I use DHCP
> > rather than a static IP, but other than that it’s similar.
> >
> >
> >
> > I’m assuming that you accidentally got 2 different powerup
> > outputs in the message below as the 1st stops and a 2nd starts
> > in the middle.
> >
> >
> >
> > How long has it been since you pulled from the Xilinx Git
> > tree?
> >
> >
> >
> > Thanks,
> >
> > John
> >
> >
> >
> >
> > ______________________________________________________________
> > From: linuxppc-embedded-bounces
> > +john.linn=xilinx.com@ozlabs.org
> > [mailto:linuxppc-embedded-bounces
> > +john.linn=xilinx.com@ozlabs.org] On Behalf Of MingLiu
> > Sent: Tuesday, April 01, 2008 8:12 AM
> > To: linuxppc-embedded@ozlabs.org
> > Subject: xilinx Ml405 NFS mount problem
> >
> >
> >
> >
> > Dear friends,
> >
> > I am bringing up my kernel from Xilinx git tree. Unfortunately I met some
> > problem when mounting the root file system. Here is the information
> > listed. I will appreciate a lot if someone can help me out of the trouble.
> > Thanks a lot!
> >
> >
> > loaded at: 00400000 0059F19C
> > board data at: 0059D120 0059D19C
> > relocated to: 004050C8 00405144
> > zimage at: 00405F3F 0059C025
> > avail ram: 005A0000 08000000
> >
> > Linux/PPC load: root=/dev/nfs
> > ip=192.168.0.4:192.168.0.3:192.168.0.3:255.255.255.0 rw
> > nfsroot=192.168.0.3:/home/mingliu/ml403_rootfs console=ttyUL0,38400
> > mem=32M
> > Uncompressing Linux...done.
> > Now booting the kernel
> > Linux version 2.6.24-rc8-xlnx-g1db182b8-dirty (mingliu@cca01) (gcc version
> > 3.4.1) #7 Tue Apr 1 14:55:25 CEST 2008
> > Xilinx Generic PowerPC board support package (Xilinx ML405) (Virtex-4 FX)
> > Zone PFN ranges:
> > DMA 0 -> 8192
> >
> > Normal 8192 -> 8192
> >
> > HighMem 8192 -> 8192
> > Movable zone start PFN for each node
> > early_node_map[1] active PFN ranges
> > 0: 0 -> 8192
> > Built 1 zonelists in Zone order, mobility grouping on. Total pages: 8128
> > Kernel command line: root=/de v/nfs
> > ip=192.168.0.4:192.168.0.3:192.168.0.3:255.255.255.0 rw
> > nfsroot=192.168.0.3:/home/mingliu/ml403_rootfs console=ttyUL0,38400
> > mem=32M
> > Xilinx INTC #0 at 0x81800000 mapped to 0xFDFFF000
> > PID hash table entries: 128 (order: 7, 512 bytes)
> > Console: colour dummy device 80x25
> > Dentry cache hash table entries: 4096 (order: 2, 16384 bytes)
> > Inode-cache hash table entries: 2048 (order: 1, 8192 bytes)
> > Memory: 28884k available (2552k kernel code, 944k data, 84k init, 0k highmem)
> > SLUB: Genslabs=11, HWalign=32, Order=0-1, MinObjects=4, CPUs=1, Nodes=1
> > Mount-cache hash table entries: 512
> > net_namespace: 64 bytes
> > NET: Registered protocol family 16
> > Registering device uartlite:0
> > Fixup MAC address for xilinx_lltemac:0
> > Regis tering device xilinx_lltemac:0
> > NET: Registered protocol family 2
> > IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
> > TCP established hash table entries: 1024 (order: 1, 8192 bytes)
> > TCP bind hash table entries: 1024 (order: 0, 4096 bytes)
> > TCP: Hash tables configured (established 1024 bind 1024)
> > TCP reno registered
> > sysctl table check failed: /kernel/l2cr .1.31 Missing strategy
> > Call Trace:
> > [c1c0fe50] [c0008b70] show_stack+0x40/0x194 (unreliable)
> > [c1c0fe90] [c003aed4] set_fail+0x68/0x80
> > [c1c0feb0] [c003b4ec] sysctl_check_table+0x600/0x77c
> > [c1c0fef0] [c003b4d4] sysctl_check_table+0x5e8/0x77c
> > [c1c0ff30] [c002605c] register_sysctl_table+0x64/0xb4
> > [c1c0ff50] [c034579c] register_ppc_htab_sysctl+0x18/0x2c
> > [c1c0ff60] [c034482c] kernel_init+0x94/0x2bc
> > [c1c0fff0] [c0004d58] kernel_thread+0x44/0x60
> > Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
> > fuse init (API version 7.9)
> > io scheduler noop registered
> > io scheduler anticipatory registered
> > io scheduler deadline registered
> > io scheduler cfq registered (default)
> > uartlite.0: ttyUL0 at MM IO 0x84000003 (irq = 3) is a uartlite
> > console [ttyUL0] enabled
> > loop: module loaded
> > nbd: registered device at major 43
> > xilinx_lltemac xilinx_lltemac.0: MAC address is now 0: a:35: 1: 2: 3
> > xilinx_lltemac xilinx_lltemac.0: XLlTemac: using DMA mode.
> > XLlTemac: Dma base address: phy: 0x84600100, virt: 0xc3008100
> > XLlTemac: buffer descriptor size: 32768 (0x8000)
> > XLlTemac: Allocating DMA descriptors with kmalloc<6>XLlTemac:
> > (buffer_descriptor_init) phy: 0x1d18000, virt: 0xc1d18000, size: 0x8000
> > XTemac: PHY detected at address 7.
> > xilinx_lltemac xilinx_lltemac.0: eth0: Xilinx TEMAC at 0x81C00000 mapped
> > to 0xC3004000, irq=2
> > console [netcon0] enabled
> > Linux version 2.6.24-rc8-xlnx-g1db182b8-dirty (mingliu@cca01) (gcc version
> > 3.4.1) #7 Tue Apr 1 14:55:25 CEST 2008
> >
> > Xilinx Generic PowerPC board support package (Xilinx ML405)
> > (Virtex-4 FX)
> >
> > Zone PFN ranges:
> > DMA 0 -> 8192
> > Normal 8192 -> 8192
> > HighMem 8192 -> 8192
> > Movable zone start PFN for each node
> > early_node_map[1] active PFN range
> > s
> > 0: 0 -> 8192
> > Built 1 zonelists in Zone order, mobility grouping on. Total pages: 8128
> > Kernel command line: root=/dev/nfs
> > ip=192.168.0.4:192.168.0.3:192.168.0.3:255.255.255.0 rw
> > nfsroot=192.168.0.3:/home/mingliu/ml403_rootfs console=ttyUL0,38400
> > mem=32M
> > Xilinx INTC #0 at 0x81800000 mapped to 0xFDFFF000
> > PID hash table entries: 128 (order: 7, 512 bytes)
> > Console: colour dummy device 80x25
> > Dentry cache hash table entries: 4096 (order: 2, 16384 bytes)
> > Inode-cache hash table entries: 2048 (order: 1, 8192 bytes)
> > Memory: 28884k available (2552k kernel code, 944k data, 84k init, 0k highmem)
> > SLUB: Genslabs=11, HWalign=32, Order=0-1, MinObjects=4, CPUs=1, Nodes=1
> > Mount-cache hash table entries: 512
> > n
> > et_namespace: 64 bytes
> > NET: Registered protocol family 16
> > Registering device uartlite:0
> > Fixup MAC address for xilinx_lltemac:0
> > Registering device xilinx_lltemac:0
> > NET: Registered protocol family 2
> > IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
> > TCP established hash table entries: 1024 (order: 1, 8192 bytes)
> > TCP bind hash table entries: 1024
> > (order: 0, 4096 bytes)
> > TCP: Hash tables configured (established 1024 bind 1024)
> > TCP reno registered
> > sysctl table check failed: /kernel/l2cr .1.31 Missing strategy
> > Call Trace:
> > [c1c0fe50] [c0008b70] show_stack+0x40/0x194 (unreliable)
> > [c1c0fe90] [c003aed4] set_fail+0x68/0x80
> > [c1c0feb0] [c003b4ec] sysctl_check_table+0x600/0x77c
> > [c1c0fef0] [c003b4d4] sysctl_c
> > heck_table+0x5e8/0x77c
> > [c1c0ff30] [c002605c] register_sysctl_table+0x64/0xb4
> > [c1c0ff50] [c034579c] register_ppc_htab_sysctl+0x18/0x2c
> > [c1c0ff60] [c034482c] kernel_init+0x94/0x2bc
> > [c1c0fff0] [c0004d58] kernel_thread+0x44/0x60
> > Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
> > fuse init (API version 7.9)
> > io scheduler noop registered<
> > /SPAN>
> > io scheduler anticipatory registered
> > io scheduler deadline registered
> > io scheduler cfq registered (default)
> > uartlite.0: ttyUL0 at MMIO 0x84000003 (irq = 3) is a uartlite
> > console [ttyUL0] enabled
> > loop: module loaded
> > nbd: registered device at major 43
> > xilinx_lltemac xilinx_lltemac.0: MAC address is now 0: a:35: 1: 2: 3
> > xilinx_lltemac xilinx_lltemac.0: XLlTemac: using DMA mode.
> > XLlTemac: Dma base address: phy: 0x84600100, virt: 0xc3008100
> > XLlTemac: buffer descriptor size: 32768 (0x8000)
> > XLlTemac: Allocating DMA descriptors with kmalloc<6>XLlTemac:
> > (buffer_descriptor_init) phy: 0x1d18000, virt: 0xc1d18000, size: 0x8000
> > XTemac: PHY detected at address 7.
> > xilinx_lltemac xilinx_lltemac.0: eth0: Xilinx TEMAC at 0x81C00000 mapped
> > <
> > SPAN style="FONT-SIZE: 12pt">to 0xC3004000, irq=2
> > console [netcon0] enabled
> > netconsole: network logging started
> > Generic platform RAM MTD, (c) 2004 Simtec Electronics
> > mice: PS/2 mouse device common for all mice
> > TCP cubic registered
> > NET: Registered protocol family 1
> > NET: Registered protocol family 17
> > RPC: Registered udp transport module.
> > RPC: Registered tcp transport module.
> > eth0: XLlTemac: Options: 0x3fa
> > eth0: XLlTemac: allocating interrupt 0 for dma mode tx.
> > eth0: XLlTemac: allocating interrupt 1 for dma mode rx.
> > eth0: XLlTemac: speed set to 1000Mb/s
> > eth0: XLlTemac: Send Threshold = 24, Receive Threshold = 4
> > eth0: XLlTemac: Send Wait bound = 254, Receive Wait bound = 254
> > IP-Config: Complete:
> >
> > device=eth0, addr=192.168.0.4, mask=255.255.255.0, gw=192.168.0.3,
> > host=192.168.0.4, domain=, nis-domain=(none),
> > bootserver=192.168.0.3, rootserver=192.168.0.3, rootpath=
> > Looking up port of RPC 100003/2 on 192.168.0.3
> > rpcbind: server 192.168.0.3 not responding, timed out
> > Root-NFS: Unable to get nfsd port number from server, using default
> > Looking up port of RPC 10000
> > 5/1 on 192.168.0.3
> > rpcbind: server 192.168.0.3 not responding, timed out
> > Root-NFS: Unable to get mountd port number from server, using default
> > mount: server 192.168.0.3 not responding, timed out
> > Root-NFS: Server returned error -5 while mounting /home/mingliu/ml403_rootfs
> > VFS: Unable to mount root fs via NFS, trying floppy.
> > VFS: Cannot open root device "nfs" or unknown-block(2,0)
> > Please append a correct "root=" boot option; here are
> > the available
> > partitions:
> > Kernel panic - not syncing: VFS: Unable to mount root fs on
> > unknown-block(2,0)
> > Rebooting in 180 seconds..
> >
> >
> > BR
> > Ming
> >
> >
> >
> >
> > ______________________________________________________________
> > Windows Live Writer，支持离线撰写博客内容，随时随地想写就写。
> > 立即使用！
> >
> >
> >
> >
> > ______________________________________________________________________
> > 使用新一代 Windows Live Messenger 轻松交流和共享！ 立即体验！
> > _______________________________________________
> > Linuxppc-embedded mailing list
> > Linuxppc-embedded@ozlabs.org
> > https://ozlabs.org/mailman/listinfo/linuxppc-embedded
>
>
>
^ permalink raw reply [flat|nested] 10+ messages in thread
* RE: xilinx Ml405 NFS mount problem
2008-04-01 23:43 ` Robert Woodworth
@ 2008-04-01 23:54 ` Rick Moleres
2008-04-01 23:55 ` John Linn
1 sibling, 0 replies; 10+ messages in thread
From: Rick Moleres @ 2008-04-01 23:54 UTC (permalink / raw)
To: Robert Woodworth, John Linn; +Cc: linuxppc-embedded
Robert,
I saw an earlier email regarding v1.00b of xps_ll_temac. Besides the =
checksum offload issue in this version of the core, there is also an =
issue when receiving multicast packets where we've seen some ping =
packets lost around receipt of a multicast packets. So for example, we =
saw this issue when attached to a switch/router that sends out STP =
packets. When attached directly between target and host the issue =
disappeared. I believe this issue is fixed in v1.01a of the core being =
released in EDK 10.1. I also think there's an answer record on how to =
work around this issue, but I don't have that AR number handy (search =
the Xilinx website and let me know if you don't find it - if you think =
this applies to you at all).
The issue you describe below doesn't appear to match the multicast =
issue, as you should see that regardless of which part you're in. You =
may want to talk to your FAE as to possible hw timing issues.
Thanks,
Rick
-----Original Message-----
From: linuxppc-embedded-bounces+moleres=3Dxilinx.com@ozlabs.org =
[mailto:linuxppc-embedded-bounces+moleres=3Dxilinx.com@ozlabs.org] On =
Behalf Of Robert Woodworth
Sent: Tuesday, April 01, 2008 5:44 PM
To: John Linn
Cc: linuxppc-embedded@ozlabs.org
Subject: RE: xilinx Ml405 NFS mount problem
Can you test your packet loss with your setup??
GigE or 100T??
Do you have hardware checksum turned on in your bitfile?
I strongly believe that there is a timing problem in the MPMC3/LL_TEMAC.
I think the smaller FX12 does not suffer as much as the larger FX60. My
FX12 is fairly good, my FX60 is very bad. Guessing. The FX20 in the
ML405 is somewhere between.
When I make small changes to my bit file (I'm currently working on an
image processing HDL module) the quality of my LL_TEMAC changes
dramatically. If I take out one of my custom modules and re-synthesize
the LL_TEMAC packet loss goes way up. Add another module, re-synthesize
and packet loss is down.
I would *really* like a Xilinx EDK expert give me some advise on this
issue.
Rob.
On Tue, 2008-04-01 at 10:53 -0600, John Linn wrote:
> Now that you say that, I have been running TCP with my NFS mount as =
I'm mounting across a corporate network.
>=20
> I am also using the latest LL TEMAC with EDK 10.1.
>=20
> Thanks,
> John
>=20
> -----Original Message-----
> From: Robert Woodworth [mailto:rwoodworth@securics.com]=20
> Sent: Tuesday, April 01, 2008 10:50 AM
> To: MingLiu
> Cc: John Linn; linuxppc-embedded@ozlabs.org
> Subject: RE: xilinx Ml405 NFS mount problem
>=20
> I think you may be suffering from the latest LL_TEMAC packet loss
> problem. (NFS/UDP really does not like packet loss)
>=20
>=20
> Let me guess. =20
> You are using a base system from "Base System Builder Wizard"?
> EDK 9.2i. Default syntheses/P&R options.
>=20
> I have seen a massive packet loss problems on my ML403 and two other
> boards I have with an FX60.
>=20
> This is probably a hardware problem.
> Xilinx has acknowledged an LL_TEMAC problem to me but has not provided =
a
> fix. I have heard that things are better with EDK/ISE-10.1 but I have
> not tested it.
>=20
>=20
> The vendor of one of my boards (Pico) has fixed the problem on the =
FX60
> by highly constraining the timing of the LL_TEMAC in map/PR. On my
> ML403 I used similar constraints and it fixed the problem, but only if
> the device is plugged into a GigE switch. The problem is still there
> with the same .bit file on a 100-T switch.=20
>=20
>=20
> Are you on a GigE switch?
>=20
>=20
>=20
> Rob.
>=20
>=20
>=20
>=20
>=20
>=20
> On Tue, 2008-04-01 at 16:15 +0000, MingLiu wrote:
> > Dear John,
> > =20
> > Thank you for your replying.=20
> >=20
> > >It=A1=AFs not obvious to me what the problem is as I don=A1=AFt see =
any driver
> > failures. Have you >tried using a ramdisk and then seeing if the
> > network is working before using NFS root? =20
> > =20
> > Not yet. I will try it soon. However from the information on the
> > LL_TEMAC, it seems everything is fine and it should work.=20
> > =20
> >=20
> >=20
> > >And I=A1=AFm assuming you have used the NFS root before so you know =
that
> > it=A1=AFs good for sure.
> >=20
> > =20
> >=20
> > >I test on the ML405 with NFS root and haven=A1=AFt seen this =
problem, but
> > my setup is a little different. I use DHCP rather than >a static =
IP,
> > but other than that it=A1=AFs similar.
> >=20
> > =20
> >=20
> > Yes. I used NFS before. I can make sure my NFS server works well. =
Also
> > in principle, static IP should get a same result as DHCP, I think.=20
> >=20
> > =20
> >=20
> > >How long has it been since you pulled from the Xilinx Git tree?
> >=20
> > =20
> >=20
> > I just pulled the Xilinx tree quite recently. I am using a latest
> > kernel.
> >=20
> > =20
> >=20
> > BR=20
> >=20
> > Ming
> >=20
> > =20
> >=20
> > =20
> > =20
> > And I=A1=AFm assuming you have used the NFS root before so =
you know
> > that it=A1=AFs good for sure.
> > =20
> > =20
> > =20
> > I test on the ML405 with NFS root and haven=A1=AFt seen this
> > problem, but my setup is a little different. I use DHCP
> > rather than a static IP, but other than that it=A1=AFs =
similar.
> > =20
> > =20
> > =20
> > I=A1=AFm assuming that you accidentally got 2 different =
powerup
> > outputs in the message below as the 1st stops and a 2nd =
starts
> > in the middle.
> > =20
> > =20
> > =20
> > How long has it been since you pulled from the Xilinx Git
> > tree?
> > =20
> > =20
> > =20
> > Thanks,
> > =20
> > John
> > =20
> > =20
> > =20
> > =20
> > =
______________________________________________________________
> > From: linuxppc-embedded-bounces
> > +john.linn=3Dxilinx.com@ozlabs.org
> > [mailto:linuxppc-embedded-bounces
> > +john.linn=3Dxilinx.com@ozlabs.org] On Behalf Of MingLiu
> > Sent: Tuesday, April 01, 2008 8:12 AM
> > To: linuxppc-embedded@ozlabs.org
> > Subject: xilinx Ml405 NFS mount problem
> > =20
> > =20
> > =20
> > =20
> > Dear friends,
> > =20
> > I am bringing up my kernel from Xilinx git tree. =
Unfortunately I met some
> > problem when mounting the root file system. Here is the =
information
> > listed. I will appreciate a lot if someone can help me out =
of the trouble.=20
> > Thanks a lot!
> > =20
> > =20
> > loaded at: 00400000 0059F19C
> > board data at: 0059D120 0059D19C
> > relocated to: 004050C8 00405144
> > zimage at: 00405F3F 0059C025
> > avail ram: 005A0000 08000000
> > =20
> > Linux/PPC load: root=3D/dev/nfs
> > ip=3D192.168.0.4:192.168.0.3:192.168.0.3:255.255.255.0 rw
> > nfsroot=3D192.168.0.3:/home/mingliu/ml403_rootfs =
console=3DttyUL0,38400
> > mem=3D32M
> > Uncompressing Linux...done.
> > Now booting the kernel
> > Linux version 2.6.24-rc8-xlnx-g1db182b8-dirty =
(mingliu@cca01) (gcc version
> > 3.4.1) #7 Tue Apr 1 14:55:25 CEST 2008
> > Xilinx Generic PowerPC board support package (Xilinx ML405) =
(Virtex-4 FX)
> > Zone PFN ranges:
> > DMA 0 -> 8192
> > =20
> > Normal 8192 -> 8192
> > =20
> > HighMem 8192 -> 8192
> > Movable zone start PFN for each node
> > early_node_map[1] active PFN ranges
> > 0: 0 -> 8192
> > Built 1 zonelists in Zone order, mobility grouping on. =
Total pages: 8128
> > Kernel command line: root=3D/de v/nfs
> > ip=3D192.168.0.4:192.168.0.3:192.168.0.3:255.255.255.0 rw
> > nfsroot=3D192.168.0.3:/home/mingliu/ml403_rootfs =
console=3DttyUL0,38400
> > mem=3D32M
> > Xilinx INTC #0 at 0x81800000 mapped to 0xFDFFF000
> > PID hash table entries: 128 (order: 7, 512 bytes)
> > Console: colour dummy device 80x25
> > Dentry cache hash table entries: 4096 (order: 2, 16384 =
bytes)
> > Inode-cache hash table entries: 2048 (order: 1, 8192 bytes)
> > Memory: 28884k available (2552k kernel code, 944k data, 84k =
init, 0k highmem)
> > SLUB: Genslabs=3D11, HWalign=3D32, Order=3D0-1, =
MinObjects=3D4, CPUs=3D1, Nodes=3D1
> > Mount-cache hash table entries: 512
> > net_namespace: 64 bytes
> > NET: Registered protocol family 16
> > Registering device uartlite:0
> > Fixup MAC address for xilinx_lltemac:0
> > Regis tering device xilinx_lltemac:0
> > NET: Registered protocol family 2
> > IP route cache hash table entries: 1024 (order: 0, 4096 =
bytes)
> > TCP established hash table entries: 1024 (order: 1, 8192 =
bytes)
> > TCP bind hash table entries: 1024 (order: 0, 4096 bytes)
> > TCP: Hash tables configured (established 1024 bind 1024)
> > TCP reno registered
> > sysctl table check failed: /kernel/l2cr .1.31 Missing =
strategy
> > Call Trace:
> > [c1c0fe50] [c0008b70] show_stack+0x40/0x194 (unreliable)
> > [c1c0fe90] [c003aed4] set_fail+0x68/0x80
> > [c1c0feb0] [c003b4ec] sysctl_check_table+0x600/0x77c
> > [c1c0fef0] [c003b4d4] sysctl_check_table+0x5e8/0x77c
> > [c1c0ff30] [c002605c] register_sysctl_table+0x64/0xb4
> > [c1c0ff50] [c034579c] register_ppc_htab_sysctl+0x18/0x2c
> > [c1c0ff60] [c034482c] kernel_init+0x94/0x2bc
> > [c1c0fff0] [c0004d58] kernel_thread+0x44/0x60
> > Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
> > fuse init (API version 7.9)
> > io scheduler noop registered
> > io scheduler anticipatory registered
> > io scheduler deadline registered
> > io scheduler cfq registered (default)
> > uartlite.0: ttyUL0 at MM IO 0x84000003 (irq =3D 3) is a =
uartlite
> > console [ttyUL0] enabled
> > loop: module loaded
> > nbd: registered device at major 43
> > xilinx_lltemac xilinx_lltemac.0: MAC address is now 0: =
a:35: 1: 2: 3
> > xilinx_lltemac xilinx_lltemac.0: XLlTemac: using DMA mode.
> > XLlTemac: Dma base address: phy: 0x84600100, virt: =
0xc3008100
> > XLlTemac: buffer descriptor size: 32768 (0x8000)
> > XLlTemac: Allocating DMA descriptors with =
kmalloc<6>XLlTemac:
> > (buffer_descriptor_init) phy: 0x1d18000, virt: 0xc1d18000, =
size: 0x8000
> > XTemac: PHY detected at address 7.
> > xilinx_lltemac xilinx_lltemac.0: eth0: Xilinx TEMAC at =
0x81C00000 mapped
> > to 0xC3004000, irq=3D2
> > console [netcon0] enabled
> > Linux version 2.6.24-rc8-xlnx-g1db182b8-dirty =
(mingliu@cca01) (gcc version
> > 3.4.1) #7 Tue Apr 1 14:55:25 CEST 2008
> > =20
> > Xilinx Generic PowerPC board support package (Xilinx ML405)
> > (Virtex-4 FX)
> > =20
> > Zone PFN ranges:
> > DMA 0 -> 8192
> > Normal 8192 -> 8192
> > HighMem 8192 -> 8192
> > Movable zone start PFN for each node
> > early_node_map[1] active PFN range
> > s
> > 0: 0 -> 8192
> > Built 1 zonelists in Zone order, mobility grouping on. =
Total pages: 8128
> > Kernel command line: root=3D/dev/nfs
> > ip=3D192.168.0.4:192.168.0.3:192.168.0.3:255.255.255.0 rw
> > nfsroot=3D192.168.0.3:/home/mingliu/ml403_rootfs =
console=3DttyUL0,38400
> > mem=3D32M
> > Xilinx INTC #0 at 0x81800000 mapped to 0xFDFFF000
> > PID hash table entries: 128 (order: 7, 512 bytes)
> > Console: colour dummy device 80x25
> > Dentry cache hash table entries: 4096 (order: 2, 16384 =
bytes)
> > Inode-cache hash table entries: 2048 (order: 1, 8192 bytes)
> > Memory: 28884k available (2552k kernel code, 944k data, 84k =
init, 0k highmem)
> > SLUB: Genslabs=3D11, HWalign=3D32, Order=3D0-1, =
MinObjects=3D4, CPUs=3D1, Nodes=3D1
> > Mount-cache hash table entries: 512
> > n
> > et_namespace: 64 bytes
> > NET: Registered protocol family 16
> > Registering device uartlite:0
> > Fixup MAC address for xilinx_lltemac:0
> > Registering device xilinx_lltemac:0
> > NET: Registered protocol family 2
> > IP route cache hash table entries: 1024 (order: 0, 4096 =
bytes)
> > TCP established hash table entries: 1024 (order: 1, 8192 =
bytes)
> > TCP bind hash table entries: 1024
> > (order: 0, 4096 bytes)
> > TCP: Hash tables configured (established 1024 bind 1024)
> > TCP reno registered
> > sysctl table check failed: /kernel/l2cr .1.31 Missing =
strategy
> > Call Trace:
> > [c1c0fe50] [c0008b70] show_stack+0x40/0x194 (unreliable)
> > [c1c0fe90] [c003aed4] set_fail+0x68/0x80
> > [c1c0feb0] [c003b4ec] sysctl_check_table+0x600/0x77c
> > [c1c0fef0] [c003b4d4] sysctl_c
> > heck_table+0x5e8/0x77c
> > [c1c0ff30] [c002605c] register_sysctl_table+0x64/0xb4
> > [c1c0ff50] [c034579c] register_ppc_htab_sysctl+0x18/0x2c
> > [c1c0ff60] [c034482c] kernel_init+0x94/0x2bc
> > [c1c0fff0] [c0004d58] kernel_thread+0x44/0x60
> > Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
> > fuse init (API version 7.9)
> > io scheduler noop registered<
> > /SPAN>
> > io scheduler anticipatory registered
> > io scheduler deadline registered
> > io scheduler cfq registered (default)
> > uartlite.0: ttyUL0 at MMIO 0x84000003 (irq =3D 3) is a =
uartlite
> > console [ttyUL0] enabled
> > loop: module loaded
> > nbd: registered device at major 43
> > xilinx_lltemac xilinx_lltemac.0: MAC address is now 0: =
a:35: 1: 2: 3
> > xilinx_lltemac xilinx_lltemac.0: XLlTemac: using DMA mode.
> > XLlTemac: Dma base address: phy: 0x84600100, virt: =
0xc3008100
> > XLlTemac: buffer descriptor size: 32768 (0x8000)
> > XLlTemac: Allocating DMA descriptors with =
kmalloc<6>XLlTemac:
> > (buffer_descriptor_init) phy: 0x1d18000, virt: 0xc1d18000, =
size: 0x8000
> > XTemac: PHY detected at address 7.
> > xilinx_lltemac xilinx_lltemac.0: eth0: Xilinx TEMAC at =
0x81C00000 mapped
> > <
> > SPAN style=3D"FONT-SIZE: 12pt">to 0xC3004000, irq=3D2
> > console [netcon0] enabled
> > netconsole: network logging started
> > Generic platform RAM MTD, (c) 2004 Simtec Electronics
> > mice: PS/2 mouse device common for all mice
> > TCP cubic registered
> > NET: Registered protocol family 1
> > NET: Registered protocol family 17
> > RPC: Registered udp transport module.
> > RPC: Registered tcp transport module.
> > eth0: XLlTemac: Options: 0x3fa
> > eth0: XLlTemac: allocating interrupt 0 for dma mode tx.
> > eth0: XLlTemac: allocating interrupt 1 for dma mode rx.
> > eth0: XLlTemac: speed set to 1000Mb/s
> > eth0: XLlTemac: Send Threshold =3D 24, Receive Threshold =3D =
4
> > eth0: XLlTemac: Send Wait bound =3D 254, Receive Wait bound =
=3D 254
> > IP-Config: Complete:
> > =20
> > device=3Deth0, addr=3D192.168.0.4, =
mask=3D255.255.255.0, gw=3D192.168.0.3,
> > host=3D192.168.0.4, domain=3D, nis-domain=3D(none),
> > bootserver=3D192.168.0.3, rootserver=3D192.168.0.3, =
rootpath=3D
> > Looking up port of RPC 100003/2 on 192.168.0.3
> > rpcbind: server 192.168.0.3 not responding, timed out
> > Root-NFS: Unable to get nfsd port number from server, using =
default
> > Looking up port of RPC 10000
> > 5/1 on 192.168.0.3
> > rpcbind: server 192.168.0.3 not responding, timed out
> > Root-NFS: Unable to get mountd port number from server, =
using default
> > mount: server 192.168.0.3 not responding, timed out
> > Root-NFS: Server returned error -5 while mounting =
/home/mingliu/ml403_rootfs
> > VFS: Unable to mount root fs via NFS, trying floppy.
> > VFS: Cannot open root device "nfs" or unknown-block(2,0)
> > Please append a correct "root=3D" boot option; here are=20
> > the available
> > partitions:
> > Kernel panic - not syncing: VFS: Unable to mount root fs on
> > unknown-block(2,0)
> > Rebooting in 180 seconds..
> > =20
> > =20
> > BR
> > Ming
> > =20
> > =20
> > =20
> > =20
> > =
______________________________________________________________
> > Windows Live =
Writer=A3=AC=D6=A7=B3=D6=C0=EB=CF=DF=D7=AB=D0=B4=B2=A9=BF=CD=C4=DA=C8=DD=A3=
=AC=CB=E6=CA=B1=CB=E6=B5=D8=CF=EB=D0=B4=BE=CD=D0=B4=A1=A3
> > =C1=A2=BC=B4=CA=B9=D3=C3=A3=A1
> > =20
> > =20
> >=20
> >=20
> > =
______________________________________________________________________
> > =CA=B9=D3=C3=D0=C2=D2=BB=B4=FA Windows Live Messenger =
=C7=E1=CB=C9=BD=BB=C1=F7=BA=CD=B9=B2=CF=ED=A3=A1 =
=C1=A2=BC=B4=CC=E5=D1=E9=A3=A1=20
> > _______________________________________________
> > Linuxppc-embedded mailing list
> > Linuxppc-embedded@ozlabs.org
> > https://ozlabs.org/mailman/listinfo/linuxppc-embedded
>=20
>=20
>=20
_______________________________________________
Linuxppc-embedded mailing list
Linuxppc-embedded@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-embedded
^ permalink raw reply [flat|nested] 10+ messages in thread
* RE: xilinx Ml405 NFS mount problem
2008-04-01 23:43 ` Robert Woodworth
2008-04-01 23:54 ` Rick Moleres
@ 2008-04-01 23:55 ` John Linn
1 sibling, 0 replies; 10+ messages in thread
From: John Linn @ 2008-04-01 23:55 UTC (permalink / raw)
To: Robert Woodworth; +Cc: linuxppc-embedded
Hi Rob,
I am using GigE and no checksum offload.
I don't have a quick way to test packet loss.
EDK 10.1 may help your problem.
-- John
-----Original Message-----
From: Robert Woodworth [mailto:rwoodworth@securics.com]=20
Sent: Tuesday, April 01, 2008 5:44 PM
To: John Linn
Cc: MingLiu; linuxppc-embedded@ozlabs.org
Subject: RE: xilinx Ml405 NFS mount problem
Can you test your packet loss with your setup??
GigE or 100T??
Do you have hardware checksum turned on in your bitfile?
I strongly believe that there is a timing problem in the MPMC3/LL_TEMAC.
I think the smaller FX12 does not suffer as much as the larger FX60. My
FX12 is fairly good, my FX60 is very bad. Guessing. The FX20 in the
ML405 is somewhere between.
When I make small changes to my bit file (I'm currently working on an
image processing HDL module) the quality of my LL_TEMAC changes
dramatically. If I take out one of my custom modules and re-synthesize
the LL_TEMAC packet loss goes way up. Add another module, re-synthesize
and packet loss is down.
I would *really* like a Xilinx EDK expert give me some advise on this
issue.
Rob.
On Tue, 2008-04-01 at 10:53 -0600, John Linn wrote:
> Now that you say that, I have been running TCP with my NFS mount as =
I'm mounting across a corporate network.
>=20
> I am also using the latest LL TEMAC with EDK 10.1.
>=20
> Thanks,
> John
>=20
> -----Original Message-----
> From: Robert Woodworth [mailto:rwoodworth@securics.com]=20
> Sent: Tuesday, April 01, 2008 10:50 AM
> To: MingLiu
> Cc: John Linn; linuxppc-embedded@ozlabs.org
> Subject: RE: xilinx Ml405 NFS mount problem
>=20
> I think you may be suffering from the latest LL_TEMAC packet loss
> problem. (NFS/UDP really does not like packet loss)
>=20
>=20
> Let me guess. =20
> You are using a base system from "Base System Builder Wizard"?
> EDK 9.2i. Default syntheses/P&R options.
>=20
> I have seen a massive packet loss problems on my ML403 and two other
> boards I have with an FX60.
>=20
> This is probably a hardware problem.
> Xilinx has acknowledged an LL_TEMAC problem to me but has not provided =
a
> fix. I have heard that things are better with EDK/ISE-10.1 but I have
> not tested it.
>=20
>=20
> The vendor of one of my boards (Pico) has fixed the problem on the =
FX60
> by highly constraining the timing of the LL_TEMAC in map/PR. On my
> ML403 I used similar constraints and it fixed the problem, but only if
> the device is plugged into a GigE switch. The problem is still there
> with the same .bit file on a 100-T switch.=20
>=20
>=20
> Are you on a GigE switch?
>=20
>=20
>=20
> Rob.
>=20
>=20
>=20
>=20
>=20
>=20
> On Tue, 2008-04-01 at 16:15 +0000, MingLiu wrote:
> > Dear John,
> > =20
> > Thank you for your replying.=20
> >=20
> > >It=A1=AFs not obvious to me what the problem is as I don=A1=AFt see =
any driver
> > failures. Have you >tried using a ramdisk and then seeing if the
> > network is working before using NFS root? =20
> > =20
> > Not yet. I will try it soon. However from the information on the
> > LL_TEMAC, it seems everything is fine and it should work.=20
> > =20
> >=20
> >=20
> > >And I=A1=AFm assuming you have used the NFS root before so you know =
that
> > it=A1=AFs good for sure.
> >=20
> > =20
> >=20
> > >I test on the ML405 with NFS root and haven=A1=AFt seen this =
problem, but
> > my setup is a little different. I use DHCP rather than >a static =
IP,
> > but other than that it=A1=AFs similar.
> >=20
> > =20
> >=20
> > Yes. I used NFS before. I can make sure my NFS server works well. =
Also
> > in principle, static IP should get a same result as DHCP, I think.=20
> >=20
> > =20
> >=20
> > >How long has it been since you pulled from the Xilinx Git tree?
> >=20
> > =20
> >=20
> > I just pulled the Xilinx tree quite recently. I am using a latest
> > kernel.
> >=20
> > =20
> >=20
> > BR=20
> >=20
> > Ming
> >=20
> > =20
> >=20
> > =20
> > =20
> > And I=A1=AFm assuming you have used the NFS root before so =
you know
> > that it=A1=AFs good for sure.
> > =20
> > =20
> > =20
> > I test on the ML405 with NFS root and haven=A1=AFt seen this
> > problem, but my setup is a little different. I use DHCP
> > rather than a static IP, but other than that it=A1=AFs =
similar.
> > =20
> > =20
> > =20
> > I=A1=AFm assuming that you accidentally got 2 different =
powerup
> > outputs in the message below as the 1st stops and a 2nd =
starts
> > in the middle.
> > =20
> > =20
> > =20
> > How long has it been since you pulled from the Xilinx Git
> > tree?
> > =20
> > =20
> > =20
> > Thanks,
> > =20
> > John
> > =20
> > =20
> > =20
> > =20
> > =
______________________________________________________________
> > From: linuxppc-embedded-bounces
> > +john.linn=3Dxilinx.com@ozlabs.org
> > [mailto:linuxppc-embedded-bounces
> > +john.linn=3Dxilinx.com@ozlabs.org] On Behalf Of MingLiu
> > Sent: Tuesday, April 01, 2008 8:12 AM
> > To: linuxppc-embedded@ozlabs.org
> > Subject: xilinx Ml405 NFS mount problem
> > =20
> > =20
> > =20
> > =20
> > Dear friends,
> > =20
> > I am bringing up my kernel from Xilinx git tree. =
Unfortunately I met some
> > problem when mounting the root file system. Here is the =
information
> > listed. I will appreciate a lot if someone can help me out =
of the trouble.=20
> > Thanks a lot!
> > =20
> > =20
> > loaded at: 00400000 0059F19C
> > board data at: 0059D120 0059D19C
> > relocated to: 004050C8 00405144
> > zimage at: 00405F3F 0059C025
> > avail ram: 005A0000 08000000
> > =20
> > Linux/PPC load: root=3D/dev/nfs
> > ip=3D192.168.0.4:192.168.0.3:192.168.0.3:255.255.255.0 rw
> > nfsroot=3D192.168.0.3:/home/mingliu/ml403_rootfs =
console=3DttyUL0,38400
> > mem=3D32M
> > Uncompressing Linux...done.
> > Now booting the kernel
> > Linux version 2.6.24-rc8-xlnx-g1db182b8-dirty =
(mingliu@cca01) (gcc version
> > 3.4.1) #7 Tue Apr 1 14:55:25 CEST 2008
> > Xilinx Generic PowerPC board support package (Xilinx ML405) =
(Virtex-4 FX)
> > Zone PFN ranges:
> > DMA 0 -> 8192
> > =20
> > Normal 8192 -> 8192
> > =20
> > HighMem 8192 -> 8192
> > Movable zone start PFN for each node
> > early_node_map[1] active PFN ranges
> > 0: 0 -> 8192
> > Built 1 zonelists in Zone order, mobility grouping on. =
Total pages: 8128
> > Kernel command line: root=3D/de v/nfs
> > ip=3D192.168.0.4:192.168.0.3:192.168.0.3:255.255.255.0 rw
> > nfsroot=3D192.168.0.3:/home/mingliu/ml403_rootfs =
console=3DttyUL0,38400
> > mem=3D32M
> > Xilinx INTC #0 at 0x81800000 mapped to 0xFDFFF000
> > PID hash table entries: 128 (order: 7, 512 bytes)
> > Console: colour dummy device 80x25
> > Dentry cache hash table entries: 4096 (order: 2, 16384 =
bytes)
> > Inode-cache hash table entries: 2048 (order: 1, 8192 bytes)
> > Memory: 28884k available (2552k kernel code, 944k data, 84k =
init, 0k highmem)
> > SLUB: Genslabs=3D11, HWalign=3D32, Order=3D0-1, =
MinObjects=3D4, CPUs=3D1, Nodes=3D1
> > Mount-cache hash table entries: 512
> > net_namespace: 64 bytes
> > NET: Registered protocol family 16
> > Registering device uartlite:0
> > Fixup MAC address for xilinx_lltemac:0
> > Regis tering device xilinx_lltemac:0
> > NET: Registered protocol family 2
> > IP route cache hash table entries: 1024 (order: 0, 4096 =
bytes)
> > TCP established hash table entries: 1024 (order: 1, 8192 =
bytes)
> > TCP bind hash table entries: 1024 (order: 0, 4096 bytes)
> > TCP: Hash tables configured (established 1024 bind 1024)
> > TCP reno registered
> > sysctl table check failed: /kernel/l2cr .1.31 Missing =
strategy
> > Call Trace:
> > [c1c0fe50] [c0008b70] show_stack+0x40/0x194 (unreliable)
> > [c1c0fe90] [c003aed4] set_fail+0x68/0x80
> > [c1c0feb0] [c003b4ec] sysctl_check_table+0x600/0x77c
> > [c1c0fef0] [c003b4d4] sysctl_check_table+0x5e8/0x77c
> > [c1c0ff30] [c002605c] register_sysctl_table+0x64/0xb4
> > [c1c0ff50] [c034579c] register_ppc_htab_sysctl+0x18/0x2c
> > [c1c0ff60] [c034482c] kernel_init+0x94/0x2bc
> > [c1c0fff0] [c0004d58] kernel_thread+0x44/0x60
> > Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
> > fuse init (API version 7.9)
> > io scheduler noop registered
> > io scheduler anticipatory registered
> > io scheduler deadline registered
> > io scheduler cfq registered (default)
> > uartlite.0: ttyUL0 at MM IO 0x84000003 (irq =3D 3) is a =
uartlite
> > console [ttyUL0] enabled
> > loop: module loaded
> > nbd: registered device at major 43
> > xilinx_lltemac xilinx_lltemac.0: MAC address is now 0: =
a:35: 1: 2: 3
> > xilinx_lltemac xilinx_lltemac.0: XLlTemac: using DMA mode.
> > XLlTemac: Dma base address: phy: 0x84600100, virt: =
0xc3008100
> > XLlTemac: buffer descriptor size: 32768 (0x8000)
> > XLlTemac: Allocating DMA descriptors with =
kmalloc<6>XLlTemac:
> > (buffer_descriptor_init) phy: 0x1d18000, virt: 0xc1d18000, =
size: 0x8000
> > XTemac: PHY detected at address 7.
> > xilinx_lltemac xilinx_lltemac.0: eth0: Xilinx TEMAC at =
0x81C00000 mapped
> > to 0xC3004000, irq=3D2
> > console [netcon0] enabled
> > Linux version 2.6.24-rc8-xlnx-g1db182b8-dirty =
(mingliu@cca01) (gcc version
> > 3.4.1) #7 Tue Apr 1 14:55:25 CEST 2008
> > =20
> > Xilinx Generic PowerPC board support package (Xilinx ML405)
> > (Virtex-4 FX)
> > =20
> > Zone PFN ranges:
> > DMA 0 -> 8192
> > Normal 8192 -> 8192
> > HighMem 8192 -> 8192
> > Movable zone start PFN for each node
> > early_node_map[1] active PFN range
> > s
> > 0: 0 -> 8192
> > Built 1 zonelists in Zone order, mobility grouping on. =
Total pages: 8128
> > Kernel command line: root=3D/dev/nfs
> > ip=3D192.168.0.4:192.168.0.3:192.168.0.3:255.255.255.0 rw
> > nfsroot=3D192.168.0.3:/home/mingliu/ml403_rootfs =
console=3DttyUL0,38400
> > mem=3D32M
> > Xilinx INTC #0 at 0x81800000 mapped to 0xFDFFF000
> > PID hash table entries: 128 (order: 7, 512 bytes)
> > Console: colour dummy device 80x25
> > Dentry cache hash table entries: 4096 (order: 2, 16384 =
bytes)
> > Inode-cache hash table entries: 2048 (order: 1, 8192 bytes)
> > Memory: 28884k available (2552k kernel code, 944k data, 84k =
init, 0k highmem)
> > SLUB: Genslabs=3D11, HWalign=3D32, Order=3D0-1, =
MinObjects=3D4, CPUs=3D1, Nodes=3D1
> > Mount-cache hash table entries: 512
> > n
> > et_namespace: 64 bytes
> > NET: Registered protocol family 16
> > Registering device uartlite:0
> > Fixup MAC address for xilinx_lltemac:0
> > Registering device xilinx_lltemac:0
> > NET: Registered protocol family 2
> > IP route cache hash table entries: 1024 (order: 0, 4096 =
bytes)
> > TCP established hash table entries: 1024 (order: 1, 8192 =
bytes)
> > TCP bind hash table entries: 1024
> > (order: 0, 4096 bytes)
> > TCP: Hash tables configured (established 1024 bind 1024)
> > TCP reno registered
> > sysctl table check failed: /kernel/l2cr .1.31 Missing =
strategy
> > Call Trace:
> > [c1c0fe50] [c0008b70] show_stack+0x40/0x194 (unreliable)
> > [c1c0fe90] [c003aed4] set_fail+0x68/0x80
> > [c1c0feb0] [c003b4ec] sysctl_check_table+0x600/0x77c
> > [c1c0fef0] [c003b4d4] sysctl_c
> > heck_table+0x5e8/0x77c
> > [c1c0ff30] [c002605c] register_sysctl_table+0x64/0xb4
> > [c1c0ff50] [c034579c] register_ppc_htab_sysctl+0x18/0x2c
> > [c1c0ff60] [c034482c] kernel_init+0x94/0x2bc
> > [c1c0fff0] [c0004d58] kernel_thread+0x44/0x60
> > Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
> > fuse init (API version 7.9)
> > io scheduler noop registered<
> > /SPAN>
> > io scheduler anticipatory registered
> > io scheduler deadline registered
> > io scheduler cfq registered (default)
> > uartlite.0: ttyUL0 at MMIO 0x84000003 (irq =3D 3) is a =
uartlite
> > console [ttyUL0] enabled
> > loop: module loaded
> > nbd: registered device at major 43
> > xilinx_lltemac xilinx_lltemac.0: MAC address is now 0: =
a:35: 1: 2: 3
> > xilinx_lltemac xilinx_lltemac.0: XLlTemac: using DMA mode.
> > XLlTemac: Dma base address: phy: 0x84600100, virt: =
0xc3008100
> > XLlTemac: buffer descriptor size: 32768 (0x8000)
> > XLlTemac: Allocating DMA descriptors with =
kmalloc<6>XLlTemac:
> > (buffer_descriptor_init) phy: 0x1d18000, virt: 0xc1d18000, =
size: 0x8000
> > XTemac: PHY detected at address 7.
> > xilinx_lltemac xilinx_lltemac.0: eth0: Xilinx TEMAC at =
0x81C00000 mapped
> > <
> > SPAN style=3D"FONT-SIZE: 12pt">to 0xC3004000, irq=3D2
> > console [netcon0] enabled
> > netconsole: network logging started
> > Generic platform RAM MTD, (c) 2004 Simtec Electronics
> > mice: PS/2 mouse device common for all mice
> > TCP cubic registered
> > NET: Registered protocol family 1
> > NET: Registered protocol family 17
> > RPC: Registered udp transport module.
> > RPC: Registered tcp transport module.
> > eth0: XLlTemac: Options: 0x3fa
> > eth0: XLlTemac: allocating interrupt 0 for dma mode tx.
> > eth0: XLlTemac: allocating interrupt 1 for dma mode rx.
> > eth0: XLlTemac: speed set to 1000Mb/s
> > eth0: XLlTemac: Send Threshold =3D 24, Receive Threshold =3D =
4
> > eth0: XLlTemac: Send Wait bound =3D 254, Receive Wait bound =
=3D 254
> > IP-Config: Complete:
> > =20
> > device=3Deth0, addr=3D192.168.0.4, =
mask=3D255.255.255.0, gw=3D192.168.0.3,
> > host=3D192.168.0.4, domain=3D, nis-domain=3D(none),
> > bootserver=3D192.168.0.3, rootserver=3D192.168.0.3, =
rootpath=3D
> > Looking up port of RPC 100003/2 on 192.168.0.3
> > rpcbind: server 192.168.0.3 not responding, timed out
> > Root-NFS: Unable to get nfsd port number from server, using =
default
> > Looking up port of RPC 10000
> > 5/1 on 192.168.0.3
> > rpcbind: server 192.168.0.3 not responding, timed out
> > Root-NFS: Unable to get mountd port number from server, =
using default
> > mount: server 192.168.0.3 not responding, timed out
> > Root-NFS: Server returned error -5 while mounting =
/home/mingliu/ml403_rootfs
> > VFS: Unable to mount root fs via NFS, trying floppy.
> > VFS: Cannot open root device "nfs" or unknown-block(2,0)
> > Please append a correct "root=3D" boot option; here are=20
> > the available
> > partitions:
> > Kernel panic - not syncing: VFS: Unable to mount root fs on
> > unknown-block(2,0)
> > Rebooting in 180 seconds..
> > =20
> > =20
> > BR
> > Ming
> > =20
> > =20
> > =20
> > =20
> > =
______________________________________________________________
> > Windows Live =
Writer=A3=AC=D6=A7=B3=D6=C0=EB=CF=DF=D7=AB=D0=B4=B2=A9=BF=CD=C4=DA=C8=DD=A3=
=AC=CB=E6=CA=B1=CB=E6=B5=D8=CF=EB=D0=B4=BE=CD=D0=B4=A1=A3
> > =C1=A2=BC=B4=CA=B9=D3=C3=A3=A1
> > =20
> > =20
> >=20
> >=20
> > =
______________________________________________________________________
> > =CA=B9=D3=C3=D0=C2=D2=BB=B4=FA Windows Live Messenger =
=C7=E1=CB=C9=BD=BB=C1=F7=BA=CD=B9=B2=CF=ED=A3=A1 =
=C1=A2=BC=B4=CC=E5=D1=E9=A3=A1=20
> > _______________________________________________
> > Linuxppc-embedded mailing list
> > Linuxppc-embedded@ozlabs.org
> > https://ozlabs.org/mailman/listinfo/linuxppc-embedded
>=20
>=20
>=20
^ permalink raw reply [flat|nested] 10+ messages in thread
end of thread, other threads:[~2008-04-01 23:55 UTC | newest]
Thread overview: 10+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2008-04-01 14:11 xilinx Ml405 NFS mount problem MingLiu
2008-04-01 14:29 ` John Linn
2008-04-01 16:15 ` MingLiu
2008-04-01 16:50 ` Robert Woodworth
2008-04-01 16:53 ` John Linn
2008-04-01 23:43 ` Robert Woodworth
2008-04-01 23:54 ` Rick Moleres
2008-04-01 23:55 ` John Linn
2008-04-01 18:36 ` MingLiu
2008-04-01 20:42 ` MingLiu
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox