From owner-freebsd-current@FreeBSD.ORG Tue Sep 16 23:26:51 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8516016A4B3 for ; Tue, 16 Sep 2003 23:26:51 -0700 (PDT) Received: from spider.deepcore.dk (cpe.atm2-0-56339.0x50c6aa0a.abnxx2.customer.tele.dk [80.198.170.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1AB6843FB1 for ; Tue, 16 Sep 2003 23:26:48 -0700 (PDT) (envelope-from sos@spider.deepcore.dk) Received: from spider.deepcore.dk (localhost [127.0.0.1]) by spider.deepcore.dk (8.12.9/8.12.9) with ESMTP id h8H6Qdj5008813; Wed, 17 Sep 2003 08:26:39 +0200 (CEST) (envelope-from sos@spider.deepcore.dk) Received: (from sos@localhost) by spider.deepcore.dk (8.12.9/8.12.9/Submit) id h8H6QNrM008812; Wed, 17 Sep 2003 08:26:23 +0200 (CEST) From: Soren Schmidt Message-Id: <200309170626.h8H6QNrM008812@spider.deepcore.dk> In-Reply-To: <3F678E6C.3060204@ludd.luth.se> To: =?ISO-8859-1?Q?Joachim_Str=F6mbergson?= Date: Wed, 17 Sep 2003 08:26:23 +0200 (CEST) X-Mailer: ELM [version 2.4ME+ PL99f (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=ISO-8859-1 X-mail-scanned: by DeepCore Virus & Spam killer v1.3 cc: Arjan van Leeuwen cc: current@FreeBSD.ORG Subject: Re: ATAng hangs with kernel from september 15 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Sep 2003 06:26:51 -0000 It seems Joachim Strömbergson wrote: > > Thanks! I guess I'm too impatient these days... Yes, it works after waiting > > for about 30 seconds. So a correction, it doesn't hang, it's just slow when > > detecting :). > > So now the tousand dollar question becomes "What in the boot contains a > timeout around 30 seconds, a timout that lately has been > committed/ctivated in the kernel code?" Well, the ATA driver has just grown more standard compliant :) You *must* hang around for 31secs to wait for slow devices to come ready, according to the ATA specs. Now I've gone to great length before to get around this by using clever heuristics, and I'm getting there again, but there are *so* many crappy devices out there that it takes time to accomodate them all. So if you experience long boot delays or misprobes, please boot verbose and mail me the output from dmesg with a subject of "ATA probe fails" and a short description of what is wrong, and I'll try to work in a solution for the problem. (And no I wont ever go the white/black-list route as others have gone). -Søren