From owner-freebsd-current Thu Mar 23 13:48:12 2000 Delivered-To: freebsd-current@freebsd.org Received: from mass.cdrom.com (mg-20425418-10.ricochet.net [204.254.18.10]) by hub.freebsd.org (Postfix) with ESMTP id C305F37BB2B for ; Thu, 23 Mar 2000 13:47:56 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id NAA02123; Thu, 23 Mar 2000 13:50:29 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <200003232150.NAA02123@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: mw@kpnqwest.ch Cc: freebsd-current@freebsd.org Subject: Re: AMI MegaRAID lockup? not accepting commands. In-reply-to: Your message of "Thu, 23 Mar 2000 20:40:27 +0100." <200003231940.TAA24686@mail.kpnqwest.ch> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 23 Mar 2000 13:50:28 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I've played around changing the spinloop to using DELAY (like the Linux model), > but this didn't prevent the controller from either "just" locking up or > crashing the whole machine with it. Changing various other places in a similar > manner (like replacing the bcopy() in amr_quartz_get_work() with similar > code as in the linux driver to wait for 0xFF to clear) didn't do the trick > either. Can you try instead the changes that I just committed to -current? I think that the problem shows up when the controller is heavily loaded; your patch will keep the load on the controller down, which may mask the 'real' bug. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message