summaryrefslogtreecommitdiffstats
path: root/chromium/docs/website/site/chromium-os/how-tos-and-troubleshooting/debugging-hangs/index.md
blob: 2e7334ce2298ab6e9266fbcdb52e58eaad91ffbc (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
---
breadcrumbs:
- - /chromium-os
  - Chromium OS
- - /chromium-os/how-tos-and-troubleshooting
  - How Tos and Troubleshooting
page_name: debugging-hangs
title: Debugging system hangs (go/cros-debug-hang)
---

If your Chromebook appears hung (i.e. the screen is frozen and the keyboard
and/or trackpad are unresponsive), try the following steps:

*   Pre-Recovery Steps
    *   Note any visible system indicators like LEDs. Are they blinking
                or solid. What color?
    *   Note charging/discharging behavior if possible. Does plugging a
                charger in change LED.
    *   Note USB response. Does touching an gnubby blink. Does charging
                a phone via a USB port work?
*   Recovery Steps
    *   Press **Alt+VolumeUp+X**. If you're using a Chromebox, use F10
                instead of VolumeUp. These three keys need to be pressed in that
                order.
        *   This should cause the Chrome browser to restart, and it may
                    take a few seconds. If the system becomes responsive, go to
                    last step.
    *   Press **Alt+VolumeUp+X** a second time.
        *   This should cause the kernel to panic-reboot. If the system
                    becomes responsive, go to last step.
    *   Press **Alt+VolumeUp+R** which should cause a warm reset &
                reboot. If so, go to last step. (This may not work on older
                hardware.)
    *   Press and hold the **power button** for 8+ seconds and the
                system will power off (if shutdown is clean) or it will reboot
                via EC reset
    *   Press **Refresh+Power button(F3).** This causes an EC reset on
                most systems and should be used only as a last resort as it
                minimizes the amount of available debug info.
*   Last Step
    *   Power on (if necessary) Log in, and immediately file feedback
                using Alt+Shift+i.
        *   Make sure that "Send system and app information" is checked.
        *   Make sure to identify what recovery steps you used including
                    the ones you believed failed.

You may also be able to see crash report IDs at chrome://crashes.

For a complete and up-to-date list of debug key sequences including those for
ChromiumOS devices without a keyboard check
[here](https://chromium.googlesource.com/chromiumos/docs/+/HEAD/debug_buttons.md).