Comment 4 for bug 1004313

i think it's a me, too.

it happens about every 5th time when my laptop tries to wake up from sleep. it got introduced somewhat recently, because i keep my debian testing more or less up to date, and it started to happen about a month ago.

on debian testing, on a Dell Latitude E6320:
Linux xxx 3.2.0-3-amd64 #1 SMP Thu Jun 28 09:07:26 UTC 2012 x86_64 GNU/Linux

below are some pieces of backtraces that i copied by hand. unfortunately the screen gets updated every few seconds with different backtraces (of different CPU's?), so i could only copy portions of the backtraces. a newline below means its from a different backtrace.

"watchdog detected hard lockup"
warn_slowpath_fmt

power_supply_am_i_supplied

native_flush_tlb_others
...
eventfd_ctx_read
try_to_wake_up

wq_worker_sleeping

acpi_ns_evaluate

arch_read_lock
led_trigger_event

menu_select
cpuidle_idle_call

CPU0: Intel(R) Core(TM) i7-2620M CPU @ 2.70GHz stepping 07
Performance Events: PEBS fmt1+, SandyBridge events, Intel PMU driver.
PEBS disabled due to CPU errata.
... version: 3
... bit width: 48
... generic registers: 4
... value mask: 0000ffffffffffff
... max period: 000000007fffffff
... fixed-purpose events: 3
... event mask: 000000070000000f
NMI watchdog enabled, takes one hw-pmu counter.
Booting Node 0, Processors #1
NMI watchdog enabled, takes one hw-pmu counter.
 #2
NMI watchdog enabled, takes one hw-pmu counter.
 #3
NMI watchdog enabled, takes one hw-pmu counter.
Brought up 4 CPUs
Total of 4 processors activated (21550.18 BogoMIPS).