> -----Original Message----- > From: linux-omap-owner@xxxxxxxxxxxxxxx > [mailto:linux-omap-owner@xxxxxxxxxxxxxxx] On Behalf Of Premi, Sanjeev > Sent: Friday, January 23, 2009 12:02 AM > To: Sriram V > Cc: linux-omap@xxxxxxxxxxxxxxx > Subject: RE: cpuidle and NO_HZ > > > -----Original Message----- > > From: Sriram V [mailto:vshrirama@xxxxxxxxx] > > Sent: Thursday, January 22, 2009 10:37 PM > > To: Premi, Sanjeev > > Cc: linux-omap@xxxxxxxxxxxxxxx > > Subject: Re: cpuidle and NO_HZ > > > > Sanjeev, > > > > On Thu, Jan 22, 2009 at 8:14 PM, Premi, Sanjeev > <premi@xxxxxx> wrote: > > > 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' > > > > > > > This seems to be a wakeup issue. SMC gpio irq needs to be > enabled as a > > wakeup source. > > I notice that sometimes even after enabling it as a wakeup source > > network interface has trouble. either it is too slow or it > just hangs > > during nfs mount or takes a long time to mount. this issue could be > > somewhere else > > > > I also notice that the whenever network interface hangs during nfs > > mount. > > the nfs server would have exited. > > [sp]Thanks. I will try the patch. > > I did believe it was a wakeup issue until I had not tried the ping. > All pings were successful; indicating that eth interface is still up. > > The 'mount' succeeding after about a minute is confirms it as well. > > Best regards, > Sanjeev > > [sp] The patch did not help :( behavior is still the same > > > > > > Regards, > > sriram > > > > > > > > > > > > > > > > > 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 > > > > > -- > 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 > > -- 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
