netdev - Re: bnx2x machine check in bnx2x_ack

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <1229361480.22295.22.camel@lb-tlvb-eliezer>
Date:	Mon, 15 Dec 2008 19:18:00 +0200
From:	"Eilon Greenstein" <eilong@...adcom.com>
To:	"Bjorn Helgaas" <bjorn.helgaas@...com>
cc:	"netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: Re: bnx2x machine check in bnx2x_ack_int()

On Mon, 2008-12-15 at 08:21 -0800, Bjorn Helgaas wrote:

> > > I'm using bnx2x 1.45.23 from RHEL5.3s4 on a prototype ia64 platform,
> > > and I see intermittent machine checks at bnx2x_ack_int+176, which is
> > > just after __ia64_readl() returns.
> > I see that you are using two 57710 chips. What kind of board are you
> > using (which PHY)?
> 
> This is a blade with separate PHYs.  In this case, there is no PHY
> at all because the module that would contain the PHY is not installed.
> 
> > > This is a proto with incomplete firmware, and the driver correctly
> > > complains about that, but it seems like there's still a hole where
> > > things blow up.
> > If you set the right FW on the board, do you still see the problem? I'm
> > asking to determine if this is a problem specific to the "no FW" case or
> > general issue with this configuration
> 
> I'm trying to get FW installed, but haven't had any luck yet.

Hmmm... So it is possible that this is HW related (since we are talking
about preliminary board with missing component and missing FW). I will
ask for some field support - someone will contact you shortly.

Thanks,
Eilon


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