From: Phil Turmel <philip@turmel.org>
To: Marc Haber <mh+linux-kernel@zugschlus.de>
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: NetXen NX3031 failing test, reporting link down, not working
Date: Sun, 26 Dec 2010 23:17:55 -0500 [thread overview]
Message-ID: <4D181373.3070107@turmel.org> (raw)
In-Reply-To: <20101225163632.GA27786@torres.zugschlus.de>
Hi Marc,
On 12/25/2010 11:36 AM, Marc Haber wrote:
> On Mon, Dec 06, 2010 at 06:17:27PM +0100, Marc Haber wrote:
>> I have HP DL 120 G6 with two Quad-GE Cards based on NetXen NX3031 (rev
>> 42) [4040:0100]. The boxes are running with a grml daily image with
>> kernel 2.6.36.1 for the time being, and the NetXens are giving me a
>> hard time.
>
> it's a pity that nobody cared to even point me into the right
> direction. I am not aware of having done anything wrong.
Poor signal-to-noise ratio on lkml itself, so don't take it personally. The net folk don't listen too closely, but akpm usually tosses these over the wall to 'em. He seems to have missed this one, so I've added the most important CC.
> Anyway, the issue could be solved by updating the on-card flashed
> firmware from 4.0.530 to 4.0.539. With this firmware, everything seems
> to be fine.
>
> Maybe the Linux driver should be adapted to not fail silently if it
> doesn't like the on-card firmware but instead log an error message so
> that people know they need to update their firmware.
I'm just a lurker, tester, and occasional bug reporter, so I can't speak to this.
Phil
prev parent reply other threads:[~2010-12-27 4:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-06 17:17 NetXen NX3031 failing test, reporting link down, not working Marc Haber
2010-12-12 19:38 ` Marc Haber
2010-12-25 16:36 ` Marc Haber
2010-12-27 4:17 ` Phil Turmel [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=4D181373.3070107@turmel.org \
--to=philip@turmel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mh+linux-kernel@zugschlus.de \
--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