2013-08-24, 11:07
Testing further these traceback messages (post #406) and it's not the GPU "time" patch (or any other recent newlock3 patch) that is causing these messages as I see them even with a "stock" OE Gotham/master build (22 August, last commit 21d1ea08afed721cd48d87e5f51cfe28542f48a6) with no additional patches.
I've updated post #406 to add an additional vcgencmd loop as running multiple loops should make it easier to provoke the traceback messages. I'd expect them to appear in Rbej builds too.
Here's a pastebin extract of the traceback messages from "stock" Gotham, in case any information is different to that included in post #406.
Firmware details for this "stock" Gotham build:
Even running the above "vcgencmd version" command kicks out a traceback message...
I've updated post #406 to add an additional vcgencmd loop as running multiple loops should make it easier to provoke the traceback messages. I'd expect them to appear in Rbej builds too.
Here's a pastebin extract of the traceback messages from "stock" Gotham, in case any information is different to that included in post #406.
Firmware details for this "stock" Gotham build:
Code:
rpi512 # vcgencmd version && uname -a
Aug 7 2013 16:19:51
Copyright (c) 2012 Broadcom
version 7c7b17433e2a63025f6f42adcb2b8766eff55e12 (clean) (release)
Linux rpi512 3.10.9 #1 PREEMPT Thu Aug 22 18:18:18 BST 2013 armv6l GNU/LinuxEven running the above "vcgencmd version" command kicks out a traceback message...
