All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: "Oelke, Mark" <mark.oelke@hp.com>
Cc: "don.brace@pmcs.com" <don.brace@pmcs.com>,
	ISS StorageDev <iss_storagedev@hp.com>,
	"storagedev@pmcs.com" <storagedev@pmcs.com>,
	"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>
Subject: Re: [BUG] hpsa: Controller lockup detected: 0x00150028
Date: Mon, 18 May 2015 18:03:45 +0200	[thread overview]
Message-ID: <20150518160345.GA18673@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <20150518152034.GC5404@twins.programming.kicks-ass.net>

On Mon, May 18, 2015 at 05:20:34PM +0200, Peter Zijlstra wrote:
> On Mon, May 18, 2015 at 01:57:39PM +0000, Oelke, Mark wrote:
> > The P212/P410/P411 firmware was recently spun to address an issue that sounds exactly like this problem.
> > Which version of controller firmware are you using?
> 
> Smart Array P212 in Slot 1
> 
>    Hardware Revision: C
>    Firmware Version: 6.60

I've updated to 6.62 and it appears to be working now; or rather, it has
not locked up yet where I think it would've locked up by now earlier.

I'll let it run for a few more hours before calling it fixed, I'll let
you know.

Thanks!

  reply	other threads:[~2015-05-18 16:03 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-18 12:40 [BUG] hpsa: Controller lockup detected: 0x00150028 Peter Zijlstra
2015-05-18 13:57 ` Oelke, Mark
2015-05-18 15:20   ` Peter Zijlstra
2015-05-18 16:03     ` Peter Zijlstra [this message]
2015-05-18 16:11       ` Peter Zijlstra
2015-05-22 15:10         ` Tomas Henzl
2015-05-22 16:40           ` Peter Zijlstra
2015-05-22 16:48             ` Handzik, Joe
2015-08-24  9:43               ` Wouter Depuydt
2015-08-24 10:02                 ` Wouter Depuydt
2015-08-24 14:11                   ` Don Brace

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=20150518160345.GA18673@twins.programming.kicks-ass.net \
    --to=peterz@infradead.org \
    --cc=don.brace@pmcs.com \
    --cc=iss_storagedev@hp.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=mark.oelke@hp.com \
    --cc=storagedev@pmcs.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.