From owner-freebsd-mobile@FreeBSD.ORG Thu Jan 20 07:43:45 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 6509016A4CF for ; Thu, 20 Jan 2005 07:43:45 +0000 (GMT) Received: from relay03.pair.com (relay03.pair.com [209.68.5.17]) by mx1.FreeBSD.org (Postfix) with SMTP id BB2C343D53 for ; Thu, 20 Jan 2005 07:43:44 +0000 (GMT) (envelope-from dwalton@acm.org) Received: (qmail 74741 invoked from network); 20 Jan 2005 07:43:42 -0000 Received: from unknown (HELO ?172.16.1.34?) (unknown) by unknown with SMTP; 20 Jan 2005 07:43:42 -0000 X-pair-Authenticated: 68.127.18.161 Message-ID: <41EF6101.7010008@acm.org> Date: Wed, 19 Jan 2005 23:42:57 -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 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-mobile@freebsd.org 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: Thu, 20 Jan 2005 07:43:45 -0000 On 9 Nov 2004, Gleb Smirnoff wrote: > > Please try the following and report whether this helped. > > 1) Merge revision 1.233 of ata-all.c to your 5.3-RELEASE ata-all.c > 2) Apply patch I've sent to this list yesterday (Subject was 'CURRENT > patchset for Thinkpad'). > 3) Rebuild your kernel with new ata-all.c > 4) Reboot and try suspend/resume. I've been unable to get APM suspend/resume to work with 5.3-R on my Thinkpad 770Z. As released, 'apm -z' causes a lockup (it worked fine in 4.x). Revision 1.233 of ata-all.c fixes that, and 'apm -z' now causes the system to properly suspend to disk, as it had before. However, when the system resumes, it spits out three errors regarding pir0, then panics. This happens with or without your patch applied to ata-all.c. Any suggestions? Any other info I can provide that might be helpful? Thanks, Dave