Logs are present at https://pantheon.corp.google.com/storage/browser/chromiumos-test-logs/bugfiles/cros/838321/?debugUI=CLOUD

In stainless, we see no results for tricky starting  R67-10575.9.0 

https://stainless.corp.google.com/search?view=matrix&row=test&col=build&first_date=2018-04-17&last_date=2018-04-30&suite=bvt*&build=R67-*&board=tricky&status=GOOD&status=WARN&status=FAIL&status=ERROR&status=ABORT&status=ALERT&status=RUNNING&status=TEST_NA&status=NOSTATUS&status=NOT_RUN&exclude_cts=true&exclude_not_run=false&exclude_non_release=true&exclude_au=true&exclude_acts=true&exclude_retried=true&exclude_non_production=true

wlwifi: Merge Core35 driver updates got added to  R67-10575.9.0 .

@kirtika: Can you check if any of those changes caused this regression?
Same for falco_li device

The missing stainless result is due to some infra migration and they are working on it.

Also is this only apply to Tricky (beltino family) ?

This issue is specific to Tricky device.
Not able to reproduce this issue on Panther.


Note: This issue looks like regression from R67-10575.9.0.
All Paygen AU tests started failing from this build with "Connection timed out" error message.
https://screenshot.googleplex.com/AZHbuqET5HM

Logs show shill crashing endlessly, and `lsmod` output has no cfg80211 or iwlwifi. 
Definitely a Core35 merge issue, am looking into what CL this build is missing.

@sontis: Can you please check falco_li too? tricky and falco_li are the two "exception" case devices on 3.8 with Intel wifi. 

Facing same issue with falco_li on 10575.22.0/ 67.0.3396.26 build.

My best guess is that R67 is missing these CLs which are in master (where tricky and falco_li  work fine): 
https://chromium-review.googlesource.com/c/chromiumos/overlays/chromiumos-overlay/+/1017804
https://chromium-review.googlesource.com/c/chromiumos/overlays/board-overlays/+/1017803
https://chrome-internal-review.googlesource.com/c/chromeos/overlays/overlay-variant-falco-li-private/+/610818

For CL:1017804 
I explicitly let it go think it was not critical - it was only removing a vestigial flag. However, I now realize that it injects "# CONFIG_CFG80211 is not set" and depending on the order in which that line and "CONFIG_CFG80211=m" are processed, that line may disable all wifi modules. 

That's my best guess, but it still doesn't make sense, since building R67 kernel locally for tricky shows me that cfg80211.ko and iwlwifi.ko are installed in the rootfs. 

Re #c10: That is the correct guess. 
Added: 
https://chromium-review.googlesource.com/c/chromiumos/overlays/chromiumos-overlay/+/1017804
https://chromium-review.googlesource.com/c/chromiumos/overlays/board-overlays/+/1017803
https://chrome-internal-review.googlesource.com/c/chromeos/overlays/overlay-variant-falco-li-private/+/610818/

Please retest after these 3 CLs have landed. 

Ping on updates since RBB for these two boards?

Not able to reproduce  this issue on M67_10575.30.0_tricky build.

Stainless results look good. Also as per #14. Closing this as verified. 

https://stainless.corp.google.com/search?view=matrix&row=test&col=build&first_date=2018-05-01&last_date=2018-05-07&suite=bvt*&board=falco_li%7C+tricky&status=GOOD&status=WARN&status=FAIL&status=ERROR&status=ABORT&status=ALERT&status=RUNNING&status=TEST_NA&status=NOSTATUS&status=NOT_RUN&exclude_cts=true&exclude_not_run=false&exclude_non_release=true&exclude_au=true&exclude_acts=true&exclude_retried=true&exclude_non_production=true

[Auto-generated comment by a script] We noticed that this issue is targeted for M-67; it appears the fix may have landed after branch point, meaning a merge might be required. Please confirm if a merge is required here - if so add Merge-Request-67 label, otherwise remove Merge-TBD label. Thanks.

IIUC, the relevant stuff was tagged (and merged) to b/76340244

Thanks, though I don't believe the merge was done yet.

See comments in the bug.  Thanks!