From owner-freebsd-stable Fri May 14 16: 1:39 1999 Delivered-To: freebsd-stable@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 674D514E0B for ; Fri, 14 May 1999 16:01:33 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id RAA47272; Fri, 14 May 1999 17:00:33 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id RAA37025; Fri, 14 May 1999 17:01:28 -0600 (MDT) Message-Id: <199905142301.RAA37025@harmony.village.org> To: jack Subject: Re: Found a Fix (was: Is aha broken?) Cc: freebsd-stable@FreeBSD.ORG In-reply-to: Your message of "Fri, 14 May 1999 18:44:57 EDT." References: Date: Fri, 14 May 1999 17:01:27 -0600 From: Warner Losh Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message jack writes: : I installed 3.2-19990514-BETA onto another box today and ran into : the same thing. Dang. :-( : The all powerful DELAY(10000) fixes it for both of my boxes. :) Cool. I can't find anything in the docs that would explain why this delay is needed. Did you try the less powerful DELAY(1000) or DELAY(100)? 10mS is a long time to spin in the kernel (granted, it is only on the probe, but there are moves afoot to make that happen at any time now). There were similar delays in the old aha driver, but I seem to recall they were in different locations. I'm committing this fix (as soon as alc's lock in src/sys/dev/aha is released). It is a very strong 3.2 candidate for merging. What's the deadline for merge? Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message