XO-1.75/Kernel/Testing
< XO-1.75
Jump to navigation
Jump to search
Kernel developers, put your new kernel in a new section here. Latest at top. Testers place links to reports indented under the kernel.
7dad6c10 - arm-3.0-wip-wfi (BROKEN)
- XO-1.75: always send the suspend hint command to the EC, even on C-series
- EC logged in S7
- further code to work around EC communications race; discussion with pgf brought up another issue, and include patch from pgf.
- testing by
- Samuel Greenfeld
- 1xC1 SKU202 tested; logs "olpc-ec-1.75: SSP reports TX underrun" and "SSP reports RX overrun" every three seconds shortly after the kernel starts initializing. This causes the XO to never fully boot, making this kernel unusable.log with EC at S7 log with EC at S47
- Samuel Greenfeld
afa391a5 - arm-3.0-wip-wfi
- Revert "olpc-1.75: back off the hardware clock gating for MMC devices"
- EC logged in S7
- test code to work around an EC communications race; needs further work, but this should hopefully keep things from hanging.
- testing by
9177e6a8 - arm-3.0-wip-wfi
- olpc-1.75: back off the hardware clock gating for MMC devices
- purpose: kill off the SET_BLOCK_COUNT errors seen by Quozl in the prior tests
- result of test: no change (the patch did not affect the outcome).
- testing by
- James Cameron, Q4C11, os20, 10sec/10sec S/R runin,
- C1 SKU201 passed, ec host,
- C1 SKU202 hung, after 11 minutes, SET_BLOCK_COUNT eMMC failure at kernel timestamp 1159.762854, host
- B1 SKU199 hung, after 2.5 hours, SET_BLOCK_COUNT eMMC failure at kernel timestamp 7409.481875, host
- B1 SKU199 hung,
- B4 SKU199 hung, (connecting serial port afterwards did not show streaming eMMC messages),
- B1 SKU198 hung.
- James Cameron, Q4C11, os20, single, dortc,
- C1 SKU202 manually stopped early, had been needing keyboard wakeup,
- B1 SKU199 manually stopped early,
- B1 SKU199 manually stopped early, had been needing keyboard wakeup,
- B4 SKU199 manually stopped early.
- James Cameron, Q4C11, os20, 10sec/10sec S/R runin,
- purpose: test theory that battery state of charge changes are associated with hangs
- Samuel Greenfeld, os23, 4 C1 SKU201 2 C1 SKU202, olpc-runin-tests-0.16.7-1 installed instead of bringup build, runin-battery test disabled
- 2xC1 SKU201 hung on resume after 10.5 hours host#3/ec#8 & host #6
- 1xC1 SKU202 hung after 11.75 due disabling pm_async or keyboard events during runin host#4, possibly while resetting system #3 in front of it.
- All systems then reset with pm_async disabled, 4 C1 SKU201 & 3 C1 SKU 202 total.
- 1xC1 SKU202 hung citing phantom keyboard events followed by an illegal instruction, pm_async disabled [1]
- 1xC1 SKU201 hung with MMC problems, pm_async disabled [2]
- Samuel Greenfeld, os23, 3 B1 SKU198 4 B1 SKU199, olpc-runin-tests-0.16.7-1 installed instead of bringup build, runin-battery test enabled, runin-camera, runin-wlan disabled, pm_async enabled'
- 1xB1 SKU 199 failure to properly handle EC interrupt on resume [3]
- James Cameron, Q4C11, os20, 10sec/10sec S/R runin, without runin-battery, without battery inserted.
- Samuel Greenfeld, os23, 4 C1 SKU201 2 C1 SKU202, olpc-runin-tests-0.16.7-1 installed instead of bringup build, runin-battery test disabled
- purpose: disable asynchronous S/R
58360582 - arm-3.0-wip-wfi
- Revert "olpc-ec-1-75: clean up cmd state locking and other things"
- purpose: test the old EC driver across runin and s/r.
- result of test: no change (the patch did not affect the outcome).
- additional tests: against normal runin, and 10sec/10sec S/R runin.
- testing by
- Richard Smith, os21, C1 SKU201, three runs, against two-stage runin, pass.
- James Cameron, Q4C11, os20, 10sec/10sec S/R runin,
- James Cameron, Q4C11, os20, 10sec/10sec S/R runin,
- Samuel Greenfeld, os23, 4 C1 SKU201 2 C1 SKU202, olpc-runin-tests-0.16.7-1 installed instead of bringup build
- C1 SKU201 hung on resume after 21 cycles (10s on/10s suspend), host#3 ec#8
- C1 SKU201 hung on resume overnight (10s on/10s suspend), host#6
- C1 SKU202 EC communications failure overnight host#1 ec#7
- Three remaining C1 systems running default runin suspend cycle timings did not hang after 18 hours.
2d8e7cc - arm-3.0-wip-wfi
- sdhci: ignore interrupts received after suspend
- zImage-2d8e7cc-wip-wfi
- os: os20, ofw: q4c08 or q4c09, runin in build, runin-fscheck disabled, runin-battery disabled, runin-sus set to 10sec/10sec
- purpose, test looking for non-ec related hangs.
- result of test: no change (the patch did not affect the outcome).
- testing by
6f125d7 - arm-3.0-wip
- sdhci: ignore interrupts received after suspend (same commit comment but different git branch than above)
- zImage-6f125d7-wip
- os: os20, ofw: q4c08, runin in build, runin-sus disabled.
- purpose: verification of a build for manufacturing testing.
- result of test: success, the kernel is stable for runin testing in manufacturing if used without suspend and resume.
- testing by
- was added to build os23.
- os23 testing by
- James Cameron, C1 SKU201, C1 SKU202, B4, B1, B1, B1, all passed 24 hr testing.
4239902
- os20 q4c09 runin 0.16.7 10sec 10sec 24hrs
- testing by
- James Cameron, fail, one unit hung, all units lost EC communications (blank SOC display, hang after runin pass),
- C1 SKU201 pass, host log at point of SOC loss, ec log at point of SOC loss
- C1 SKU202 hang at 1821 cycles, remaining 10:35:38, no serial cable was attached,
- B4 SKU199 pass,
- B1 SKU199 pass,
- B1 SKU199 pass,
- B1 SKU198 pass,
- James Cameron, fail, one unit hung, all units lost EC communications (blank SOC display, hang after runin pass),