From owner-freebsd-current Thu Jun 4 08:15:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA23317 for freebsd-current-outgoing; Thu, 4 Jun 1998 08:15:17 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sendero.simon-shapiro.org (sendero.simon-shapiro.org.142.69.207.in-addr.arpa [207.69.142.25] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id IAA23249 for ; Thu, 4 Jun 1998 08:14:57 -0700 (PDT) (envelope-from shimon@sendero.simon-shapiro.org) Received: (qmail 11909 invoked by uid 1000); 4 Jun 1998 16:16:35 -0000 Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <19980604095717.A22406@freebie.lemis.com> Date: Thu, 04 Jun 1998 12:16:35 -0400 (EDT) Reply-To: shimon@simon-shapiro.org Organization: The Simon Shapiro Foundation From: Simon Shapiro To: Greg Lehey Subject: Re: DPT driver fails and panics with Degraded Array Cc: Michael Hancock , "freebsd-current@freebsd.org" , tcobb , Karl Pielorz , Bob Willcox , Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 04-Jun-98 Greg Lehey wrote: ... >>> I had to put some pretty ugly validity checks in the interrupt code to >>> prevent my driver from trying to do an iodone (AIX's version of >>> biodone) >>> on already completed (or purged, I don't remember for sure...its been >>> over a year now) commands. Seems that the DPT firmware would (on >>> occasion) interrupt with a status packet that pointed to a ccb that my >>> driver had already completed. As I recall this would only happen under >>> heavy load and it was pretty intermittant. As far as I know, it was >>> never actually fixed. >> >> Actually, this is *extremely* relevant, if the firmware is still doing >> it and the DPT driver isn't aware of this. > > This would normally cause a 'biodone: buffer already done' message, > which is a warning, not a panic. The only way I could think of this > happening on a valid buffer (apart from the obvious of calling it > while it wasn't busy) would be if something messed around with other > buffer flags. I haven't been following this thread very > carefully--were the panics associated with SMP only? If so, how is > mutual exclusion performed in the bottom half of SMP drivers? Actually this is a 2.2 (UP :-) problem. Not a 3.0, and not an SMP for sure. Actually, SMP interrupt service is slow enough that this probably never has a chance to show at all. Simon (We are getting about 2/3 the interrupts/sec under SMP. Last we checked which was about 2 months ago). --- Sincerely Yours, Simon Shapiro Shimon@Simon-Shapiro.ORG 770.265.7340 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message