XO-4/Kernel/Testing: Difference between revisions
< XO-4
Jump to navigation
Jump to search
No edit summary |
|||
| (65 intermediate revisions by 3 users not shown) | |||
| Line 1: | Line 1: | ||
Final testing push default configuration for 13.2.0: |
|||
| ⚫ | |||
* fs-update 32009o4.zd with this [http://dev.laptop.org/~kernels/public_rpms/f18-xo4/kernel-3.5.7_xo4-20130614.1404.olpc.62d1459.armv7hl.rpm kernel], or |
|||
* fs-update 32010o4.zd |
|||
* change-tag TS DEVL \ enable aggressive mode with repeated runs |
|||
Debugging configuration: |
|||
* log the output of the serial console, |
|||
* olpc-dev-kernel |
|||
* no_console_suspend |
|||
See also: |
See also: |
||
*[[XO-4/Kernel/Runin|using runin for kernel testing]] |
*[[XO-4/Kernel/Runin|using runin for kernel testing]] |
||
*[http://dev.laptop.org/~kernels/public_rpms/f18-xo4/?C=M;O=D latest kernel RPMs] |
|||
Testing might be tracked below by kernel git hash. |
|||
| ⚫ | |||
<!-- |
<!-- |
||
| Line 16: | Line 29: | ||
and add after this html comment |
and add after this html comment |
||
--> |
--> |
||
== 9e42d55 == |
|||
* build 24 (with kernel rpm), Q7B11jd, EC 0.3.08, runin 0.21.1, blacklisted btmrvl_sdio and mwifiex_sdio, aggressive, in progress by James: |
|||
** SKU296, 7 cycles, |
|||
** SKU295, 3124 cycles, |
|||
** SKU292, 2834 cycles, |
|||
** SKU293, 3090 cycles. |
|||
== 6ebcabf == |
|||
''In Progress'' |
|||
*stock kernel in build 25, along w. Q7B11 and EC 0.3.08 |
|||
*build 24 (with kernel rpm), runin 0.21.1, blacklisted btmrvl_sdio only, no-wireless, aggressive, SKU296, 4849 cycles, completed, by James. |
|||
*build 25, aggressive timing, (2) B1 and a 1.2 GHz B0B w. 8686 cards, 6.5K S/R cycles each, in progress by wad. |
|||
*build 25, aggressive timing, B1 w. 8686 card, 3000 cycles, in progress by wad. |
|||
*build 25, no-wireless and blacklisted mwifiex_sdio and btmrvl_sdio drivers, aggressive timing, (7) B1 and C1 units w. 8787 cards, all 3200 cycles, in progress by wad. |
|||
* build 25, C2, with 8787 enabled, with no_console_suspend. Started 2013-01-17 00:07:25 UCT. Logging to runin-with-8787-with-n_c_s-0.log |
|||
''Failures'' |
|||
*build 25, aggressive timing, (7) B1 and C1 units w. 8787 cards, all failed within 100 S/R cycles, by wad. |
|||
*build 25, aggressive timing, (2) B1 units w. 8686 cards, hung at 1600 and 160 S/R cycles, by wad. |
|||
*build 25, sku 295, drivers blacklisted, hang on wakeup from idle suspend using keyboard --- traced to another EC wakeup issue by pgf |
|||
*build 24 (with kernel rpm), abbreviated scan, interlocked scan, aggressive timing, by James, all failed within 100 S/R cycles, |
|||
*build 24 (with kernel rpm), blacklisted btmrvl_sdio only, no-wireless, aggressive, SKU295, hang after suspend, after 3018 cycles. |
|||
*build 25, C2, with 8787 enabled, without no_console_suspend, hung at the 70th suspend cycle (last message was "Suspending console(s)...". Next try will be with no_console_suspend. Saving log file as runin-with-8787-without-n_c_s.log. by wmb. |
|||
''Success'' |
|||
*Huh ? We never declare success, only "in progress" or "failed"! |
|||
== 62abd44 == |
|||
*stock kernel in build 24, along w. Q7B11 and EC 0.3.08 |
|||
*build 24, abbreviated scan, interlocked scan, aggressive timing, test ended prematurely with iw lockup, 50 suspend cycles on SKU295, 71 suspend cycles on SKU296, |
|||
== e673868 == |
|||
*stock kernel in build 23, along w. Q7B11 and EC 0.3.08 |
|||
*build 23, abbreviated scan, interlocked scan, 4306 suspend cycles, aggressive timing, by James, passed. |
|||
*build 23, no-wireless and blacklisted mwifiex_sdio and btmrvl_sdio drivers, 14,800 suspend cycles, aggressive timing, SKU 297, by wad, passed |
|||
Latest revision as of 23:48, 14 June 2013
Final testing push default configuration for 13.2.0:
- fs-update 32009o4.zd with this kernel, or
- fs-update 32010o4.zd
- change-tag TS DEVL \ enable aggressive mode with repeated runs
Debugging configuration:
- log the output of the serial console,
- olpc-dev-kernel
- no_console_suspend
See also:
Testing might be tracked below by kernel git hash.
Kernel developers, put your new kernel in a new section here. Latest at top. Testers place links to reports indented under the kernel. Test reports should include Open Firmware and EC versions.