Workaround for this bug: root@localhost:/proc# echo performance > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor root@localhost:/proc# echo performance > /sys/devices/system/cpu/cpu1/cpufreq/scaling_governor
The stacktrace shows that the bug is related to frequency scaling. Above commands will set the policy for frequency scaling to "performance", which will cause the PandaBoard to always run at the highest frequency and just not do any frequency scaling. This is clearly not a nice workaround, but it seems to be working just fine for me. My PandaBoard ES didn't crash in 3 days. Note: The above commands are probably not permanent, so you will have to execute them after every reboot. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1012735 Title: omap4 kernel oops To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-ti-omap4/+bug/1012735/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
