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
parent reply other threads:[~2013-03-01 12:51 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <511DF7B4.8060504@openvz.org>]
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$(echo .)cz \
--cc=bhelgaas@google$(echo .)com \
--cc=bp@alien8$(echo .)de \
--cc=e1000-devel@lists$(echo .)sourceforge.net \
--cc=khlebnikov@openvz$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=rjw@sisk$(echo .)pl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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