Closed Bug 499729 Opened 15 years ago Closed 15 years ago

reimage maemo-n810-03

Categories

(Release Engineering :: General, defect)

ARM
Maemo
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: mozilla, Unassigned)

Details

infinite reboot
Fixed, then maemo-n810-07 fell over.
sigh, 06 and 16 are having issues?
might give up resuscitating these for today.
04 and 11 were unresponsive and unnetworked for a couple 15min pings in a row, but when i networked them and ssh'ed in, they were only up for 4-5min.  long reboots?

reimaging 06 and 08 right now. not sure what was up with 16... i think it was down for two hourly pings in a row but appears to be ok now.
I upped the [now misnamed] daily_reboot.sh check to every 15 min.
I was getting a number of down devices regularly earlier today; when I checked on them they weren't connected to wifi.  This was despite the shelf being open.

I:
- turned off bluetooth on a number of devices... not sure where that came from
- added a ping loop to buildbot/start.sh; if there are 50 failed pings in a row, reboot. (~20min, + 120s wait at the beginning)
- reimaged 06 and 08

Right now things look pretty good.  Time will tell.
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.