[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <6278d2220907270207g7ff93fd1kdf59e32f139269d3@mail.gmail.com>
Date: Mon, 27 Jul 2009 10:07:00 +0100
From: Daniel J Blueman <daniel.blueman@...il.com>
To: Peter Zijlstra <a.p.zijlstra@...llo.nl>
Cc: "Rafael J. Wysocki" <rjw@...k.pl>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Kernel Testers List <kernel-testers@...r.kernel.org>
Subject: Re: [Bug #13730] hitting lockdep limits...
On Mon, Jul 27, 2009 at 7:21 AM, Peter Zijlstra<a.p.zijlstra@...llo.nl> wrote:
> On Sun, 2009-07-26 at 22:28 +0200, Rafael J. Wysocki wrote:
>> This message has been generated automatically as a part of a report
>> of recent regressions.
>>
>> The following bug entry is on the current list of known regressions
>> from 2.6.30. Please verify if it still should be listed and let me know
>> (either way).
>>
>>
>> Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=13730
>> Subject : hitting lockdep limits...
>> Submitter : Daniel J Blueman <daniel.blueman@...il.com>
>> Date : 2009-07-05 18:19 (22 days old)
>> References : http://marc.info/?l=linux-kernel&m=124681799023782&w=4
>>
>
>
> Is this still a problem after?
>
> commit b0a5b83ee0fce9dbf8ff5fe1f8c9ae7dfafe458c
> Author: Ingo Molnar <mingo@...e.hu>
> Date: Tue Jun 16 16:11:14 2009 +0200
>
> dma-debug: Put all hash-chain locks into the same lock class
Using the same .config and use profile, I haven't seen this in
2.6.31-rc4, thus this can be closed. I've updated the kernel bugzilla
entry also.
--
Daniel J Blueman
--
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