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.
See also:
0a896953 - arm-3.0-wip-wfi
- olpc-ec: consolidate code and ensure TxFIFO is empty before writing to it
- EC logged in S7, runin 0.17.0 or 0.16.7 (not C2 builds) if possible
- Past kernels tested briefly in the past ~12 hours suggest that the fixes in said kernels may fix all known easily reproducible hangs. Need to prove/disprove this.
- If you have enough systems, try using stock runin 0.17.0-style settings as well as anything known to cause particular types of failures. (EC failures seem to be common within a few hours with 10s on/10s off suspend, only using runin-main/gtk/common/tests/sus/battery.)
- testing by
- James Cameron, six units, defconfig, runin 0.17.0, 10sec/10sec, 60sec watchdog, 0 to pm_async, started around Sat Jan 7 08:24:00 UTC 2012,
- Samuel Greenfeld, five C1 units, runin 0.16.7 setup like 0.17 (light sensor test disabled), 0 to pm_async
- one C1 SKU201 hang during resume, normal runin settings, see [host log]
- B1 testing being setup to try and reproduce SET_BLOCK_COUNT hangs above
- Jon Nettleton
ebf24ea6 - arm-3.0-wip-wfi
- http://dev.laptop.org/git/olpc-kernel/commit/?h=arm-3.0-wip-wfi&id=ebf24ea6
- test dependencies: EC logged in S7, use whatever magic possible to get the EC errors
- Another attempt to fix the problem of EC communication failures
- testing by
196c2f806 - arm-3.0-wip-wfi
- http://dev.laptop.org/git/olpc-kernel/commit/?h=arm-3.0-wip-wfi&id=196c2f80
- testing by
- James Cameron, with a local debugging patch, saw two instances of eMMC "error -110 sending SET_BLOCK_COUNT command", on C1 SKU201 and C1 SKU202, two test units with full runin 0sec/3sec (extreme) suspend and resume failed to show any hangs, currently going are five test units with full runin 10sec/10sec (aggressive) suspend and resume.
- C1 SKU202 reported EC related kernel problems, see log, should be fixed in later kernels.
- James Cameron, with a local debugging patch, saw two instances of eMMC "error -110 sending SET_BLOCK_COUNT command", on C1 SKU201 and C1 SKU202, two test units with full runin 0sec/3sec (extreme) suspend and resume failed to show any hangs, currently going are five test units with full runin 10sec/10sec (aggressive) suspend and resume.
46e079fe - arm-3.0-wip-wfi
- http://dev.laptop.org/git/olpc-kernel/commit/?h=arm-3.0-wip-wfi&id=46e079fe
- EC logged in S7
- Should fix the hang caused by suspend being aborted due to a wakeup event. May also help with other IRQ hangs as I have fixed a previous mistake I made when moving the audio island code.
- Testing aborted suspends can be done by running this command and then hitting the keyboard right away.
echo $(cat /sys/power/wakeup_count) > /sys/power/wakeup_count && echo mem > /sys/power/state
- testing by
- James Cameron, with a local debugging patch, saw one instance of eMMC "error -110 sending SET_BLOCK_COUNT command", on C1 SKU201, see log tail, and several instances of the hang in dpm_resume().
bfc1b92b - arm-3.0-wip-wfi
- http://dev.laptop.org/git/olpc-kernel/commit/?h=arm-3.0-wip-wfi&id=bfc1b92b
- EC logged in S7
- Should fix the (known) cause of failing EC commands on s/r. Please test both this and the prior kernel.
- testing by
b7f22e1d - arm-3.0-wip-wfi
- http://dev.laptop.org/git/olpc-kernel/commit/?h=arm-3.0-wip-wfi&id=b7f22e1d
- EC logged in S7
- Should fix the problem where, upon a single EC error, all further EC commands fail. Please test!
- testing by
10ebd28f - arm-3.0-wip-wfi
- olpc-ec: log a warning if we manage to process an EC command deep inside of suspend,
- a tar.gz by James,
- testing by
- Richard?
ae48be89 - arm-3.0-wip-wfi
- a tar.gz by James,
- testing by
5ba0b446 - arm-3.0-wip-wfi
- olpc-ec: allow unknown commands to be executed
- test dependencies: EC logging (S7), kernel logging with EC debug enabled ("echo 1 > /sys/module/olpc_ec_1_75/parameters/ec_debug"), pm_async disabled.
- purpose: improve EC driver; fewer (or no?) races/crashes..
- testing by
ff199462 - arm-3.0-wip-wfi
- olpc-ec: ensure gpio cmd is left low if something screws up
- EC logged in S7
- Still has FIQ debugger
- Should help reset EC bus to avoid subsequent failures after the first command fails.
- testing by
- Samuel Greenfeld
- C1 hang on resume (#3), OLS runin disabled, Q4C11 normal EC code host (mmp2_pm_finish: Enable audio island ... mmp2_pm_finish: Done ... 72.616ms ... mmp-camera mmp-camera.0: resume) [1]
- C1 hang on resume (#6), OLS runin disabled, Q4C11 normal EC code
- C1 hang on resume (#3), OLS runin disabled, Q4C11 modified EC code ecimage-0.3.07pgf-668.bin host ec
- Samuel Greenfeld
3d4cf36c - arm-3.0-wip-wfi
- mmp2_fiq_debugger.c add file missing from other merge
- EC logged in S7
- This enables the FIQ debugger. Reproduce kernel hangs, then from a serial console send a Break which should drop you to a debug prompt. run bt to see what is going on.
- testing by
- James Cameron, 10sec/10sec,
- James Cameron, 0sec/3sec, FIQ was verified as working before starting,
26f404e3 - arm-3.0-wip-wfi
- Revert "olpc-ec: don't process/ack packets when there's an underrun error"
- EC logged in S7
- further code to work around EC communications race; discussion with pgf brought up another issue, and include patch from pgf. Test that audio pop during suspend/resume is gone from jnettlet.
- testing by
- Samuel Greenfeld
- 3xC1 running os23 with olpc-runin-tests-0.16.7-1 installed instead of bringup build, Q4C11, all tests (2 with EC serial), 3xC1 running with battery test disabled. Test in progress.
- 1xC1 SKU201 (#6) running aggressive (10s on/10s off) suspend failed after 15 minutes during resume, power & full battery LEDs on, all other LEDs off. All tests except the battery test were running on this unit at the time of failure. host (mmp2_pm_finish: Enable audio island ... mmp2_pm_finish: Done)
- 1xC1 SKU201 (#3) running aggressive (10s on/10s off) suspend failed at a point TBD with EC communications failure and the eMMC root filesystem remounted read-only. It continued suspend & resume testing after the failure point(s). host ec
- 3xC1 running os23 with olpc-runin-tests-0.16.7-1 installed instead of bringup build, Q4C11, all tests (2 with EC serial), 3xC1 running with battery test disabled. Test in progress.
- James Cameron
- Samuel Greenfeld
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 [2]
- 1xC1 SKU201 hung with MMC problems, pm_async disabled [3]
- 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 [4]
- 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
- purpose: no-suspend-contention runin branch
- five units run to 100 suspend cycles, 2.5 hours each, no issues.
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),