:With a kernel built from -current cvsup'd at Sun Aug 22 04:03:19 BST 1999,
:I got the following panic doing make -j8 world with /usr/src via NFS and
:/usr/obj local:
:Panic: free vnode isn't
:mp_lock = 00000001; cpuid = 0; lapic.id = 00000000
:backtrace (hand-transcribed):
:getnewvnode() + 0x157
:nfs_nget() + 0x107
:lookup() + 0x2ab
:namei() + 0x137
:stat() + 0x44
:syscall() + 0x186
:Xint0x80_syscall() + 0x31
:Any ideas?
:Bob Bishop              (0118) 977 4017  international code +44 118
:[EMAIL PROTECTED]        fax (0118) 989 4254  between 0800 and 1800 UK

    This is the second person with a crash in nfs_lookup.  No major changes
    have been made to NFS yet -- my patch set is still uncommitted.  I can
    only conclude that something else someone has done has broken something. 

    With my patchset and the latest current, I am able to do buildworlds
    in a loop forever on an SMP box using precisely that setup:  /usr/src
    via NFS, /usr/obj local (and also /usr/obj/ via VN).

    At this instant my patch set will not patch cleanly due to some 
    inappropriate commits made last night which I am trying to resolve.
    (However, these commits are probably not responsible for this particular
    problem since you indicate an early sunday morning image).

    I recommend waiting a few days, hopefully this mess will be straightened
    out by then and we can put everyone on the same page again.  I can't 
    update my patch until the mess that was committed last night has been 
    backed out.

                                        Matthew Dillon 
                                        <[EMAIL PROTECTED]>

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Reply via email to