From owner-freebsd-scsi Sat Dec 2 6:47:20 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from aslan.scsiguy.com (aslan.scsiguy.com [63.229.232.106]) by hub.freebsd.org (Postfix) with ESMTP id 284E137B400 for ; Sat, 2 Dec 2000 06:47:18 -0800 (PST) Received: from aslan (localhost [127.0.0.1]) by aslan.scsiguy.com (8.11.0/8.9.3) with ESMTP id eB2ElF487377; Sat, 2 Dec 2000 07:47:15 -0700 (MST) (envelope-from gibbs@aslan.scsiguy.com) Message-Id: <200012021447.eB2ElF487377@aslan.scsiguy.com> To: Kenneth Wayne Culver Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: kernel panics in 4.2 In-Reply-To: Your message of "Fri, 01 Dec 2000 17:26:49 EST." Date: Sat, 02 Dec 2000 07:47:15 -0700 From: "Justin T. Gibbs" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >I sent this message to -questions,-current, and -stable earlier, but >nobody seems to know about my problem: > >I just recently tried putting an adaptec 2940w SCSI controller into my >FreeBSD machine (running -STABLE cvsupped and recompiled every night at >1:30AM) and since including the driver in my kernel I've noticed some >random panics. It may be code displacement that has caused some uninilialized data to be hit. The SCSI driver will never be touched after the initial bus scan, so it is hard to believe that this is directly caused by the SCSI subsystem. You really need to capture the panic message in order for this to be debugged. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message