public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Pallipadi, Venkatesh" <venkatesh.pallipadi@intel.com>
To: Miles Lane <miles.lane@gmail.com>
Cc: Andi Kleen <andi@firstfloor.org>,
	LKML <linux-kernel@vger.kernel.org>,
	"Eric W. Biederman" <ebiederm@xmission.com>,
	Alexander Viro <viro@zeniv.linux.org.uk>,
	Greg Kroah-Hartman <gregkh@suse.de>,
	"Li, Shaohua" <shaohua.li@intel.com>,
	Dave Jones <davej@redhat.com>
Subject: Re: 2.6.33-rc4-git7 -- head/6104 is trying to acquire lock: (cpuidle_lock){+.+.+.}, at: [<c129e2ec>] show_current_governor+0x12/0x4e
Date: Thu, 21 Jan 2010 17:33:25 -0800	[thread overview]
Message-ID: <1264124005.16916.301.camel@localhost.localdomain> (raw)
In-Reply-To: <20100121191812.GA1840@redhat.com>

On Thu, 2010-01-21 at 11:18 -0800, Dave Jones wrote:
> On Thu, Jan 21, 2010 at 12:50:09PM -0500, Miles Lane wrote:
>  > I was scanning the first few characters of all the files in /proc and
>  > /sys.  I will attempt to determine which file(s) triggered this.
> 
> 
> Dropped cpufreq-list from Cc, added cpuidle maintainers.
> While they sound similar, they are unrelated.

Thanks for reporting the problem. I am able to reproduce this locally.
Will followup once I have some time to poke at it a bit more.

Thanks,
Venki




  reply	other threads:[~2010-01-22  1:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-21 17:50 2.6.33-rc4-git7 -- head/6104 is trying to acquire lock: (cpuidle_lock){+.+.+.}, at: [<c129e2ec>] show_current_governor+0x12/0x4e Miles Lane
2010-01-21 19:18 ` Dave Jones
2010-01-22  1:33   ` Pallipadi, Venkatesh [this message]
2010-01-23  1:34     ` Pallipadi, Venkatesh

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=1264124005.16916.301.camel@localhost.localdomain \
    --to=venkatesh.pallipadi@intel.com \
    --cc=andi@firstfloor.org \
    --cc=davej@redhat.com \
    --cc=ebiederm@xmission.com \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=miles.lane@gmail.com \
    --cc=shaohua.li@intel.com \
    --cc=viro@zeniv.linux.org.uk \
    /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