On 28.09.2012, at 17:10, J. Bruce Fields wrote: > On Fri, Sep 28, 2012 at 04:19:55AM +0200, Alexander Graf wrote: >> >> On 28.09.2012, at 04:04, Linus Torvalds wrote: >> >>> On Thu, Sep 27, 2012 at 6:55 PM, Alexander Graf <agraf@xxxxxxx> wrote: >>>> >>>> Below are OOPS excerpts from different rc's I tried. All of them crashed - all the way up to current Linus' master branch. I haven't cross-checked, but I don't remember any such behavior from pre-3.6 releases. >>> >>> Since you seem to be able to reproduce it easily (and apparently >>> reliably), any chance you could just bisect it? >>> >>> Since I assume v3.5 is fine, and apparently -rc1 is already busted, a simple >>> >>> git bisect start >>> git bisect good v3.5 >>> git bisect bad v3.6-rc1 >>> >>> will get you started on your adventure.. >> >> Heh, will give it a try :). The thing really does look quite bisectable. >> >> >> It might take a few hours though - the machine isn't exactly fast by today's standards and it's getting late here. But I'll keep you updated. > > I doubt it's anything special about that workload, but just for kicks I > tried a "git clone -ls" (cloning my linux tree to another directory on > the same nfs filesystem), with server on 3.6.0-rc7, and didn't see > anything interesting (just an xfs lockdep warning that looks like this > one jlayton already reported: > http://oss.sgi.com/archives/xfs/2012-09/msg00088.html > ) > > Any (even partial) bisection results would certainly be useful, thanks. Yeah, still trying. Running the same workload in a PPC VM didn't show any badness. Then I tried again to bisect on the machine it broken on, and that commit failed even more badly on me than the previous ones, destroying my local git tree. Trying to narrow down now in a slightly more contained environment :). Alex -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
