Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S262791AbVDYUQf (ORCPT ); Mon, 25 Apr 2005 16:16:35 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S262789AbVDYUQe (ORCPT ); Mon, 25 Apr 2005 16:16:34 -0400 Received: from iolanthe.rowland.org ([192.131.102.54]:30848 "HELO iolanthe.rowland.org") by vger.kernel.org with SMTP id S262779AbVDYUOO (ORCPT ); Mon, 25 Apr 2005 16:14:14 -0400 Date: Mon, 25 Apr 2005 16:14:13 -0400 (EDT) From: Alan Stern X-X-Sender: stern@iolanthe.rowland.org To: Alexander Nyberg cc: Greg KH , Amit Gud , , , , , , USB development list Subject: Re: [PATCH] PCI: Add pci shutdown ability In-Reply-To: <1114458325.983.17.camel@localhost.localdomain> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1342 Lines: 32 On Mon, 25 Apr 2005, Alexander Nyberg wrote: > Not sure what you mean by "make kexec work nicer" but if it is because > some devices don't work after a kexec I have some objections. That was indeed the reason, at least in my case. The newly-rebooted kernel doesn't work too well when there are active devices, with no driver loaded, doing DMA and issuing IRQs because they were never shut down. > What about the kexec-on-panic? > > In the end at least every storage device should work after a > kexec-on-panic or else there might be cases where we cannot get dumps of > what happened. My guess is that having access to the network might come > in handy after a kexec-on-panic as well. > > So if this patch is because some devices don't work across kexec I don't > think this is a good idea because the same devices won't work after a > kexec-on-panic. Do I understand your argument correctly? You seem to be saying that because this new facility sometimes won't work (the kexec-on-panic case) it shouldn't be added at all. What about all the other times when it will work? Alan Stern - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/