From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S262236AbVHCLvb (ORCPT ); Wed, 3 Aug 2005 07:51:31 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S262247AbVHCLtT (ORCPT ); Wed, 3 Aug 2005 07:49:19 -0400 Received: from gate.crashing.org ([63.228.1.57]:23982 "EHLO gate.crashing.org") by vger.kernel.org with ESMTP id S262236AbVHCLrS (ORCPT ); Wed, 3 Aug 2005 07:47:18 -0400 Subject: Re: Calling suspend() in halt/restart/shutdown -> not a good idea From: Benjamin Herrenschmidt To: "Eric W. Biederman" Cc: Pavel Machek , Andrew Morton , Linux Kernel list In-Reply-To: References: <1122908972.18835.153.camel@gaston> <20050802095312.GA1442@elf.ucw.cz> Content-Type: text/plain Date: Wed, 03 Aug 2005 13:43:07 +0200 Message-Id: <1123069387.30257.33.camel@gaston> Mime-Version: 1.0 X-Mailer: Evolution 2.2.2 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Tue, 2005-08-02 at 08:40 -0600, Eric W. Biederman wrote: > Pavel Machek writes: > > > Hi! > > > >> Why are we calling driver suspend routines in these ? This is _not_ > > > > Well, reason is that if you remove device_suspend() you'll get > > emergency hard disk park during powerdown. As harddrives can survive > > only limited number of emergency stops, that is not a good idea. > > Then the practical question is: do we suspend the disk by > calling device_suspend() for every device. Or do we modify > the ->shutdown() method for the disk. afaik, IDE used to have a shutdown callback or a shutdown notifier already anyway. If that was lost, then this is a different problem. If SATA and/or SCSI aren't doing it, then they need fixing, but suspend() isn't the solution. Ben.