[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <c4e36d110908251333p2da20276j650232cea8da4c1f@mail.gmail.com>
Date: Tue, 25 Aug 2009 22:33:30 +0200
From: Zdenek Kabelac <zdenek.kabelac@...il.com>
To: Bjorn Helgaas <bjorn.helgaas@...com>
Cc: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
len.brown@...el.com, linux-acpi@...r.kernel.org,
Henrique de Moraes Holschuh <hmh@....eng.br>,
Zhang Rui <rui.zhang@...el.com>
Subject: Re: INFO: possible circular locking dependency - kacpid
acpi_os_wait_events_complete
2009/8/25 Bjorn Helgaas <bjorn.helgaas@...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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists