From: Ioannis Barkas <jnyb.de@gmail.com>
To: linux-ide@vger.kernel.org
Subject: Re: ASMedia ASM1166/ASM1064 port restrictions will break cards with port-multipliers
Date: Fri, 15 Mar 2024 23:19:54 +0200 [thread overview]
Message-ID: <CADUzMVaFcD26QiBK_eKCbtC5Ot-+hAruNbUx+2pQNTKtMhDGRA@mail.gmail.com> (raw)
Hello there,
This issue came to surface when I used my ASM1166 card with an
external SATA II JMB393 RAID PMP module.
In kernel 6.8 I get:
ahci 0000:02:00.0: AHCI 0001.0301 32 slots 32 ports 6 Gbps 0x3f impl SATA mode
ahci 0000:02:00.0: flags: 64bit ncq sntf stag pm led only pio slum
part deso sadm sds apst
In kernel 6.6 I get:
ahci 0000:02:00.0: AHCI 0001.0301 32 slots 32 ports 6 Gbps 0xffffff3f
impl SATA mode
ahci 0000:02:00.0: flags: 64bit ncq sntf stag pm led only pio slum
part deso sadm sds apst
PMP is attached at port #1 of the ASM116. Two SSDs are at port A and B
of the PMP.
In kernel 6.8 I can only see one SSD:
ata7: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
In kernel 6.6 I can see both SSDs:
ata7: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata15: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ASM1166 is not declaring PMP compliance at its capabilities but it
works on its own way if it is not touched. Upon touching it PMP
support is effectively disabled so only the first attached device is
visible. I believe the hflag is needed here.
The safest option would be a configurable parameter to set it per
case. My PMP can be set to RAID mode so it is possible to break RAID
arrays if a PMP is used on that ASMedia host or older ones.
Best regards,
Ioannis
next reply other threads:[~2024-03-15 21:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-15 21:19 Ioannis Barkas [this message]
2024-03-17 9:46 ` ASMedia ASM1166/ASM1064 port restrictions will break cards with port-multipliers Niklas Cassel
[not found] <CAFDm6W19R3KHDO09c94Uwry9mdG+whAVy=u4Sdpt30A2MK1KPA@mail.gmail.com>
2024-03-13 6:36 ` Andrey Melnikov
2024-03-13 17:37 ` Cryptearth
2024-03-13 21:21 ` Hans de Goede
2024-03-13 21:52 ` Re[2]: " Conrad Kostecki
2024-03-13 22:20 ` Hans de Goede
2024-03-16 14:01 ` Andrey Jr. Melnikov
2024-03-17 1:34 ` Cryptearth
2024-03-14 15:58 ` Niklas Cassel
2024-03-15 15:01 ` Hans de Goede
2024-03-16 11:33 ` Cryptearth
2024-03-17 9:36 ` Niklas Cassel
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=CADUzMVaFcD26QiBK_eKCbtC5Ot-+hAruNbUx+2pQNTKtMhDGRA@mail.gmail.com \
--to=jnyb.de@gmail.com \
--cc=linux-ide@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).