From: ebiederm@xmission.com (Eric W. Biederman)
To: Dhananjay Phadke <dhananjay.phadke@qlogic.com>
Cc: "netdev\@vger.kernel.org" <netdev@vger.kernel.org>,
Ameen Rahman <ameen.rahman@qlogic.com>,
Amit Salecha <amit.salecha@qlogic.com>
Subject: Re: REGRESSION: On 2.6.32-rc5 the firmware hangs, and the nic is unusable.
Date: Wed, 04 Nov 2009 13:43:17 -0800 [thread overview]
Message-ID: <m1skcux8y2.fsf@fess.ebiederm.org> (raw)
In-Reply-To: <4AF1D2C6.20002@qlogic.com> (Dhananjay Phadke's message of "Wed\, 4 Nov 2009 11\:15\:18 -0800")
Dhananjay Phadke <dhananjay.phadke@qlogic.com> writes:
> Eric W. Biederman wrote:
>> 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
>>
>
> Agree, 2.6.31 window missed bonding (mac addr setup) fixes.
>
>> 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?
>
> This can be fixed in next rc patch of 2.6.32, if I get enough info to debug.
>
> Could you provide full dmesg, so that I can see what's going on around firmware
> hang message? Also provide your test details (bonding / whatever configured).
I will dig up that dmesg in a bit. Working on a machine when the network is
down is a pain.
There was no bonding configured. Essentially just:
ifup eth0 finally get a dhcp response firmware hangs..
Eric
next prev parent reply other threads:[~2009-11-04 21:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-04 7:40 REGRESSION: On 2.6.32-rc5 the firmware hangs, and the nic is unusable Eric W. Biederman
2009-11-04 19:15 ` Dhananjay Phadke
2009-11-04 21:43 ` Eric W. Biederman [this message]
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=m1skcux8y2.fsf@fess.ebiederm.org \
--to=ebiederm@xmission.com \
--cc=ameen.rahman@qlogic.com \
--cc=amit.salecha@qlogic.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).