[lkml]   [2010]   [Sep]   [20]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: [Bug #17752] 2.6.36-rc3: inconsistent lock state (iprune_sem, shrink_icache_memory)
    Rafael J. Wysocki wrote:
    > This message has been generated automatically as a part of a summary report
    > of recent regressions.
    > The following bug entry is on the current list of known regressions
    > from 2.6.35. Please verify if it still should be listed and let the tracking team
    > know (either way).
    > Bug-Entry :
    > Subject : 2.6.36-rc3: inconsistent lock state (iprune_sem, shrink_icache_memory)
    > Submitter : Stefan Richter <>
    > Date : 2010-09-01 6:37 (20 days old)
    > Message-ID : <>
    > References :

    I think this should not be marked as a regression. See the older reports of
    very similar issues (in my LKML mail from September 3, logged in bugzilla in
    comment #1) (2.6.33-rc, xfs involved) (2.6.32.y, ntfs involved)
    and hch's analysis in the first of these two threads (several filesystems and
    other code paths)
    So, unless my trace was a code path that only newly acquired that oldproblem
    of other code paths, this is an older issue. Alas this is not obvious to me
    at least from the log that I got.

    I did not have lockdep enabled on the machine which delivered the log during
    the last few months or so; I just remembered to re-enable it at the occasion
    of switching to 2.6.36-rc.
    Stefan Richter
    -=====-==-=- =--= =-=--

     \ /
      Last update: 2010-09-20 22:49    [W:0.020 / U:19.120 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site