New issue
Advanced search Search tips

Issue 651278 link

Starred by 1 user

Issue metadata

Status: Untriaged
Owner: ----
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

pixel 1 freezes

Project Member Reported by semenzato@chromium.org, Sep 29 2016

Issue description

I am getting 2-3 freezes per week.  My link suddenly seems to become less responsive, then it freezes.  It reboots with a triple alt-volup-X.

I sent some feedback reports after the reboot.  This is one of them.

https://feedback.corp.google.com/product/208/neutron?lView=rd&lRSort=1&lROrder=2&lRFilter=1&lReportSearch=user:semenzato&lReport=17324695840

Console-ramoops shows the sysrq-x with these two stack traces, which don't tell me much.

I looked for crashes but couldn't find them.  I'll send more feedback reports.

[ 5904.661586] SysRq : Cros dump and crash
[ 5904.661605] sysrq_x_cros_signal_process: signal 6 chrome pid 1861 tgid 1861
[ 5909.741302] SysRq : Cros dump and crash
[ 5914.636994] SysRq : Cros dump and crash
[ 5914.637022]   task                        PC stack   pid father
[ 5914.637050] powerd          D ffff88011e76b0b8     0   375   1032 0x00000000
[ 5914.637094]  ffff8800268dbce0 0000000000000086 ffffffff8a0144c0 ffff8800268dbfd8
[ 5914.637119]  ffff8800268dbfd8 0000000000011d40 ffff88011e76ad00 000000010055b3b4
[ 5914.637142]  00000000000000c8 ffff880149a72828 ffff8800268dbe78 ffff880149a72800
[ 5914.637166] Call Trace:
[ 5914.637188]  [<ffffffff89cc8f22>] schedule+0x64/0x66
[ 5914.637204]  [<ffffffff89cc7295>] schedule_timeout+0xfc/0x13c
[ 5914.637225]  [<ffffffff8983fed2>] ? ftrace_raw_output_itimer_expire+0xb0/0xb0
[ 5914.637244]  [<ffffffff89cc7333>] schedule_timeout_uninterruptible+0x1e/0x20
[ 5914.637262]  [<ffffffff89cc7333>] ? schedule_timeout_uninterruptible+0x1e/0x20
[ 5914.637280]  [<ffffffff89841454>] msleep+0x51/0x5b
[ 5914.637297]  [<ffffffffc01584b8>] 0xffffffffc01584b7
[ 5914.637311]  [<ffffffffc0158552>] 0xffffffffc0158551
[ 5914.637326]  [<ffffffffc0158783>] 0xffffffffc0158782
[ 5914.637345]  [<ffffffffc00f62e9>] iio_enum_read+0xc0/0x1c9 [industrialio]
[ 5914.637364]  [<ffffffff89aefc5c>] dev_attr_show+0x25/0x49
[ 5914.637381]  [<ffffffff8994d603>] sysfs_read_file+0xc9/0x136
[ 5914.637400]  [<ffffffff898f60bd>] vfs_read+0xa3/0xc7
[ 5914.637416]  [<ffffffff898f633e>] sys_pread64+0x5f/0x80
[ 5914.637432]  [<ffffffff89cca902>] system_call_fastpath+0x16/0x1b

[ 5914.640654] RChrome_IOThread  4524   2589930.091373   1850288   112   2589930.091373    253998.557620   5639295.647098 /
[ 5914.640712] 
[ 5915.640596] Kernel panic - not syncing: ChromeOS X Key
[ 5915.640623] Pid: 0, comm: swapper/0 Tainted: G        WC   3.8.11 #1
[ 5915.640641] Call Trace:
[ 5915.640654]  <IRQ>  [<ffffffff89cc5caa>] panic+0xd2/0x1d3
[ 5915.640690]  [<ffffffff89a69578>] sysrq_handle_cros_xkey+0xa2/0xa2
[ 5915.640706]  [<ffffffff89a697f4>] __handle_sysrq+0x94/0x12c
[ 5915.640722]  [<ffffffff89a699ca>] sysrq_filter+0x119/0x16f
[ 5915.640739]  [<ffffffff89b7f0e0>] input_to_handler+0x60/0xcc
[ 5915.640756]  [<ffffffff89b7fe8d>] input_pass_values.part.3+0x79/0x149
[ 5915.640774]  [<ffffffff89b82174>] input_handle_event.part.6+0x410/0x46e
[ 5915.640792]  [<ffffffff89b822cc>] input_event+0x61/0x78
[ 5915.640809]  [<ffffffff89b8703b>] atkbd_interrupt+0x499/0x5a6
[ 5915.640827]  [<ffffffff89b7c20d>] serio_interrupt+0x42/0x7b
[ 5915.640845]  [<ffffffff89b7d3cd>] i8042_interrupt+0x29b/0x2ad
[ 5915.640863]  [<ffffffff8988c271>] handle_irq_event_percpu+0x41/0x191
[ 5915.640879]  [<ffffffff8988c3ff>] handle_irq_event+0x3e/0x5b
[ 5915.640896]  [<ffffffff8988ec29>] handle_edge_irq+0xa4/0xbd
[ 5915.640914]  [<ffffffff8980384e>] handle_irq+0x118/0x120
[ 5915.640931]  [<ffffffff89ccbf2a>] do_IRQ+0x4a/0xa1
[ 5915.640945]  [<ffffffff89cc9f2a>] common_interrupt+0x6a/0x6a
[ 5915.640957]  <EOI>  [<ffffffff89bcd465>] ? cpuidle_wrap_enter+0x42/0x75
[ 5915.640988]  [<ffffffff89bcd4a8>] cpuidle_enter_tk+0x10/0x12
[ 5915.641004]  [<ffffffff89bcd07c>] cpuidle_enter_state+0x13/0x39
[ 5915.641021]  [<ffffffff89bcd17d>] cpuidle_idle_call+0xdb/0x1bd
[ 5915.641039]  [<ffffffff89809d47>] cpu_idle+0xb7/0xee
[ 5915.641056]  [<ffffffff89cb9859>] rest_init+0x6d/0x6f
[ 5915.641072]  [<ffffffff8a0d3b16>] start_kernel+0x387/0x3a8
[ 5915.641090]  [<ffffffff8a0d32ac>] x86_64_start_reservations+0xb0/0xb3
[ 5915.641107]  [<ffffffff8a0d3396>] x86_64_start_kernel+0xe7/0xea
[ 5915.641131] Kernel Offset: 0x8800000 from 0xffffffff81000000 (relocation range: 0xffffffff80000000-0xffffffffbfffffff)
 
I had another freeze and looked at console-ramoops in chrome://system, but there was only the sysrq stack from cpu_idle().  So Chrome must be wedged.  But why isn't it killed by the first sysrq-X?  I tested in a normal (unfrozen) situation, and the first sysrq-X is working fine, it kills Chrome immediately.

Sign in to add a comment