I believe my wireless card has been disabled.
Reported by
rosensteinkevin@gmail.com,
Jul 28 2017
|
||||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; CrOS x86_64 9460.60.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/59.0.3071.91 Safari/537.36 Platform: 9460.60.0 (Official Build) stable-channel celes Steps to reproduce the problem: 1. Powerwash Chromebook with wifi-disabled 2. Log into chromebook and try to turn on wifi 3. Wifi will not turn on and move back and forth like a game of ping-pong What is the expected behavior? SUMMARY Test Name: ChromeOS Internet Disconnected Test Test ID: 0 Test result: Problem detected CRITERIA A no problem result is returned when the connected network interface returns a connected status code A problem result is returned when the connected network interface returns a disconnected status code: Doesn't give me a status code ??! DETAILS Fri Jul 28 2017 00:17:32 GMT-0400 (EDT) - Number of available networks detected: 0 What went wrong? Can't get my wireless internet to work. Oh and my Bluetooth doesn't work either but I rather have that fixed later. Chromebook I have is samsung 3 chromebook. I do have a USB adapter for eithernet, as the chromebook does not come with a built-in lan, so that is the only way I can use the internet. Did this work before? N/A Chrome version: 59.0.3071.91 Channel: stable OS Version: 9460.60.0 Flash Version: Shockwave Flash 26.0 r0 If anyone has a debugging suggestions that would be great.
,
Jul 28 2017
,
Jul 28 2017
From feedback report 69315194195: [ 11.290322] Intel(R) Wireless WiFi driver for Linux [ 11.290338] Copyright(c) 2003- 2015 Intel Corporation [ 11.300993] iwlwifi 0000:02:00.0: irq 314 for MSI/MSI-X [ 11.322851] iwlwifi 0000:02:00.0: Direct firmware load for iwl-dbg-cfg.ini failed with error -2 [ 11.323219] platform vpd: Driver vpd requests probe deferral [ 11.343645] iwlwifi 0000:02:00.0: capa flags index 3 larger than supported by driver [ 11.344656] iwlwifi 0000:02:00.0: loaded firmware version 27.518394.0 op_mode iwlmvm [ 11.397279] iwlwifi 0000:02:00.0: Detected Intel(R) Dual Band Wireless AC 7265, REV=0x210 [ 11.404371] iwlwifi 0000:02:00.0: L1 Enabled - LTR Disabled [...] [ 11.778517] iwlwifi 0000:02:00.0: L1 Enabled - LTR Disabled [ 11.877137] cdc_ether 2-1:2.0 eth0: kevent 11 may have been dropped [ 11.903854] ------------[ cut here ]------------ [ 11.903854] WARNING: CPU: 1 PID: 1786 at /mnt/host/source/src/third_party/kernel/v3.18/drivers/net/wireless/iwl7000/iwlwifi/pcie/trans.c:2043 iwl_trans_pcie_reclaim+0xbce/0x33d9 [iwlwifi]() [ 11.903854] Timeout waiting for hardware access (CSR_GP_CNTRL 0x080003dc) [ 11.903854] Modules linked in: snd_soc_sst_cht_bsw_rt5645 iwlmvm(+) memconsole_x86_legacy memconsole iwlwifi snd_hda_codec_hdmi iwl7000_mac80211 snd_hda_intel snd_hda_codec snd_hwdep snd_hda_core snd_intel_sst_acpi snd_soc_sst_acpi snd_intel_sst_core snd_soc_sst_mfld_platform snd_soc_rt5645 snd_soc_rl6231 ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat bluetooth zram xt_mark bridge fuse stp llc cdc_ether usbnet mii cfg80211 ip6table_filter snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device joydev uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_core [ 11.903854] CPU: 1 PID: 1786 Comm: modprobe Tainted: G W 3.18.0-14597-g61c88fee5b70 #1 [ 11.903854] Hardware name: GOOGLE Celes, BIOS Google_Celes.7287.92.74 01/19/2017 [ 11.903854] 0000000000000000 000000001595c607 ffff880067c73988 ffffffffa3c9bb40 [ 11.903854] 0000000000000000 ffff880067c739e0 ffff880067c739c8 ffffffffa3663a1a [ 11.903854] ffff880067c739a8 ffffffffc05be5c8 ffff880068b30028 0000000000000000 [ 11.903854] Call Trace: [ 11.903854] [<ffffffffa3c9bb40>] dump_stack+0x4e/0x71 [ 11.903854] [<ffffffffa3663a1a>] warn_slowpath_common+0x81/0x9b [ 11.903854] [<ffffffffc05be5c8>] ? iwl_trans_pcie_reclaim+0xbce/0x33d9 [iwlwifi] [ 11.903854] [<ffffffffa3663a89>] warn_slowpath_fmt+0x55/0x6b [ 11.903854] [<ffffffffc05b0283>] ? iwl_read32+0x1f/0x6e [iwlwifi] [ 11.903854] [<ffffffffc05be5c8>] iwl_trans_pcie_reclaim+0xbce/0x33d9 [iwlwifi] [ 11.903854] [<ffffffffc05b0807>] iwl_set_bits_mask_prph+0x3c/0x89 [iwlwifi] [ 11.903854] [<ffffffffc05beacb>] iwl_trans_pcie_reclaim+0x10d1/0x33d9 [iwlwifi] [ 11.903854] [<ffffffffc05c10e7>] iwl_trans_pcie_rf_kill+0x314/0x904 [iwlwifi] [ 11.903854] [<ffffffffc05e1ad1>] iwl_free_fw_paging+0x2a9/0xa5a [iwlmvm] [ 11.903854] [<ffffffffc05e102b>] ? init_module+0x4e02b/0x4e828 [iwlmvm] [ 11.903854] [<ffffffffc05e2318>] iwl_run_init_mvm_ucode+0x96/0x2b2 [iwlmvm] [ 11.903854] [<ffffffffc05e157a>] ? init_module+0x4e57a/0x4e828 [iwlmvm] [ 11.903854] [<ffffffffc05eb579>] iwl_mvm_enter_d0i3+0xde9/0xfff [iwlmvm] [ 11.903854] [<ffffffffc05b1166>] iwl_opmode_deregister+0x309/0x334 [iwlwifi] [ 11.903854] [<ffffffffa3c9f06c>] ? mutex_lock+0x21/0x3f [ 11.903854] [<ffffffffc05b13c5>] iwl_opmode_register+0x8f/0x1729 [iwlwifi] [ 11.903854] [<ffffffffc0593036>] init_module+0x36/0x1000 [iwlmvm] [ 11.903854] [<ffffffffc0593000>] ? 0xffffffffc0593000 [ 11.903854] [<ffffffffa36003b5>] do_one_initcall+0x188/0x19d [ 11.903854] [<ffffffffa373d235>] ? __vunmap+0xac/0xb7 [ 11.903854] [<ffffffffa36c5cff>] load_module+0x1608/0x1ba9 [ 11.903854] [<ffffffffa36c6421>] SyS_finit_module+0x86/0xab [ 11.903854] [<ffffffffa3ca0c5c>] system_call_fastpath+0x1c/0x21 [ 11.903854] ---[ end trace fe461817d1f58ad2 ]--- [ 14.525957] iwlwifi 0000:02:00.0: Could not load the [0] uCode section [ 14.527828] iwlwifi 0000:02:00.0: Failed to start INIT ucode: -5 [ 14.536452] iwlwifi 0000:02:00.0: Failed to run INIT ucode: -5 [ 14.536841] iwlwifi 0000:02:00.0: L1 Enabled - LTR Disabled This looks like a hardware failure to me. The wifi kernel driver is not even able to initialize the hardware at boot time. (We already have a "hardware problem detected" dialog that pops up when the GBB HWID doesn't match the image. Maybe it would be helpful if this also complained if a network interface or a /dev node is missing? It would be an easier way to diagnose these sorts of failures than reading the logs.)
,
Jul 28 2017
,
Jul 28 2017
FWIW I searched around for a similar backtrace, and it looks like http://b/35587526 most closely resembles this one.
,
Jul 28 2017
+ Rajat to correct me. Re: #c5, per Rajat, these two should be different issues: in this bug, CSR_GP_CNTRL is reading a valid value: 0x080003dc, so I dont know if we can conclude that the issue is pcie. in http://b/35587526 CSR_GP_CNTRL is read as 0xffffffff, which is a sign that we've lost communication with the registers in pcie config space.
,
Jul 28 2017
#6 is correct. They seem to be different issues to me.
,
Jul 30
Issue has not been modified or commented on in the last 365 days, please re-open or file a new bug if this is still an issue. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by afakhry@chromium.org
, Jul 28 2017Components: -UI Internals>Network>Connectivity OS>Systems>Network
Labels: -Pri-2 Pri-1