From owner-freebsd-scsi Tue Jul 29 17:26:29 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id RAA24270 for freebsd-scsi-outgoing; Tue, 29 Jul 1997 17:26:29 -0700 (PDT) Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA24264 for ; Tue, 29 Jul 1997 17:26:27 -0700 (PDT) Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5]) by mail.cdsnet.net (8.8.6/8.8.6) with SMTP id RAA18411; Tue, 29 Jul 1997 17:26:21 -0700 (PDT) Date: Tue, 29 Jul 1997 17:26:21 -0700 (PDT) From: Jaye Mathisen To: Simon Shapiro cc: scsi@FreeBSD.ORG Subject: RE: DPT crashes In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Tue, 29 Jul 1997, Simon Shapiro wrote: > > I need to see things like the DPT options you configured the kernel with, > firmware level, controller model, RAID configuration, motherboard type, > slot number in the machine, did you manage to re-boot the machine? > did it happen again? Versipon of the driver, etc. I'm using the DPT kernel config file that came with the patch. Controller is a PM3334UW, connected to 3 4GB Barracuda's, running RAID-5. Motherboard is a Digital Prioris HX6000 (intel if I recall), it's in slot 1 of the primary PCI bus. The firmware is dated March 1997, I think it's 07L0. The system reboots fine. I'm using 2.2.2 with the 1.10 patch. It just happened again, which is interesting, because I can sup -current just fine, but it crashes so far each time I cvsup 2.2.2... Can't imagine there's a correlation, but it's interesting. > > The error message you report is a catchall at the end of the case statement. > IOW, something we really know nothing about. > > If it happens regularly, you may want to activate few options in the > kernel, to see if we can catch the error in a better defined light. > > > Waited several minutes, rebooted, and it came up. > > > > > > BTW, the -current patch in /crash doesn't seem to apply to a real > > -current, or at least, it won't on mine, while the 2.2.2 patch applies > > fine. > > By definition, -current is a moving target. We make no particular effort > here to track it with patches. Once we put the driver in the kernel, we > will be obliged to update it. The mechanisms to do so are in place. > 2.2 is a ``stable'' release and API's are not supposed to change. > Another reason for the -current ``neglect'' is that we anticipate a major > re-write of the SCSI layer in 3.0, and with it a major work on the DPT > driver. We simply do not have time to track all three threads. > > > > > On Tue, 29 Jul 1997, Simon Shapiro wrote: > > > > > > > > Hi Jaye Mathisen; On 28-Jul-97 you wrote: > > > > > > > > > > > > Just died with 2.2.2 with DPT: Undocumented error" during a CVSUP > > > > of the world from my local cvsup mirror. > > > > > > Nurse: Dr. The patient is sick. > > > Dr.: Give him two aspirins and call me in the morning. > > > Lawyer: Good! > > > > > > Undocumented error is exactly that. An error which i do not know what > > it > > > is. i could guess all day long but would prefer more data :-) > > > > > > Simon > > > > > >