From: "Dmitry Kravkov" <dmitry@broadcom.com>
To: "Carlos Peón Costa" <carlospeon@hotmail.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: RE: bnx2x kerneloops
Date: Wed, 2 Nov 2011 20:19:41 +0200 [thread overview]
Message-ID: <1320257981.12759.2.camel@lb-tlvb-dmitry> (raw)
In-Reply-To: <SNT113-W38A7D5A673342F70A1F808DBD40@phx.gbl>
On Wed, 2011-11-02 at 04:59 -0700, Carlos Peón Costa wrote:
>
> Hi, It's a HP BL460c G6.
> Regards.
It looks like problem happened before the WATCHDOG, FW has asserted for
some reason.
Can you provide /var/log/messages and describe in details the scenario?
Thanks
next prev parent reply other threads:[~2011-11-02 18:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-02 11:04 bnx2x kerneloops Carlos Peón Costa
2011-11-02 11:54 ` Dmitry Kravkov
2011-11-02 11:59 ` Carlos Peón Costa
2011-11-02 18:19 ` Dmitry Kravkov [this message]
[not found] ` <SNT113-W9B428C68CF654B313283EDBD50@phx.gbl>
2011-11-03 8:09 ` Carlos Peón Costa
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=1320257981.12759.2.camel@lb-tlvb-dmitry \
--to=dmitry@broadcom.com \
--cc=carlospeon@hotmail.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