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

Issue 714324 link

Starred by 7 users

Issue metadata

Status: Archived
Owner:
Last visit > 30 days ago
Closed: Dec 13
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug-Regression


Show other hotlists

Hotlists containing this issue:
Chrome-Bug-Cleanup


Sign in to add a comment

Intel wifi disconnect on tricky with public sessions

Project Member Reported by marchuk@chromium.org, Apr 21 2017

Issue description

Chrome Version: (copy from chrome://version)
Google Chrome Version	
57.0.2987.146
Platform Version	
9202.64.0 (Official Build) stable-channel tricky
Firmware Version	
Google_Tricky.5829.18.0

What steps will reproduce the problem?
(1)Enable public sessions on tricky, connect to wifi
(2)Open browser in public session

What is the expected result?
Continue browsing

What happens instead?
Wifi disconnects

Have following in messages:

017-04-04T23:27:23.058629-07:00 INFO kernel: [401786.113420] pcieport 0000:00:1c.1: AER: Multiple Corrected error received: id=00e1
2017-04-04T23:27:23.058632-07:00 WARNING kernel: [401786.113438] pcieport 0000:00:1c.1: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e1(Receiver ID)
2017-04-04T23:27:23.058634-07:00 WARNING kernel: [401786.113450] pcieport 0000:00:1c.1:   device [8086:9c16] error status/mask=00000001/00002000
2017-04-04T23:27:23.058636-07:00 WARNING kernel: [401786.113461] pcieport 0000:00:1c.1:    [ 0] Receiver Error        
2017-04-04T23:27:23.058638-07:00 INFO kernel: [401786.113473] pcieport 0000:00:1c.1: AER: Corrected error received: id=00e1
2017-04-04T23:27:23.058639-07:00 DEBUG kernel: [401786.113488] pcieport 0000:00:1c.1: can't find device of ID00e1
2017-04-04T23:27:23.061549-07:00 INFO kernel: [401786.114644] pcieport 0000:00:1c.1: AER: Corrected error received: id=00e1
2017-04-04T23:27:23.061553-07:00 WARNING kernel: [401786.114659] pcieport 0000:00:1c.1: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e1(Receiver ID)
2017-04-04T23:27:23.061555-07:00 WARNING kernel: [401786.114671] pcieport 0000:00:1c.1:   device [8086:9c16] error status/mask=00000001/00002000
2017-04-04T23:27:23.061557-07:00 WARNING kernel: [401786.114682] pcieport 0000:00:1c.1:    [ 0] Receiver Error        
2017-04-04T23:27:23.061559-07:00 INFO kernel: [401786.115246] pcieport 0000:00:1c.1: AER: Multiple Corrected error received: id=00e1
2017-04-04T23:27:23.061561-07:00 WARNING kernel: [401786.115264] pcieport 0000:00:1c.1: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e1(Receiver ID)
2017-04-04T23:27:23.061563-07:00 WARNING kernel: [401786.115276] pcieport 0000:00:1c.1:   device [8086:9c16] error status/mask=00000001/00002000
2017-04-04T23:27:23.061565-07:00 WARNING kernel: [401786.115286] pcieport 0000:00:1c.1:    [ 0] Receiver Error        
2017-04-04T23:27:23.061566-07:00 ERR kernel: [401786.115567] iwlwifi 0000:02:00.0: Hardware error detected.  Restarting.


Not able to reproduce in QD6 so far, but have customer with many devices affected.
 
F2X6B62 - debug-logs_20170405-125831.tgz
2.1 MB Download
Description: Show this description

Comment 2 by mventura@google.com, May 11 2017

Hello team, has there been any progress on this bug? This issue has also been reproduced on version 58. 
Cc: bhthompson@google.com
Labels: Hotlist-Enterprise
Owner: bhthompson@chromium.org
Hi Bernie, can you please help to triage/assign?
Components: -Content>Core OS>Systems>Network
Owner: kirtika@chromium.org
Kirtika, is this something you have come across before?

I see this in a few partner bugs over the years, is this something we should pass to intel-wifi-cros@intel.corp-partner.google.com ?

Comment 5 by leonelf@google.com, May 23 2017

Hello team, Is there any update about this bug? The issue is still reproducible. 

Labels: M-58
Hi Bernie, Kirtika, should we add intel in cc? or maybe raise a b?
Cc: sduraisamy@chromium.org vidster@chromium.org
Labels: -Type-Bug Type-Bug-Regression

Comment 8 by leonelf@google.com, Jun 7 2017

Hello team, do you have any update about this issue?
Components: UI>Shell>PublicAccounts
Status: Assigned (was: Untriaged)
Hello!
This bug is receiving this notice because there has been no acknowledgment of its existence in quite a bit of time
- If you are currently working on this bug, please provide an update.
- If you are currently affected by this bug, please update with your current symptoms and relevant logs.

If there has been no updates provided by EOD Wednesday, 12/12/18 (5pm EST), this bug will be archived and can be re-opened at any time deemed necessary.

Thank you!
Status: Archived (was: Assigned)
Due to lack of action this bug has been Archived. If work is still being done on this issue or you are still experiencing this issue please feel free to re-open with the appropriate information.

Sign in to add a comment