[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1264124005.16916.301.camel@localhost.localdomain>
Date: Thu, 21 Jan 2010 17:33:25 -0800
From: "Pallipadi, Venkatesh" <venkatesh.pallipadi@...el.com>
To: Miles Lane <miles.lane@...il.com>
Cc: Andi Kleen <andi@...stfloor.org>,
LKML <linux-kernel@...r.kernel.org>,
"Eric W. Biederman" <ebiederm@...ssion.com>,
Alexander Viro <viro@...iv.linux.org.uk>,
Greg Kroah-Hartman <gregkh@...e.de>,
"Li, Shaohua" <shaohua.li@...el.com>, Dave Jones <davej@...hat.com>
Subject: Re: 2.6.33-rc4-git7 -- head/6104 is trying to acquire lock:
(cpuidle_lock){+.+.+.}, at: [<c129e2ec>] show_current_governor+0x12/0x4e
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
--
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