From: "Darrick J. Wong" <djwong@us.ibm.com>
To: Mark Haverkamp <markh@osdl.org>
Cc: linux-scsi <linux-scsi@vger.kernel.org>
Subject: Re: aic94xx panic on module load
Date: Tue, 28 Nov 2006 10:01:10 -0800 [thread overview]
Message-ID: <456C7966.7080602@us.ibm.com> (raw)
In-Reply-To: <1164734233.21827.8.camel@markh3.pdx.osdl.net>
Mark Haverkamp wrote:
> I got this panic when loading the aic94xx module. The adapter is
> connected to an HP MSA50 SAS enclosure with 3 72GB SAS disks.
>
> Kernel 2.6.19-rc6-scsi-misc on an x86_64
<snip>
> sas: task finished with resp:0x0, stat:0x89
> sas: sas_discover_sata() for device 500508b300a27a2c at 500508b300a27a2f:0xc returned 0xffffff06
> kobject_add failed for port-2:0:12 with -EEXIST, don't try to register things with the same name in the same directory.
Your expander is reporting your SAS disks to aic94xx as SATA disks,
which is why the sas_discover_sata fails. I don't know why it would do
that... flaky hardware? I'm not really sure what to do when we're given
bad information.
> Kernel BUG at drivers/scsi/libsas/sas_expander.c:603
I believe this BUG is fixed by a few patches in aic94xx-sas. For sure
you'll want the patch named "libsas: better error handling in
sas_ex_discover_end_dev()" patch; see commit
82f6bc0849b6fce9a965dde11dd6f685adc7285e.
There are some dependencies:
e384a0bdd9d3abb5ba2f6eac9ac4d0ac61e1c6a1 ->
1f8787b198c4ba058a0bfc06c2ca7f301168a5dd ->
82f6bc0849b6fce9a965dde11dd6f685adc7285e.
--D
next prev parent reply other threads:[~2006-11-28 18:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-28 17:17 aic94xx panic on module load Mark Haverkamp
2006-11-28 18:01 ` Darrick J. Wong [this message]
2006-11-29 19:29 ` Mark Haverkamp
2006-11-28 18:44 ` Douglas Gilbert
2006-11-28 18:51 ` Mark Haverkamp
2006-11-28 21:46 ` Mark Haverkamp
2006-11-28 23:17 ` Mark Haverkamp
2006-11-29 1:52 ` Douglas Gilbert
2006-11-29 15:16 ` Mark Haverkamp
2006-11-29 16:30 ` Douglas Gilbert
2006-11-30 7:11 ` Luben Tuikov
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=456C7966.7080602@us.ibm.com \
--to=djwong@us.ibm.com \
--cc=linux-scsi@vger.kernel.org \
--cc=markh@osdl.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