From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [PATCH v2 1/1] e1000e: Undo e1000e_pm_freeze if __e1000_shutdown fails
Date: Tue, 27 Jun 2017 13:51:05 -0700 [thread overview]
Message-ID: <1498596665.3244.2.camel@intel.com> (raw)
In-Reply-To: <CAPM=9tzdpEDoMNYj7Z_ZM3Z0JsCpjfNW1Z+y-1p5z3HssJ5aaw@mail.gmail.com>
On Wed, 2017-06-28 at 05:28 +1000, Dave Airlie wrote:
> On 20 June 2017 at 18:49, Daniel Vetter <daniel@ffwll.ch> wrote:
> > On Wed, Jun 07, 2017 at 01:07:33AM +0000, Brown, Aaron F wrote:
> > > > 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@davemloft.net>; Nikula, Jani
> > > > <jani.nikula@intel.com>
> > > > Cc: Ursulin, Tvrtko <tvrtko.ursulin@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@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@intel.com>
> > > > > Date: Wed, 31 May 2017 18:50:43 +0300
> > > > >
> > > > > > From: Chris Wilson <chris@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@intel.com>
> > > > > > Cc: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
> > > > > > Cc: Dave Ertman <davidx.m.ertman@intel.com>
> > > > > > Cc: Bruce Allan <bruce.w.allan@intel.com>
> > > > > > Cc: intel-wired-lan at lists.osuosl.org
> > > > > > Cc: netdev at vger.kernel.org
> > > > > > Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> > > > > > [Jani: bikeshed repainted]
> > > > > > Signed-off-by: Jani Nikula <jani.nikula@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@intel.com>
> >
> > Hm, I seem to be blind, but I can't find it anywhere in -rc6. Does
> > someone
> > have the sha1 from Linus' git for this patch?
>
> Guys this is a pretty serious regression, just left blowing in the
> wind, is anyone responsible for e1000e?
This was submitted and accepted into David Miller's net-next tree. I can
see if Dave can pull it into his net tree. DOes stable need to pick this
up as well?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: This is a digitally signed message part
URL: <http://lists.osuosl.org/pipermail/intel-wired-lan/attachments/20170627/41559e5b/attachment.asc>
WARNING: multiple messages have this Message-ID (diff)
From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
To: Dave Airlie <airlied@gmail.com>,
"Brown, Aaron F" <aaron.f.brown@intel.com>,
David Miller <davem@davemloft.net>,
"Nikula, Jani" <jani.nikula@intel.com>,
"Ursulin, Tvrtko" <tvrtko.ursulin@intel.com>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"jani.nikula@linux.intel.com" <jani.nikula@linux.intel.com>,
"chris@chris-wilson.co.uk" <chris@chris-wilson.co.uk>,
"Ertman, David M" <david.m.ertman@intel.com>,
"intel-wired-lan@lists.osuosl.org"
<intel-wired-lan@lists.osuosl.org>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Cc: "daniel.vetter@ffwll.ch" <daniel.vetter@ffwll.ch>
Subject: Re: [Intel-wired-lan] [PATCH v2 1/1] e1000e: Undo e1000e_pm_freeze if __e1000_shutdown fails
Date: Tue, 27 Jun 2017 13:51:05 -0700 [thread overview]
Message-ID: <1498596665.3244.2.camel@intel.com> (raw)
In-Reply-To: <CAPM=9tzdpEDoMNYj7Z_ZM3Z0JsCpjfNW1Z+y-1p5z3HssJ5aaw@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 2907 bytes --]
On Wed, 2017-06-28 at 05:28 +1000, Dave Airlie wrote:
> On 20 June 2017 at 18:49, Daniel Vetter <daniel@ffwll.ch> wrote:
> > On Wed, Jun 07, 2017 at 01:07:33AM +0000, Brown, Aaron F wrote:
> > > > From: Intel-wired-lan [mailto:intel-wired-lan-bounces@osuosl.org]
> > > > On Behalf
> > > > Of Jeff Kirsher
> > > > Sent: Tuesday, June 6, 2017 1:46 PM
> > > > To: David Miller <davem@davemloft.net>; Nikula, Jani
> > > > <jani.nikula@intel.com>
> > > > Cc: Ursulin, Tvrtko <tvrtko.ursulin@intel.com>; daniel.vetter@ffwll
> > > > .ch; intel-
> > > > gfx@lists.freedesktop.org; linux-kernel@vger.kernel.org;
> > > > jani.nikula@linux.intel.com; chris@chris-wilson.co.uk; Ertman,
> > > > David M
> > > > <david.m.ertman@intel.com>; intel-wired-lan@lists.osuosl.org; dri-
> > > > devel@lists.freedesktop.org; netdev@vger.kernel.org; airlied@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@intel.com>
> > > > > Date: Wed, 31 May 2017 18:50:43 +0300
> > > > >
> > > > > > From: Chris Wilson <chris@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@intel.com>
> > > > > > Cc: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
> > > > > > Cc: Dave Ertman <davidx.m.ertman@intel.com>
> > > > > > Cc: Bruce Allan <bruce.w.allan@intel.com>
> > > > > > Cc: intel-wired-lan@lists.osuosl.org
> > > > > > Cc: netdev@vger.kernel.org
> > > > > > Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> > > > > > [Jani: bikeshed repainted]
> > > > > > Signed-off-by: Jani Nikula <jani.nikula@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@intel.com>
> >
> > Hm, I seem to be blind, but I can't find it anywhere in -rc6. Does
> > someone
> > have the sha1 from Linus' git for this patch?
>
> Guys this is a pretty serious regression, just left blowing in the
> wind, is anyone responsible for e1000e?
This was submitted and accepted into David Miller's net-next tree. I can
see if Dave can pull it into his net tree. DOes stable need to pick this
up as well?
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
WARNING: multiple messages have this Message-ID (diff)
From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
To: Dave Airlie <airlied@gmail.com>,
"Brown, Aaron F" <aaron.f.brown@intel.com>,
David Miller <davem@davemloft.net>,
"Nikula, Jani" <jani.nikula@intel.com>,
"Ursulin, Tvrtko" <tvrtko.ursulin@intel.com>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"jani.nikula@linux.intel.com" <jani.nikula@linux.intel.com>,
"chris@chris-wilson.co.uk" <chris@chris-wilson.co.uk>,
"Ertman, David M" <david.m.ertman@intel.com>,
"intel-wired-lan@lists.osuosl.org"
<intel-wired-lan@lists.osuosl.org>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Cc: "daniel.vetter@ffwll.ch" <daniel.vetter@ffwll.ch>
Subject: Re: [Intel-wired-lan] [PATCH v2 1/1] e1000e: Undo e1000e_pm_freeze if __e1000_shutdown fails
Date: Tue, 27 Jun 2017 13:51:05 -0700 [thread overview]
Message-ID: <1498596665.3244.2.camel@intel.com> (raw)
In-Reply-To: <CAPM=9tzdpEDoMNYj7Z_ZM3Z0JsCpjfNW1Z+y-1p5z3HssJ5aaw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2907 bytes --]
On Wed, 2017-06-28 at 05:28 +1000, Dave Airlie wrote:
> On 20 June 2017 at 18:49, Daniel Vetter <daniel@ffwll.ch> wrote:
> > On Wed, Jun 07, 2017 at 01:07:33AM +0000, Brown, Aaron F wrote:
> > > > From: Intel-wired-lan [mailto:intel-wired-lan-bounces@osuosl.org]
> > > > On Behalf
> > > > Of Jeff Kirsher
> > > > Sent: Tuesday, June 6, 2017 1:46 PM
> > > > To: David Miller <davem@davemloft.net>; Nikula, Jani
> > > > <jani.nikula@intel.com>
> > > > Cc: Ursulin, Tvrtko <tvrtko.ursulin@intel.com>; daniel.vetter@ffwll
> > > > .ch; intel-
> > > > gfx@lists.freedesktop.org; linux-kernel@vger.kernel.org;
> > > > jani.nikula@linux.intel.com; chris@chris-wilson.co.uk; Ertman,
> > > > David M
> > > > <david.m.ertman@intel.com>; intel-wired-lan@lists.osuosl.org; dri-
> > > > devel@lists.freedesktop.org; netdev@vger.kernel.org; airlied@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@intel.com>
> > > > > Date: Wed, 31 May 2017 18:50:43 +0300
> > > > >
> > > > > > From: Chris Wilson <chris@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@intel.com>
> > > > > > Cc: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
> > > > > > Cc: Dave Ertman <davidx.m.ertman@intel.com>
> > > > > > Cc: Bruce Allan <bruce.w.allan@intel.com>
> > > > > > Cc: intel-wired-lan@lists.osuosl.org
> > > > > > Cc: netdev@vger.kernel.org
> > > > > > Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> > > > > > [Jani: bikeshed repainted]
> > > > > > Signed-off-by: Jani Nikula <jani.nikula@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@intel.com>
> >
> > Hm, I seem to be blind, but I can't find it anywhere in -rc6. Does
> > someone
> > have the sha1 from Linus' git for this patch?
>
> Guys this is a pretty serious regression, just left blowing in the
> wind, is anyone responsible for e1000e?
This was submitted and accepted into David Miller's net-next tree. I can
see if Dave can pull it into his net tree. DOes stable need to pick this
up as well?
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2017-06-27 20:51 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-30 20:15 [PULL] topic/e1000e-fix Daniel Vetter
2017-05-30 22:10 ` David Miller
2017-05-30 23:06 ` Dave Airlie
2017-05-31 5:54 ` Daniel Vetter
2017-05-31 6:10 ` [Intel-wired-lan] " Daniel Vetter
2017-05-31 6:10 ` Daniel Vetter
2017-05-31 6:10 ` Daniel Vetter
2017-05-31 15:08 ` [Intel-wired-lan] " David Miller
2017-05-31 15:08 ` David Miller
2017-05-31 15:50 ` [Intel-wired-lan] " Jani Nikula
2017-05-31 15:50 ` Jani Nikula
2017-05-31 15:50 ` Jani Nikula
2017-05-31 15:50 ` [Intel-wired-lan] [PATCH v2 1/1] e1000e: Undo e1000e_pm_freeze if __e1000_shutdown fails Jani Nikula
2017-05-31 15:50 ` Jani Nikula
2017-05-31 15:50 ` Jani Nikula
2017-06-02 18:14 ` [Intel-wired-lan] " David Miller
2017-06-02 18:14 ` David Miller
2017-06-02 18:14 ` David Miller
2017-06-06 20:46 ` [Intel-wired-lan] " Jeff Kirsher
2017-06-06 20:46 ` Jeff Kirsher
2017-06-07 1:07 ` [Intel-wired-lan] " Brown, Aaron F
2017-06-07 1:07 ` Brown, Aaron F
2017-06-07 1:07 ` Brown, Aaron F
2017-06-20 8:49 ` Daniel Vetter
2017-06-20 8:49 ` Daniel Vetter
2017-06-20 8:49 ` Daniel Vetter
2017-06-27 19:28 ` Dave Airlie
2017-06-27 19:28 ` Dave Airlie
2017-06-27 19:28 ` Dave Airlie
2017-06-27 20:51 ` Jeff Kirsher [this message]
2017-06-27 20:51 ` Jeff Kirsher
2017-06-27 20:51 ` Jeff Kirsher
2017-06-28 5:35 ` Daniel Vetter
2017-06-28 5:35 ` Daniel Vetter
2017-06-28 5:35 ` Daniel Vetter
2017-06-05 5:20 ` Neftin, Sasha
2017-06-05 5:20 ` Neftin, Sasha
2017-06-05 5:20 ` Neftin, Sasha
2017-05-31 16:23 ` [Intel-wired-lan] [PULL] topic/e1000e-fix Daniel Vetter
2017-05-31 16:23 ` Daniel Vetter
2017-05-31 16:23 ` Daniel Vetter
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1498596665.3244.2.camel@intel.com \
--to=jeffrey.t.kirsher@intel.com \
--cc=intel-wired-lan@osuosl.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.