Submitted as a bug:
http://bugs.slimdevices.com/show_bug.cgi?id=16993
--
steve781
steve781's Profile: http://forums.slimdevices.com/member.php?userid=42824
View this thread: http://forums.slimdevices.com/showthread.php?t=
It just happened again. This time I just powered up a SB Radio and then
tried to play a stream directly on the Touch. Here's a snippet of the
log at the time of the hang. Any idea how I can get this in front of
the right person who can decode the entries? Is there enough here to
file a bug?
Feb 2
I'm still being plagued by this issue. It happened again last night when
I attempted to change from one favorite to another. The slimserver
process was running at 80% again, so it is definitely some kind of
hang. I need to determine if it is a hardware problem or a bug in the
latest Touch server.
It's not easy to repro. It usually takes a day or two of uptime before
the failure. Most of the time it happens when navigating the Internet
Radio lists, but it has also happened when moving between favorites. It
never happens when I go through the Touch UI, it always happens when
using the SB Rad
There seems to be another thread about this problem - the reboot seems
to be caused by the watchdog timer expiring which should be a safety
mechanism but it seems there is some sort of CPU loop with some city
lists.
See
http://forums.slimdevices.com/showthread.php?t=81207
There is a bug report f
Could be an excessive CPU use issue due to a bug, but it also could be a
memory problem. Possibly from the Touch trying to process too large of
a list. Do you only see that level of CPU usage after you've used 'Find
a City'? What's the level if you _don't_ use it?
--
JJZolx
--
I may have some leads in the TinySB crashes I'm experiencing. To cause
the problem all I need to do is navigate streams using the Find a City
menu item. It doesn't happen right away, but usually within a day or
two TinySB will crash (hang) and my SB Radio will lose the connection
to the server.
W
Becuase of all the crashes my SBS on the Touch is having, I'm starting
to suspect a hardware issue. Are there any hardware or memory
diagnostics that I can run to rule in/out hardware issues? Thanks,
Steve
--
steve781
ste
