From owner-freebsd-mobile@FreeBSD.ORG  Mon Dec  1 13:38:17 2003
Return-Path: <owner-freebsd-mobile@FreeBSD.ORG>
Delivered-To: freebsd-mobile@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 4C48E16A4CE
	for <freebsd-mobile@freebsd.org>;
	Mon,  1 Dec 2003 13:38:17 -0800 (PST)
Received: from ran.psg.com (ip166.usw253.dsl-acs2.sea.iinet.com
	[209.20.253.166])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 5A2AB4400D
	for <freebsd-mobile@freebsd.org>;
	Mon,  1 Dec 2003 13:38:09 -0800 (PST)	(envelope-from randy@psg.com)
Received: from localhost ([127.0.0.1] helo=ran.psg.com)
	by ran.psg.com with esmtp (Exim 4.22)
	id 1AQvk6-000B8m-BI; Mon, 01 Dec 2003 13:38:06 -0800
From: Randy Bush <randy@psg.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Date: Mon, 1 Dec 2003 13:38:05 -0800
To: Kevin Oberman <oberman@es.net>
References: <peter.schuller@infidyne.com>
	<200312010222.42940.peter.schuller@infidyne.com>
	<20031201213416.469935D04@ptavv.es.net>
Message-Id: <E1AQvk6-000B8m-BI@ran.psg.com>
cc: FreeBSD Laptoppers <freebsd-mobile@freebsd.org>
Subject: Re: thinkpad t40 4.0-stable won't resume 
X-BeenThere: freebsd-mobile@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Mobile computing with FreeBSD <freebsd-mobile.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-mobile>,
	<mailto:freebsd-mobile-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-mobile>
List-Post: <mailto:freebsd-mobile@freebsd.org>
List-Help: <mailto:freebsd-mobile-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-mobile>,
	<mailto:freebsd-mobile-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Dec 2003 21:38:17 -0000

> This sounds suspiciously like a problem that has cropped up in CURRENT
> with ATAng. It looks like an interrupt is lost on resume. If I have a
> single disk on the system, it hangs resetting that disk. If I have two
> disks, it hangs on the second one. Either way, it never returns from
> suspend.

this describes the symptom exactly

> On CURRENT, this only seems to show up with ACPI, but I don't think you
> are using ACPI on your system from the dmesg.

nope, -stable

randy