lkml.org 
[lkml]   [2009]   [Jul]   [27]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    SubjectRe: [Bug #13730] hitting lockdep limits...
    From
    On Mon, Jul 27, 2009 at 7:21 AM, Peter Zijlstra<a.p.zijlstra@chello.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@gmail.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@elte.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@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

    \
     
     \ /
      Last update: 2009-07-27 11:09    [W:0.022 / U:0.492 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site