Bug 6861 - Using Choose Player crashed Controller
: Using Choose Player crashed Controller
Status: RESOLVED DUPLICATE of bug 6918
Product: SB Controller
Classification: Unclassified
Component: Setup
: unspecified
: PC Windows XP
: P2 normal (vote)
: ---
Assigned To: Dan Evans
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2008-01-29 15:33 UTC by Dan Evans
Modified: 2008-02-03 12:04 UTC (History)
2 users (show)

See Also:
Category: ---


Attachments
Logs from Jive crash. (30.84 KB, application/octet-stream)
2008-01-29 15:35 UTC, Dan Evans
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Dan Evans 2008-01-29 15:33:13 UTC
I was attempting to set up a Receiver I'd just factory resetted.  I selected "Choose Player" and selected the player awaiting setup.  Jive then rebooted suddenly.  The player remained on setup. (blinking RED)

Logs attached below but they're strange-- dated Feb. 14, 2022 ?!
Comment 1 Dan Evans 2008-01-29 15:35:08 UTC
Created attachment 2772 [details]
Logs from Jive crash.

Crash occurred about 3:20 01/29/08  (for purposes of parsing logs)
Comment 2 KDF 2008-01-29 15:43:35 UTC
strange indeed.  I can't even find a Jan 29 in there anywhere.  Dates also seem to jump back and forth.
Comment 3 Blackketter Dean 2008-01-29 21:20:41 UTC
Doesn't make sense to me either.

Dan: did this happen only once?
Comment 4 Richard Titmuss 2008-01-30 02:11:54 UTC
I added logging to /log on the SD card as well, thought that path would be easier to tell non-unix community/customers. Been regretting choosing /var for a while. Looks like I messed up the logging to /var in the process, both were meant to work. Dan can you use /log instead. I've fixed /var in r1693, but will probably remove that option in 7.0.1.

I have seen this crash, maybe once. It's rare, and (if the logging was working) will probably result in a core file. You mentioned "rebooted suddenly", any reboot will be due to the watchdog timer which is currently set for 30 seconds. Do you think Jive was stuck for 30 seconds?

Comment 5 Richard Titmuss 2008-01-30 04:10:26 UTC
So while working on the power management I did get a crash in Choose Player. This is probably related to the work I was doing and unlikely to be the same as Dan saw. But for future reference the stack trace from the core file was:

#0  0x40c0a128 in wpa_ctrl_get_fd ()
   from /home/ubuntu/build/squeezeboxJive/build/usr/lib/lua/5.1/jiveWireless.so
(gdb) bt
#0  0x40c0a128 in wpa_ctrl_get_fd ()
   from /home/ubuntu/build/squeezeboxJive/build/usr/lib/lua/5.1/jiveWireless.so
#1  0x40c09fe4 in jive_net_wpa_ctrl_get_fd ()
   from /home/ubuntu/build/squeezeboxJive/build/usr/lib/lua/5.1/jiveWireless.so
#2  0x00025ec4 in luaD_precall ()
#3  0x00025ff4 in luaD_call ()
#4  0x000233cc in lua_call ()
#5  0x403862b4 in getfd () from /home/ubuntu/build/squeezeboxJive/build/usr/lib/lua/5.1/socket/core.so
#6  0x40386380 in collect_fd () from /home/ubuntu/build/squeezeboxJive/build/usr/lib/lua/5.1/socket/core.so
#7  0x403864e4 in global_select () from /home/ubuntu/build/squeezeboxJive/build/usr/lib/lua/5.1/socket/core.so
#8  0x00025ec4 in luaD_precall ()
#9  0x0002f4e4 in $a ()
#10 0x0002f4e4 in $a ()

This was caused be restarting the wpa-supplicant and it will need fixing before the power saving can be enabled.
Comment 6 Dan Evans 2008-01-30 10:02:19 UTC
Dean: I have seen this only once

Richard: I will switch to /log going forward.  Was it 30 seconds?  I can't say for certain, but I don't remember it being 30 seconds.  It's easily possible I got distracted by something though and it was stuck longer than I think.
Comment 7 Blackketter Dean 2008-02-01 17:45:23 UTC
Dan to try to reproduce.

QA Folk:  Keep an eye out for this...
Comment 8 Blackketter Dean 2008-02-02 09:02:55 UTC
CC'ing Ben.  Any idea, Ben?
Comment 9 Blackketter Dean 2008-02-03 12:04:14 UTC
Marking this as a dup, as there's additional information in bug 6819

*** This bug has been marked as a duplicate of 6918 ***