[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20130130200041.GD23895@pd.tnic>
Date: Wed, 30 Jan 2013 21:00:41 +0100
From: Borislav Petkov <bp@...en8.de>
To: Jiri Slaby <jslaby@...e.cz>
Cc: Bjorn Helgaas <bhelgaas@...gle.com>, x86@...nel.org,
lkml <linux-kernel@...r.kernel.org>,
Konstantin Khlebnikov <khlebnikov@...nvz.org>,
"Rafael J. Wysocki" <rjw@...k.pl>
Subject: Re: Uhhuh. NMI received for unknown reason 2c on CPU 0.
On Wed, Jan 30, 2013 at 08:43:55PM +0100, Jiri Slaby wrote:
> On 01/30/2013 06:44 PM, Borislav Petkov wrote:
> > 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.
>
> It happens here too. Dunno what is the root cause. I *think* that it
> never happened unless I used ethernet. Other than that I see no pattern.
>
> Attaching -C 20 grep of messages over the last half year if there is
> something that may help somehow.
Cool, so it happens once a day, not every day, everytime during resume,
and with e1000e. Can you try Bjorn's suggestion to remove e1000e
altogether and see if it still happens?
--
Regards/Gruss,
Boris.
Sent from a fat crate under my desk. Formatting is fine.
--
--
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/
Powered by blists - more mailing lists