Suspend Resume Improvement
How we might further improve our testing, reporting, and diagnosis of suspend issues. We should look at how we can better find out which devices are causing issues. For example resume can work but be delayed for 10s or so by a device. How can we detect this better. Apport, checkbox and the like.
Blueprint information
- Status:
- Complete
- Approver:
- Pete Graner
- Priority:
- Essential
- Drafter:
- Manoj Iyer
- Direction:
- Approved
- Assignee:
- Manoj Iyer
- Definition:
- Approved
- Series goal:
- Accepted for lucid
- Implementation:
-
Implemented
- Milestone target:
-
lucid-alpha-3
- Started by
- Pete Graner
- Completed by
- Robbie Williamson
Whiteboard
Status:
Planning for CELF testing drive complete. Patches proposed for additional timing information during suspend/resume. Looking to use bootchart style reports for comparisons.
Patches to tag / add subject when staging drivers are in use when reporting suspend/resume have been submitted (see Bug 524167 and Bug 524174)
Work Items lucid-alpha-3:
[manjo] Look at adding timing information to suspend/resume of devices:DONE
[manjo] Produce testing images for SCALE:DONE
Work Items ubuntu-
[manjo] Review current filed bugs for general trends:DONE
[manjo] apport -- allow us to detect frequency of failure:POSTPONED
[leannogasawara] apport -- tag / add subject when staging drivers are in use when reporting suspend/resume:DONE
[apw] arsenal -- extract resume time from apport reports and add to title (and tag?) based on time spread:DONE
