• Registered: 2007-11-09
  • Posts: 340

Topic: Problems with new Beta Firmware

I've noticed a few issues with the new beta firmware; these are not major issues and fall well within the definition of "beta":

* Manually changing widgets sometimes takes a while, and sometimes causes the control panel to reinitialize.
   I've noticed this with Chumbyland, a large widget.  If I either manually move to a new widget, use the tilt w/ button method, or change channels, the widget will take a long time to switch.  The control panel / tilt functionality work speedily; it's just the dismissing of the existing widget takes a long time or causes the control panel to reboot.

* As widgets rotate, sometimes parts of the screen flickers or wavers at the point of rotating away.  This I've seen with a number of widgets and on two separate Chumbys.

These were not an issue with the previous beta, and only occurred after the new beta.  Please let me know if there is anything I can help with.

wayn3w

2 Reply by servalan (edited by servalan 2009-05-06 14:02:40)

  • From: Australia
  • Registered: 2008-11-12
  • Posts: 104

Re: Problems with new Beta Firmware

I'm seeing these issues with 1.7 release - with the release control panel, particularly the reinitialise after manually changing widgets. Is there a way to go back to the 1.6 software & turn updates off - the 1.7 update has rendered my chumby pretty much inoperable.

I'd guess the issues above aren't related to the beta control panel - but with the 1.7 firmware.

  • From: San Diego
  • Registered: 2007-10-25
  • Posts: 205

Re: Problems with new Beta Firmware

wayn3w,

Problem 1.  We have not been able to replicate this issue.  What are the 2 widgets before and after chumbyland?
What HW version is your chumby?
What is your chumbys link quality shown in the control panel?

Problem 2. We have been able to replicate this and are looking into it.

Chumbymatt's Website

4 Reply by cbreeze (edited by cbreeze 2009-05-06 16:50:31)

  • From: Tulsa, OK
  • Registered: 2008-08-04
  • Posts: 657

Re: Problems with new Beta Firmware

Hi,

If it helps, Chumbyland was last updated a couple days before the 1.7 update.  I am sure nothing new has been introduced on my end (and in almost all cases I can track back to issues I have created smile ).

Many reports of this problem are coming in via the Chumbyland boards, as well as "in-widget".  I have been able to verify the issue as well.

If there is anything I can do to assist in any type of troubleshooting, please let me know.

Cheers.

Get -> Chumbyland | Joice | Word Up | Newsdom

cbreeze's Website

  • Registered: 2008-10-30
  • Posts: 7

Re: Problems with new Beta Firmware

Hi!  I've had my chumby for almost a year, and this is the first problem I've ever had with it.  I too have had many problems over the last day, ever since loading 1.7.  Most of the issues arise during my use of chumbyland.  In the past, the widget has frozen occasionally, which I would fix by reloading the channel.  Now the widget is freezing and I can't even pull up the control panel to reload.  Also, I don't know what the switch on top of the chumby is called, but when the chumby freezes like this, the unit now doesn't respond to my clicking it, so the only way to work around this is to remove the unit from the A/C power source.  Yesterday rebooting by removing it from the power would work, but today (Tuesday night US EDT), my chumby is totally rebooting BY ITSELF, with no instigation by me.  This is ridiculous.  I can't work around it and it's ruining my chumby experience.  Is there some way to revert to 1.6?  I had no troubles even remotely similar to this prior to this update.  Help!

  • From: Australia
  • Registered: 2008-11-12
  • Posts: 104

Re: Problems with new Beta Firmware

Chumbymatt wrote:

Problem 1.  We have not been able to replicate this issue.  What are the 2 widgets before and after chumbyland?

5 widgets in channel. Radio Paradise Now Playing, Chumbyland Sights, Chumbyland, All in One Clock, Chumbyland

Internode stream of Radio Paradise playing.

I can reproduce the problem quite easily, after Chumbyland loads a few times, the top button stops responding & after a few minutes the chumby re-initialises dropping out the radio stream & all the widgets.

Chumbymatt wrote:

What HW version is your chumby?

HW: 3.7 SW: 1.7.0 FW: 1649

Chumbymatt wrote:

What is your chumbys link quality shown in the control panel?

95

  • Registered: 2007-11-09
  • Posts: 340

Re: Problems with new Beta Firmware

Thank you for the prompt response!

Chumbymatt wrote:

Problem 1.  We have not been able to replicate this issue.  What are the 2 widgets before and after chumbyland?

Doom Server Monitor, Chumbland Sites
Chumbyland
Accelerator for Development, Now Playing

What HW version is your chumby?

3.7

What is your chumbys link quality shown in the control panel?

85

  • From: San Diego, CA
  • Registered: 2007-08-09
  • Posts: 112

Re: Problems with new Beta Firmware

Folks,
If you're trying to debug this issue, we'd like to make sure we get accurate log info on the problem at hand.  I recommend that you run an ssh session on your chumbys while monitoring the flash player restarts; and cut/paste the findings into the forum post along with the HW/SW/FW versions as well as the widgets in your channel (in order).

For info on how to run SSH, go here:  http://wiki.chumby.com/mediawiki/index. … trol_Panel




-Sam

sam m's Website

  • From: Australia
  • Registered: 2008-11-12
  • Posts: 104

Re: Problems with new Beta Firmware

Not sure what the best way to monitor the flash widget... I'm using top & copying & pasting the data, every time top updates... I see:

Mem: 55916K used, 6032K free, 0K shrd, 8004K buff, 15384K cached
Load average: 2.74 2.58 1.79
  PID USER     STATUS   RSS    VSZ  PPID %CPU %MEM COMMAND
2725 root     RW     23584  38772  2663 99.0 38.0 chumbyflashplay

2725 root     RW     23584  38772  2663 99.2 38.0 chumbyflashplay

2725 root     RW     23584  38772  2663 99.0 38.0 chumbyflashplay

while the chumby is in its frozen state.... i.e. the CPU is pegged, but memory is ok... it stays like the above for a minute or so & then another chumbyflashplay is forked:

Mem: 43352K used, 18596K free, 0K shrd, 8004K buff, 15520K cached
Load average: 2.56 2.62 1.89
  PID USER     STATUS   RSS    VSZ  PPID %CPU %MEM COMMAND
3070 root     SW     10576  30496  3008 14.0 17.0 chumbyflashplay

until a few minutes later when the process happens again & the chumby freezes, CPU usage spikes from about 55-60% to 99.N%

There are no other processes doing much at all... I guess with the flashplayer chomping 99% of the CPU they won't be able to.... I've given up listening to a radio stream - so that's not a factor in this problem...

This is the top output while the chumby is in frozen state:
3070 root     RW     23948  39088  3008 99.2 38.5 chumbyflashplay
2957 root     RW       860   4504  2498  0.3  1.3 top
1742 root     DW         0      0     1  0.1  0.0 rt73
2494 root     SW      1912   5960  2171  0.0  3.0 sshd
3069 root     SW      1284   5180  3008  0.0  2.0 btplayd
2242 root     SW      1268  21024     1  0.0  2.0 chumbhowld
2139 root     SW      1228  11496     1  0.0  1.9 mDNSResponder
3072 root     SW       924   3212  3071  0.0  1.4 chumbpipe
2171 root     SW       892   3276     1  0.0  1.4 sshd
2498 root     SW       892   4504  2494  0.0  1.4 sh
2257 root     SW       840   4500     1  0.0  1.3 crond
1034 root     SW       776   3528     1  0.0  1.2 mountmon
2164 root     SW       680   2916     1  0.0  1.0 mDNSPublish
1426 root     SWN      564   1560     1  0.0  0.9 headphone_mgr
  995 root     SW<      500   1600     1  0.0  0.8 udevd
2267 root     SW<      432   3480     1  0.0  0.6 chumbalarmd
3008 root     SW       396   1820     1  0.0  0.6 start_control_p
    1 root     SW       344   1816     0  0.0  0.5 init
  988 root     SW       340   2016     1  0.0  0.5 syslogd

& shortly after the flashplayer has reinitialised:
Mem: 43328K used, 18620K free, 0K shrd, 8004K buff, 15524K cached
Load average: 2.67 2.64 2.19
  PID USER     STATUS   RSS    VSZ  PPID %CPU %MEM COMMAND
3439 root     SW     10564  30496  3377 13.4 17.0 chumbyflashplay
2957 root     RW       860   4504  2498  0.5  1.3 top
2494 root     SW      1912   5960  2171  0.0  3.0 sshd
3443 root     SW      1544   7568     1  0.0  2.4 chumbyflashplay
3438 root     SW      1284   5180  3377  0.0  2.0 btplayd
2242 root     SW      1268  21024     1  0.0  2.0 chumbhowld
2139 root     SW      1228  11496     1  0.0  1.9 mDNSResponder
3441 root     SW       924   3212  3440  0.0  1.4 chumbpipe
2171 root     SW       892   3276     1  0.0  1.4 sshd
2498 root     SW       892   4504  2494  0.0  1.4 sh
2257 root     SW       840   4500     1  0.0  1.3 crond
1034 root     SW       776   3528     1  0.0  1.2 mountmon
2164 root     SW       680   2916     1  0.0  1.0 mDNSPublish
1426 root     SWN      564   1560     1  0.0  0.9 headphone_mgr
  995 root     SW<      500   1600     1  0.0  0.8 udevd
2267 root     SW<      432   3480     1  0.0  0.6 chumbalarmd
3377 root     SW       396   1820     1  0.0  0.6 start_control_p
    1 root     SW       344   1816     0  0.0  0.5 init
  988 root     SW       344   2016     1  0.0  0.5 syslogd
3440 root     SW       304   1816  3439  0.0  0.4 sh
2270 root     SW       124   1816     1  0.0  0.1 init
2199 root     SW       104   1816     1  0.0  0.1 httpd
  679 root     SW         0      0     1  0.0  0.0 mtdblockd

If you need more info or have a better way of monitoring the flashplayer, please let me know. & is there any way of going back to a working release of the firmware? I appreciate the need to debug - but I'd just like a working chumby back...

Thanks!

  • Duane
  • Duane
  • Blue Octy
  • Offline
  • From: San Diego, CA
  • Registered: 2006-08-24
  • Posts: 8,211

Re: Problems with new Beta Firmware

Yeah, what you do is:

stop_control_panel; chumbyflashplayer.x -i /tmp/controlpanel.swf

You'll get a pretty verbose log of stuff.  If the player crashes, it should end up at a prompt instead of restarting - the last hundred or so lines before the halt is what we'd like to see.

Duane's Website

  • From: Australia
  • Registered: 2008-11-12
  • Posts: 104

Re: Problems with new Beta Firmware

5 widgets in channel. Radio Paradise Now Playing, Chumbyland Sights, Chumbyland, All in One Clock, Chumbyland
HW: 3.7 SW: 1.7.0 FW: 1649
Wireless signal strength: 93

Straight crash:

2009-05-08 10:08:48 NetStreamRequest::Open(172): Opening protocol 'http://' host 'chumby.develephant.com' port 80 location '/chumbyland/games_api.php'
2009-05-08 10:08:48 NetStreamRequest::Open(172) opened http object id 193
2009-05-08 10:08:48 NetStreamRequest::Step(171) done, closing stream (3770 of 3770 bytes, avail=0) status=0 (ok)
2009-05-08 10:08:48 SI_Object::SI_GetImageInfo(40b0760c,1916712488,{725499a8,3770})
2009-05-08 10:08:48 ImagePNGObject::Open() w=20 h=32 channels=1 bitdepth=8 ctype=3 (pal) interlace=0 comp=0 filt=0
2009-05-08 10:08:48 ImagePNGObject::Open() got 256 palette entries
2009-05-08 10:08:48 ImagePNGObject::Open() - channel count changed from 1 to 4
2009-05-08 10:08:48 allocating 80 bytes per row
2009-05-08 10:08:48 ImagePNGObject::SendFlashData() imageid=1916712488 requested format ARGB8888 80 bytes/scanline buff=723009f4
2009-05-08 10:08:48 Displaying rows from 0 to 31 inclusive palette count=256 (scaled size = 20X32)
2009-05-08 10:08:50 NetStreamRequest::ProcessHeaders(172) content-type: text/html
2009-05-08 10:08:51 TRACE: (Advance timer heartbeat)
2009-05-08 10:08:52 NetStreamRequest::Step(172) done, closing stream (105667 of 0 bytes, avail=0) status=200 (ok)
2009-05-08 10:08:55 ClientObject::DoUpdate(id=9 master=n): got FI_ActionScriptInterruptedByTimeout {1x}
2009-05-08 10:08:57 MemoryObject::Alloc(0x40b0760c) rejected request for 1 blocks (32K) - 12288K/12288K already in use
2009-05-08 10:08:57 SI_NotifyError(0x40b0760c): Error 1 (FI_OutOfMemoryError)
2009-05-08 10:08:57 SI_NotifyError: terminating slave instance 9
2009-05-08 10:08:57 ClientObject::ProcessSoftEvents() - 1 events processed
2009-05-08 10:08:57 ClientObject::DoUpdate(id=9 master n): got FI_ActionScriptInterruptedByTimeoutWithError
2009-05-08 10:08:57 ClientObject::MainLoop() - deleting instance 002782c0 (deferred delete)
2009-05-08 10:08:57 ClientObject::~ClientObject(this=0x002782c0) mmobj=0x40b0760c
2009-05-08 10:08:57 StreamSoundObject::~StreamSoundObject(this=0x72c0005c, mmobj=0x40b0760c) complete 0 played 0
2009-05-08 10:08:57 SoundObject::~SoundObject[c](this=0x72c0005c)
2009-05-08 10:08:57 SoundObject::Remove(0x72c0005c) making 0x70c0005c new head of list
2009-05-08 10:10:02 Start time: 2009-05-08 10:06:04
2009-05-08 10:10:02 End time  : 2009-05-08 10:10:02
2009-05-08 10:10:02 Elapsed   : 3m 58s (238)
2009-05-08 10:10:02 chumbySignalHandler(15) SIGTERM - requested termination
Killed

Freeze for a few minutes & start again...

2009-05-08 10:24:27 NetStreamRequest::Open(137): Opening protocol 'http://' host 'chumby.develephant.com' port 80 location '/chumbyland/chum_api.php'
2009-05-08 10:24:27 NetStreamRequest::Open(137) opened http object id 250
2009-05-08 10:24:28 NetStreamRequest::ProcessHeaders(136) content-type: text/html
2009-05-08 10:24:28 ClientObject::HeartBeat(1194512) elapsed 15.060s prev high 196.132s
2009-05-08 10:24:28 NetStreamRequest::Step(136) done, closing stream (507 of 507 bytes, avail=0) status=200 (ok)
2009-05-08 10:24:28 TRACE: (Master heartbeat)
2009-05-08 10:24:29 NetStreamRequest::ProcessHeaders(137) content-type: text/html
2009-05-08 10:24:30 TRACE: (Bend sensor heartbeat)
2009-05-08 10:24:30 TRACE: (Advance timer heartbeat)
2009-05-08 10:24:30 NetStreamRequest::Step(137) done, closing stream (25388 of 0 bytes, avail=0) status=200 (ok)
2009-05-08 10:24:31 MemoryObject::Alloc(0x352214) rejected request for 1 blocks (32K) - 12288K/12288K already in use
2009-05-08 10:24:31 SI_NotifyError(0x352214): Error 1 (FI_OutOfMemoryError)
2009-05-08 10:24:31 SI_NotifyError: terminating slave instance 29
2009-05-08 10:24:31 ClientObject::ProcessSoftEvents() - 1 events processed
2009-05-08 10:24:31 ClientObject::DoUpdate(id=29 master n): got FI_ActionScriptInterruptedByTimeoutWithError
2009-05-08 10:24:31 ClientObject::MainLoop() - deleting instance 0027b700 (deferred delete)
2009-05-08 10:24:31 ClientObject::~ClientObject(this=0x0027b700) mmobj=0x00352214
2009-05-08 10:24:31 StreamSoundObject::~StreamSoundObject(this=0x77c0005c, mmobj=0x00352214) complete 0 played 0
2009-05-08 10:24:31 SoundObject::~SoundObject[h](this=0x77c0005c)
2009-05-08 10:24:31 SoundObject::Remove(0x77c0005c) making 0x70c0005c new head of list
2009-05-08 10:27:33 ClientObject::~ClientObject() player has been destroyed, MM_Object 00352214
2009-05-08 10:27:33 SoundObject::GlobalCleanup(drainPCM=n)
2009-05-08 10:27:33 ClientObject::<dtor>() cancelled 0 sockets belonging to 0x00352214
2009-05-08 10:27:33 DisplayObject::<dtor>(this=77c00024) flashbuff=002a7400 framebuff=00279ac8
2009-05-08 10:27:33 FrameBuffer::ReleaseFrameBuffer() final instance freed
2009-05-08 10:27:33 CO::~stream (mmobj=00352214) m_stream=77c000f0
2009-05-08 10:27:33 CO::~download
2009-05-08 10:27:33 KeyboardObject::<dtor>(this=0x77c0012c mmobj=0x00352214) new g_globalInstance = 0x70c0012c
2009-05-08 10:27:33 ChumbyMem::UnlinkPrivate(001e31b8) new head is 0026f948
2009-05-08 10:27:33 ClientObject::MainLoop() - restarting with client 001ecfc8 (master)
2009-05-08 10:27:33 ClientObject::MainLoop() - continuing with instance 00000000 (deleted) master 001ecfc8
2009-05-08 10:27:33 TRACE: WidgetPlayer.advanceTimerHandler(): widget died with error -5 (terminated)
2009-05-08 10:27:33 ClientObject::SetSlaveVariable(_chumby_timer_expires): no slave instance found
2009-05-08 10:27:33 Could not set slave var _chumby_timer_expires to -1
2009-05-08 10:27:33 TRACE: WidgetPlayer.nextWidget(): loading next widget instance
2009-05-08 10:27:33 ClientObject::SetSlaveVariable(_chumby_timer_expires): no slave instance found
2009-05-08 10:27:33 Could not set slave var _chumby_timer_expires to -1
2009-05-08 10:27:33 TRACE: WidgetPlayer.changeProfileEasterEgg(): Checking for profile easter egg
2009-05-08 10:27:33 TRACE:  - not found
2009-05-08 10:27:33 TRACE: WidgetPlayer.fetchWidgetInstanceXML(): processing widget instance
2009-05-08 10:27:33 TRACE: - clearing advance timer handler
2009-05-08 10:27:33 TRACE: WidgetPlayer.playWidget(): playing widget instance (current play mode "playing")
2009-05-08 10:27:33 TRACE: WidgetPlayer.loadWidgetIntoProxy(): loading widget instance into player
2009-05-08 10:27:33 TRACE: - loading widget movie "All In One Clock" from http://movies.chumby.com/xmlmovie/3501D272-EED4-11DD-93FA-001E681DFAC2
2009-05-08 10:27:33 kStopSlave: no slave running or slave mismatch for instance id -1
2009-05-08 10:27:33 ASnative(5,72) 0x4058360c setting cdsce=0
2009-05-08 10:27:33 ClientObject::StartSlaveCommon() starting slave 'http://movies.chumby.com/xmlmovie/3501D272-EED4-11DD-93FA-001E681DFAC2'
2009-05-08 10:27:33 ClientObject::StartSlaveCommon() created new settings instance 0x002a4dd8 to be freed when slave dies
2009-05-08 10:27:33 MemoryStateMonitor::Check() - MemFree=17776kb, Cached=15380kb, Buffers=8004kb, total=41160kb - above danger zone by 28872kb
2009-05-08 10:27:33 ClientObject::ClientObject(this=0x00279630) asynch load = Y
2009-05-08 10:27:33 ClientObject(33) mmobj=0x002a5cb4, PlatformPlayer=0x002ae8a0
2009-05-08 10:27:33 ChumbyMem::ctor() using heap memory 0x78c00000 size 4096kB
2009-05-08 10:27:33 ChumbyMem::LinkPrivate(mgr=002a4e70) previous head is 0026f948
2009-05-08 10:27:33 DisplayObject::<ctor>(this=78c00024) UDMA is disabled, falling back to /dev/fb[#]
2009-05-08 10:27:33 FrameBuffer::<constructor>(0,320X240) 640 bytes per line, 153600 == buffer size
2009-05-08 10:27:33 FrameBuffer::AssureFrameBuffer() file for /dev/fb0 is 0x278f00 (fileno 7)
2009-05-08 10:27:33 FrameBuffer::AssureFrameBuffer() m_frame_buffer=0x40553000
2009-05-08 10:27:33 FrameBuffer::GetFrameBuffer(0, 320X240) - creating new FrameBuffer instance 1e3b08
2009-05-08 10:27:33 DisplayObject::<ctor>(this=78c00024) got fb=001e3b08 for 320X240 idx=0 153600 bytes
2009-05-08 10:27:33 SoundObject::SoundObject[i](0x78c0005c mmobj=0x002a5cb4): initializing audio, buffers=16, bpb=2048
2009-05-08 10:27:33 SoundObject::Add[i](this=0x78c0005c, mmobj=0x002a5cb4)
2009-05-08 10:27:33 StreamSoundObject::StreamSoundObject(this=0x78c0005c, mmobj=0x002a5cb4==0x002a5cb4): setting up audio
2009-05-08 10:27:33 KeyboardObject::<ctor>(this=0x78c0012c mmobj=0x002a5cb4) next=0x70c0012c
2009-05-08 10:27:33 ClientObject::Initialize() - successfully set vector font data for 24991 bytes
2009-05-08 10:27:33 ClientObject::LoadSwfToMemFromURL(http://movies.chumby.com/xmlmovie/3501D272-EED4-11DD-93FA-001E681DFAC2) - instantiating http object, async=Y, timeout = 60 sec
2009-05-08 10:27:33 DisplayObject::SwitchActiveDisplay(1) - no change, forcing redraw, asserting active display
2009-05-08 10:27:33 DisplayObject::SwitchActiveDisplay(0) - no change, forcing redraw
2009-05-08 10:27:33 kStartSlave: Object origin=(null), length = 0, interface count = 0, first=0x70413198
2009-05-08 10:27:33 TRACE: - using widget instance timing:
2009-05-08 10:27:33 TRACE:  - timeout, 300000 ms
2009-05-08 10:27:33 TRACE: - running the widget for 300 seconds
2009-05-08 10:27:33 TRACE: - expires at Fri May 8 10:32:33 GMT+1000 2009
2009-05-08 10:27:33 TRACE: Setting advance timer handler
2009-05-08 10:27:33 TRACE: (Master heartbeat)

Let me know if you need more info & if someone would please answer the question about going back to the 1.6 software... I may be the only one posting, but there are many people keen to have a working chumby back - thanks!

  • Duane
  • Duane
  • Blue Octy
  • Offline
  • From: San Diego, CA
  • Registered: 2006-08-24
  • Posts: 8,211

Re: Problems with new Beta Firmware

Thanks for the log - it seems to indicate soem sort of memory leak issue.  This gives us some pointers on where to look.

servalan wrote:

if someone would please answer the question about going back to the 1.6 software... I may be the only one posting, but there are many people keen to have a working chumby back - thanks!

Go to this page and scroll to "updating with a usb flash drive".

The device will bug you every hour or so about updating - I believe that creating a "hosts" file and redirecting "update.chumby.com" to "127.0.0.1" should stop those messages.

Duane's Website

13 Reply by servalan (edited by servalan 2009-05-11 20:29:15)

  • From: Australia
  • Registered: 2008-11-12
  • Posts: 104

Re: Problems with new Beta Firmware

Duane wrote:

The device will bug you every hour or so about updating - I believe that creating a "hosts" file and redirecting "update.chumby.com" to "127.0.0.1" should stop those messages.

Thanks... a bit of a pain as you have to reenter a wireless key... but happily back running 1.6 here - thanks again!

Edit: If you wish to stop the update nags after reverting to 1.6, this is what I did - there may be easier ways - this works for me - no implied warranty....:

0. Make sure a USB key is installed on the chumby & is mounted as /usb/mnt - I am assuming one was used to revert to 1.6

1. Get SSH up & running on your chumby & login

2. Create a directory to hold a custom /etc directory:
# mkdir /psp/etc

3. Copy the contents of /etc to the new custom directory:
# cp -rd /etc/* /psp/etc

4. On the USB key create a custom hosts file:
# cp /etc/hosts /mnt/usb/hosts
# echo "127.0.0.1 update.chumby.com" >> /mnt/usb/hosts

5. Check the new hosts file has the extra line to redirect update.chumby.com to the localhost. i.e. knobble the lookup for the update host:
# cat /mnt/usb/hosts
127.0.0.1 localhost.localdomain localhost
127.0.0.1 update.chumby.com

6. Create a debugchumby file on the USB key which will run when the chumby is turned on & execute the commands listed - first mount the custom writeable /psp/etc directory as the /etc filesystem, then copy in the custom hosts file (don't copy & paste the > characters - they're prompts for multi-line echo commands):
# echo "#!/bin/sh
> mount -t loop -o bind /psp/etc /etc
> cp /mnt/usb/hosts /etc/hosts" > /mnt/usb/debugchumby

7. Check the debugchumby script looks ok
# cat /mnt/usb/debugchumby
#!/bin/sh
mount -t loop -o bind /psp/etc /etc
cp /mnt/usb/hosts /etc/hosts

8. Reboot the chumby, the update nag should be gone.

9. To back out the changes, power off the chumby, remove the USB key from the chumby & power on the chumby again.

  • Registered: 2007-11-09
  • Posts: 340

Re: Problems with new Beta Firmware

Duane, et al,

Do you have all the debugging information you need or should I also scrape the control panel logs as well?

wayn3w

  • Duane
  • Duane
  • Blue Octy
  • Offline
  • From: San Diego, CA
  • Registered: 2006-08-24
  • Posts: 8,211

Re: Problems with new Beta Firmware

I think we're good for now.  Thanks!

Duane's Website

  • From: Australia
  • Registered: 2009-04-14
  • Posts: 118

Re: Problems with new Beta Firmware

Interesting - I have no problems with the new version. I'm in Australia with Internde and have had no dropouts with streaming radio - I have 24 widgets in my channel.

  • Registered: 2007-11-21
  • Posts: 24

Re: Problems with new Beta Firmware

I am having the same problem with Chumbyland. It is pretty much useless on the Chumby because it keeps resetting. I think i will try and revert back to 1.6 until this is cleared up.

thanks
John

  • Registered: 2007-11-09
  • Posts: 340

Re: Problems with new Beta Firmware

I also had the same problem with Sky Happenings after it's been running for a while: attempting to manually switch to another widget would pause for a long time before actually switching.

wayn3w

  • From: Michigan
  • Registered: 2008-04-21
  • Posts: 43

Re: Problems with new Beta Firmware

I think I've cleared up the interval leak in Sky Happenings. Wayn3w, let me know if you still have any problems

  • From: San Diego, CA
  • Registered: 2007-01-29
  • Posts: 9

Re: Problems with new Beta Firmware

I've been trying unsuccessfully to reproduce this using the 1.7 firmware. Are you playing any streaming audio while this is going on?
The log snippet below looks like Chumbyland ran out of memory (I haven't been able to get that to happen) then control panel stopped responding and was killed by the watchdog script (which sent the SIGTERM).

I think that making this problem happen may require the right timing, i.e. when Chumbyland is really busy. Any observations about how long you were in the Chumbyland widget before the crash and if anything unusual was happening just before Chumbyland got terminated would help.

Thanks!

servalan wrote:

5 widgets in channel. Radio Paradise Now Playing, Chumbyland Sights, Chumbyland, All in One Clock, Chumbyland
HW: 3.7 SW: 1.7.0 FW: 1649
Wireless signal strength: 93

Straight crash:

2009-05-08 10:08:48 NetStreamRequest::Open(172): Opening protocol 'http://' host 'chumby.develephant.com' port 80 location '/chumbyland/games_api.php'
...
2009-05-08 10:08:57 SI_NotifyError(0x40b0760c): Error 1 (FI_OutOfMemoryError)
2009-05-08 10:08:57 SI_NotifyError: terminating slave instance 9
2009-05-08 10:08:57 ClientObject::ProcessSoftEvents() - 1 events processed
2009-05-08 10:08:57 ClientObject::DoUpdate(id=9 master n): got FI_ActionScriptInterruptedByTimeoutWithError
2009-05-08 10:08:57 ClientObject::MainLoop() - deleting instance 002782c0 (deferred delete)
2009-05-08 10:08:57 ClientObject::~ClientObject(this=0x002782c0) mmobj=0x40b0760c
2009-05-08 10:08:57 StreamSoundObject::~StreamSoundObject(this=0x72c0005c, mmobj=0x40b0760c) complete 0 played 0
2009-05-08 10:08:57 SoundObject::~SoundObject[c](this=0x72c0005c)
2009-05-08 10:08:57 SoundObject::Remove(0x72c0005c) making 0x70c0005c new head of list
2009-05-08 10:10:02 Start time: 2009-05-08 10:06:04
2009-05-08 10:10:02 End time  : 2009-05-08 10:10:02
2009-05-08 10:10:02 Elapsed   : 3m 58s (238)
2009-05-08 10:10:02 chumbySignalHandler(15) SIGTERM - requested termination
Killed

...
Let me know if you need more info & if someone would please answer the question about going back to the 1.6 software... I may be the only one posting, but there are many people keen to have a working chumby back - thanks!

hgroover's Website

  • Registered: 2007-11-09
  • Posts: 340

Re: Problems with new Beta Firmware

hgroover wrote:

I've been trying unsuccessfully to reproduce this using the 1.7 firmware. Are you playing any streaming audio while this is going on?
The log snippet below looks like Chumbyland ran out of memory (I haven't been able to get that to happen) then control panel stopped responding and was killed by the watchdog script (which sent the SIGTERM).

I get this problem after using Chumbyland for a short period of time, even as short as a minute, and I do not stream audio.  I have seen the watchdog script take effect when Chumbyland runs out of memory, but this is not this issue.  This problem occurs when a normally running game is manually switched away, either by using the tilt controls, the control panel navigational controls, or changing the channel.  The game is functioning fine until switching away.  Has something changed in the area of memory garbage collection?

People are finding the problem is alleviated when they roll back to 1.6.  And I have seen this problem with the SkyHappenings widget, too.

Tell you what -- when you are in the game trying to recreate the problem, create a 'classified' ad announcing who you are, and me and a few others (servlan, cbreeze) can assist with your recreation of the problem.  Just let us know here a rough time when you'll be playing the game.

wayn3w

  • From: Australia
  • Registered: 2008-11-12
  • Posts: 104

Re: Problems with new Beta Firmware

wayn3w wrote:

Tell you what -- when you are in the game trying to recreate the problem, create a 'classified' ad announcing who you are, and me and a few others (servlan, cbreeze) can assist with your recreation of the problem.  Just let us know here a rough time when you'll be playing the game.

Happy to help as wayn3w says.

I haven't had any problems since reverting back to 1.6 a few weeks ago.