From owner-freebsd-questions Sun Dec 10 14:53:48 2000 From owner-freebsd-questions@FreeBSD.ORG Sun Dec 10 14:53:47 2000 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from aslan.scsiguy.com (aslan.scsiguy.com [63.229.232.106]) by hub.freebsd.org (Postfix) with ESMTP id C983D37B400 for ; Sun, 10 Dec 2000 14:53:46 -0800 (PST) Received: from aslan (localhost [127.0.0.1]) by aslan.scsiguy.com (8.11.0/8.9.3) with ESMTP id eBAMrh480538; Sun, 10 Dec 2000 15:53:44 -0700 (MST) (envelope-from gibbs@aslan.scsiguy.com) Message-Id: <200012102253.eBAMrh480538@aslan.scsiguy.com> To: Kenneth Wayne Culver Cc: freebsd-questions@FreeBSD.ORG Subject: Re: kernel panic in 4.2 with AHA-2940 In-Reply-To: Your message of "Sat, 09 Dec 2000 14:01:58 EST." Date: Sun, 10 Dec 2000 15:53:43 -0700 From: "Justin T. Gibbs" Sender: gibbs@aslan.scsiguy.com Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >I don't know where to go from here though, I have absolutely no idea why >cnp->cn_nameptr would be NULL, or how any of this could be caused >by the SCSI driver, but I know it is the ahc driver's fault >because when I take that driver out of the kernel, everything >works fine again. Anyway, any help is appreciated. > >Ken That doesn't mean that it is the ahc driver's fault. Just by moving the data-segment around by adding *any* driver, could cause a bug to manifest. None of the panic's I've seen so far have anything to do with the ahc driver and since you've said that the controller is not even in use, I can't see how it can be the root cause of the problem. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message