On Thu, Jul 06, 2006 at 07:58:14AM -0700, Tom London wrote:
> After installing .2356 I get this each time I boot:
> =======================================================
> [ INFO: possible circular locking dependency detected ]
> -------------------------------------------------------
> S06cpuspeed/1620 is trying to acquire lock:
> (dbs_mutex){--..}, at: [<c060d6bb>] mutex_lock+0x21/0x24
>
> but task is already holding lock:
> (cpucontrol){--..}, at: [<c060d6bb>] mutex_lock+0x21/0x24
>
> which lock already depends on the new lock.
Seen that one: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=197803
It's a tricky problem, but people (including myself) are looking into it.
The new lock dependancy checker may pick up on a bunch of things
like this over the next few weeks. Please post any of these
that you see to bugzilla, even if things continue to work fine
afterwards.
Dave
--
http://www.codemonkey.org.uk
--
fedora-test-list mailing list
fedora-test-list@xxxxxxxxxx
To unsubscribe:
https://www.redhat.com/mailman/listinfo/fedora-test-list