Bugzilla – Bug 16329
Enabled alarm doesn't ring at all
Last modified: 2010-08-24 07:47:53 UTC
I had set 4 Radios, all connected to MySB.com and with firmware r8837 or r8885, to ring at 7:30 am. Of these, I had to reset two to turn the alarm on. For the last two, I did not. When I enabled the alarm for these two, the alarm icon did not appear at the bottom of the screen. I pressed the Power button to OFF to show the clock screensaver and simulate usage. For the last two, the alarm icon failed to appear on the clock screensaver too. At 7:30 am, the units I had reset did ring. The units that never displayed the alarm icon did not ring. Looking at MySB.com, the last two players had their alarm state and time set properly. Also, the last two players had been running for awhile. Both had been streaming Classical.com previously. The two failing players eventually both crashed with System Error screens after about 2 hours. Looking at one failing player with free and top showed one had plenty of free memory available: Mem: 57612K used, 4492K free, 0K shrd, 7988K buff, 18024K cached CPU: 23% usr 26% sys 0% nic 47% idle 0% io 2% irq 0% sirq Load average: 0.65 0.49 0.39 1/65 746 PID PPID USER STAT VSZ %MEM %CPU COMMAND 719 699 root R 2792 4% 17% top 976 1 root R 32168 52% 14% /usr/bin/jive 997 976 root S 7248 12% 11% jive_alsa -d default -c dac -b 20000 - 680 925 root S 2580 4% 6% dropbear -i 308 2 root SW< 0 0% 3% [IRQ-9] 41 2 root SW< 0 0% 3% [IRQ-34] 925 1 root S 2872 5% 0% /usr/sbin/inetd 912 1 root S 2796 5% 0% /sbin/syslogd -S 699 680 root S 2792 4% 0% -sh 978 1 root S 2792 4% 0% /sbin/getty tty3 9600 VC vt100 1051 1 root S 2788 4% 0% udhcpc -R -a -p /var/run/udhcpc.eth1.p 1 0 root S 2788 4% 0% init 914 1 root S 2788 4% 0% /sbin/klogd 977 1 root S 2788 4% 0% init 968 1 root S 2092 3% 0% /usr/sbin/wpa_supplicant -B -Dwext -ie 387 1 root S < 2032 3% 0% /sbin/udevd -d 917 1 root S 1812 3% 0% /usr/sbin/watchdog 1015 1 root S 1812 3% 0% /usr/sbin/wpa_cli -B -a/etc/network/wp 9 2 root SW< 0 0% 0% [sirq-tasklet/0] 935 2 root SW< 0 0% 0% [AR6K Async] # free total used free shared buffers Mem: 62104 57708 4396 0 7988 Swap: 0 0 0 Total: 62104 57708 4396 Attaching logs for both. Please note that alarms were enabled around 7:20 am.
Created attachment 6897 [details] Log from Radio #1
Created attachment 6898 [details] Log from Radio #2
Created attachment 6899 [details] Crash log from one of the Radios
Created attachment 6900 [details] Log from NOT failing Radio
Note that "taskstatusbar" is in error state. Felix and Ben could not figure out how it got that way.
The next day I had 4 Radios set to ring at 7:30 am. Sure enough, the same two Radios from earlier in this bug rang but both sounded the backup alarm. The other two were OK. But that's another bug .... I then changed the alarm time at 7:40 am to ring at 8:00 am for those two (backup alarm Radios). After I changed the alarm, I saw the alarm icon at the bottom of the screen. I then pressed the Power button on each, and saw the alarm icon on the clock screensaver. When it was 8:00 am, the screen on both switched to the Alarm Clock screen. It's the same screen you see when you press the Alarm button on the front of Radio. Neither alarm sounded. I checked MySB.com, and both Radios had alarms set to 8:00 am. Logs for both units attached.
Created attachment 6901 [details] Log from Radio #1 -- Comment #6 Alarm set 7:40 am, alarm icon seen, doesn't ring at 8:00 am but see Alarm Clock menu
Created attachment 6902 [details] Log from Radio #2 -- Comment #6 Alarm set 7:40 am, alarm icon seen, doesn't ring at 8:00 am but see Alarm Clock menu
I forgot to mention that alarm icon was not visible at 8 am when Alarm Clock menu appeared. It was there before. Afterwards, at 8:20 am the alarm sounded. The alarm icon then reappeared. Backup alarm sounded then too, followed by the stream specified in the alarm. But that's another bug.
Created attachment 6903 [details] Log from Radio #2 -- Alarm OK at 9 am I set both of the previously problematic Radios to ring at 9 am. Both rang just fine -- played the stream specified, no backup alarm. Will possibly not have problems with alarms again today, since it is now past the MySB.com heavy usage window for alarms. Will try later today. Log for successful 9 am attached.
The most significant thing I see in the failed logs is the almost complete lack of log messages from between 7:40 and 8:00. The working log, however, has all the messages I would expect from a working system. I briefly looked at this line as being a potential red flag, but it shows up in both the non-working and working logs frequently: Jun 30 08:01:44 squeezeplay: WARN net.thread - NetworkThread.lua:146 network thread timeout for Task(SocketHttp {mysqueezebox.com_Request}(R)) I'm at a loss for what's going on here. Running a bad build? Out of memory issue? I'm admittedly clutching at straws and guessing.
Set alarm to ring at 7:30 am and it did with the right stream on this Radio. Also OK at 8:30 am. At 3 pm, noticed that the alarm icon was not on the screen. Pressed Power button, and saw that alarm was enabled and time was set, but no alarm icon. I changed Alarm 1 time to 15:20, and alarm icon still did not appear. Before 3:20 pm, I tested the unit by selecting Internet Radi->Staff Picks. The Staff Picks screen eventually appeared, but spinny was visible for a long time. Maybe indicative of internet connectivity issue? Sometime before 3:20 pm, the alarm icon appeared on the screen. The alarm subsequently rang at 3:20 pm. MySB.com alarm state was up-to-date the whole time. Attaching logs for this unit. I have two other Radios in the "no alarm icon on screen even though alarms enabled". Will leave in this state for further testing.
Created attachment 6907 [details] Log 1 from Radio #2 -- Comment #12
Created attachment 6908 [details] Log 2 from Radio #2 -- Comment #12
Follow up to Comment 12 -- once alarm rung at 3:20 pm, the alarm icon no longer appears on the screen, either at the bottom of the screen or on the clock screensaver.
I wonder if at least part of this is a dup of bug 16295
Mickey, what is the status of this one?
Unable to reproduce with r9009 firmware. Closing *** This bug has been marked as a duplicate of bug 16295 ***