Issue 224255 in chromium: Chromebook Pixel turns itself off/crashes after being exposed to high amounts of electromagnetic radiation in Airport x-Ray machines.

[chro...@googlecode.com]

Status: Unconfirmed
Owner: ----
Labels: Pri-2 Via-Wizard Type-Bug OS-Chrome

New issue 224255 by frohrw...@google.com: Chromebook Pixel turns itself
off/crashes after being exposed to high amounts of electromagnetic
radiation in Airport x-Ray machines.
http://code.google.com/p/chromium/issues/detail?id=224255

UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_8_2)
AppleWebKit/537.22 (KHTML, like Gecko) Chrome/25.0.1364.172 Safari/537.22

Steps to reproduce the problem:
1. Put pixel to sleep (closing the lid)
2. Expose it to high amounts of electromagnetic radiation (xray it)
3. Pixel wakes up, goes back to sleep right after radiation exposure
4. Upon next wakeup, Pixel crashes and reboots

What is the expected behavior?
Ideally, this should not happen. We never know when Aliens attack us and
use EMP to reboot our Chromebooks

What went wrong?
When the Pixel is in standby and is exposed to high amounts of radiation,
the chromebook wakes up, goes to sleep and shuts itself down with a kernel
event after a while.

The part of the log during the event:

From the time I passed the security check

Exposure to Xray radiation at 18:09:00
181 | 2013-03-18 18:09:00 | ACPI Wake | S3
182 | 2013-03-18 18:09:00 | Wake Source | GPIO | 12
183 | 2013-03-18 18:09:00 | Wake Source | GPIO | 14
184 | 2013-03-18 18:09:02 | ACPI Enter | S3
185 | 2013-03-19 18:09:00 | ACPI Wake | S3
186 | 2013-03-19 18:09:00 | Wake Source | RTC Alarm | 0
187 | 2013-03-19 18:09:00 | Wake Source | GPIO | 14
188 | 2013-03-19 18:09:04 | Kernel Event | Clean Shutdown
189 | 2013-03-19 18:09:04 | ACPI Enter | S5
190 | 2013-03-20 00:03:18 | System boot | 127
191 | 2013-03-20 00:03:18 | SUS Power Fail
192 | 2013-03-20 00:03:18 | System Reset
193 | 2013-03-20 00:03:18 | ACPI Wake | S5
194 | 2013-03-20 00:05:09 | ACPI Enter | S3

Did this work before? N/A

Chrome version: 27.0.1438.8 Channel: dev
OS Version: 3833.0.0

Aliens.

--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

[chro...@googlecode.com]

Updates:
Cc: ble...@chromium.org mten...@chromium.org

Comment #1 on issue 224255 by mten...@chromium.org: Chromebook Pixel turns

itself off/crashes after being exposed to high amounts of electromagnetic
radiation in Airport x-Ray machines.
http://code.google.com/p/chromium/issues/detail?id=224255

Benson, was the wake due to the touchscreen in this case?

[chro...@googlecode.com]

Updates:
Labels: Cr-OS-Hardware

Comment #2 on issue 224255 by tha...@chromium.org: Chromebook Pixel turns

itself off/crashes after being exposed to high amounts of electromagnetic
radiation in Airport x-Ray machines.
http://code.google.com/p/chromium/issues/detail?id=224255

(No comment was entered for this change.)

[chro...@googlecode.com]

Comment #5 on issue 224255 by frohrw...@google.com: Chromebook Pixel turns

itself off/crashes after being exposed to high amounts of electromagnetic
radiation in Airport x-Ray machines.
http://code.google.com/p/chromium/issues/detail?id=224255

(And yep, I meant void kampff as you normally cannot flip the turtle...)

Uhm BTW the xray machine was a US model, located at SFO (if that makes much
difference)

[chro...@googlecode.com]

Comment #6 on issue 224255 by paw...@google.com: Chromebook Pixel turns

itself off/crashes after being exposed to high amounts of electromagnetic
radiation in Airport x-Ray machines.
http://code.google.com/p/chromium/issues/detail?id=224255

Apparently it makes a difference. Can't reproduce in MXP.

[chro...@googlecode.com]

Updates:
Status: Started
Owner: ble...@chromium.org
Cc: de...@chromium.org
Labels: Cr-UI-Input-Touch M-27

Comment #7 on issue 224255 by ble...@chromium.org: Chromebook Pixel turns

itself off/crashes after being exposed to high amounts of electromagnetic
radiation in Airport x-Ray machines.
http://code.google.com/p/chromium/issues/detail?id=224255

We disable the touchpad as a wakesource on lid close. The touchscreen is
never a wakeup source... I'm double checking if we disable the ACPI wakeup
sources too. There may be a minor bug in R26 and R27 on that actually.

What's probably happening here is the radiation is causing the interrupt to
trigger, perhaps?

[chro...@googlecode.com]

Comment #8 on issue 224255 by ble...@chromium.org: Chromebook Pixel turns

itself off/crashes after being exposed to high amounts of electromagnetic
radiation in Airport x-Ray machines.
http://code.google.com/p/chromium/issues/detail?id=224255

Touch devices are turned off when the lid is closed, but the acpi wakeup
for the TSCR and TPAD gpios are still live on 26 and 27.

[chro...@googlecode.com]

Comment #11 on issue 224255 by dbaseh...@google.com: Chromebook Pixel turns

itself off/crashes after being exposed to high amounts of electromagnetic
radiation in Airport x-Ray machines.
http://code.google.com/p/chromium/issues/detail?id=224255

Since it boots and then resets, I don't think this has anything to do with
dark resume. No state should be persisted after it shuts down.

Dark resume could have shut the machine down, but that is expected
behavior. The next boot is some time after that shutdown, so I don't think
it has anything to do with this. It's hard to tell without logs, though, do
we have those?

[chro...@googlecode.com]

Comment #12 on issue 224255 by ble...@chromium.org: Chromebook Pixel turns

itself off/crashes after being exposed to high amounts of electromagnetic
radiation in Airport x-Ray machines.
http://code.google.com/p/chromium/issues/detail?id=224255

I discussed this with derek, and we believe the shutting down and reset on
next lid open is the intended dark resume behavior. The system woke back up
almost exactly 23 hours, 59 minutes, 59 seconds later, and the power
manager shut the machine down gracefully to save power.

The event that happened at 2013-03-18 18:09:00 may still be related to the
touchscreen or touchpad wakes, as both of the acpi wakeups for those gpios
are still live even though the touchscreen and touchpad devices themselves
are in an off state. It's not out of the question that some wiggling on the
interrupt line occurred and woke the system.

I just fixed issue 224396, which should make sure the touch device wake
sources are disabled from /proc/acpi/wakeup as well.


Or...
http://i2.kym-cdn.com/photos/images/original/000/158/329/9189283.jpg

[chro...@googlecode.com]

Updates:
Status: Fixed

Comment #13 on issue 224255 by ble...@chromium.org: Chromebook Pixel turns

itself off/crashes after being exposed to high amounts of electromagnetic
radiation in Airport x-Ray machines.
http://code.google.com/p/chromium/issues/detail?id=224255

issue 224396 was fixed, so this once a new R26 or R27 is pushed, the system
should no longer be able to wake up in this way.

[chro...@googlecode.com]

Comment #15 on issue 224255 by semenz...@chromium.org: Chromebook Pixel

turns itself off/crashes after being exposed to high amounts of
electromagnetic radiation in Airport x-Ray machines.
http://code.google.com/p/chromium/issues/detail?id=224255

We have another report in case you want to verify the version:


BTW I noticed this issue today at the airport as well.
- feedback/730090388 incase you want to take alook.
- It was on a roller before it went on a belt, and its possible that the
laptop bounced a bit during the process.
- The event happened at 17:07 in case you want to see what happened before
and after.
- I noticed it because the lightbar got activated (side to side movement...
not static blue) as I picked it up from the belt.


013-04-04T15:55:32.615319-07:00 localhost powerd_suspend[22720]: Going to
suspend-to-RAM state : args=--suspend_duration=86399 --wakeup_count=10583
2013-04-04T15:55:32.860015-07:00 localhost powerd_suspend[22720]: Explicit
sync
2013-04-04T15:55:33.476249-07:00 localhost powerd_suspend[22720]:
Finalizing suspend
2013-04-04T17:07:27.686937-07:00 localhost kernel: [ 7998.306525] PM:
Syncing filesystems ... done.
2013-04-04T17:07:27.686993-07:00 localhost kernel: [ 7998.356873] PM:
Preparing system for mem sleep
2013-04-04T17:07:27.688192-07:00 localhost kernel: [ 7998.356880] Freezing
user space processes ... (elapsed 0.01 seconds) done.
2013-04-04T17:07:27.688243-07:00 localhost kernel: [ 7998.368665] Freezing
remaining freezable tasks ... (elapsed 0.01 seconds) done.
2013-04-04T17:07:27.688254-07:00 localhost kernel: [ 7998.379654] PM:
Entering mem sleep
2013-04-04T17:07:27.688262-07:00 localhost kernel: [ 7998.379808] calling
rfkill6+ @ 22721, parent: hci0
2013-04-04T17:07:27.688270-07:00 localhost kernel: [ 7998.379817] call
rfkill6+ returned 0 after 0 usecs

[chro...@googlecode.com]

Updates:
Status: Verified
Cc: ka...@chromium.org

Comment #17 on issue 224255 by rajeevku...@chromium.org: Chromebook Pixel

turns itself off/crashes after being exposed to high amounts of
electromagnetic radiation in Airport x-Ray machines.
http://code.google.com/p/chromium/issues/detail?id=224255

Based on feedback from Benson, closing verified.