From owner-freebsd-stable Mon May 29 22:42: 0 2000 Delivered-To: freebsd-stable@freebsd.org Received: from public.bta.net.cn (public.bta.net.cn [202.96.0.97]) by hub.freebsd.org (Postfix) with ESMTP id 5A5F037B88E for ; Mon, 29 May 2000 22:40:43 -0700 (PDT) (envelope-from robinson@netrinsics.com) Received: from netrinsics.com ([202.108.133.69]) by public.bta.net.cn (8.9.3/8.9.3) with ESMTP id NAA16080 for ; Tue, 30 May 2000 13:36:52 +0800 (GMT) Received: (from robinson@localhost) by netrinsics.com (8.9.3/8.9.3) id NAA48935 for freebsd-stable@freebsd.org; Tue, 30 May 2000 13:40:35 +0800 (+0800) (envelope-from robinson) Date: Tue, 30 May 2000 13:40:35 +0800 (+0800) From: Michael Robinson Message-Id: <200005300540.NAA48935@netrinsics.com> To: freebsd-stable@freebsd.org Subject: panic: blst_radix_free: freeing free block Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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