Closed Bug 738882 (tegra-076) Opened 13 years ago Closed 11 years ago

tegra-076 problem tracking

Categories

(Infrastructure & Operations Graveyard :: CIDuty, task, P2)

ARM
Android

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: philor, Unassigned)

References

()

Details

(Whiteboard: [buildduty])

Looks like the afternoon of the 20th it started hitting nothing but RETRY, then the morning of the 21st it mercifully died, and my vague memory says that it's been alerting ever since about its 100% packet loss.
This device was switched to Batt mode instead of norm. I reset the switch
Assignee: nobody → coop
Status: NEW → ASSIGNED
Priority: -- → P2
Already back in production.
Status: ASSIGNED → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
[Todo add to recovery bug -- swap sdcard] Last job 27 days, 17:12:13 ago buildbot.tac.sed;error.flg [Remote Device Error: unable to write to sdcard] Which is due to no sdcard actually mounted.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
ran ./stop_cp.sh on it
Assignee: coop → nobody
Summary: tegra-076 needs recovery → tegra-076 problem tracking
2012-10-30 13:15:02,296 WARNING MainProcess: Remote Device Error: unable to write to sdcard
Depends on: 807671
Was back in production, but timed out a lot. I ran stop_cp. Callek?
Assignee: nobody → bugspam.Callek
Going to try a reimage+sdcard swap.
Assignee: bugspam.Callek → nobody
Depends on: 817995
Status: REOPENED → RESOLVED
Closed: 13 years ago12 years ago
Resolution: --- → FIXED
Product: mozilla.org → Release Engineering
Watcher version needs upgrading - upgrade unsuccessful via script, requesting this tegra to be reimaged with the new image that has the latest Watcher (1.16).
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
No longer blocks: 925447
Depends on: 925447
explicitly disabled in slavealloc. Hangs at attempts to run |info| on sutAgent port (however |ver| and similar |exec mount| works fine). It also has invalid time and other weird stuff in logcat 01-01 00:01:57.226 W/ActivityManager( 1020): Launch timeout has expired, giving up wake lo ck! 01-01 00:01:57.303 W/ActivityManager( 1020): Activity idle timeout for HistoryRecord{483c2 9e8 com.mozilla.SUTAgentAndroid/.SUTAgentAndroid} 01-01 00:01:58.736 W/InputManagerService( 1020): Starting input on non-focused client com. android.internal.view.IInputMethodClient$Stub$Proxy@48447b98 (uid=10018 pid=1227) return code [0] :joel, is this signs of a dead device, is there anything more I can look for, or is it potentially scrap metal at this point.
Flags: needinfo?(jmaher)
if after a reboot, you cannot do a info command then something is wrong. we might want to reimage this device also if both of those fail, then it is scrap metal. It sounds like a familiar state, but that state is always remedied with a reboot.
Flags: needinfo?(jmaher)
Re-enabled in slavealloc.
Status: REOPENED → RESOLVED
Closed: 12 years ago11 years ago
Resolution: --- → FIXED
(In reply to Chris Cooper [:coop] from comment #11) > Re-enabled in slavealloc. And still no job, re-disabled listed for decom
Status: RESOLVED → REOPENED
Depends on: tegra-decomm
Resolution: FIXED → ---
Looks like this has been decommed now.
Status: REOPENED → RESOLVED
Closed: 11 years ago11 years ago
Resolution: --- → FIXED
Product: Release Engineering → Infrastructure & Operations
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in before you can comment on or make changes to this bug.