From owner-freebsd-current@FreeBSD.ORG  Thu Jan  6 11:48:39 2005
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
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 B1B0D16A4CE
	for <freebsd-current@freebsd.org>;
	Thu,  6 Jan 2005 11:48:39 +0000 (GMT)
Received: from critter.freebsd.dk (f170.freebsd.dk [212.242.86.170])
	by mx1.FreeBSD.org (Postfix) with ESMTP id E60B443D31
	for <freebsd-current@freebsd.org>;
	Thu,  6 Jan 2005 11:48:38 +0000 (GMT)
	(envelope-from phk@critter.freebsd.dk)
Received: from critter.freebsd.dk (localhost [127.0.0.1])
	by critter.freebsd.dk (8.13.1/8.13.1) with ESMTP id j06BmT0i053363;
	Thu, 6 Jan 2005 12:48:29 +0100 (CET)
	(envelope-from phk@critter.freebsd.dk)
To: Nate Lawson <nate@root.org>
From: "Poul-Henning Kamp" <phk@phk.freebsd.dk>
In-Reply-To: Your message of "Thu, 06 Jan 2005 01:43:37 PST."
             <41DD0849.9010006@root.org> 
Date: Thu, 06 Jan 2005 12:48:29 +0100
Message-ID: <53362.1105012109@critter.freebsd.dk>
Sender: phk@critter.freebsd.dk
cc: FreeBSD Current <freebsd-current@freebsd.org>
cc: "M. Warner Losh" <imp@bsdimp.com>
Subject: Re: Extra long time resuming -current 
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 06 Jan 2005 11:48:39 -0000

In message <41DD0849.9010006@root.org>, Nate Lawson writes:

>When I updated to a recent -current, my laptop takes a very long time to 
>resume (20 seconds) whereas before it took about 2 seconds.  I suspect 
>the PCI device probe delay capability you added triggered this.  Perhaps 
>the PCI resume code queries the register, gets all ones since the bus is 
>not active yet, and takes the maximum delay for each device access?

It's ata-disk timeouts.  I saw it yesterday as well.

-- 
Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
phk@FreeBSD.ORG         | TCP/IP since RFC 956
FreeBSD committer       | BSD since 4.3-tahoe    
Never attribute to malice what can adequately be explained by incompetence.