From owner-freebsd-current  Mon Jun 18 18:51:35 2001
Delivered-To: freebsd-current@freebsd.org
Received: from wantadilla.lemis.com (wantadilla.lemis.com [192.109.197.80])
	by hub.freebsd.org (Postfix) with ESMTP id DA3EF37B401
	for <freebsd-current@freebsd.org>; Mon, 18 Jun 2001 18:51:30 -0700 (PDT)
	(envelope-from grog@lemis.com)
Received: by wantadilla.lemis.com (Postfix, from userid 1004)
	id 06B126ACBC; Tue, 19 Jun 2001 11:21:25 +0930 (CST)
Date: Tue, 19 Jun 2001 11:21:24 +0930
From: Greg Lehey <grog@FreeBSD.org>
To: Chad David <davidc@acns.ab.ca>
Cc: freebsd-current@freebsd.org
Subject: Re: panic from May
Message-ID: <20010619112124.B58585@wantadilla.lemis.com>
References: <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
In-Reply-To: <20010616152239.A4458@colnta.acns.ab.ca>; from davidc@acns.ab.ca on Sat, Jun 16, 2001 at 03:22:39PM -0600
Organization: The FreeBSD Project
Phone: +61-8-8388-8286
Fax: +61-8-8388-8725
Mobile: +61-418-838-708
WWW-Home-Page: http://www.FreeBSD.org/
X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF  13 24 52 F8 6D A4 95 EF
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-current.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-current>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-current>
X-Loop: FreeBSD.ORG

On Saturday, 16 June 2001 at 15:22:39 -0600, Chad David wrote:
> 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?

Sorry, I don't understand that.

> Would a recent kernel over the existing userland have any hope
> between then and now?

Maybe.

If you're using -CURRENT, you should expect this kind of problem.  And
we expect that you try to solve it yourself.  There are very few
people who are interested in problems you might have with a month old
-CURRENT.  

The first thing you should do is update to real -CURRENT sources.  Try
again.  If it still happens, climb into the dump and have a good look
round.

Greg
--
See complete headers for address and phone numbers

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message