New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 838277 link

Starred by 2 users

Issue metadata

Status: Verified
Owner: ----
Closed: Jun 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

Squawks with a StP2 chip in the lab. Investigate chromeos4-row7-rack4-host9.cros

Project Member Reported by kirtika@google.com, Apr 30 2018

Issue description

network_WlanDriver test failed on this host. 
there is no wifi interface on it. 
lspci shows the chip is detected as a StP2, and Squawks is a WP2 device which doesn't carry the StP2 firmware. 

1. Is this device truly a Squawks?
2. Can someone open up the device and get me a picture of the wifi card on it? 
3. Any history for why a StP2 was shoved in there? (our labs only carry spare StP2 no WP2, so this mistake is possible during rework). 


 
Labels: wifi-test-failures
This device belong to the generic pool. Squawks for wifi testing is at 
chromeos2-row11-rack5-host6 and has correct chipset. 

~ $dut_info chromeos2-row11-rack5-host6
Chrome OS Version : 10666.0.0 (Official Build) dev-channel squawks test
Wireless Chip Info :        description: Wireless interface
       product: Wireless 7260


Cc: johndhong@chromium.org
We're running some very minimal Wifi tests on all machines now. We don't want to see unsupported configurations anywhere in the regular pool.

+ John, who has been helping with all our mismatched Wifi problems
Cc: englab-sys-cros@google.com
Strange...it detects what I believe is the intel wifi card but firmware broken???

localhost ~ # lspci                                                                                                                                                                                                                              
00:00.0 Host bridge: Intel Corporation Atom Processor Z36xxx/Z37xxx Series SoC Transaction Register (rev 0e)
00:02.0 VGA compatible controller: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display (rev 0e)
00:14.0 USB controller: Intel Corporation Atom Processor Z36xxx/Z37xxx Series USB xHCI (rev 0e)
00:1a.0 Encryption controller: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Trusted Execution Engine (rev 0e)
00:1b.0 Audio device: Intel Corporation Atom Processor Z36xxx/Z37xxx Series High Definition Audio Controller (rev 0e)
00:1c.0 PCI bridge: Intel Corporation Atom Processor E3800 Series PCI Express Root Port 1 (rev 0e)
00:1f.0 ISA bridge: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Power Control Unit (rev 0e)
01:00.0 Network controller: Intel Corporation Wireless 7265 (rev 59)

localhost ~ # lsmod                                                                                                                                                                                                                              
....
iwlwifi               253952  0


localhost ~ # lshw -C network                                                                                                                                                                                                                    
  *-network UNCLAIMED     
       description: Network controller
       product: Wireless 7265
       vendor: Intel Corporation
       physical id: 0
       bus info: pci@0000:01:00.0
       version: 59
       width: 64 bits
       clock: 33MHz
       capabilities: pm msi pciexpress cap_list
       configuration: latency=0
       resources: memory:d0800000-d0801fff


2018-05-11T10:18:02.703051+00:00 INFO kernel: [   25.787205] Intel(R) Wireless WiFi driver for Linux
2018-05-11T10:18:02.703074+00:00 INFO kernel: [   25.787214] Copyright(c) 2003- 2015 Intel Corporation
2018-05-11T10:18:02.723711+00:00 WARNING kernel: [   25.807053] iwlwifi 0000:01:00.0: Direct firmware load for iwl-dbg-cfg.ini failed with error -2
2018-05-11T10:18:02.723735+00:00 WARNING kernel: [   25.807124] iwlwifi 0000:01:00.0: Direct firmware load for iwlwifi-7265D-29.ucode failed with error -2
2018-05-11T10:18:02.723738+00:00 ERR kernel: [   25.807132] iwlwifi 0000:01:00.0: no suitable firmware found!
2018-05-11T10:18:02.723741+00:00 ERR kernel: [   25.807137] iwlwifi 0000:01:00.0: minimum version required: iwlwifi-7265D-22
2018-05-11T10:18:02.723743+00:00 ERR kernel: [   25.807142] iwlwifi 0000:01:00.0: maximum version supported: iwlwifi-7265D-29
2018-05-11T10:18:02.723745+00:00 ERR kernel: [   25.807146] iwlwifi 0000:01:00.0: check git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git


Cc: dschimmels@chromium.org jashur@chromium.org
chromeos2-row11-rack5-host6 is in a wifi cell and not directly under the management of englab-sys-cros so not sure if what is there intentional.

Comment 7 by kirtika@google.com, May 11 2018

The point is that this is an older device (BYT family) which should WP2 wifi chip (wilkins peak), which is 7260 not 7265.
It currently has 7265 (StP2 / Stone Peak2) which was introduced only starting BSW.
We are running basic wifi tests on all DUTs in the lab (bvt-perbuild and bvt-cq) and do not wish to see unsupported wifi configurations anywhere. 
Please get this machine out of this pool. Its unlikely we have spare WP2 cards to swap out this one with, but if we do, swapping out the StP2 in here for a WP2 is an acceptable fix for this bug. 
Looking at a different squawks it should be an intel 7260 (if I'm understanding go/CrConn) and not a 7265

localhost ~ # lshw -C network   
  *-network               
       description: Wireless interface
       product: Wireless 7260
       vendor: Intel Corporation
       physical id: 0
       bus info: pci@0000:01:00.0
       logical name: wlan0
       version: 6b
       serial: e8:2a:ea:34:29:43
       width: 64 bits
       clock: 33MHz
       capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless
       configuration: broadcast=yes driver=iwlwifi driverversion=4.4.127-13888-g4190cb01e593 firmware=17.388f111f.0 latency=0 link=no multicast=yes wireless=IEEE 802.11abgn
       resources: irq:265 memory:d0800000-d0801fff

Based off some other work I believe that is the only squawks DUT that is this way as the rest load the intel driver just fine.

Even other DUTs with the same HWID work so that cannot be used to differentiate...

chromeos4-row7-rack4-host9
SQUAWKS D7A-D2G-A5Z

chromeos6-row2-rack12-host12
SQUAWKS D7A-D2G-A5Z

johndhong@phobrz:~$ ssh chromeos6-row2-rack12-host12
Warning: Permanently added 'chromeos6-row2-rack12-host12,100.115.129.130' (ED25519) to the list of known hosts.
localhost ~ # lshw -C network
  *-network               
       description: Wireless interface
       product: Wireless 7260
       vendor: Intel Corporation
       physical id: 0
       bus info: pci@0000:01:00.0
       logical name: wlan0
       version: 6b
       serial: e8:2a:ea:33:dd:7b
       width: 64 bits
       clock: 33MHz
       capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless
       configuration: broadcast=yes driver=iwlwifi driverversion=4.4.131-14084-gcd9adea7ce8e firmware=17.388f111f.0 latency=0 link=no multicast=yes wireless=IEEE 802.11abgn
       resources: irq:265 memory:d0800000-d0801fff

chromeos2-row11-rack5-host6  DUT is fine. chromeos4-row7-rack4-host9 maintained by englab-sys-cros has incorrect wifi chipset. Sorry If my comment#3 caused  confusion. 
Filed https://b.corp.google.com/issues/79605193 to replace the DUT
chromeos4-row7-rack4-host9 is labeled as a PVT device.  How did it end
up with a non-factory configuration?

Unknown... In discussions with crosdistors I can loop you in if you like...
> Unknown... In discussions with crosdistors I can loop you in if you like...

I'll settle for a summary of the conclusions here, once it's sorted.

To note here (while we're trying to investigate more): I verified that all lab devices with label board:squawks (locked or unlocked) have this in `lspci -n -d '8086::0280'`:

01:00.0 0280: 8086:08b1 (rev 6b)

IIUC, that is the correct ID.

Caveats: there was one (locked) device which a technician is currently testing with a different DUT; I also could not currently reach the following:

chromeos1-row3-rack1-host2
chromeos4-row7-rack4-host11
chromeos4-row7-rack4-host17
chromeos4-row7-rack4-host9
chromeos4-row7-rack5-host9
chromeos6-row2-rack12-host18
chromeos6-row2-rack12-host4
chromeos6-row2-rack12-host5
chromeos6-row2-rack12-host6

Several were currently repairing, but some are "ready" yet un-pingable.

If someone needs the answer to "are there any more devices in the lab like this", they'll need to check the above lspci commands on the above list of devices.

Comment 16 by afaris@google.com, May 22 2018

To summarize the work done in http://b/80089040, I've brought back up everything (they are pingable) except for

chromeos4-row7-rack4-host9

from my list (Not chromeos1). I also ran the lspci -n -d '8086::0280' command for each, which yielded

01:00.0 0280: 8086:08b1 (rev 6b)

chromeos4-row7-rack4-host9 was not on the shelf when I checked.

 
Status: Fixed (was: Untriaged)
DUT has been replaced!
https://buganizer.corp.google.com/issues/79605193#comment9

07:56 dpapp@dpapp-glaptop:~$ ssh chromeos4-row7-rack4-host9
localhost ~ # lspci -n -d '8086::0280'
01:00.0 0280: 8086:08b1 (rev 6b)

Thanks dpapp!
Status: Verified (was: Fixed)
The devices under wificell label have the correct id and chipset. 
Id : 01:00.0 0280: 8086:08b1 (rev 6b) and chipset product: Wireless 7260
Also, the bad dut is replaced #17. 

Sign in to add a comment