From owner-freebsd-current Mon Jun 18 18:40:54 2001 Delivered-To: freebsd-current@freebsd.org Received: from colnta.acns.ab.ca (h24-68-206-125.sbm.shawcable.net [24.68.206.125]) by hub.freebsd.org (Postfix) with ESMTP id 673C337B407 for ; Mon, 18 Jun 2001 18:40:48 -0700 (PDT) (envelope-from davidc@colnta.acns.ab.ca) Received: (from davidc@localhost) by colnta.acns.ab.ca (8.11.4/8.11.3) id f5GLMdw04523 for freebsd-current@freebsd.org; Sat, 16 Jun 2001 15:22:39 -0600 (MDT) (envelope-from davidc) Date: Sat, 16 Jun 2001 15:22:39 -0600 From: Chad David To: freebsd-current@freebsd.org Subject: panic from May Message-ID: <20010616152239.A4458@colnta.acns.ab.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I get the following panic on a GENERIC kernel from around May 23: (copied by hand) /usr/src/sys/kern/kern_synch.c:385: sleeping with "vm" locked from /usr/src/sys/vm/vm_pager.c:428 panic: sleeping process owns a mutext Debugger("panic") Stopped at Debugger+0x44: pushl %ebx db> trace Debugger() panic() propagate_priority() _mtx_lock_sleep() obreak() syscall() syscall_with_err_pushd() this looks a lot like... my system cvsupped around May 25 reliably causes a panic when I $ cp /cdrom/distfiles/somefiles /tmp I've written down the message from the debugger: /usr/src/sys/kern_synch.c:385: sleeping with "vm" locked from /usr/src/sys/vm/vm_pager.c: 428 panic: sleeping process owns a mutex Debugger("panic") >trace Debugger(...) panic() propagate_priority() _mtx_lock_sleep() ffs_write() vn_write() writev() syscall() syscall_with_err_pushed() .... from the current archives. What can I do get this thing through a make world? Would a recent kernel over the existing userland have any hope between then and now? Thanks. Chad To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message