From owner-freebsd-current Sat Oct 2 6:39:55 1999 Delivered-To: freebsd-current@freebsd.org Received: from pozo.com (pozo.com [216.101.162.50]) by hub.freebsd.org (Postfix) with ESMTP id AE9B415254 for ; Sat, 2 Oct 1999 06:39:51 -0700 (PDT) (envelope-from mantar@pacbell.net) Received: from dual (dual.pozo.com [216.101.162.51]) by pozo.com (8.9.3/8.9.3) with ESMTP id GAA00241; Sat, 2 Oct 1999 06:39:36 -0700 (PDT) (envelope-from mantar@pacbell.net) Message-Id: <4.2.1.9.19991002063849.00a97330@216.101.162.50> X-Sender: null@216.101.162.50 X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.1.9 (Beta) Date: Sat, 02 Oct 1999 06:39:36 -0700 To: Poul-Henning Kamp , A.Leidinger@WJPServer.CS.Uni-SB.de From: Manfred Antar Subject: Re: ahc failure while updating from pre-signal-change Cc: current@FreeBSD.ORG In-Reply-To: <17657.938863152@critter.freebsd.dk> References: <"Your message of Sat, 02 Oct 1999 11:39:24 +0200." <199910020939.LAA01186@work.net.local> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 01:19 PM 10/02/99 +0200, Poul-Henning Kamp wrote: >Ok, I've committed what I belive is a fix for the problem. It was not >the locking as Bruce suggested, although his suggestion still has a point, >it was si_iosize_max which was uninitialized, which confuses minphys >and subsequently various other stuff. My problem with locking up on startup is now gone Thanks Manfred ===================== || mantar@pacbell.net || || Ph. (415) 681-6235 || ===================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message