Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 30 May 2000 13:40:35 +0800 (+0800)
From:      Michael Robinson <robinson@netrinsics.com>
To:        freebsd-stable@freebsd.org
Subject:   panic: blst_radix_free: freeing free block
Message-ID:  <200005300540.NAA48935@netrinsics.com>

next in thread | raw e-mail | index | archive | help
On a stock 4.0-RELEASE kernel, if I uncomment the second swap partition in
the following fstab, I get a panic on boot immediately after the "adding swap"
message for the first swap partition.

  # Device                Mountpoint      FStype  Options         Dump    Pass#
  /dev/da0s1b             none            swap    sw              0       0
  #/dev/da1s1b            none            swap    sw              0       0
  /dev/da0s1a             /               ufs     rw              1       1
  /dev/da0s1e             /usr            ufs     rw              2       2
  /dev/da1s1e             /data           ufs     rw              2       2
  /dev/acd0c              /cdrom  cd9660  ro,noauto       0       0
  proc                    /proc           procfs  rw              0       0

The panic message is:

  panic: blst_radix_free: freeing free block

However, if I manually run "swapon /dev/da1s1b" after booting, everything
runs normally.

This is on an Intel L440GX motherboard with 1GB of ECC RAM, and the following
disklabels:

  # /dev/rda0s1c:

  8 partitions:
  #        size   offset    fstype   [fsize bsize bps/cpg]
    a:    81920        0    4.2BSD     1024  8192    16   # (Cyl.    0 - 5*)
    b:  1058592    81920      swap                        # (Cyl.    5*- 70*)
    c: 17912412        0    unused        0     0         # (Cyl.    0 - 1114*)
    e: 16771900  1140512    4.2BSD     1024  8192    16   # (Cyl.   70*- 1114*)

  # /dev/rda1s1c:

  8 partitions:
  #        size   offset    fstype   [fsize bsize bps/cpg]
    a:    81920        0    4.2BSD     1024  8192    16   # (Cyl.    0 - 5*)
    b:  1058592    81920      swap                        # (Cyl.    5*- 70*)
    c: 17912412        0    unused        0     0         # (Cyl.    0 - 1114*)
    e: 16771900  1140512    4.2BSD     1024  8192    16   # (Cyl.   70*- 1114*)

Is this due to a known operator screwup, a known problem that's been fixed, a 
known problem that isn't fixed, or a new unknown problem?

	-Michael Robinson



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




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200005300540.NAA48935>