From: "Eilon Greenstein" <eilong@broadcom.com>
To: "Bjorn Helgaas" <bjorn.helgaas@hp.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: bnx2x machine check in bnx2x_ack_int()
Date: Mon, 15 Dec 2008 19:18:00 +0200 [thread overview]
Message-ID: <1229361480.22295.22.camel@lb-tlvb-eliezer> (raw)
In-Reply-To: <200812150921.08668.bjorn.helgaas@hp.com>
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
next prev parent reply other threads:[~2008-12-15 17:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-09 19:04 bnx2x machine check in bnx2x_ack_int() Bjorn Helgaas
2008-12-15 8:03 ` Eilon Greenstein
2008-12-15 16:21 ` Bjorn Helgaas
2008-12-15 17:18 ` Eilon Greenstein [this message]
2008-12-15 18:04 ` Bjorn Helgaas
2008-12-15 19:36 ` Eilon Greenstein
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=1229361480.22295.22.camel@lb-tlvb-eliezer \
--to=eilong@broadcom.com \
--cc=bjorn.helgaas@hp.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox