From owner-freebsd-scsi Fri Sep 5 13:00:18 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id NAA28383 for freebsd-scsi-outgoing; Fri, 5 Sep 1997 13:00:18 -0700 (PDT) Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA28240; Fri, 5 Sep 1997 12:58:53 -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 MAA09927; Fri, 5 Sep 1997 12:58:47 -0700 (PDT) Date: Fri, 5 Sep 1997 12:58:45 -0700 (PDT) From: Jaye Mathisen To: Steve Passe cc: scsi@FreeBSD.ORG, smp@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: Scary DPT problem. In-Reply-To: <199709051909.NAA14813@Ilsa.StevesCafe.com> 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 My apologies. I'm well aware of the purpose of -current vs -stable. I was more concerned with the fact that it appears to be possible to get the DPT controller so scrambled up that a simple reboot doesn't reset it. Not anything with SMP/3.0... FWIW, I can still crash SMP/3.0 if I bump up InetLoad high enough, but I still can't crash a 3.0-uniprocessor kernel with no MAXMEM... Haven't supped since yesterday, given the headaches of applying the DPT patches all the time to the sys tree. I don't see this so much as a 3.0 problem, as a DPT issue, but I could be off base. Wouldn't be the first time... :0 On Fri, 5 Sep 1997, Steve Passe wrote: > Hi, > > > Using DPT-1.2.4 with 3.0/SMP. > > > > I was running a test of adding 25000 accounts and removing them, and > > making sure everything was hunky-dory, when the dreaded: > > > > "DPT: Undocumented Error" > > db> > > > > Occurs. > > > > OK, Happened in the past. Hit the reset switch: "No Operating System". > > Power-Cycle "No Operating System". Swear, curse, cry, yell, shake. > > > > Power-cycle it, and let it sit. It finally reboots, but the passwd file > > .db's are completely hosed. and /etc/group is a goner. > > > > Makes me nervous to deploy this out in the sticks... I'm hoping it's just > > an SMP or 3.0-current problem, as opposed to some deep dark nasty DPT > > issue. > > SMP-current should definitely NOT be used for anything critical right now! > We KNOW we have a show-stopper in there... It probably affects ALL SMP > systems, just bites some earlier than others. > > On the bright side, we are closing in on it, and hopefully will have a > resolution by later today (no promises). > -- > Steve Passe | powered by > smp@csn.net | Symmetric MultiProcessor FreeBSD > >