linux-kernel - Re: Uhhuh. NMI received for unknown reason 2c on CPU 0.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <511DF7B4.8060504@openvz.org>
Date:	Fri, 15 Feb 2013 12:54:12 +0400
From:	Konstantin Khlebnikov <khlebnikov@...nvz.org>
To:	Borislav Petkov <bp@...en8.de>,
	Bjorn Helgaas <bhelgaas@...gle.com>,
	"Rafael J. Wysocki" <rjw@...k.pl>, Jiri Slaby <jslaby@...e.cz>,
	x86@...nel.org, lkml <linux-kernel@...r.kernel.org>
Subject: Re: Uhhuh. NMI received for unknown reason 2c on CPU 0.

Borislav Petkov wrote:
> On Thu, Feb 14, 2013 at 10:17:46AM -0700, Bjorn Helgaas wrote:
>> On Thu, Feb 14, 2013 at 7:39 AM, Borislav Petkov<bp@...e.de>  wrote:
>>> On Sun, Feb 03, 2013 at 03:46:56PM +0100, Borislav Petkov wrote:
>>>> On Sun, Feb 03, 2013 at 12:04:46AM +0100, Rafael J. Wysocki wrote:
>>>>> The [2/5] is at: https://patchwork.kernel.org/patch/2001211/
>>>>>
>>>>> The other two are attached.  I suppose the ordering doesn't matter.
>>>>
>>>> Ok, the eth link cable hotplugging issue seems fixed, plugging and
>>>> unplugging the cable works as expected.
>>>
>>> Q: what happened to those, are they going upstream for 3.9 or are you
>>> sending them now for 3.8?
>>>
>>> They fix at least the cable hotplugging issue so at least one thing is
>>> covered.
>>
>> I haven't done anything with the e1000e patches; I assume the e1000e
>> maintainers will take care of those.
>>
>> I merged the following patches for v3.9:
>>
>>      * pci/konstantin-runtime-pm:
>>        PCI/PM: Clear state_saved during suspend
>>        PCI: Use atomic_inc_return() rather than atomic_add_return()
>>        PCI: Catch attempts to disable already-disabled devices
>>        PCI: Disable Bus Master unconditionally in pci_device_shutdown()
>>
>> You can see the actual patches I merged at:
>> http://git.kernel.org/?p=linux/kernel/git/helgaas/pci.git;a=shortlog;h=refs/heads/next
>>
>> 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:

[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

>
> Rafael said this one is a real bugfix. Looks like e1000e maintainers are
> picking that one?
>
> * pci-pm-fix-e1000e-runtime-suspend.patch
>
> I don't see that one in your tree.
>
> * pci-pm-clear-state_saved-during-suspend.patch
>
> I can see this one in your tree: http://git.kernel.org/?p=linux/kernel/git/helgaas/pci.git;a=commitdiff;h=82fee4d67ab86d6fe5eb0f9a9e988ca9d654d765
>
> With the imminence of the 3.8 release, we probably want to wait for
> after the merge window and retest again, then apply and packport stuff,
> if needed.
>
> And the NMI issue is still unfixed so this needs more work, AFAICT. Oh
> well, after the merge window.
>

--
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/