Bug 14140 - Knobs stop working after a while
: Knobs stop working after a while
Status: CLOSED FIXED
Product: SB Radio
Classification: Unclassified
Component: Buttons/Knob
: Include FW version in comment
: PC Other
: P1 critical (vote)
: 7.4.0
Assigned To: Caleb Crome
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2009-09-18 19:52 UTC by Andy Grundman
Modified: 2009-10-05 14:25 UTC (History)
5 users (show)

See Also:
Category: Bug


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Andy Grundman 2009-09-18 19:52:20 UTC
PVT2, firmware 7656.

After a while both knobs will stop scrolling.  Push still works.

Here's a log of when it first happened:

Sep 18 22:24:07 kernel: [ 4893.580897] i2c-adapter i2c-1: Data not transmitted
Sep 18 22:24:07 kernel: [ 4893.585948] i2c-adapter i2c-1: Could not set I2C Bus Busy bit to zero.
Sep 18 22:24:07 squeezeplay: ERROR  squeezeplay.task - Task.lua:75 task error statusbar: ...jive/applets/SqueezeboxBaby/SqueezeboxBabyApplet.lua:620: attempt to perform bitwise operation on local 'chargerState' (a nil value)
Sep 18 22:24:07 squeezeplay: stack traceback:
Sep 18 22:24:07 squeezeplay: 	/usr/share/jive/jive/ui/Task.lua:75: in function 'resume'
Sep 18 22:24:07 squeezeplay: 	/usr/share/jive/jive/ui/Framework.lua:317: in function 'eventLoop'
Sep 18 22:24:07 squeezeplay: 	/usr/share/jive/jive/JiveMain.lua:435: in function </usr/share/jive/jive/JiveMain.lua:277>
Sep 18 22:24:07 squeezeplay: 	(tail call): ?
Sep 18 22:24:07 squeezeplay: 	/usr/share/jive/jive/JiveMain.lua:650: in main chunk
Sep 18 22:24:07 squeezeplay: 	[C 0x53fdd]: ?
Sep 18 22:24:07 squeezeplay: 	[C 0x28f19]: ?
Sep 18 22:24:12 squeezeplay: WARN   squeezeplay.task - Task.lua:98 task statusbar in error state
Sep 18 22:24:17 squeezeplay: WARN   squeezeplay.task - Task.lua:98 task statusbar in error state
Sep 18 22:24:22 squeezeplay: WARN   squeezeplay.task - Task.lua:98 task statusbar in error state
Sep 18 22:24:27 squeezeplay: WARN   squeezeplay.task - Task.lua:98 task statusbar in error state
Sep 18 22:24:32 squeezeplay: WARN   squeezeplay.task - Task.lua:98 task statusbar in error state
Sep 18 22:24:37 squeezeplay: WARN   squeezeplay.task - Task.lua:98 task statusbar in error state
Comment 1 Andy Grundman 2009-09-18 19:53:16 UTC
I should note Baby was on battery this whole time.
Comment 2 Caleb Crome 2009-09-18 20:01:21 UTC
What hardware revision?
Comment 3 Caleb Crome 2009-09-18 20:02:10 UTC
Oh, you said PVT2 :-)

That's odd.  How long had it been on battery?

what's
 # cat /sys/bus/i2c/devices/1-0010/battery_voltage 

say?
Comment 4 Andy Grundman 2009-09-18 20:05:48 UTC
I don't know how long it has been on battery, 2-3 hours.

# cat /sys/bus/i2c/devices/1-0010/battery_voltage 
cat: read error: Operation not permitted
Comment 5 Andy Grundman 2009-09-18 20:07:01 UTC
There are some additional log messages related to msp and i2c:

[ 6287.830762] ERROR: msp430 i2c bus failed
[ 6287.834783] i2c-adapter i2c-1: Bus Arbitration lost
[ 7262.247032] i2c-adapter i2c-1: Bus Arbitration lost
[ 7262.253940] i2c-adapter i2c-1: Could not grab Bus ownership
[ 7411.795152] i2c-adapter i2c-1: Bus Arbitration lost
[ 7411.802230] i2c-adapter i2c-1: Could not grab Bus ownership
Comment 6 Andy Grundman 2009-09-21 09:02:30 UTC
Just happened again.

Firmware 7660
AC power only
Playing music for 90 minutes

[ 5304.611286] i2c-adapter i2c-1: Data not transmitted
[ 5304.618494] i2c-adapter i2c-1: Could not set I2C Bus Busy bit to zero.
[ 5579.071532] i2c-adapter i2c-1: Could not grab Bus ownership
[ 5579.077253] i2c-adapter i2c-1: Bus Arbitration lost
[ 5579.082539] i2c-adapter i2c-1: Could not grab Bus ownership
[ 5579.088230] i2c-adapter i2c-1: Bus Arbitration lost
[ 5579.093483] i2c-adapter i2c-1: Could not grab Bus ownership
[ 5579.099165] i2c-adapter i2c-1: Bus Arbitration lost
[ 5579.104419] i2c-adapter i2c-1: Could not grab Bus ownership
[ 5579.111103] ERROR: msp430 i2c bus failed
[ 5579.115120] i2c-adapter i2c-1: Bus Arbitration lost

I re-programmed the msp and here are all the values afterwards:
												
	adc_0	1023										
	adc_1	362										
	adc_10	480										
	adc_11	682										
	adc_12	6										
	adc_13	5										
	adc_14	5										
	adc_15	4										
	adc_2	421										
	adc_3	89										
	adc_4	894										
	adc_5	210										
	adc_6	494										
	adc_7	738										
	adc_8	895										
	adc_9	680										
	alarm_time	4294967295										
	ambient	80										
	battery_capacity	2000										
	battery_charge	810										
	battery_charge_rate	10										
	battery_disable	7										
	battery_discharge_rate	11										
	battery_temperature	1161										
	battery_vmon1_voltage	4235										
	battery_vmon2_voltage	8491										
	battery_voltage	14905										
	charger_event	0										
	charger_state	8										
	fw	1255										
	gp_register	283686952306183										
	ir	1234										
	kill	238										
	modalias	i2c:msp430										
	msp_buffer	283686965740782										
	name	msp430										
	power_mode	7										
	sys_voltage	17686										
	test_1	7										
	test_2	0										
	test_4	67438087										
	test_8	283686952306183										
	time	122										
	wall_voltage	18052
Comment 7 Caleb Crome 2009-09-21 09:33:37 UTC
Woah!  This was AC only?  I don't think anybody's seen that.  

We should swap that unit out for a new one, and do some FA on that.  That sounds like it could be hardware issue.
Comment 8 Caleb Crome 2009-09-22 09:09:17 UTC
This only seems to be happening to Andy's unit.  I believe that it's a problem with his unit -- it's on the way back here.
Comment 9 Andy Grundman 2009-09-23 14:17:39 UTC
I'm seeing this on my new PVT2 Baby too... :(  It's basically sat unused on AC power all day, just showing the clock.  Went to do something and the knobs were dead in the usual way.
Comment 10 Caleb Crome 2009-09-23 14:27:09 UTC
(In reply to comment #9)
> I'm seeing this on my new PVT2 Baby too... :(  It's basically sat unused on AC
> power all day, just showing the clock.  Went to do something and the knobs were
> dead in the usual way.

Wha?!?!?  That doesn't make sense.
Was the battery plugged in at all?
Comment 11 Andy Grundman 2009-09-23 18:35:14 UTC
Well it happened again, with the new power supply.  It had been working fine for several hours and I brought Baby back down to the office.  When I plugged it into my strip down here it killed it.  I thought it might be something to do with my power strip, but I can't reproduce it now.  Tried several plug/unplug cycles waiting a few minutes on battery in between, with no luck.  I'll keep the wall_voltage loop going in case it happens again.
Comment 12 Caleb Crome 2009-09-23 20:52:01 UTC
This is very, very strange.  Your previous unit's been running here since about 4pm, no odd behavior, nothing.  Works perfectly.  I'm on battery now.  I'll switch to AC power.
-C
Comment 13 Andy Grundman 2009-09-24 14:34:11 UTC
It has not happened at all today using the no-IR firmware.  I updated (accidentally) to r7745 which downgraded the MSP version to 1263, and then I saw the problem come back within 30 minutes.
Comment 14 Caleb Crome 2009-09-24 17:09:08 UTC
Okay, so I think I have a fix to this.  Checked in in rev r7746, on the trunk branch.

The question is:  do we check this in for 7.4.0?  

Richard?  Anybody?
Comment 15 Caleb Crome 2009-09-24 17:10:09 UTC
This seems to be due to some IR or RF interference in Andy's office.  Others could experience this, and have their units stop responding to knobs, IR, etc.
Comment 16 SVN Bot 2009-09-25 06:13:45 UTC
 == Auto-comment from SVN commit #7747 to the jive repo by richard ==
 == https://svn.slimdevices.com/jive?view=revision&revision=7747 ==

Fixed bug #14140
Review Caleb's msp changes, and checking in for 7.4.0.
Comment 17 James Richardson 2009-10-05 14:25:40 UTC
This bug has been marked as fixed in the 7.4.0 release version of SqueezeBox Server!
    * SqueezeCenter: 28672
    * Squeezebox 2 and 3: 130
    * Transporter: 80
    * Receiver: 65
    * Boom: 50
    * Controller: 7790
    * Radio: 7790  

Please see the Release Notes for all the details: http://wiki.slimdevices.com/index.php/Release_Notes

If you haven't already, please download and install the new version from http://www.logitechsqueezebox.com/support/download-squeezebox-server.html

If you are still experiencing this problem, feel free to reopen the bug with your new comments and we'll have another look.