New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 902473 link

Starred by 1 user

Issue metadata

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



Sign in to add a comment

divide by zero errors in elan_probe

Project Member Reported by groeck@chromium.org, Nov 6

Issue description

Seen quite widely in kernel crash reports.

<4>[ 0.616573] divide error: 0000 [#1] PREEMPT SMP
<0>[ 0.619668] gsmi: Log Shutdown Reason 0x03
<4>[ 0.619672] Modules linked in:
<4>[ 0.619680] CPU: 1 PID: 63 Comm: kworker/u4:1 Not tainted 4.4.159-15335-gcd8d1af51057 #1
<4>[ 0.619683] Hardware name: GOOGLE Gnawty, BIOS Google_Gnawty.5216.239.156 12/03/2017
<4>[ 0.619693] Workqueue: events_unbound async_run_entry_fn
<4>[ 0.619698] task: ffff880077443c00 task.stack: ffff880077ffc000
<4>[ 0.619701] RIP: 0010:[<ffffffffb3d4dacb>] [<ffffffffb3d4dacb>] elan_probe+0x199/0x550
<4>[ 0.619710] RSP: 0000:ffff880077fffca8 EFLAGS: 00010246
<4>[ 0.619714] RAX: 0000000000000c87 RBX: 0000000000000000 RCX: 3104eb588aad4ae4
<4>[ 0.619717] RDX: 0000000000000000 RSI: 0000000000000002 RDI: ffff880077cbb128
<4>[ 0.619720] RBP: ffff880077fffcf8 R08: 0000000000000000 R09: 00000000000003e8
<4>[ 0.619724] R10: 0000000021bedb8b R11: ffffffffb3d65c16 R12: ffff8800776b6928
<4>[ 0.619727] R13: fffffffffffffff4 R14: ffff880077d09c20 R15: ffff880077d09c00
<4>[ 0.619731] FS: 0000000000000000(0000) GS:ffff88007ab00000(0000) knlGS:0000000000000000
<4>[ 0.619734] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
<4>[ 0.619738] CR2: 0000000000000000 CR3: 000000003440c000 CR4: 0000000000100670
<4>[ 0.619740] Stack:
<4>[ 0.619744] ffffffffb3b45661 ffff880077d09c20 ffff880077c52000 00000000000000ac
<4>[ 0.619752] 3104eb588aad4ae4 ffffffffb3d4d932 0000000000000000 ffffffffb44b7c90
<4>[ 0.619760] ffff880077d09c00 ffff880077d09c20 ffff880077fffd30 ffffffffb3d628f0
<4>[ 0.619768] Call Trace:
<4>[ 0.619776] [<ffffffffb3b45661>] ? acpi_device_wakeup+0x7c/0x90
<4>[ 0.619782] [<ffffffffb3d4d932>] ? cyapa_gen6_change_power_state+0xa9/0xa9
<4>[ 0.619788] [<ffffffffb3d628f0>] i2c_device_probe+0x1cd/0x204
<4>[ 0.619795] [<ffffffffb3c7f806>] driver_probe_device+0x281/0x2db
<4>[ 0.619799] [<ffffffffb3c7fa71>] __driver_attach+0x62/0x84
<4>[ 0.619804] [<ffffffffb3c7fa0f>] ? driver_attach+0x23/0x23
<4>[ 0.619810] [<ffffffffb3c7dcae>] bus_for_each_dev+0x76/0xb0
<4>[ 0.619815] [<ffffffffb3c7fa0d>] driver_attach+0x21/0x23
<4>[ 0.619820] [<ffffffffb3c7e4df>] driver_attach_async+0xe/0x10
<4>[ 0.619825] [<ffffffffb38890bc>] async_run_entry_fn+0x40/0xd5
<4>[ 0.619831] [<ffffffffb391456f>] worker_thread+0x24c/0x75e
<4>[ 0.619836] [<ffffffffb3914323>] ? list_move_tail+0x26/0x26
<4>[ 0.619840] [<ffffffffb3886d83>] kthread+0xb9/0xc9
<4>[ 0.619846] [<ffffffffb3fa1370>] ? __switch_to_asm+0x40/0x70
<4>[ 0.619851] [<ffffffffb3886cca>] ? rcu_read_unlock_sched_notrace+0x48/0x48
<4>[ 0.619856] [<ffffffffb3fa13ee>] ret_from_fork+0x4e/0x80
<4>[ 0.619861] [<ffffffffb3886cca>] ? rcu_read_unlock_sched_notrace+0x48/0x48
<4>[ 0.619864] Code: 00 49 8b 3c 24 49 8b 44 24 18 4c 8b 58 68 48 8d 75 cc 48 8d 55 c8 e8 25 89 25 00 89 c3 85 c0 75 7f 41 8b 84 24 90 00 00 00 31 d2 <f7> 75 cc 41 89 84 24 98 00 00 00 41 8b 84 24 94 00 00 00 31 d2
<1>[ 0.619963] RIP [<ffffffffb3d4dacb>] elan_probe+0x199/0x550
<4>[ 0.619969] RSP <ffff880077fffca8>
<4>[ 0.620025] ---[ end trace 331d3104146760cc ]---
<0>[ 0.623404] Kernel panic - not syncing: Fatal exception

 
Labels: -Pri-3 Pri-2
Status: Started (was: Untriaged)
Note that the problem probably exists in all kernel versions (and upstream). Final fix should be sent upstream.

Cc: kt.l...@emc.com.tw

Sign in to add a comment