[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20090319184948.44bf5e9a@hobbes.lan>
Date: Thu, 19 Mar 2009 18:49:48 -0700
From: Jesse Barnes <jbarnes@...tuousgeek.org>
To: Ingo Molnar <mingo@...e.hu>
Cc: "Rafael J. Wysocki" <rjw@...k.pl>, Yinghai Lu <yinghai@...nel.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Matthew Wilcox <matthew@....cx>,
Jesse Brandeburg <jesse.brandeburg@...il.com>,
David Miller <davem@...emloft.net>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
NetDev <netdev@...r.kernel.org>, linux-pci@...r.kernel.org,
pm list <linux-pm@...ts.linux-foundation.org>
Subject: Re: [PATCH] pci: fix kexec with power state D3
> > And, quite frankly, I'm not sure if users will be happy with
> > the $subject patch, because it _really_ breaks things (well,
> > the kexec users who don't use suspend might be, but surely
> > suspend users who don't use kexec won't).
>
> Please note that i havent reviewed the patches and i did not
> take any sides in the discussion - i just flagged the maintainer
> ping-pong. As long as we pick one of the patches (or a third
> one) within a bound amount of time we should be fine :)
I'll defer to Rafael here; he's been working the most in this area.
The changelog wasn't very complete for the original patch, but it
sounds like in the kexec case the newly booted kernel will get an igb
device in D3 which it can't handle? That really does sound like a
driver bug, not something we should mess with in the core.
--
Jesse Barnes, Intel Open Source Technology Center
--
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