public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Nigel Cunningham <ncunningham-oKK1aGe2n869koe0gwxAeg@public.gmane.org>
To: ACPI List <acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Event loop: DSDT or ACPI bug?
Date: Wed, 05 Nov 2003 14:12:45 +1300	[thread overview]
Message-ID: <1067994765.1765.41.camel@laptop-linux> (raw)

Hi all.

If I generate a lid event during suspend I end up with keventd sucking
CPU post-resume (2.4 kernel). If set a breakpoint at
acpi_os_queue_for_execution, I see:

while(1) {
	trace 1 (below)
	trace 2
	trace 3
	trace 2
}

I'm not sure whether this is because some aspect of the hardware state
doesn't match the kernel or if there's a bug in my DSDT or in ACPI, and
I wonder if it's related to some of the other event problems people have
been reporting. If there are things I can do to generate more useful
info, feel free to ask.

(If I add a line in acpi_os_queue_for_execution, making it not queue
events when suspending, I don't get the loop, but neither do I get any
further acpi events.)

Regards,

Nigel

traces (hand recorded, excuse typos please. I left out arguments but can
send them too if desired):

1.
acpi_os_queue_for_execution
acpi_ev_gpedispatch
acpi_ev_gpe_detect
acpi_ev_sci_xrupt_handler
handle_IRQ_event
do_IRQ
call_do_IRQ
acpi_ev_address_space_dispatch
acpi_ex_access_region
acpi_ex_field_datum_io
acpi_ex_write_with_update_rule
acpi_ex_insert_into_field
acpi_ex_write_data_to_field
acpi_ex_store_object_to_node
acpi_ex_store
acpi_ex_opcode_1A_1T_1R
acpi_ps_parse_loop
acpi_ps_parse_aml
acpi_psx_execute
acpi_ns_execute_control_method
acpi_ns_evaluate_by_handle
acpi_ev_asynch_execute_gpe_method
acpi_os_execute_deferred
__run_task_queue
context_thread
arch_kernel_thread

2.
acpi_os_queue_for_execution
acpi_ev_queue_notify_request
acpi_ex_opcode_2A_0T_0R
acpi_ps_parse_loop
acpi_ps_parse_aml
acpi_psx_execute
acpi_ns_execute_control_method
acpi_ns_evaluate_by_handle
acpi_ev_asynch_execute_gpe_method
acpi_os_execute_deferred
__run_task_queue
context_thread
arch_kernel_thread

3.
acpi_os_queue_for_execution
acpi_ev_gpedispatch
acpi_ev_gpe_detect
acpi_ev_sci_xrupt_handler
handle_IRQ_event
do_IRQ
call_do_IRQ
acpi_os_execute_deferred
__run_task_queue
context_thread
arch_kernel_thread

-- 
Nigel Cunningham
495 St Georges Road South, Hastings 4201, New Zealand

Evolution (n): A hypothetical process whereby infinitely improbable events occur 
with alarming frequency, order arises from chaos, and no one is given credit.



-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive?  Does it
help you create better code?   SHARE THE LOVE, and help us help
YOU!  Click Here: http://sourceforge.net/donate/

                 reply	other threads:[~2003-11-05  1:12 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1067994765.1765.41.camel@laptop-linux \
    --to=ncunningham-okk1age2n869koe0gwxaeg@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox