From owner-freebsd-current@FreeBSD.ORG Sat Oct 18 14:19:35 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C766816A4B3 for ; Sat, 18 Oct 2003 14:19:35 -0700 (PDT) Received: from ipng.org.uk (public1-blac3-3-cust241.manc.broadband.ntl.com [213.106.20.241]) by mx1.FreeBSD.org (Postfix) with ESMTP id 08B2843FB1 for ; Sat, 18 Oct 2003 14:19:31 -0700 (PDT) (envelope-from stu@ipng.org.uk) Received: from stu by ipng.org.uk with local (Exim 4.22) id 1AAyTU-0005HX-7e for freebsd-current@freebsd.org; Sat, 18 Oct 2003 22:19:00 +0100 Date: Sat, 18 Oct 2003 22:19:00 +0100 From: Stuart Walsh To: freebsd-current@freebsd.org Message-ID: <20031018211900.GA19175@deepfreeze.stu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.4i Subject: atapicam related panic X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 18 Oct 2003 21:19:35 -0000 Hi, I have an easily reproducable panic when using atapicam. Vague trace follows: panic was caused by this: KASSERT(bp->b_flags & B_PHYS, ("vmapbuf")); trace: vmapbuf cam_periph xptioctl spec_ioctl spec_vnoperate vn_ioctl ioctl syscall Let me know if you need any further information, this panic is easily reproducable for me(cdrecord --scanbus is enough). Regards, Stuart