When I have some spare time, I will start experimenting with the configs. I see this behavior on multiple boards, but have not been able to find a systematic difference.
Thanks again for the help,
Kristian
-Kristian
-- To join: http://beagleboard.org/discuss
To unsubscribe from this group, send email to:
beagleboard...@googlegroups.com
Frequently asked questions: http://beagleboard.org/faq
-- Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Senior Staff Specialist, Cricket Coach Microsoft Windows Free Zone - Linux used for all Computing Tasks
Images to test..
http://rcn-ee.homeip.net:81/testing/beaglebone/3.2-cpufreq-more/
I tried this /3.2-cpufreq-more/ version and have the same crash but now I am looking at the backtrace it is different to yours at the top but still ends up stalling when it 's attempting to schedule io. Mine seems to be locking up scheduling tty io which I assume is eventually going into the USB serial device.
Does anyone know if the wait for completion and schedule encapsulates some sort of interrupt setup and callback? Interrupts not working maybe?
On Friday, 18 May 2012 14:22:01 UTC+10, RobertCNelson wrote:
On Thu, May 17, 2012 at 5:30 PM, Robert Nelson wrote: