Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1750983AbXA3AS6 (ORCPT ); Mon, 29 Jan 2007 19:18:58 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752630AbXA3AS6 (ORCPT ); Mon, 29 Jan 2007 19:18:58 -0500 Received: from smtp.osdl.org ([65.172.181.24]:34787 "EHLO smtp.osdl.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750983AbXA3AS5 (ORCPT ); Mon, 29 Jan 2007 19:18:57 -0500 Date: Mon, 29 Jan 2007 16:16:26 -0800 From: Stephen Hemminger To: Linus Torvalds Cc: Thomas Gleixner , Linux Kernel Mailing List , Jeff Garzik Subject: Re: Linux 2.6.20-rc6 - sky2 resume breakage Message-ID: <20070129161626.33277eb1@freekitty> In-Reply-To: References: <1169931333.17469.125.camel@localhost.localdomain> <20070129113159.7ad22e4c@freekitty> <1170101430.29240.34.camel@localhost.localdomain> <20070129133849.1b523226@freekitty> <1170109401.29240.49.camel@localhost.localdomain> <20070129144055.151cfe52@freekitty> <20070129154518.40b0b3d3@freekitty> Organization: Linux Foundation X-Mailer: Sylpheed-Claws 2.5.0-rc3 (GTK+ 2.10.6; x86_64-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1764 Lines: 42 On Mon, 29 Jan 2007 16:12:27 -0800 (PST) Linus Torvalds wrote: > > > On Mon, 29 Jan 2007, Stephen Hemminger wrote: > > > > Why do you insist on maintaining the wrong initialization order > > on resume? When I raised the issue, Len brought up that the resume > > order did not match spec, but then there has been slow progress > > in fixing it (it's buried in -mm tree). > > It's not getting merged, SINCE IT DOESN'T WORK. It causes all sorts of > problems, because ACPI requires all kinds of things to be up and running > in order to actually work, and that in turn breaks all the devices that > have different ordering constraints. > > ACPI is a piece of sh*t. It asks the OS to do impossible things, like > running it early in the config sequence when it then at the same time > wants to depend on stuff that are there *late* in the sequence. It's not > the first time this insane situation has happened, either. You will find no argument from me with that statement. > But we'll try to merge the patch that totally switches around the whole > initialization order hopefully early after 2.6.20. But no way in hell do > we do it now, and I personally suspect we'll end reverting it when we do > try it just because it will probably break other things. But we'll see. > > In the meantime, sky2 doesn't work with MSI On one and only one platform. It works fine on others. Don't blame the driver, stop it in PCI. -- Stephen Hemminger - 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/