From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756258Ab3A3RoI (ORCPT ); Wed, 30 Jan 2013 12:44:08 -0500 Received: from mail.skyhub.de ([78.46.96.112]:37014 "EHLO mail.skyhub.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754414Ab3A3RoG (ORCPT ); Wed, 30 Jan 2013 12:44:06 -0500 Date: Wed, 30 Jan 2013 18:44:02 +0100 From: Borislav Petkov To: Bjorn Helgaas Cc: x86@kernel.org, lkml , Konstantin Khlebnikov , "Rafael J. Wysocki" Subject: Re: Uhhuh. NMI received for unknown reason 2c on CPU 0. Message-ID: <20130130174402.GB23980@pd.tnic> Mail-Followup-To: Borislav Petkov , Bjorn Helgaas , x86@kernel.org, lkml , Konstantin Khlebnikov , "Rafael J. Wysocki" References: <20130129202848.GE25415@pd.tnic> <20130130034204.GB30965@pd.tnic> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Jan 30, 2013 at 10:27:42AM -0700, Bjorn Helgaas wrote: > You're right, I don't think we're quite ready to merge those patches. > But if your NMI is easy to reproduce, it might be worth removing > e1000e altogether to see if it still happens. That's the problem - I've seen it only once so far. I'll watch out for it and do the above when I find a reliable way of reproducing it. Will keep you posted. Thanks. -- Regards/Gruss, Boris. Sent from a fat crate under my desk. Formatting is fine. --