lockmgr: thread <..> unlocking unheld lock
Andrew Gallatin
gallatin at cs.duke.edu
Fri Oct 14 14:20:50 PDT 2005
John Baldwin writes:
> On Thursday 13 October 2005 04:24 pm, Andrew Gallatin wrote:
> > John Baldwin writes:
> > > On Wednesday 05 October 2005 02:00 pm, Andrew Gallatin wrote:
> > > > It also seems to have started happening on a second amd64 that I just
> > > > upgraded from a mid-august -current to CVS cvsupped yesterday. This
> > > > is a UP amd64 3000+..
> > >
> > > Can you try reverting any of the recent changes to
> > > amd64/include/atomic.h? The ones to change foo_ptr() to take uintptr_t
> > > should be fine, but maybe try reverting the changes after that (not
> > > using +m for example).
> >
> > Inline asm is Greek to me, and I'd be no better than a monkey typing
> > at making changes like that.
> >
> > Would you like me to just try reverting all of 1.38?
> >
> > Drew
>
> Yes, that would work fine.
I just did a pair of buildworlds, and a portsnap fetch & update, and
got 11 of those messages. So it looks like it wasn't your atomic
changes.
Drew
More information about the freebsd-current
mailing list