Issue metadata
Sign in to add a comment
|
Cannot connect to WiFi on latest ToT R61-9620.0.0 |
||||||||||||||||||||||
Issue descriptionChrome Version: <From about:version: Google Chrome 61.0.3119.0> Chrome OS Version: <From about:version: Platform 9620.0.0> Chrome OS Platform: <Multiple Boards Reks, Kevin, Paine> Network info: <WiFi> Please specify Cr-* of the system to which this bug/feature applies (add the label below). Cannot connect to any wireless network in the network list. Reks on 9612.0.0 is working as expected. Diff between 9612.0.0 and 9620.0.0 https://crosland.corp.google.com/log/9612.0.0..9620.0.0 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? Cannot connect to a wireless network. Workaround: Ethernet. Please provide any additional information below. Attach a screen shot or log if possible. logs attached.
,
Jun 5 2017
Looking into it now. Also reported on eve.
,
Jun 5 2017
Get stuck on OOBE Network Screen.Could not proceed with any WiFi network. Ethernet works. Seen same issue on Daisy,Paine,Reks devices in latest M61. M ChromeOS Chrome ARC Type Channel 61 9620.0.0 61.0.3119.0 (multiple) release dev
,
Jun 5 2017
The supplicant crash is related to issue 729259 , which we re-enabled SetH40Enable (which was accidentally turned into a no-op by https://android-review.googlesource.com/#/c/174019/). However, it seems like something has changed in supplicant (or shill) that it now causes a crash in supplicant if we actually invokes it. Thread 0 (crashed) 0 libc-2.23.so!strlen + 0x26 rax = 0x0000000000000000 rdx = 0x0000000000000000 rcx = 0x0000000000000000 rbx = 0x00005d6919ab2150 rsi = 0x000000000000002f rdi = 0x0000000000000000 rbp = 0x00007fff6d2b51a0 rsp = 0x00007fff6d2b5168 r8 = 0x6e6163696c707075 r9 = 0x7265746e492f3174 r10 = 0x2f312f7365636166 r11 = 0x0000000000000000 r12 = 0x00005d6919ab2174 r13 = 0x00005d6919a7deb0 r14 = 0x00007fff6d2b51c0 r15 = 0x0000000000000000 rip = 0x00007ddfbdaadb26 Found by: given as instruction pointer in context 1 wpa_supplicant!wpas_dbus_new_decompose_object_path [dbus_new_helpers.c : 986 + 0x8] rbx = 0x00005d6919ab2150 rbp = 0x00007fff6d2b51a0 rsp = 0x00007fff6d2b5170 r12 = 0x00005d6919ab2174 r13 = 0x00005d6919a7deb0 r14 = 0x00007fff6d2b51c0 r15 = 0x0000000000000000 rip = 0x00005d6917a95b27 Found by: call frame info 2 wpa_supplicant!wpas_dbus_handler_set_ht40_enable [dbus_new_handlers.c : 2134 + 0x7] rbx = 0x00000000000000ff rbp = 0x00007fff6d2b5210 rsp = 0x00007fff6d2b51b0 r12 = 0x00005d6919a7deb0 r13 = 0x00005d6919a7deb0 r14 = 0x00007fff6d2b52f2 r15 = 0x00005d6919a826e0 rip = 0x00005d6917a9ab79 Found by: call frame info 3 wpa_supplicant!message_handler [dbus_new_helpers.c : 354 + 0x7] rbx = 0x00000000000000ff rbp = 0x00007fff6d2b5420 rsp = 0x00007fff6d2b5220 r12 = 0x00005d6919a7deb0 r13 = 0x00005d6917b11778 r14 = 0x00007fff6d2b52f2 r15 = 0x00005d6917b11790 rip = 0x00005d6917a94da2 Found by: call frame info 4 libdbus-1.so.3.14.8 + 0x2866a rbx = 0x0000000000000000 rbp = 0x00007fff6d2b5500 rsp = 0x00007fff6d2b5430 r12 = 0x00005d6919aa13c0 r13 = 0x00005d6917a94920 r14 = 0x0000000000000000 r15 = 0x00005d6919a7d670 rip = 0x00007ddfbe31b66a Found by: call frame info 5 libdbus-1.so.3.14.8 + 0x170f6 rbp = 0x00007fff6d2b55b0 rsp = 0x00007fff6d2b5510 rip = 0x00007ddfbe30a0f6 Found by: previous frame's frame pointer 6 wpa_supplicant!process_watch [dbus_common.c : 38 + 0x8] rbp = 0x00007fff6d2b55e0 rsp = 0x00007fff6d2b55c0 rip = 0x00005d6917a9f908 Found by: previous frame's frame pointer 7 wpa_supplicant!eloop_run [eloop.c : 495 + 0x4] rbx = 0x0000000000000000 rbp = 0x00007fff6d2b5660 rsp = 0x00007fff6d2b55f0 r14 = 0x00005d6917b15850 r15 = 0x0000000000000004 rip = 0x00005d6917a4830a Found by: call frame info 8 wpa_supplicant!wpa_supplicant_run [wpa_supplicant.c : 5033 + 0x5] rbx = 0x0000000000000001 rbp = 0x00007fff6d2b5690 rsp = 0x00007fff6d2b5670 r12 = 0x00005d6919a7c480 r13 = 0x00005d6919a7c480 r14 = 0x0000000000000001 r15 = 0x00005d6919a7ca90 rip = 0x00005d6917ab187f Found by: call frame info 9 wpa_supplicant!main [main.c : 345 + 0x8] rbx = 0x0000000000000001 rbp = 0x00007fff6d2b5780 rsp = 0x00007fff6d2b56a0 r12 = 0x00005d6919a7c480 r13 = 0x00005d6919a7c480 r14 = 0x0000000000000001 r15 = 0x00005d6919a7ca90 rip = 0x00005d6917abdd5d Found by: call frame info 10 libc-2.23.so!__libc_start_main [libc-start.c : 289 + 0x1a] rbx = 0x0000000000000000 rbp = 0x00007fff6d2b5850 rsp = 0x00007fff6d2b5790 r12 = 0x00005d6917add760 r13 = 0x00007fff6d2b5870 r14 = 0x0000000000000000 r15 = 0x0000000000000000 rip = 0x00007ddfbda48816 Found by: call frame info 11 wpa_supplicant!_start + 0x29 rbx = 0x0000000000000000 rbp = 0x0000000000000000 rsp = 0x00007fff6d2b5860 r12 = 0x00005d6917a38b80 r13 = 0x00007fff6d2b5870 r14 = 0x0000000000000000 r15 = 0x0000000000000000 rip = 0x00005d6917a38ba9 Found by: call frame info 12 0x7fff6d2b5868 rbx = 0x0000000000000000 rbp = 0x0000000000000000 rsp = 0x00007fff6d2b5868 r12 = 0x00005d6917a38b80 r13 = 0x00007fff6d2b5870 r14 = 0x0000000000000000 r15 = 0x0000000000000000 rip = 0x00007fff6d2b5868 Found by: call frame info 13 0x7fff6d33e000 rsp = 0x00007fff6d2b5910 rip = 0x00007fff6d33e000 Found by: stack scanning 14 wpa_supplicant!_init + 0x1c08 rsp = 0x00007fff6d2b59a0 rip = 0x00005d6917a38b80 Found by: stack scanning
,
Jun 5 2017
Looks like the supplicant code has been broken for a while, but the crash hasn't been observed as the affected code path was accidentally turned into a no-op. Here's a potential fix: https://chromium-review.googlesource.com/c/524295/
,
Jun 5 2017
Unable to connect to WiFi on OOBE screen on Chell with version 61.0.3119.0/9620.0.0
,
Jun 6 2017
,
Jun 6 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromiumos/third_party/hostap/+/a07f7158fe3af528a2cd2c3fcf9c1011bcd0c09e commit a07f7158fe3af528a2cd2c3fcf9c1011bcd0c09e Author: Ben Chan <benchan@chromium.org> Date: Tue Jun 06 01:33:59 2017 CHROMIUM: Fix network ID extraction is SetHT40Enable method Commit dc4609236 ("CHROMIUMOS: Add support for user configurable HT40 setting") introduced a Chromium OS specific SetHT40Enable method for user configurable HT40 setting. However, the code in wpas_dbus_handler_set_ht40_enable has been broken since commit 054dc3136 ("D-Bus: Clean up wpas_dbus_new_decompose_object_path()") where wpas_dbus_new_decompose_object_path() was changed to a different function signature. wpas_dbus_handler_set_ht40_enable() wasn't updated accordingly, which results in a crash when wpas_dbus_new_decompose_object_path() is invoked incorrectly. BUG= chromium:729693 TEST=Verify that supplicant no longer crashes when shill invokes the SetHT40Enable method. Change-Id: I6ed7b572bee233a65cd19aa31380a0ce0fbf245c Reviewed-on: https://chromium-review.googlesource.com/524295 Commit-Ready: Kirtika Ruchandani <kirtika@chromium.org> Tested-by: Kirtika Ruchandani <kirtika@chromium.org> Reviewed-by: Kevin Cernekee <cernekee@chromium.org> [modify] https://crrev.com/a07f7158fe3af528a2cd2c3fcf9c1011bcd0c09e/wpa_supplicant/dbus/dbus_new_handlers.c
,
Jun 6 2017
,
Jun 6 2017
Issue 729528 has been merged into this issue.
,
Jul 25 2017
Verified with version 9765.5.0, 61.0.3163.11
,
Sep 20 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromiumos/third_party/hostap/+/94fb79396b9f28347691d772060f16b64058679c commit 94fb79396b9f28347691d772060f16b64058679c Author: Peter Qiu <zqiu@chromium.org> Date: Wed Sep 20 22:35:01 2017 CHROMIUMOS: Add support for user configurable HT40 setting Add a DBUS command to enable/disable HT40 for a network. Also do not perform OBSS scan if HT40 is disabled on the given network. This also amends commit a07f7158fe3af528a2cd2c3fcf9c1011bcd0c09e which fixes a bug in the dbus object path handling. BUG= chromium:419046 , chromium:729693 TEST=emerge-peppy wpa_supplicant Change-Id: Idca3a80aa6ca94d4765e26c7084f9c80efe3f87d Original-reviewed-on: https://chromium-review.googlesource.com/220651 Original-reviewed-by: Paul Stewart <pstew@chromium.org> Original-tested-by: Peter Qiu <zqiu@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/669516 Tested-by: Eric Caruso <ejcaruso@chromium.org> Reviewed-by: Kevin Cernekee <cernekee@chromium.org> [modify] https://crrev.com/94fb79396b9f28347691d772060f16b64058679c/wpa_supplicant/dbus/dbus_new_handlers.h [modify] https://crrev.com/94fb79396b9f28347691d772060f16b64058679c/wpa_supplicant/sme.c [modify] https://crrev.com/94fb79396b9f28347691d772060f16b64058679c/wpa_supplicant/dbus/dbus_new.c [modify] https://crrev.com/94fb79396b9f28347691d772060f16b64058679c/wpa_supplicant/dbus/dbus_new_handlers.c |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by agonzale...@gmail.com
, Jun 5 2017