Bug 10720 – Jive: /usr/bin/jive uses over 90% of CPU cycle

Bug 10720 - Jive: /usr/bin/jive uses over 90% of CPU cycle

Summary:

Jive: /usr/bin/jive uses over 90% of CPU cycle

Status:	CLOSED WORKSFORME

Product:	SB Controller
Classification:	Unclassified
Component:	Setup
Version:	unspecified
Platform:	Other Other

Importance:	-- normal (vote)
Target Milestone:	Investigating
Assigned To:	James Richardson

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2009-01-15 16:36 UTC by Wallace Lai
Modified:	2012-02-27 17:18 UTC (History)
CC List:	3 users (show)

See Also:
Category:	---

Attachments
putty log for this bug. (323.72 KB, application/octet-stream) 2009-01-15 16:36 UTC, Wallace Lai	Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Wallace Lai 2009-01-15 16:36:47 UTC

Created attachment 4657 [details]
putty log for this bug.

FW:  Both 7.3 and 7.4

Steps to Reproduce:
1.  Have a Jive connected to a dongle and start the putty log.
2.  Power cycle the Jive.
3.  After Jive boots up, go to putty windows and type "top".
4.  Notice /usr/bin/jive is using up over 90% of CPU cycles.  The Jive is very very sluggish.
5  When this happens, updating to a new FW keeps failing.  Even when the FW is in the SD card.  Jive would go into the spinning wheel for a few seconds, then say try again.

Comment 1 Wallace Lai 2009-01-15 17:45:05 UTC

By the way, version r3665 may not have been r3665.  there were several builds that the "About" page kept reporting r3665.

Comment 2 James Richardson 2009-01-21 14:41:45 UTC

Richard: what if anything do we need to do about this?  what logs or tests should I run?

I have not seen this issue with r3852 yet, but will continue to test it

Comment 3 James Richardson 2009-01-22 14:04:47 UTC

Richard: did you change anything in r3856 that may have addressed this issue?  so far no high CPU load or laggy UI

Comment 4 Richard Titmuss 2009-01-26 06:15:20 UTC

no, i've not knowingly done anything to address this. should we close this bug unless it can be recreated?

Comment 5 James Richardson 2009-01-26 08:32:50 UTC

I'm going to mark it as investigating for now...

Comment 6 James Richardson 2009-02-18 09:51:41 UTC

I have not see this issue on FW >3665

Closing for now, please reopen if anyone sees this issue again

Comment 7 James Richardson 2012-02-27 17:18:56 UTC

Closing resolved bugs - if you feel this bug still exists please first re-test with the latest SW/FW version.  If you are able to reproduce then feel free to reopen and attach new logs / steps to reproduce.