From: Zdenek Kabelac <zdenek.kabelac@gmail.com>
To: Bjorn Helgaas <bjorn.helgaas@hp.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
len.brown@intel.com, linux-acpi@vger.kernel.org,
Henrique de Moraes Holschuh <hmh@hmh.eng.br>,
Zhang Rui <rui.zhang@intel.com>
Subject: Re: INFO: possible circular locking dependency - kacpid acpi_os_wait_events_complete
Date: Tue, 25 Aug 2009 22:33:30 +0200 [thread overview]
Message-ID: <c4e36d110908251333p2da20276j650232cea8da4c1f@mail.gmail.com> (raw)
In-Reply-To: <200908251251.37135.bjorn.helgaas@hp.com>
2009/8/25 Bjorn Helgaas <bjorn.helgaas@hp.com>:
> On Tuesday 25 August 2009 02:10:58 am Zdenek Kabelac wrote:
>> Now with 2.6.31-rc7 (3edf2fb9d80a46d6c32ba12547a42419845b4b76)
>> I'm getting this INFO trace - also I've noticed complete reset during resume
>> which could be eventually related to this ?
>
> What's the most recent kernel where this did not occur? Is this
> a regression since 2.6.30?
>
>> My machine - T61, 4GB, C2D
>> I suspect that some resent thinkpad-acpi changes.
>
> Do you have any evidence that points to thinkpad_acpi? I looked
> at the recent changes there, and I don't see anything obviously
> related to kacpid or deferred work.
>
Well I've never seen this INFO trace before - also I'm not sure I
could reliable retest it - might be coincidence of suspend out of port
replicator and resume while being attached on it - however I do this
relatively often and I start to see this after I' started to use -rc7
kernel.
My guess is purely based on the fact that commit touching functions
from INFO trace was recently merged to main tree.
If there will be some time I could try to make few tests for suspend
resume - but I hope the trace would be enough for analysis.
Zdenek
next prev parent reply other threads:[~2009-08-25 20:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-25 8:10 Zdenek Kabelac
2009-08-25 18:51 ` Bjorn Helgaas
2009-08-25 20:33 ` Zdenek Kabelac [this message]
[not found] ` <200908251459.37106.bjorn.helgaas@hp.com>
2009-08-26 14:12 ` Zdenek Kabelac
2009-09-11 7:48 ` Zdenek Kabelac
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=c4e36d110908251333p2da20276j650232cea8da4c1f@mail.gmail.com \
--to=zdenek.kabelac@gmail.com \
--cc=bjorn.helgaas@hp.com \
--cc=hmh@hmh.eng.br \
--cc=len.brown@intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rui.zhang@intel.com \
/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
all inboxes | Powered by JetHome®