netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: ebiederm@xmission.com (Eric W. Biederman)
To: Dhananjay Phadke <dhananjay.phadke@qlogic.com>
Cc: <netdev@vger.kernel.org>
Subject: REGRESSION: On 2.6.32-rc5 the firmware hangs, and the nic is unusable.
Date: Tue, 03 Nov 2009 23:40:50 -0800	[thread overview]
Message-ID: <m1tyxaagal.fsf@fess.ebiederm.org> (raw)


On 2.6.31.5 I get:
ethtool -i eth0
driver: netxen_nic
version: 4.0.30
firmware-version: 4.0.305
bus-info: 0000:06:00.0

And everything works except bonding.

On 2.6.32-rc5 I dhcp I get an IP
there is a sanity test ping.

Then the driver reports a firmware hang and
the interface goes down and I am dead in the water.

I'm a bit frustrated with this as it seems with each kernel release
the driver gets a little bit less usable.

Have I given you enough information to track this down?

Eric

             reply	other threads:[~2009-11-04  7:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-04  7:40 Eric W. Biederman [this message]
2009-11-04 19:15 ` REGRESSION: On 2.6.32-rc5 the firmware hangs, and the nic is unusable Dhananjay Phadke
2009-11-04 21:43   ` Eric W. Biederman
2009-11-04 22:42   ` Eric W. Biederman

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=m1tyxaagal.fsf@fess.ebiederm.org \
    --to=ebiederm@xmission.com \
    --cc=dhananjay.phadke@qlogic.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).