From owner-freebsd-questions Fri Sep 6 08:55:19 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA03042 for questions-outgoing; Fri, 6 Sep 1996 08:55:19 -0700 (PDT) Received: from unicorn.uk1.vbc.net (unicorn.uk1.vbc.net [204.137.194.11]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id IAA03035; Fri, 6 Sep 1996 08:55:15 -0700 (PDT) Received: (from gordon@localhost) by unicorn.uk1.vbc.net (8.7.3/8.7.3) id QAA00717; Fri, 6 Sep 1996 16:54:34 +0100 Date: Fri, 6 Sep 1996 16:54:34 +0100 (BST) From: Gordon Henderson X-Sender: gordon@unicorn To: questions@freebsd.org, scsi@freebsd.org Subject: CCD Setup woes ... (Kernel Panic) Message-ID: Distribution: world Organization: Home for lost Drogons MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I'm tring to get a CCD going as an experiment and it's causing the kernel to panic. The hardware is: ASUS P120 motherboard, 128MB RAM, crappy old Adaptec ISA card (aha driver) and 3 x Maxtor 2GB drives. (ISA video, no ether yet) I'm using the adaptec card until I get some decent buslogic PCI cards. (I've had LOTS of problems with Adaptec 2940 PCI cards!) Drive 0 is the root disk and has /, swap, /usr and /var. Drives 1 & 2 are setup identical, 64MB swap partition (b) and the rest empty (partition f) for the ccd. (I'm not using the swap partitions yet, but read that it was a bad thing the have the ccd partitions at the start of the disk) I built a kernel with the ccd driver present as it says in the man page, did a cd /dev ; sh MAKEDEV ccd0 with no problems. Then I did: ccdconfig -c -v ccd0 32 none /dev/sd1f /dev/sd2f which resulted in a kernel panic. The message is: vm_bounce_alloc: b_bufsize(0x80) < b_count(0x200) !! panic: vm_bounce_alloc followed by the usual syncing disks bit. The number in the b_bufsize() varies from crash to crash. Am I doing anything obviously wrong? Gordon