From owner-freebsd-current@FreeBSD.ORG Wed Jun 18 17:25:19 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 77EBD37B401 for ; Wed, 18 Jun 2003 17:25:19 -0700 (PDT) Received: from msgbas1x.cos.agilent.com (msgbas1x.cos.agilent.com [192.25.240.36]) by mx1.FreeBSD.org (Postfix) with ESMTP id CA5E043F75 for ; Wed, 18 Jun 2003 17:25:18 -0700 (PDT) (envelope-from darrylo@soco.agilent.com) Received: from relcos1.cos.agilent.com (relcos1.cos.agilent.com [130.29.152.239]) by msgbas1x.cos.agilent.com (Postfix) with ESMTP id 02827182C8 for ; Wed, 18 Jun 2003 18:25:18 -0600 (MDT) Received: from mina.soco.agilent.com (mina.soco.agilent.com [141.121.54.157]) by relcos1.cos.agilent.com (Postfix) with ESMTP id 9A7309EA for ; Wed, 18 Jun 2003 18:25:17 -0600 (MDT) Received: from mina.soco.agilent.com (darrylo@localhost [127.0.0.1]) SMKit7.1.1_Agilent) with ESMTP id RAA17828 for ; Wed, 18 Jun 2003 17:25:17 -0700 (PDT) Message-Id: <200306190025.RAA17828@mina.soco.agilent.com> To: freebsd-current@freebsd.org In-Reply-To: Your message of "Wed, 18 Jun 2003 13:16:23 EDT." Mime-Version: 1.0 (generated by tm-edit 1.7) Content-Type: text/plain; charset=US-ASCII Date: Wed, 18 Jun 2003 17:25:16 -0700 From: Darryl Okahata Subject: Re: APM problem in 5.1-RELEASE X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Darryl Okahata List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 19 Jun 2003 00:25:19 -0000 Jesse Guardiani wrote: > Help! This APM BIOS suspends fine under Linux (2.4.18 > kernel)! I've tried everything I can think of to > get suspend working under 5.1-RELEASE! Wild-a** guess: > ata1-slave: timeout waiting for interrupt > ata1-slave: ATAPI identify failed I don't get this in my dmesg (and I have an A31, where apm seems to work). As you say it seems to be hanging during ATA reset, perhaps this has something to do with it? Is there any way to disable the ata1-slave? BIOS? Kernel setting??? -- Darryl Okahata darrylo@soco.agilent.com DISCLAIMER: this message is the author's personal opinion and does not constitute the support, opinion, or policy of Agilent Technologies, or of the little green men that have been following him all day.