https://bugzilla.kernel.org/show_bug.cgi?id=15924
Steven Rostedt <rost...@goodmis.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |rost...@goodmis.org
--- Comment #42 from Steven Rostedt <rost...@goodmis.org> 2010-05-28 19:28:20
---
I have an old box (Compaq Preserio) that I bought back in 2003. I'm currently
installing Fedora 12 on it. The default .31 kernel could not handle the PCI
wifi card, .32 (and .33) would lock up in X, and .34 which seemed to fix the
previous two, would have kacpi_notify running at 100%.
I ran ftrace on it (workqueue and sched events along with tracing the
acpi_ev_*). The kacpi_notify never goes to sleep. It is scheduled out via a
"cond_resched" in the running state. This means on a non preempt, non voluntary
preempt kernel, this would lock up the box.
Here's what I did:
# echo 'sched_switch' 'sched_wakeup' sched_wakeup_new 'workqueue' irq >
/debug/tracing/set_event
# echo acpi_os_execute_deferred >> /debug/tracing/set_ftrace_filter
# echo 'acpi_ev_*' >> /debug/tracing/set_ftrace_filter
# echo function > /debug/tracing/current_tracer
# echo 1 > /debug/tracing/options/stacktrace
Which would produce the following:
kacpi_notify-17 [000] 807.509455: acpi_ev_is_notify_object
<-acpi_ex_opcode_2A_0T_0R
kacpi_notify-17 [000] 807.509456: acpi_ev_queue_notify_request
<-acpi_ex_opcode_2A_0T_0R
kacpi_notify-17 [000] 807.509462: workqueue_insertion:
thread=kacpi_notify:17 func=acpi_os_execute_deferred
kacpi_notify-17 [000] 807.509462: <stack trace>
=> ftrace_raw_event_workqueue_insertion
=> insert_work
=> __queue_work
=> queue_work_on
=> queue_work
=> __acpi_os_execute
=> acpi_os_execute
=> acpi_ev_queue_notify_request
kacpi_notify-17 [000] 807.509485: acpi_ev_address_space_dispatch
<-acpi_ex_access_region
I'm currently bisecting to find where the issue is. On a bad kernel,
kacpi_notify takes up 100% of the CPU, on a good kernel, it does not even show
up.
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
------------------------------------------------------------------------------
_______________________________________________
acpi-bugzilla mailing list
acpi-bugzilla@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/acpi-bugzilla
