From: joe j. <joe...@qi...> - 2011-02-28 18:24:28
|
Ever since I began working with the Overo Water COM, I have noticed some anomalies when configured for an NFS mount. My setup consists of booting the MLO, Uboot, and kernel from the microSD card and then mounting the rootfs from a host (NFS). This setup works pretty good about 90% of the time, however once in a while (other 10%), the Overo seems to get into this unknown state that prevents it from booting to completion, it gets stuck somewhere in the middle of the boot sequence and the last thing that it prints is something like the following: Cannot open /dev/ttyS1 or something about NFS server not being found. It also reveals itself by not allowing me to run known-good apps after bootup, during run-time (i.e. does not allow me to open my driver mods that I just inserted). I suspect it is an Overo state issue because as I soon as I switch out the Gumstix for a different one, using same SD card, it works again. Then, if I wait long enough, the non-working card starts working again after a few minutes of sitting on my desk. The amount of time that it has to be sitting is still undetermined as I have tried swapping back too soon and the non-working Gumstix continues to fail. Furthermore, this unknown problematic state seems to only affect my NFS configuration. I've tried changing the configuration to mount the rootfs from the SD card and it works, no problem. But as soon as I switch back to NFS my issues start again. Does anyone know of a technique for how to reset the state to a default? Again, the only technique I've found successful so far, is to let the Gumstix HW sit unplugged for a while for (~30 mins) before it NFS starts working. This technique is kind of sloppy an slow. -- View this message in context: http://old.nabble.com/Overo-Water-COM---Problematic-state-for-NFS-tp31032877p31032877.html Sent from the Gumstix mailing list archive at Nabble.com. |
From: Chris W. <whi...@gm...> - 2011-03-01 17:07:11
|
Just guessing here, but could this be a MAC address issue? Are you using the same IP and/or MAC on two different COMs? -chris On Mon, Feb 28, 2011 at 12:24 PM, joe joe <joe...@qi...> wrote: > > > Ever since I began working with the Overo Water COM, I have noticed some > anomalies when configured for an NFS mount. My setup consists of booting > the MLO, Uboot, and kernel from the microSD card and then mounting the > rootfs from a host (NFS). This setup works pretty good about 90% of the > time, however once in a while (other 10%), the Overo seems to get into this > unknown state that prevents it from booting to completion, it gets stuck > somewhere in the middle of the boot sequence and the last thing that it > prints is something like the following: Cannot open /dev/ttyS1 or something > about NFS server not being found. It also reveals itself by not allowing me > to run known-good apps after bootup, during run-time (i.e. does not allow me > to open my driver mods that I just inserted). > > I suspect it is an Overo state issue because as I soon as I switch out the > Gumstix for a different one, using same SD card, it works again. Then, if I > wait long enough, the non-working card starts working again after a few > minutes of sitting on my desk. The amount of time that it has to be sitting > is still undetermined as I have tried swapping back too soon and the > non-working Gumstix continues to fail. > > Furthermore, this unknown problematic state seems to only affect my NFS > configuration. I've tried changing the configuration to mount the rootfs > from the SD card and it works, no problem. But as soon as I switch back to > NFS my issues start again. > > Does anyone know of a technique for how to reset the state to a default? > Again, the only technique I've found successful so far, is to let the > Gumstix HW sit unplugged for a while for (~30 mins) before it NFS starts > working. This technique is kind of sloppy an slow. > > -- > View this message in context: http://old.nabble.com/Overo-Water-COM---Problematic-state-for-NFS-tp31032877p31032877.html > Sent from the Gumstix mailing list archive at Nabble.com. > > > ------------------------------------------------------------------------------ > Free Software Download: Index, Search & Analyze Logs and other IT data in > Real-Time with Splunk. Collect, index and harness all the fast moving IT data > generated by your applications, servers and devices whether physical, virtual > or in the cloud. Deliver compliance at lower cost and gain new business > insights. http://p.sf.net/sfu/splunk-dev2dev > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > |
From: joe j. <joe...@qi...> - 2011-03-02 13:24:41
|
I'm only using a single Gumstix COM when this happens. I go from doing a lot of consecutive good boots/runs to all of a sudden having issues as I described previously. Chris Whittenburg wrote: > > Just guessing here, but could this be a MAC address issue? Are you > using the same IP and/or MAC on two different COMs? > > -chris > > > On Mon, Feb 28, 2011 at 12:24 PM, joe joe <joe...@qi...> > wrote: >> >> >> Ever since I began working with the Overo Water COM, I have noticed some >> anomalies when configured for an NFS mount. My setup consists of booting >> the MLO, Uboot, and kernel from the microSD card and then mounting the >> rootfs from a host (NFS). This setup works pretty good about 90% of the >> time, however once in a while (other 10%), the Overo seems to get into >> this >> unknown state that prevents it from booting to completion, it gets stuck >> somewhere in the middle of the boot sequence and the last thing that it >> prints is something like the following: Cannot open /dev/ttyS1 or >> something >> about NFS server not being found. It also reveals itself by not allowing >> me >> to run known-good apps after bootup, during run-time (i.e. does not allow >> me >> to open my driver mods that I just inserted). >> >> I suspect it is an Overo state issue because as I soon as I switch out >> the >> Gumstix for a different one, using same SD card, it works again. Then, if >> I >> wait long enough, the non-working card starts working again after a few >> minutes of sitting on my desk. The amount of time that it has to be >> sitting >> is still undetermined as I have tried swapping back too soon and the >> non-working Gumstix continues to fail. >> >> Furthermore, this unknown problematic state seems to only affect my NFS >> configuration. I've tried changing the configuration to mount the rootfs >> from the SD card and it works, no problem. But as soon as I switch back >> to >> NFS my issues start again. >> >> Does anyone know of a technique for how to reset the state to a default? >> Again, the only technique I've found successful so far, is to let the >> Gumstix HW sit unplugged for a while for (~30 mins) before it NFS starts >> working. This technique is kind of sloppy an slow. >> >> -- >> View this message in context: >> http://old.nabble.com/Overo-Water-COM---Problematic-state-for-NFS-tp31032877p31032877.html >> Sent from the Gumstix mailing list archive at Nabble.com. >> >> >> ------------------------------------------------------------------------------ >> Free Software Download: Index, Search & Analyze Logs and other IT data in >> Real-Time with Splunk. Collect, index and harness all the fast moving IT >> data >> generated by your applications, servers and devices whether physical, >> virtual >> or in the cloud. Deliver compliance at lower cost and gain new business >> insights. http://p.sf.net/sfu/splunk-dev2dev >> _______________________________________________ >> gumstix-users mailing list >> gum...@li... >> https://lists.sourceforge.net/lists/listinfo/gumstix-users >> > > ------------------------------------------------------------------------------ > Free Software Download: Index, Search & Analyze Logs and other IT data in > Real-Time with Splunk. Collect, index and harness all the fast moving IT > data > generated by your applications, servers and devices whether physical, > virtual > or in the cloud. Deliver compliance at lower cost and gain new business > insights. http://p.sf.net/sfu/splunk-dev2dev > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > > -- View this message in context: http://old.nabble.com/Overo-Water-COM---Problematic-state-for-NFS-tp31032877p31049254.html Sent from the Gumstix mailing list archive at Nabble.com. |
From: Bob C. <bco...@ve...> - 2011-03-02 01:32:16
|
Joe Joe, What expansion board are you using? The next time this happens can you post the exact error message you see? Do you have a second expansion board that you can test the Overo water on? Suppose you have two expansion boards and the Overo still shows this behavior of getting "stuck". Does the problem go away if you use a fan to cool the expansion board and Overo? Is the NFS resource you are mounting actually an networked external hard drive enclosure? I wonder if the NFS resource itself is being kept nice and cool? Can you post a picture somewhere of your Overo, with all devices connected, when this happens? Thanks Bob Cochran On 02/28/2011 01:24 PM, joe joe wrote: > > Ever since I began working with the Overo Water COM, I have noticed some > anomalies when configured for an NFS mount. My setup consists of booting > the MLO, Uboot, and kernel from the microSD card and then mounting the > rootfs from a host (NFS). This setup works pretty good about 90% of the > time, however once in a while (other 10%), the Overo seems to get into this > unknown state that prevents it from booting to completion, it gets stuck > somewhere in the middle of the boot sequence and the last thing that it > prints is something like the following: Cannot open /dev/ttyS1 or something > about NFS server not being found. It also reveals itself by not allowing me > to run known-good apps after bootup, during run-time (i.e. does not allow me > to open my driver mods that I just inserted). > > I suspect it is an Overo state issue because as I soon as I switch out the > Gumstix for a different one, using same SD card, it works again. Then, if I > wait long enough, the non-working card starts working again after a few > minutes of sitting on my desk. The amount of time that it has to be sitting > is still undetermined as I have tried swapping back too soon and the > non-working Gumstix continues to fail. > > Furthermore, this unknown problematic state seems to only affect my NFS > configuration. I've tried changing the configuration to mount the rootfs > from the SD card and it works, no problem. But as soon as I switch back to > NFS my issues start again. > > Does anyone know of a technique for how to reset the state to a default? > Again, the only technique I've found successful so far, is to let the > Gumstix HW sit unplugged for a while for (~30 mins) before it NFS starts > working. This technique is kind of sloppy an slow. > |