On 1/19/2013 2:46 PM, Kent A. Reed wrote:
> On 1/19/2013 9:57 AM, Charles Steinkuehler wrote:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> I've setup Michael Haberler's network booting of my BeagleBone, and I
>> seem to be having the same network crashing on DHCP lease renewal
>> issue others have seen.
>>
>> Has anyone identified and resolved the issue, or just worked around it?
>>
>> It looks like Kent Reed had this problem, but has switched to using a
>> rootfs on the SD card. I didn't see an actual solution in the archives.
>>
>
> I'm sorry you fell in the same hole, Charles, but I'm relieved I'm not
> the only guy in it!
>
> I haven't finished gathering data (got distracted by the
> BeagleBoard-xM comments yesterday, including yours, and pulled mine
> out of a project to see if I can boot and run LinuxCNC as built by
> Michael).
>
> Anal-retentive tester that I am, so far I've tried various
> combinations of:
>
> 1) U-Boot IP provisioning: either setting the relevant environment
> variables explicitly or setting them via DHCP (U-Boot command dhcp
> with autoload=no)
>
> 2) kernel loading: either from the microSD card or via TFTP (U-Boot
> command tftp with autoload=no)
>
> 3) kernel IP provisioning: either setting the relevant boot parameters
> explicitly or setting them via DHCP (boot parameter: ip=dhcp)
>
> 4) rootfs mounting: either from the microSD card or via NFS
>
>
> So far, it seems that I can succeed with a number of
> combinations---many with rootfs mounted via NFS---but not with 1=dhcp,
> 2=ftfp, 3=dhcp, 4=nfs (e.g., the very combination that Michael
> described on his Wiki page) and I can cheat death with this last one
> by greatly increasing the lease time.
>
> I think this combination being an issue is a good clue but I haven't
> noodled through what it means.
>
> YMMV :-)
Gentle persons:
I neglected to include yet another variable. As Bas pointed out in the
other thread ("[Emc-developers] "new RTOS" status: Scheduler (?) lockup
on ARM") one can also load the kernel via NFS rather than TFTP. This
means my item 2 should have three options, namely, from microSD, via
TFTP, or via NFS.
A few minutes ago, I restarted my BeagleBone with 1=dhcp, 2=nfs, 3=dhcp,
4=nfs, and then started LinuxCNC with the same test as before, simulated
3-axis mill processing 3D_Chips.ngc.
Unlike the nearly identical configuration with 2=tftp, which reliably
locked up after a few minutes*, this configuration is still running 20
minutes later. I'll leave it running while I try to get some sleep.
Assuming it's still running when I get up, I'll rerun the original
configuration to confirm it's still failing...if it doesn't fail, then
I'm really going to start tearing my hair!
Regards.
Kent
*actually about 2.5 minutes which happens to be 1/2 of the
lease-expiration time I set in dhcpd.conf. Since I know that many dhcp
clients by default start looking for renewals on their leases at this
50-percent point, I'm suspicious that some related is causing my
lockups. And, no, Michael, I don't have your stale leases hanging around.
------------------------------------------------------------------------------
Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS,
MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current
with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft
MVPs and experts. ON SALE this month only -- learn more at:
http://p.sf.net/sfu/learnmore_123012
_______________________________________________
Emc-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/emc-developers
