All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Oelke, Mark" <mark.oelke@hp.com>
To: Peter Zijlstra <peterz@infradead.org>,
	"don.brace@pmcs.com" <don.brace@pmcs.com>
Cc: 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 13:57:39 +0000	[thread overview]
Message-ID: <EC48209BE0009041A0D3C6A996EAD2AE27A7FAEE@G9W0754.americas.hpqcorp.net> (raw)
In-Reply-To: <20150518124058.GH21418@twins.programming.kicks-ass.net>

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?

-----Original Message-----
From: Peter Zijlstra [mailto:peterz@infradead.org] 
Sent: Monday, May 18, 2015 7:41 AM
To: don.brace@pmcs.com
Cc: ISS StorageDev; storagedev@pmcs.com; linux-scsi@vger.kernel.org
Subject: [BUG] hpsa: Controller lockup detected: 0x00150028

Hi,

On my HP-DL180-G6 with a HP Smart Array P212.

I can reliably trigger a controller lockup by running smartctl.

I'm trying to monitor my HDD temps using:

  for ((i=0; i<8; i++)) ; do
	smartctl -d cciss,$i -a /dev/sg0 | grep ^194 ;

  done | awk '{t=$10; if (t > T) T = t;} END {print T}'

After a few of those runs, I get:

[ 1540.277776] hpsa 0000:06:00.0: Controller lockup detected: 0x00150028

And my disks are gone.

With linux 3.16 the whole kernel came down with NMI watchdog timeouts / RCU stalls in the detect_lockup() worklet.

On linux 4.0 those appear to be gone, but the controller isn't coming back either.

It this a known 'feature'; is there anything I can do to help diagnose/fix this issue?

 ~ Peter

  reply	other threads:[~2015-05-18 13:58 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 [this message]
2015-05-18 15:20   ` Peter Zijlstra
2015-05-18 16:03     ` Peter Zijlstra
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=EC48209BE0009041A0D3C6A996EAD2AE27A7FAEE@G9W0754.americas.hpqcorp.net \
    --to=mark.oelke@hp.com \
    --cc=don.brace@pmcs.com \
    --cc=iss_storagedev@hp.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=peterz@infradead.org \
    --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.