From owner-freebsd-hackers@FreeBSD.ORG Tue Nov 16 23:23:53 2010 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D2A411065674; Tue, 16 Nov 2010 23:23:53 +0000 (UTC) (envelope-from mavbsd@gmail.com) Received: from mail-ew0-f54.google.com (mail-ew0-f54.google.com [209.85.215.54]) by mx1.freebsd.org (Postfix) with ESMTP id 302428FC28; Tue, 16 Nov 2010 23:23:52 +0000 (UTC) Received: by ewy3 with SMTP id 3so792393ewy.13 for ; Tue, 16 Nov 2010 15:23:52 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:sender:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :x-enigmail-version:content-type:content-transfer-encoding; bh=k2jGH1Q7e3/GVc30qnzMF1CfnVd9hzgVTyYY3Eg+6Uc=; b=Z3L/KRBtDySjJDYVXyLf/5on75ggqoSfy1J9xSg1GHiHqlcu1ZCQdKVbYRPSw3n2KU +cbjRtKuXC3tesma6k780ylyjYf5GyByk/PAZaORC/kohVhO/1zQA+GHValbMYzu46A5 4DQREOYOF4VSGxz7s7uJimNlMGia8Ttv6jocg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:x-enigmail-version:content-type :content-transfer-encoding; b=LfnPN/rJAGu+eRWh5BsNiQfhtRuhpZWGFB6xiOL+EFJitJmeXEj+8Cc1hGfcJNkVBq qLTWQcXrXhZGFCa/J9TVMfevwDU3/tjI9ulzF2gu9hZiLyi5qtlrYLUCToEHT7nk7xtx V31gLcpztjB2CF9Fm6IZF1lFNEIdxEHsIoa+s= Received: by 10.204.122.65 with SMTP id k1mr8241628bkr.151.1289949831988; Tue, 16 Nov 2010 15:23:51 -0800 (PST) Received: from mavbook2.mavhome.dp.ua (pc.mavhome.dp.ua [212.86.226.226]) by mx.google.com with ESMTPS id 4sm879570bki.1.2010.11.16.15.23.49 (version=SSLv3 cipher=RC4-MD5); Tue, 16 Nov 2010 15:23:50 -0800 (PST) Sender: Alexander Motin Message-ID: <4CE3125E.1000307@FreeBSD.org> Date: Wed, 17 Nov 2010 01:23:10 +0200 From: Alexander Motin User-Agent: Thunderbird 2.0.0.23 (X11/20091212) MIME-Version: 1.0 To: Alexander Best References: <201009161742.24228.tijl@coosemans.org> <201009161619.o8GGJAmv035378@lurza.secnetix.de> <20101018155944.GA12425@freebsd.org> <868w1r92rf.fsf@ds4.des.no> <20101021122110.GA65490@freebsd.org> <4CC156F5.1050109@FreeBSD.org> <20101022100309.GA16446@freebsd.org> <20101116204000.00005aea@unknown> <20101116221725.GA49789@freebsd.org> In-Reply-To: <20101116221725.GA49789@freebsd.org> X-Enigmail-Version: 0.96.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Bruce Cran , Tijl Coosemans , Oliver Fromme , freebsd-hackers@freebsd.org, =?ISO-8859-1?Q?Dag-Erling_Sm=F8rgra?=, =?ISO-8859-1?Q?v?= Subject: Re: Summary: Re: Spin down HDD after disk sync or before power off X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Nov 2010 23:23:53 -0000 Alexander Best wrote: > On Tue Nov 16 10, Bruce Cran wrote: >> On Fri, 22 Oct 2010 10:03:09 +0000 >> Alexander Best wrote: >> >>> so how about olivers patch? it will only apply to ata devices so it's >>> garanteed not to break any other CAM devices (i'm thinking about the >>> aac controller issue). you could revert your previous shutdown work >>> and plug olivers patch into CAM. you might want to replace the >>> combination of flush/standby immediate with sleep. >> One problem with the code that's been committed is that the shutdown >> event handler doesn't get run during a suspend operation so an >> emergency unload still gets done when running "acpiconf -s3". > > unfortunately i don't think a can help you on that one. acpi never worked for > me! even 'acpiconf -s1' will hopelessly crash my system. :( It is not necessary to have fully working suspend to work on this. Bounce mode should be enough. If bounce is also not working for you - it definitely should be the first thing to fix. >From the other side ATM I see no good approach to this, as soon as CAM devices are not present on NewBus to handle suspend events. Unless SIM drivers will expose those events to CAM in some way. -- Alexander Motin