From owner-freebsd-current Sat May 26 14:16:29 2001 Delivered-To: freebsd-current@freebsd.org Received: from bremen.shuttle.de (bremen.shuttle.de [194.95.249.251]) by hub.freebsd.org (Postfix) with ESMTP id E704237B422 for ; Sat, 26 May 2001 14:16:25 -0700 (PDT) (envelope-from schweikh@schweikhardt.net) Received: by bremen.shuttle.de (Postfix, from userid 10) id AA65817DAC; Sat, 26 May 2001 23:05:59 +0200 (CEST) Received: (from schweikh@localhost) by hal9000.schweikhardt.net (8.11.1/8.11.1) id f4QJio901854 for freebsd-current@freebsd.org; Sat, 26 May 2001 21:44:50 +0200 (CEST) (envelope-from schweikh) Date: Sat, 26 May 2001 21:44:50 +0200 From: Jens Schweikhardt To: freebsd-current@freebsd.org Subject: mutex panic Message-ID: <20010526214450.B1114@schweikhardt.net> 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 hello, world\n 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() Anything else I can do to track this down? Regards, Jens -- Jens Schweikhardt http://www.schweikhardt.net/ SIGSIG -- signature too long (core dumped) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message