Hi all,
While trying to use NFS hosted filesystem, I have made a strange observation. Have verified it on multiple OMAP3EVM boards.
With CONFIG_NO_HZ and CONFIG_CPU_IDLE, after the print "Freeing init memory: 152K" in the log below; the boot sequence almost stops for approx a minute before proceeding further.
Sending DHCP requests .<6>eth0: link up, 100Mbps, full-duplex, lpa 0x01E1
., OK
IP-Config: Got DHCP answer from 0.0.0.0, my address is 192.168.1.9
IP-Config: Complete:
device=eth0, addr=192.168.1.9, mask=255.255.255.0, gw=192.168.1.9,
host=192.168.1.9, domain=india.ti.com, nis-domain=(none),
bootserver=0.0.0.0, rootserver=192.168.1.2, rootpath=
Looking up port of RPC 100003/2 on 192.168.1.2
Looking up port of RPC 100005/1 on 192.168.1.2
VFS: Mounted root (nfs filesystem).
Freeing init memory: 152K
init started: BusyBox v1.11.1 (2008-08-06 21:12:30 IST)
starting pid 442, tty '': '/etc/init.d/rcS'
Later, the system response is slow.
Toggling either of these CONFIG options seems to resolve the issue.
My initial suspicion was on the SMC911x driver, but during this 'wait' period ping requests to the EVM are successful.
Just wanted to check if anyone has seen this behavior.
(I am on Kevin's latest PM branch 998bd5675a1e...).
Best regards,
Sanjeev
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
