From owner-freebsd-current Thu Sep 24 21:33:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA24197 for freebsd-current-outgoing; Thu, 24 Sep 1998 21:33:23 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA24192 for ; Thu, 24 Sep 1998 21:33:21 -0700 (PDT) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.9.1/8.7.3) id WAA00895; Thu, 24 Sep 1998 22:26:45 -0600 (MDT) Date: Thu, 24 Sep 1998 22:26:45 -0600 (MDT) From: "Justin T. Gibbs" Message-Id: <199809250426.WAA00895@narnia.plutotech.com> To: shimon@simon-shapiro.org cc: current@FreeBSD.ORG Subject: Re: options DPT_LOST_IRQ Newsgroups: pluto.freebsd.current In-Reply-To: User-Agent: tin/pre-1.4-971204 (UNIX) (FreeBSD/3.0-BETA (i386)) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> > This looks like an "Atlas II firmware of death" problem, not a DPT >> > problem. What firmware are you using? Before switching to LYK8, I >> > saw similar behavior on an Adaptec controller with an AtlasII. >> > >> > -- >> > Justin ... >> Right now I have the LX80 firmware. Thanks > > Although I have had my generous share of grief with these drives (I never > touch them but people seem to like them, this particular problem is not > drive induced. LX80 is known to be bogus. I would not be at all surprised if Adam is not seeing a lost interrupt problem at all. This is not to say that the lost interrupt problem doesn't exist, but I'd feel better about diagnosing Adam's problem if his drive's firmware was up to date. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message