[Intel-wired-lan] [PATCH v2 1/1] e1000e: Undo e1000e_pm_freeze if __e1000_shutdown fails

[Brown, Aaron F]

> From: Intel-wired-lan [mailto:intel-wired-lan-bounces at osuosl.org] On Behalf
> Of Jeff Kirsher
> Sent: Tuesday, June 6, 2017 1:46 PM
> To: David Miller <davem at davemloft.net>; Nikula, Jani
> <jani.nikula at intel.com>
> Cc: Ursulin, Tvrtko <tvrtko.ursulin at intel.com>; daniel.vetter at ffwll.ch; intel-
> gfx at lists.freedesktop.org; linux-kernel at vger.kernel.org;
> jani.nikula at linux.intel.com; chris at chris-wilson.co.uk; Ertman, David M
> <david.m.ertman at intel.com>; intel-wired-lan at lists.osuosl.org; dri-
> devel at lists.freedesktop.org; netdev at vger.kernel.org; airlied at gmail.com
> Subject: Re: [Intel-wired-lan] [PATCH v2 1/1] e1000e: Undo
> e1000e_pm_freeze if __e1000_shutdown fails
> 
> On Fri, 2017-06-02 at 14:14 -0400, David Miller wrote:
> > From: Jani Nikula <jani.nikula at intel.com>
> > Date: Wed, 31 May 2017 18:50:43 +0300
> >
> > > From: Chris Wilson <chris at chris-wilson.co.uk>
> > >
> > > An error during suspend (e100e_pm_suspend),
> >
> >  ...
> > > lead to complete failure:
> >
> >  ...
> > > The unwind failures stems from commit 2800209994f8 ("e1000e:
> > > Refactor PM
> > > flows"), but it may be a later patch that introduced the non-
> > > recoverable
> > > behaviour.
> > >
> > > Fixes: 2800209994f8 ("e1000e: Refactor PM flows")
> > > Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=99847
> > > Cc: Tvrtko Ursulin <tvrtko.ursulin at intel.com>
> > > Cc: Jeff Kirsher <jeffrey.t.kirsher at intel.com>
> > > Cc: Dave Ertman <davidx.m.ertman at intel.com>
> > > Cc: Bruce Allan <bruce.w.allan at intel.com>
> > > Cc: intel-wired-lan at lists.osuosl.org
> > > Cc: netdev at vger.kernel.org
> > > Signed-off-by: Chris Wilson <chris at chris-wilson.co.uk>
> > > [Jani: bikeshed repainted]
> > > Signed-off-by: Jani Nikula <jani.nikula at intel.com>
> >
> > Jeff, please make sure this gets submitted to me soon.
> 
> Expect it later tonight, just finishing up testing.

Tested-by: Aaron Brown <aaron.f.brown at intel.com>