From owner-freebsd-stable@FreeBSD.ORG Thu Oct 26 17:09:44 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D537516A416; Thu, 26 Oct 2006 17:09:44 +0000 (UTC) (envelope-from adam@adamretter.eclipse.co.uk) Received: from mra02.ch.as12513.net (mra02.ch.as12513.net [82.153.254.70]) by mx1.FreeBSD.org (Postfix) with ESMTP id 49F5E43D55; Thu, 26 Oct 2006 17:09:43 +0000 (GMT) (envelope-from adam@adamretter.eclipse.co.uk) Received: from localhost (localhost [127.0.0.1]) by mra02.ch.as12513.net (Postfix) with ESMTP id B44DED4BC7; Thu, 26 Oct 2006 18:09:41 +0100 (BST) Received: from mra02.ch.as12513.net ([127.0.0.1]) by localhost (mra02.ch.as12513.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 08939-01-16; Thu, 26 Oct 2006 18:09:39 +0100 (BST) Received: from webmail03.ch.as12513.net (webmail03.ch.as12513.net [82.153.254.77]) by mra02.ch.as12513.net (Postfix) with ESMTP id 62C23D4B8B; Thu, 26 Oct 2006 18:09:37 +0100 (BST) Content-Disposition: inline Content-Transfer-Encoding: quoted-printable From: To: Benjamin Lutz , Thomas Quinot Date: Thu, 26 Oct 2006 18:09:37 +0100 X-Uidl: 20061026091854.GB31681@melamine.cuivre.fr.eu.org X-Mailer: AtMail 4.3 Message-Id: <20061026170937.62C23D4B8B@mra02.ch.as12513.net> X-Virus-Scanned: by Eclipse VIRUSshield at eclipse.net.uk MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-stable@freebsd.org Subject: Re: atapicam problem X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: adam@adamretter.eclipse.co.uk List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 Oct 2006 17:09:44 -0000 Thomas, do you think this could be related to the problem I= had with atapi_cam slowing my machine down to an unuseable state? &n= bsp; Thanks Adam. On Thu Oct 26 9:18 , Thomas Qui= not sent: =0D > Well, I'm having problems with that. I built a new kernel with all the= =0D > CAM debugging options enabled (otherwise it's GENERIC), but this one <= br />=0D > would panic as soon as I load the atapicam module if I load it = =0D > manually, or as soon as drive detection starts if the boot loader load= s =0D > it. I've had a look at the dump with kgdb, and it appears that a =0D > null-dereference happens in line 4205 of sys/cam/cam_xpt.c: path2 is <= br />=0D > NULL. =0D =0D OK, sorry for the delay, can you apply the attached patch and try again? =0D =0D Thomas. =0D =0D =0D