From owner-freebsd-current  Sat Mar 17 10:52:24 2001
Delivered-To: freebsd-current@freebsd.org
Received: from mail.virtual-estates.net (video-collage.com [160.79.196.177])
	by hub.freebsd.org (Postfix) with ESMTP id B681137B719
	for <current@freebsd.org>; Sat, 17 Mar 2001 10:52:21 -0800 (PST)
	(envelope-from mi@mail.virtual-estates.net)
Received: (from mi@localhost)
	by mail.virtual-estates.net (8.9.3+3.2W/8.9.3) id NAA28619
	for current@freebsd.org; Sat, 17 Mar 2001 13:43:04 -0500 (EST)
From: Mikhail Teterin <mi@mail.virtual-estates.net>
Message-Id: <200103171843.NAA28619@mail.virtual-estates.net>
Subject: another panic (doscmd)
To: current@freebsd.org
Date: Sat, 17 Mar 2001 13:43:04 -0500 (EST)
Reply-To: mi+freebsd@virtual-estates.net
X-Mailer: ELM [version 2.4ME+ PL60 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Hello!

I was not able to obtain a trace :( The panic mechanism itself went into
an infinite loop continuously displaying

	kern_sync.c:385 sleeping with "panic" locked from kern_shutdown.c:544

as fast as it could :-( All I did was (as a regular user):

	doscmd r4d1di.exe

The r4d1di.exe can be found here:

	http://aldan.algebra.com:8015/~mi/doscmd-crash/r4d1di.exe

(it is a stupid self-extracting executable).

	-mi

P.S. BTW, any news on the two panics I reported earlier:

	Attempts to run a staticly linked Linux binary panic a regular
	kernel, or cause the binary to seg-fault on the one with INVARIANTS
	and WITNESS:
		http://aldan.algebra.com:8015/~mi/civctp-crash/

	Attemps to mount an msdos-floppy cause panic:
		http://aldan.algebra.com:8015/~mi/mount_msdos-crash/

P.P.S. hub.freebsd.org has strange difficulties with the algebra.com domain.
If you are trying to reach me, try mi+freebsd@virtual-estates.net. Sorry.

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