From: Andrew Morton <akpm@linux-foundation.org>
To: Michael Chan <mchan@broadcom.com>, netdev@vger.kernel.org
Cc: bugme-daemon@bugzilla.kernel.org
Subject: Re: [Bugme-new] [Bug 9914] New: bnx2 driver of latest kernel 2.6.24 not working with Cisco catalyst 650x Switch
Date: Thu, 7 Feb 2008 23:18:18 -0800 [thread overview]
Message-ID: <20080207231818.cdee64a3.akpm@linux-foundation.org> (raw)
In-Reply-To: <bug-9914-10286@http.bugzilla.kernel.org/>
On Thu, 7 Feb 2008 23:06:55 -0800 (PST) bugme-daemon@bugzilla.kernel.org wrote:
> http://bugzilla.kernel.org/show_bug.cgi?id=9914
>
> Summary: bnx2 driver of latest kernel 2.6.24 not working with
> Cisco catalyst 650x Switch
> Product: Drivers
> Version: 2.5
> KernelVersion: 2.6.24
> Platform: All
> OS/Version: Linux
> Tree: Mainline
> Status: NEW
> Severity: normal
> Priority: P1
> Component: Network
> AssignedTo: jgarzik@pobox.com
> ReportedBy: kaccountsend@gmail.com
>
>
> Latest working kernel version: (Works with Redhat 4 kernel)
> Earliest failing kernel version: 2.6.24
> Distribution: Self, kernel.org's kernel version 2.6.24
> Hardware Environment: Dell 2950
> Software Environment: Linux from Scratch, kernel version 2.6.24
>
> Problem Description:
> I am using the latest kernel 2.6.24. The hardware unit is a 2950 Dell box.
> The firmware version of bnx2 is 2.9.1. The bnx2 driver does work with other
> flavors of Cisco Switches like 290x. It is having problems at a customer site
> who has a Cisco 650x.
>
> The customer tried the RHEL 4 and does seem to work fine. The RHEL4 comes with
> the version of bnx2: 1.4.38
>
> The version on 2.6.24 is 1.6.9.
>
> Can anyone give me pointers as to why this is broken? Where can I get a patch?
>
> Any help is appreciated.
>
>
>
>
> Steps to reproduce:
> The driver does not auto-negotiate, neither does it work with a fixed link
> speed.
>
parent reply other threads:[~2008-02-08 7:18 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <bug-9914-10286@http.bugzilla.kernel.org/>]
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=20080207231818.cdee64a3.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=mchan@broadcom.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.