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 21:36:34 +0200 [thread overview]
Message-ID: <1229369794.26330.2.camel@lb-tlvb-eliezer> (raw)
In-Reply-To: <200812151104.00724.bjorn.helgaas@hp.com>
On Mon, 2008-12-15 at 10:04 -0800, Bjorn Helgaas wrote:
> Yep, it's definitely possible that this is HW related. The proto
> has 57710, but the product will ultimately use the 57711, so I don't
> really even care about testing the 57710.
>
> After upgrading some pieces on my boards, I can't reproduce the
> MCA either. So I guess we can just write it off for now. The only
> reason I pointed out the issue at all is because it really hampered
> testing of standard distro bits on the rest of the box.
Please let me know if you see this issue again - we can try to
root-cause it. And again, sorry for the late initial response.
Eilon
prev parent reply other threads:[~2008-12-15 19:38 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
2008-12-15 18:04 ` Bjorn Helgaas
2008-12-15 19:36 ` Eilon Greenstein [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=1229369794.26330.2.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