Issue metadata
Sign in to add a comment
|
Multiple crashes when connected to some access point |
||||||||||||||||||||||
Issue descriptionChrome Version: 60.0.3112.114 OS: ChromeOs HW: ASUS Chromebook C202SA (terra) What steps will reproduce the problem? (1) update to 60.0.3112.114 from 59.0.3071.91 (2) Sign in to the device. (3) move around in the buildings What is the expected result? not to crash & reboot What happens instead? crash & reboot customer video: https://drive.google.com/open?id=0B01ZVp8vDQocVGpPOUNCVTZLUFU Customer Info: https://drive.google.com/open?id=17jNEelHbI9loEx7kljc9Z3nsaR8SUZGWS0MnEKVwqY4 debug logs 1 ChromeBook: https://drive.google.com/open?id=0B01ZVp8vDQocWFc0emFBM2V1bUE policy 1 ChromeBook (nothing about network) : https://drive.google.com/open?id=0B01ZVp8vDQocYXRwREhYRnk1RlE debug logs 2 ChromeBook: https://drive.google.com/open?id=0B01ZVp8vDQocR0hfUDI4OWx0Tzg policy 2 ChromeBook (nothing about network) : https://drive.google.com/open?id=0B01ZVp8vDQocUENlRmRqQ2tEb28 Crashes: 9dedeb8f34f452e0 null_pointer 6ca917fe7c593d8c null_pointer a60ab448628275af null_pointer the issue is connecting to Cisco Aironet AP 2800 (AIR-AP2802IE-K9)
,
Oct 6 2017
,
Oct 6 2017
Same issue reproduces customer Reks devices, M59 and M60, IWL 7265 crashes system, crash ID 4611b905b1cd4d07. Logs look similar, I could attach if needed.
,
Oct 9 2017
I checked again the log and it was happening also on 9460.60.0 59.0.3071.91
,
Oct 10 2017
,
Oct 11 2017
If my Chromebook devices are connecting at 802.11ac with a channel width higher than 20 MHz then the Dell Chromebook11 and our newer Lenovo's will consistently reboot over and over again until it connects to an AP running a 20 MHz channel width.
,
Oct 17 2017
@donnie.banks, please update to Chrome OS 61.
,
Nov 17 2017
+Kirtika to evaluate and confirm if this is fixed in latest build
,
Aug 1
,
Dec 14
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/19/18 (5pm EST), this bug will be archived and can be re-opened at any time deemed necessary. Thank you!
,
Dec 20
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 |
|||||||||||||||||||||||
Comment 1 by marcore@chromium.org
, Oct 6 2017