From owner-freebsd-mobile@FreeBSD.ORG Sun Jan 30 12:30:51 2005 Return-Path: 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 C0BD816A4CF for ; Sun, 30 Jan 2005 12:30:51 +0000 (GMT) Received: from relay02.pair.com (relay02.pair.com [209.68.5.16]) by mx1.FreeBSD.org (Postfix) with SMTP id 2228543D55 for ; Sun, 30 Jan 2005 12:30:49 +0000 (GMT) (envelope-from dwalton@acm.org) Received: (qmail 65247 invoked from network); 30 Jan 2005 12:30:47 -0000 Received: from unknown (HELO ?172.16.1.34?) (unknown) by unknown with SMTP; 30 Jan 2005 12:30:47 -0000 X-pair-Authenticated: 68.125.128.172 Message-ID: <41FCD342.2040905@acm.org> Date: Sun, 30 Jan 2005 04:29:54 -0800 From: Dave Walton User-Agent: Mozilla Thunderbird 1.0 (X11/20041208) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Gleb Smirnoff References: <41EF6101.7010008@acm.org> <20050120092812.GB16150@cell.sick.ru> <41F02F9A.40201@acm.org> <41F0A398.7080800@orel.ru> <41F4C6BD.4060406@acm.org> <41F4D7EE.9030108@orel.ru> <41F8C5EA.3040007@acm.org> <20050127140010.GA82418@cell.sick.ru> <41F94FAA.2070307@acm.org> <20050128075144.GA88243@cell.sick.ru> In-Reply-To: <20050128075144.GA88243@cell.sick.ru> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-mobile@freebsd.org cc: Andrew Belashov Subject: Re: Trouble with APM suspend in 5.3-R X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: dwalton@acm.org List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 30 Jan 2005 12:30:51 -0000 Gleb Smirnoff wrote: > On Thu, Jan 27, 2005 at 12:31:38PM -0800, Dave Walton wrote: > D> It was on, now that you mention it. Why do you ask? > > Can you try the attached patch? Ah, we've come full circle, back to this patch, but this time with the pcm panic out of the way. Well, with this patch added, it still locks up without an error message, but now the HDD LED is OFF when it happens. What's the next step? Thanks, Dave