public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Alexey Starikovskiy <alexey.y.starikovskiy@linux.intel.com>
To: Dominik Brodowski <linux@dominikbrodowski.net>
Cc: Len Brown <lenb@kernel.org>, linux-acpi@vger.kernel.org
Subject: Re: ec locking issue
Date: Tue, 20 Feb 2007 21:24:36 +0300	[thread overview]
Message-ID: <45DB3CE4.8090001@linux.intel.com> (raw)
In-Reply-To: <20070219214502.GA19762@isilmar.linta.de>

Dominik Brodowski wrote:
> Hi,
>
> On Mon, Feb 19, 2007 at 08:44:31AM -0500, Dominik Brodowski wrote:
>   
>> On Fri, Feb 16, 2007 at 12:54:55PM -0500, Len Brown wrote:
>>     
>>>>> acpi_ec_transaction
>>>>> acpi_ec_read
>>>>> acpi_ec_space_handler
>>>>> acpi_ev_address_space_dispatch
>>>>> acpi_ex_access_region
>>>>> acpi_ex_field_datum_
>>>>> acpi_ex_extract_from_field
>>>>> ...
>>>>> acpi_ex_ns_evaluate
>>>>> acpi_ev_execute_reg_method
>>>>> acpi_ev_reg_run
>>>>> acpi_ns_walk_namespace
>>>>> acpi_ev_execute_reg_methods
>>>>> acpi_install_address_space_handler
>>>>> acpi_ec_start
>>>>> acpi_start_single_object
>>>>> acpi_device_probe
>>>>> really_probe
>>>>> ...
>>>>> bus_add_driver
>>>>> ...
>>>>> acpi_ec_init
>>>>>           
>>> Alexey,
>>> Thanks for the fix -- it is applied.
>>>
>>> Dominik,
>>> Did this fix help, or is the problem elsehwere?
>>>       
>> Unfortunately, this doesn't solve the issue for me -- now I get a panic with
>> EIP at __list_add+0x2d/0x60, with the call trace being
>>
>> 	...
>> 	die
>> 	do_page_fault
>> 	error_code
>> 	__mutex_lock_slowpath
>> 	mutex_lock
>> 	acpi_ec_transaction
>>
>> and then the same as above... Will try it out with lockdep disabled.
>>     
>
> No, doesn't seem to be lockdep-related; same issue continues. "acpi=off"
> fixes the issue, though, of course...
>
> Thanks,
> 	Dominik
>   

Dominik,
Could you send your acpidump and full dmesg please?

Thanks,
    Alex.

  reply	other threads:[~2007-02-20 18:24 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-15 19:26 ec locking issue Dominik Brodowski
2007-02-15 20:16 ` Alexey Starikovskiy
2007-02-16 17:54   ` Len Brown
2007-02-19 13:44     ` Dominik Brodowski
2007-02-19 21:45       ` Dominik Brodowski
2007-02-20 18:24         ` Alexey Starikovskiy [this message]
2007-02-20 19:59           ` Dominik Brodowski
2007-02-20 22:07             ` Alexey Starikovskiy
2007-02-22  1:04               ` Dominik Brodowski

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=45DB3CE4.8090001@linux.intel.com \
    --to=alexey.y.starikovskiy@linux.intel.com \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux@dominikbrodowski.net \
    /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