From: Jiri Slaby <jslaby@suse.cz>
To: Konstantin Khlebnikov <khlebnikov@openvz.org>,
Borislav Petkov <bp@alien8.de>,
Bjorn Helgaas <bhelgaas@google.com>,
"Rafael J. Wysocki" <rjw@sisk.pl>,
lkml <linux-kernel@vger.kernel.org>,
e1000-devel@lists.sourceforge.net,
ML netdev <netdev@vger.kernel.org>
Subject: e1000e broken after resume on x230 [was: Uhhuh. NMI received for unknown reason 2c on CPU 0.]
Date: Fri, 01 Mar 2013 13:51:08 +0100 [thread overview]
Message-ID: <5130A43C.9040207@suse.cz> (raw)
In-Reply-To: <511DF7B4.8060504@openvz.org>
On 02/15/2013 09:54 AM, Konstantin Khlebnikov wrote:
> Borislav Petkov wrote:
>> On Thu, Feb 14, 2013 at 10:17:46AM -0700, Bjorn Helgaas wrote:
>>> It's pretty late for v3.8, but let me know if you think they're
>>> critical.
>>
>> Ok, I meant those:
>>
>> http://marc.info/?l=linux-kernel&m=135984592927219
>>
>> They fix the link detection issue on my x230. So let's see. The first
>> one is:
>>
>> * https://patchwork.kernel.org/patch/2001211/ (e1000e: fix pci device
>> enable
>> counter balance)
>
> please use this instead:
Hi, I am a bit confused. Is this fixed in -next yet? And if so, is it
known which commit IDs are needed to fix the issue in 3.7 (see below)?
> [PATCH v2 1/7] e1000e: fix pci-device enable-counter balance
> https://lkml.org/lkml/2013/2/4/190
>
> from v2 patchset: https://lkml.org/lkml/2013/2/4/185
So this is now in -next as:
commit e34f7147d93afe5efc574734bbff6584c0cc4a02
Author: Konstantin Khlebnikov <khlebnikov@openvz.org>
Date: Mon Feb 25 09:19:04 2013 +0400
e1000e: fix pci-device enable-counter balance
>> I don't see that one in your tree.
>>
>> * pci-pm-clear-state_saved-during-suspend.patch
This is:
commit 82fee4d67ab86d6fe5eb0f9a9e988ca9d654d765
Author: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Date: Mon Feb 4 15:56:05 2013 +0400
PCI/PM: Clear state_saved during suspend
>> Rafael said this one is a real bugfix. Looks like e1000e maintainers are
>> picking that one?
>>
>> * pci-pm-fix-e1000e-runtime-suspend.patch
Is this one replaced by a different fix in the end? Which one? I don't
think it is in -next yet, right?
confused,
--
js
suse labs
next prev parent reply other threads:[~2013-03-01 12:50 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-29 20:28 Uhhuh. NMI received for unknown reason 2c on CPU 0 Borislav Petkov
2013-01-29 21:32 ` Bjorn Helgaas
2013-01-30 3:42 ` Borislav Petkov
2013-01-30 17:27 ` Bjorn Helgaas
2013-01-30 17:44 ` Borislav Petkov
2013-01-30 19:43 ` Jiri Slaby
2013-01-30 20:00 ` Borislav Petkov
2013-01-30 20:33 ` Jiri Slaby
2013-01-30 21:39 ` Rafael J. Wysocki
2013-01-30 22:17 ` Jiri Slaby
2013-01-30 22:45 ` Rafael J. Wysocki
2013-01-30 23:12 ` Jiri Slaby
2013-01-30 23:47 ` Jiri Slaby
2013-01-31 0:54 ` Rafael J. Wysocki
2013-01-31 7:09 ` Borislav Petkov
2013-01-31 8:14 ` Jiri Slaby
2013-01-31 13:12 ` Rafael J. Wysocki
2013-01-31 13:10 ` Borislav Petkov
2013-02-02 23:04 ` Rafael J. Wysocki
2013-02-03 14:46 ` Borislav Petkov
2013-02-03 20:15 ` Rafael J. Wysocki
2013-02-03 20:58 ` Borislav Petkov
2013-02-03 21:06 ` Borislav Petkov
2013-02-03 21:15 ` Borislav Petkov
2013-02-14 14:39 ` Borislav Petkov
2013-02-14 17:17 ` Bjorn Helgaas
2013-02-14 19:12 ` Borislav Petkov
2013-02-15 8:54 ` Konstantin Khlebnikov
2013-02-15 9:16 ` Borislav Petkov
2013-03-04 21:50 ` Borislav Petkov
2013-03-05 0:16 ` Bjorn Helgaas
2013-03-05 9:42 ` Jiri Slaby
2013-03-05 9:58 ` Borislav Petkov
2013-03-05 10:01 ` Jiri Slaby
2013-03-05 10:02 ` Jeff Kirsher
2013-03-05 10:14 ` Borislav Petkov
2013-03-05 10:29 ` Jeff Kirsher
2013-03-05 11:27 ` Borislav Petkov
2013-03-05 11:33 ` Jeff Kirsher
2013-03-05 11:42 ` Borislav Petkov
2013-03-06 0:13 ` Rafael J. Wysocki
2013-03-06 0:19 ` Borislav Petkov
2013-03-08 16:47 ` Borislav Petkov
2013-03-05 10:01 ` Jeff Kirsher
2013-03-05 10:04 ` Jiri Slaby
2013-03-01 12:51 ` Jiri Slaby [this message]
2013-02-06 13:54 ` Jiri Slaby
2013-02-06 21:29 ` Rafael J. Wysocki
2013-01-31 8:28 ` Jiri Slaby
2013-01-31 13:18 ` Borislav Petkov
2013-01-31 13:24 ` Borislav Petkov
2013-03-01 12:55 ` Jiri Slaby
2013-04-04 7:32 ` Jiri Slaby
2013-04-04 9:33 ` Borislav Petkov
2013-04-04 9:38 ` Jiri Slaby
2013-04-04 9:58 ` Borislav Petkov
2013-01-31 13:29 ` Rafael J. Wysocki
2013-02-03 21:29 ` Jiri Slaby
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=5130A43C.9040207@suse.cz \
--to=jslaby@suse.cz \
--cc=bhelgaas@google.com \
--cc=bp@alien8.de \
--cc=e1000-devel@lists.sourceforge.net \
--cc=khlebnikov@openvz.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rjw@sisk.pl \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).