[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <m1skcux8y2.fsf@fess.ebiederm.org>
Date: Wed, 04 Nov 2009 13:43:17 -0800
From: ebiederm@...ssion.com (Eric W. Biederman)
To: Dhananjay Phadke <dhananjay.phadke@...gic.com>
Cc: "netdev\@vger.kernel.org" <netdev@...r.kernel.org>,
Ameen Rahman <ameen.rahman@...gic.com>,
Amit Salecha <amit.salecha@...gic.com>
Subject: Re: REGRESSION: On 2.6.32-rc5 the firmware hangs, and the nic is unusable.
Dhananjay Phadke <dhananjay.phadke@...gic.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
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists