From: bugzilla-daemon@bugzilla.kernel.org
To: linux-scsi@vger.kernel.org
Subject: [Bug 214967] mvsas not detecting some disks
Date: Mon, 15 Nov 2021 23:59:55 +0000 [thread overview]
Message-ID: <bug-214967-11613-Pv7UjYNkSY@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-214967-11613@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=214967
--- Comment #9 from Matthew Perkowski (mgperkow@gmail.com) ---
(In reply to Damien Le Moal from comment #7)
> (In reply to Matthew Perkowski from comment #1)
> > I stumbled across this and gave it a try, and it fixed my immediate
> problem:
> >
> > https://sourceforge.net/p/scst/mailman/scst-devel/thread/4FDDA78C.400@acm.
> > org/
> >
> > However, it doesn't look like the mvsas driver has changed in some time, so
> > I'm thinking the problem was caused by another change somewhere else in the
> > kernel, and adding that one line of code to mv_sas.c simply "band-aided"
> the
> > immediate issue I was experiencing.
>
> I am not familiar with the mv_sas driver & associated HBAs. Do these
> implement SAT using libata on the host ? Or does the HBA firmware handle
> scsi command translation ? Some quick grep in the driver code does not
> reveal much.
I'm afraid I don't know that for certain. I know the card HAS firmware since
I've updated it once before. I'll see if those patches solve the problem. If
not, maybe I can figure out more about the card to help us along. I can tell
you that the card uses this controller chip:
https://www.marvell.com/content/dam/marvell/en/public-collateral/storage/marvell-storage-88se94xx-product-brief-2011-04.pdf
I'm not accustomed to interpreting hardware information at such a low level
myself, but it mentions offering "native 6Gb/s SATA interface support."
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2021-11-16 0:02 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-08 14:08 [Bug 214967] New: mvsas not detecting some disks bugzilla-daemon
2021-11-08 16:28 ` [Bug 214967] " bugzilla-daemon
2021-11-14 0:19 ` bugzilla-daemon
2021-11-14 0:56 ` bugzilla-daemon
2021-11-15 22:34 ` bugzilla-daemon
2021-11-15 23:13 ` bugzilla-daemon
2021-11-15 23:24 ` bugzilla-daemon
2021-11-15 23:34 ` bugzilla-daemon
2021-11-15 23:53 ` bugzilla-daemon
2021-11-15 23:59 ` bugzilla-daemon [this message]
2021-11-16 0:04 ` bugzilla-daemon
2021-11-16 0:04 ` bugzilla-daemon
2021-11-16 3:08 ` bugzilla-daemon
2021-11-16 3:11 ` bugzilla-daemon
2021-11-16 3:16 ` bugzilla-daemon
2021-11-16 8:09 ` bugzilla-daemon
2021-11-16 12:29 ` bugzilla-daemon
2021-11-16 23:55 ` bugzilla-daemon
2024-02-04 21:19 ` bugzilla-daemon
2025-01-18 3:07 ` bugzilla-daemon
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=bug-214967-11613-Pv7UjYNkSY@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-scsi@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