Issue metadata
Sign in to add a comment
|
[Reef] No Network connectivity (Ethernet n WiFi) |
||||||||||||||||||||||||
Issue descriptionChrome Version: <From about:version: Google Chrome 58.0.3028.0> Chrome OS Version: <From about:version: Platform 9334.0.0> Chrome OS Platform: <Reef/Snappy/Electro> Network info: <WiFi/Ethernet> Please specify Cr-* of the system to which this bug/feature applies (add the label below). How frequently does this problem reproduce? (Always, sometimes, hard to reproduce?) Always. What is the impact to the user, and is there a workaround? If so, what is it? Device unusable. Please provide any additional information below. Attach a screen shot or log if possible. 1) Cave, Caroline : (Intel SP2 wifi chip) do not see this issue. 2) Samus
,
Mar 3 2017
I see no network connectivity on OOBE /Login screen (device does not scan any wifi networks or connect to Ethernet) for Snappy and Electro DUT's 2017-03-03T18:59:11.921930+00:00 ERR wpa_supplicant[609]: Could not set interface wlan0 flags (UP): No such device 2017-03-03T18:59:11.921942+00:00 ERR wpa_supplicant[609]: nl80211: Could not set interface 'wlan0' UP 2017-03-03T18:59:11.921949+00:00 NOTICE wpa_supplicant[609]: nl80211: deinit ifname=wlan0 disabled_11b_rates=0 2017-03-03T18:59:11.922102+00:00 ERR wpa_supplicant[609]: wlan0: Failed to initialize driver interface. Snappy on 9333.0.0 looks good. I see couple of WiFi Kernel 4.0 changes from 9333.0.0 https://crosland.corp.google.com/log/9333.0.0..9334.0.0 b) Snappy in the lab is down. I have a snappy on R57 in dev cell right now but it is being used for different task right now. Will let you know when it is available.
,
Mar 3 2017
This might be a nice 100% repro case for issues I am chasing. Please give me a list of the failing DUT hostnames (chromeosX-rowY-rackZ-hsotA) for all Reef/Electro/Snappy. Please lock them down and ensure no further tests are run. I'll put debug firmware on them and run my tests over the weekend. Thanks!
,
Mar 3 2017
This particular issue was seen with manual testing. There is currently only 1 snappy in the lab which is down. Tried rebooting it using dut-control but that did not work, also tried with repair procedure without success. We'll ask the lab team in 1758 to manually boot it but there is no guarantee that it will stay up. I went to the 1758 couple days back and manually rebooted this snappy and it stayed on for few minutes and went down again. After few retries it stayed up and we were able to run wifi_matfunc test suite against it but at some point it went down again. Not sure if something is wrong with this particular device or general issue with snappy. We also have 1 pyro (another reef board) in the lab that we setup few days back but there is some issue with the router for that cell so its not running any tests yet. Lab team is looking into that as well.
,
Mar 3 2017
Since we branched at release-R58-9334.B please feel to merge the revert/fix as soon as ready.
,
Mar 4 2017
,
Mar 6 2017
Marking as duplicate since this should very likely be the same bad Intel patch issue. Please speak up if I am mistaken, close otherwise.
,
Mar 7 2017
This issue has been approved for a merge. Please merge the fix to any appropriate branches as soon as possible! If all merges have been completed, please remove any remaining Merge-Approved labels from this issue. Thanks for your time! To disable nags, add the Disable-Nags label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Mar 10 2017
This issue has been approved for a merge. Please merge the fix to any appropriate branches as soon as possible! If all merges have been completed, please remove any remaining Merge-Approved labels from this issue. Thanks for your time! To disable nags, add the Disable-Nags label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by kirtika@chromium.org
, Mar 3 2017