From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
To: Borislav Petkov <bp@alien8.de>
Cc: Jiri Slaby <jslaby@suse.cz>, "Rafael J. Wysocki" <rjw@sisk.pl>,
Bjorn Helgaas <bhelgaas@google.com>,
Konstantin Khlebnikov <khlebnikov@openvz.org>,
x86@kernel.org, lkml <linux-kernel@vger.kernel.org>,
e1000-devel@lists.sourceforge.net,
Bruce Allan <bruce.w.allan@intel.com>
Subject: Re: Uhhuh. NMI received for unknown reason 2c on CPU 0.
Date: Tue, 05 Mar 2013 02:02:48 -0800 [thread overview]
Message-ID: <1362477768.8626.14.camel@jtkirshe-mobl> (raw)
In-Reply-To: <20130305095821.GC4881@pd.tnic>
[-- Attachment #1: Type: text/plain, Size: 2086 bytes --]
On Tue, 2013-03-05 at 10:58 +0100, Borislav Petkov wrote:
> On Tue, Mar 05, 2013 at 10:42:17AM +0100, Jiri Slaby wrote:
> > On 03/05/2013 01:16 AM, Bjorn Helgaas wrote:
> > > [+cc e1000-devel, Jeff, Bruce]
> > >
> > > On Mon, Mar 4, 2013 at 2:50 PM, Borislav Petkov <bp@alien8.de> wrote:
> > >> On Fri, Feb 15, 2013 at 10:16:41AM +0100, Borislav Petkov wrote:
> > >>> So it looks Bjorn has taken most of them and the e1000e one will go
> > >>> through the e1000e maintainers. I'll test after the merge window is
> > >>> done.
> > >>
> > >> Issue still persists on 3.9-rc1 :-( :
> > >>
> > >> Mar 4 21:47:34 nazgul vmunix: [ 3223.412541] e1000e: eth0 NIC Link is Up 100 Mbps Full Duplex, Flow Control: Rx/Tx
> > >> Mar 4 21:47:34 nazgul vmunix: [ 3223.412554] e1000e 0000:00:19.0 eth0: 10/100 speed: disabling TSO
> > >> Mar 4 21:47:35 nazgul vmunix: [ 3224.034158] Uhhuh. NMI received for unknown reason 2c on CPU 0.
> > >> Mar 4 21:47:35 nazgul vmunix: [ 3224.034166] Do you have a strange power saving mode enabled?
> > >> Mar 4 21:47:35 nazgul vmunix: [ 3224.034168] Dazed and confused, but trying to continue
> > >
> > > The e1000e changes didn't get merged, did they? I don't see the
> > > following changes mentioned at https://lkml.org/lkml/2013/2/4/185 in
> > > 3.9-rc1:
> > >
> > > e1000e: fix pci-device enable-counter balance
> > > e1000e: fix runtime power management transitions
> > > e1000e: fix accessing to suspended device
> >
> > You're right. They are not even in -next :(.
>
> Oh, and there's another issue with this driver I reported yesterday:
> http://marc.info/?l=linux-kernel&m=136243374114892&w=2:
>
> "Trying to free already-free IRQ 20"
>
> which happens during suspend so it seems also related.
>
> Rafael, what's the state of those patches here:
> https://lkml.org/lkml/2013/2/4/185, are they ready to be tested or you
> still have issues with them?
They are in my queue of e1000e patches for net and are being testing
currently. I should be able to push them upstream this week.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-03-05 10:02 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 [this message]
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 ` e1000e broken after resume on x230 [was: Uhhuh. NMI received for unknown reason 2c on CPU 0.] Jiri Slaby
2013-02-06 13:54 ` Uhhuh. NMI received for unknown reason 2c on CPU 0 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=1362477768.8626.14.camel@jtkirshe-mobl \
--to=jeffrey.t.kirsher@intel.com \
--cc=bhelgaas@google.com \
--cc=bp@alien8.de \
--cc=bruce.w.allan@intel.com \
--cc=e1000-devel@lists.sourceforge.net \
--cc=jslaby@suse.cz \
--cc=khlebnikov@openvz.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rjw@sisk.pl \
--cc=x86@kernel.org \
/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).