Issue 26111 in chromium-os: Kernel panic - not syncing: Watchdog detected hard LOCKUP on cpu 2

[chrom...@googlecode.com]

Status: Untriaged
Owner: ----
CC: kr...@chromium.org, tturche...@chromium.org
Labels: Type-Bug Pri-2 Area-Platform Sev-1 Crash

New issue 26111 by bhaves...@chromium.org: Kernel panic - not syncing:
Watchdog detected hard LOCKUP on cpu 2
http://code.google.com/p/chromium-os/issues/detail?id=26111

Chrome OS Version : 1660.18.0
Chrome Version : 18.0.1025.8
Type of computer : Alex
Network info : <network, encryption type, router model (if known)>

CrashReport:http://crash/reportdetail?reportid=0826c20857c37847

Please specify Area-* of the system to which this bug/feature applies (add
the label below).

What steps will reproduce the problem?
1.Leave machine idle for some times.
2.Wake it up.

What do you see instead?
Kernel crash.

How frequently does this problem reproduce? hard to reproduce

<0>[12658.226399] Kernel panic - not syncing: Watchdog detected hard LOCKUP
on cpu 2
<5>[12658.226399] Pid: 18433, comm: kworker/u:1 Tainted: G WC
3.0.13 #1
<5>[12658.226399] Call Trace:
<5>[12658.226399] [<8105fd54>] ? touch_nmi_watchdog+0x57/0x57
<5>[12658.226399] [<8137221d>] panic+0x53/0x14a
<5>[12658.226399] [<8105fd54>] ? touch_nmi_watchdog+0x57/0x57
<5>[12658.226399] [<8105fdca>] watchdog_overflow_callback+0x76/0x98
<5>[12658.226399] [<8107e8c4>] __perf_event_overflow+0x1fc/0x281
<5>[12658.226399] [<8100c82f>] ? x86_perf_event_set_period+0x194/0x19f
<5>[12658.226399] [<8100c82f>] ? x86_perf_event_set_period+0x194/0x19f
<5>[12658.226399] [<8107ee25>] perf_event_overflow+0x11/0x13
<5>[12658.226399] [<8100f465>] intel_pmu_handle_irq+0x37a/0x3c9
<5>[12658.226399] [<81047fc5>] ? atomic_notifier_call_chain+0x14/0x16
<5>[12658.226399] [<8104825c>] ? notify_die+0x2d/0x31
<5>[12658.226399] [<81002c09>] ? do_nmi+0x5d/0x244
<5>[12658.226399] [<81002de8>] ? do_nmi+0x23c/0x244
<5>[12658.226399] [<81002c09>] ? do_nmi+0x5d/0x244
<5>[12658.226399] [<8100cfa7>] perf_event_nmi_handler+0x3a/0x7c
<5>[12658.226399] [<81047f77>] notifier_call_chain.isra.0+0x2b/0x4d
<5>[12658.226399] [<81047fc5>] atomic_notifier_call_chain+0x14/0x16
<5>[12658.226399] [<8104825c>] notify_die+0x2d/0x31
<5>[12658.226399] [<81002c09>] do_nmi+0x5d/0x244
<5>[12658.226399] [<81002de8>] ? do_nmi+0x23c/0x244
<5>[12658.226399] [<81377c44>] nmi_stack_correct+0x2f/0x34
<5>[12658.226399] [<811fe181>] ? i915_read32+0x45/0x5e
<5>[12658.226399] [<81202718>] i915_get_vblank_counter+0x6d/0x9b
<5>[12658.226399] [<811f08ea>] vblank_disable_and_save+0x8b/0x15b
<5>[12658.226399] [<8104878c>] ? sched_clock_local+0x10/0x14b
<5>[12658.226399] [<811f1332>] drm_vblank_off+0x30/0x164
<5>[12658.226399] [<811fe2df>] ? i915_write32+0x23/0x52
<5>[12658.226399] [<81218979>] i9xx_crtc_disable+0x48/0x123
<5>[12658.226399] [<81218a87>] i9xx_crtc_prepare+0xd/0xf
<5>[12658.226399] [<811eac1e>] drm_crtc_helper_set_mode+0x1ed/0x36f
<5>[12658.226399] [<811eadf3>] drm_helper_resume_force_mode+0x53/0xea
<5>[12658.226399] [<811f1275>] ? drm_irq_install+0x11e/0x154
<5>[12658.226399] [<811fdbb8>] i915_drm_thaw+0x99/0xbf
<5>[12658.226399] [<811fddbb>] i915_resume+0x3d/0x50
<5>[12658.226399] [<811fdde0>] i915_pm_resume+0x12/0x14
<5>[12658.226399] [<811843fe>] pci_pm_resume+0xad/0xd4
<5>[12658.226399] [<81235305>] pm_op+0x57/0x89
<5>[12658.226399] [<8123591f>] device_resume+0xb7/0x12f
<5>[12658.226399] [<812359b2>] async_resume+0x1b/0x3f
<5>[12658.226399] [<8104969a>] async_run_entry_fn+0x98/0x132
<5>[12658.226399] [<81040066>] process_one_work+0x142/0x227
<5>[12658.226399] [<81049602>] ? async_schedule+0x16/0x16
<5>[12658.226399] [<81040e5b>] worker_thread+0xfc/0x1cc
<5>[12658.226399] [<81040d5f>] ? manage_workers.isra.24+0x14f/0x14f
<5>[12658.226399] [<81043aa7>] kthread+0x67/0x6c
<5>[12658.226399] [<81043a40>] ? __init_kthread_worker+0x2d/0x2d
<5>[12658.226399] [<8137831e>] kernel_thread_helper+0x6/0x10

Attachments:
upload_file_kcrash-0826c20857c37847.kcrash 125 KB
log-020812-184329.tar.bz2 153 KB

[chrom...@googlecode.com]

Comment #1 on issue 26111 by bhaves...@chromium.org: Kernel panic - not

syncing: Watchdog detected hard LOCKUP on cpu 2
http://code.google.com/p/chromium-os/issues/detail?id=26111

Logs: http://cros-hwqual-5.mtv.corp.google.com/bugs/26111/

[chrom...@googlecode.com]

Updates:
Cc: mar...@chromium.org bfr...@chromium.org ol...@chromium.org
Labels: Mstone-R18

Comment #2 on issue 26111 by arsc...@chromium.org: Kernel panic - not

syncing: Watchdog detected hard LOCKUP on cpu 2
http://code.google.com/p/chromium-os/issues/detail?id=26111

i915 maybe?

[chrom...@googlecode.com]

Comment #4 on issue 26111 by qui...@chromium.org: Kernel panic - not

syncing: Watchdog detected hard LOCKUP on cpu 2
http://code.google.com/p/chromium-os/issues/detail?id=26111

Seeing the same (sometimes with CPU 1 instead of 2) on 19.0.1034.0 Aura,
platform 1704.0.2012_02_08_1059 (developer build). Happy to supply logs if
it helps.

[chrom...@googlecode.com]

Comment #6 on issue 26111 by sivag...@chromium.org: Kernel panic - not

syncing: Watchdog detected hard LOCKUP on cpu 2
http://code.google.com/p/chromium-os/issues/detail?id=26111

Got the same kernel crash on Chrome OS: 1835.0.0, Chrome:19.0.1051.0

Crash report: http://crash/reportdetail?reportid=1e986aaa9de86071

[chrom...@googlecode.com]

Comment #8 on issue 26111 by joshwood...@chromium.org: Kernel panic - not

syncing: Watchdog detected hard LOCKUP on cpu 2
http://code.google.com/p/chromium-os/issues/detail?id=26111

+marcheu, is this something you can look into? Or someone else on the
Graphics team?

[chrom...@googlecode.com]

Updates:
Cc: scunning...@chromium.org

Comment #14 on issue 26111 by mar...@chromium.org: Kernel panic - not

syncing: Watchdog detected hard LOCKUP on cpu 2
http://code.google.com/p/chromium-os/issues/detail?id=26111

Issue 29609 has been merged into this issue.

[chrom...@googlecode.com]

Updates:
Status: Fixed

Comment #16 on issue 26111 by mar...@chromium.org: Kernel panic - not

syncing: Watchdog detected hard LOCKUP on cpu 2
http://code.google.com/p/chromium-os/issues/detail?id=26111

Has been long fixed.