On Fri, 2011-05-20 at 19:10 +0200, Toralf Förster wrote: > Steven Rostedt wrote at 18:11:36 > > > Wait! This is where we need the WARN_ON_SMP(), do we have that patch in? > > > > > > I think UML is UP, and that spin_is_locked() will always return false. > > > > Could you apply these patches: > > > > 2092e6be WARN_ON_SMP(): Allow use in if() statements on UP > > 29096202 futex: Fix WARN_ON() test for UP > > > > On top of this commit, and see if the problem goes away. What could have > > happened, is that you have two bugs, with one of them fixed. If the git > > bisect stumbled on this bug, it will show this one, even though later > > on, this code was fixed. If you apply the above two patches and it works > > again, then this isn't the bug you are looking for. > > > > -- Steve > Right - applying those 2 commits on top of v2.6.38-rc8-1-g2e12978 works - now > the issue is away. > > And yes - now I've to look for the other of two bugs, which was introduced > between the tags v2.6.38 and v2.6.39, I think.
Another thing you could do is checkout 29096202 and see if it works. If it does, you can base that as your "git bisect good" and you should not be affected by this bug again. -- Steve ------------------------------------------------------------------------------ What Every C/C++ and Fortran developer Should Know! Read this article and learn how Intel has extended the reach of its next-generation tools to help Windows* and Linux* C/C++ and Fortran developers boost performance applications - including clusters. http://p.sf.net/sfu/intel-dev2devmay _______________________________________________ User-mode-linux-devel mailing list User-mode-linux-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
