Bugzilla – Bug 14945
SBC is rebooting (unknown cause)
Last modified: 2010-04-08 17:27:00 UTC
Se further comments in https://bugs-archive.lyrion.org/show_bug.cgi?id=13693 Theres been new development nobody will reopen that bug ?
My two controllers reboot frequently when coming out a sleep.
Do either of you have an SD card in the Controller? IF so, when you remove the card do your controllers reboot when comming out of sleep?
No SD card in the controller .
(In reply to comment #2) > Do either of you have an SD card in the Controller? IF so, when you remove the > card do your controllers reboot when comming out of sleep? No SD card here. I didn't know it accepted SD cards.
Can you both please do a Factory Reset on your controllers, then email me your MAC address as well as the PID from the sticker in the battery compartment.
Do any of you have the Controller enabled as a Play Back device? Settings > Advanced > Beta Features > Audio Playback >Enable Playback (BETA)
No audio playback is turned off . I try it from time to time (the playback bug ) , I might also have tied to conect that player to SN /msb.com sometimes.
(In reply to comment #6) > Do any of you have the Controller enabled as a Play Back device? > > Settings > Advanced > Beta Features > Audio Playback >Enable Playback (BETA) No. I do not have remote playback activated.
Everyone having this issue, we need to get a Log of what's happening. Please insert an SD card into your device, make sure there is a LOG folder at the root of the SD card. Once you have replicated the error, upload the resulting file(s) from the log folder to this bug
Created attachment 6242 [details] messages file of sbc I scp to controller and took the messages file, my SD card log directory is always empty for some reason . How to fix that. However the log is after the restart ? and sbc sedoes not keep the previus log files ? as messages1 and so forth ?
(In reply to comment #9) > Everyone having this issue, we need to get a Log of what's happening. Please > insert an SD card into your device, make sure there is a LOG folder at the root > of the SD card. > > Once you have replicated the error, upload the resulting file(s) from the log > folder to this bug I have placed the card in the slot and created the LOG directory. As soon as I get a chance, I'll send some data.
My controller rebooted on awakening from sleep twice yesterday. I had taken the SD card out due to unrelated problems. I will put the SD card back in. Is this still recommended?
Jim: Yes, I still need to get a log of the error from your controller
I experienced a reboot while the SD card was in the remote. However, when I read the card, there was no data in the Log folder. What do you suggest?
Maybe you can ssh to the controller and use cat on the messages file and copy and past3e to a txt document. Or use scp to copy the messagesit ? I have no controller anymore so I cant try right now. from memory the file would reside somewhere var/log I also had this problem no log on the SD card ( I think there is forums posts about it maybe a new bug ) Q: does the controller use log rotation of some kind ? i'm only finding 1 messages file ? Q2: with a log directory on an SD card will there be older logs to ? Q3: Is the folder name case sensitive ? log vs LOG ? on my ubuntu machine it is var/log likevise on my CC4.2 server
I'm not technically adept enough to ssh or "use cat". Sorry. (In reply to comment #15) > Maybe you can ssh to the controller and use cat on the messages file and copy > and past3e to a txt document. > Or use scp to copy the messagesit ? > > I have no controller anymore so I cant try right now. > from memory the file would reside somewhere var/log > > I also had this problem no log on the SD card ( I think there is forums posts > about it maybe a new bug ) > > Q: does the controller use log rotation of some kind ? i'm only finding 1 > messages file ? > > Q2: with a log directory on an SD card will there be older logs to ? > > Q3: Is the folder name case sensitive ? log vs LOG ? on my ubuntu machine it is > var/log likevise on my CC4.2 server
I have used my *new* controller (old one exchanged with logitech for examination) a little bit for a week and noticed one reboot and several cracks from the speaker. I have reformatted my SD card on a PC and put it in hopefully it catches some files. My exchange controller came in a box marked C/NO:32-0516 DATE1:10-OCT-08 Controller itself is marked PM/N C-RL65 P/N:830-000019 PID: LZ841S2
Your right, I forgot about that one. 7.4.x has an issue writing Log files. It was fixed in 7.5.x Q: does the controller use log rotation of some kind ? I'm only finding 1 messages file ? A: The internal log is wiped each reboot. So there is only 1 log Q2: with a log directory on an SD card will there be older logs to ? A2: yes, the SD card log folder (when its working) will continue writing to the same log file till XX size then start a new log file Q3: Is the folder name case sensitive ? log vs LOG ? on my ubuntu machine it is var/log likevise on my CC4.2 server A3: NO If you guys want, you can upgrade your controllers with the 7.5 firmware, then retest. 1) you could write log files 2) you can verify that the reboot is fixed/broken in the 7.5 firmware. Simply download the .BIN file from here: http://update.slimdevices.com/update/firmware/7.5.0/ You would want to download 2 files and place them on the SD card jive_7.5.0_r8162.bin (rxxx will changed each day) jive.version Once you have both of those on the SD card, put it in your Controller. Boot, go to Settings > advanced > software update You should see the number of the firmware you downloaded (r8162 in this example) Select that version to load it onto your controller. Let me know if that doesn't work, or you still don't get a log file
I'm on 7.5 the latest reboot was with a late 7.5 But now the SD card is in hopefully I get something Btw I use and old 16mb card for this is it big enough for the log files ?
Created attachment 6358 [details] cat-messages Now it rebooted again, but SD card write is still not working on 7.5 I did a cat Odd circumstance the server was off i'd except sbc to wol. It rebooted then wol Next I'll connect directly to mysbs.com with one of my players with help of sbc, to see if this in the end will provoke reboot more often. Reboot have only occured 2 times afiak since i got my new controller. It might have rebooted more unoticed by me.
Oopps note in that messages file it boots with the wrong date JAN 1 and then switches to DEC 5
Created attachment 6361 [details] messages again Ooops, it did it again. Another rebbot another log. Can you see anything from these ? is there something else that can be done ?
Was that log from the SD card or did you get it from the controller AFTER the device reset? Firmware r7.5 should re-enable logging to SD card, that is the best way to capture this error, as the logs are wiped when the device reboots.
Created attachment 6364 [details] mesages.0 Yes I spc'd this log :-/ but now the SD card do work ? I've found the 6september logs there. Attaches messages.0 and messages again with more info in them
Created attachment 6365 [details] messages again
Btw the SD card just started to work again I have removed the card and checked it was empty until now ?
Yes, those are the right ones, looking into it now
Created attachment 6380 [details] zip with the latest log files More logs after todays crash for some odd reson the files are created 10 september even if it's 12 now ? A look in these log files confirm that it is nothing in them from the last 2 days ? I have used the controller and it rebooted just now ?
Ok. I finally got around to installing 7.5.0 in the controller. My controller rebooted twice yesterday before the installation. I should have some log files for you too.
Uh oh. Looks like I'm hung in a software install cycle. When the controller rebooted, it just came right back to the screen asking if I wanted to install the 7.5.0 software. So I took the SD card out and now it wants to upgrade to 7.4.1 r7915 I'm going to do that since I cannot do anything else.
Now I'm getting odd behavior. The controller will make a little crackling sound when it goes to sleep. Dang.
That crackling noise is nothing new numerous reports about it in the forum. I had it on two different controllers, so it should be a software issue unless an alarmingly large amount of controllers have hardware issues :-/ But i don't think there is a bug report on this yet ? or is it . One wonders if it is some kind of power save that turns of the audio circuits or something ?
Felix says he will look at the logs
Hmm, the latest log file (12/12/09) stops when Controller went to sleep. I don't know how we can capture a log onto SD card when Controller wakes up. But here is something I would like you guys to try and see if that makes a difference: When you wake your Controller keep turning the wheel until it has fully resumed, i.e. shows the menu again. Thanks Felix
I don't know if this will help with the troubleshooting, but when I used to use the release version of 7.4.1 on my standard Windows box, I NEVER had this problem with my Controller. Since moving to the release version of SBS for WHS, I am getting the reboot bug regularly.
I also changed my router before the reboots started happening. This probably has more relevance than the change to WHS, since there may be a specific control packet which is causing the the Controller to restart itself. The router is a D-Link DIR-615
I've got the same problem. Installed the 7.5.0 firmware -> You don't have do downgrade after that - just press help -> then HOME-Button and you can use the controller with 7.5.0 Maybe someone can tell us how to get arround that message ;-) I will report if this firmware will cause reboots again. Lars
Changing priorities due to management guidance.
(In reply to comment #38) > Changing priorities due to management guidance. Reboots still appears with 7.5.0 firmware. I've found the following WARNING in dmesg: Unbalanced enable for IRQ 52 WARNING: at kernel/irq/manage.c:158 enable_irq() [<c0033bcc>] (dump_stack+0x0/0x14) from [<c0068798>] (enable_irq+0x68/0xb0) [<c0068730>] (enable_irq+0x0/0xb0) from [<bf01c79c>] (sbi_get_int_status+0x4c/0x244 [gspi8xxx]) r5:c3c723a0 r4:00000005 [<bf01c750>] (sbi_get_int_status+0x0/0x244 [gspi8xxx]) from [<bf005f2c>] (wlan_service_main_thread+0x1b4/0x548 [gspi8xxx]) r8:c3c72d70 r7:c38fc000 r6:c3c723a0 r5:c3a90000 r4:00000000 [<bf005d78>] (wlan_service_main_thread+0x0/0x548 [gspi8xxx]) from [<c005ac90>] (kthread+0x54/0x80) [<c005ac3c>] (kthread+0x0/0x80) from [<c004a800>] (do_exit+0x0/0x7dc) r5:00000000 r4:00000000 NETDEV WATCHDOG: eth0: transmit timed out I will add the log soon.
Inserted sd card for logs... but no logs will created inside... Maybe sd-card is not mounted at check in rcS. So I did the steps manually: # ps ax|grep syslog[d] 435 ? Ss 0:00 /sbin/syslogd -S # if [ -e /media/*/log ]; then echo yep; fi yep # killall syslogd # ps ax|grep syslog[d] # LOG_DIR=`echo /media/*/log`; /sbin/syslogd -S -s1000 -O $LOG_DIR/messages # ps ax|grep syslog[d] 777 ? Ss 0:00 /sbin/syslogd -S -s1000 -O /media/mmcblk0p1/log/messages # ulimit -c unlimited # echo "$LOG_DIR/core-%e" > /proc/sys/kernel/core_pattern I will send the content after next reboot. By the way... Has there already been a bug created for the sd-log problem? Lars
On my Ubuntu squeezebox Server I could get around the initial downgrade request of the controller using the 7.5.0 firmware: Put the updated 7.5.0 firmware file and the corresponding version file into /var/lib/squeezeboxserver/cache/updates: cd /var/lib/squeezeboxserver/cache/updates mv jive.version jive.version.old wget http://update.slimdevices.com/update/firmware/7.5.0/jive.version wget http://update.slimdevices.com/update/firmware/7.5.0/jive_7.5.0_r8272.bin
Created attachment 6419 [details] messages 7.5.0 after reboot /media/mmcblk0p1/log/messages after reboot / 7.5.0 system Curious is that last entry in this log is at 6:23:41 and next entry in /var/log/messages is 7:16:59
(In reply to comment #38) > Changing priorities due to management guidance. Hi Chris, due to still appearing reboots with 7.5 firmware I suggest to set it to critical. Lars
== Auto-comment from SVN commit #8283 to the jive repo by felix == == https://svn.slimdevices.com/jive?view=revision&revision=8283 == Bug: 14945 Description: Possible fix for SBC is rebooting (unknown cause) - Test w/ patch: 50 times ok out of 50 suspend resume cycles - Test w/o patch: 37 times not ok out of 67 suspend resume cycles
Update hours worked.
Assuming there isn't another cause forcing SBC to reset while resuming from suspend I think this should be fixed. Fix is in r8283.
(In reply to comment #46) > Assuming there isn't another cause forcing SBC to reset while resuming from > suspend I think this should be fixed. > > Fix is in r8283. Nice but... latest fw on server http://update.slimdevices.com/update/firmware/7.5.0/jive_7.5.0_r8280.bin Please build ;-)
This happens quite frequently to my controller since the 7.4.1 software. Also boot up time longer since 7.4.0, so quite a pain!
*** Bug 15791 has been marked as a duplicate of this bug. ***
This bug has been marked fixed in a released version of Squeezebox Server or the accompanying firmware or mysqueezebox.com release. If you are still seeing this issue, please let us know!