New issue
Advanced search Search tips

Issue 829963 link

Starred by 2 users
Status: Unconfirmed
Owner: ----
EstimatedDays: ----
NextAction: 2019-07-09
OS: Chrome
Pri: 3
Type: Bug-Regression



Sign in to add a comment

Connected bluetooth headset sometimes sends Pixelbook into a crash boot-loop

Project Member Reported by dkozdoba@google.com, Apr 6 2018 
UserAgent: Mozilla/5.0 (X11; CrOS x86_64 10323.67.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/65.0.3325.209 Safari/537.36
Platform: 10323.67.0 (Official Build) stable-channel eve

Steps to reproduce the problem:
1. Connect Bluetooth headset (Bose SoundSport) to Pixelbook 
2. Listen to some audio for a while (e.g. TGIF for ~40min)
3. Make an attempt to pause/resume audio
4. The system reboots.
5. Restoring pages makes system reboot again.
6. This happens until Bluetooth is disconnected or bluetooth is disabled on ChromeOS.

What is the expected behavior?
Not to crash.

What went wrong?
Crash.

Crashed report ID: no crash report was created/found

How much crashed? Whole browser

Is it a problem with a plugin? N/A 

Did this work before? Yes I noticed this started to happen in April.

Chrome version: 65.0.3325.209  Channel: stable
OS Version: 10323.67.0
Flash Version:

Comment 1 by ranger...@gmail.com, Apr 7 2018 

Having a very similar issue with my Pixelbook - had it crash 4 times in the last 30 minutes just during my attempt to finish typing this bug report!

Found just ONE crash report in the chrome://crashes coinciding with the crash this morning, however, over the last 24 hours, this must have crashed to reboot ~15 times, with slightly different circumstances each time.

[IMPORTANT: Your crash has already been automatically reported to our crash system. Please file this bug only if you can provide more information about it.]

Chrome Version: 65.0.3325.209
Operating System: Linux 4.4.111-12566-g94bdaa2af495-dirty

URL (if applicable) where crash occurred: specifically included (although doesn't seem relevant): bugs.chrominum.org, youtube.com, steampowered.com, redbox.com

Can you reproduce this crash? not with specific accuracy - but consistency reproducible over last 24 hours by just using the device 

What steps will reproduce this crash? (If it's not reproducible, what were you doing just before the crash?)
1. Pixelbook Bluetooth on/off, both when connected/not connected to Bluetooth device(s) - Pixel XL (Marlin) or Bose QC35 Headphones
2. Using device in any combination of ways including using/not using Bluetooth devices, ARC++ apps, sometime ~5 minutes, sometime ~40 minutes before crashes.
3. On crash, no warning or error messages - Pixelbook completely reboots
4. After crash, behavior continues under many different use conditions with random times between crashes (as mentioned, ~15 times over last 24 hours, with several crashes in the middle of submitting this bug report, yet was able to retype the entire report (again) and submit it without a crash on the 5th attempt - post crash reboot)
5. As OP mentioned, can't seem to find crash reports the majority of the time, only ONE crash log was found to be generated after a crash this morning (3 additional crashes have occurred since this log was generated - none which were logged in chrome://crashes)
6. Seems to be happening after rebooting for update sometime yesterday - however I didn't even notice if it was a component update or OS update - and I haven't has extensive usage over the last few days - so I'm just speculating that it's possibly correlated.

****DO NOT CHANGE BELOW THIS LINE****
Crash ID: crash/1632693aec046250

Comment 2 by ranger...@gmail.com, Apr 7 2018 

Some more digging in the event log shows 14 total kernel panics <24 hours, along with some additional support to my possible suspicions that whatever update I rebooted to install around the 18:26 mark yesterday seems to have really affected the stability - no kernel panics are logged prior to the 18:26 mark yesterday when the cr50 update status is reset - 14 since then.

169 | 2018-04-06 17:27:32 | EC Event | Lid Open
170 | 2018-04-06 17:27:32 | EC Event | Power Button
171 | 2018-04-06 17:27:32 | EC Event | Battery Shutdown in previous boot
172 | 2018-04-06 17:27:33 | ACPI Wake | Deep S3
173 | 2018-04-06 17:27:33 | Wake Source | Power Button | 0
174 | 2018-04-06 17:28:54 | ACPI Enter | S3
175 | 2018-04-06 17:49:09 | EC Event | Lid Open
176 | 2018-04-06 17:49:09 | ACPI Wake | Deep S3
177 | 2018-04-06 18:25:57 | Kernel Event | Clean Shutdown
178 | 2018-04-06 18:26:03 | System boot | 5
179 | 2018-04-06 18:26:03 | Last post code in previous boot | 0x98 | FSP-M Exit
180 | 2018-04-06 18:26:03 | System Reset
181 | 2018-04-06 18:26:03 | cr50 Update Reset
182 | 2018-04-06 18:26:03 | ACPI Enter | S5
183 | 2018-04-06 18:26:05 | System boot | 6
184 | 2018-04-06 18:26:05 | Power Fail
185 | 2018-04-06 18:26:05 | ACPI Wake | Deep S5
186 | 2018-04-06 18:26:05 | Wake Source | Power Button | 0
187 | 2018-04-06 18:27:58 | Kernel Event | Oops
188 | 2018-04-06 18:27:58 | Kernel Event | Panic
189 | 2018-04-06 18:28:00 | System boot | 7
190 | 2018-04-06 18:28:00 | System Reset
191 | 2018-04-06 18:32:29 | ACPI Enter | S3
192 | 2018-04-06 22:36:54 | EC Event | Lid Open
193 | 2018-04-06 22:36:54 | ACPI Wake | Deep S3
194 | 2018-04-06 22:38:13 | Kernel Event | Oops
195 | 2018-04-06 22:38:13 | Kernel Event | Panic
196 | 2018-04-06 22:38:15 | System boot | 8
197 | 2018-04-06 22:38:15 | System Reset
198 | 2018-04-06 23:36:21 | ACPI Enter | S3
199 | 2018-04-06 23:40:45 | EC Event | Lid Open
200 | 2018-04-06 23:40:45 | ACPI Wake | Deep S3
201 | 2018-04-06 23:41:35 | Kernel Event | Oops
202 | 2018-04-06 23:41:35 | Kernel Event | Panic
203 | 2018-04-06 23:41:37 | System boot | 9
204 | 2018-04-06 23:41:37 | System Reset
205 | 2018-04-06 23:50:37 | Kernel Event | Oops
206 | 2018-04-06 23:50:37 | Kernel Event | Panic
207 | 2018-04-06 23:50:39 | System boot | 10
208 | 2018-04-06 23:50:39 | System Reset
209 | 2018-04-06 23:51:38 | Kernel Event | Oops
210 | 2018-04-06 23:51:38 | Kernel Event | Panic
211 | 2018-04-06 23:51:40 | System boot | 11
212 | 2018-04-06 23:51:40 | System Reset
213 | 2018-04-06 23:52:33 | Kernel Event | Oops
214 | 2018-04-06 23:52:33 | Kernel Event | Panic
215 | 2018-04-06 23:52:34 | System boot | 12
216 | 2018-04-06 23:52:34 | System Reset
217 | 2018-04-07 00:06:38 | Kernel Event | Oops
218 | 2018-04-07 00:06:38 | Kernel Event | Panic
219 | 2018-04-07 00:06:40 | System boot | 13
220 | 2018-04-07 00:06:40 | System Reset
221 | 2018-04-07 00:07:27 | Kernel Event | Oops
222 | 2018-04-07 00:07:27 | Kernel Event | Panic
223 | 2018-04-07 00:07:29 | System boot | 14
224 | 2018-04-07 00:07:29 | System Reset
225 | 2018-04-07 00:28:22 | Kernel Event | Oops
226 | 2018-04-07 00:28:22 | Kernel Event | Panic
227 | 2018-04-07 00:28:24 | System boot | 15
228 | 2018-04-07 00:28:24 | System Reset
229 | 2018-04-07 00:28:37 | Kernel Event | Clean Shutdown
230 | 2018-04-07 00:28:37 | ACPI Enter | S5
231 | 2018-04-07 08:41:39 | System boot | 16
232 | 2018-04-07 08:41:39 | EC Event | Lid Open
233 | 2018-04-07 08:41:39 | ACPI Wake | Deep S5
234 | 2018-04-07 08:41:39 | Wake Source | Power Button | 0
235 | 2018-04-07 08:55:01 | ACPI Enter | S3
236 | 2018-04-07 09:02:52 | EC Event | Lid Open
237 | 2018-04-07 09:02:52 | ACPI Wake | Deep S3
238 | 2018-04-07 09:07:24 | Kernel Event | Oops
239 | 2018-04-07 09:07:24 | Kernel Event | Panic
240 | 2018-04-07 09:07:26 | System boot | 17
241 | 2018-04-07 09:07:26 | System Reset
242 | 2018-04-07 09:43:26 | Kernel Event | Oops
243 | 2018-04-07 09:43:26 | Kernel Event | Panic
244 | 2018-04-07 09:43:27 | System boot | 18
245 | 2018-04-07 09:43:27 | System Reset
246 | 2018-04-07 09:46:23 | Kernel Event | Oops
247 | 2018-04-07 09:46:23 | Kernel Event | Panic
248 | 2018-04-07 09:46:25 | System boot | 19
249 | 2018-04-07 09:46:25 | System Reset
250 | 2018-04-07 11:15:08 | Kernel Event | Oops
251 | 2018-04-07 11:15:08 | Kernel Event | Panic
252 | 2018-04-07 11:15:10 | System boot | 20
253 | 2018-04-07 11:15:10 | System Reset
254 | 2018-04-07 11:16:05 | Kernel Event | Oops
255 | 2018-04-07 11:16:05 | Log area cleared | 1026
256 | 2018-04-07 11:16:05 | Kernel Event | Panic
257 | 2018-04-07 11:16:07 | System boot | 21
258 | 2018-04-07 11:16:07 | System Reset

Comment 3 by benhenry@google.com, Jan 10

Labels: Pri-3
NextAction: 2019-07-09
Downgrading P2s that haven't been modified in more than 6 months, which have no component or owner.
►

Sign in to add a comment