From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mathieu Desnoyers Subject: Re: [Bug #13424] possible deadlock when doing governor switching Date: Sun, 28 Jun 2009 21:25:58 -0400 Message-ID: <20090629012558.GA22666@Krystal> References: <5Hhc7UkUKEO.A.IOG.9jASKB@chimera> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: <5Hhc7UkUKEO.A.IOG.9jASKB@chimera> Sender: kernel-testers-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org List-ID: Content-Type: text/plain; charset="us-ascii" To: "Rafael J. Wysocki" Cc: Linux Kernel Mailing List , Kernel Testers List , Shaohua Li , Venkatesh Pallipadi * Rafael J. Wysocki (rjw-KKrjLPT3xs0@public.gmane.org) wrote: > This message has been generated automatically as a part of a report > of regressions introduced between 2.6.29 and 2.6.30. > > The following bug entry is on the current list of known regressions > introduced between 2.6.29 and 2.6.30. Please verify if it still should > be listed and let me know (either way). > Yep, it still exists. Venkatesh Pallipadi from Intel is working on it. We need to figure out a proper way to fix policy rwlock vs dbs_mutex vs timer mutex dependency. Mathieu > > Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=13424 > Subject : possible deadlock when doing governor switching > Submitter : Shaohua Li > Date : 2009-05-31 16:36 (29 days old) > References : http://www.spinics.net/lists/cpufreq/msg00711.html > Handled-By : Mathieu Desnoyers > > > -- Mathieu Desnoyers OpenPGP key fingerprint: 8CD5 52C3 8E3C 4140 715F BA06 3F25 A8FE 3BAE 9A68