netdev - Re: bnx2 receive ring crash

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <1266014941.9371.6.camel@HP1>
Date:	Fri, 12 Feb 2010 14:49:01 -0800
From:	"Michael Chan" <mchan@...adcom.com>
To:	"Brian Haley" <brian.haley@...com>
cc:	"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
	"Montgomery, Bob" <bob.montgomery@...com>
Subject: Re: bnx2 receive ring crash


On Fri, 2010-02-12 at 13:50 -0800, Brian Haley wrote:
> Hi Michael,
> 
> We've been seeing some crashes in the bnx2 driver lately in the 2.6.32.x stable
> series kernels, v2.0.2 of the driver.  One of our engineers has gone through
> the dumps and found some inconsistencies in the receive ring, but we don't know
> how it happened.  I was hoping someone from Broadcom might be able to take a
> look and help point us in the right direction so we can track this down, since
> it's most likely broken upstream as well.  We'll be running tests against
> the latest net-next kernel next week.  Hopefully there is enough information
> below.

Thanks for the detailed report.  The software logic to handle the rx
rings hasn't changed much for many years and my guess is that this may
be caused by firmware.  We haven't seen this type of failure in our lab.
If you can do further debugging for us, I'd like to send you a patch to
switch back to an earlier version of the firmware to see if it fixes the
issue.  Thanks again.


--
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