XO-4/Kernel/Testing

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.

See also:

• using runin for kernel testing

9e42d55

• stock kernel in build 26, along with Q7B11, EC 0.3.08, and runin 0.21.0,
• build 24 (with kernel rpm), Q7B11jd, EC 0.3.09, runin 0.21.1, blacklisted btmrvl_sdio and mwifiex_sdio, aggressive, in progress by James:
  • SKU293 with 8686, out of memory fail at 2940 cycles,
  • SKU295, 2487 cycles,
  • SKU292 with 8787, 2526 cycles,
  • SKU296, with watchdog, 20 cycles.

• build 24 (with kernel rpm), Q7B11jd, EC 0.3.08, runin 0.21.1, blacklisted btmrvl_sdio and mwifiex_sdio, aggressive, by James:
  • SKU296, hung at 2649 cycles, olpc-ec-1.75: transmit FIFO not empty,
  • SKU295, 3869 cycles, completed,
  • SKU292, 3633 cycles, completed,

• build 24 (with kernel rpm), Q7B11jd, EC 0.3.08, runin 0.21.1, blacklisted btmrvl_sdio, aggressive, by James:
  • SKU293 with 8686, hung at 3122 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, a B1 w. 8686 card, 10K S/R, in progress by wad.
• build 25, aggressive timing, a B1 w. 8686 card, 6000 cycles, in progress by wad.
• build 25, no-wireless and blacklisted mwifiex_sdio and btmrvl_sdio drivers, aggressive timing, (2) C1 units w. 8787 cards, all 11K+ 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
• build 25 plus EC 3.09, no_console_suspend debug and aggressive, SKU 298, 2200 S/R cycles, in progress by wad
• build 25 plus EC 3.09, aggressive timing, a B1 and a 1.2 GHz B0B w. 8686 cards, around 2200 S/R cycles each, in progress by wad.

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, aggressive timing, a B1 and a 1.2 GHz B0B w. 8686 cards, around 8K S/R cycles each, hung in resume, by wad.
• build 25, no wireless and blacklisted mwifiex/btmrvl drivers, aggressive timing, (2) C1 and a B1, 8K S/R cycles, hung (lost power due to EC bug), by wad.
• build 25, no wireless and blacklisted mwifiex/btmrvl drivers, aggressive timing, (1) B1 w. 8787, 8K S/R cycles, hung, 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