From owner-freebsd-current  Wed May 24 16:33:20 1995
Return-Path: current-owner
Received: (from majordom@localhost)
          by freefall.cdrom.com (8.6.10/8.6.6) id QAA27307
          for current-outgoing; Wed, 24 May 1995 16:33:20 -0700
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.34])
          by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id QAA27293
          for <current@freebsd.org>; Wed, 24 May 1995 16:33:13 -0700
Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id JAA05634; Thu, 25 May 1995 09:28:32 +1000
Date: Thu, 25 May 1995 09:28:32 +1000
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199505242328.JAA05634@godzilla.zeta.org.au>
To: pb@fasterix.freenix.fr
Subject: Re: kern/438: panic: vwakeup: neg numoutput
Cc: current@FreeBSD.org
Sender: current-owner@FreeBSD.org
Precedence: bulk

>	Panic when trying to disklabel the IDE drive attached on the
>	'diskless' PC.

>>How-To-Repeat:

>	# disklabel -w -r /dev/wd0s2 labelname

>-> console messages
>	fixlabel: invalid magic
>	fixlabel: invalid magic
>	panic: vwakeup: neg numoutput

The panic will be fixed soon.

I can't duplicate the messages from fixlabel().  They indicate that
disklabel has constructed a bogus label or that fixlabel() has been
passed the wrong label pointer.

>	Notes:

>		- I used wd0s2. That's obviously wrong, but I'm not sure
>		  that's relevant.

wd0s2 would have been correct (disklabel converts it to /dev/rwd0s2c ==
/dev/rwd0s2), but /dev/wd0s2 is the block device, and there is a bug for
the block device in the label fixup code.

Bruce