[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20081207091841.1d460c1a@infradead.org>
Date: Sun, 7 Dec 2008 09:18:41 -0800
From: Arjan van de Ven <arjan@...radead.org>
To: "Rafael J. Wysocki" <rjw@...k.pl>
Cc: Linus Torvalds <torvalds@...ux-foundation.org>,
Alan Stern <stern@...land.harvard.edu>,
Takashi Iwai <tiwai@...e.de>, Greg KH <greg@...ah.com>,
LKML <linux-kernel@...r.kernel.org>,
Jesse Barnes <jbarnes@...tuousgeek.org>,
pm list <linux-pm@...ts.linux-foundation.org>,
Ingo Molnar <mingo@...e.hu>,
Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [linux-pm] [PATCH 1/3] PCI: Rework default handling of suspend
and resume
On Sun, 7 Dec 2008 14:39:27 +0100
"Rafael J. Wysocki" <rjw@...k.pl> wrote:
> On Sunday, 7 of December 2008, Linus Torvalds wrote:
> >
> > On Sat, 6 Dec 2008, Linus Torvalds wrote:
> > >
> > > And btw, I'm talking suspend, not hibernate.
>
> Even as far as hibernation is concerned, I wouldn't _expect_ any BIOS
> to do anything like this as long as we use the ACPI facility to enter
> S4.
there are funky scenarios where the BIOS ends up .. not knowing.
Like
you boot your laptop
you then hot-dock your laptop
then you suspend (say S4)
..
during resume, the bios sees a very different system than it saw before.
I can totally imagine not all of them getting it right, esp if other
OSes would just re-register interrupts
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists