From owner-freebsd-current  Fri Jan 19 04:13:14 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id EAA11281
          for current-outgoing; Fri, 19 Jan 1996 04:13:14 -0800 (PST)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id EAA11275
          for <freebsd-current@freebsd.org>; Fri, 19 Jan 1996 04:12:57 -0800 (PST)
Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id WAA03698; Fri, 19 Jan 1996 22:58:38 +1100
Date: Fri, 19 Jan 1996 22:58:38 +1100
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199601191158.WAA03698@godzilla.zeta.org.au>
To: jdli@linux.csie.nctu.edu.tw, phk@critter.tfs.com
Subject: Re: [bug?] change in subr_diskslice.c
Cc: freebsd-current@freebsd.org
Sender: owner-current@freebsd.org
Precedence: bulk

>> [new kernel panic info from log]
>> dsinit
>> Debugger("Slice code got negative blocknumber") called.
>This is bad in the first place.  Can I get you to compile DDB into your
>kernel and email a traceback to dyson@freebsd.org and phk@freebsd.org

This may be caused by garbage block numbers in the extended partition
tables.  These aren't checked because they must be relied on.

>> sd1s1s2s3s4s5s1s2s4s5s6s4s1s2s5s2s1s2s4s5: error reading extended
>This isn't too good either  I belive I have a bug in the sprintf somewhere...

I think sprintf() forgets to null-terminate the string, but I can't
explain where "sd1s1s2..." came from.

Bruce