Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 29 Jul 1997 17:26:21 -0700 (PDT)
From:      Jaye Mathisen  <mrcpu@cdsnet.net>
To:        Simon Shapiro <Shimon@i-Connect.Net>
Cc:        scsi@FreeBSD.ORG
Subject:   RE: DPT crashes
Message-ID:  <Pine.NEB.3.95.970729171718.938T-100000@mail.cdsnet.net>
In-Reply-To: <XFMail.970729170958.Shimon@i-Connect.Net>

next in thread | previous in thread | raw e-mail | index | archive | help


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
> > > 
> > 
> 




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.NEB.3.95.970729171718.938T-100000>