From owner-freebsd-acpi@FreeBSD.ORG Fri Mar 23 18:07:41 2007 Return-Path: X-Original-To: freebsd-acpi@freebsd.org Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 7199416A400 for ; Fri, 23 Mar 2007 18:07:41 +0000 (UTC) (envelope-from nate@root.org) Received: from root.org (root.org [67.118.192.226]) by mx1.freebsd.org (Postfix) with ESMTP id 40F0D13C487 for ; Fri, 23 Mar 2007 18:07:41 +0000 (UTC) (envelope-from nate@root.org) Received: (qmail 47922 invoked from network); 23 Mar 2007 17:31:03 -0000 Received: from ppp-71-139-28-99.dsl.snfc21.pacbell.net (HELO ?10.0.0.235?) (nate-mail@71.139.28.99) by root.org with ESMTPA; 23 Mar 2007 17:31:03 -0000 Message-ID: <46040ED0.3090607@root.org> Date: Fri, 23 Mar 2007 10:30:56 -0700 From: Nate Lawson User-Agent: Thunderbird 1.5.0.7 (X11/20061027) MIME-Version: 1.0 To: alex65536@yandex.ru References: <73519472.20070323091455@yandex.ru> In-Reply-To: <73519472.20070323091455@yandex.ru> X-Enigmail-Version: 0.94.1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-acpi@freebsd.org Subject: Re: toshiba portege r100 resumes from S3 after a small patch X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Mar 2007 18:07:41 -0000 alex65536@yandex.ru wrote: > I've found a way to make my toshiba portege r100 resume. > > I just edited function ata_resume() in /usr/src/sys/dev/ata/ata-all.c like > that: > > ... > int > ata_resume(device_t dev) > { > printf("a delay to be sure disks have started...\n"); > DELAY(2000000); // delay for 2 seconds > ... > } > ... > > Without that delay system crashes sometimes with message "ad0: detached". > > I think that would work with some other toshiba laptops. > > A small problem is that the delay occurs two times, for both ata > channels, but it's better than nothing. It sounds like the ata driver is somehow timing out too quickly on the first commands. I've forwarded this to the ata maintainer to see if he has any comments. Thanks, Nate