Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754067AbYLBDnW (ORCPT ); Mon, 1 Dec 2008 22:43:22 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751397AbYLBDnO (ORCPT ); Mon, 1 Dec 2008 22:43:14 -0500 Received: from smtp1.linux-foundation.org ([140.211.169.13]:58258 "EHLO smtp1.linux-foundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751388AbYLBDnN (ORCPT ); Mon, 1 Dec 2008 22:43:13 -0500 Date: Mon, 1 Dec 2008 19:42:48 -0800 (PST) From: Linus Torvalds To: "Rafael J. Wysocki" cc: Greg KH , Ingo Molnar , Jesse Barnes , Len Brown , LKML , Takashi Iwai , Andrew Morton , Ivan Kokshaysky Subject: Re: Regression from 2.6.26: Hibernation (possibly suspend) broken on Toshiba R500 (bisected) In-Reply-To: Message-ID: References: <200812020320.31876.rjw@sisk.pl> User-Agent: Alpine 2.00 (LFD 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1030 Lines: 25 On Mon, 1 Dec 2008, Linus Torvalds wrote: > > or something like that. And then we just need to figure out which setup > routine sets the wrong alignment flag,. Oh, btw, one more thing: since it apparently sometimes _does_ resume from hibernation without all this, I'd also like to see the actual differences in /proc/ioports and /proc/iomem that happen as a result of the different alignment. I also really suspect we should add a whole "alignment" field to "struct resource", instead of the size-vs-start flags. The fact is, some PCI devices have alignment that is neither tied to size or anything else: I think some PCI bus resources are really always 4kB-aligned, for example (and aligning them by size will give a bigger alignment than actually required). Linus -- 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/