From owner-freebsd-scsi Fri Sep 6 10:08:22 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA13359 for freebsd-scsi-outgoing; Fri, 6 Sep 1996 10:08:22 -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 KAA13347 for ; Fri, 6 Sep 1996 10:08:19 -0700 (PDT) Received: (from gordon@localhost) by unicorn.uk1.vbc.net (8.7.3/8.7.3) id SAA01065; Fri, 6 Sep 1996 18:08:15 +0100 Date: Fri, 6 Sep 1996 18:08:15 +0100 (BST) From: Gordon Henderson X-Sender: gordon@unicorn To: "Justin T. Gibbs" cc: freebsd-scsi@freebsd.org Subject: Re: CCD Setup woes ... (Kernel Panic) In-Reply-To: <199609061625.JAA05107@freefall.freebsd.org> Message-ID: Distribution: world Organization: Home for lost Drogons MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Fri, 6 Sep 1996, Justin T. Gibbs wrote: > > 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 > > A stack trace would be helpfull in tracking this down. Put DDB in your > kernel (options DDB) and use the 'trace' command when the panic occurs. I'm having to copy this over by hand, but it goes: _Debugger _panic _vm_bounce_alloc _sd_strategy _scsi_strategy _sdstrategy _spec_strategy _ccdstart _ccdstrategy _correct_readdisklabel _ccdgetdisklabel _ccdioctl _spec_ioctl _vm_ioctl _ioctl _syscall It's FreeBSD 2.1.5R... Gordon -- Gordon Henderson gordon@vbc.net VBCnet GB Ltd http://www.uk.vbc.net/ Bristol, England +44 117 929 1316 fax +44 117 927 2015