Closed Bug 731669 Opened 12 years ago Closed 12 years ago

Figure out reboot issues on panda boards

Categories

(Testing :: General, defect)

x86
macOS
defect
Not set
critical

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: armenzg, Assigned: ted)

References

Details

ctalbert is suspecting that it might be related to hardware issues of the non-ES boards.

This is one of our highest priorities to get these boards working properly in our current buildbot automation.
Blocks: 729323
Well, I have tried this now on a panda board ES and I have exactly the same issue as we did with the non-ES panda.

Reboot merely shuts down the panda board. It doesn't actually come back up.

:(
Have you had a chance to ask in the pandaboard forums?
Did this get figured out as well?
On the image I built both "adb reboot" and the SUTAgent's rebt command work.

Additionally, the rack enclosure for the pandas has remote power-cycling, so I think this should be good to go.
Assignee: ctalbert → ted.mielczarek
I guess we can close this then? or not yet?
Sounds good.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
I had trouble with this working reliably, even from adb while using Ted's image.  We should make sure we can do 20 in a row from each method.
I admittedly did not test it that thoroughly, I simply rebooted my board a few times with each method.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
I did 20 reboots in a row via adb as well as SUT.

My problems with reboot were seen after abusing the panda with tests.  I suspect those are more related to SUT/ADB reliability and networking in general.
Status: REOPENED → RESOLVED
Closed: 12 years ago12 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.