netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: David Miller <davem@davemloft.net>, netdev <netdev@vger.kernel.org>
Subject: Re: [BUG] igb: panic at boot time with latest Linus tree
Date: Tue, 31 Jul 2012 01:51:33 -0700	[thread overview]
Message-ID: <1343724693.2230.18.camel@jtkirshe-mobl> (raw)
In-Reply-To: <1343724174.21269.168.camel@edumazet-glaptop>

[-- Attachment #1: Type: text/plain, Size: 889 bytes --]

On Tue, 2012-07-31 at 10:42 +0200, Eric Dumazet wrote:
> On Mon, 2012-07-30 at 23:26 -0700, Jeff Kirsher wrote:
> > On Tue, 2012-07-31 at 08:14 +0200, Eric Dumazet wrote:
> > > For information, I get this each time I boot on latest Linus tree :
> > > 
> > > RTNL is left locked, so machine unusable.
> > > 
> > > No problem with David net tree, so thats a bit strange...
> > > 
> > > Not sure I'll have time to investigate today
> > > (And tomorrow I am off for the day)
> > > 
> > > 
> > > 
> > 
> > I have an igb patch current in test to fix a panic in igb.  Here is the
> > patch:
> > 
> 
> 
> 
> Ah sorry for the false alarm, it appears I had igb module in a out of date initrd file (coming from my net tree)

No problem, thanks for the feedback.  Whether or not it was false alarm,
the feedback is always a good thing which helps us improve.

Cheers,
Jeff

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

      reply	other threads:[~2012-07-31  8:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-31  6:14 [BUG] igb: panic at boot time with latest Linus tree Eric Dumazet
2012-07-31  6:26 ` Jeff Kirsher
2012-07-31  8:42   ` Eric Dumazet
2012-07-31  8:51     ` Jeff Kirsher [this message]

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=1343724693.2230.18.camel@jtkirshe-mobl \
    --to=jeffrey.t.kirsher@intel.com \
    --cc=davem@davemloft.net \
    --cc=eric.dumazet@gmail.com \
    --cc=netdev@vger.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).